Re: [irs-discuss] New Non-WG Mailing List: irs-discuss -- Interface to The Internet Routing System (IRS)

"Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lucent.com> Wed, 29 August 2012 19:46 UTC

Return-Path: <pranjal.dutta@alcatel-lucent.com>
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 5484221F84F9; Wed, 29 Aug 2012 12:46:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.46
X-Spam-Level:
X-Spam-Status: No, score=-7.46 tagged_above=-999 required=5 tests=[AWL=-0.861, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EKgk4b2HJ3px; Wed, 29 Aug 2012 12:46:54 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id B08C621F84F2; Wed, 29 Aug 2012 12:46:54 -0700 (PDT)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q7TJko81019480 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 29 Aug 2012 14:46:52 -0500 (CDT)
Received: from INBANSXCHHUB03.in.alcatel-lucent.com (inbansxchhub03.in.alcatel-lucent.com [135.250.12.80]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q7TJkm7W031877 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 30 Aug 2012 01:16:48 +0530
Received: from INBANSXCHMBSA3.in.alcatel-lucent.com ([135.250.12.53]) by INBANSXCHHUB03.in.alcatel-lucent.com ([135.250.12.80]) with mapi; Thu, 30 Aug 2012 01:16:47 +0530
From: "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lucent.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, "forces@ietf.org" <forces@ietf.org>
Date: Thu, 30 Aug 2012 01:16:45 +0530
Thread-Topic: [irs-discuss] New Non-WG Mailing List: irs-discuss -- Interface to The Internet Routing System (IRS)
Thread-Index: Ac2EdvQovMF6DegBTteBe7s7RqbWJwBpq4qQ
Message-ID: <C584046466ED224CA92C1BC3313B963E13F0B8C5D3@INBANSXCHMBSA3.in.alcatel-lucent.com>
References: <20120727004529.5739.53836.idtracker@ietfa.amsl.com> <20120824160539.GA2134@laperouse.bortzmeyer.org>
In-Reply-To: <20120824160539.GA2134@laperouse.bortzmeyer.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: "tnadeau@juniper.net" <tnadeau@juniper.net>, "wardd@cisco.com" <wardd@cisco.com>, "akatlas@juniper.net" <akatlas@juniper.net>, "irs-discuss@ietf.org" <irs-discuss@ietf.org>
Subject: Re: [irs-discuss] New Non-WG Mailing List: irs-discuss -- Interface to The Internet Routing System (IRS)
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: Wed, 29 Aug 2012 19:46:55 -0000

I am not quite sure about this. We find the problem statement of IRS as follows:

<>
   In order to enable applications to have access to and control over
   information in the Internet's routing system, we need a publically
   documented interface specification.  The interface needs to support
   real-time, transaction-based interactions using efficient data models
   and encodings.  Furthermore, the interface must support a variety of
   use cases including those where verified control feed-back loops are
   needed. </>

The way I understand, it's about building flexible/programmable 
abstractions into Routing Systems - It's not necessary that entire control plane is taken away. So I don't see the framework as complete separation 
of control plane and data plane.

The IRS frame work further highlights Bidirectional Interfaces to the Routing System.

Thanks,
Pranjal


-----Original Message-----
From: irs-discuss-bounces@ietf.org [mailto:irs-discuss-bounces@ietf.org] On Behalf Of Stephane Bortzmeyer
Sent: Friday, August 24, 2012 9:06 AM
To: forces@ietf.org
Cc: tnadeau@juniper.net; irs-discuss@ietf.org; akatlas@juniper.net; wardd@cisco.com
Subject: Re: [irs-discuss] New Non-WG Mailing List: irs-discuss -- Interface to The Internet Routing System (IRS)

On Thu, Jul 26, 2012 at 05:45:29PM -0700,
 IETF Secretariat <ietf-secretariat@ietf.org> wrote 
 a message of 34 lines which said:

> A new IETF non-working group email list has been created.
> 
> List address: irs-discuss@ietf.org
> Archive: http://www.ietf.org/mail-archive/web/irs-discuss/
> To subscribe: https://www.ietf.org/mailman/listinfo/irs-discuss

It really looks like very close from what the Forces working group
have been doing. Can anyone explain why we need to start a new
project?
_______________________________________________
irs-discuss mailing list
irs-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/irs-discuss