[babel] Sub-TLVs, flags and Isolation in the IANA registry
David Schinazi <dschinazi@apple.com> Thu, 29 June 2017 01:44 UTC
Return-Path: <dschinazi@apple.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA229129AE9 for <babel@ietfa.amsl.com>; Wed, 28 Jun 2017 18:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
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 GiDhZx0_bASL for <babel@ietfa.amsl.com>; Wed, 28 Jun 2017 18:44:28 -0700 (PDT)
Received: from mail-in4.apple.com (mail-out4.apple.com [17.151.62.26]) (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 5CDA4127419 for <babel@ietf.org>; Wed, 28 Jun 2017 18:44:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1498700668; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=IaO+zh9/GIaBFvuRAMm+UXLiOYSRAleC73LHuZmEZYY=; b=o1A7MGcfJ00b2H14mp+tocQHaq+TBqveaCX6R4TYOyqO5JP8TpdDdHFKTASX0Bda uvDMTIr/Igae+hjXTO3ULB0bvA4eSGsjALnK9hPVBnohPV4b2kGc+wInh8sp9Aly IkLNTsv0AQGT3erPY4RG8+2e8hXIE+oQVPbduLgkr/b0WjIsIXXek5pm6SZfC4XQ 2KoN57hLSfEHf9VZnC4OE/mYO8sRcrahvGJZ1YzZl6J1iNwFcHz5lxF//qhjBTHB AuF/kgYF0KsKTFcAlCoRi+5ciF3x1YjI33110ATL3R6L55YN0SdTfPS9n6fO98Hu xJ6RErNHn1/7RrqD1nz0ZA==;
Received: from relay8.apple.com (relay8.apple.com [17.128.113.102]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail-in4.apple.com (Apple Secure Mail Relay) with SMTP id DF.93.06336.C7B54595; Wed, 28 Jun 2017 18:44:28 -0700 (PDT)
X-AuditID: 11973e12-c4dff700000018c0-e9-59545b7c31c0
Received: from jimbu (jimbu.apple.com [17.151.62.37]) by relay8.apple.com (Apple SCV relay) with SMTP id 19.E6.05704.B7B54595; Wed, 28 Jun 2017 18:44:28 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_fSv9zDWJRRUJq5Ij5rn6uQ)"
Received: from da0602a-dhcp207.apple.com (da0602a-dhcp207.apple.com [17.226.23.207]) by jimbu.apple.com (Oracle Communications Messaging Server 8.0.1.2.20170210 64bit (built Feb 10 2017)) with ESMTPSA id <0OSA005C9CU3A720@jimbu.apple.com> for babel@ietf.org; Wed, 28 Jun 2017 18:44:27 -0700 (PDT)
Sender: dschinazi@apple.com
From: David Schinazi <dschinazi@apple.com>
Message-id: <C3C79ED4-51F2-45F2-B8A3-BA1F3BBC7CA0@apple.com>
Date: Wed, 28 Jun 2017 18:44:27 -0700
To: Babel at IETF <babel@ietf.org>
X-Mailer: Apple Mail (2.3273)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUi2FCYplsTHRJpcOUtp8WWRd0sDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKmLp0AlPBfuGKn1ffMDcw/hfoYuTkkBAwkfiw4ARLFyMXh5DA GiaJ7l/n2GESd2c9ZoJILGOU+LD+ICNIgldAUOLH5HssIDazQJjEhiVbwOJCAhuYJI6drASx hQWkJbou3GXtYuTgYBPQkjiwxggibC1xv+c51BgbidZHp5hBbBYBVYkFLZfAbBEBJYnNN38y Q9wgK3FrNkicC8iewiYxe+p51gmM/LOQnDELyRkQtpbE90etQHEOIFte4uB5WYiwpsSze5/Y IWxtiSfvLrAuYGRbxSiUm5iZo5uZZ6KXWFCQk6qXnJ+7iREUrNPthHYwnlpldYhRgINRiYeX YW1wpBBrYllxZe4hRmkOFiVx3i9aIZFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGGUni9sX 6G+dNetwZ/riuSZp8Y/bbNcus51ttu64/6urdhmiPeyJa1bpfcietdZLR8zV60v//7OV7GIn eJOqTm3e9Ey1ba+XwvHre56yCR37Z35wxU2z6zsvRmR7f9l+bFViwkL/griFmy5Nv/IrJiam nF+FfYm2ZNF/xb6TN77f1j5lVTjvbawSS3FGoqEWc1FxIgBKVZOvNwIAAA==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjkeLIzCtJLcpLzFFi42IRnG6nqlsTHRJp8PoFq8WWRd0sDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKmLp0AlPBfuGKn1ffMDcw/hfoYuTkkBAwkbg76zFTFyMXh5DA MkaJD+sPMoIkeAUEJX5MvscCYjMLhElsWLIFLC4ksIFJ4tjJShBbWEBaouvCXdYuRg4ONgEt iQNrjCDC1hL3e55DjbGRaH10ihnEZhFQlVjQcgnMFhFQkth88yczxA2yErdmX2KewMgzC8nm WUg2Q9haEt8ftQLFOYBseYmD52UhwpoSz+59YoewtSWevLvAuoCRbRWjQFFqTmKlhV5iQUFO ql5yfu4mRlBwNRSm7WBsWm51iFGAg1GJh3fFquBIIdbEsuLK3EOMEhzMSiK8XOYhkUK8KYmV ValF+fFFpTmpxYcYJzICPTCRWUo0OR8Y+nkl8YYmJgYmxsZmxsbmJua0FFYS511xG+hIgfTE ktTs1NSC1CKYo5g4OKUaGK+/mB/xYx0XY/gK7rfr1+R1Ml/RNI5yS3xY9WT2l2h1sfith2c1 LHFYFH6l0SmlJryy5vKekjsfGP5+PDiRn2HhpJ/60/+wBMSnvhULs1TVEP5l4RpjOs2n58Ht Gw1smj/3Lb/rpbpN8+mOhN2+23RbHvZPfv83Z+pNzULJ9btyXpVJu9VbSSuxFGckGmoxFxUn AgCVNZrjoQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/XAiSgc3OcC1I0q3bmryz2kfYmGg>
Subject: [babel] Sub-TLVs, flags and Isolation in the IANA registry
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jun 2017 01:44:30 -0000
Hi everyone, Currently the Babel IANA registry contains one registry for sub-TLVs and one registry for flags. https://www.iana.org/assignments/babel/babel.xhtml <https://www.iana.org/assignments/babel/babel.xhtml> The RFC6126 flags are meant for the Update TLV. The current work-in-progress version of the draft introduces Hello Flags and got me thinking: 1) Should we have two separate registries: - Hello Flags (16 bits) - Update Flags (8 bits) 2) Should we have one sub-TLV registry per TLV? The majority of currently defined sub-TLVs only make sense for one TLV, so I wonder if sharing the space will cause us to run out of sub-TLVs prematurely. Thoughts? Thanks, David Schinazi
- [babel] Sub-TLVs, flags and Isolation in the IANA… David Schinazi
- Re: [babel] Sub-TLVs, flags and Isolation in the … Juliusz Chroboczek