Re: [netmod] bit positions

Ladislav Lhotka <lhotka@nic.cz> Wed, 19 December 2018 12:46 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EC93130DFA for <netmod@ietfa.amsl.com>; Wed, 19 Dec 2018 04:46:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 YL-Fa9aBgYHj for <netmod@ietfa.amsl.com>; Wed, 19 Dec 2018 04:46:21 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC001130DFE for <netmod@ietf.org>; Wed, 19 Dec 2018 04:46:21 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:718:1a02:1::380]) by mail.nic.cz (Postfix) with ESMTPSA id 6E38D60604; Wed, 19 Dec 2018 13:46:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1545223580; bh=3nnnEkXAyIc0IhJ3FKZhJoWTAsfKqvvZlmavZHJMn7o=; h=From:To:Date; b=yOg593IVAPPbkQzXzJxEjD0KVnu6FFEV7OO5vRlUuEAQ+ovmHndrUqViJENpcadBw 3zpIKYfBnNLVLhqotFgUu5HJ+WPKFaLFHU89x1Q0bBhV3NR1MDEQ3i6X8yD5ONCU2y TJa/CX/F3/H4uSzIeXtK3s1EyjyZdN68H3CZyH/E=
Message-ID: <a2b8d61f0bdd644349c749f283ad5c0f6b84617a.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Cc: NETMOD WG <netmod@ietf.org>
Date: Wed, 19 Dec 2018 13:46:20 +0100
In-Reply-To: <20181219124246.lvkiwofmq6wk4p5o@anna.jacobs.jacobs-university.de>
References: <0e6b0f62bbea33615a77d909dfde7098372f889b.camel@nic.cz> <20181219121617.7galbbhjy4bgqyo4@anna.jacobs.jacobs-university.de> <f4c1f95ede2f36f2c41adb5ed95d011f49ffd297.camel@nic.cz> <20181219124246.lvkiwofmq6wk4p5o@anna.jacobs.jacobs-university.de>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.3
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/nR65ZkcJbsW6XG9JCFFK1crekYw>
Subject: Re: [netmod] bit positions
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2018 12:46:24 -0000

On Wed, 2018-12-19 at 13:42 +0100, Juergen Schoenwaelder wrote:
> On Wed, Dec 19, 2018 at 01:35:02PM +0100, Ladislav Lhotka wrote:
> > On Wed, 2018-12-19 at 13:16 +0100, Juergen Schoenwaelder wrote:
> > > Lada,
> > > 
> > > RFC 7950 says:
> > > 
> > >    The "position" statement, which is optional, takes as an argument a
> > >    non-negative integer value that specifies the bit's position within a
> > >    hypothetical bit field.  The position value MUST be in the range 0 to
> > >    4294967295, and it MUST be unique within the bits type.
> > > 
> > > Neither the XML nor the JSON encoding rulse uses the position
> > > property.  I believe the interpretation of the position field is going
> > > to be protocol specific. DNS may do things in its own way, a CBOR
> > > encoding of bits may do a different thing.
> > 
> > So do you suggest to keep the position equal to the number in the IANA
> > registry?
> > 
> 
> That seems to be the most obvious thing to do.

OK. It will be certainly more palatable to DNS folks.

Thanks, Lada

> 
> /js
> 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67