Re: [NGO] NETCONF Data types
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Mon, 07 January 2008 14:25 UTC
Return-path: <ngo-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JBsuy-0006it-PN; Mon, 07 Jan 2008 09:25:32 -0500
Received: from ngo by megatron.ietf.org with local (Exim 4.43) id 1JBsux-0006ih-OD for ngo-confirm+ok@megatron.ietf.org; Mon, 07 Jan 2008 09:25:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JBsux-0006iZ-Eb for ngo@ietf.org; Mon, 07 Jan 2008 09:25:31 -0500
Received: from hermes.jacobs-university.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JBsux-0006vd-1F for ngo@ietf.org; Mon, 07 Jan 2008 09:25:31 -0500
Received: from localhost (demetrius.jacobs-university.de [212.201.44.32]) by hermes.jacobs-university.de (Postfix) with ESMTP id 8B8A28A250; Mon, 7 Jan 2008 15:25:30 +0100 (CET)
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 00539-01; Mon, 7 Jan 2008 15:25:26 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 1BF5B8A22E; Mon, 7 Jan 2008 15:25:26 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id B5F5245C0DA; Mon, 7 Jan 2008 15:25:24 +0100 (CET)
Date: Mon, 07 Jan 2008 15:25:24 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Sharon Chisholm <schishol@nortel.com>
Subject: Re: [NGO] NETCONF Data types
Message-ID: <20080107142524.GC8185@elstar.local>
References: <037801c83770$93f5bf40$ca168182@china.huawei.com> <4915F014FDD99049A9C3A8C1B832004F0252120D@IMCSRV2.MITRE.ORG> <713043CE8B8E1348AF3C546DBE02C1B41276324B@zcarhxm2.corp.nortel.com> <20080107140437.GA8185@elstar.local> <713043CE8B8E1348AF3C546DBE02C1B4127632BB@zcarhxm2.corp.nortel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <713043CE8B8E1348AF3C546DBE02C1B4127632BB@zcarhxm2.corp.nortel.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: ngo@ietf.org
X-BeenThere: ngo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@jacobs-university.de
List-Id: NETCONF Goes On - discussions on future work and extensions to NETCONF <ngo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ngo>
List-Post: <mailto:ngo@ietf.org>
List-Help: <mailto:ngo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=subscribe>
Errors-To: ngo-bounces@ietf.org
On Mon, Jan 07, 2008 at 09:07:05AM -0500, Sharon Chisholm wrote: > If it is define with length=64, then you know you can't read it and > ignore it. If it is defined with length=32, the you know you can > read it and do. I think this "works sometimes" approach is not really a solution. That said, every decent parser which turns ASCII number strings into binary data should be able to detect overflows (C standard functions strtol() and friends do this) even without an explicit "length" indication - so you can have this "works sometimes" approach already today. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ NGO mailing list NGO@ietf.org https://www1.ietf.org/mailman/listinfo/ngo
- [NGO] NETCONF Data types Sharon Chisholm
- Re: [NGO] NETCONF Data types Juergen Schoenwaelder
- Re: [NGO] NETCONF Data types Andy Bierman
- RE: [NGO] NETCONF Data types Sharon Chisholm
- Re: [NGO] NETCONF Data types Andy Bierman
- Re: [NGO] NETCONF Data types Juergen Schoenwaelder
- Re: [NGO] NETCONF Data types Martin Bjorklund
- Re: [NGO] NETCONF Data types Balazs Lengyel
- RE: [NGO] NETCONF Data types Sharon Chisholm
- Re: [NGO] NETCONF Data types Andy Bierman
- RE: [NGO] NETCONF Data types Sharon Chisholm
- Re: [NGO] NETCONF Data types Ladislav Lhotka
- Re: [NGO] NETCONF Data types Martin Bjorklund
- Re: [NGO] NETCONF Data types Andy Bierman
- RE: [NGO] NETCONF Data types David Harrington
- Re: [NGO] NETCONF Data types Ladislav Lhotka
- RE: [NGO] NETCONF Data types Mehmet Ersue
- Re: [NGO] NETCONF Data types Juergen Schoenwaelder
- Re: [NGO] NETCONF Data types tom.petch
- Re: [NGO] NETCONF Data types Juergen Schoenwaelder
- Re: [NGO] NETCONF Data types Andy Bierman
- Re: [NGO] NETCONF Data types Andy Bierman
- RE: [NGO] NETCONF Data types Natale, Bob
- RE: [NGO] NETCONF Data types Sharon Chisholm
- Re: [NGO] NETCONF Data types Juergen Schoenwaelder
- RE: [NGO] NETCONF Data types Sharon Chisholm
- RE: [NGO] NETCONF Data types Ladislav Lhotka
- Re: [NGO] NETCONF Data types Juergen Schoenwaelder
- Re: [NGO] NETCONF Data types Phil Shafer
- RE: [NGO] NETCONF Data types Sharon Chisholm
- Re: [NGO] NETCONF Data types Phil Shafer
- RE: [NGO] NETCONF Data types Sharon Chisholm
- Re: [NGO] NETCONF Data types Juergen Schoenwaelder