Re: [i2rs] I2RS topology is generic?

Alia Atlas <akatlas@gmail.com> Wed, 04 March 2015 21:52 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9B0B1AC3EA; Wed, 4 Mar 2015 13:52:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.399
X-Spam-Level:
X-Spam-Status: No, score=-101.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Te5W6S9Wcm-o; Wed, 4 Mar 2015 13:52:17 -0800 (PST)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C8CB1AC3E4; Wed, 4 Mar 2015 13:52:16 -0800 (PST)
Received: by oiav63 with SMTP id v63so8303613oia.8; Wed, 04 Mar 2015 13:52:14 -0800 (PST)
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=gdqDeuNUlbyNdZY5nrJyl7p72DYvVj4egNpPblUBiLM=; b=Af+koeP4x5SycNSngOP87YNkqaX+sPCOKXJHDF8giCMD6jc1jphBjxpp5cekrLgjRI dBVg00SsU0HR14YtBvPX42gKVHRvMWi+IHsu0LB6wVN2FJN4pZT3yFCWZoOWM9kIAz9P ItEqylDW8BtkmExp5sixq4v1jAj2iYfOfFWAPulLz3iT2LbrCuBkesOAzDktSMH4YtZH s/d0Z1wL0Pft5+GJ9FbrEBsmcyCzIBnq6eOcp8KzgnsyiZS21BE7kGSEQFhkwS8I8Ybq kFt4IroedBe71n53nyKqqmU2AHAKHFBkFjqR0ub5WzMHBDS3NNidLOO45axYbxDOfy2d buqg==
MIME-Version: 1.0
X-Received: by 10.60.57.9 with SMTP id e9mr4778854oeq.24.1425505934833; Wed, 04 Mar 2015 13:52:14 -0800 (PST)
Received: by 10.60.97.135 with HTTP; Wed, 4 Mar 2015 13:52:14 -0800 (PST)
In-Reply-To: <54F77E2B.6020104@cisco.com>
References: <54F77E2B.6020104@cisco.com>
Date: Wed, 04 Mar 2015 16:52:14 -0500
Message-ID: <CAG4d1rftLqhkY2hL+7CBp7MxPH05Zqt+1G=GNSrRYOLSSty=-w@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary="089e0149c4a8defc5f05107d767a"
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/jbF2OAqX7Nhrb2ghKz2zK-FsSi0>
Cc: "i2rs@ietf.org" <i2rs@ietf.org>, "supa-chairs@ietf.org" <supa-chairs@ietf.org>
Subject: Re: [i2rs] I2RS topology is generic?
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 04 Mar 2015 21:52:18 -0000

Hi Benoit,

Yes, as is clearly articulated in the draft,it is a generic topology into
which all other topology-related work should
plug.

I2RS and Alex are very happy to hear comments and reviews of that draft.

Regards,
Alia

On Wed, Mar 4, 2015 at 4:50 PM, Benoit Claise <bclaise@cisco.com> wrote:

>  Dear Alia,
>
> I would need your guidance. On my side, I'm trying to help the SUPA people
> with the scope of their work.
>
> During a SUPA call during which Sue explained the I2RS work (thanks again
> Sue), she answered a key question: any topology work should be based on the
> I2RS topology draft (draft-clemm-i2rs-yang-network-topo draft). This draft
> was called the generic topology model draft.
>
> Discussing further with the SUPA BoF chairs, it was observed that the I2RS
> charter doesn't mention it's a generic topology model. So please let us
> know what your intention is. Is this L3 topology a generic one, into which
> all others topology-related work should plug?
>
> The SUPA requirement is a way to express topology at several layers of
> abstraction (granularity).
>
> Regards, Benoit
>
>
>