Re: [Netconf] Review of draft-ietf-netconf-monitoring-02.txt

["Natale, Bob" <RNATALE at mitre.org>]

Hi Balazs,

Martin has the purpose of draft-ietf-opsawg-smi-datatypes-in-xsd
exactly right -- I really don't see any prospect of a change in the
purpose of that document (now at -02 and I'm hoping very close to being
ready for WGLC).

Likewise, draft-ietf-opsawg-smi-textual-conventions-in-xsd will likely
be of the same nature -- as faithful as possible of a direct
representations of the major TCs we have defined for SNMP, using the
same set of requirements (suitably adjusted where necessary) defined
for the base SMI datatypes.

Finally, draft-ietf-opsawg-smi-structure-in-xsd might allow for more
creativity in terms of representing MIB structure in XSD, although I
believe our plan (led by Dave Harrington) is avoid unnecessary
incompatibilities with libsmi.

(I've used tentative titles on the last two documents wrt OPSAWG
sponsorship, anticipating that the pattern there will follow from the
base datatypes document.)

Cheers,
BobN

-----Original Message-----
From: netconf-bounces at ietf.org [mailto:netconf-bounces at ietf.org] On
Behalf Of Balazs Lengyel
Sent: Tuesday, July 22, 2008 4:55 PM
To: Martin Bjorklund
Cc: netconf at ietf.org
Subject: Re: [Netconf] Review of draft-ietf-netconf-monitoring-02.txt

Should we ask Bob to change his aim? Both Netconf monitoring and DSDL
will need the XSD types.
Balazs

Martin Bjorklund wrote:
> Balazs Lengyel <balazs.lengyel at ericsson.com> wrote:
>>
>> Sharon Chisholm wrote:
>>> 5.2 int:host schema
>>> This should be a separate draft as many other will need it. Is
>>> there today no XML schema for such basic stuff? Can we refer to
>>> draft-ietf-opsawg-smi-datatypes-in-xsd? What is the state of that?
>>> Anyone who cares about XSD should start pushing that draft!
>> <sharon>
>>> We looked at that and either it didn't meet our needs or there was
>>> a namespace issue, either way, we couldn't use it. In general, if
we
>>> can get better data types by not deriving them from legacy
>>> definitions then we should not be afraid to do that. I agree though
>>> that this should be a separate document..
>>> </sharon>
>> {BALAZS}: draft-ietf-opsawg-smi-datatypes-in-xsd is not yet ready so
>> it can not be legacy. Also Bob Natale indicated to me that he
>> intends to go on working on it, so join forces. 
> 
> If I understand the intention of
> draft-ietf-opsawg-smi-datatypes-in-xsd correctly, it is supposed to
> provide a direct XSD version of SMI data types.  No nice-to-have
types
> will be defined by this spec.
> 
> For this particular type (inet:host), the best SMIv2 type we can use
> is InetAddress from rfc 4001, but we can do better in XML (see e.g.
> inet-types.yang :).
> 
> 
> /martin

-- 
Balazs Lengyel                       Ericsson Hungary Ltd.
TSP System Manager
ECN: 831 7320                        Fax: +36 1 4377792
Tel: +36-1-437-7320     email: Balazs.Lengyel at ericsson.com
_______________________________________________
Netconf mailing list
Netconf at ietf.org
https://www.ietf.org/mailman/listinfo/netconf
_______________________________________________
Netconf mailing list
Netconf at ietf.org
https://www.ietf.org/mailman/listinfo/netconf