Re: Canonical configuration database order

["Randy Presuhn" <randy_presuhn@mindspring.com>]

Hi -

> From: "Andy Bierman" <ietf@andybierman.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: "Netconf (E-mail)" <netconf@ops.ietf.org>
> Sent: Friday, June 02, 2006 9:33 AM
> Subject: Re: Canonical configuration database order
>
> Randy Presuhn wrote:
> > Hi -
> > 
> >> From: "Andy Bierman" <ietf@andybierman.com>
> >> To: "Netconf (E-mail)" <netconf@ops.ietf.org>
> >> Sent: Friday, June 02, 2006 8:30 AM
> >> Subject: Canonical configuration database order
> > ...
> >> The canonical order for named sibling instances is the natural sort order,
> >> based on the key associated with the nodes.  For multiple unnamed
> > ...
> > 
> > What is meant by "the natural sort order"?
> 
> Ascending order for each component of the key.
> Keys are evaluated 'top to bottom', where the
> topmost component represents the major index,
> and each successive key component represents
> successive minor index components.
...

Yes, but what is meant by "ascending order"?
I'm wondering whether, for example, strings are
canonicalized before comparison (e.g. is "A" plus
"Umlaut" the same thing as "A-Umlaut"), whether
locales matter (e.g. does "tra" come before or
after "tuy"), and what happens with numbers
(e.g. does 9.9 come before or after 999)?

Randy


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>