Re: [Isis-wg] Accept as WG doc?

Ayan Banerjee <ayabaner@cisco.com> Fri, 13 February 2009 05:27 UTC

Return-Path: <ayabaner@cisco.com>
X-Original-To: isis-wg@core3.amsl.com
Delivered-To: isis-wg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE90C3A6407 for <isis-wg@core3.amsl.com>; Thu, 12 Feb 2009 21:27:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.202
X-Spam-Level:
X-Spam-Status: No, score=-5.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wf76vEf6CXoX for <isis-wg@core3.amsl.com>; Thu, 12 Feb 2009 21:27:36 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 76D8E3A684E for <isis-wg@ietf.org>; Thu, 12 Feb 2009 21:27:36 -0800 (PST)
X-IronPort-AV: E=Sophos; i="4.38,200,1233532800"; d="scan'208,217"; a="248676263"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 13 Feb 2009 05:27:42 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n1D5Rgsk002479; Thu, 12 Feb 2009 21:27:42 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n1D5RgXQ007811; Fri, 13 Feb 2009 05:27:42 GMT
Received: from xmb-sjc-22b.amer.cisco.com ([128.107.191.112]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 12 Feb 2009 21:27:42 -0800
Received: from 10.21.69.126 ([10.21.69.126]) by xmb-sjc-22b.amer.cisco.com ([128.107.191.112]) with Microsoft Exchange Server HTTP-DAV ; Fri, 13 Feb 2009 05:26:44 +0000
User-Agent: Microsoft-Entourage/12.15.0.081119
Date: Thu, 12 Feb 2009 21:26:42 -0800
From: Ayan Banerjee <ayabaner@cisco.com>
To: hannes@juniper.net, David Ward <dward@cisco.com>, chopps@rawdofmt.org
Message-ID: <C5BA4492.99EB%ayabaner@cisco.com>
Thread-Topic: [Isis-wg] Accept as WG doc?
Thread-Index: AcmNm6ce1/Go+MbEjUS27g3fY0szGg==
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3317318803_370094"
X-OriginalArrivalTime: 13 Feb 2009 05:27:42.0498 (UTC) FILETIME=[CB2D9820:01C98D9B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5104; t=1234502862; x=1235366862; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ayabaner@cisco.com; z=From:=20Ayan=20Banerjee=20<ayabaner@cisco.com> |Subject:=20Re=3A=20[Isis-wg]=20Accept=20as=20WG=20doc? |Sender:=20; bh=w2SBEKHXNXQk7UM6ipoIMq9/h4uhmoLBJlBXXXF4qbA=; b=RcOdO6yLieEc03zLRhZX/xXz6v5D2nMcabIqWcLCk1yaaDdzciiZjsS4Xn XtrTkWN3fF89k74GHh4ovqNzuMPRqQrm+pbc1T1YA/t8NNQ5EbC/GMGjD8dY 5eaFtNcmFg;
Authentication-Results: sj-dkim-4; header.From=ayabaner@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
Cc: isis-wg@ietf.org
Subject: Re: [Isis-wg] Accept as WG doc?
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Fri, 13 Feb 2009 05:27:41 -0000

Hannes,

We propose to carry multicast information in a new Multicast-Group PDU to
address:
 ­Rapid join/leave multicast group events to not impact unicast-spf/lsp
flooding 
 ­Management separation of multicast group information
 ­Increase LSP-ID space for large volumes of multicast information
 ­Efficient SPF runs and multicast-attachment updates due to database
separation 
 ­Inter-operability with older implementations is not of any concern

Please note that 
(a) ³Extending LSP space² draft can be used in addition to what is being
proposed. 
(b) ³Multiple instances² draft separates the databases. However, here the
multicast 
information is to be used in conjunction with the uni-cast information.

Thanks,
Ayan

 hi david, et al,
 
 may i ask why there is need for dedicated PDU types ?
 
 i feel a bit of discomfort adding a set of new PDU types
 which only cover existing functionality, just because of
 of extending or seperating LSP space. it is my view that
 we already have vehicles to address that.
 
 two (hard) questions:
 
 1. why is the "multiple instances" draft not good enough
    seperating the different databases ? it seems like
    we are getting down the road of PDU-type being
    a functional database multiplexer.
 
 2. why is the "extending LSP space" draft not good enough
    if LSP space shortage is of concern ?
 
 /hannes
 
 On Tue, Feb 03, 2009 at 03:54:17PM -0600, David Ward wrote:
 | All -
 | 
 | Please let us know if you believe this document should be accepted as
 | a WG document:
 | 
 | http://tools.ietf.org/html/draft-ward-l2isis-04
 | 
 | Thanks
 | 
 | Chris, Dave
 | _______________________________________________
 | Isis-wg mailing list
 | Isis-wg@ietf.org
 | https://www.ietf.org/mailman/listinfo/isis-wg