IETF Logo Mail Archive

Re: [Isis-wg] FW: New Version Notification for draft-ginsberg-isis-l2bundles-00.txt

"Ahmed Bashandy (bashandy)" <bashandy@cisco.com> Mon, 27 July 2015 18:08 UTC

Return-Path: <bashandy@cisco.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B33671B315B for <isis-wg@ietfa.amsl.com>; Mon, 27 Jul 2015 11:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 BHaeGwmqTuHa for <isis-wg@ietfa.amsl.com>; Mon, 27 Jul 2015 11:08:54 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9E541B316B for <isis-wg@ietf.org>; Mon, 27 Jul 2015 11:08:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1019; q=dns/txt; s=iport; t=1438020533; x=1439230133; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=G/t7UNUKzE79IFoDnW0luz/kHA3EbEakqUemsKYEy3M=; b=Q5vHYgQT6ZKEefSrQ22VqV8XYVV50eEdiioWm8V/KUuxP96q5aZWA66q 7vigYgPQcV81mkEfbH+IxA80UhKMdMStFbamSyWCBx0DPlRF5b/jFYnvG Ga1MIFa5HAEXP/MlPXGg6VtLKpXrdXMTf2hJHtIfhVaMXnI3GWh6v1IH2 I=;
X-IronPort-AV: E=Sophos;i="5.15,556,1432598400"; d="scan'208";a="13513545"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-8.cisco.com with ESMTP; 27 Jul 2015 18:08:53 +0000
Received: from [128.107.165.110] (dhcp-128-107-165-110.cisco.com [128.107.165.110]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t6RI8qE1030280; Mon, 27 Jul 2015 18:08:53 GMT
Message-ID: <55B673B4.70208@cisco.com>
Date: Mon, 27 Jul 2015 11:08:52 -0700
From: "Ahmed Bashandy (bashandy)" <bashandy@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
References: <20150706195853.3266.51125.idtracker@ietfa.amsl.com> <F3ADE4747C9E124B89F0ED2180CC814F594896C2@xmb-aln-x02.cisco.com> <alpine.DEB.2.02.1507201536560.11810@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1507201536560.11810@uplift.swm.pp.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/puM2mrBMcEQS5wNFjq3TjJoGcAY>
Cc: "isis-wg@ietf.org list" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] FW: New Version Notification for draft-ginsberg-isis-l2bundles-00.txt
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2015 18:08:55 -0000

Hi,

See inline "AB>"

Ahmed

On 7/20/2015 6:42 AM, Mikael Abrahamsson wrote:
> On Mon, 6 Jul 2015, Les Ginsberg (ginsberg) wrote:
>
>> Folks -
>>
>> A new draft has been submitted. Comments welcome.
>
> It would be interesting to see text in there how this would interact 
> with BFD and/or LACP and ip address configuration.
AB> All this draft is doing is advertising TE attributes for each 
individual member and adj-SID to allow traffic to be explicitly directed 
towards one or more member links. Nothing more than this:)

>
> If I understand correctly, LACP isn't used, IP address isn't 
> configured on the individual interfaces? So, BFD can't be used for 
> individual links? Where is the IP address configured, just on one of 
> the interfaces?
>
> I have no opinion on the ISIS parts of this, I just don't understand 
> operational considerations and I would appreciate (more) text on this 
> topic.

AB> Can you be more specific about the operational considerations?

Ahmed

v2.23.0 | Report a Bug | By Email