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

Benson Schliesser <bensons@queuefull.net> Fri, 24 August 2012 16:24 UTC

Return-Path: <bensons@queuefull.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 9AB5421F8683 for <irs-discuss@ietfa.amsl.com>; Fri, 24 Aug 2012 09:24:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.699
X-Spam-Level:
X-Spam-Status: No, score=-3.699 tagged_above=-999 required=5 tests=[AWL=-0.100, 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 i7ECFa8FGiNH for <irs-discuss@ietfa.amsl.com>; Fri, 24 Aug 2012 09:24:15 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4BAC421F85C3 for <irs-discuss@ietf.org>; Fri, 24 Aug 2012 09:24:15 -0700 (PDT)
Received: by dadf8 with SMTP id f8so1027452dad.31 for <irs-discuss@ietf.org>; Fri, 24 Aug 2012 09:24:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=pr0Aa+VVhR2Uo9/bkCQIrmDgmLoDS9I+14wAmvdADBQ=; b=gAX3zC1eQ0MrHwaet3RLIXQrh/YiNTbcdko0N+o07ngSwa7s6fojIsgOTGD+Fj03Y+ KQUrpNUD7/o5pGi9XU0ObSTst2Ufjn7heDtc2DDGE2q6hf6ZJfTVQgPR28pbpND92TMr mXBkwJEO2YfaaXUfwt6CjFc+8jUQRKciAlTIRRdFhbl5nKL7oN5tgT5REpevU+BuBtgK w17e6bU2u1+AktCgc+H9LEhO21jRHRju1zl8ZIqal4fnUQHDBdh8hfwBpf/5SlY34Jug 7wDiN4YVqCMhMgXqqQ9YKsn0Ihl3JdmNRVa7Gs0Vi1BetJGoXWAPJGaFuz2VMyg/IYpv UKXg==
Received: by 10.68.238.74 with SMTP id vi10mr14085439pbc.48.1345825455075; Fri, 24 Aug 2012 09:24:15 -0700 (PDT)
Received: from wasteland.local (natint3.juniper.net. [66.129.224.36]) by mx.google.com with ESMTPS id gf3sm8573158pbc.74.2012.08.24.09.24.12 (version=SSLv3 cipher=OTHER); Fri, 24 Aug 2012 09:24:13 -0700 (PDT)
Message-ID: <5037AAAC.7090907@queuefull.net>
Date: Fri, 24 Aug 2012 11:24:12 -0500
From: Benson Schliesser <bensons@queuefull.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
References: <20120727004529.5739.53836.idtracker@ietfa.amsl.com> <20120824160539.GA2134@laperouse.bortzmeyer.org>
In-Reply-To: <20120824160539.GA2134@laperouse.bortzmeyer.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQm2amaa+jXRJLx9TnWdS0Zk9qnXbkYTo+Q3H/0V5Fz0LX/rWenDPPCtPMJFKum5K0xXkUXh
Cc: tnadeau@juniper.net, wardd@cisco.com, forces@ietf.org, akatlas@juniper.net, irs-discuss@ietf.org
Subject: Re: [irs-discuss] [forces] 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: Fri, 24 Aug 2012 16:24:16 -0000

Hi, Stephane.

On 8/24/12 11:05 AM, Stephane Bortzmeyer wrote:
>> 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?

At a high level, I think there is a different assumption about where the 
control-plane resides. In IRS the forwarding and control planes might be 
co-resident in the router (i.e. not "separated"), and the IRS protocol 
would be a way of extending limited control over routing state to 
external applications.

If I understand ForCES correctly (which is possibly not the case) then I 
imagine it could be used in a similar architecture and/or as a protocol 
layer for IRS. But the first step in the context of IRS is to make a 
problem statement, understand requirements, etc.

Others might have more intelligent comments, which I welcome. :) But 
please let me know if this perspective helps clarify things, and/or if 
I'm missing some ideas that I should understand better, etc.

Cheers,
-Benson