Subject: [netmod] Change control rules minutes - provisional (!!!!)

From: Balazs Lengyel <[email-masked]>
Date: Wed, 08 Oct 2008 23:26:43 +0200

2008-10-08

Datatypes, normalization, lexical/value representation
------------------------------------------------------
For all data types have a normailzed lexical form
Data is compared in value format
edit-config + get-config: might bring back a different lexical form
netconf server must send back data in the normalized form

description of the lexical space of each type will be in plain english
it will be in description clause or a separate normalization clause

check which datatypes need the normalization explained both for
base yang draft and the datatypes draft

Update rules
------------------------------------------------------

Protect old clients,
Protect old importing modules

Allowed:
  new typedefs
  new groupings
  expand value range
  remove must
  add new optional stuff
  allow new rpc
  allow new notifications
  allow new data in existing notifications
  allow new optional parameters to rpc input(?)
  allow new parameters to rpc output(?)
  remove mandatory
  reference (update)
  description (semantic equivalence)
  status (in one direction)
  length
  add default(?)
  add new bits
  add new enum values at the end of the list
  config false ->true
  -

Not allowed:
  delete nodes
  leaf order changes (due to strict encoding order)
  change basic type uint8 -> int8
  change length restriction of string
  make a type into union
  no new mandatory nodes
  change datatype of a leaf (underlying datatype at the base of the type hierarchy)
  add new membertypes to a union
  change units
  change default
  add iffeature
  change the value of enum
  add enums in the middle
  -

Ericsson Question
==================
Why do we allow extension of value range?

Why is the exact versioning good? Doesn't it result in too many version

_______________________________________________
netmod mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/netmod