[trill] Order of bits in TRILL bitmaps

Petr Hroudný <petr.hroudny@gmail.com> Thu, 21 August 2014 06:37 UTC

Return-Path: <petr.hroudny@gmail.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFDC81A6F7F for <trill@ietfa.amsl.com>; Wed, 20 Aug 2014 23:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.299
X-Spam-Level:
X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] 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 dzSL5yEBuw9R for <trill@ietfa.amsl.com>; Wed, 20 Aug 2014 23:37:47 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DED01A0AD5 for <trill@ietf.org>; Wed, 20 Aug 2014 23:37:47 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id f8so8132615wiw.6 for <trill@ietf.org>; Wed, 20 Aug 2014 23:37:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=OODHtkDrX6M9mXXBzAI36KoIN26M8aLiDWo/0h5ED88=; b=wTEUSF8VHxYs8NzGoDwVbauQcdnWa9xdOOXctdPqcQoqJQcvle1wCxG9+yF7ie6jwg Cd/QxNmVC2owKPYhMJ+6VUOBtcFTu116R2/JhujQk0y345SVSIDRmIOJ9Eb2zHQZ0Bto HB33sALJsjLE1OqncBVl39gNGj72b2FmkJgNu0eD3bKGG5AyQVXv3POleR2qyMxYN0cH /e3UKltaw33vRs2Z83uT4phkBH5MJppBHX0oZjLNg5LNLwWpuzWhlXQ5t/1zFdH//cyY biApWtL4yc4LzfaLHn7FG4kkaXyP7IGCXhWwnhkrkiYCVLgt2aSzC710PgFvN5MLgvYG O34A==
MIME-Version: 1.0
X-Received: by 10.195.13.79 with SMTP id ew15mr62277099wjd.19.1408603066090; Wed, 20 Aug 2014 23:37:46 -0700 (PDT)
Received: by 10.180.21.101 with HTTP; Wed, 20 Aug 2014 23:37:46 -0700 (PDT)
Date: Thu, 21 Aug 2014 08:37:46 +0200
Message-ID: <CANi4_5fGtOVvC0nwqdoWXEv5AraQR_UY4NmYuaUYvpt5xjvQyQ@mail.gmail.com>
From: Petr Hroudný <petr.hroudny@gmail.com>
To: trill@ietf.org
Content-Type: multipart/alternative; boundary="047d7bfd093a6249d805011df5fa"
Archived-At: http://mailarchive.ietf.org/arch/msg/trill/_vFlPTazl13jG4Jumf9cMP87UIA
Subject: [trill] Order of bits in TRILL bitmaps
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Aug 2014 06:41:32 -0000

Hi all,

I'm looking for the WG opinion about the correct order of bits in bitmaps
specified in RFC7176 sections 2.2.2 & 2.2.5 and 2.2.4 & 2.3.1.

For the first two, the RFC says:

   o  VLAN bit-map: The highest-order bit indicates the VLAN equal to
      the start VLAN ID, the next highest bit indicates the VLAN equal
      to start VLAN ID + 1, continuing to the end of the VLAN bit-map
      field.

I understand this as follows: if only the start VLAN ID is enabled,
the bitmap should have a value of 0x80.

Nevertheless, I've seen an implementation, where the bitmap reads 0x01.

Which one is correct?


For the second two, the RFC says:

   o  Capabilities and Header Flags Supported: A bit vector of 32 bits
      numbered 0 through 31 in network order.

I understand this as follows: if I want to set the FGL-safe bit (bit
1), the bitmap should read 0x40 0x00 0x00 0x00.

Nevertheless, I've seen an implementation, where the bitmap reads
0x00, 0x00, 0x00, 0x40

Which one is correct?


As this might create a serious interop issues, I'm seeking for WG
opinion on this.



    Thanks, Petr