Re: [dtn-security] Re: [dtn-dev] Re: SDNV-new

Michael Demmer <demmer@cs.berkeley.edu> Tue, 31 May 2005 21:55 UTC

Received: from pisco (pisco.CS.Berkeley.EDU [128.32.37.175]) by webbie.berkeley.intel-research.net (8.11.6/8.11.6) with ESMTP id j4VLtpV31535; Tue, 31 May 2005 14:55:51 -0700
Received: from demmer by pisco with local (Exim 4.50) id 1DdEiF-0000V4-3R; Tue, 31 May 2005 14:55:51 -0700
Date: Tue, 31 May 2005 14:55:51 -0700
From: Michael Demmer <demmer@cs.berkeley.edu>
To: Scott Burleigh <Scott.Burleigh@jpl.nasa.gov>
Cc: dtn-security@mailman.dtnrg.org, dtn-dev@mailman.dtnrg.org
Subject: Re: [dtn-security] Re: [dtn-dev] Re: SDNV-new
Message-ID: <20050531215551.GB30682@pisco.cs.berkeley.edu>
References: <200505241854.j4OIsx724035@smtp-bedford-dr.mitre.org> <42944BEF.7090007@cs.tcd.ie> <20050525152006.GA7633@pisco.cs.berkeley.edu> <42949E83.9050000@cs.tcd.ie> <20050525163707.GB14911@pisco.cs.berkeley.edu> <4294ABB9.5010009@jpl.nasa.gov> <4295D547.9080808@cs.tcd.ie> <20050531172941.GA30682@pisco.cs.berkeley.edu> <429CA577.8000705@jpl.nasa.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <429CA577.8000705@jpl.nasa.gov>
User-Agent: Mutt/1.4.2i
Sender: dtn-security-admin@mailman.dtnrg.org
Errors-To: dtn-security-admin@mailman.dtnrg.org
X-BeenThere: dtn-security@mailman.dtnrg.org
X-Mailman-Version: 2.0.13
Precedence: bulk
Reply-To: dtn-security@mailman.dtnrg.org
List-Unsubscribe: <http://mailman.dtnrg.org/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@mailman.dtnrg.org?subject=unsubscribe>
List-Id: DTN Security Discussion <dtn-security.mailman.dtnrg.org>
List-Post: <mailto:dtn-security@mailman.dtnrg.org>
List-Help: <mailto:dtn-security-request@mailman.dtnrg.org?subject=help>
List-Subscribe: <http://mailman.dtnrg.org/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@mailman.dtnrg.org?subject=subscribe>
List-Archive: <http://mailman.dtnrg.org/pipermail/dtn-security/>

As Rajesh said, the main rational for the byte savings is for small
values. Therefore, for things we expect to be big, like crypto keys,
we can send the length of the key first as an SDNV, then the
value. This won't waste too much over just sending the key as an SDNV
by itself (at most it wastes a byte or two).

As such, my instinct is to just go with 1-2-3-4-5-6-7-8. 

-m