IETF Logo Mail Archive

Re: [i2rs] I2RS topology is generic?

Benoit Claise <bclaise@cisco.com> Wed, 04 March 2015 22:11 UTC

Return-Path: <bclaise@cisco.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 098F21A892A; Wed, 4 Mar 2015 14:11:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.91
X-Spam-Level:
X-Spam-Status: No, score=-13.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 2-yEBLKRyVLf; Wed, 4 Mar 2015 14:11:54 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F00DB1A8756; Wed, 4 Mar 2015 14:11:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4626; q=dns/txt; s=iport; t=1425507114; x=1426716714; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=f7MW0KEcxSxI2tZsr1FvN/XMRD5jQ5ZcuN2GQ8OZ1rk=; b=Aivv1gJM9ZAsNRQ7+B9QYFPTbp68NdYBbPhBrcMX+9BG0BmVUbRKUL02 UNUumDgAlS+BkB98ytDt9t/UCakVCK5EYrdJGyl/bjy4hMCviozA9TmdO obu03xETWtHL7pNvTHWVstvVBYoP2gZTp/TQU8VBNxDc1GcmR1iMk/wVr c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ChBQAHg/dU/xbLJq1ahC6DC8QEAoFvAQEBAQEBfIQQAQEEI1UBEAsECgoJFggDAgIJAwIBAgE0EQYNAQUCAQGIK71YmloBAQEBAQEBAQEBAQEBAQEBAQEBAQEXixKEbgeCaIFDBYpigyKLTIEagyaCMok4g0AjhA0fMYJDAQEB
X-IronPort-AV: E=Sophos;i="5.11,343,1422921600"; d="scan'208,217";a="370825816"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 04 Mar 2015 22:11:50 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t24MBo2A026729; Wed, 4 Mar 2015 22:11:50 GMT
Message-ID: <54F78325.5090806@cisco.com>
Date: Wed, 04 Mar 2015 16:11:49 -0600
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Alia Atlas <akatlas@gmail.com>
References: <54F77E2B.6020104@cisco.com> <CAG4d1rftLqhkY2hL+7CBp7MxPH05Zqt+1G=GNSrRYOLSSty=-w@mail.gmail.com>
In-Reply-To: <CAG4d1rftLqhkY2hL+7CBp7MxPH05Zqt+1G=GNSrRYOLSSty=-w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070700090201010906040306"
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/UyemMecT3N-3KsyXh91sP8xA7fQ>
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 22:11:56 -0000

Thank you Alia.

Regards, Benoit
> 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 
> <mailto: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
>
>
>

v2.23.0 | Report a Bug | By Email