Re: [irs-discuss] Rough Draft IRS Charter

Christopher LILJENSTOLPE <liljenstolpe@gmail.com> Mon, 05 November 2012 19:43 UTC

Return-Path: <liljenstolpe@gmail.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 7312521F8448 for <irs-discuss@ietfa.amsl.com>; Mon, 5 Nov 2012 11:43:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 5KLNvl35D0cO for <irs-discuss@ietfa.amsl.com>; Mon, 5 Nov 2012 11:43:17 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0526821F881F for <irs-discuss@ietf.org>; Mon, 5 Nov 2012 11:43:11 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so2813137dan.31 for <irs-discuss@ietf.org>; Mon, 05 Nov 2012 11:43:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=BcwIypqyGnMKu5Zj4XjiLQz6VKwp5EEjAvwRks1g+bg=; b=eqK2Y5O3sCiMVGqn2GATUjt32kw31nuf6EjX4x6gopIDO4VKYdqBuTI4Bn7xx8xpIv vwJD9VwLkhXn8B0bpwzF+lL6mI/KDvAgP9xxniV2wJyP40Htwzc167kyc7jtFCVuI5gl GyWPr5j52qD6OyETStZPu75tbpbejZRqCjJMt6SSMHKECrFWA8ugUg3oaUXdpcMCF6RI InpR2yo8jfIZpyLhLS07XHgARulUfFuqSg646cfOYPv+uxj6XT0i+gegrcbzyYzbP+V3 xZ6DqeRnMeFHLBIAfxDxOZyuY1dbvpM6z7Xjpid1F4nA9DTHrrNEZR+oAm1H+kyc0qeB 48nQ==
Received: by 10.68.224.9 with SMTP id qy9mr33166799pbc.3.1352144591828; Mon, 05 Nov 2012 11:43:11 -0800 (PST)
Received: from dhcp-6450.meeting.ietf.org (dhcp-6450.meeting.ietf.org. [130.129.100.80]) by mx.google.com with ESMTPS id se4sm11005290pbb.13.2012.11.05.11.43.09 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 05 Nov 2012 11:43:10 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Christopher LILJENSTOLPE <liljenstolpe@gmail.com>
In-Reply-To: <00d901cdbb58$76572070$63056150$@olddog.co.uk>
Date: Mon, 5 Nov 2012 11:43:08 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <5EEE5819-2A40-4FE7-AA39-D93F78E12B2A@gmail.com>
References: <DF7F294AF4153D498141CBEFADB17704C7EC9FE484@EMBX01-WF.jnpr.net> <282BBE8A501E1F4DA9C775F964BB21FE519702F264@GRFMBX704BA020.griffon.local> <62CCD4C52ACDAD4481149BD5D8A72FD30251AA11@CH1PRD0510MB355.namprd05.prod.outlook.com> <00d901cdbb58$76572070$63056150$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1499)
Cc: 'Ross Callon' <rcallon@juniper.net>, 'Capello Alessandro' <alessandro.capello@telecomitalia.it>, 'Maglione Roberta' <roberta.maglione@telecomitalia.it>, dward@cisco.com, irs-discuss@ietf.org
Subject: Re: [irs-discuss] Rough Draft IRS Charter
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, 05 Nov 2012 19:43:17 -0000

Greetings all,

On 05Nov2012, at 05.21, "Adrian Farrel" <adrian@olddog.co.uk> wrote:

<snip>
>  
> Hello,
>  I have a question on working item 2:
>  
> “The working group is chartered to work on the following items:
>  
> 2.       Tightly scoped key use cases for operational use of IRS. These use cases will include at least:
> a.       Interactions with the RIB
> b.      Association of routing policies with routing state
> c.       The ability to extract information about topology from the network
> “
> Does this bullet exclude the possibility to use IRS to gather information about network measurements such as available bandwidth on a link, information related to jitter delay for specific flows etc. ?

<snip>

However, I would want to test those use cases against existing capabilities BEFORE adding more use cases.  I'm not sure I'm in favor of replicating work and capabilities already done elsewhere (i.e. bandwidth available on a link, etc).

	Chris