[rbridge] Parent node ID selection for multi destination trees

varshah <varshah@cisco.com> Sat, 17 March 2012 00:46 UTC

Return-Path: <rbridge-bounces@postel.org>
X-Original-To: ietfarch-trill-archive-Osh9cae4@ietfa.amsl.com
Delivered-To: ietfarch-trill-archive-Osh9cae4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCEB321E8083 for <ietfarch-trill-archive-Osh9cae4@ietfa.amsl.com>; Fri, 16 Mar 2012 17:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level:
X-Spam-Status: No, score=-3.135 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, RCVD_NUMERIC_HELO=2.067]
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 g+9VzaqtQr2I for <ietfarch-trill-archive-Osh9cae4@ietfa.amsl.com>; Fri, 16 Mar 2012 17:46:30 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5B55721E8014 for <trill-archive-Osh9cae4@lists.ietf.org>; Fri, 16 Mar 2012 17:46:30 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q2H0V9rr021870; Fri, 16 Mar 2012 17:31:10 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q2H0UfWJ021828 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Fri, 16 Mar 2012 17:30:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2959; q=dns/txt; s=iport; t=1331944250; x=1333153850; h=date:subject:from:to:message-id:mime-version; bh=0r2gq0/KSBwYp8C0S2JrPgVEEiH536jZoRUD1Zyyc+U=; b=eOsy2V6yNJMs88oUGRFRVu+8ZKBGl7t5rPzUfPaOw0qfh2sztE2Kgc5p MushxRIgeQSd7x1WDd/MO58s4A4ELUoPgofWqb7WGcQk5zhGJzt/7GwWR uEjtM1NR0M04klDQ6xoqz20S5bQ30HnHSeqeRDRJ00Z2tGIIlxhdY1QCy s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqgKAKTaY0+tJXHB/2dsb2JhbABCgkarCQGHeHUCgQeCCwEEEgEUFk4BDAEEgRUBBDWHZwELmTGBJ58sjVeDIgSIIzOFKodmjj8ngUGDBg
X-IronPort-AV: E=Sophos; i="4.73,601,1325462400"; d="scan'208,217"; a="64174929"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-9.cisco.com with ESMTP; 17 Mar 2012 00:30:40 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id q2H0Ue7M011883 for <rbridge@postel.org>; Sat, 17 Mar 2012 00:30:40 GMT
Received: from xmb-rcd-209.cisco.com ([72.163.62.216]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 16 Mar 2012 19:30:39 -0500
Received: from 171.70.224.21 ([171.70.224.21]) by XMB-RCD-209.cisco.com ([72.163.62.216]) with Microsoft Exchange Server HTTP-DAV ; Sat, 17 Mar 2012 00:30:39 +0000
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Fri, 16 Mar 2012 17:30:36 -0700
From: varshah <varshah@cisco.com>
To: rbridge@postel.org
Message-ID: <CB89293C.1B4D9%varshah@cisco.com>
Thread-Topic: Parent node ID selection for multi destination trees
Thread-Index: Ac0D1Su3nMSoQBCcN0SVRzVksbkNFg==
Mime-version: 1.0
X-OriginalArrivalTime: 17 Mar 2012 00:30:39.0662 (UTC) FILETIME=[2DE6A4E0:01CD03D5]
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: varshah@cisco.com
Subject: [rbridge] Parent node ID selection for multi destination trees
X-BeenThere: rbridge@postel.org
X-Mailman-Version: 2.1.6
Precedence: list
List-Id: "Developing a hybrid router/bridge." <rbridge.postel.org>
List-Unsubscribe: <http://mailman.postel.org/mailman/listinfo/rbridge>, <mailto:rbridge-request@postel.org?subject=unsubscribe>
List-Archive: <http://mailman.postel.org/pipermail/rbridge>
List-Post: <mailto:rbridge@postel.org>
List-Help: <mailto:rbridge-request@postel.org?subject=help>
List-Subscribe: <http://mailman.postel.org/mailman/listinfo/rbridge>, <mailto:rbridge-request@postel.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0867287770=="
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi,

Reading section 4.5 of RFC 6325
(http://tools.ietf.org/html/rfc6325#section-4.5) it seems that the selection
of a parent node  (7 byte- node ID) for a node N on a multi destination tree
j; should be based on j % p, where p is the number of equal cost parent
nodes to reach node N from root node R.

The intent seems to use lowest parent node ID for tree 1, next for tree 2
and so on.... And circle through if we have more possible trees than parent
nodes.

However, the trees are numbered starting 1, and the parent node IDs are
indexed starting 0 to (p ­ 1).  So, for a node N, when the network supports
2 trees and with two possible parent nodes,  we would use

parent node indexed at 1 for tree 1, j % p --> 1 % 2 = 1 and
Parent node indexed at 0 for tree 2, j % p --> 2 % 2 = 0.

To stay with the real intention, it would help if we had (j - 1) %p.

In that case,
parent node indexed at 0 for tree 1, (j  - 1)% p --> 0 % 2 = 0 and
Parent node indexed at 1 for tree 2,( j ­ 1) % p --> 1 % 2 = 1.

Thanks,
-Varun
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge