Re: [irs-discuss] draft-ward-irs-framework

Alia Atlas <akatlas@gmail.com> Mon, 30 July 2012 22:19 UTC

Return-Path: <akatlas@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 F2CDF11E820B for <irs-discuss@ietfa.amsl.com>; Mon, 30 Jul 2012 15:19:46 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D11E-69SU4bY for <irs-discuss@ietfa.amsl.com>; Mon, 30 Jul 2012 15:19:46 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2917511E81EB for <irs-discuss@ietf.org>; Mon, 30 Jul 2012 15:19:46 -0700 (PDT)
Received: by yenq13 with SMTP id q13so5848914yen.31 for <irs-discuss@ietf.org>; Mon, 30 Jul 2012 15:19:45 -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=1tUVZu6uIVZl1kkrz+dnNt8j8Nm0BK55csm6OFrdFqU=; b=GWDitlhj3vHMbYOcD5WDCecLzoLgZT9Br6tot+/Iwc6wxLrlPuZ7PUOTmJ7Up8FH3N CwO5OiMPz7gWBqYoDiPf61PepgvMp8/BajAHmndYG6aXWqXmpWbMygRCoXtBkTH3BpQv T2rKYa469Qmw3TrJNvOF9tJ+3eN2IlYVzNm4mdMTYV04chtk+s5AvSqiYpX1CNqFRudK g0Ao/uuQ3dDUbf8tuoFEiu16zAE5ZHcQ5TNcSSY+AivYY7Lyq2M69aH8sTXtP9zbUjpu 3aXR3Fx5y9ihSbi3rrDtBZGaMXRoxSJWIKMM/oP25rOsNmKh1JG/7C/VvAoCqiF2Gadb Ztsg==
MIME-Version: 1.0
Received: by 10.50.158.226 with SMTP id wx2mr85358igb.18.1343686785390; Mon, 30 Jul 2012 15:19:45 -0700 (PDT)
Received: by 10.50.34.169 with HTTP; Mon, 30 Jul 2012 15:19:45 -0700 (PDT)
In-Reply-To: <50156873.2030407@joelhalpern.com>
References: <17897894-CD09-482F-9F1A-F01CF44DC906@lucidvision.com> <50156873.2030407@joelhalpern.com>
Date: Mon, 30 Jul 2012 18:19:45 -0400
Message-ID: <CAG4d1reQME_VNsS-uh5BUnAHfS0G=EQ53sdZR9Xkt=v3GVVxXA@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: irs-discuss@ietf.org
Subject: Re: [irs-discuss] draft-ward-irs-framework
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 22:19:47 -0000

Joel,

Thanks for the feedback.  I think the problem-statement draft (now at
http://tools.ietf.org/html/draft-atlas-irs-problem-statement-00)
focuses a bit more on the problem and less on the protocol aspects.

The framework does try to describe the need for data models that have
semantic meaning included - and gives some ideas on what information
might want to be in some of those data-models.  To get the details
correct, I think we'll want to drive from agreed upon specific
vertical use-cases.

I do think that, assuming there is interest, we want to move forward
to use-cases and nail down a small set of data-models to focus on, at
least with their requirements.  There could be multiple transfer
protocols, if we needed them, but it's quite premature to focus on the
protocol specifics now.

As for the protocol, I tried to focus on the key aspects and/or goals
that we think the interface needs to have.  I do apologize for the
extensive use of "streaming" in the doc - I added the key aspects part
and obviously didn't prune out the streaming adjective everywhere.
The intent was to to imply the asynchronous, duplex nature - not, say,
TCP like streaming.

Alia

On Sun, Jul 29, 2012 at 12:44 PM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> As far as I can tell, the document could use signifiantly more clarity on
> the problem to be solved, and the information modeling gaps that appear to
> exist, and much less (maybe none) discussion of why a new protocol is
> needed.  It seems to me that the descriptions of existing protocols tend to
> be based on assumptions that are not borne out by the rest of the document.
>
> As an example, the assumption that the solution must be some form of
> streaming (whatever that means) is not grounded in the document.
>
> Yours,
> Joel M. Halpern
>
>
> On 7/29/2012 12:39 PM, Thomas Nadeau wrote:
>>
>>
>>         We wanted to kick off the discussion here about the framework
>> draft. What do you think? How can this be improved? Are we on the right
>> track?
>>
>>         The (proposed) Framework can be found here:
>>
>> http://lucidvision.com/draft-ward-irs-framework-00.txt
>>
>>         We will be sending out a problem statement draft later today as
>> well.
>>
>>         --Tom, Alia, Ward
>>
>>
>> _______________________________________________
>> 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