Re: [NGO] NETCONF Data types

Phil Shafer <phil@juniper.net> Mon, 07 January 2008 18:12 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 1JBwSm-0001So-8Z; Mon, 07 Jan 2008 13:12:40 -0500
Received: from ngo by megatron.ietf.org with local (Exim 4.43) id 1JBwSl-0001Sj-DT for ngo-confirm+ok@megatron.ietf.org; Mon, 07 Jan 2008 13:12:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JBwSl-0001Sb-3X for ngo@ietf.org; Mon, 07 Jan 2008 13:12:39 -0500
Received: from exprod7og104.obsmtp.com ([64.18.2.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JBwSk-0004az-Nl for ngo@ietf.org; Mon, 07 Jan 2008 13:12:39 -0500
Received: from source ([66.129.224.36]) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP; Mon, 07 Jan 2008 10:11:22 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 7 Jan 2008 10:11:33 -0800
Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m07IBW932916; Mon, 7 Jan 2008 10:11:32 -0800 (PST) (envelope-from phil@idle.juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.13.8/8.13.8) with ESMTP id m07I7cg6086168; Mon, 7 Jan 2008 18:07:42 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200801071807.m07I7cg6086168@idle.juniper.net>
To: Sharon Chisholm <schishol@nortel.com>
Subject: Re: [NGO] NETCONF Data types
In-reply-to: <713043CE8B8E1348AF3C546DBE02C1B4127DEF68@zcarhxm2.corp.nortel.com>
Date: Mon, 07 Jan 2008 13:07:38 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 07 Jan 2008 18:11:33.0598 (UTC) FILETIME=[BC2B37E0:01C85158]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: ngo@ietf.org
X-BeenThere: ngo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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

"Sharon Chisholm" writes:
>This was intended as a design time definition.

Then I'm lost.  You said earlier:

>> In that case, a better approach is likely a complex type
>> which gives length and value. This way if you handle all lengths, you
>> just need to look at the value field.

Where is the complex type?  Sounded like you meant to encode both
the length and the value in the transmitted data.  What's the value
of carrying to length if the module definition tells you the max length?
Or am I misreading you completely?

Thanks,
 Phil


_______________________________________________
NGO mailing list
NGO@ietf.org
https://www1.ietf.org/mailman/listinfo/ngo