Re: [i2rs] Call for Adoption by WG: draft-atlas-i2rs-architecture-01 (ends Aug 12)

Alia Atlas <akatlas@gmail.com> Tue, 13 August 2013 20:26 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D41711E81C7 for <i2rs@ietfa.amsl.com>; Tue, 13 Aug 2013 13:26:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level:
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 qF6KRbpd6rFZ for <i2rs@ietfa.amsl.com>; Tue, 13 Aug 2013 13:26:42 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 86C5211E81C3 for <i2rs@ietf.org>; Tue, 13 Aug 2013 13:26:24 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id ta17so10808857obb.4 for <i2rs@ietf.org>; Tue, 13 Aug 2013 13:26:24 -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=70ZFD6fyomE2a0CJvZDaZABskIbgpaaSMYq86puCvKA=; b=Ojpqba8IhfA4P73FT16MZzFKVcTjfv3MIf6IIYBC6mXfBmukP2AMhj/1FLRuLoNCaT MT/DQ8KGN5wtjvZP9RBLASqafdHWNX9mpcUKj1O0sd+CAZYGbIwCg6ehrp+CTQ8QwUP4 VOoZ06G75xNGm1YfYkOn4XjviPMGkEobC82vjRzAslZoXfyDqpNHgtDvdj6rzJa5y6IN 2Y7GSOJz69lUCV6+uSpFltQEwobz84/8/kv1FZE5nfNrD/+wZApBjqHltRfVJJ4bK6be U0zG7y/kGcEUC4puz15gkPL9dZ1WCztVdA9rramQ0Ne5Ed0HSDic7sDcFYpQz5uGc28o PSSA==
MIME-Version: 1.0
X-Received: by 10.182.214.98 with SMTP id nz2mr5548098obc.37.1376425584001; Tue, 13 Aug 2013 13:26:24 -0700 (PDT)
Received: by 10.182.221.98 with HTTP; Tue, 13 Aug 2013 13:26:23 -0700 (PDT)
In-Reply-To: <CAAFAkD9SvCRLgtJxU4quoR08AT3BLPCDxifsjYW7xzp-WtxeWg@mail.gmail.com>
References: <CAG4d1rdDqdajvUeF4WwJ1Jwn_=xqOMkXrkWwCHtsdsZn6WKzRA@mail.gmail.com> <CAAFAkD9SvCRLgtJxU4quoR08AT3BLPCDxifsjYW7xzp-WtxeWg@mail.gmail.com>
Date: Tue, 13 Aug 2013 16:26:23 -0400
Message-ID: <CAG4d1rcRA2Q3qVH2KR=2p_PeqXowijCMhfRZz=TU-B8qicSNGw@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: Jamal Hadi Salim <hadi@mojatatu.com>
Content-Type: multipart/alternative; boundary="e89a8ff1cefefe944e04e3da0d39"
Cc: "i2rs@ietf.org" <i2rs@ietf.org>
Subject: Re: [i2rs] Call for Adoption by WG: draft-atlas-i2rs-architecture-01 (ends Aug 12)
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i2rs>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 20:26:46 -0000

Hi Jamal,

Thanks for your comments.  Responses in-line.

Alia

On Thu, Aug 1, 2013 at 5:07 AM, Jamal Hadi Salim <hadi@mojatatu.com> wrote:

> I have the draft and support its adoption.
>
> Some comments:
> 1) ForCES model can support different levels of granularities. Yes,
> original intent
> was to do datapath control-southbound interfaces; but it is very usable in
> wide
> range of applications that desire a model. Example, if you attended the
> ForCES
> meeting you may have seen a demo where ForCES was used to model VMs
> doing arbitrary network functions where the ForCES was then used to
> orchestrate
> that infrastructure.
>

[Alia] You have been talking about ForCES as being applicable for quite a
while.  It would be interesting to read a draft that does the
compare/contrast for I2RS as well as the data-model for the RIB info model.
  There are also concerns about duplicating data models in different
technologies and issues around tool-chain availability and automation.


> 2) I think we may end up needing more clarity on the transport. Merely
> saying
> you'd use congestion-aware transport and spelling out desire for different
> levels of reliability is insufficient. An I2RS agent is a proxy;
> reliability and congestion
> control need to take into consideration those two requirements above the
> transport layer.
>

[Alia] Yes, the transport needed depends on the communication pattern being
used and that ties to the data-models as well.  I think we need a protocol
requirements draft that describes some of this in more detail.  I have the
idea that I2RS would have a default transport - and then some information
streams may only be available over a different transport channel - or the
client could request data across a different transport channel and so on.


> 3) identity/roles
> It would be useful to specify some sample space of common practise.
>

[Alia] Sure - I think this has to come out of the security space.  I've
heard suggestions about looking at the NetConf Access Control Model
(RFC6536).  I believe that Wes George was looking at some ideas and there
were a number of security-related folks interested at the WG meeting.

Regards,
Alia


> cheers,
> jamal
>
> On Wed, Jul 24, 2013 at 5:52 PM, Alia Atlas <akatlas@gmail.com> wrote:
> > Please review draft-atlas-i2rs-architecture-01 and comment on whether it
> > should be adopted by I2RS.  Detailed technical conversation is also most
> > welcome.
> >
> > Authors: Are you aware of any IPR that applies to
> > draft-atlas-i2rs-architecture-01? Is so, has this IPR been disclosed in
> > compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for
> more
> > details).
> >
> > This WG call for adoption will complete on August 12.
> >
> > Thanks,
> > Alia
> >
> > _______________________________________________
> > i2rs mailing list
> > i2rs@ietf.org
> > https://www.ietf.org/mailman/listinfo/i2rs
> >
>