From opsawg-bounces@ietf.org Thu Nov 01 15:36:26 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Infpo-0003dC-Vx; Thu, 01 Nov 2007 15:36:08 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Infpo-0003d7-5w
	for opsawg-confirm+ok@megatron.ietf.org; Thu, 01 Nov 2007 15:36:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Infpn-0003cz-SQ
	for opsawg@ietf.org; Thu, 01 Nov 2007 15:36:07 -0400
Received: from exprod7og104.obsmtp.com ([64.18.2.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Infpg-0007Nw-Ft
	for opsawg@ietf.org; Thu, 01 Nov 2007 15:36:07 -0400
Received: from source ([66.129.224.36]) by exprod7ob104.postini.com
	([64.18.6.12]) with SMTP; Thu, 01 Nov 2007 12:34:51 PDT
Received: from proton.jnpr.net ([10.10.2.37]) by gamma.jnpr.net with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 1 Nov 2007 12:35:32 -0700
Received: from [172.23.1.146] ([172.23.1.146] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Nov 2007 15:35:30 -0400
Message-ID: <472A2A7E.7090401@juniper.net>
Date: Thu, 01 Nov 2007 15:35:26 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
Subject: Re: [OPSAWG] XSDMI
References: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com>
In-Reply-To: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Nov 2007 19:35:30.0541 (UTC)
	FILETIME=[5CBE79D0:01C81CBE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Hi David,

The following is a possible compromise:

David progresses the XSDMI work in the OPS Area WG. Although the XSD
produced by XSDMI is made available to everyone, there is no mandate to
use it. This means that it the NETCONF community decides that XSDMI does
not fulfill their requirements, they will be free to specify something else.

All drafts progressed as XSDMI will be submitted for publication as
INFORMATIONAL.

Comments?

                              Ron


David Harrington wrote:
> Hi,
> 
> Juergen has raised the issue that the XSD produced by the XDMI effort
> and the XSD produced by the YANG effort might be different, and having
> two different XSD equivalents for MIB datatypes would be suboptimal. I
> agree.
> 
> However, I have the concern that while vendors wait for YANG to be
> completed, they will need to develop proprietary data models for use
> with netconf. Some vendors will want to reuse datatypes found in the
> 15 year compilation of IETF NM experience found in the standard MIB
> modules, and supported by existing implementation code. If they need
> to develop their own translations of existing SMI datatypes and
> textual conventions into XSD and XML, we could wind up with a variety
> of competing XSD specifications. 
> 
> The XSDMI work would provide reusable XSD equivalents of SMI datatypes
> and textual conventions. If vendors use these consistent XSD
> translations, then later work to derive standards from the proprietary
> information/data models would be easier because there would be
> increased commonality in the datatypes and textual conventions and
> semantics used to model the information.
> 
> In addition to proprietary data models, there are multiple IETF
> efforts to translate existing information models (often from
> ASN.1-based formats) into XML formats.
> draft-frascone-xml-dictionary-00 describes the Diameter "dictionary"
> in XML format; draft-legg-xed-roadmap-06.txt describes translating
> LDAP and X.509 directory information models into semantically
> equivalent XML renditions of existing directory protocols; IPPM is
> working on an information model in XML for traceroute measurements. So
> a MIB-related translation to XML is not unique.
> 
> The XSDMI effort is about taking the MIB, which operators have
> complained is not well suited to configuration, and translating
> aspects of the MIB into equivalent XSD. The fact that the MIB
> datatypes can be translated into XSD will not make the MIB more
> suitable for configuration; it will simply make reusable dataypes
> available in an XML-compatible format.
> 
> The netconf community should be focused on defining a data modeling
> language and data models for configuration. The YANG approach for
> netconf focuses not only on configuration, but also on developing an
> information modeling language which can then be used by tools to
> generate syntax-specific data models for a variety of purposes, such
> as Netconf-suitable XSD data models, SNMP-suitable MIB modules, plus
> data models for other modeling systems. I have a concern that the SNMP
> community has not been asking for this approach, and the IETF failed
> to reach consensus on the need for the information-modeling approach
> when it was presented to the SMING WG. If the
> information-model-generates-data-models approach is adopted by the
> IETF, then does that mean that efforts to use XML-based data models
> for ipfix, Diameter, IPPM, and LDAP should not be permitted until YANG
> can determine how to generate those data models as well?
> 
> Just to be clear, I support the YANG effort because I believe it could
> lead to better consistency of data modeling across protocols, but it
> has yet to be proven to be viable, and other efforts to converge or
> harmonize data models have had mixed success at best. We should not
> put all our eggs into one basket. If the YANG approach proves to be
> viable, then the XSDMI translations can be modified as needed to work
> with YANG in the future. But XSDMI could give us XSD datatypes to
> develop data models, possibly years before consensus on YANG will be
> achieved.
> 
> I believe the XSDMI effort should be an OPS-area effort (indeed an
> IETF-wide effort), focused in the OPSAWG, to allow the representation
> and translation into XML idiom of the existing datatypes, textual
> conventions, and semantic models defined in 15 years of work by
> multiple working groups and multiple areas of the IETF. 
> 
> David Harrington
> dbharrington@comcast.net
> ietfdbh@comcast.net
> 
> 
> 
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www1.ietf.org/mailman/listinfo/opsawg
> 


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Thu Nov 01 19:23:11 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1InjNH-0003Mr-Ht; Thu, 01 Nov 2007 19:22:55 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1InjNG-0003Lm-Rq
	for opsawg-confirm+ok@megatron.ietf.org; Thu, 01 Nov 2007 19:22:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1InjNG-0003JH-HL
	for opsawg@ietf.org; Thu, 01 Nov 2007 19:22:54 -0400
Received: from mail.globalsuite.net ([69.46.103.200])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1InjN6-00075d-4a
	for opsawg@ietf.org; Thu, 01 Nov 2007 19:22:49 -0400
X-AuditID: c0a8013c-ae7bcbb000007c30-6d-472a5fb39de9
Received: from Harrington73653 (streamline120.sjccnet.com [207.87.51.120])
	by mail.globalsuite.net (Symantec Mail Security) with ESMTP id
	D0F1C4DC002; Thu,  1 Nov 2007 17:22:26 -0600 (MDT)
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Ron Bonica'" <rbonica@juniper.net>
References: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com>
	<472A2A7E.7090401@juniper.net>
Subject: RE: [OPSAWG] XSDMI
Date: Thu, 1 Nov 2007 16:22:08 -0700
Message-ID: <05a401c81cde$06d6d880$3f8011ac@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
In-Reply-To: <472A2A7E.7090401@juniper.net>
Thread-Index: Acgcvm5N8DhrR/W7SqKKWhnP0qFHVQAGVFGw
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Hi,

The goal of XSDMI is to provide a standard translation of SMI
datatypes, textual conventions, and macros into XML family formats,
such as XSD.

I have said this over and over: There has never been any intention on
my part to mandate that any XML-based protocol, including Netconf,
MUST use the XSD output from the XSDMI translations. These
translatinos are being provided to **enable and encourage** reuse of
SMIv2 datatypes and textual conventions in XML-based protocols, and to
provide XML-based support for SMIv2 macros to encourage reuse of the
MIB data models (schemas) in XML-capable management applications and
databases.

It is purely a Netconf decision whether to reuse these datatype
translations, just as it would be purely a "foo" protocol decision
whether the datatypes were appropriate for reuse in the "foo"
environment. The XSDMI work is totally independent of the work being
done by and for the Netconf community.

Perasnally, I expect that the data modeling needed for configuration
will require things that SMIv2 does not have - the ability to
distinguish config data from state data, the ability to specify data
from the candidate datastore vs that from the running or startup
datastores, nested data structures, standardized methods, etc. SMIv2
MIBs and the XSD equivalents cannot do this! 

I think it unlikely that the XSD output from a Netconf-specific
effort, such as YANG, will match the XSD output from the XSDMI effort,
because if it did then it could be argued that there is no need to
move to a new data modeling language, only the need to translate SMIv2
into XML-based formats. XML and XSD do not enable better
configuration; a configuration-focused protocol and
configuration-focused data models will do that. I consider it
appropriate that the data models from the SMIv2 MIB and the data
models designed for Netcof configuration not match because they are
designed to serve different purposes. 

The data models that already exist for SNMP and syslog and RADIUS and
Diameter and IPFIX do not match, because they serve different purposes
and contain different modeling information, even though they are all
related to network management. The data model encodings used for MIBs
and LDAP search filters and X.509 certificates differ because they
serve different purposes, even though they all use ASN.1 encoding. The
netconf data models and their encodings SHOULD differ from the
SNMP/MIB data models because the information that we need to model and
to encode on the wire for these different purposes and different
protocols is different.

I do not feel that publishing the XSDMI translations as Informational
is called for. This work is **independent** of Netconf.

The goal of XSDMI is to provide a **standard** translation of SMI
datatypes, textual conventions, and macros into XML family formats,
such as XSD, so other protocols can **choose** to use compatible
datatypes, and have a standard interoperable translation already
available so they don't have to do the translation themselves, and so
the standard translations can be done by people who really understand
the purpose and constraints of the SMIv2 datatypes and textual
conventions and macros.

It has **never** been my intention that people should be **forced** to
use these translated datatypes, textual conventions, and macros with
other protocols, only that we would make it easier for them to do so
if they wanted to, and to promote interoperability by giving them
standard translations they could use.

David Harrington
dbharrington@comcast.net
ietfdbh@comcast.net


> -----Original Message-----
> From: Ron Bonica [mailto:rbonica@juniper.net] 
> Sent: Thursday, November 01, 2007 12:35 PM
> To: David Harrington
> Cc: opsawg@ietf.org
> Subject: Re: [OPSAWG] XSDMI
> 
> Hi David,
> 
> The following is a possible compromise:
> 
> David progresses the XSDMI work in the OPS Area WG. Although the XSD
> produced by XSDMI is made available to everyone, there is no 
> mandate to
> use it. This means that it the NETCONF community decides that 
> XSDMI does
> not fulfill their requirements, they will be free to specify 
> something else.
> 
> All drafts progressed as XSDMI will be submitted for publication as
> INFORMATIONAL.
> 
> Comments?
> 
>                               Ron
> 
> 
> David Harrington wrote:
> > Hi,
> > 
> > Juergen has raised the issue that the XSD produced by the 
> XDMI effort
> > and the XSD produced by the YANG effort might be different, 
> and having
> > two different XSD equivalents for MIB datatypes would be 
> suboptimal. I
> > agree.
> > 
> > However, I have the concern that while vendors wait for YANG to be
> > completed, they will need to develop proprietary data models for
use
> > with netconf. Some vendors will want to reuse datatypes found in
the
> > 15 year compilation of IETF NM experience found in the standard
MIB
> > modules, and supported by existing implementation code. If they
need
> > to develop their own translations of existing SMI datatypes and
> > textual conventions into XSD and XML, we could wind up with 
> a variety
> > of competing XSD specifications. 
> > 
> > The XSDMI work would provide reusable XSD equivalents of 
> SMI datatypes
> > and textual conventions. If vendors use these consistent XSD
> > translations, then later work to derive standards from the 
> proprietary
> > information/data models would be easier because there would be
> > increased commonality in the datatypes and textual conventions and
> > semantics used to model the information.
> > 
> > In addition to proprietary data models, there are multiple IETF
> > efforts to translate existing information models (often from
> > ASN.1-based formats) into XML formats.
> > draft-frascone-xml-dictionary-00 describes the Diameter
"dictionary"
> > in XML format; draft-legg-xed-roadmap-06.txt describes translating
> > LDAP and X.509 directory information models into semantically
> > equivalent XML renditions of existing directory protocols; IPPM is
> > working on an information model in XML for traceroute 
> measurements. So
> > a MIB-related translation to XML is not unique.
> > 
> > The XSDMI effort is about taking the MIB, which operators have
> > complained is not well suited to configuration, and translating
> > aspects of the MIB into equivalent XSD. The fact that the MIB
> > datatypes can be translated into XSD will not make the MIB more
> > suitable for configuration; it will simply make reusable dataypes
> > available in an XML-compatible format.
> > 
> > The netconf community should be focused on defining a data
modeling
> > language and data models for configuration. The YANG approach for
> > netconf focuses not only on configuration, but also on developing
an
> > information modeling language which can then be used by tools to
> > generate syntax-specific data models for a variety of purposes,
such
> > as Netconf-suitable XSD data models, SNMP-suitable MIB modules,
plus
> > data models for other modeling systems. I have a concern 
> that the SNMP
> > community has not been asking for this approach, and the IETF
failed
> > to reach consensus on the need for the information-modeling
approach
> > when it was presented to the SMING WG. If the
> > information-model-generates-data-models approach is adopted by the
> > IETF, then does that mean that efforts to use XML-based data
models
> > for ipfix, Diameter, IPPM, and LDAP should not be permitted 
> until YANG
> > can determine how to generate those data models as well?
> > 
> > Just to be clear, I support the YANG effort because I 
> believe it could
> > lead to better consistency of data modeling across protocols, but
it
> > has yet to be proven to be viable, and other efforts to converge
or
> > harmonize data models have had mixed success at best. We should
not
> > put all our eggs into one basket. If the YANG approach proves to
be
> > viable, then the XSDMI translations can be modified as 
> needed to work
> > with YANG in the future. But XSDMI could give us XSD datatypes to
> > develop data models, possibly years before consensus on YANG will
be
> > achieved.
> > 
> > I believe the XSDMI effort should be an OPS-area effort (indeed an
> > IETF-wide effort), focused in the OPSAWG, to allow the 
> representation
> > and translation into XML idiom of the existing datatypes, textual
> > conventions, and semantic models defined in 15 years of work by
> > multiple working groups and multiple areas of the IETF. 
> > 
> > David Harrington
> > dbharrington@comcast.net
> > ietfdbh@comcast.net
> > 
> > 
> > 
> > 
> > _______________________________________________
> > OPSAWG mailing list
> > OPSAWG@ietf.org
> > https://www1.ietf.org/mailman/listinfo/opsawg
> > 
> 




_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Thu Nov 01 21:42:36 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1InlXp-0001kK-9P; Thu, 01 Nov 2007 21:41:57 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1InlXo-0001ja-HD
	for opsawg-confirm+ok@megatron.ietf.org; Thu, 01 Nov 2007 21:41:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1InlXo-0001hE-5s
	for opsawg@ietf.org; Thu, 01 Nov 2007 21:41:56 -0400
Received: from exprod7og103.obsmtp.com ([64.18.2.159])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1InlXc-0002jc-Pn
	for opsawg@ietf.org; Thu, 01 Nov 2007 21:41:51 -0400
Received: from source ([66.129.224.36]) by exprod7ob103.postini.com
	([64.18.6.12]) with SMTP; Thu, 01 Nov 2007 18:40:58 PDT
Received: from proton.jnpr.net ([10.10.2.37]) by gamma.jnpr.net with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 1 Nov 2007 18:41:20 -0700
Received: from [172.23.1.146] ([172.23.1.146] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Nov 2007 21:41:18 -0400
Message-ID: <472A8039.2030903@juniper.net>
Date: Thu, 01 Nov 2007 21:41:13 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
Subject: Re: [OPSAWG] XSDMI
References: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com>
	<472A2A7E.7090401@juniper.net>
	<05a401c81cde$06d6d880$3f8011ac@china.huawei.com>
In-Reply-To: <05a401c81cde$06d6d880$3f8011ac@china.huawei.com>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Nov 2007 01:41:18.0759 (UTC)
	FILETIME=[76E6C370:01C81CF1]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7f3fa64b9851a63d7f3174ef64114da7
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

David,

Are there any aspects of the proposal that you would like to change? Or
are we in violent agreement?

                                Ron


David Harrington wrote:
> Hi,
> 
> The goal of XSDMI is to provide a standard translation of SMI
> datatypes, textual conventions, and macros into XML family formats,
> such as XSD.
> 
> I have said this over and over: There has never been any intention on
> my part to mandate that any XML-based protocol, including Netconf,
> MUST use the XSD output from the XSDMI translations. These
> translatinos are being provided to **enable and encourage** reuse of
> SMIv2 datatypes and textual conventions in XML-based protocols, and to
> provide XML-based support for SMIv2 macros to encourage reuse of the
> MIB data models (schemas) in XML-capable management applications and
> databases.
> 
> It is purely a Netconf decision whether to reuse these datatype
> translations, just as it would be purely a "foo" protocol decision
> whether the datatypes were appropriate for reuse in the "foo"
> environment. The XSDMI work is totally independent of the work being
> done by and for the Netconf community.
> 
> Perasnally, I expect that the data modeling needed for configuration
> will require things that SMIv2 does not have - the ability to
> distinguish config data from state data, the ability to specify data
> from the candidate datastore vs that from the running or startup
> datastores, nested data structures, standardized methods, etc. SMIv2
> MIBs and the XSD equivalents cannot do this! 
> 
> I think it unlikely that the XSD output from a Netconf-specific
> effort, such as YANG, will match the XSD output from the XSDMI effort,
> because if it did then it could be argued that there is no need to
> move to a new data modeling language, only the need to translate SMIv2
> into XML-based formats. XML and XSD do not enable better
> configuration; a configuration-focused protocol and
> configuration-focused data models will do that. I consider it
> appropriate that the data models from the SMIv2 MIB and the data
> models designed for Netcof configuration not match because they are
> designed to serve different purposes. 
> 
> The data models that already exist for SNMP and syslog and RADIUS and
> Diameter and IPFIX do not match, because they serve different purposes
> and contain different modeling information, even though they are all
> related to network management. The data model encodings used for MIBs
> and LDAP search filters and X.509 certificates differ because they
> serve different purposes, even though they all use ASN.1 encoding. The
> netconf data models and their encodings SHOULD differ from the
> SNMP/MIB data models because the information that we need to model and
> to encode on the wire for these different purposes and different
> protocols is different.
> 
> I do not feel that publishing the XSDMI translations as Informational
> is called for. This work is **independent** of Netconf.
> 
> The goal of XSDMI is to provide a **standard** translation of SMI
> datatypes, textual conventions, and macros into XML family formats,
> such as XSD, so other protocols can **choose** to use compatible
> datatypes, and have a standard interoperable translation already
> available so they don't have to do the translation themselves, and so
> the standard translations can be done by people who really understand
> the purpose and constraints of the SMIv2 datatypes and textual
> conventions and macros.
> 
> It has **never** been my intention that people should be **forced** to
> use these translated datatypes, textual conventions, and macros with
> other protocols, only that we would make it easier for them to do so
> if they wanted to, and to promote interoperability by giving them
> standard translations they could use.
> 
> David Harrington
> dbharrington@comcast.net
> ietfdbh@comcast.net
> 
> 
> 
>>-----Original Message-----
>>From: Ron Bonica [mailto:rbonica@juniper.net] 
>>Sent: Thursday, November 01, 2007 12:35 PM
>>To: David Harrington
>>Cc: opsawg@ietf.org
>>Subject: Re: [OPSAWG] XSDMI
>>
>>Hi David,
>>
>>The following is a possible compromise:
>>
>>David progresses the XSDMI work in the OPS Area WG. Although the XSD
>>produced by XSDMI is made available to everyone, there is no 
>>mandate to
>>use it. This means that it the NETCONF community decides that 
>>XSDMI does
>>not fulfill their requirements, they will be free to specify 
>>something else.
>>
>>All drafts progressed as XSDMI will be submitted for publication as
>>INFORMATIONAL.
>>
>>Comments?
>>
>>                              Ron
>>
>>
>>David Harrington wrote:
>>
>>>Hi,
>>>
>>>Juergen has raised the issue that the XSD produced by the 
>>
>>XDMI effort
>>
>>>and the XSD produced by the YANG effort might be different, 
>>
>>and having
>>
>>>two different XSD equivalents for MIB datatypes would be 
>>
>>suboptimal. I
>>
>>>agree.
>>>
>>>However, I have the concern that while vendors wait for YANG to be
>>>completed, they will need to develop proprietary data models for
> 
> use
> 
>>>with netconf. Some vendors will want to reuse datatypes found in
> 
> the
> 
>>>15 year compilation of IETF NM experience found in the standard
> 
> MIB
> 
>>>modules, and supported by existing implementation code. If they
> 
> need
> 
>>>to develop their own translations of existing SMI datatypes and
>>>textual conventions into XSD and XML, we could wind up with 
>>
>>a variety
>>
>>>of competing XSD specifications. 
>>>
>>>The XSDMI work would provide reusable XSD equivalents of 
>>
>>SMI datatypes
>>
>>>and textual conventions. If vendors use these consistent XSD
>>>translations, then later work to derive standards from the 
>>
>>proprietary
>>
>>>information/data models would be easier because there would be
>>>increased commonality in the datatypes and textual conventions and
>>>semantics used to model the information.
>>>
>>>In addition to proprietary data models, there are multiple IETF
>>>efforts to translate existing information models (often from
>>>ASN.1-based formats) into XML formats.
>>>draft-frascone-xml-dictionary-00 describes the Diameter
> 
> "dictionary"
> 
>>>in XML format; draft-legg-xed-roadmap-06.txt describes translating
>>>LDAP and X.509 directory information models into semantically
>>>equivalent XML renditions of existing directory protocols; IPPM is
>>>working on an information model in XML for traceroute 
>>
>>measurements. So
>>
>>>a MIB-related translation to XML is not unique.
>>>
>>>The XSDMI effort is about taking the MIB, which operators have
>>>complained is not well suited to configuration, and translating
>>>aspects of the MIB into equivalent XSD. The fact that the MIB
>>>datatypes can be translated into XSD will not make the MIB more
>>>suitable for configuration; it will simply make reusable dataypes
>>>available in an XML-compatible format.
>>>
>>>The netconf community should be focused on defining a data
> 
> modeling
> 
>>>language and data models for configuration. The YANG approach for
>>>netconf focuses not only on configuration, but also on developing
> 
> an
> 
>>>information modeling language which can then be used by tools to
>>>generate syntax-specific data models for a variety of purposes,
> 
> such
> 
>>>as Netconf-suitable XSD data models, SNMP-suitable MIB modules,
> 
> plus
> 
>>>data models for other modeling systems. I have a concern 
>>
>>that the SNMP
>>
>>>community has not been asking for this approach, and the IETF
> 
> failed
> 
>>>to reach consensus on the need for the information-modeling
> 
> approach
> 
>>>when it was presented to the SMING WG. If the
>>>information-model-generates-data-models approach is adopted by the
>>>IETF, then does that mean that efforts to use XML-based data
> 
> models
> 
>>>for ipfix, Diameter, IPPM, and LDAP should not be permitted 
>>
>>until YANG
>>
>>>can determine how to generate those data models as well?
>>>
>>>Just to be clear, I support the YANG effort because I 
>>
>>believe it could
>>
>>>lead to better consistency of data modeling across protocols, but
> 
> it
> 
>>>has yet to be proven to be viable, and other efforts to converge
> 
> or
> 
>>>harmonize data models have had mixed success at best. We should
> 
> not
> 
>>>put all our eggs into one basket. If the YANG approach proves to
> 
> be
> 
>>>viable, then the XSDMI translations can be modified as 
>>
>>needed to work
>>
>>>with YANG in the future. But XSDMI could give us XSD datatypes to
>>>develop data models, possibly years before consensus on YANG will
> 
> be
> 
>>>achieved.
>>>
>>>I believe the XSDMI effort should be an OPS-area effort (indeed an
>>>IETF-wide effort), focused in the OPSAWG, to allow the 
>>
>>representation
>>
>>>and translation into XML idiom of the existing datatypes, textual
>>>conventions, and semantic models defined in 15 years of work by
>>>multiple working groups and multiple areas of the IETF. 
>>>
>>>David Harrington
>>>dbharrington@comcast.net
>>>ietfdbh@comcast.net
>>>
>>>
>>>
>>>
>>>_______________________________________________
>>>OPSAWG mailing list
>>>OPSAWG@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/opsawg
>>>
>>
> 
> 
> 


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 02 04:02:21 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1InrTI-00076X-8R; Fri, 02 Nov 2007 04:01:40 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1InrTD-00074X-Us
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 02 Nov 2007 04:01:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1InrT8-0006v4-O4
	for opsawg@ietf.org; Fri, 02 Nov 2007 04:01:30 -0400
Received: from mail.globalsuite.net ([69.46.103.200])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1InrSv-0004LU-JF
	for opsawg@ietf.org; Fri, 02 Nov 2007 04:01:23 -0400
X-AuditID: c0a8013c-af7bebb000007c30-dd-472ad919a13a
Received: from Harrington73653 (streamline120.sjccnet.com [207.87.51.120])
	by mail.globalsuite.net (Symantec Mail Security) with ESMTP id
	39A694DC005; Fri,  2 Nov 2007 02:00:25 -0600 (MDT)
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Ron Bonica'" <rbonica@juniper.net>
References: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com>
	<472A2A7E.7090401@juniper.net>
	<05a401c81cde$06d6d880$3f8011ac@china.huawei.com>
	<472A8039.2030903@juniper.net>
Subject: RE: [OPSAWG] XSDMI
Date: Fri, 2 Nov 2007 01:00:06 -0700
Message-ID: <05ba01c81d26$62769340$3f8011ac@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
In-Reply-To: <472A8039.2030903@juniper.net>
Thread-Index: Acgc8YaKoKBFuDzITtWejD597ZZXsgANMMMg
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 1ba0ec39a747b7612d6a8ae66d1a873c
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

I believe XSDMI should generate standards-track documents, not
Informational documents.

dbh 

> -----Original Message-----
> From: Ron Bonica [mailto:rbonica@juniper.net] 
> Sent: Thursday, November 01, 2007 6:41 PM
> To: David Harrington
> Cc: opsawg@ietf.org
> Subject: Re: [OPSAWG] XSDMI
> 
> David,
> 
> Are there any aspects of the proposal that you would like to 
> change? Or
> are we in violent agreement?
> 
>                                 Ron
> 
> 
> David Harrington wrote:
> > Hi,
> > 
> > The goal of XSDMI is to provide a standard translation of SMI
> > datatypes, textual conventions, and macros into XML family
formats,
> > such as XSD.
> > 
> > I have said this over and over: There has never been any 
> intention on
> > my part to mandate that any XML-based protocol, including Netconf,
> > MUST use the XSD output from the XSDMI translations. These
> > translatinos are being provided to **enable and encourage** reuse
of
> > SMIv2 datatypes and textual conventions in XML-based 
> protocols, and to
> > provide XML-based support for SMIv2 macros to encourage reuse of
the
> > MIB data models (schemas) in XML-capable management applications
and
> > databases.
> > 
> > It is purely a Netconf decision whether to reuse these datatype
> > translations, just as it would be purely a "foo" protocol decision
> > whether the datatypes were appropriate for reuse in the "foo"
> > environment. The XSDMI work is totally independent of the work
being
> > done by and for the Netconf community.
> > 
> > Perasnally, I expect that the data modeling needed for
configuration
> > will require things that SMIv2 does not have - the ability to
> > distinguish config data from state data, the ability to specify
data
> > from the candidate datastore vs that from the running or startup
> > datastores, nested data structures, standardized methods, etc.
SMIv2
> > MIBs and the XSD equivalents cannot do this! 
> > 
> > I think it unlikely that the XSD output from a Netconf-specific
> > effort, such as YANG, will match the XSD output from the 
> XSDMI effort,
> > because if it did then it could be argued that there is no need to
> > move to a new data modeling language, only the need to 
> translate SMIv2
> > into XML-based formats. XML and XSD do not enable better
> > configuration; a configuration-focused protocol and
> > configuration-focused data models will do that. I consider it
> > appropriate that the data models from the SMIv2 MIB and the data
> > models designed for Netcof configuration not match because they
are
> > designed to serve different purposes. 
> > 
> > The data models that already exist for SNMP and syslog and 
> RADIUS and
> > Diameter and IPFIX do not match, because they serve 
> different purposes
> > and contain different modeling information, even though they are
all
> > related to network management. The data model encodings 
> used for MIBs
> > and LDAP search filters and X.509 certificates differ because they
> > serve different purposes, even though they all use ASN.1 
> encoding. The
> > netconf data models and their encodings SHOULD differ from the
> > SNMP/MIB data models because the information that we need 
> to model and
> > to encode on the wire for these different purposes and different
> > protocols is different.
> > 
> > I do not feel that publishing the XSDMI translations as 
> Informational
> > is called for. This work is **independent** of Netconf.
> > 
> > The goal of XSDMI is to provide a **standard** translation of SMI
> > datatypes, textual conventions, and macros into XML family
formats,
> > such as XSD, so other protocols can **choose** to use compatible
> > datatypes, and have a standard interoperable translation already
> > available so they don't have to do the translation 
> themselves, and so
> > the standard translations can be done by people who really 
> understand
> > the purpose and constraints of the SMIv2 datatypes and textual
> > conventions and macros.
> > 
> > It has **never** been my intention that people should be 
> **forced** to
> > use these translated datatypes, textual conventions, and macros
with
> > other protocols, only that we would make it easier for them to do
so
> > if they wanted to, and to promote interoperability by giving them
> > standard translations they could use.
> > 
> > David Harrington
> > dbharrington@comcast.net
> > ietfdbh@comcast.net
> > 
> > 
> > 
> >>-----Original Message-----
> >>From: Ron Bonica [mailto:rbonica@juniper.net] 
> >>Sent: Thursday, November 01, 2007 12:35 PM
> >>To: David Harrington
> >>Cc: opsawg@ietf.org
> >>Subject: Re: [OPSAWG] XSDMI
> >>
> >>Hi David,
> >>
> >>The following is a possible compromise:
> >>
> >>David progresses the XSDMI work in the OPS Area WG. Although the
XSD
> >>produced by XSDMI is made available to everyone, there is no 
> >>mandate to
> >>use it. This means that it the NETCONF community decides that 
> >>XSDMI does
> >>not fulfill their requirements, they will be free to specify 
> >>something else.
> >>
> >>All drafts progressed as XSDMI will be submitted for publication
as
> >>INFORMATIONAL.
> >>
> >>Comments?
> >>
> >>                              Ron
> >>
> >>
> >>David Harrington wrote:
> >>
> >>>Hi,
> >>>
> >>>Juergen has raised the issue that the XSD produced by the 
> >>
> >>XDMI effort
> >>
> >>>and the XSD produced by the YANG effort might be different, 
> >>
> >>and having
> >>
> >>>two different XSD equivalents for MIB datatypes would be 
> >>
> >>suboptimal. I
> >>
> >>>agree.
> >>>
> >>>However, I have the concern that while vendors wait for YANG to
be
> >>>completed, they will need to develop proprietary data models for
> > 
> > use
> > 
> >>>with netconf. Some vendors will want to reuse datatypes found in
> > 
> > the
> > 
> >>>15 year compilation of IETF NM experience found in the standard
> > 
> > MIB
> > 
> >>>modules, and supported by existing implementation code. If they
> > 
> > need
> > 
> >>>to develop their own translations of existing SMI datatypes and
> >>>textual conventions into XSD and XML, we could wind up with 
> >>
> >>a variety
> >>
> >>>of competing XSD specifications. 
> >>>
> >>>The XSDMI work would provide reusable XSD equivalents of 
> >>
> >>SMI datatypes
> >>
> >>>and textual conventions. If vendors use these consistent XSD
> >>>translations, then later work to derive standards from the 
> >>
> >>proprietary
> >>
> >>>information/data models would be easier because there would be
> >>>increased commonality in the datatypes and textual conventions
and
> >>>semantics used to model the information.
> >>>
> >>>In addition to proprietary data models, there are multiple IETF
> >>>efforts to translate existing information models (often from
> >>>ASN.1-based formats) into XML formats.
> >>>draft-frascone-xml-dictionary-00 describes the Diameter
> > 
> > "dictionary"
> > 
> >>>in XML format; draft-legg-xed-roadmap-06.txt describes
translating
> >>>LDAP and X.509 directory information models into semantically
> >>>equivalent XML renditions of existing directory protocols; IPPM
is
> >>>working on an information model in XML for traceroute 
> >>
> >>measurements. So
> >>
> >>>a MIB-related translation to XML is not unique.
> >>>
> >>>The XSDMI effort is about taking the MIB, which operators have
> >>>complained is not well suited to configuration, and translating
> >>>aspects of the MIB into equivalent XSD. The fact that the MIB
> >>>datatypes can be translated into XSD will not make the MIB more
> >>>suitable for configuration; it will simply make reusable dataypes
> >>>available in an XML-compatible format.
> >>>
> >>>The netconf community should be focused on defining a data
> > 
> > modeling
> > 
> >>>language and data models for configuration. The YANG approach for
> >>>netconf focuses not only on configuration, but also on developing
> > 
> > an
> > 
> >>>information modeling language which can then be used by tools to
> >>>generate syntax-specific data models for a variety of purposes,
> > 
> > such
> > 
> >>>as Netconf-suitable XSD data models, SNMP-suitable MIB modules,
> > 
> > plus
> > 
> >>>data models for other modeling systems. I have a concern 
> >>
> >>that the SNMP
> >>
> >>>community has not been asking for this approach, and the IETF
> > 
> > failed
> > 
> >>>to reach consensus on the need for the information-modeling
> > 
> > approach
> > 
> >>>when it was presented to the SMING WG. If the
> >>>information-model-generates-data-models approach is adopted by
the
> >>>IETF, then does that mean that efforts to use XML-based data
> > 
> > models
> > 
> >>>for ipfix, Diameter, IPPM, and LDAP should not be permitted 
> >>
> >>until YANG
> >>
> >>>can determine how to generate those data models as well?
> >>>
> >>>Just to be clear, I support the YANG effort because I 
> >>
> >>believe it could
> >>
> >>>lead to better consistency of data modeling across protocols, but
> > 
> > it
> > 
> >>>has yet to be proven to be viable, and other efforts to converge
> > 
> > or
> > 
> >>>harmonize data models have had mixed success at best. We should
> > 
> > not
> > 
> >>>put all our eggs into one basket. If the YANG approach proves to
> > 
> > be
> > 
> >>>viable, then the XSDMI translations can be modified as 
> >>
> >>needed to work
> >>
> >>>with YANG in the future. But XSDMI could give us XSD datatypes to
> >>>develop data models, possibly years before consensus on YANG will
> > 
> > be
> > 
> >>>achieved.
> >>>
> >>>I believe the XSDMI effort should be an OPS-area effort (indeed
an
> >>>IETF-wide effort), focused in the OPSAWG, to allow the 
> >>
> >>representation
> >>
> >>>and translation into XML idiom of the existing datatypes, textual
> >>>conventions, and semantic models defined in 15 years of work by
> >>>multiple working groups and multiple areas of the IETF. 
> >>>
> >>>David Harrington
> >>>dbharrington@comcast.net
> >>>ietfdbh@comcast.net
> >>>
> >>>
> >>>
> >>>
> >>>_______________________________________________
> >>>OPSAWG mailing list
> >>>OPSAWG@ietf.org
> >>>https://www1.ietf.org/mailman/listinfo/opsawg
> >>>
> >>
> > 
> > 
> > 
> 




_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 02 05:14:29 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Insay-0007ie-Mg; Fri, 02 Nov 2007 05:13:40 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Insax-0007h9-DV
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 02 Nov 2007 05:13:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Insax-0007h1-1G
	for opsawg@ietf.org; Fri, 02 Nov 2007 05:13:39 -0400
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Insav-0008TD-Qs
	for opsawg@ietf.org; Fri, 02 Nov 2007 05:13:38 -0400
X-IronPort-AV: E=Sophos;i="4.21,361,1188792000"; d="scan'208";a="75517897"
Received: from 14.140.8.135.in-addr.arpa (HELO 307622ANEX5.global.avaya.com)
	([135.64.140.14])
	by nj300815-nj-outbound.avaya.com with ESMTP; 02 Nov 2007 05:13:36 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [OPSAWG] XSDMI
Date: Fri, 2 Nov 2007 10:13:32 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A045A9FFB@307622ANEX5.global.avaya.com>
In-Reply-To: <05ba01c81d26$62769340$3f8011ac@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] XSDMI
Thread-Index: Acgc8YaKoKBFuDzITtWejD597ZZXsgANMMMgAAH+ynA=
References: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com><472A2A7E.7090401@juniper.net><05a401c81cde$06d6d880$3f8011ac@china.huawei.com><472A8039.2030903@juniper.net>
	<05ba01c81d26$62769340$3f8011ac@china.huawei.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "David Harrington" <ietfdbh@comcast.net>,
	"Ron Bonica" <rbonica@juniper.net>
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 1df8e4abc9851cb4adb45bd64d8514ae
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

As a contributor I agree with David's point - providing a
'standards-track' mapping and XSDMI translation would better serve the
goal of translating the current SMI-based data models and with the right
wording in the charter and documents we can make very clear that the
effort is independent of NETCONF and does not mandate anything for
NETCONF or other protocols. However, I do not believe that we should
make a determination of the final status of the documents now, or get
blocked in the discussion about this item that early. Let us present the
revised version of documents to the OPSAWG meeting in Vancouver with the
proposal to re-charter OPSAWG to include as a generic area work items.
If OPSAWG accepts these two documents as work items in its charter the
discussion should anyway happen here and be subject to consensus of the
WG. =20

Dan

=20

> -----Original Message-----
> From: David Harrington [mailto:ietfdbh@comcast.net]=20
> Sent: Friday, November 02, 2007 10:00 AM
> To: 'Ron Bonica'
> Cc: opsawg@ietf.org
> Subject: RE: [OPSAWG] XSDMI
>=20
> I believe XSDMI should generate standards-track documents,=20
> not Informational documents.
>=20
> dbh=20
>=20
> > -----Original Message-----
> > From: Ron Bonica [mailto:rbonica@juniper.net]
> > Sent: Thursday, November 01, 2007 6:41 PM
> > To: David Harrington
> > Cc: opsawg@ietf.org
> > Subject: Re: [OPSAWG] XSDMI
> >=20
> > David,
> >=20
> > Are there any aspects of the proposal that you would like=20
> to change?=20
> > Or are we in violent agreement?
> >=20
> >                                 Ron
> >=20
> >=20
> > David Harrington wrote:
> > > Hi,
> > >=20
> > > The goal of XSDMI is to provide a standard translation of SMI=20
> > > datatypes, textual conventions, and macros into XML family
> formats,
> > > such as XSD.
> > >=20
> > > I have said this over and over: There has never been any
> > intention on
> > > my part to mandate that any XML-based protocol, including=20
> Netconf,=20
> > > MUST use the XSD output from the XSDMI translations. These=20
> > > translatinos are being provided to **enable and encourage** reuse
> of
> > > SMIv2 datatypes and textual conventions in XML-based
> > protocols, and to
> > > provide XML-based support for SMIv2 macros to encourage reuse of
> the
> > > MIB data models (schemas) in XML-capable management applications
> and
> > > databases.
> > >=20
> > > It is purely a Netconf decision whether to reuse these datatype=20
> > > translations, just as it would be purely a "foo" protocol=20
> decision=20
> > > whether the datatypes were appropriate for reuse in the "foo"
> > > environment. The XSDMI work is totally independent of the work
> being
> > > done by and for the Netconf community.
> > >=20
> > > Perasnally, I expect that the data modeling needed for
> configuration
> > > will require things that SMIv2 does not have - the ability to=20
> > > distinguish config data from state data, the ability to specify
> data
> > > from the candidate datastore vs that from the running or startup=20
> > > datastores, nested data structures, standardized methods, etc.
> SMIv2
> > > MIBs and the XSD equivalents cannot do this!=20
> > >=20
> > > I think it unlikely that the XSD output from a Netconf-specific=20
> > > effort, such as YANG, will match the XSD output from the
> > XSDMI effort,
> > > because if it did then it could be argued that there is=20
> no need to=20
> > > move to a new data modeling language, only the need to
> > translate SMIv2
> > > into XML-based formats. XML and XSD do not enable better=20
> > > configuration; a configuration-focused protocol and=20
> > > configuration-focused data models will do that. I consider it=20
> > > appropriate that the data models from the SMIv2 MIB and the data=20
> > > models designed for Netcof configuration not match because they
> are
> > > designed to serve different purposes.=20
> > >=20
> > > The data models that already exist for SNMP and syslog and
> > RADIUS and
> > > Diameter and IPFIX do not match, because they serve
> > different purposes
> > > and contain different modeling information, even though they are
> all
> > > related to network management. The data model encodings
> > used for MIBs
> > > and LDAP search filters and X.509 certificates differ=20
> because they=20
> > > serve different purposes, even though they all use ASN.1
> > encoding. The
> > > netconf data models and their encodings SHOULD differ from the=20
> > > SNMP/MIB data models because the information that we need
> > to model and
> > > to encode on the wire for these different purposes and different=20
> > > protocols is different.
> > >=20
> > > I do not feel that publishing the XSDMI translations as
> > Informational
> > > is called for. This work is **independent** of Netconf.
> > >=20
> > > The goal of XSDMI is to provide a **standard** translation of SMI=20
> > > datatypes, textual conventions, and macros into XML family
> formats,
> > > such as XSD, so other protocols can **choose** to use compatible=20
> > > datatypes, and have a standard interoperable translation already=20
> > > available so they don't have to do the translation
> > themselves, and so
> > > the standard translations can be done by people who really
> > understand
> > > the purpose and constraints of the SMIv2 datatypes and textual=20
> > > conventions and macros.
> > >=20
> > > It has **never** been my intention that people should be
> > **forced** to
> > > use these translated datatypes, textual conventions, and macros
> with
> > > other protocols, only that we would make it easier for them to do
> so
> > > if they wanted to, and to promote interoperability by giving them=20
> > > standard translations they could use.
> > >=20
> > > David Harrington
> > > dbharrington@comcast.net
> > > ietfdbh@comcast.net
> > >=20
> > >=20
> > >=20
> > >>-----Original Message-----
> > >>From: Ron Bonica [mailto:rbonica@juniper.net]
> > >>Sent: Thursday, November 01, 2007 12:35 PM
> > >>To: David Harrington
> > >>Cc: opsawg@ietf.org
> > >>Subject: Re: [OPSAWG] XSDMI
> > >>
> > >>Hi David,
> > >>
> > >>The following is a possible compromise:
> > >>
> > >>David progresses the XSDMI work in the OPS Area WG. Although the
> XSD
> > >>produced by XSDMI is made available to everyone, there is=20
> no mandate=20
> > >>to use it. This means that it the NETCONF community decides that=20
> > >>XSDMI does not fulfill their requirements, they will be free to=20
> > >>specify something else.
> > >>
> > >>All drafts progressed as XSDMI will be submitted for publication
> as
> > >>INFORMATIONAL.
> > >>
> > >>Comments?
> > >>
> > >>                              Ron
> > >>
> > >>
> > >>David Harrington wrote:
> > >>
> > >>>Hi,
> > >>>
> > >>>Juergen has raised the issue that the XSD produced by the
> > >>
> > >>XDMI effort
> > >>
> > >>>and the XSD produced by the YANG effort might be different,
> > >>
> > >>and having
> > >>
> > >>>two different XSD equivalents for MIB datatypes would be
> > >>
> > >>suboptimal. I
> > >>
> > >>>agree.
> > >>>
> > >>>However, I have the concern that while vendors wait for YANG to
> be
> > >>>completed, they will need to develop proprietary data models for
> > >=20
> > > use
> > >=20
> > >>>with netconf. Some vendors will want to reuse datatypes found in
> > >=20
> > > the
> > >=20
> > >>>15 year compilation of IETF NM experience found in the standard
> > >=20
> > > MIB
> > >=20
> > >>>modules, and supported by existing implementation code. If they
> > >=20
> > > need
> > >=20
> > >>>to develop their own translations of existing SMI datatypes and=20
> > >>>textual conventions into XSD and XML, we could wind up with
> > >>
> > >>a variety
> > >>
> > >>>of competing XSD specifications.=20
> > >>>
> > >>>The XSDMI work would provide reusable XSD equivalents of
> > >>
> > >>SMI datatypes
> > >>
> > >>>and textual conventions. If vendors use these consistent XSD=20
> > >>>translations, then later work to derive standards from the
> > >>
> > >>proprietary
> > >>
> > >>>information/data models would be easier because there would be=20
> > >>>increased commonality in the datatypes and textual conventions
> and
> > >>>semantics used to model the information.
> > >>>
> > >>>In addition to proprietary data models, there are multiple IETF=20
> > >>>efforts to translate existing information models (often from=20
> > >>>ASN.1-based formats) into XML formats.
> > >>>draft-frascone-xml-dictionary-00 describes the Diameter
> > >=20
> > > "dictionary"
> > >=20
> > >>>in XML format; draft-legg-xed-roadmap-06.txt describes
> translating
> > >>>LDAP and X.509 directory information models into semantically=20
> > >>>equivalent XML renditions of existing directory protocols; IPPM
> is
> > >>>working on an information model in XML for traceroute
> > >>
> > >>measurements. So
> > >>
> > >>>a MIB-related translation to XML is not unique.
> > >>>
> > >>>The XSDMI effort is about taking the MIB, which operators have=20
> > >>>complained is not well suited to configuration, and translating=20
> > >>>aspects of the MIB into equivalent XSD. The fact that the MIB=20
> > >>>datatypes can be translated into XSD will not make the MIB more=20
> > >>>suitable for configuration; it will simply make reusable=20
> dataypes=20
> > >>>available in an XML-compatible format.
> > >>>
> > >>>The netconf community should be focused on defining a data
> > >=20
> > > modeling
> > >=20
> > >>>language and data models for configuration. The YANG=20
> approach for=20
> > >>>netconf focuses not only on configuration, but also on developing
> > >=20
> > > an
> > >=20
> > >>>information modeling language which can then be used by tools to=20
> > >>>generate syntax-specific data models for a variety of purposes,
> > >=20
> > > such
> > >=20
> > >>>as Netconf-suitable XSD data models, SNMP-suitable MIB modules,
> > >=20
> > > plus
> > >=20
> > >>>data models for other modeling systems. I have a concern
> > >>
> > >>that the SNMP
> > >>
> > >>>community has not been asking for this approach, and the IETF
> > >=20
> > > failed
> > >=20
> > >>>to reach consensus on the need for the information-modeling
> > >=20
> > > approach
> > >=20
> > >>>when it was presented to the SMING WG. If the=20
> > >>>information-model-generates-data-models approach is adopted by
> the
> > >>>IETF, then does that mean that efforts to use XML-based data
> > >=20
> > > models
> > >=20
> > >>>for ipfix, Diameter, IPPM, and LDAP should not be permitted
> > >>
> > >>until YANG
> > >>
> > >>>can determine how to generate those data models as well?
> > >>>
> > >>>Just to be clear, I support the YANG effort because I
> > >>
> > >>believe it could
> > >>
> > >>>lead to better consistency of data modeling across protocols, but
> > >=20
> > > it
> > >=20
> > >>>has yet to be proven to be viable, and other efforts to converge
> > >=20
> > > or
> > >=20
> > >>>harmonize data models have had mixed success at best. We should
> > >=20
> > > not
> > >=20
> > >>>put all our eggs into one basket. If the YANG approach proves to
> > >=20
> > > be
> > >=20
> > >>>viable, then the XSDMI translations can be modified as
> > >>
> > >>needed to work
> > >>
> > >>>with YANG in the future. But XSDMI could give us XSD=20
> datatypes to=20
> > >>>develop data models, possibly years before consensus on YANG will
> > >=20
> > > be
> > >=20
> > >>>achieved.
> > >>>
> > >>>I believe the XSDMI effort should be an OPS-area effort (indeed
> an
> > >>>IETF-wide effort), focused in the OPSAWG, to allow the
> > >>
> > >>representation
> > >>
> > >>>and translation into XML idiom of the existing=20
> datatypes, textual=20
> > >>>conventions, and semantic models defined in 15 years of work by=20
> > >>>multiple working groups and multiple areas of the IETF.
> > >>>
> > >>>David Harrington
> > >>>dbharrington@comcast.net
> > >>>ietfdbh@comcast.net
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>_______________________________________________
> > >>>OPSAWG mailing list
> > >>>OPSAWG@ietf.org
> > >>>https://www1.ietf.org/mailman/listinfo/opsawg
> > >>>
> > >>
> > >=20
> > >=20
> > >=20
> >=20
>=20
>=20
>=20
>=20
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www1.ietf.org/mailman/listinfo/opsawg
>=20


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 02 05:55:10 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IntEk-0001UJ-L2; Fri, 02 Nov 2007 05:54:46 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IntEj-0001UA-TK
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 02 Nov 2007 05:54:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IntEj-0001Tc-IW
	for opsawg@ietf.org; Fri, 02 Nov 2007 05:54:45 -0400
Received: from hermes.jacobs-university.de ([212.201.44.23])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IntEj-0000zW-7h
	for opsawg@ietf.org; Fri, 02 Nov 2007 05:54:45 -0400
Received: from localhost (demetrius.jacobs-university.de [212.201.44.32])
	by hermes.jacobs-university.de (Postfix) with ESMTP id 06AD48A11C;
	Fri,  2 Nov 2007 10:54:44 +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 07326-04; Fri,  2 Nov 2007 10:54:39 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133])
	by hermes.jacobs-university.de (Postfix) with ESMTP id A73BF8A115;
	Fri,  2 Nov 2007 10:54:36 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501)
	id 5F81A3B80BA; Fri,  2 Nov 2007 10:54:36 +0100 (CET)
Date: Fri, 2 Nov 2007 10:54:36 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: [OPSAWG] XSDMI
Message-ID: <20071102095436.GC1818@elstar.local>
Mail-Followup-To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>,
	David Harrington <ietfdbh@comcast.net>,
	Ron Bonica <rbonica@juniper.net>, opsawg@ietf.org
References: <05ba01c81d26$62769340$3f8011ac@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A045A9FFB@307622ANEX5.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A045A9FFB@307622ANEX5.global.avaya.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@jacobs-university.de
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

On Fri, Nov 02, 2007 at 10:13:32AM +0100, Romascanu, Dan (Dan) wrote:

> As a contributor I agree with David's point - providing a
> 'standards-track' mapping and XSDMI translation would better serve
> the goal of translating the current SMI-based data models and with
> the right wording in the charter and documents we can make very
> clear that the effort is independent of NETCONF and does not mandate
> anything for NETCONF or other protocols.

So which protocol is going to use this XSDMI mapping?
I always wonder what these "other protocols" are...

/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/>


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 02 10:25:50 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1InxSn-0000dG-03; Fri, 02 Nov 2007 10:25:33 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1InxSm-0000d9-3V
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 02 Nov 2007 10:25:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1InxSl-0000d1-Os
	for opsawg@ietf.org; Fri, 02 Nov 2007 10:25:31 -0400
Received: from mail.globalsuite.net ([69.46.103.200])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1InxSl-0008U1-6h
	for opsawg@ietf.org; Fri, 02 Nov 2007 10:25:31 -0400
X-AuditID: c0a8013c-aadbabb0000032fe-10-472b3359f6ee
Received: from Harrington73653 (streamline120.sjccnet.com [207.87.51.120])
	by mail.globalsuite.net (Symantec Mail Security) with ESMTP id
	BF0D84DC024; Fri,  2 Nov 2007 08:25:28 -0600 (MDT)
From: "David Harrington" <ietfdbh@comcast.net>
To: <j.schoenwaelder@jacobs-university.de>,
	"'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>
References: <05ba01c81d26$62769340$3f8011ac@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A045A9FFB@307622ANEX5.global.avaya.com>
	<20071102095436.GC1818@elstar.local>
Subject: RE: [OPSAWG] XSDMI
Date: Fri, 2 Nov 2007 07:25:09 -0700
Message-ID: <05f501c81d5c$2d5808c0$3f8011ac@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
In-Reply-To: <20071102095436.GC1818@elstar.local>
Thread-Index: AcgdNmbJ0SGycnkEROeFOLF4VT6GXwAISUhA
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Hi Juergen,

The whole point is that this WG should not be authorized to make the
decision about which other protocols or which applications will use
these mappings. No protocols or applications should be required to use
the XSDMI mappings, and the decision about the applicability of these
mappings should rest with the developers of any current or future
protocols or applications that could benefit from their reuse.

The mappings should be done in the OPS area, where SMIv2 experts are
available to ensure the semantics of the SMIv2 constructs are
maintained in the mappings. The mappings would then be available to
make it easier for developers of protocols and network management
applications, current and future, inside and outside the IETF, to use
the standardized, vendor-neutral, interoperable XML-based mapping for
SMIv2 constructs if they choose to do so. The documents should also
identify which SMIv2 constructs are NOT RECOMMENDED for use by new
protocols, and which mappings are provided for backwards compatibility
and should be used only when accessing or modeling SMIv2 MIB data
models.

Relying on the developers of future protocols and applications to do
the mappings themselves as needed, could result in a proliferation of
incompatible, non-interoperable, vendor-specific, protocol-biased, and
potentially incorrect mappings of SMIv2 constructs. 

dbh 

> -----Original Message-----
> From: Juergen Schoenwaelder 
> [mailto:j.schoenwaelder@jacobs-university.de] 
> Sent: Friday, November 02, 2007 2:55 AM
> To: Romascanu, Dan (Dan)
> Cc: David Harrington; Ron Bonica; opsawg@ietf.org
> Subject: Re: [OPSAWG] XSDMI
> 
> On Fri, Nov 02, 2007 at 10:13:32AM +0100, Romascanu, Dan (Dan)
wrote:
> 
> > As a contributor I agree with David's point - providing a
> > 'standards-track' mapping and XSDMI translation would better serve
> > the goal of translating the current SMI-based data models and with
> > the right wording in the charter and documents we can make very
> > clear that the effort is independent of NETCONF and does not
mandate
> > anything for NETCONF or other protocols.
> 
> So which protocol is going to use this XSDMI mapping?
> I always wonder what these "other protocols" are...
> 
> /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/>
> 




_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 02 11:05:49 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iny5B-0005oL-BM; Fri, 02 Nov 2007 11:05:13 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Iny5A-0005oB-KB
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 02 Nov 2007 11:05:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Iny5A-0005nd-A0
	for opsawg@ietf.org; Fri, 02 Nov 2007 11:05:12 -0400
Received: from exprod7og101.obsmtp.com ([64.18.2.155])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iny53-0000lg-SH
	for opsawg@ietf.org; Fri, 02 Nov 2007 11:05:12 -0400
Received: from source ([66.129.224.36]) by exprod7ob101.postini.com
	([64.18.6.12]) with SMTP; Fri, 02 Nov 2007 08:04:34 PDT
Received: from proton.jnpr.net ([10.10.2.37]) by emailsmtp56.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959); Fri, 2 Nov 2007 08:03:32 -0700
Received: from [172.23.1.146] ([172.23.1.146] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Nov 2007 11:03:29 -0400
Message-ID: <472B3C3D.4000903@juniper.net>
Date: Fri, 02 Nov 2007 11:03:25 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
Subject: Re: [OPSAWG] XSDMI
References: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com>
	<472A2A7E.7090401@juniper.net>
	<05a401c81cde$06d6d880$3f8011ac@china.huawei.com>
	<472A8039.2030903@juniper.net>
	<05ba01c81d26$62769340$3f8011ac@china.huawei.com>
In-Reply-To: <05ba01c81d26$62769340$3f8011ac@china.huawei.com>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Nov 2007 15:03:29.0947 (UTC)
	FILETIME=[875336B0:01C81D61]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4a4195ffb11c7b0baf82f77b2a730aa9
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org


  Why?

  Doesn't the existence of a standards track RFC mandate that people use
the XSDMI mappings? Isn't that exactly the mandate that we are trying to
avoid?

                                    Ron


David Harrington wrote:
> I believe XSDMI should generate standards-track documents, not
> Informational documents.
> 
> dbh 
> 
> 
>>-----Original Message-----
>>From: Ron Bonica [mailto:rbonica@juniper.net] 
>>Sent: Thursday, November 01, 2007 6:41 PM
>>To: David Harrington
>>Cc: opsawg@ietf.org
>>Subject: Re: [OPSAWG] XSDMI
>>
>>David,
>>
>>Are there any aspects of the proposal that you would like to 
>>change? Or
>>are we in violent agreement?
>>
>>                                Ron
>>
>>
>>David Harrington wrote:
>>
>>>Hi,
>>>
>>>The goal of XSDMI is to provide a standard translation of SMI
>>>datatypes, textual conventions, and macros into XML family
> 
> formats,
> 
>>>such as XSD.
>>>
>>>I have said this over and over: There has never been any 
>>
>>intention on
>>
>>>my part to mandate that any XML-based protocol, including Netconf,
>>>MUST use the XSD output from the XSDMI translations. These
>>>translatinos are being provided to **enable and encourage** reuse
> 
> of
> 
>>>SMIv2 datatypes and textual conventions in XML-based 
>>
>>protocols, and to
>>
>>>provide XML-based support for SMIv2 macros to encourage reuse of
> 
> the
> 
>>>MIB data models (schemas) in XML-capable management applications
> 
> and
> 
>>>databases.
>>>
>>>It is purely a Netconf decision whether to reuse these datatype
>>>translations, just as it would be purely a "foo" protocol decision
>>>whether the datatypes were appropriate for reuse in the "foo"
>>>environment. The XSDMI work is totally independent of the work
> 
> being
> 
>>>done by and for the Netconf community.
>>>
>>>Perasnally, I expect that the data modeling needed for
> 
> configuration
> 
>>>will require things that SMIv2 does not have - the ability to
>>>distinguish config data from state data, the ability to specify
> 
> data
> 
>>>from the candidate datastore vs that from the running or startup
>>>datastores, nested data structures, standardized methods, etc.
> 
> SMIv2
> 
>>>MIBs and the XSD equivalents cannot do this! 
>>>
>>>I think it unlikely that the XSD output from a Netconf-specific
>>>effort, such as YANG, will match the XSD output from the 
>>
>>XSDMI effort,
>>
>>>because if it did then it could be argued that there is no need to
>>>move to a new data modeling language, only the need to 
>>
>>translate SMIv2
>>
>>>into XML-based formats. XML and XSD do not enable better
>>>configuration; a configuration-focused protocol and
>>>configuration-focused data models will do that. I consider it
>>>appropriate that the data models from the SMIv2 MIB and the data
>>>models designed for Netcof configuration not match because they
> 
> are
> 
>>>designed to serve different purposes. 
>>>
>>>The data models that already exist for SNMP and syslog and 
>>
>>RADIUS and
>>
>>>Diameter and IPFIX do not match, because they serve 
>>
>>different purposes
>>
>>>and contain different modeling information, even though they are
> 
> all
> 
>>>related to network management. The data model encodings 
>>
>>used for MIBs
>>
>>>and LDAP search filters and X.509 certificates differ because they
>>>serve different purposes, even though they all use ASN.1 
>>
>>encoding. The
>>
>>>netconf data models and their encodings SHOULD differ from the
>>>SNMP/MIB data models because the information that we need 
>>
>>to model and
>>
>>>to encode on the wire for these different purposes and different
>>>protocols is different.
>>>
>>>I do not feel that publishing the XSDMI translations as 
>>
>>Informational
>>
>>>is called for. This work is **independent** of Netconf.
>>>
>>>The goal of XSDMI is to provide a **standard** translation of SMI
>>>datatypes, textual conventions, and macros into XML family
> 
> formats,
> 
>>>such as XSD, so other protocols can **choose** to use compatible
>>>datatypes, and have a standard interoperable translation already
>>>available so they don't have to do the translation 
>>
>>themselves, and so
>>
>>>the standard translations can be done by people who really 
>>
>>understand
>>
>>>the purpose and constraints of the SMIv2 datatypes and textual
>>>conventions and macros.
>>>
>>>It has **never** been my intention that people should be 
>>
>>**forced** to
>>
>>>use these translated datatypes, textual conventions, and macros
> 
> with
> 
>>>other protocols, only that we would make it easier for them to do
> 
> so
> 
>>>if they wanted to, and to promote interoperability by giving them
>>>standard translations they could use.
>>>
>>>David Harrington
>>>dbharrington@comcast.net
>>>ietfdbh@comcast.net
>>>
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Ron Bonica [mailto:rbonica@juniper.net] 
>>>>Sent: Thursday, November 01, 2007 12:35 PM
>>>>To: David Harrington
>>>>Cc: opsawg@ietf.org
>>>>Subject: Re: [OPSAWG] XSDMI
>>>>
>>>>Hi David,
>>>>
>>>>The following is a possible compromise:
>>>>
>>>>David progresses the XSDMI work in the OPS Area WG. Although the
> 
> XSD
> 
>>>>produced by XSDMI is made available to everyone, there is no 
>>>>mandate to
>>>>use it. This means that it the NETCONF community decides that 
>>>>XSDMI does
>>>>not fulfill their requirements, they will be free to specify 
>>>>something else.
>>>>
>>>>All drafts progressed as XSDMI will be submitted for publication
> 
> as
> 
>>>>INFORMATIONAL.
>>>>
>>>>Comments?
>>>>
>>>>                             Ron
>>>>
>>>>
>>>>David Harrington wrote:
>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>Juergen has raised the issue that the XSD produced by the 
>>>>
>>>>XDMI effort
>>>>
>>>>
>>>>>and the XSD produced by the YANG effort might be different, 
>>>>
>>>>and having
>>>>
>>>>
>>>>>two different XSD equivalents for MIB datatypes would be 
>>>>
>>>>suboptimal. I
>>>>
>>>>
>>>>>agree.
>>>>>
>>>>>However, I have the concern that while vendors wait for YANG to
> 
> be
> 
>>>>>completed, they will need to develop proprietary data models for
>>>
>>>use
>>>
>>>
>>>>>with netconf. Some vendors will want to reuse datatypes found in
>>>
>>>the
>>>
>>>
>>>>>15 year compilation of IETF NM experience found in the standard
>>>
>>>MIB
>>>
>>>
>>>>>modules, and supported by existing implementation code. If they
>>>
>>>need
>>>
>>>
>>>>>to develop their own translations of existing SMI datatypes and
>>>>>textual conventions into XSD and XML, we could wind up with 
>>>>
>>>>a variety
>>>>
>>>>
>>>>>of competing XSD specifications. 
>>>>>
>>>>>The XSDMI work would provide reusable XSD equivalents of 
>>>>
>>>>SMI datatypes
>>>>
>>>>
>>>>>and textual conventions. If vendors use these consistent XSD
>>>>>translations, then later work to derive standards from the 
>>>>
>>>>proprietary
>>>>
>>>>
>>>>>information/data models would be easier because there would be
>>>>>increased commonality in the datatypes and textual conventions
> 
> and
> 
>>>>>semantics used to model the information.
>>>>>
>>>>>In addition to proprietary data models, there are multiple IETF
>>>>>efforts to translate existing information models (often from
>>>>>ASN.1-based formats) into XML formats.
>>>>>draft-frascone-xml-dictionary-00 describes the Diameter
>>>
>>>"dictionary"
>>>
>>>
>>>>>in XML format; draft-legg-xed-roadmap-06.txt describes
> 
> translating
> 
>>>>>LDAP and X.509 directory information models into semantically
>>>>>equivalent XML renditions of existing directory protocols; IPPM
> 
> is
> 
>>>>>working on an information model in XML for traceroute 
>>>>
>>>>measurements. So
>>>>
>>>>
>>>>>a MIB-related translation to XML is not unique.
>>>>>
>>>>>The XSDMI effort is about taking the MIB, which operators have
>>>>>complained is not well suited to configuration, and translating
>>>>>aspects of the MIB into equivalent XSD. The fact that the MIB
>>>>>datatypes can be translated into XSD will not make the MIB more
>>>>>suitable for configuration; it will simply make reusable dataypes
>>>>>available in an XML-compatible format.
>>>>>
>>>>>The netconf community should be focused on defining a data
>>>
>>>modeling
>>>
>>>
>>>>>language and data models for configuration. The YANG approach for
>>>>>netconf focuses not only on configuration, but also on developing
>>>
>>>an
>>>
>>>
>>>>>information modeling language which can then be used by tools to
>>>>>generate syntax-specific data models for a variety of purposes,
>>>
>>>such
>>>
>>>
>>>>>as Netconf-suitable XSD data models, SNMP-suitable MIB modules,
>>>
>>>plus
>>>
>>>
>>>>>data models for other modeling systems. I have a concern 
>>>>
>>>>that the SNMP
>>>>
>>>>
>>>>>community has not been asking for this approach, and the IETF
>>>
>>>failed
>>>
>>>
>>>>>to reach consensus on the need for the information-modeling
>>>
>>>approach
>>>
>>>
>>>>>when it was presented to the SMING WG. If the
>>>>>information-model-generates-data-models approach is adopted by
> 
> the
> 
>>>>>IETF, then does that mean that efforts to use XML-based data
>>>
>>>models
>>>
>>>
>>>>>for ipfix, Diameter, IPPM, and LDAP should not be permitted 
>>>>
>>>>until YANG
>>>>
>>>>
>>>>>can determine how to generate those data models as well?
>>>>>
>>>>>Just to be clear, I support the YANG effort because I 
>>>>
>>>>believe it could
>>>>
>>>>
>>>>>lead to better consistency of data modeling across protocols, but
>>>
>>>it
>>>
>>>
>>>>>has yet to be proven to be viable, and other efforts to converge
>>>
>>>or
>>>
>>>
>>>>>harmonize data models have had mixed success at best. We should
>>>
>>>not
>>>
>>>
>>>>>put all our eggs into one basket. If the YANG approach proves to
>>>
>>>be
>>>
>>>
>>>>>viable, then the XSDMI translations can be modified as 
>>>>
>>>>needed to work
>>>>
>>>>
>>>>>with YANG in the future. But XSDMI could give us XSD datatypes to
>>>>>develop data models, possibly years before consensus on YANG will
>>>
>>>be
>>>
>>>
>>>>>achieved.
>>>>>
>>>>>I believe the XSDMI effort should be an OPS-area effort (indeed
> 
> an
> 
>>>>>IETF-wide effort), focused in the OPSAWG, to allow the 
>>>>
>>>>representation
>>>>
>>>>
>>>>>and translation into XML idiom of the existing datatypes, textual
>>>>>conventions, and semantic models defined in 15 years of work by
>>>>>multiple working groups and multiple areas of the IETF. 
>>>>>
>>>>>David Harrington
>>>>>dbharrington@comcast.net
>>>>>ietfdbh@comcast.net
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>_______________________________________________
>>>>>OPSAWG mailing list
>>>>>OPSAWG@ietf.org
>>>>>https://www1.ietf.org/mailman/listinfo/opsawg
>>>>>
>>>>
>>>
>>>
> 
> 
> 


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 02 11:24:01 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1InyN8-0000YW-9z; Fri, 02 Nov 2007 11:23:46 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1InyN6-0000XV-F3
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 02 Nov 2007 11:23:44 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1InyN6-0000XN-15
	for opsawg@ietf.org; Fri, 02 Nov 2007 11:23:44 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1InyN4-0002Ch-8w
	for opsawg@ietf.org; Fri, 02 Nov 2007 11:23:43 -0400
X-IronPort-AV: E=Sophos;i="4.21,363,1188792000"; d="scan'208";a="80381390"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by co300216-co-outbound.avaya.com with ESMTP; 02 Nov 2007 11:23:39 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [OPSAWG] XSDMI
Date: Fri, 2 Nov 2007 16:22:56 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A045AA037@307622ANEX5.global.avaya.com>
In-Reply-To: <472B3C3D.4000903@juniper.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] XSDMI
Thread-Index: AcgdYi38CQlUXaC5QjW47gIuoNaygwAAO0Eg
References: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com><472A2A7E.7090401@juniper.net><05a401c81cde$06d6d880$3f8011ac@china.huawei.com><472A8039.2030903@juniper.net><05ba01c81d26$62769340$3f8011ac@china.huawei.com>
	<472B3C3D.4000903@juniper.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Ron Bonica" <rbonica@juniper.net>,
	"David Harrington" <ietfdbh@comcast.net>
X-Spam-Score: 1.8 (+)
X-Scan-Signature: d2bb8c7db26f2d12109e0cd8e454db52
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

The standards track RFC should be clear about its applicability. In this
case the applicability should be clearly limited to the translation
between existing SMIv2 data types and TCs  in into XML data models
expressed in XSD. It does not mandate usage of a certain protocol,
protocols using XML can use anything else than XSD, and even when using
XSD they can define their own data structures using other tools.=20

In other words, the standard should be about 'how to translate from A to
B', it's not about mandating the usage of B.=20

Dan


=20
=20

> -----Original Message-----
> From: Ron Bonica [mailto:rbonica@juniper.net]=20
> Sent: Friday, November 02, 2007 5:03 PM
> To: David Harrington
> Cc: opsawg@ietf.org
> Subject: Re: [OPSAWG] XSDMI
>=20
>=20
>   Why?
>=20
>   Doesn't the existence of a standards track RFC mandate that=20
> people use the XSDMI mappings? Isn't that exactly the mandate=20
> that we are trying to avoid?
>=20
>                                     Ron
>=20
>=20
> David Harrington wrote:
> > I believe XSDMI should generate standards-track documents, not=20
> > Informational documents.
> >=20
> > dbh
> >=20
> >=20
> >>-----Original Message-----
> >>From: Ron Bonica [mailto:rbonica@juniper.net]
> >>Sent: Thursday, November 01, 2007 6:41 PM
> >>To: David Harrington
> >>Cc: opsawg@ietf.org
> >>Subject: Re: [OPSAWG] XSDMI
> >>
> >>David,
> >>
> >>Are there any aspects of the proposal that you would like=20
> to change?=20
> >>Or are we in violent agreement?
> >>
> >>                                Ron
> >>
> >>
> >>David Harrington wrote:
> >>
> >>>Hi,
> >>>
> >>>The goal of XSDMI is to provide a standard translation of SMI=20
> >>>datatypes, textual conventions, and macros into XML family
> >=20
> > formats,
> >=20
> >>>such as XSD.
> >>>
> >>>I have said this over and over: There has never been any
> >>
> >>intention on
> >>
> >>>my part to mandate that any XML-based protocol, including Netconf,=20
> >>>MUST use the XSD output from the XSDMI translations. These=20
> >>>translatinos are being provided to **enable and encourage** reuse
> >=20
> > of
> >=20
> >>>SMIv2 datatypes and textual conventions in XML-based
> >>
> >>protocols, and to
> >>
> >>>provide XML-based support for SMIv2 macros to encourage reuse of
> >=20
> > the
> >=20
> >>>MIB data models (schemas) in XML-capable management applications
> >=20
> > and
> >=20
> >>>databases.
> >>>
> >>>It is purely a Netconf decision whether to reuse these datatype=20
> >>>translations, just as it would be purely a "foo" protocol decision=20
> >>>whether the datatypes were appropriate for reuse in the "foo"
> >>>environment. The XSDMI work is totally independent of the work
> >=20
> > being
> >=20
> >>>done by and for the Netconf community.
> >>>
> >>>Perasnally, I expect that the data modeling needed for
> >=20
> > configuration
> >=20
> >>>will require things that SMIv2 does not have - the ability to=20
> >>>distinguish config data from state data, the ability to specify
> >=20
> > data
> >=20
> >>>from the candidate datastore vs that from the running or startup=20
> >>>datastores, nested data structures, standardized methods, etc.
> >=20
> > SMIv2
> >=20
> >>>MIBs and the XSD equivalents cannot do this!=20
> >>>
> >>>I think it unlikely that the XSD output from a Netconf-specific=20
> >>>effort, such as YANG, will match the XSD output from the
> >>
> >>XSDMI effort,
> >>
> >>>because if it did then it could be argued that there is no need to=20
> >>>move to a new data modeling language, only the need to
> >>
> >>translate SMIv2
> >>
> >>>into XML-based formats. XML and XSD do not enable better=20
> >>>configuration; a configuration-focused protocol and=20
> >>>configuration-focused data models will do that. I consider it=20
> >>>appropriate that the data models from the SMIv2 MIB and the data=20
> >>>models designed for Netcof configuration not match because they
> >=20
> > are
> >=20
> >>>designed to serve different purposes.=20
> >>>
> >>>The data models that already exist for SNMP and syslog and
> >>
> >>RADIUS and
> >>
> >>>Diameter and IPFIX do not match, because they serve
> >>
> >>different purposes
> >>
> >>>and contain different modeling information, even though they are
> >=20
> > all
> >=20
> >>>related to network management. The data model encodings
> >>
> >>used for MIBs
> >>
> >>>and LDAP search filters and X.509 certificates differ because they=20
> >>>serve different purposes, even though they all use ASN.1
> >>
> >>encoding. The
> >>
> >>>netconf data models and their encodings SHOULD differ from the=20
> >>>SNMP/MIB data models because the information that we need
> >>
> >>to model and
> >>
> >>>to encode on the wire for these different purposes and different=20
> >>>protocols is different.
> >>>
> >>>I do not feel that publishing the XSDMI translations as
> >>
> >>Informational
> >>
> >>>is called for. This work is **independent** of Netconf.
> >>>
> >>>The goal of XSDMI is to provide a **standard** translation of SMI=20
> >>>datatypes, textual conventions, and macros into XML family
> >=20
> > formats,
> >=20
> >>>such as XSD, so other protocols can **choose** to use compatible=20
> >>>datatypes, and have a standard interoperable translation already=20
> >>>available so they don't have to do the translation
> >>
> >>themselves, and so
> >>
> >>>the standard translations can be done by people who really
> >>
> >>understand
> >>
> >>>the purpose and constraints of the SMIv2 datatypes and textual=20
> >>>conventions and macros.
> >>>
> >>>It has **never** been my intention that people should be
> >>
> >>**forced** to
> >>
> >>>use these translated datatypes, textual conventions, and macros
> >=20
> > with
> >=20
> >>>other protocols, only that we would make it easier for them to do
> >=20
> > so
> >=20
> >>>if they wanted to, and to promote interoperability by giving them=20
> >>>standard translations they could use.
> >>>
> >>>David Harrington
> >>>dbharrington@comcast.net
> >>>ietfdbh@comcast.net
> >>>
> >>>
> >>>
> >>>
> >>>>-----Original Message-----
> >>>>From: Ron Bonica [mailto:rbonica@juniper.net]
> >>>>Sent: Thursday, November 01, 2007 12:35 PM
> >>>>To: David Harrington
> >>>>Cc: opsawg@ietf.org
> >>>>Subject: Re: [OPSAWG] XSDMI
> >>>>
> >>>>Hi David,
> >>>>
> >>>>The following is a possible compromise:
> >>>>
> >>>>David progresses the XSDMI work in the OPS Area WG. Although the
> >=20
> > XSD
> >=20
> >>>>produced by XSDMI is made available to everyone, there is=20
> no mandate=20
> >>>>to use it. This means that it the NETCONF community decides that=20
> >>>>XSDMI does not fulfill their requirements, they will be free to=20
> >>>>specify something else.
> >>>>
> >>>>All drafts progressed as XSDMI will be submitted for publication
> >=20
> > as
> >=20
> >>>>INFORMATIONAL.
> >>>>
> >>>>Comments?
> >>>>
> >>>>                             Ron
> >>>>
> >>>>
> >>>>David Harrington wrote:
> >>>>
> >>>>
> >>>>>Hi,
> >>>>>
> >>>>>Juergen has raised the issue that the XSD produced by the
> >>>>
> >>>>XDMI effort
> >>>>
> >>>>
> >>>>>and the XSD produced by the YANG effort might be different,
> >>>>
> >>>>and having
> >>>>
> >>>>
> >>>>>two different XSD equivalents for MIB datatypes would be
> >>>>
> >>>>suboptimal. I
> >>>>
> >>>>
> >>>>>agree.
> >>>>>
> >>>>>However, I have the concern that while vendors wait for YANG to
> >=20
> > be
> >=20
> >>>>>completed, they will need to develop proprietary data models for
> >>>
> >>>use
> >>>
> >>>
> >>>>>with netconf. Some vendors will want to reuse datatypes found in
> >>>
> >>>the
> >>>
> >>>
> >>>>>15 year compilation of IETF NM experience found in the standard
> >>>
> >>>MIB
> >>>
> >>>
> >>>>>modules, and supported by existing implementation code. If they
> >>>
> >>>need
> >>>
> >>>
> >>>>>to develop their own translations of existing SMI datatypes and=20
> >>>>>textual conventions into XSD and XML, we could wind up with
> >>>>
> >>>>a variety
> >>>>
> >>>>
> >>>>>of competing XSD specifications.=20
> >>>>>
> >>>>>The XSDMI work would provide reusable XSD equivalents of
> >>>>
> >>>>SMI datatypes
> >>>>
> >>>>
> >>>>>and textual conventions. If vendors use these consistent XSD=20
> >>>>>translations, then later work to derive standards from the
> >>>>
> >>>>proprietary
> >>>>
> >>>>
> >>>>>information/data models would be easier because there would be=20
> >>>>>increased commonality in the datatypes and textual conventions
> >=20
> > and
> >=20
> >>>>>semantics used to model the information.
> >>>>>
> >>>>>In addition to proprietary data models, there are multiple IETF=20
> >>>>>efforts to translate existing information models (often from=20
> >>>>>ASN.1-based formats) into XML formats.
> >>>>>draft-frascone-xml-dictionary-00 describes the Diameter
> >>>
> >>>"dictionary"
> >>>
> >>>
> >>>>>in XML format; draft-legg-xed-roadmap-06.txt describes
> >=20
> > translating
> >=20
> >>>>>LDAP and X.509 directory information models into semantically=20
> >>>>>equivalent XML renditions of existing directory protocols; IPPM
> >=20
> > is
> >=20
> >>>>>working on an information model in XML for traceroute
> >>>>
> >>>>measurements. So
> >>>>
> >>>>
> >>>>>a MIB-related translation to XML is not unique.
> >>>>>
> >>>>>The XSDMI effort is about taking the MIB, which operators have=20
> >>>>>complained is not well suited to configuration, and translating=20
> >>>>>aspects of the MIB into equivalent XSD. The fact that the MIB=20
> >>>>>datatypes can be translated into XSD will not make the MIB more=20
> >>>>>suitable for configuration; it will simply make reusable=20
> dataypes=20
> >>>>>available in an XML-compatible format.
> >>>>>
> >>>>>The netconf community should be focused on defining a data
> >>>
> >>>modeling
> >>>
> >>>
> >>>>>language and data models for configuration. The YANG=20
> approach for=20
> >>>>>netconf focuses not only on configuration, but also on developing
> >>>
> >>>an
> >>>
> >>>
> >>>>>information modeling language which can then be used by tools to=20
> >>>>>generate syntax-specific data models for a variety of purposes,
> >>>
> >>>such
> >>>
> >>>
> >>>>>as Netconf-suitable XSD data models, SNMP-suitable MIB modules,
> >>>
> >>>plus
> >>>
> >>>
> >>>>>data models for other modeling systems. I have a concern
> >>>>
> >>>>that the SNMP
> >>>>
> >>>>
> >>>>>community has not been asking for this approach, and the IETF
> >>>
> >>>failed
> >>>
> >>>
> >>>>>to reach consensus on the need for the information-modeling
> >>>
> >>>approach
> >>>
> >>>
> >>>>>when it was presented to the SMING WG. If the=20
> >>>>>information-model-generates-data-models approach is adopted by
> >=20
> > the
> >=20
> >>>>>IETF, then does that mean that efforts to use XML-based data
> >>>
> >>>models
> >>>
> >>>
> >>>>>for ipfix, Diameter, IPPM, and LDAP should not be permitted
> >>>>
> >>>>until YANG
> >>>>
> >>>>
> >>>>>can determine how to generate those data models as well?
> >>>>>
> >>>>>Just to be clear, I support the YANG effort because I
> >>>>
> >>>>believe it could
> >>>>
> >>>>
> >>>>>lead to better consistency of data modeling across protocols, but
> >>>
> >>>it
> >>>
> >>>
> >>>>>has yet to be proven to be viable, and other efforts to converge
> >>>
> >>>or
> >>>
> >>>
> >>>>>harmonize data models have had mixed success at best. We should
> >>>
> >>>not
> >>>
> >>>
> >>>>>put all our eggs into one basket. If the YANG approach proves to
> >>>
> >>>be
> >>>
> >>>
> >>>>>viable, then the XSDMI translations can be modified as
> >>>>
> >>>>needed to work
> >>>>
> >>>>
> >>>>>with YANG in the future. But XSDMI could give us XSD=20
> datatypes to=20
> >>>>>develop data models, possibly years before consensus on YANG will
> >>>
> >>>be
> >>>
> >>>
> >>>>>achieved.
> >>>>>
> >>>>>I believe the XSDMI effort should be an OPS-area effort (indeed
> >=20
> > an
> >=20
> >>>>>IETF-wide effort), focused in the OPSAWG, to allow the
> >>>>
> >>>>representation
> >>>>
> >>>>
> >>>>>and translation into XML idiom of the existing=20
> datatypes, textual=20
> >>>>>conventions, and semantic models defined in 15 years of work by=20
> >>>>>multiple working groups and multiple areas of the IETF.
> >>>>>
> >>>>>David Harrington
> >>>>>dbharrington@comcast.net
> >>>>>ietfdbh@comcast.net
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>_______________________________________________
> >>>>>OPSAWG mailing list
> >>>>>OPSAWG@ietf.org
> >>>>>https://www1.ietf.org/mailman/listinfo/opsawg
> >>>>>
> >>>>
> >>>
> >>>
> >=20
> >=20
> >=20
>=20
>=20
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www1.ietf.org/mailman/listinfo/opsawg
>=20


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 02 12:56:42 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Inzoe-0003L8-9o; Fri, 02 Nov 2007 12:56:16 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Inzod-0003L1-E4
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 02 Nov 2007 12:56:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Inzod-0003Kj-2t
	for opsawg@ietf.org; Fri, 02 Nov 2007 12:56:15 -0400
Received: from mail.globalsuite.net ([69.46.103.200])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1InzoR-0005Dx-7o
	for opsawg@ietf.org; Fri, 02 Nov 2007 12:56:15 -0400
X-AuditID: c0a8013c-aadbabb0000032fe-75-472b5697c3a8
Received: from Harrington73653 (streamline120.sjccnet.com [207.87.51.120])
	by mail.globalsuite.net (Symantec Mail Security) with ESMTP id
	A09F34DC002; Fri,  2 Nov 2007 10:55:50 -0600 (MDT)
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>,
	"'Ron Bonica'" <rbonica@juniper.net>
References: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com><472A2A7E.7090401@juniper.net><05a401c81cde$06d6d880$3f8011ac@china.huawei.com><472A8039.2030903@juniper.net><05ba01c81d26$62769340$3f8011ac@china.huawei.com>
	<472B3C3D.4000903@juniper.net>
	<EDC652A26FB23C4EB6384A4584434A045AA037@307622ANEX5.global.avaya.com>
Subject: RE: [OPSAWG] XSDMI
Date: Fri, 2 Nov 2007 09:55:32 -0700
Message-ID: <061d01c81d71$2f6c8450$3f8011ac@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A045AA037@307622ANEX5.global.avaya.com>
Thread-Index: AcgdYi38CQlUXaC5QjW47gIuoNaygwAAO0EgAAGwL3A=
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 9361ae25efd9cff62e36f70ef966350e
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Hi,

Sure, I think an applicability statement is a good idea. Note that the
document is not allowed to mention anything about being a standard, or
imply being a standard: 

"  The Internet-Draft should neither state nor imply that it has any
   standards status; to do so conflicts with the role of the RFC
Editor
   and the IESG.  The title of the document should not imply a status.
   Avoid the use of the terms Standard, Proposed, Draft, Experimental,
   Historic, Required, Recommended, Elective, or Restricted in the
title
   of the Internet-Draft.  Indicating what status the document is
aimed
   for is OK, but should be done with the words "Intended status:
   <status>".

So, is the following text acceptable, or does this imply standards
status?

"This memo describes how to translate from SMIv2 constructs to
XML-based formats. This memo does not mandate the use of this
translation by any particular protocol or application."

dbh

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] 
> Sent: Friday, November 02, 2007 8:23 AM
> To: Ron Bonica; David Harrington
> Cc: opsawg@ietf.org
> Subject: RE: [OPSAWG] XSDMI
> 
> The standards track RFC should be clear about its 
> applicability. In this
> case the applicability should be clearly limited to the translation
> between existing SMIv2 data types and TCs  in into XML data models
> expressed in XSD. It does not mandate usage of a certain protocol,
> protocols using XML can use anything else than XSD, and even 
> when using
> XSD they can define their own data structures using other tools. 
> 
> In other words, the standard should be about 'how to 
> translate from A to
> B', it's not about mandating the usage of B. 
> 
> Dan
> 
> 
>  
>  
> 
> > -----Original Message-----
> > From: Ron Bonica [mailto:rbonica@juniper.net] 
> > Sent: Friday, November 02, 2007 5:03 PM
> > To: David Harrington
> > Cc: opsawg@ietf.org
> > Subject: Re: [OPSAWG] XSDMI
> > 
> > 
> >   Why?
> > 
> >   Doesn't the existence of a standards track RFC mandate that 
> > people use the XSDMI mappings? Isn't that exactly the mandate 
> > that we are trying to avoid?
> > 
> >                                     Ron
> > 
> > 
> > David Harrington wrote:
> > > I believe XSDMI should generate standards-track documents, not 
> > > Informational documents.
> > > 
> > > dbh
> > > 
> > > 
> > >>-----Original Message-----
> > >>From: Ron Bonica [mailto:rbonica@juniper.net]
> > >>Sent: Thursday, November 01, 2007 6:41 PM
> > >>To: David Harrington
> > >>Cc: opsawg@ietf.org
> > >>Subject: Re: [OPSAWG] XSDMI
> > >>
> > >>David,
> > >>
> > >>Are there any aspects of the proposal that you would like 
> > to change? 
> > >>Or are we in violent agreement?
> > >>
> > >>                                Ron
> > >>
> > >>
> > >>David Harrington wrote:
> > >>
> > >>>Hi,
> > >>>
> > >>>The goal of XSDMI is to provide a standard translation of SMI 
> > >>>datatypes, textual conventions, and macros into XML family
> > > 
> > > formats,
> > > 
> > >>>such as XSD.
> > >>>
> > >>>I have said this over and over: There has never been any
> > >>
> > >>intention on
> > >>
> > >>>my part to mandate that any XML-based protocol, 
> including Netconf, 
> > >>>MUST use the XSD output from the XSDMI translations. These 
> > >>>translatinos are being provided to **enable and encourage**
reuse
> > > 
> > > of
> > > 
> > >>>SMIv2 datatypes and textual conventions in XML-based
> > >>
> > >>protocols, and to
> > >>
> > >>>provide XML-based support for SMIv2 macros to encourage reuse
of
> > > 
> > > the
> > > 
> > >>>MIB data models (schemas) in XML-capable management
applications
> > > 
> > > and
> > > 
> > >>>databases.
> > >>>
> > >>>It is purely a Netconf decision whether to reuse these datatype

> > >>>translations, just as it would be purely a "foo" 
> protocol decision 
> > >>>whether the datatypes were appropriate for reuse in the "foo"
> > >>>environment. The XSDMI work is totally independent of the work
> > > 
> > > being
> > > 
> > >>>done by and for the Netconf community.
> > >>>
> > >>>Perasnally, I expect that the data modeling needed for
> > > 
> > > configuration
> > > 
> > >>>will require things that SMIv2 does not have - the ability to 
> > >>>distinguish config data from state data, the ability to specify
> > > 
> > > data
> > > 
> > >>>from the candidate datastore vs that from the running or
startup 
> > >>>datastores, nested data structures, standardized methods, etc.
> > > 
> > > SMIv2
> > > 
> > >>>MIBs and the XSD equivalents cannot do this! 
> > >>>
> > >>>I think it unlikely that the XSD output from a Netconf-specific

> > >>>effort, such as YANG, will match the XSD output from the
> > >>
> > >>XSDMI effort,
> > >>
> > >>>because if it did then it could be argued that there is 
> no need to 
> > >>>move to a new data modeling language, only the need to
> > >>
> > >>translate SMIv2
> > >>
> > >>>into XML-based formats. XML and XSD do not enable better 
> > >>>configuration; a configuration-focused protocol and 
> > >>>configuration-focused data models will do that. I consider it 
> > >>>appropriate that the data models from the SMIv2 MIB and the
data 
> > >>>models designed for Netcof configuration not match because they
> > > 
> > > are
> > > 
> > >>>designed to serve different purposes. 
> > >>>
> > >>>The data models that already exist for SNMP and syslog and
> > >>
> > >>RADIUS and
> > >>
> > >>>Diameter and IPFIX do not match, because they serve
> > >>
> > >>different purposes
> > >>
> > >>>and contain different modeling information, even though they
are
> > > 
> > > all
> > > 
> > >>>related to network management. The data model encodings
> > >>
> > >>used for MIBs
> > >>
> > >>>and LDAP search filters and X.509 certificates differ 
> because they 
> > >>>serve different purposes, even though they all use ASN.1
> > >>
> > >>encoding. The
> > >>
> > >>>netconf data models and their encodings SHOULD differ from the 
> > >>>SNMP/MIB data models because the information that we need
> > >>
> > >>to model and
> > >>
> > >>>to encode on the wire for these different purposes and
different 
> > >>>protocols is different.
> > >>>
> > >>>I do not feel that publishing the XSDMI translations as
> > >>
> > >>Informational
> > >>
> > >>>is called for. This work is **independent** of Netconf.
> > >>>
> > >>>The goal of XSDMI is to provide a **standard** 
> translation of SMI 
> > >>>datatypes, textual conventions, and macros into XML family
> > > 
> > > formats,
> > > 
> > >>>such as XSD, so other protocols can **choose** to use
compatible 
> > >>>datatypes, and have a standard interoperable translation
already 
> > >>>available so they don't have to do the translation
> > >>
> > >>themselves, and so
> > >>
> > >>>the standard translations can be done by people who really
> > >>
> > >>understand
> > >>
> > >>>the purpose and constraints of the SMIv2 datatypes and textual 
> > >>>conventions and macros.
> > >>>
> > >>>It has **never** been my intention that people should be
> > >>
> > >>**forced** to
> > >>
> > >>>use these translated datatypes, textual conventions, and macros
> > > 
> > > with
> > > 
> > >>>other protocols, only that we would make it easier for them to
do
> > > 
> > > so
> > > 
> > >>>if they wanted to, and to promote interoperability by 
> giving them 
> > >>>standard translations they could use.
> > >>>
> > >>>David Harrington
> > >>>dbharrington@comcast.net
> > >>>ietfdbh@comcast.net
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>>-----Original Message-----
> > >>>>From: Ron Bonica [mailto:rbonica@juniper.net]
> > >>>>Sent: Thursday, November 01, 2007 12:35 PM
> > >>>>To: David Harrington
> > >>>>Cc: opsawg@ietf.org
> > >>>>Subject: Re: [OPSAWG] XSDMI
> > >>>>
> > >>>>Hi David,
> > >>>>
> > >>>>The following is a possible compromise:
> > >>>>
> > >>>>David progresses the XSDMI work in the OPS Area WG. Although
the
> > > 
> > > XSD
> > > 
> > >>>>produced by XSDMI is made available to everyone, there is 
> > no mandate 
> > >>>>to use it. This means that it the NETCONF community 
> decides that 
> > >>>>XSDMI does not fulfill their requirements, they will be free
to 
> > >>>>specify something else.
> > >>>>
> > >>>>All drafts progressed as XSDMI will be submitted for
publication
> > > 
> > > as
> > > 
> > >>>>INFORMATIONAL.
> > >>>>
> > >>>>Comments?
> > >>>>
> > >>>>                             Ron
> > >>>>
> > >>>>
> > >>>>David Harrington wrote:
> > >>>>
> > >>>>
> > >>>>>Hi,
> > >>>>>
> > >>>>>Juergen has raised the issue that the XSD produced by the
> > >>>>
> > >>>>XDMI effort
> > >>>>
> > >>>>
> > >>>>>and the XSD produced by the YANG effort might be different,
> > >>>>
> > >>>>and having
> > >>>>
> > >>>>
> > >>>>>two different XSD equivalents for MIB datatypes would be
> > >>>>
> > >>>>suboptimal. I
> > >>>>
> > >>>>
> > >>>>>agree.
> > >>>>>
> > >>>>>However, I have the concern that while vendors wait for YANG
to
> > > 
> > > be
> > > 
> > >>>>>completed, they will need to develop proprietary data 
> models for
> > >>>
> > >>>use
> > >>>
> > >>>
> > >>>>>with netconf. Some vendors will want to reuse 
> datatypes found in
> > >>>
> > >>>the
> > >>>
> > >>>
> > >>>>>15 year compilation of IETF NM experience found in the
standard
> > >>>
> > >>>MIB
> > >>>
> > >>>
> > >>>>>modules, and supported by existing implementation code. If
they
> > >>>
> > >>>need
> > >>>
> > >>>
> > >>>>>to develop their own translations of existing SMI 
> datatypes and 
> > >>>>>textual conventions into XSD and XML, we could wind up with
> > >>>>
> > >>>>a variety
> > >>>>
> > >>>>
> > >>>>>of competing XSD specifications. 
> > >>>>>
> > >>>>>The XSDMI work would provide reusable XSD equivalents of
> > >>>>
> > >>>>SMI datatypes
> > >>>>
> > >>>>
> > >>>>>and textual conventions. If vendors use these consistent XSD 
> > >>>>>translations, then later work to derive standards from the
> > >>>>
> > >>>>proprietary
> > >>>>
> > >>>>
> > >>>>>information/data models would be easier because there would
be 
> > >>>>>increased commonality in the datatypes and textual
conventions
> > > 
> > > and
> > > 
> > >>>>>semantics used to model the information.
> > >>>>>
> > >>>>>In addition to proprietary data models, there are 
> multiple IETF 
> > >>>>>efforts to translate existing information models (often from 
> > >>>>>ASN.1-based formats) into XML formats.
> > >>>>>draft-frascone-xml-dictionary-00 describes the Diameter
> > >>>
> > >>>"dictionary"
> > >>>
> > >>>
> > >>>>>in XML format; draft-legg-xed-roadmap-06.txt describes
> > > 
> > > translating
> > > 
> > >>>>>LDAP and X.509 directory information models into semantically

> > >>>>>equivalent XML renditions of existing directory protocols;
IPPM
> > > 
> > > is
> > > 
> > >>>>>working on an information model in XML for traceroute
> > >>>>
> > >>>>measurements. So
> > >>>>
> > >>>>
> > >>>>>a MIB-related translation to XML is not unique.
> > >>>>>
> > >>>>>The XSDMI effort is about taking the MIB, which operators
have 
> > >>>>>complained is not well suited to configuration, and 
> translating 
> > >>>>>aspects of the MIB into equivalent XSD. The fact that the MIB

> > >>>>>datatypes can be translated into XSD will not make the 
> MIB more 
> > >>>>>suitable for configuration; it will simply make reusable 
> > dataypes 
> > >>>>>available in an XML-compatible format.
> > >>>>>
> > >>>>>The netconf community should be focused on defining a data
> > >>>
> > >>>modeling
> > >>>
> > >>>
> > >>>>>language and data models for configuration. The YANG 
> > approach for 
> > >>>>>netconf focuses not only on configuration, but also on 
> developing
> > >>>
> > >>>an
> > >>>
> > >>>
> > >>>>>information modeling language which can then be used 
> by tools to 
> > >>>>>generate syntax-specific data models for a variety of
purposes,
> > >>>
> > >>>such
> > >>>
> > >>>
> > >>>>>as Netconf-suitable XSD data models, SNMP-suitable MIB
modules,
> > >>>
> > >>>plus
> > >>>
> > >>>
> > >>>>>data models for other modeling systems. I have a concern
> > >>>>
> > >>>>that the SNMP
> > >>>>
> > >>>>
> > >>>>>community has not been asking for this approach, and the IETF
> > >>>
> > >>>failed
> > >>>
> > >>>
> > >>>>>to reach consensus on the need for the information-modeling
> > >>>
> > >>>approach
> > >>>
> > >>>
> > >>>>>when it was presented to the SMING WG. If the 
> > >>>>>information-model-generates-data-models approach is adopted
by
> > > 
> > > the
> > > 
> > >>>>>IETF, then does that mean that efforts to use XML-based data
> > >>>
> > >>>models
> > >>>
> > >>>
> > >>>>>for ipfix, Diameter, IPPM, and LDAP should not be permitted
> > >>>>
> > >>>>until YANG
> > >>>>
> > >>>>
> > >>>>>can determine how to generate those data models as well?
> > >>>>>
> > >>>>>Just to be clear, I support the YANG effort because I
> > >>>>
> > >>>>believe it could
> > >>>>
> > >>>>
> > >>>>>lead to better consistency of data modeling across 
> protocols, but
> > >>>
> > >>>it
> > >>>
> > >>>
> > >>>>>has yet to be proven to be viable, and other efforts 
> to converge
> > >>>
> > >>>or
> > >>>
> > >>>
> > >>>>>harmonize data models have had mixed success at best. We
should
> > >>>
> > >>>not
> > >>>
> > >>>
> > >>>>>put all our eggs into one basket. If the YANG approach 
> proves to
> > >>>
> > >>>be
> > >>>
> > >>>
> > >>>>>viable, then the XSDMI translations can be modified as
> > >>>>
> > >>>>needed to work
> > >>>>
> > >>>>
> > >>>>>with YANG in the future. But XSDMI could give us XSD 
> > datatypes to 
> > >>>>>develop data models, possibly years before consensus 
> on YANG will
> > >>>
> > >>>be
> > >>>
> > >>>
> > >>>>>achieved.
> > >>>>>
> > >>>>>I believe the XSDMI effort should be an OPS-area effort
(indeed
> > > 
> > > an
> > > 
> > >>>>>IETF-wide effort), focused in the OPSAWG, to allow the
> > >>>>
> > >>>>representation
> > >>>>
> > >>>>
> > >>>>>and translation into XML idiom of the existing 
> > datatypes, textual 
> > >>>>>conventions, and semantic models defined in 15 years 
> of work by 
> > >>>>>multiple working groups and multiple areas of the IETF.
> > >>>>>
> > >>>>>David Harrington
> > >>>>>dbharrington@comcast.net
> > >>>>>ietfdbh@comcast.net
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>_______________________________________________
> > >>>>>OPSAWG mailing list
> > >>>>>OPSAWG@ietf.org
> > >>>>>https://www1.ietf.org/mailman/listinfo/opsawg
> > >>>>>
> > >>>>
> > >>>
> > >>>
> > > 
> > > 
> > > 
> > 
> > 
> > _______________________________________________
> > OPSAWG mailing list
> > OPSAWG@ietf.org
> > https://www1.ietf.org/mailman/listinfo/opsawg
> > 
> 




_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 02 13:24:35 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Io0Fj-0003Pe-P6; Fri, 02 Nov 2007 13:24:15 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Io0Fi-0003P2-Kh
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 02 Nov 2007 13:24:14 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Io0Fi-0003Ou-9x
	for opsawg@ietf.org; Fri, 02 Nov 2007 13:24:14 -0400
Received: from smtp104.sbc.mail.mud.yahoo.com ([68.142.198.203])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1Io0Fh-0006M5-UK
	for opsawg@ietf.org; Fri, 02 Nov 2007 13:24:14 -0400
Received: (qmail 61926 invoked from network); 2 Nov 2007 17:24:13 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@67.127.99.221
	with plain)
	by smtp104.sbc.mail.mud.yahoo.com with SMTP; 2 Nov 2007 17:24:12 -0000
X-YMail-OSG: k5YBqOcVM1kWE4e7STvRtHOEI.3FrPN.f0NcndKFyllpirpV
Message-ID: <472B5D57.6000804@andybierman.com>
Date: Fri, 02 Nov 2007 10:24:39 -0700
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: [OPSAWG] XSDMI
References: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com><472A2A7E.7090401@juniper.net><05a401c81cde$06d6d880$3f8011ac@china.huawei.com><472A8039.2030903@juniper.net><05ba01c81d26$62769340$3f8011ac@china.huawei.com>	<472B3C3D.4000903@juniper.net>
	<EDC652A26FB23C4EB6384A4584434A045AA037@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A045AA037@307622ANEX5.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Romascanu, Dan (Dan) wrote:
> The standards track RFC should be clear about its applicability. In this
> case the applicability should be clearly limited to the translation
> between existing SMIv2 data types and TCs  in into XML data models
> expressed in XSD. It does not mandate usage of a certain protocol,
> protocols using XML can use anything else than XSD, and even when using
> XSD they can define their own data structures using other tools. 
> 
> In other words, the standard should be about 'how to translate from A to
> B', it's not about mandating the usage of B. 
> 

I think an SDO can do better than this.
There is disagreement between the way YANG encodes some SMIv2
data types and the way draft-romascanu does it, particularly
related to IPv4 and IPv6 addresses, duration, and dateTime.
These technical issues should be worked out in the opsawg.

It is important to get alignment on fundamental data types
like these, which will show up over and over in standard
data models.

I want a well-constrained set of standard data types
(encoded in XSD for now), such that if a standards-track
XML data model of any kind uses the data type 'InetAddress'
or any of the other standard named types, that the
standard syntax and semantics will apply.

This problem has nothing to do with SMIv2.
It has to do with standards, and whether or not
we have any for XML data models in the IETF.


> Dan
> 


Andy



_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 02 14:46:06 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Io1WW-0002uF-Am; Fri, 02 Nov 2007 14:45:40 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Io1WU-0002u8-SR
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 02 Nov 2007 14:45:38 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Io1WU-0002td-HO
	for opsawg@ietf.org; Fri, 02 Nov 2007 14:45:38 -0400
Received: from hermes.jacobs-university.de ([212.201.44.23])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Io1WT-0001WD-Uy
	for opsawg@ietf.org; Fri, 02 Nov 2007 14:45:38 -0400
Received: from localhost (demetrius.jacobs-university.de [212.201.44.32])
	by hermes.jacobs-university.de (Postfix) with ESMTP id B0B9F89A6D;
	Fri,  2 Nov 2007 19:45:36 +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 26112-05; Fri,  2 Nov 2007 19:45:32 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133])
	by hermes.jacobs-university.de (Postfix) with ESMTP id CF0186A4CD;
	Fri,  2 Nov 2007 19:45:29 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501)
	id 1211F3C11A1; Fri,  2 Nov 2007 19:45:29 +0100 (CET)
Date: Fri, 2 Nov 2007 19:45:28 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: David Harrington <ietfdbh@comcast.net>
Subject: Re: [OPSAWG] XSDMI
Message-ID: <20071102184528.GB25692@elstar.local>
Mail-Followup-To: David Harrington <ietfdbh@comcast.net>,
	"'Romascanu, Dan (Dan)'" <dromasca@avaya.com>,
	'Ron Bonica' <rbonica@juniper.net>, opsawg@ietf.org
References: <05ba01c81d26$62769340$3f8011ac@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A045A9FFB@307622ANEX5.global.avaya.com>
	<20071102095436.GC1818@elstar.local>
	<05f501c81d5c$2d5808c0$3f8011ac@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <05f501c81d5c$2d5808c0$3f8011ac@china.huawei.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@jacobs-university.de
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

On Fri, Nov 02, 2007 at 07:25:09AM -0700, David Harrington wrote:

> The whole point is that this WG should not be authorized to make the
> decision about which other protocols or which applications will use
> these mappings. No protocols or applications should be required to use
> the XSDMI mappings, and the decision about the applicability of these
> mappings should rest with the developers of any current or future
> protocols or applications that could benefit from their reuse.

I am still wondering how useful is it to develop standards-track
protocol neutral feel free to ignore SMIv2 translations to XSD. It is
unclear to me how this helps to "make the Internet work better"
[BCP95].

If we are really concerned about the proliferation of incompatible
data models, then what really needs to be done is to define a common
way to write up NETCONF data models since proprietary incompatible
languages are already around. Trying to move towards interoperable
standardized configuration was the direction taken a few years ago
after the IAB workshop and so far I believed this goal is still on the
table.

I find it quite irritating that the IETF does not seen ti have the
stamina to address the NETCONF data modeling issue and to complete the
work they have started a few years ago towards XML-based standardized
(configuration) management. And if we talk at the same time about
spending resources on standards-track protocol neutral feel free to
ignore SMIv2 translations to XSD, then this increases my irritation
even more. Perhaps the IETF network management "area" has lost
direction.

/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/>


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 02 15:17:34 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Io20o-0002ch-4q; Fri, 02 Nov 2007 15:16:58 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Io20m-0002cY-7b
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 02 Nov 2007 15:16:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Io20l-0002cQ-SP
	for opsawg@ietf.org; Fri, 02 Nov 2007 15:16:55 -0400
Received: from smtp121.sbc.mail.sp1.yahoo.com ([69.147.64.94])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1Io20l-000316-AT
	for opsawg@ietf.org; Fri, 02 Nov 2007 15:16:55 -0400
Received: (qmail 18622 invoked from network); 2 Nov 2007 19:16:53 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@67.127.99.221
	with plain)
	by smtp121.sbc.mail.sp1.yahoo.com with SMTP; 2 Nov 2007 19:16:53 -0000
X-YMail-OSG: uiOOX.AVM1nwv5reRT.7JYmzKyJawiN4m2DTJq_UZhuf.7rH
Message-ID: <472B77D1.5050103@andybierman.com>
Date: Fri, 02 Nov 2007 12:17:37 -0700
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>, 
	"'Romascanu, Dan (Dan)'" <dromasca@avaya.com>,
	'Ron Bonica' <rbonica@juniper.net>,  opsawg@ietf.org
Subject: Re: [OPSAWG] XSDMI
References: <05ba01c81d26$62769340$3f8011ac@china.huawei.com>	<EDC652A26FB23C4EB6384A4584434A045A9FFB@307622ANEX5.global.avaya.com>	<20071102095436.GC1818@elstar.local>	<05f501c81d5c$2d5808c0$3f8011ac@china.huawei.com>
	<20071102184528.GB25692@elstar.local>
In-Reply-To: <20071102184528.GB25692@elstar.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: 
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Juergen Schoenwaelder wrote:
> On Fri, Nov 02, 2007 at 07:25:09AM -0700, David Harrington wrote:
> 
>> The whole point is that this WG should not be authorized to make the
>> decision about which other protocols or which applications will use
>> these mappings. No protocols or applications should be required to use
>> the XSDMI mappings, and the decision about the applicability of these
>> mappings should rest with the developers of any current or future
>> protocols or applications that could benefit from their reuse.
> 
> I am still wondering how useful is it to develop standards-track
> protocol neutral feel free to ignore SMIv2 translations to XSD. It is
> unclear to me how this helps to "make the Internet work better"
> [BCP95].
> 

In the general sense I agree with you.
But in this case, a set of protocol-neutral data types
is useful and possible.

IMO, if an XML data model uses a data type called Counter32,
it should be the same Counter32 we already know in the IETF.
I never said the data model must use Counter32 instead of MyCounter
or whatever.

There is a set of protocol neutral data types within draft-romascanu,
plus some SNMP-centric stuff that could be separated out.
There is nothing NETCONF-specific about an IP address.


> If we are really concerned about the proliferation of incompatible
> data models, then what really needs to be done is to define a common
> way to write up NETCONF data models since proprietary incompatible
> languages are already around. Trying to move towards interoperable
> standardized configuration was the direction taken a few years ago
> after the IAB workshop and so far I believed this goal is still on the
> table.
> 
> I find it quite irritating that the IETF does not seen ti have the
> stamina to address the NETCONF data modeling issue and to complete the
> work they have started a few years ago towards XML-based standardized
> (configuration) management. And if we talk at the same time about
> spending resources on standards-track protocol neutral feel free to
> ignore SMIv2 translations to XSD, then this increases my irritation
> even more. Perhaps the IETF network management "area" has lost
> direction.

I think the area is proceeding slowly, that's all.

I would like these core data types to be in alignment
with the YANG versions (pick one or the other), decided
on a case-by-base basis.



> 
> /js
> 

Andy



_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 02 15:24:44 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Io289-0006rr-Be; Fri, 02 Nov 2007 15:24:33 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Io287-0006rB-Pa
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 02 Nov 2007 15:24:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Io287-0006qh-Em
	for opsawg@ietf.org; Fri, 02 Nov 2007 15:24:31 -0400
Received: from elasmtp-dupuy.atl.sa.earthlink.net ([209.86.89.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Io287-0003GN-1t
	for opsawg@ietf.org; Fri, 02 Nov 2007 15:24:31 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=dk20050327; d=mindspring.com;
	b=d+FbyKheOExpInOSVZZznA9LptE05nVBUp40Bfyl9Z4IXvGZWshXWo0F8wTt0qVN;
	h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [68.166.189.246] (helo=oemcomputer)
	by elasmtp-dupuy.atl.sa.earthlink.net with asmtp (Exim 4.34)
	id 1Io286-0000Xt-Fa
	for opsawg@ietf.org; Fri, 02 Nov 2007 15:24:30 -0400
Message-ID: <001301c81d8e$7c21a380$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <opsawg@ietf.org>
References: <05ba01c81d26$62769340$3f8011ac@china.huawei.com><EDC652A26FB23C4EB6384A4584434A045A9FFB@307622ANEX5.global.avaya.com><20071102095436.GC1818@elstar.local><05f501c81d5c$2d5808c0$3f8011ac@china.huawei.com>
	<20071102184528.GB25692@elstar.local>
Subject: Re: [OPSAWG] XSDMI
Date: Fri, 2 Nov 2007 12:25:17 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888a4beb055f130b31a1b62c48272cc5a472100bf1e42842cf6350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.166.189.246
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Hi -

> From: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
> To: "David Harrington" <ietfdbh@comcast.net>
> Cc: <opsawg@ietf.org>
> Sent: Friday, November 02, 2007 10:45 AM
> Subject: Re: [OPSAWG] XSDMI
...
> If we are really concerned about the proliferation of incompatible
> data models, then what really needs to be done is to define a common
> way to write up NETCONF data models since proprietary incompatible
> languages are already around. Trying to move towards interoperable
> standardized configuration was the direction taken a few years ago
> after the IAB workshop and so far I believed this goal is still on the
> table.
> 
> I find it quite irritating that the IETF does not seen ti have the
> stamina to address the NETCONF data modeling issue and to complete the
> work they have started a few years ago towards XML-based standardized
> (configuration) management. And if we talk at the same time about
> spending resources on standards-track protocol neutral feel free to
> ignore SMIv2 translations to XSD, then this increases my irritation
> even more. Perhaps the IETF network management "area" has lost
> direction.
...

Perhaps I've misunderstood what has been said in WG meetings (it's
been a while since I've attended a face-to-face meeting) and on the
mailing lists.  My impression has been that, despite everything said in
the IAB workshop, the IETF direction for new work has been to
abandon any kind of common modeling approach in favor of CLI
masquerading as XML, and that, consequently, any attempt to provide
real data modeling standardization with any "teeth" in its applicability
won't get anywhere.  The current situation seems to be to favor the least
"threatening" of the proposals.  Perhaps the tacit assumption is that once
it's in place, it will prevent the others from taking hold.  But perhaps I've
been away too long and have merely become overly cynical.

Randy



_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 02 15:50:57 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Io2X7-0006MO-T4; Fri, 02 Nov 2007 15:50:21 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Io2X6-0006MF-Rl
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 02 Nov 2007 15:50:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Io2X6-0006M6-I5
	for opsawg@ietf.org; Fri, 02 Nov 2007 15:50:20 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Io2X0-0004ES-DN
	for opsawg@ietf.org; Fri, 02 Nov 2007 15:50:20 -0400
X-IronPort-AV: E=Sophos;i="4.21,363,1188792000"; d="scan'208";a="80446501"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by co300216-co-outbound.avaya.com with ESMTP; 02 Nov 2007 15:50:08 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [OPSAWG] XSDMI
Date: Fri, 2 Nov 2007 20:49:26 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A045AA051@307622ANEX5.global.avaya.com>
In-Reply-To: <472B77D1.5050103@andybierman.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] XSDMI
Thread-Index: AcgdhQSfHXpSBeRSTRqU2Hb6xxTu1gABAtdg
References: <05ba01c81d26$62769340$3f8011ac@china.huawei.com>	<EDC652A26FB23C4EB6384A4584434A045A9FFB@307622ANEX5.global.avaya.com>	<20071102095436.GC1818@elstar.local>	<05f501c81d5c$2d5808c0$3f8011ac@china.huawei.com>
	<20071102184528.GB25692@elstar.local>
	<472B77D1.5050103@andybierman.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Andy Bierman" <ietf@andybierman.com>,
	"David Harrington" <ietfdbh@comcast.net>,
	"Ron Bonica" <rbonica@juniper.net>, <opsawg@ietf.org>
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: 
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org



=20
=20

> -----Original Message-----
> From: Andy Bierman [mailto:ietf@andybierman.com]=20
>=20
> I would like these core data types to be in alignment with=20
> the YANG versions (pick one or the other), decided on a=20
> case-by-base basis.
>=20

Yes, but we need to have the yang data types published as Internet-Draft
to be able to entertain this discussion. Until then it is not clear to
me what is the degree of (mis)-alignment that we are talking about.=20

Dan


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 02 15:55:40 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Io2cG-0000df-LM; Fri, 02 Nov 2007 15:55:40 -0400
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Io2cF-0000bZ-3E
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 02 Nov 2007 15:55:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Io2cE-0000bR-Po
	for opsawg@ietf.org; Fri, 02 Nov 2007 15:55:38 -0400
Received: from [198.152.12.100] (helo=nj300815-nj-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Io2c8-0004Ok-0P
	for opsawg@ietf.org; Fri, 02 Nov 2007 15:55:38 -0400
X-IronPort-AV: E=Sophos;i="4.21,363,1188792000"; d="scan'208";a="75654561"
Received: from 14.140.8.135.in-addr.arpa (HELO 307622ANEX5.global.avaya.com)
	([135.64.140.14])
	by nj300815-nj-outbound.avaya.com with ESMTP; 02 Nov 2007 15:54:45 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [OPSAWG] XSDMI
Date: Fri, 2 Nov 2007 20:54:24 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A045AA054@307622ANEX5.global.avaya.com>
In-Reply-To: <20071102184528.GB25692@elstar.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] XSDMI
Thread-Index: AcgdgJyotedELhNPTCCkd2GdnA/nnQACPjUQ
References: <05ba01c81d26$62769340$3f8011ac@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A045A9FFB@307622ANEX5.global.avaya.com>
	<20071102095436.GC1818@elstar.local>
	<05f501c81d5c$2d5808c0$3f8011ac@china.huawei.com>
	<20071102184528.GB25692@elstar.local>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <j.schoenwaelder@jacobs-university.de>,
	"David Harrington" <ietfdbh@comcast.net>
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org



=20
=20

> -----Original Message-----
> From: Juergen Schoenwaelder=20
> [mailto:j.schoenwaelder@jacobs-university.de]=20
> Sent: Friday, November 02, 2007 8:45 PM
> To: David Harrington
> Cc: Romascanu, Dan (Dan); 'Ron Bonica'; opsawg@ietf.org
> Subject: Re: [OPSAWG] XSDMI
>=20
> On Fri, Nov 02, 2007 at 07:25:09AM -0700, David Harrington wrote:
>=20
> > The whole point is that this WG should not be authorized to=20
> make the=20
> > decision about which other protocols or which applications will use=20
> > these mappings. No protocols or applications should be=20
> required to use=20
> > the XSDMI mappings, and the decision about the=20
> applicability of these=20
> > mappings should rest with the developers of any current or future=20
> > protocols or applications that could benefit from their reuse.
>=20
> I am still wondering how useful is it to develop=20
> standards-track protocol neutral feel free to ignore SMIv2=20
> translations to XSD. It is unclear to me how this helps to=20
> "make the Internet work better"
> [BCP95].
>=20

It's not about ignoring but about not mandating. Isn't this the same
architectural principle of not coupling tightly the protocol and the
data modeling language that is in place with SNMP as well? Even SMIv2 is
supposed to be able to work with protocols other than SNMP.=20

Dan


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Mon Nov 05 15:12:26 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ip8J7-00005q-7k; Mon, 05 Nov 2007 15:12:25 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Ip8J6-0008Ua-30
	for opsawg-confirm+ok@megatron.ietf.org; Mon, 05 Nov 2007 15:12:24 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ip8J1-0008P4-5a
	for opsawg@ietf.org; Mon, 05 Nov 2007 15:12:19 -0500
Received: from exprod7og110.obsmtp.com ([64.18.2.173])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ip8J0-0001VL-Oq
	for opsawg@ietf.org; Mon, 05 Nov 2007 15:12:19 -0500
Received: from source ([66.129.224.36]) by exprod7ob110.postini.com
	([64.18.6.12]) with SMTP; Mon, 05 Nov 2007 12:11:17 PST
Received: from proton.jnpr.net ([10.10.2.37]) by emailsmtp56.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959); Mon, 5 Nov 2007 12:12:11 -0800
Received: from [172.23.1.35] ([172.23.1.35] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Nov 2007 15:12:09 -0500
Message-ID: <472F7916.4070102@juniper.net>
Date: Mon, 05 Nov 2007 15:12:06 -0500
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
Subject: Re: [OPSAWG] XSDMI
References: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com><472A2A7E.7090401@juniper.net><05a401c81cde$06d6d880$3f8011ac@china.huawei.com><472A8039.2030903@juniper.net><05ba01c81d26$62769340$3f8011ac@china.huawei.com>
	<472B3C3D.4000903@juniper.net>
	<EDC652A26FB23C4EB6384A4584434A045AA037@307622ANEX5.global.avaya.com>
	<061d01c81d71$2f6c8450$3f8011ac@china.huawei.com>
In-Reply-To: <061d01c81d71$2f6c8450$3f8011ac@china.huawei.com>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Nov 2007 20:12:09.0856 (UTC)
	FILETIME=[254A5000:01C81FE8]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org


> 
> So, is the following text acceptable, or does this imply standards
> status?
> 
> "This memo describes how to translate from SMIv2 constructs to
> XML-based formats. This memo does not mandate the use of this
> translation by any particular protocol or application."
> 
> dbh


Hi David,

It seems to mee that PS status is at odds with this applicability
statement. If the memo does not mandate use, why does the memo need to
be PS?


                                  Ron





_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Mon Nov 05 16:04:44 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ip97k-0006jU-96; Mon, 05 Nov 2007 16:04:44 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Ip97i-0006iY-7G
	for opsawg-confirm+ok@megatron.ietf.org; Mon, 05 Nov 2007 16:04:42 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ip97h-0006iQ-TL
	for opsawg@ietf.org; Mon, 05 Nov 2007 16:04:41 -0500
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ip97h-0003LT-JT
	for opsawg@ietf.org; Mon, 05 Nov 2007 16:04:41 -0500
X-IronPort-AV: E=Sophos;i="4.21,374,1188792000"; d="scan'208";a="76234099"
Received: from 5.7.8.135.in-addr.arpa (HELO co300216-co-erhwest.avaya.com)
	([198.152.7.5])
	by nj300815-nj-outbound.avaya.com with ESMTP; 05 Nov 2007 16:04:40 -0500
X-IronPort-AV: E=Sophos;i="4.21,374,1188792000"; d="scan'208";a="128045821"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	05 Nov 2007 16:04:40 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [OPSAWG] XSDMI
Date: Mon, 5 Nov 2007 22:04:39 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A045AA725@307622ANEX5.global.avaya.com>
In-Reply-To: <472F7916.4070102@juniper.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] XSDMI
Thread-Index: Acgf6DbZ35o2dFG5TDia7P8KmbI0XwABxm6w
References: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com><472A2A7E.7090401@juniper.net><05a401c81cde$06d6d880$3f8011ac@china.huawei.com><472A8039.2030903@juniper.net><05ba01c81d26$62769340$3f8011ac@china.huawei.com>
	<472B3C3D.4000903@juniper.net>
	<EDC652A26FB23C4EB6384A4584434A045AA037@307622ANEX5.global.avaya.com>
	<061d01c81d71$2f6c8450$3f8011ac@china.huawei.com>
	<472F7916.4070102@juniper.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Ron Bonica" <rbonica@juniper.net>,
	"David Harrington" <ietfdbh@comcast.net>
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org



=20
=20

> -----Original Message-----
> From: Ron Bonica [mailto:rbonica@juniper.net]=20
> Sent: Monday, November 05, 2007 10:12 PM
> To: David Harrington
> Cc: Romascanu, Dan (Dan); opsawg@ietf.org
> Subject: Re: [OPSAWG] XSDMI
>=20
>=20
> >=20
> > So, is the following text acceptable, or does this imply standards=20
> > status?
> >=20
> > "This memo describes how to translate from SMIv2 constructs to=20
> > XML-based formats. This memo does not mandate the use of this=20
> > translation by any particular protocol or application."
> >=20
> > dbh
>=20
>=20
> Hi David,
>=20
> It seems to mee that PS status is at odds with this=20
> applicability statement. If the memo does not mandate use,=20
> why does the memo need to be PS?
>=20
>=20
>                                   Ron
>=20
>=20

Because what is standardized is the method of translation, not the usage
of the result of the translation.=20

Dan


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Tue Nov 06 11:44:07 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IpRX5-0002eR-6O; Tue, 06 Nov 2007 11:44:07 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IpRX3-0002Zi-6w
	for opsawg-confirm+ok@megatron.ietf.org; Tue, 06 Nov 2007 11:44:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IpRWy-0002Tq-Ar
	for opsawg@ietf.org; Tue, 06 Nov 2007 11:44:00 -0500
Received: from exprod7og104.obsmtp.com ([64.18.2.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IpRWu-0000Rl-SL
	for opsawg@ietf.org; Tue, 06 Nov 2007 11:44:00 -0500
Received: from source ([66.129.224.36]) by exprod7ob104.postini.com
	([64.18.6.12]) with SMTP; Tue, 06 Nov 2007 08:43:12 PST
Received: from proton.jnpr.net ([10.10.2.37]) by gamma.jnpr.net with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 6 Nov 2007 08:43:21 -0800
Received: from [172.23.1.35] ([172.23.1.35] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Nov 2007 11:43:18 -0500
Message-ID: <473099A3.4060402@juniper.net>
Date: Tue, 06 Nov 2007 11:43:15 -0500
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: [OPSAWG] XSDMI
References: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com><472A2A7E.7090401@juniper.net><05a401c81cde$06d6d880$3f8011ac@china.huawei.com><472A8039.2030903@juniper.net><05ba01c81d26$62769340$3f8011ac@china.huawei.com>
	<472B3C3D.4000903@juniper.net>
	<EDC652A26FB23C4EB6384A4584434A045AA037@307622ANEX5.global.avaya.com>
	<061d01c81d71$2f6c8450$3f8011ac@china.huawei.com>
	<472F7916.4070102@juniper.net>
	<EDC652A26FB23C4EB6384A4584434A045AA725@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A045AA725@307622ANEX5.global.avaya.com>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Nov 2007 16:43:19.0118 (UTC)
	FILETIME=[22CD2EE0:01C82094]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Dan,

I don't think that I am convinced. But rather than occupying the WG with
this debate, why don't we just proceed with the work. When the memo is
ready for publication, we can revisit the document status issue with the
benefit of some additional experience under our belts.

At that time, we should be able to make a more informed decision because
we will know what the output will look like and we will know whether it
is acceptable to any protocol folks.

                                Ron


Romascanu, Dan (Dan) wrote:
> 
>  
>  
> 
> 
>>-----Original Message-----
>>From: Ron Bonica [mailto:rbonica@juniper.net] 
>>Sent: Monday, November 05, 2007 10:12 PM
>>To: David Harrington
>>Cc: Romascanu, Dan (Dan); opsawg@ietf.org
>>Subject: Re: [OPSAWG] XSDMI
>>
>>
>>
>>>So, is the following text acceptable, or does this imply standards 
>>>status?
>>>
>>>"This memo describes how to translate from SMIv2 constructs to 
>>>XML-based formats. This memo does not mandate the use of this 
>>>translation by any particular protocol or application."
>>>
>>>dbh
>>
>>
>>Hi David,
>>
>>It seems to mee that PS status is at odds with this 
>>applicability statement. If the memo does not mandate use, 
>>why does the memo need to be PS?
>>
>>
>>                                  Ron
>>
>>
> 
> 
> Because what is standardized is the method of translation, not the usage
> of the result of the translation. 
> 
> Dan
> 


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Tue Nov 06 14:12:47 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IpTqw-0004TB-UT; Tue, 06 Nov 2007 14:12:46 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IpTqw-0004O9-23
	for opsawg-confirm+ok@megatron.ietf.org; Tue, 06 Nov 2007 14:12:46 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IpTqv-0004N5-GS
	for opsawg@ietf.org; Tue, 06 Nov 2007 14:12:45 -0500
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IpTqv-0000D8-2I
	for opsawg@ietf.org; Tue, 06 Nov 2007 14:12:45 -0500
X-IronPort-AV: E=Sophos;i="4.21,380,1188792000"; d="scan'208";a="76467939"
Received: from 5.6.8.135.in-addr.arpa (HELO nj300815-nj-erheast.avaya.com)
	([198.152.6.5])
	by nj300815-nj-outbound.avaya.com with ESMTP; 06 Nov 2007 14:12:44 -0500
X-IronPort-AV: E=Sophos;i="4.21,380,1188792000"; d="scan'208";a="122570787"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	06 Nov 2007 14:12:43 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [OPSAWG] XSDMI
Date: Tue, 6 Nov 2007 20:10:22 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A045E3D0C@307622ANEX5.global.avaya.com>
In-Reply-To: <473099A3.4060402@juniper.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] XSDMI
Thread-Index: AcgglD0o1J3xuo0AQiC1Xa2n8zFYwgAE9dOg
References: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com><472A2A7E.7090401@juniper.net><05a401c81cde$06d6d880$3f8011ac@china.huawei.com><472A8039.2030903@juniper.net><05ba01c81d26$62769340$3f8011ac@china.huawei.com>
	<472B3C3D.4000903@juniper.net>
	<EDC652A26FB23C4EB6384A4584434A045AA037@307622ANEX5.global.avaya.com>
	<061d01c81d71$2f6c8450$3f8011ac@china.huawei.com>
	<472F7916.4070102@juniper.net>
	<EDC652A26FB23C4EB6384A4584434A045AA725@307622ANEX5.global.avaya.com>
	<473099A3.4060402@juniper.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Ron Bonica" <rbonica@juniper.net>
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Sounds good. I believe that Scott and Tim include XSDMI on the agenda
for the OPSAWG meeting in Vancouver.=20

Thanks,=20

Dan


=20
=20

> -----Original Message-----
> From: Ron Bonica [mailto:rbonica@juniper.net]=20
> Sent: Tuesday, November 06, 2007 6:43 PM
> To: Romascanu, Dan (Dan)
> Cc: David Harrington; opsawg@ietf.org
> Subject: Re: [OPSAWG] XSDMI
>=20
> Dan,
>=20
> I don't think that I am convinced. But rather than occupying=20
> the WG with this debate, why don't we just proceed with the=20
> work. When the memo is ready for publication, we can revisit=20
> the document status issue with the benefit of some additional=20
> experience under our belts.
>=20
> At that time, we should be able to make a more informed=20
> decision because we will know what the output will look like=20
> and we will know whether it is acceptable to any protocol folks.
>=20
>                                 Ron
>=20
>=20
> Romascanu, Dan (Dan) wrote:
> >=20
> > =20
> > =20
> >=20
> >=20
> >>-----Original Message-----
> >>From: Ron Bonica [mailto:rbonica@juniper.net]
> >>Sent: Monday, November 05, 2007 10:12 PM
> >>To: David Harrington
> >>Cc: Romascanu, Dan (Dan); opsawg@ietf.org
> >>Subject: Re: [OPSAWG] XSDMI
> >>
> >>
> >>
> >>>So, is the following text acceptable, or does this imply standards=20
> >>>status?
> >>>
> >>>"This memo describes how to translate from SMIv2 constructs to=20
> >>>XML-based formats. This memo does not mandate the use of this=20
> >>>translation by any particular protocol or application."
> >>>
> >>>dbh
> >>
> >>
> >>Hi David,
> >>
> >>It seems to mee that PS status is at odds with this applicability=20
> >>statement. If the memo does not mandate use, why does the=20
> memo need to=20
> >>be PS?
> >>
> >>
> >>                                  Ron
> >>
> >>
> >=20
> >=20
> > Because what is standardized is the method of translation, not the=20
> > usage of the result of the translation.
> >=20
> > Dan
> >=20
>=20


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Tue Nov 06 14:19:20 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IpTxI-0006kn-Ku; Tue, 06 Nov 2007 14:19:20 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IpTxG-0006iN-I6
	for opsawg-confirm+ok@megatron.ietf.org; Tue, 06 Nov 2007 14:19:18 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IpTxG-0006iE-7A
	for opsawg@ietf.org; Tue, 06 Nov 2007 14:19:18 -0500
Received: from qmta06.westchester.pa.mail.comcast.net ([76.96.62.56])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IpTxF-0000Nn-Px
	for opsawg@ietf.org; Tue, 06 Nov 2007 14:19:18 -0500
Received: from OMTA08.westchester.pa.mail.comcast.net ([76.96.62.12])
	by QMTA06.westchester.pa.mail.comcast.net with smtp
	id 9WnV1Y0070Fqzac0003J00; Tue, 06 Nov 2007 19:19:16 +0000
Received: from Harrington73653 ([24.128.104.207])
	by OMTA08.westchester.pa.mail.comcast.net with comcast
	id 9XKD1Y00A4UVsHU0000000; Tue, 06 Nov 2007 19:19:16 +0000
X-Authority-Analysis: v=1.0 c=1 a=TrqIRcCQlZPyRHqXls4A:9
	a=9A9OtOaubpqm1h8U5InQPvkvdEoA:4 a=4dyfk4FV-b8A:10
	a=lZB815dzVvQA:10 a=peF9eE_zjQwA:10 a=gi0PWCVxevcA:10
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>,
	"'Ron Bonica'" <rbonica@juniper.net>
References: <02ac01c80ffe$3fab7450$b927303d@china.huawei.com><472A2A7E.7090401@juniper.net><05a401c81cde$06d6d880$3f8011ac@china.huawei.com><472A8039.2030903@juniper.net><05ba01c81d26$62769340$3f8011ac@china.huawei.com>
	<472B3C3D.4000903@juniper.net>
	<EDC652A26FB23C4EB6384A4584434A045AA037@307622ANEX5.global.avaya.com>
	<061d01c81d71$2f6c8450$3f8011ac@china.huawei.com>
	<472F7916.4070102@juniper.net>
	<EDC652A26FB23C4EB6384A4584434A045AA725@307622ANEX5.global.avaya.com>
	<473099A3.4060402@juniper.net>
	<EDC652A26FB23C4EB6384A4584434A045E3D0C@307622ANEX5.global.avaya.com>
Subject: RE: [OPSAWG] XSDMI
Date: Tue, 6 Nov 2007 14:18:57 -0500
Message-ID: <00ab01c820a9$e0f9d390$6502a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A045E3D0C@307622ANEX5.global.avaya.com>
Thread-Index: AcgglD0o1J3xuo0AQiC1Xa2n8zFYwgAE9dOgAABYyXA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Spam-Score: 1.8 (+)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

I agree with making the decision on PS vs Informational later, as long
as the work is allowed to continue in the meantime. 

That will give the YANG team time to produce internet-drafts, so we
can compare the formats and hopefully end up with one consistent
format.

dbh

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] 
> Sent: Tuesday, November 06, 2007 2:10 PM
> To: Ron Bonica
> Cc: David Harrington; opsawg@ietf.org
> Subject: RE: [OPSAWG] XSDMI
> 
> Sounds good. I believe that Scott and Tim include XSDMI on the
agenda
> for the OPSAWG meeting in Vancouver. 
> 
> Thanks, 
> 
> Dan
> 
> 
>  
>  
> 
> > -----Original Message-----
> > From: Ron Bonica [mailto:rbonica@juniper.net] 
> > Sent: Tuesday, November 06, 2007 6:43 PM
> > To: Romascanu, Dan (Dan)
> > Cc: David Harrington; opsawg@ietf.org
> > Subject: Re: [OPSAWG] XSDMI
> > 
> > Dan,
> > 
> > I don't think that I am convinced. But rather than occupying 
> > the WG with this debate, why don't we just proceed with the 
> > work. When the memo is ready for publication, we can revisit 
> > the document status issue with the benefit of some additional 
> > experience under our belts.
> > 
> > At that time, we should be able to make a more informed 
> > decision because we will know what the output will look like 
> > and we will know whether it is acceptable to any protocol folks.
> > 
> >                                 Ron
> > 
> > 
> > Romascanu, Dan (Dan) wrote:
> > > 
> > >  
> > >  
> > > 
> > > 
> > >>-----Original Message-----
> > >>From: Ron Bonica [mailto:rbonica@juniper.net]
> > >>Sent: Monday, November 05, 2007 10:12 PM
> > >>To: David Harrington
> > >>Cc: Romascanu, Dan (Dan); opsawg@ietf.org
> > >>Subject: Re: [OPSAWG] XSDMI
> > >>
> > >>
> > >>
> > >>>So, is the following text acceptable, or does this imply 
> standards 
> > >>>status?
> > >>>
> > >>>"This memo describes how to translate from SMIv2 constructs to 
> > >>>XML-based formats. This memo does not mandate the use of this 
> > >>>translation by any particular protocol or application."
> > >>>
> > >>>dbh
> > >>
> > >>
> > >>Hi David,
> > >>
> > >>It seems to mee that PS status is at odds with this
applicability 
> > >>statement. If the memo does not mandate use, why does the 
> > memo need to 
> > >>be PS?
> > >>
> > >>
> > >>                                  Ron
> > >>
> > >>
> > > 
> > > 
> > > Because what is standardized is the method of 
> translation, not the 
> > > usage of the result of the translation.
> > > 
> > > Dan
> > > 
> > 
> 




_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Tue Nov 06 22:44:57 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ipbqa-0002H9-Uf; Tue, 06 Nov 2007 22:44:56 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IpbqZ-0002Fn-GK
	for opsawg-confirm+ok@megatron.ietf.org; Tue, 06 Nov 2007 22:44:55 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IpbqZ-0002Fc-4M
	for opsawg@ietf.org; Tue, 06 Nov 2007 22:44:55 -0500
Received: from newdev.eecs.harvard.edu ([140.247.60.212])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IpbqY-00024x-Tz
	for opsawg@ietf.org; Tue, 06 Nov 2007 22:44:55 -0500
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501)
	id 00F7961B682; Tue,  6 Nov 2007 22:42:06 -0500 (EST)
To: opsawg@ietf.org
Message-Id: <20071107034206.00F7961B682@newdev.eecs.harvard.edu>
Date: Tue,  6 Nov 2007 22:42:06 -0500 (EST)
From: sob@harvard.edu (Scott O. Bradner)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Subject: [OPSAWG] agenda requests for opsawg in Vancouver
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org


this is a first call for timeslots on the opsawg session in Vancouver

we are currently scheduled for tuesday afternoon from 1520 to 1720

Scott & Ted



_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Wed Nov 07 11:44:14 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ipo0k-0000iR-55; Wed, 07 Nov 2007 11:44:14 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Ipo0i-0000iM-Ph
	for opsawg-confirm+ok@megatron.ietf.org; Wed, 07 Nov 2007 11:44:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ipo0d-0000bJ-Sv
	for opsawg@ietf.org; Wed, 07 Nov 2007 11:44:07 -0500
Received: from zrtps0kp.nortel.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ipo0a-0007hT-Ss
	for opsawg@ietf.org; Wed, 07 Nov 2007 11:44:07 -0500
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com
	[47.129.230.99])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	lA7Gi2b23781 for <opsawg@ietf.org>; Wed, 7 Nov 2007 16:44:02 GMT
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [OPSAWG] Updated Syslog Alarm Draft
Date: Wed, 7 Nov 2007 11:43:53 -0500
Message-ID: <713043CE8B8E1348AF3C546DBE02C1B411B3A93B@zcarhxm2.corp.nortel.com>
In-Reply-To: <713043CE8B8E1348AF3C546DBE02C1B41066751D@zcarhxm2.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] Updated Syslog Alarm Draft
Thread-Index: AcfjJtEq7TeB/I13RUmd9KkO6MzpGQ+Nordg
References: <713043CE8B8E1348AF3C546DBE02C1B41066751D@zcarhxm2.corp.nortel.com>
From: "Sharon Chisholm" <schishol@nortel.com>
To: <opsawg@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Ping.=20

-----Original Message-----
From: Chisholm, Sharon (CAR:ZZ00)=20
Sent: Monday, August 20, 2007 8:37 AM
To: opsawg@ietf.org
Subject: [OPSAWG] Updated Syslog Alarm Draft

Hi

We have updated the Syslog Alarm work with the changes I discussed in
the Chicago meeting.=20

=09
http://www.ietf.org/internet-drafts/draft-gerhards-chisholm-syslog-alarm
-01.txt

I'm requesting that this work be added to this working group as a
standards track document.

Thanks,

Sharon Chisholm
Nortel
Ottawa, Ontario
Canada


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Wed Nov 07 22:34:43 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IpyAE-0001Zc-4d; Wed, 07 Nov 2007 22:34:42 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IpyAD-0001YR-9f
	for opsawg-confirm+ok@megatron.ietf.org; Wed, 07 Nov 2007 22:34:41 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IpyAC-0001YJ-Uu
	for opsawg@ietf.org; Wed, 07 Nov 2007 22:34:40 -0500
Received: from qmta05.westchester.pa.mail.comcast.net ([76.96.62.48])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IpyAC-00065Z-Jo
	for opsawg@ietf.org; Wed, 07 Nov 2007 22:34:40 -0500
Received: from OMTA09.westchester.pa.mail.comcast.net ([76.96.62.20])
	by QMTA05.westchester.pa.mail.comcast.net with smtp
	id A2Np1Y0040SCNGk0005D00; Thu, 08 Nov 2007 03:34:40 +0000
Received: from Harrington73653 ([24.128.104.207])
	by OMTA09.westchester.pa.mail.comcast.net with comcast
	id A3ab1Y0064UVsHU0000000; Thu, 08 Nov 2007 03:34:40 +0000
X-Authority-Analysis: v=1.0 c=1 a=48vgC7mUAAAA:8 a=MnOWF-GcQBiLmS3pVUwA:9
	a=BUJohORWM2NbRnBSKYf2mLb0_5wA:4 a=lZB815dzVvQA:10
	a=50e4U0PicR4A:10
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Scott O. Bradner'" <sob@harvard.edu>,
	<opsawg@ietf.org>
References: <20071107034206.00F7961B682@newdev.eecs.harvard.edu>
Subject: RE: [OPSAWG] agenda requests for opsawg in Vancouver
Date: Wed, 7 Nov 2007 22:34:17 -0500
Message-ID: <005401c821b8$3e265de0$6502a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
Thread-Index: Acgg8JJfbqQjQZnkSKyaeqx+0l0qpwArYb4g
In-Reply-To: <20071107034206.00F7961B682@newdev.eecs.harvard.edu>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: 
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Hi,

We would like to request time for discussion of
draft-romascanu-netconf-datatypes-03.txt and
draft-li-mib-convert-xx.txt.

dbh

> -----Original Message-----
> From: Scott O. Bradner [mailto:sob@harvard.edu] 
> Sent: Tuesday, November 06, 2007 10:42 PM
> To: opsawg@ietf.org
> Subject: [OPSAWG] agenda requests for opsawg in Vancouver
> 
> 
> this is a first call for timeslots on the opsawg session in
Vancouver
> 
> we are currently scheduled for tuesday afternoon from 1520 to 1720
> 
> Scott & Ted
> 
> 
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www1.ietf.org/mailman/listinfo/opsawg
> 




_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Wed Nov 07 23:25:56 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ipyxo-0005ZC-9u; Wed, 07 Nov 2007 23:25:56 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Ipyxm-0005Xr-BT
	for opsawg-confirm+ok@megatron.ietf.org; Wed, 07 Nov 2007 23:25:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ipyxm-0005XV-1T
	for opsawg@ietf.org; Wed, 07 Nov 2007 23:25:54 -0500
Received: from umi.kikuken.org ([202.126.16.27] helo=ari.kikuken.org)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Ipyxi-0007Rq-Cm
	for opsawg@ietf.org; Wed, 07 Nov 2007 23:25:54 -0500
Received: (qmail 21084 invoked from network); 8 Nov 2007 13:25:48 +0900
Received: from unknown (HELO localhost) (218.100.15.124)
	by umi.kikuken.org with SMTP; 8 Nov 2007 13:25:48 +0900
Date: Thu, 08 Nov 2007 13:25:48 +0900 (JST)
Message-Id: <20071108.132548.94837533.yu@kikuken.org>
To: sob@harvard.edu
Subject: Re: [OPSAWG] agenda requests for opsawg in Vancouver
From: KIKUCHI Yutaka <yu@kikuken.org>
In-Reply-To: <20071107034206.00F7961B682@newdev.eecs.harvard.edu>
References: <20071107034206.00F7961B682@newdev.eecs.harvard.edu>
Organization: Kochi Univ. of Tech.
X-Mailer: Mew version 4.2.53 on Emacs 22.0.50 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: opsawg@ietf.org, zin@jaist.ac.jp, satoru@ft.solteria.net,
	nagami@inetcore.com
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Hi,

We would like to discuss about our I-D
draft-kikuchi-tunnel-measure-req-02.txt
``Quality Measurement Requirements for Tunneling Protocols''.
The newest version will be appeared later.

-- Best Regards, Yu.

> 
> this is a first call for timeslots on the opsawg session in Vancouver
> 
> we are currently scheduled for tuesday afternoon from 1520 to 1720
> 
> Scott & Ted
> 
> 
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www1.ietf.org/mailman/listinfo/opsawg
> 


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Mon Nov 12 10:11:44 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Irawy-00080r-2Z; Mon, 12 Nov 2007 10:11:44 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Iraww-00080D-33
	for opsawg-confirm+ok@megatron.ietf.org; Mon, 12 Nov 2007 10:11:42 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Irawq-0007qN-24
	for opsawg@ietf.org; Mon, 12 Nov 2007 10:11:36 -0500
Received: from qmta03.emeryville.ca.mail.comcast.net ([76.96.30.32])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Irawp-0003CQ-3S
	for opsawg@ietf.org; Mon, 12 Nov 2007 10:11:35 -0500
Received: from OMTA09.emeryville.ca.mail.comcast.net ([76.96.30.20])
	by QMTA03.emeryville.ca.mail.comcast.net with smtp
	id Boi71Y0030S2fkC0109h00; Mon, 12 Nov 2007 15:11:35 +0000
Received: from Harrington73653 ([24.128.104.207])
	by OMTA09.emeryville.ca.mail.comcast.net with comcast
	id BrBV1Y00H4UVsHU0000000; Mon, 12 Nov 2007 15:11:36 +0000
X-Authority-Analysis: v=1.0 c=1 a=48vgC7mUAAAA:8 a=IEx8MEJOqsr1paw1gfEA:9
	a=K6VaqQAEoD5bVOkaVDcA:7 a=SqMP8VgzDHzj73qwse958Sx1Mm8A:4
	a=kkUMZHjH4KkA:10 a=3FZX-ydVlcEA:10 a=lZB815dzVvQA:10
	a=4dyfk4FV-b8A:10 a=50e4U0PicR4A:10
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Wijnen, Bert \(Bert\)'" <bwijnen@alcatel-lucent.com>, <opsawg@ietf.org>
References: <D4D321F6118846429CD792F0B5AF471F7E5AFD@DEEXC1U02.de.lucent.com>
Subject: RE: [OPSAWG] draft-ietf-opsawg-operations-and-management-00.txt 
Date: Mon, 12 Nov 2007 10:11:04 -0500
Message-ID: <086101c8253e$3f821970$6502a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <D4D321F6118846429CD792F0B5AF471F7E5AFD@DEEXC1U02.de.lucent.com>
Thread-Index: Acf6+3iW7u1v5dLtS+Cr1h/iKZ2zUwAmyEJAADCuZyAKOLxXAA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9
Cc: 
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Hi,

inline. 

> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@alcatel-lucent.com] 
> Sent: Friday, September 21, 2007 10:41 AM
> To: opsawg@ietf.org
> Subject: [OPSAWG] draft-ietf-opsawg-operations-and-management-00.txt

> 
> I have read the document and here are some minor comments:
> 
> 1. the document is quite long. I know this is an easy comment as a 
>    reader and no so easy to address as an editor.
>    but we should realize that WG members who need to read this
>    as preparation for their protocol-to-be-developed will be 
>    less inclined to do so when the document is too long.

agreed. I can remove some redundancy, but otherwise I am not sure how
to shorten the document. Specific suggestions welcome.

One approach might be to move the discussion of existing protocols and
data models into a separate document. I can see that discussion being
ongoing as new protocols and data models are approved. I would like WG
feedback on this.

> 
> 2. Section 4.3.1
>  
>       [DISCUSS:: 'control plane' and 'data plane' are such slippery
>        terms that I think they need to be defined.]
> 
>    I don't think we need to define them We are not giving any hard
>    recommendations/requirements, just guidelines on how to think 
>    about these management aspects. In that context, I don't think
>    we need to be precise. So we can avoid many long discussions
>    to try to agree on an exact (or at least acceptable) definition.

I removed the discuss.

> 
> 3. Section 5.1 starts off with
>       SNMP [RFC3410] is a Full Standard 
>    Well, RFC3410 is Informational. I know that SNMP (Specifically
> SNMPv3)
>    is at IETF Full Standard level. But people who quickly check the 
>    rfc-index for RFC3410 might get confused.

fixed.
> 
> 4. Section 6.5
> 
> 
>      IPsec Security Policy IPsec Action MIB
>      [I-D.ietf-ipsp-ipsecaction-mib] defines a MIB module for
>      configuration of an IPsec action within the IPsec security
policy
>      database (SPD).  [TODO: this is not yet a PS, and has 
> dependencies
> on
>      a dead document?]
> 
>      IPsec Security Policy IKE Action MIB 
> [I-D.ietf-ipsp-ikeaction-mib]
>      defines a MIB module for configuration of an Internet 
> Key Exchange
>      (IKE) [RFC4306] action within the IPsec security policy
database
>      (SPD).  [TODO: this is not yet a PS, and has 
> dependencies on a dead
>      document?]
> 
>    These 2 MIB modules have been back and forth between MIB-doctor
> review
>    and new revision for many (3-4) years now (cycles are around a
year
>    at least). As far as I can tell, I do not see them making much
(if
>    any progress). SO I think we should not discuss them here at all.

removed.

> 
> Bert Wijnen 
> 
> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] 
> Sent: Thursday, September 20, 2007 5:00 PM
> To: ops-area@ietf.org
> Subject: [OPS-AREA] FW:
> I-DACTION:draft-ietf-opsawg-operations-and-management-00.txt 
> 
>  
> The Guidelines for operations and management of new protocols
document
> was submitted as OPSAWG I-D. Please use the OPSAWG list for 
> comments and
> discussions. 
> 
> Dan
> 
> 
>  
> 
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Wednesday, September 19, 2007 10:15 PM
> To: i-d-announce@ietf.org
> Cc: opsawg@ietf.org
> Subject: I-D 
> ACTION:draft-ietf-opsawg-operations-and-management-00.txt 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Operations and Management 
> Area Working
> Group Working Group of the IETF.
> 
> 	Title		: Guidelines for Considering Operations and
> Management of New Protocols
> 	Author(s)	: D. Harrington
> 	Filename	:
> draft-ietf-opsawg-operations-and-management-00.txt
> 	Pages		: 37
> 	Date		: 2007-9-19
> 	
> 
>    New protocols or protocol extensions are best designed with due
>    consideration of operations and management issues related to the
>    protocol.  Retrofitting operations and management 
> recommendations to
>    protocols is sub-optimal.  The purpose of this document is 
> to provide
>    guidance to authors of protocol documents about aspects to
consider
>    related to the operations and management that should be
considered
>    for inclusion in documents defining requirements or 
> functionality of
>    new protocols or protocol extensions.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-opsawg-operatio
> ns-and-man
> agement-00.txt
> 
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body
of
> the message. 
> You can also visit
https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then "get
> draft-ietf-opsawg-operations-and-management-00.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE
>
/internet-drafts/draft-ietf-opsawg-operations-and-management-00.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack"
or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail
> readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been
split
> 	up into multiple messages), so check your local documentation
on
> 	how to manipulate these messages.
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www1.ietf.org/mailman/listinfo/opsawg
> 




_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Tue Nov 13 09:36:16 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IrwsB-0004Ts-GB; Tue, 13 Nov 2007 09:36:15 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IrwsA-0004T4-Ic
	for opsawg-confirm+ok@megatron.ietf.org; Tue, 13 Nov 2007 09:36:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Irws5-0004MV-9b
	for opsawg@ietf.org; Tue, 13 Nov 2007 09:36:09 -0500
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Irws2-0003zo-PF
	for opsawg@ietf.org; Tue, 13 Nov 2007 09:36:09 -0500
X-IronPort-AV: E=Sophos;i="4.21,410,1188792000"; d="scan'208";a="78097676"
Received: from 5.7.8.135.in-addr.arpa (HELO co300216-co-erhwest.avaya.com)
	([198.152.7.5])
	by nj300815-nj-outbound.avaya.com with ESMTP; 13 Nov 2007 09:36:03 -0500
X-IronPort-AV: E=Sophos;i="4.21,410,1188792000"; d="scan'208";a="130346668"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	13 Nov 2007 09:36:03 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 13 Nov 2007 15:35:49 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A04615969@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Some comments on draft-ietf-opsawg-operations-and-management-00
Thread-Index: AcgmAnvf+4eVkLVMT8Gk5uokMR1fHg==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <opsawg@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Subject: [OPSAWG] Some comments on
	draft-ietf-opsawg-operations-and-management-00
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Here are a few comments about
draft-ietf-opsawg-operations-and-management-00. They are 'high-level'
meaning that I am dealing more with the structure of the document and
giving my take on a some of the open questions. All are contributor
opinions. I am leaving nits and smaller editorial comments for a later
phase.

1. >  [DISCUSS - This document seems to be just as concerned with the
   protocol designer's "mind-set" and the protocol development process
   as it is with the protocol as a finished product.  While we all agree
   that it would be a good thing to imprint operational sensitivities
   into the consciousness of the protocol developer, I do not think that
   this is a practical goal.  The best that we can do is to set forth a
   list of objective criteria by which a protocol designer can evaluate
   whether the protocol that he/she has developed is manageable.]

I would add here that a target audience is also the group of reviewers
that evaluate the protocol in phases of approval

2. >    [DISCUSS: - the document may attempt to cover too much ground.
Maybe
   it will develop into a framework document, supported by documents of
   the following sort: . what makes a MIB usable? . how much protocol
   state information needs to be exposed and how? . how much performance
   information needs to be exposed and how?]

I am concerned about too much fragmentation. Let us agree that this is
the framework document plus guidelines information, and we can debate
how much needs to make it in the framework. Out of the example you give
the first two do not seem to belong here, but the third does.=20

3. The last paragraph of section 2.1 dealing with the need of an
operational model and analysis is very important but does not seem to
belong here. I think that it should be moved into 3.1 and that it should
be re-written in bullets format to make the list of issues to look at as
part of an operational model clear. =20

4. Section 3.5 seems to limit the impact on network operation only to
network traffic or devices. I believe that it should consider also
impact on applications and registries, for example DNS entries, or size
of routing tables.=20

5. Section 4.3 should start with a short discussion about the need to
provide information in documents about how faults information is being
propagated (asynchronous notifications, polling of health indicators,
hierarchy of faults)

6. Section 4.3.4 needs clarification and more details.=20

7. I believe that some of the issues raised in 4.6 go to a level of
detail beyond the other classes of management  operations and should be
left for appropriate data models or protocol design documents. Unless
there are some generic recommendations issues like maximal values of
counters, behavior at rollout, persistency and discontinuities should be
out of scope. I would rather expect from a protocol document to identify
what are the principal performance factors that need to be looked at
when measuring the efficiency of the protocol implementations.=20

8.  I agree to a large extent to Juergen's DISCUSS. It may be better to
shorten this section, provide a crisp recommendation to look at the
existing standard track MIB modules, and move the rest of the section in
an Annex.=20

9. It may be useful to include in Section 7.1 a bulleted list of the
issues that may be included in the Manageability and Operations sections
of IETF documents with the observation that this list is provided for
guidance and document authors may pick what is relevant for their
document.=20

Thanks and Regards,

Dan


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Tue Nov 13 12:18:17 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IrzOx-0002HW-IS; Tue, 13 Nov 2007 12:18:15 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IrzOq-0002A7-EQ
	for opsawg-confirm+ok@megatron.ietf.org; Tue, 13 Nov 2007 12:18:09 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IrzOm-00024j-QQ
	for opsawg@ietf.org; Tue, 13 Nov 2007 12:18:05 -0500
Received: from exprod7og109.obsmtp.com ([64.18.2.171])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IrzOk-0007bz-Ls
	for opsawg@ietf.org; Tue, 13 Nov 2007 12:18:04 -0500
Received: from source ([66.129.224.36]) by exprod7ob109.postini.com
	([64.18.6.12]) with SMTP; Tue, 13 Nov 2007 09:17:45 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Nov 2007 09:16:08 -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 lADHG8n27225;
	Tue, 13 Nov 2007 09:16:08 -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 lADHDAmR021241;
	Tue, 13 Nov 2007 17:13:10 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200711131713.lADHDAmR021241@idle.juniper.net>
To: "David Harrington" <ietfdbh@comcast.net>
Subject: Re: [OPSAWG] XSDMI 
Date: Tue, 13 Nov 2007 12:13:10 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 13 Nov 2007 17:16:08.0678 (UTC)
	FILETIME=[E1A47060:01C82618]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

[Joining the conversation late, but .....]

"David Harrington" writes:
>Juergen has raised the issue that the XSD produced by the XDMI effort
>and the XSD produced by the YANG effort might be different, and having
>two different XSD equivalents for MIB datatypes would be suboptimal. I
>agree.

Cool....

>However, I have the concern that while vendors wait for YANG to be
>completed, they will need to develop proprietary data models for use
>with netconf. Some vendors will want to reuse datatypes found in the
>15 year compilation of IETF NM experience found in the standard MIB
>modules, and supported by existing implementation code.

Can this concern be addressed by altering XSDMI to follow the
encodings of YANG?  There are already SMI->YANG translators and
YANG->XSD translators, so the SMI->XSD path is covered.  How
different are the XSDs produced by XSDMI and SMI-based YANG?

>The XSDMI effort is about taking the MIB, which operators have
>complained is not well suited to configuration, and translating
>aspects of the MIB into equivalent XSD.

IMHO translating MIBs into XML will not make them instantly
configuration friendly.  There's a lot more that needs to
happen.

>The YANG approach for
>netconf focuses not only on configuration, but also on developing an
>information modeling language which can then be used by tools to
>generate syntax-specific data models for a variety of purposes, such
>as Netconf-suitable XSD data models, SNMP-suitable MIB modules, plus
>data models for other modeling systems.

I don't think we're that ambitious.  ;-)

Quite the opposite, we tried to minimize the problem domain we were
focusing on, in order to be able to define a solvable problem.  We
leveraged the knowledge gained from having solved this problem in
multiple proprietary implementations to create a data modeling
language that NETCONF modelers can use to define their models.  We've
put features in that have allowed our previous implementations to
achieve the scale and power that is required in our problem space.
The utility of YANG outside that problem space is not interesting to
us.

>Just to be clear, I support the YANG effort because I believe it could
>lead to better consistency of data modeling across protocols, but it
>has yet to be proven to be viable, and other efforts to converge or
>harmonize data models have had mixed success at best.

Yes, YANG is boldly going where many have tried before, but the strength
of YANG is that it's based on working products that use capabilities
of the modeling language to support industrial-strength NETCONF
implementations.  Think of this as field-trials, meaning the
YANG-style solution's viability has been proven in the core for many
years.

>If the YANG approach proves to be
>viable, then the XSDMI translations can be modified as needed to work
>with YANG in the future. But XSDMI could give us XSD datatypes to
>develop data models, possibly years before consensus on YANG will be
>achieved.

IMHO this puts the cart before the horse, giving an encoding/syntax
(XSD) that modeling languages like YANG will have to encode to.  I
can't see a new XSDMIv2 being churned out that becomes
YANG-compatible.  If you want to be compatible, start now.

Thanks,
 Phil


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Tue Nov 13 16:48:12 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Is3cB-0001zT-1w; Tue, 13 Nov 2007 16:48:11 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Is3cA-0001zO-BR
	for opsawg-confirm+ok@megatron.ietf.org; Tue, 13 Nov 2007 16:48:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Is3c9-0001yd-BB
	for opsawg@ietf.org; Tue, 13 Nov 2007 16:48:09 -0500
Received: from qmta10.emeryville.ca.mail.comcast.net ([76.96.30.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Is3c6-0005Hv-6Y
	for opsawg@ietf.org; Tue, 13 Nov 2007 16:48:09 -0500
Received: from OMTA06.emeryville.ca.mail.comcast.net ([76.96.30.51])
	by QMTA10.emeryville.ca.mail.comcast.net with comcast
	id CGaB1Y00516AWCU010UV00; Tue, 13 Nov 2007 21:48:08 +0000
Received: from Harrington73653 ([24.128.104.207])
	by OMTA06.emeryville.ca.mail.comcast.net with comcast
	id CMo21Y00E4UVsHU0000000; Tue, 13 Nov 2007 21:48:08 +0000
X-Authority-Analysis: v=1.0 c=1 a=talcTAgpeTFAFG-RVpMA:9
	a=ldtPAD0207Sqins9cJ4A:7 a=pB8AggayjBHWncw_AYxvjdXBnmcA:4
	a=peF9eE_zjQwA:10 a=uWS-M9W3EfsA:10
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Phil Shafer'" <phil@juniper.net>
References: <200711131713.lADHDAmR021241@idle.juniper.net>
Subject: RE: [OPSAWG] XSDMI 
Date: Tue, 13 Nov 2007 16:47:33 -0500
Message-ID: <0c1101c8263e$cd3e0200$6502a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <200711131713.lADHDAmR021241@idle.juniper.net>
Thread-Index: AcgmGSXIoQKLG7pBQHqIUxMQZT8u/gAH6DRA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Spam-Score: 1.8 (+)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

inline 

> -----Original Message-----
> From: Phil Shafer [mailto:phil@juniper.net] 
> 
> Can this concern be addressed by altering XSDMI to follow the
> encodings of YANG?  There are already SMI->YANG translators and
> YANG->XSD translators, so the SMI->XSD path is covered.  How
> different are the XSDs produced by XSDMI and SMI-based YANG?

Here's what I know about the XSD encodings of YANG:
from 
"It is possible to generate an XSD document representing the data
   model defined in YANG.  The XSD will specify the structure of the
   model, the used types, cardinality, etc. but a good part of the
   information in YANG can not be represented in standard XSD
constructs
   e.g. config, status, default, keyref.

   The above information will be added to XSD inside annotation
   statements (which can not be handled by standard XML tools).  The
   exact form of annotations is for further study.

   Data models defined in YANG might have multiple top-level elements.
   To make it possible to validate the XML encoded data, both for the
   generated XSD describing the data model and for the config and
state
   data received in NETCONF RPCs a single top level element <data>
shall
   be added.

   From a YANG model many different XSD schemas can be generated
   defining the same data model.  The exact rules to generate XSD from
   YANG are outside the scope of this document, however some general
   considerations are needed.
"

The WG has absolutely no idea how different the translations of XSDMI
and YANG are because we have never seen the XSD output from YANG.


> 
> >The XSDMI effort is about taking the MIB, which operators have
> >complained is not well suited to configuration, and translating
> >aspects of the MIB into equivalent XSD.
> 
> IMHO translating MIBs into XML will not make them instantly
> configuration friendly.  There's a lot more that needs to
> happen.

And it is not our intention to make MIB modules
configuration-friendly. The XSDMI translations are not about Netconf.
It is solely about making SMI datatypes and textual conventions
avaiable for use in XML-based environments that **choose** to use the
XSDMI translations.

> 
> >The YANG approach for
> >netconf focuses not only on configuration, but also on developing
an
> >information modeling language which can then be used by tools to
> >generate syntax-specific data models for a variety of purposes,
such
> >as Netconf-suitable XSD data models, SNMP-suitable MIB modules,
plus
> >data models for other modeling systems.
> 
> I don't think we're that ambitious.  ;-)
> 
> Quite the opposite, we tried to minimize the problem domain we were
> focusing on, in order to be able to define a solvable problem.  We
> leveraged the knowledge gained from having solved this problem in
> multiple proprietary implementations to create a data modeling
> language that NETCONF modelers can use to define their models.
We've
> put features in that have allowed our previous implementations to
> achieve the scale and power that is required in our problem space.
> The utility of YANG outside that problem space is not interesting to
> us.

But it is interesting to others who may want to use the XSD
equivalents of SMI datatypes and TCs for non-YANG and non-Netconf
purposes.

> 
> >Just to be clear, I support the YANG effort because I 
> believe it could
> >lead to better consistency of data modeling across protocols, but
it
> >has yet to be proven to be viable, and other efforts to converge or
> >harmonize data models have had mixed success at best.
> 
> Yes, YANG is boldly going where many have tried before, but 
> the strength
> of YANG is that it's based on working products that use capabilities
> of the modeling language to support industrial-strength NETCONF
> implementations.  Think of this as field-trials, meaning the
> YANG-style solution's viability has been proven in the core for many
> years.
> 
> >If the YANG approach proves to be
> >viable, then the XSDMI translations can be modified as needed to
work
> >with YANG in the future. But XSDMI could give us XSD datatypes to
> >develop data models, possibly years before consensus on YANG will
be
> >achieved.
> 
> IMHO this puts the cart before the horse, giving an encoding/syntax
> (XSD) that modeling languages like YANG will have to encode to.  I
> can't see a new XSDMIv2 being churned out that becomes
> YANG-compatible.  If you want to be compatible, start now.

We have published our XSD encodings in the IETF. YANG has not. 

If there are SMI->YANG and YANG->XSD tools, then why aren't you
publishing the specs and the output so we can see the translations so
we can compare them? If yours are better than ours, which may be the
case, then by all means we can try to be compatible starting now, but
we have not seen your encodings; we cannot start trying to be
compatible until you do publish your encodings.

I have seen three different proposals for doing SMI-XSD translations,
not including the YANG approach, and each approach has advantages and
disadvantages. I would like to have the OPSAWG be able to consider all
the different tradeoffs and decide as a community which approach is
best. 

I do not like abdicating all responsibility to a closed design team to
make the decisions for the IETF. Are all your design decision based on
achieving vendor-neutrality, or are some decisions favorable to the
existing implementations of certain vendors? Are any of the designs
encumbered by IPR? Are you making decisions to trade away some feature
that others may want without even consulting those who might be
impacted by the decision?

I am not expecting XSDMI to become a standard in the next two months
or the next six, and probably not the next year (this is the IETF
after all). So there is plenty of time to try to build compatibility
between the approaches, if you publish your specs and output. If YANG
can deliver on its promises of a viable solution, and the industry
accepts it, I have no issue with deprecating XSDMI. But I do not want
to **not** do XSDMI, and not have that point of comparison, just
because you promise a better solution. I've dealt with too much
vaporware in my life to want to put all my eggs in one promised
basket.

I'm not trying in any way to require YANG to use the XSDMI encodings,
or otherwise contrain the design of YANG. I think YANG and SMI are in
different applicability spaces. I resent that members of the YANG team
want to force the rest of us to use only their encodings and to
constrain the IETF from doing any work on an SMI-XSD translation that
is not the YANG translation.

> 
> Thanks,
>  Phil
> 

dbh




_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Tue Nov 13 16:48:50 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Is3co-0002wX-G8; Tue, 13 Nov 2007 16:48:50 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Is3cm-0002vg-TL
	for opsawg-confirm+ok@megatron.ietf.org; Tue, 13 Nov 2007 16:48:48 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Is3cm-0002vX-HF
	for opsawg@ietf.org; Tue, 13 Nov 2007 16:48:48 -0500
Received: from qmta08.emeryville.ca.mail.comcast.net ([76.96.30.80])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Is3cl-00011I-9h
	for opsawg@ietf.org; Tue, 13 Nov 2007 16:48:48 -0500
Received: from OMTA12.emeryville.ca.mail.comcast.net ([76.96.30.44])
	by QMTA08.emeryville.ca.mail.comcast.net with comcast
	id CG0Y1Y0090x6nqc010Vz00; Tue, 13 Nov 2007 21:48:49 +0000
Received: from Harrington73653 ([24.128.104.207])
	by OMTA12.emeryville.ca.mail.comcast.net with comcast
	id CMoj1Y00A4UVsHU0000000; Tue, 13 Nov 2007 21:48:49 +0000
X-Authority-Analysis: v=1.0 c=1 a=48vgC7mUAAAA:8 a=kb4b72rcZSWPmxtS2ZEA:9
	a=qEza9-EmKuD6k1DEsIsA:7 a=Ge4yDRST9HaQkZ61W_lQASNbzAIA:4
	a=4dyfk4FV-b8A:10 a=lZB815dzVvQA:10 a=NfA2RSpTaHsA:10
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>,
	<opsawg@ietf.org>
References: <EDC652A26FB23C4EB6384A4584434A04615969@307622ANEX5.global.avaya.com>
Subject: RE: [OPSAWG] Some comments
	ondraft-ietf-opsawg-operations-and-management-00
Date: Tue, 13 Nov 2007 16:48:15 -0500
Message-ID: <0c1201c8263e$e603dda0$6502a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04615969@307622ANEX5.global.avaya.com>
Thread-Index: AcgmAnvf+4eVkLVMT8Gk5uokMR1fHgAJIdmQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 72dbfff5c6b8ad2b1b727c13be042129
Cc: 
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

discussions inline.

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] 
> Sent: Tuesday, November 13, 2007 9:36 AM
> To: opsawg@ietf.org
> Subject: [OPSAWG] Some comments 
> ondraft-ietf-opsawg-operations-and-management-00
> 
> Here are a few comments about
> draft-ietf-opsawg-operations-and-management-00. They are
'high-level'
> meaning that I am dealing more with the structure of the document
and
> giving my take on a some of the open questions. All are contributor
> opinions. I am leaving nits and smaller editorial comments for a
later
> phase.
> 
> 1. >  [DISCUSS - This document seems to be just as concerned with
the
>    protocol designer's "mind-set" and the protocol development
process
>    as it is with the protocol as a finished product.  While 
> we all agree
>    that it would be a good thing to imprint operational
sensitivities
>    into the consciousness of the protocol developer, I do not 
> think that
>    this is a practical goal.  The best that we can do is to 
> set forth a
>    list of objective criteria by which a protocol designer 
> can evaluate
>    whether the protocol that he/she has developed is manageable.]
> 
> I would add here that a target audience is also the group of
reviewers
> that evaluate the protocol in phases of approval

done.

> 
> 2. >    [DISCUSS: - the document may attempt to cover too much
ground.
> Maybe
>    it will develop into a framework document, supported by 
> documents of
>    the following sort: . what makes a MIB usable? . how much
protocol
>    state information needs to be exposed and how? . how much 
> performance
>    information needs to be exposed and how?]
> 
> I am concerned about too much fragmentation. Let us agree that this
is
> the framework document plus guidelines information, and we can
debate
> how much needs to make it in the framework. Out of the 
> example you give
> the first two do not seem to belong here, but the third does. 

This DISCUSS text captured somebody else's wording; that was not my
example. I would like to see a succinct set of guidelines. I think
fragmentation would hurt the utility of such guidelines. I can see
separating the survey of existing protocols and data models from the
guidelines to keep the size down, and to distinguish the purpose of
the "considerations" from the "survey of existing".

(Boy, am I the wrong editor for succinct ;-) Suggestions highly
welcome for how to make the guidelines and discussions more succinct.

> 
> 3. The last paragraph of section 2.1 dealing with the need of an
> operational model and analysis is very important but does not seem
to
> belong here. I think that it should be moved into 3.1 and 
> that it should
> be re-written in bullets format to make the list of issues to 
> look at as
> part of an operational model clear.  

done.

> 
> 4. Section 3.5 seems to limit the impact on network operation only
to
> network traffic or devices. I believe that it should consider also
> impact on applications and registries, for example DNS 
> entries, or size
> of routing tables. 

I added your comment about what should be considered. Additional text
and detail welcome.

> 
> 5. Section 4.3 should start with a short discussion about the need
to
> provide information in documents about how faults information is
being
> propagated (asynchronous notifications, polling of health
indicators,
> hierarchy of faults)

Done. I understand the distinction between notifications and polling.
However, I am not sure what you had in mind with the hierarchy of
faults. I wrote some text, but it may not be what you had in mind.

> 
> 6. Section 4.3.4 needs clarification and more details. 

I beleve this text was submitted by somebody without details. I am
open to proposed text to expand this section. Alternately, I am open
to eliminating this section.

> 
> 7. I believe that some of the issues raised in 4.6 go to a level of
> detail beyond the other classes of management  operations and 
> should be
> left for appropriate data models or protocol design documents.
Unless
> there are some generic recommendations issues like maximal values of
> counters, behavior at rollout, persistency and 
> discontinuities should be
> out of scope. I would rather expect from a protocol document 
> to identify
> what are the principal performance factors that need to be looked at
> when measuring the efficiency of the protocol implementations. 

I eliminated some text and expanded other text. I do think that
discussing persistence of the information (not necessarily just
counters) is something the protocol designers should consider if it is
relevant to the managed protocol. I think this is part of the
information model, not just the data model.

> 
> 8.  I agree to a large extent to Juergen's DISCUSS. It may be 
> better to
> shorten this section, provide a crisp recommendation to look at the
> existing standard track MIB modules, and move the rest of the 
> section in
> an Annex. 

The Juergen discuss you reference I assume is the one in section 6:
[DISCUSS: JS: The weakest part of the document is IMHO section 6. It
is not clear to me what David's intention were here; sometimes he
gives general advise while at other places he kind of surveys data
models and such things. I am also not sure all the stuff listed there
is actually useful to list; for example, has anybody ever deployed the
technology which came out of the snmpconf working group? So we need to
be more selective and probably also organize our pointers based on the
protocol layer people are working on (transmission specific MIB
modules are kind of widely used, people managing application servers
usually do not use much of SNMP; the IETF application management MIBs
we have produced have not gained large deployments as far as I can
tell). ]

Juergen commented in Section 5: "what I really like, the text
discusses for which applications they were designed or already
successfully deployed. I like to perhaps see even stronger
guidelines;"

My intention in Section 6 is similar. I think we should identify which
data models exist already, what they were designed for, and whether
they have been implemented and deployed. I said in section 6 that
Section 6 should only include data models that have reached Draft
Standard or better, and Proposed Standard should be listed in an
appendix. Some of the data models in Section 6 are only PS, and need
to be moved. Unfortunately, we stopped advancing MIB modules through
the standards-track, so the DS vs. PS is no longer a valid indicator
of implementation and deployment.

I think it is very important to identify which data models we
recommend and which we do not, and if not, then why they are not
recommended. 

I tried sorting by FCAPS to reflect their purpose; JS suggests sorting
by layer.
I tried sorting by layer when creating recommendations for Enterasys,
and not all MIB modules are layer-specific, just as all MIB modules
are not purpose-specific either. I am certainly willing to try to sort
by layer.

You suggest a crisp recommendation to look at standards-track data
models. I think that is way inadequate. 

We offer a tremendous number of MIB modules, most of which are at PS,
and we have no further recommendations about which are widely
implemented and deployed, which are not recommended, and which are
simply too new to know if they are useful. The many MIB modues we
offer model many different things, and even "experts" in SNMP don't
know what is in every MIB module without research. If somebody that is
not a management expert wants to know if there is a MIB module that
provides the ability to monitor or control some feature such as
memory, they cannot search for "MIB memory" in the RFC search engine
and find the HOST-RESOURCES-MIB. If they do manage to find it through
other means, they cannot tell whether this is a good MIB to use to
model the types of memory they are considering (such as blade-specific
memory in a router chassis).

I think we should provide some real **guidance** about which existing
data models cover which features, and whether the data model is
recommended.

> 
> 9. It may be useful to include in Section 7.1 a bulleted list of the
> issues that may be included in the Manageability and 
> Operations sections
> of IETF documents with the observation that this list is provided
for
> guidance and document authors may pick what is relevant for their
> document. 

I don't understand the edits. What bullets did you have in mind?
The appendix is intended to contain a checklist. Would that be the
same as your bulleted list?
I think the observation that authors may pick what they consider
relevant should be an observation of the IESG or of an agreed-to
review requirements document, not this document. This document gives
guidelines for what to consdier, and I think every aspect should be
considered, even if they choose not to include discussion of every
aspect.

> 
> Thanks and Regards,
> 
> Dan
> 
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www1.ietf.org/mailman/listinfo/opsawg
> 




_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Tue Nov 13 17:43:08 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Is4TJ-00012c-4r; Tue, 13 Nov 2007 17:43:05 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Is4TI-00012N-Cs
	for opsawg-confirm+ok@megatron.ietf.org; Tue, 13 Nov 2007 17:43:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Is4TH-00010T-HX
	for opsawg@ietf.org; Tue, 13 Nov 2007 17:43:03 -0500
Received: from exprod7og105.obsmtp.com ([64.18.2.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Is4TE-0006Io-Ow
	for opsawg@ietf.org; Tue, 13 Nov 2007 17:43:03 -0500
Received: from source ([66.129.224.36]) by exprod7ob105.postini.com
	([64.18.6.12]) with SMTP; Tue, 13 Nov 2007 14:42:55 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Nov 2007 14:35:04 -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 lADMZ3n57259;
	Tue, 13 Nov 2007 14:35:04 -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 lADMW5aL023186;
	Tue, 13 Nov 2007 22:32:05 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200711132232.lADMW5aL023186@idle.juniper.net>
To: "David Harrington" <ietfdbh@comcast.net>
Subject: Re: [OPSAWG] XSDMI 
In-reply-to: <0c1101c8263e$cd3e0200$6502a8c0@china.huawei.com> 
Date: Tue, 13 Nov 2007 17:32:05 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 13 Nov 2007 22:35:04.0230 (UTC)
	FILETIME=[6F51F460:01C82645]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

"David Harrington" writes:
>I do not like abdicating all responsibility to a closed design team to
>make the decisions for the IETF.

I don't think we're asking for that, we've just burning
the midnight oil trying to get the YANG spec out.  Now
we're finishing up tools and such.  More will be available
shortly.

>Are all your design decision based on
>achieving vendor-neutrality, or are some decisions favorable to the
>existing implementations of certain vendors?

I think the group has done an incredible job of designing YANG with
the benefit of hindsight on existing projects, with foresight toward
future uses, and with vision for the growth of NETCONF.

>Are any of the designs
>encumbered by IPR?

No.

>Are you making decisions to trade away some feature
>that others may want without even consulting those who might be
>impacted by the decision?

Absolutely.  That's the purpose of using a small design group.  Well
considered design decisions without consulting the entire population.

>If YANG
>can deliver on its promises of a viable solution, and the industry
>accepts it, I have no issue with deprecating XSDMI. But I do not want
>to **not** do XSDMI, and not have that point of comparison, just
>because you promise a better solution.

Cool.  Take a read of the spec, and we can sit down and walk
thru features point by point in Vancouver.

>I think YANG and SMI are in
>different applicability spaces.

I guess I'm confused about what space XSDMI is aiming for then.
Who is your target audience?  What protocol(s) will use it?

Thanks,
 Phil


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Tue Nov 13 17:45:50 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Is4Vx-0004HO-Ta; Tue, 13 Nov 2007 17:45:49 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Is4Vw-0004G5-IY
	for opsawg-confirm+ok@megatron.ietf.org; Tue, 13 Nov 2007 17:45:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Is4Vw-0004Fx-8k
	for opsawg@ietf.org; Tue, 13 Nov 2007 17:45:48 -0500
Received: from hermes.jacobs-university.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Is4Vs-0006LZ-R4
	for opsawg@ietf.org; Tue, 13 Nov 2007 17:45:48 -0500
Received: from localhost (demetrius.jacobs-university.de [212.201.44.32])
	by hermes.jacobs-university.de (Postfix) with ESMTP id EEDC58A165;
	Tue, 13 Nov 2007 23:45:43 +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 27287-01; Tue, 13 Nov 2007 23:45:39 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133])
	by hermes.jacobs-university.de (Postfix) with ESMTP id 4031C86668;
	Tue, 13 Nov 2007 23:45:39 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501)
	id 352873E10C3; Tue, 13 Nov 2007 23:45:38 +0100 (CET)
Date: Tue, 13 Nov 2007 23:45:38 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: David Harrington <ietfdbh@comcast.net>
Subject: Re: [OPSAWG] XSDMI
Message-ID: <20071113224538.GA3646@elstar.local>
Mail-Followup-To: David Harrington <ietfdbh@comcast.net>,
	'Phil Shafer' <phil@juniper.net>, opsawg@ietf.org
References: <200711131713.lADHDAmR021241@idle.juniper.net>
	<0c1101c8263e$cd3e0200$6502a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0c1101c8263e$cd3e0200$6502a8c0@china.huawei.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@jacobs-university.de
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

On Tue, Nov 13, 2007 at 04:47:33PM -0500, David Harrington wrote:
 
> If there are SMI->YANG and YANG->XSD tools, then why aren't you
> publishing the specs and the output so we can see the translations so
> we can compare them? If yours are better than ours, which may be the
> case, then by all means we can try to be compatible starting now, but
> we have not seen your encodings; we cannot start trying to be
> compatible until you do publish your encodings.

Get the latest libsmi sources and run smidump -f yang to turn all your
MIB modules into yang. There is currently no specification how this is
done - just running code. ;-) For the yang to xsd translation, there
is a running implementation as well, but it is not yet public. Please
give us a few more days; working out the details of the language,
writing a specification, implementing tools, bug fixing tools, dealing
with IETF decision bodies, preparing slide ware, ... all takes time
and energy.
 
> I do not like abdicating all responsibility to a closed design team to
> make the decisions for the IETF. Are all your design decision based on
> achieving vendor-neutrality, or are some decisions favorable to the
> existing implementations of certain vendors? Are any of the designs
> encumbered by IPR? Are you making decisions to trade away some feature
> that others may want without even consulting those who might be
> impacted by the decision?

A clear "no" to all your concerns. Starting with a small group of
technical people was the only way to get this going and we are now in
the process of putting all details and implementations on the table
for consideration by the IETF and the NETCONF community. There is no
hidden agenda.

/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/>


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Wed Nov 14 07:51:27 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IsHiI-0005RC-JE; Wed, 14 Nov 2007 07:51:26 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IsHiH-0005Oi-6X
	for opsawg-confirm+ok@megatron.ietf.org; Wed, 14 Nov 2007 07:51:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IsHiB-00059Q-98
	for opsawg@ietf.org; Wed, 14 Nov 2007 07:51:19 -0500
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IsHi8-0000JW-Mi
	for opsawg@ietf.org; Wed, 14 Nov 2007 07:51:19 -0500
X-IronPort-AV: E=Sophos;i="4.21,416,1188792000"; d="scan'208";a="78409681"
Received: from 5.6.8.135.in-addr.arpa (HELO nj300815-nj-erheast.avaya.com)
	([198.152.6.5])
	by nj300815-nj-outbound.avaya.com with ESMTP; 14 Nov 2007 07:51:13 -0500
X-IronPort-AV: E=Sophos;i="4.21,416,1188792000"; d="scan'208";a="124809989"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	14 Nov 2007 07:51:13 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [OPSAWG] Some comments
	ondraft-ietf-opsawg-operations-and-management-00
Date: Wed, 14 Nov 2007 13:50:50 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A04615D43@307622ANEX5.global.avaya.com>
In-Reply-To: <0c1201c8263e$e603dda0$6502a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] Some comments
	ondraft-ietf-opsawg-operations-and-management-00
Thread-Index: AcgmAnvf+4eVkLVMT8Gk5uokMR1fHgAJIdmQACULZ+A=
References: <EDC652A26FB23C4EB6384A4584434A04615969@307622ANEX5.global.avaya.com>
	<0c1201c8263e$e603dda0$6502a8c0@china.huawei.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "David Harrington" <ietfdbh@comcast.net>,
	<opsawg@ietf.org>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: 
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

In-line.=20

A lot of good and agreed text was deleted.=20

Dan


=20
=20

> -----Original Message-----
> From: David Harrington [mailto:ietfdbh@comcast.net]=20
> This DISCUSS text captured somebody else's wording; that was=20
> not my example. I would like to see a succinct set of=20
> guidelines. I think fragmentation would hurt the utility of=20
> such guidelines. I can see separating the survey of existing=20
> protocols and data models from the guidelines to keep the=20
> size down, and to distinguish the purpose of the=20
> "considerations" from the "survey of existing".
>=20
> (Boy, am I the wrong editor for succinct ;-) Suggestions=20
> highly welcome for how to make the guidelines and discussions=20
> more succinct.

One possible suggestion was made already I believe - keep the core of
the recommendations in the body of the RFC and move the survey of
existing protocols and data models to Annexes. This has the advantage of
keeping all in one document.=20


> >=20
> > 4. Section 3.5 seems to limit the impact on network operation only
> to
> > network traffic or devices. I believe that it should consider also
> > impact on applications and registries, for example DNS=20
> > entries, or size
> > of routing tables.=20
>=20
> I added your comment about what should be considered. Additional text
> and detail welcome.

The impact on performance may also be noted - increased delay or jitter
in real-time traffic applications, or response time in client-server
applications when encryption or filtering are applied.=20

I am sure there are other examples which operators may point to.=20

>=20
> Done. I understand the distinction between notifications and polling.
> However, I am not sure what you had in mind with the hierarchy of
> faults. I wrote some text, but it may not be what you had in mind.

I need to see that text :-) What I had in mind is fault propagation and
aggregated status indicators based on concatenation of propagated faults
from a given domain or device.=20

>=20
> >=20
> > 6. Section 4.3.4 needs clarification and more details.=20
>=20
> I beleve this text was submitted by somebody without details. I am
> open to proposed text to expand this section. Alternately, I am open
> to eliminating this section.

I would not mind eliminating rather than leaving in something which is
not clear enough.=20



> You suggest a crisp recommendation to look at standards-track data
> models. I think that is way inadequate.=20
>=20
> We offer a tremendous number of MIB modules, most of which are at PS,
> and we have no further recommendations about which are widely
> implemented and deployed, which are not recommended, and which are
> simply too new to know if they are useful. The many MIB modues we
> offer model many different things, and even "experts" in SNMP don't
> know what is in every MIB module without research. If somebody that is
> not a management expert wants to know if there is a MIB module that
> provides the ability to monitor or control some feature such as
> memory, they cannot search for "MIB memory" in the RFC search engine
> and find the HOST-RESOURCES-MIB. If they do manage to find it through
> other means, they cannot tell whether this is a good MIB to use to
> model the types of memory they are considering (such as blade-specific
> memory in a router chassis).
>=20
> I think we should provide some real **guidance** about which existing
> data models cover which features, and whether the data model is
> recommended.

I was probably not clear enough, my 'crisp' recommendation was not for
all MIB documents that happened to reach standards track but for a
selected handful of useful ones. We are probably in agreement.=20


>=20
> >=20
> > 9. It may be useful to include in Section 7.1 a bulleted list of the
> > issues that may be included in the Manageability and=20
> > Operations sections
> > of IETF documents with the observation that this list is provided
> for
> > guidance and document authors may pick what is relevant for their
> > document.=20
>=20
> I don't understand the edits. What bullets did you have in mind?
> The appendix is intended to contain a checklist. Would that be the
> same as your bulleted list?

Yes, I missed the appendix. It's good as it is.=20


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Thu Nov 15 10:47:27 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IsgwB-000534-8p; Thu, 15 Nov 2007 10:47:27 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IsgwA-00051z-RA
	for opsawg-confirm+ok@megatron.ietf.org; Thu, 15 Nov 2007 10:47:26 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Isgw4-0004il-Vh
	for opsawg@ietf.org; Thu, 15 Nov 2007 10:47:21 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Isgw4-0001rV-NQ
	for opsawg@ietf.org; Thu, 15 Nov 2007 10:47:20 -0500
Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42])
	by ns3.neustar.com (Postfix) with ESMTP id 62F62175C8;
	Thu, 15 Nov 2007 15:47:20 +0000 (GMT)
Received: from mirror by ietf.org with local (Exim 4.43)
	id 1Isgw3-0002Rd-TJ; Thu, 15 Nov 2007 10:47:19 -0500
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: dharrington@huawei.com
From: IETF I-D Submission Tool <idsubmission@ietf.org>
Message-Id: <E1Isgw3-0002Rd-TJ@ietf.org>
Date: Thu, 15 Nov 2007 10:47:19 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: opsawg@ietf.org
Subject: [OPSAWG] New Version Notification for 
 draft-ietf-opsawg-operations-and-management-01 
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org


A new version of I-D, draft-ietf-opsawg-operations-and-management-01.txt has been successfuly submitted by David Harrington and posted to the IETF repository.

Filename:	 draft-ietf-opsawg-operations-and-management
Revision:	 01
Title:		 Guidelines for Considering Operations and Management of New Protocols
Creation_date:	 2007-11-14
WG ID:		 opsawg
Number_of_pages: 39

Abstract:
New protocols or protocol extensions are best designed with due
consideration of operations and management issues related to the
protocol.  Retrofitting operations and management recommendations to
protocols is sub-optimal.  The purpose of this document is to provide
guidance to authors and reviewers of documents defining new protocols
or protocol extensions, covering aspects of operations and management
that should be considered.
                                                                                  


The IETF Secretariat.




_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Thu Nov 15 10:55:26 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ish3u-0001CN-GH; Thu, 15 Nov 2007 10:55:26 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IsgzB-000166-Ou
	for opsawg-confirm+ok@megatron.ietf.org; Thu, 15 Nov 2007 10:50:33 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IsgzB-00012z-Ar; Thu, 15 Nov 2007 10:50:33 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IsgzA-0001x1-Ua; Thu, 15 Nov 2007 10:50:33 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 97040175C8;
	Thu, 15 Nov 2007 15:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Isgyg-00017p-4w; Thu, 15 Nov 2007 10:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Isgyg-00017p-4w@stiedprstage1.ietf.org>
Date: Thu, 15 Nov 2007 10:50:02 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
X-Mailman-Approved-At: Thu, 15 Nov 2007 10:55:25 -0500
Cc: opsawg@ietf.org
Subject: [OPSAWG] I-D
	Action:draft-ietf-opsawg-operations-and-management-01.txt 
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operations and Management Area Working Group Working Group of the IETF.


	Title           : Guidelines for Considering Operations and Management of New Protocols
	Author(s)       : D. Harrington
	Filename        : draft-ietf-opsawg-operations-and-management-01.txt
	Pages           : 39
	Date            : 2007-11-14

New protocols or protocol extensions are best designed with due
consideration of operations and management issues related to the
protocol.  Retrofitting operations and management recommendations to
protocols is sub-optimal.  The purpose of this document is to provide
guidance to authors and reviewers of documents defining new protocols
or protocol extensions, covering aspects of operations and management
that should be considered.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-opsawg-operations-and-management-01.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-opsawg-operations-and-management-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-opsawg-operations-and-management-01.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-11-15104717.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-opsawg-operations-and-management-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-opsawg-operations-and-management-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-11-15104717.I-D\@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg

--NextPart--





From opsawg-bounces@ietf.org Thu Nov 15 14:59:19 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iskru-0006F5-J4; Thu, 15 Nov 2007 14:59:18 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Iskrt-0006AV-0Q
	for opsawg-confirm+ok@megatron.ietf.org; Thu, 15 Nov 2007 14:59:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Iskrs-0006AK-Mr
	for opsawg@ietf.org; Thu, 15 Nov 2007 14:59:16 -0500
Received: from smtp122.sbc.mail.sp1.yahoo.com ([69.147.64.95])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Iskrp-0004dc-3s
	for opsawg@ietf.org; Thu, 15 Nov 2007 14:59:16 -0500
Received: (qmail 62592 invoked from network); 15 Nov 2007 19:59:12 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@67.127.99.221
	with plain)
	by smtp122.sbc.mail.sp1.yahoo.com with SMTP; 15 Nov 2007 19:59:12 -0000
X-YMail-OSG: 8hb6cC8VM1lAqybpVzg0KnXL_9J.OuQHsNMjXFWbjP11JR1h
Message-ID: <473CA543.7070500@andybierman.com>
Date: Thu, 15 Nov 2007 12:00:03 -0800
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>, 'Phil Shafer' <phil@juniper.net>,
	opsawg@ietf.org
Subject: Re: [OPSAWG] XSDMI
References: <200711131713.lADHDAmR021241@idle.juniper.net>	<0c1101c8263e$cd3e0200$6502a8c0@china.huawei.com>
	<20071113224538.GA3646@elstar.local>
In-Reply-To: <20071113224538.GA3646@elstar.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: 
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Juergen Schoenwaelder wrote:
> On Tue, Nov 13, 2007 at 04:47:33PM -0500, David Harrington wrote:
>  
>> If there are SMI->YANG and YANG->XSD tools, then why aren't you
>> publishing the specs and the output so we can see the translations so
>> we can compare them? If yours are better than ours, which may be the
>> case, then by all means we can try to be compatible starting now, but
>> we have not seen your encodings; we cannot start trying to be
>> compatible until you do publish your encodings.
> 
> Get the latest libsmi sources and run smidump -f yang to turn all your
> MIB modules into yang. There is currently no specification how this is
> done - just running code. ;-) For the yang to xsd translation, there
> is a running implementation as well, but it is not yet public. Please
> give us a few more days; working out the details of the language,
> writing a specification, implementing tools, bug fixing tools, dealing
> with IETF decision bodies, preparing slide ware, ... all takes time
> and energy.
> 

I can concur with Juergen that writing a good YANG to XSD translator
is hard enough.  Writing down every algorithm is very difficult.
Free tools should be good enough for now, but I agree with Dave
that a standard XSD representation of SMIv2 is needed, and the
YANG to XSD translation needs to match, for all SMIv2 TCs and types.

I think there is a big difference between alignment between
SMIv2 and YANG data types, and aligning the SMIv2 and YANG languages.
The latter is a non-goal, and translation from YANG to SMIv2 is
not supportable.

There is a significant issue created by romascanu-datatypes,
because it is a 'best hits' collection of TCs from other MIB modules.
I would much rather have an architecture based on the SMI to YANG
to XSD conversion path, in which the original modules are preserved.
Creating a best-hits module is going to create import conflicts if
the original modules are ever converted to XSD as well.


>> I do not like abdicating all responsibility to a closed design team to
>> make the decisions for the IETF. Are all your design decision based on
>> achieving vendor-neutrality, or are some decisions favorable to the
>> existing implementations of certain vendors? Are any of the designs
>> encumbered by IPR? Are you making decisions to trade away some feature
>> that others may want without even consulting those who might be
>> impacted by the decision?
> 
> A clear "no" to all your concerns. Starting with a small group of
> technical people was the only way to get this going and we are now in
> the process of putting all details and implementations on the table
> for consideration by the IETF and the NETCONF community. There is no
> hidden agenda.

Nobody thinks the IETF should rubber-stamp YANG.
IMO, YANG should be published as an Experimental RFC ASAP,
to get some experience with the DML and to develop some
more free tools.

The standards-track path can be separate, and be as
slow and deliberate as necessary.  By the time the IETF
figures out what to do about NETCONF and XSD, running code
will probably overtake events anyway.

> 
> /js
> 

Andy




_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Thu Nov 15 17:47:57 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IsnV6-0005M6-AD; Thu, 15 Nov 2007 17:47:56 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IsnV5-0005L0-Nn
	for opsawg-confirm+ok@megatron.ietf.org; Thu, 15 Nov 2007 17:47:55 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IsnV5-0005GM-5s
	for opsawg@ietf.org; Thu, 15 Nov 2007 17:47:55 -0500
Received: from qmta03.emeryville.ca.mail.comcast.net ([76.96.30.32])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IsnV4-0003Ls-71
	for opsawg@ietf.org; Thu, 15 Nov 2007 17:47:55 -0500
Received: from OMTA10.emeryville.ca.mail.comcast.net ([76.96.30.28])
	by QMTA03.emeryville.ca.mail.comcast.net with comcast
	id D7a91Y00F0cQ2SL0A0J000; Thu, 15 Nov 2007 22:47:56 +0000
Received: from Harrington73653 ([24.128.104.207])
	by OMTA10.emeryville.ca.mail.comcast.net with comcast
	id DAnp1Y0094UVsHU0800000; Thu, 15 Nov 2007 22:47:55 +0000
X-Authority-Analysis: v=1.0 c=1 a=LYOn7yqr53GihZGlTDYA:9
	a=OUyNIwInDzEEcJSsyYAA:7 a=9RjAGQmW47sZbjzhgTIlJIItusgA:4
	a=gJcimI5xSWUA:10
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Andy Bierman'" <ietf@andybierman.com>,
	"'Phil Shafer'" <phil@juniper.net>, <opsawg@ietf.org>
References: <200711131713.lADHDAmR021241@idle.juniper.net>	<0c1101c8263e$cd3e0200$6502a8c0@china.huawei.com>
	<20071113224538.GA3646@elstar.local>
	<473CA543.7070500@andybierman.com>
Subject: RE: [OPSAWG] XSDMI
Date: Thu, 15 Nov 2007 17:47:47 -0500
Message-ID: <0f5c01c827d9$8bfcdbd0$6502a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <473CA543.7070500@andybierman.com>
Thread-Index: Acgnwf5g+qu55rM4T2yXmlSWceh6tQACtrWw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Cc: 
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

 

> I can concur with Juergen that writing a good YANG to XSD translator
> is hard enough.  Writing down every algorithm is very difficult.
> Free tools should be good enough for now, but I agree with Dave
> that a standard XSD representation of SMIv2 is needed, and the
> YANG to XSD translation needs to match, for all SMIv2 TCs and types.

I agree that a standard XSD representation of SMIv2 is needed, but I
do not fully agree that the YANG-to-XSD needs to match the XSDMI
transaltions.

While it would appear beneficial for all management interfaces to use
the same datatypes, experience has taught us this is not necessarily
true. That is why Netconf is looking to use XML/XSD instead of SMI,
and why RADIUS and Diameter use named attributes, and IPFIX uses IEs,
and syslog uses SDEs, and so on. Different purposes may benefit from
different types of data models, and different datatypes for the same
concept.  

At the same time, two different standard protocols may use the same
basic encoding rules, such as ASN.1 or XML, without having to use
exactly the same language for modeling. 

We learned that in a smaller way in SNMPv2. We started out believeing
that there should be one MIB for SNMPv2 and all aspects of SNMPv2
should use those same objects. But as we got into more detailed
design, we found that actually the different-purpose portions of
SNMPv2 had slightly different assumptions about the managed objects in
the MIB, and that caused conflicts as people working on different
parts tried to slightly redefine the managed object, and caused other
parts to no longer work properly. In SNMPv3, we deliberately chose to
separate the MIB module for access control from the MIB for
authentication, even though both MIB modules included the name of the
authenticated principal.

There are multiple use cases for an XSD translation of SMIv2. I do not
believe that YANG should be constrained to produce XSD that will be
viable for all use cases. I think YANG should focus on YANG-XSD
translations that are useful for configuration, including new data
modeling approaches for configuration with new aspects such as nested
structures. 

If romascanu-netconf-datatypes had not been proposed first in the
netconf community, we could have had these translations to XSD done
years ago. But any data modeling work, even for non-netconf use cases
was held up by "wait until the netconf protocol is finshed"; now you
want "wait until the YANG tools are finished, and then wait until we
get around to documenting the algorithms, and then bring the specs to
the IETF, so we can debate any variations used by different tools, and
then go through the whole standards process to get the IETF stamp of
approval." 

If there are use cases that are not germane to Netconf configuration,
why must we wait for YANG?

Think of a manager station that uses an XML-compatible database. The
manager application designers want to use XSD to validate SMIv2 values
received from SNMP agents before it puts those values into its
XML-based records. This saves them the cost and effort of developing
SMI datatype validation routines, since they can use the XSD
validation routines of their database. 

They need the XSD to accurately reflect the original semantics that
were specified in SMIv2. It would be useful to have the IETF provide
standard XSD for those validations, since we have the expertise about
the original semantics of the SMIv2 datatypes, and we can save people
the cost of figuring out and debugging the SMI-XSD translations
themselves.

And they shouldn't need a netconf-specific YANG toolkit to get these
translations.

> 
> I think there is a big difference between alignment between
> SMIv2 and YANG data types, and aligning the SMIv2 and YANG
languages.
> The latter is a non-goal, and translation from YANG to SMIv2 is
> not supportable.
> 
> There is a significant issue created by romascanu-datatypes,
> because it is a 'best hits' collection of TCs from other MIB
modules.
> I would much rather have an architecture based on the SMI to YANG
> to XSD conversion path, in which the original modules are preserved.
> Creating a best-hits module is going to create import conflicts if
> the original modules are ever converted to XSD as well.

Why don't we just have XSDMI use a prefix of smi: for its translated
datatypes, and have YANG use a prefix of yang: for its XSD output?
Wouldn't that solve the imports problem you raise?

> 
> 
> >> I do not like abdicating all responsibility to a closed 
> design team to
> >> make the decisions for the IETF. Are all your design 
> decision based on
> >> achieving vendor-neutrality, or are some decisions favorable to
the
> >> existing implementations of certain vendors? Are any of the
designs
> >> encumbered by IPR? Are you making decisions to trade away 
> some feature
> >> that others may want without even consulting those who might be
> >> impacted by the decision?
> > 
> > A clear "no" to all your concerns. Starting with a small group of
> > technical people was the only way to get this going and we 
> are now in
> > the process of putting all details and implementations on the
table
> > for consideration by the IETF and the NETCONF community. There is
no
> > hidden agenda.
> 
> Nobody thinks the IETF should rubber-stamp YANG.
> IMO, YANG should be published as an Experimental RFC ASAP,
> to get some experience with the DML and to develop some
> more free tools.
> 
> The standards-track path can be separate, and be as
> slow and deliberate as necessary.  By the time the IETF
> figures out what to do about NETCONF and XSD, running code
> will probably overtake events anyway.

XSDMI is not about NETCONF!!!!
It is about providing XSD to accurately reflect the original semantics
that were specified in SMIv2, so people can utilize the XSD to
validate SMIv2 data that may not have anything to do with NETCONF.

> 
> > 
> > /js
> > 
> 
> Andy
> 
> 
> 




_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Thu Nov 15 20:56:39 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IsqRi-00016Q-KJ; Thu, 15 Nov 2007 20:56:38 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IsqRh-00012e-3I
	for opsawg-confirm+ok@megatron.ietf.org; Thu, 15 Nov 2007 20:56:37 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IsqRg-00012J-GC
	for opsawg@ietf.org; Thu, 15 Nov 2007 20:56:36 -0500
Received: from smtp117.sbc.mail.sp1.yahoo.com ([69.147.64.90])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IsqRg-00054S-07
	for opsawg@ietf.org; Thu, 15 Nov 2007 20:56:36 -0500
Received: (qmail 773 invoked from network); 16 Nov 2007 01:56:35 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@67.127.99.221
	with plain)
	by smtp117.sbc.mail.sp1.yahoo.com with SMTP; 16 Nov 2007 01:56:34 -0000
X-YMail-OSG: 0WBogzAVM1kUecTwnZadmy0F0zQmblwFXag74KpF1IAVv1LM
Message-ID: <473CF93B.9040205@andybierman.com>
Date: Thu, 15 Nov 2007 17:58:19 -0800
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
Subject: Re: [OPSAWG] XSDMI
References: <200711131713.lADHDAmR021241@idle.juniper.net>	<0c1101c8263e$cd3e0200$6502a8c0@china.huawei.com>
	<20071113224538.GA3646@elstar.local>
	<473CA543.7070500@andybierman.com>
	<0f5c01c827d9$8bfcdbd0$6502a8c0@china.huawei.com>
In-Reply-To: <0f5c01c827d9$8bfcdbd0$6502a8c0@china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

David Harrington wrote:
>  
> 
>> I can concur with Juergen that writing a good YANG to XSD translator
>> is hard enough.  Writing down every algorithm is very difficult.
>> Free tools should be good enough for now, but I agree with Dave
>> that a standard XSD representation of SMIv2 is needed, and the
>> YANG to XSD translation needs to match, for all SMIv2 TCs and types.
> 
> I agree that a standard XSD representation of SMIv2 is needed, but I
> do not fully agree that the YANG-to-XSD needs to match the XSDMI
> transaltions.
> 

It is less work to standardize a TC once.
In every case, the semantics (DESCRIPTION clause) are
cut and pasted from SMIv2 into the XML data model.  The only issues
are syntax-related.  Hopefully, the syntax differences can
be resolved.  If not, then 2 versions of the same TC would
be the result, hopefully with different names.

 >....
>> The standards-track path can be separate, and be as
>> slow and deliberate as necessary.  By the time the IETF
>> figures out what to do about NETCONF and XSD, running code
>> will probably overtake events anyway.
> 
> XSDMI is not about NETCONF!!!!
> It is about providing XSD to accurately reflect the original semantics
> that were specified in SMIv2, so people can utilize the XSD to
> validate SMIv2 data that may not have anything to do with NETCONF.
> 


I keep hearing about the mystery protocols behind door #2.
What other protocols besides NETCONF are relevant here?

There is nothing NETCONF-specific at all about any of
the SMIv2 TCs in the YANG I-D.  A few TCs in romascanu-datatypes
are SNMP-specific, such as RowStatus.  It is unlikely that
a RowStatus object would have relevance outside the SNMP protocol.

However, a set of derived types is not even close to the
same thing as a data model.  Having a standard InetAddress
doesn't help that much unless there are standard objects
using that type.  Say one object is for the DHCP server address
and another is the default gateway address.  Just knowing
that they are both InetAddresses doesn't help much without
the data model.



>>> /js
>>>
>> Andy


Andy




_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 16 02:58:02 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Isw5R-0007yn-Lg; Fri, 16 Nov 2007 02:58:01 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Isw5P-0007qo-44
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 16 Nov 2007 02:57:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Isw5J-0007bA-1i
	for opsawg@ietf.org; Fri, 16 Nov 2007 02:57:53 -0500
Received: from hermes.jacobs-university.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Isw5G-0000oR-7d
	for opsawg@ietf.org; Fri, 16 Nov 2007 02:57:53 -0500
Received: from localhost (demetrius.jacobs-university.de [212.201.44.32])
	by hermes.jacobs-university.de (Postfix) with ESMTP id 13BAF8A186;
	Fri, 16 Nov 2007 08:57:49 +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 20795-04; Fri, 16 Nov 2007 08:57:44 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133])
	by hermes.jacobs-university.de (Postfix) with ESMTP id 36E7B8A142;
	Fri, 16 Nov 2007 08:57:41 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501)
	id DB24F3E45BB; Fri, 16 Nov 2007 08:57:40 +0100 (CET)
Date: Fri, 16 Nov 2007 08:57:40 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: David Harrington <ietfdbh@comcast.net>
Subject: Re: [OPSAWG] XSDMI
Message-ID: <20071116075740.GA16015@elstar.local>
Mail-Followup-To: David Harrington <ietfdbh@comcast.net>,
	'Andy Bierman' <ietf@andybierman.com>,
	'Phil Shafer' <phil@juniper.net>, opsawg@ietf.org
References: <200711131713.lADHDAmR021241@idle.juniper.net>
	<0c1101c8263e$cd3e0200$6502a8c0@china.huawei.com>
	<20071113224538.GA3646@elstar.local>
	<473CA543.7070500@andybierman.com>
	<0f5c01c827d9$8bfcdbd0$6502a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0f5c01c827d9$8bfcdbd0$6502a8c0@china.huawei.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@jacobs-university.de
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

On Thu, Nov 15, 2007 at 05:47:47PM -0500, David Harrington wrote:
 
> I agree that a standard XSD representation of SMIv2 is needed, but I
> do not fully agree that the YANG-to-XSD needs to match the XSDMI
> transaltions.

It does not have to, but it is really bad if it does not...

> Think of a manager station that uses an XML-compatible database. The
> manager application designers want to use XSD to validate SMIv2 values
> received from SNMP agents before it puts those values into its
> XML-based records. This saves them the cost and effort of developing
> SMI datatype validation routines, since they can use the XSD
> validation routines of their database. 

I assume this manager station will have lots of fun once SMIv2 data
comes also in via NETCONF and the XML representation is different.
The IETF is about interoperability and multiple ways to represent the
same data has so far been considered not a good idea to achieve
interoperability.

/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/>


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Fri Nov 16 12:53:05 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1It5NI-0007Ks-LV; Fri, 16 Nov 2007 12:53:05 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1It5NH-0007J9-Pw
	for opsawg-confirm+ok@megatron.ietf.org; Fri, 16 Nov 2007 12:53:03 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1It5NH-0007GD-6I
	for opsawg@ietf.org; Fri, 16 Nov 2007 12:53:03 -0500
Received: from smtp105.sbc.mail.mud.yahoo.com ([68.142.198.204])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1It5NG-0000yu-Gl
	for opsawg@ietf.org; Fri, 16 Nov 2007 12:53:03 -0500
Received: (qmail 9431 invoked from network); 16 Nov 2007 17:53:01 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@67.127.99.221
	with plain)
	by smtp105.sbc.mail.mud.yahoo.com with SMTP; 16 Nov 2007 17:53:01 -0000
X-YMail-OSG: ja9DKnsVM1ntoQF_v61zBv4O2hkbK.oQlDES1KWOpGYpl.DG
Message-ID: <473DD8DA.40608@andybierman.com>
Date: Fri, 16 Nov 2007 09:52:26 -0800
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
Subject: Re: [OPSAWG] XSDMI
References: <200711131713.lADHDAmR021241@idle.juniper.net>	<0c1101c8263e$cd3e0200$6502a8c0@china.huawei.com>
	<20071113224538.GA3646@elstar.local>
	<473CA543.7070500@andybierman.com>
	<0f5c01c827d9$8bfcdbd0$6502a8c0@china.huawei.com>
In-Reply-To: <0f5c01c827d9$8bfcdbd0$6502a8c0@china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Hi Dave,

>>...
> While it would appear beneficial for all management interfaces to use
> the same datatypes, experience has taught us this is not necessarily
> true. That is why Netconf is looking to use XML/XSD instead of SMI,
> and why RADIUS and Diameter use named attributes, and IPFIX uses IEs,
> and syslog uses SDEs, and so on. Different purposes may benefit from
> different types of data models, and different datatypes for the same
> concept.  
> 
> At the same time, two different standard protocols may use the same
> basic encoding rules, such as ASN.1 or XML, without having to use
> exactly the same language for modeling. 
> 

I told the IESG I did not object to their no-YANG-BoF decision,
based on the NETCONF-only factor.  But it seems you are right.
Different protocol WGs are not encoding their data structures
the same way at all, and that is not likely to change.

YANG gets some of its power (like all app-specific DMLs)
by abstracting away, or hard-wiring, various aspects of
the protocol/application mapping.

In YANG, the data definitions are hard-wired
to be placed inside <config> parameters within NETCONF RPC
operations.  The rpc and notification definitions fit
within the <rpc> and <notification> PDUs, respectively.

When I said another protocol WG could do the work to
define how seemingly generic data structure definitions
(like list, container, leaf) fit within a different
protocol PDU structure, I didn't mean YANG should be generic.
(It is definitely OPS-NM specific, like SMIv2, because
network operators need to read and understand the data structures.)
I just meant that the IESG is right to be concerned
about too much WG overlap, and inventing too many
ways to do the same thing.

But now I do not think there is any overlap.
NETCONF needs a DML that ordinary people can read.
People who do not write code or protocols for a living,
but run networks for a living.  YANG is simple enough
to meet that requirement.  It is also powerful enough
to model even the most complex NETCONF configurations,
including runtime constraints via Xpath expressions,
extensible templates, and conditional object augmentation.


Andy



_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Tue Nov 20 07:17:25 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IuS2e-0000iO-IB; Tue, 20 Nov 2007 07:17:24 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IuS2c-0000iC-RG
	for opsawg-confirm+ok@megatron.ietf.org; Tue, 20 Nov 2007 07:17:22 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IuS2X-0000ho-D7
	for opsawg@ietf.org; Tue, 20 Nov 2007 07:17:17 -0500
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IuS2X-0000GS-3f
	for opsawg@ietf.org; Tue, 20 Nov 2007 07:17:17 -0500
X-IronPort-AV: E=Sophos;i="4.21,441,1188792000"; d="scan'208";a="85261985"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by co300216-co-outbound.avaya.com with ESMTP; 20 Nov 2007 07:17:14 -0500
X-IronPort-AV: E=Sophos;i="4.21,441,1188792000"; d="scan'208";a="126553874"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	20 Nov 2007 07:16:37 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 20 Nov 2007 13:16:14 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0464C275@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Preliminary agenda of the OPSAREA meeting in Vancouver - take 3
Thread-Index: AcgrbyUk3MCUm4o+RYqSdOu4oekY8Q==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <opsawg@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: [OPSAWG] Preliminary agenda of the OPSAREA meeting in Vancouver -
	take 3
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org


1. Note well, agenda bashing, note takers, blue sheets

2. Report from the NMRG workshop in the Netherlands (November 8-9) with
the topic of SNMP trace analysis - Dan Romascanu on behalf of Juergen
Schoenwaelder

3. Reorganization and extension of the OPS Directorate - Ron Bonica

4. Status of MIB2RDML work - Bob Natale

5. XML Schema Usage for NETCONF - Sharon Chisholm
http://www.ietf.org/internet-drafts/draft-chisholm-netconf-model-07.txt

6. Technical Discussion on the YANG data modeling language - David
Partain
http://www.ietf.org/internet-drafts/draft-bjorklund-netconf-yang-00.txt

7. Open microphone


=20


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Wed Nov 21 14:33:54 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IuvKb-0007DT-QQ; Wed, 21 Nov 2007 14:33:53 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IuvKY-0006a1-Nb
	for opsawg-confirm+ok@megatron.ietf.org; Wed, 21 Nov 2007 14:33:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IuvKS-0005uZ-3W
	for opsawg@ietf.org; Wed, 21 Nov 2007 14:33:44 -0500
Received: from newdev.eecs.harvard.edu ([140.247.60.212])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IuvKN-0000MP-Vo
	for opsawg@ietf.org; Wed, 21 Nov 2007 14:33:44 -0500
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501)
	id D6C5664EBF1; Wed, 21 Nov 2007 14:32:57 -0500 (EST)
To: opsawg@ietf.org
Message-Id: <20071121193257.D6C5664EBF1@newdev.eecs.harvard.edu>
Date: Wed, 21 Nov 2007 14:32:57 -0500 (EST)
From: sob@harvard.edu (Scott O. Bradner)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Subject: [OPSAWG] draft opsawg draft agenda
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org


DRAFT agenda - OPSAWG

at this point we have a short agenda -
we may add more to it by the cutoff next week

but, based on the list discussions, we may have plenty to talk about in any case

1.  Welcome, agenda, scribe, bluesheets
    
2. David Harrington
Datatypes for Netconf Data Models
   draft-romascanu-netconf-datatypes-03.txt
Using Smidump to Convert MIB to XSD 
   draft-li-mib-convert-00.txt


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Thu Nov 22 00:45:56 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iv4st-0002nj-MB; Thu, 22 Nov 2007 00:45:55 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Iv4ss-0002nS-GX
	for opsawg-confirm+ok@megatron.ietf.org; Thu, 22 Nov 2007 00:45:54 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Iv4ss-0002nK-4s
	for opsawg@ietf.org; Thu, 22 Nov 2007 00:45:54 -0500
Received: from umi.kikuken.org ([202.126.16.27] helo=ari.kikuken.org)
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1Iv4sq-0006EG-Tc
	for opsawg@ietf.org; Thu, 22 Nov 2007 00:45:53 -0500
Received: (qmail 8963 invoked from network); 22 Nov 2007 14:45:50 +0900
Received: from unknown (HELO localhost) (218.100.15.124)
	by umi.kikuken.org with SMTP; 22 Nov 2007 14:45:50 +0900
Date: Thu, 22 Nov 2007 14:45:52 +0900 (JST)
Message-Id: <20071122.144552.44275045.yu@kikuken.org>
To: opsawg@ietf.org
Subject: Re: [OPSAWG] agenda requests for opsawg in Vancouver
From: KIKUCHI Yutaka <yu@kikuken.org>
In-Reply-To: <20071108.132548.94837533.yu@kikuken.org>
References: <20071107034206.00F7961B682@newdev.eecs.harvard.edu>
	<20071108.132548.94837533.yu@kikuken.org>
Organization: Kochi Univ. of Tech.
X-Mailer: Mew version 4.2.53 on Emacs 22.0.50 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: zin@jaist.ac.jp, satoru@ft.solteria.net, nagami@inetcore.com
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Hi,

The chairs advised us that we should explain how the past suggestions
had been addressed here before the determination of the final agenda.

The following are suggestions and questions already we received
(not in the appearance order).
1. why tunnel specific?
2. when used? testing or all time?
3. reuse IPPM metrics, do not produce a new one
4. sequence number overhead, happens fragmentation
5. the use of "passive" seems not accurate
6. how this secured?
7. discusstion should be in IPPM

The last one has been discussed in the PMOL mailing list.
I am going to state the rest issues later.

Please see also for detail:
http://www1.ietf.org/mail-archive/web/opsawg/current/msg00015.html
http://www1.ietf.org/mail-archive/web/opsawg/current/msg00017.html
http://www1.ietf.org/mail-archive/web/opsawg/current/msg00018.html
http://www3.ietf.org/proceedings/07mar/minutes/opsarea.txt
http://www3.ietf.org/proceedings/07jul/minutes/opsawg.txt

http://www.ietf.org/internet-drafts/draft-kikuchi-tunnel-measure-req-02.txt
http://www.ietf.org/internet-drafts/draft-kikuchi-passive-measure-01.txt

-- Yu.

> Hi,
> 
> We would like to discuss about our I-D
> draft-kikuchi-tunnel-measure-req-02.txt
> ``Quality Measurement Requirements for Tunneling Protocols''.
> The newest version will be appeared later.
> 
> -- Best Regards, Yu.
> 
> > 
> > this is a first call for timeslots on the opsawg session in Vancouver
> > 
> > we are currently scheduled for tuesday afternoon from 1520 to 1720
> > 
> > Scott & Ted
> > 
> > 
> > 
> > _______________________________________________
> > OPSAWG mailing list
> > OPSAWG@ietf.org
> > https://www1.ietf.org/mailman/listinfo/opsawg
> > 
> 


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Thu Nov 22 04:58:52 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iv8pf-0008AC-Ra; Thu, 22 Nov 2007 04:58:51 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1Iv8pd-0008A0-Ou
	for opsawg-confirm+ok@megatron.ietf.org; Thu, 22 Nov 2007 04:58:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Iv8pX-00089S-A0
	for opsawg@ietf.org; Thu, 22 Nov 2007 04:58:43 -0500
Received: from umi.kikuken.org ([202.126.16.27] helo=ari.kikuken.org)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Iv8pS-0001nQ-VJ
	for opsawg@ietf.org; Thu, 22 Nov 2007 04:58:43 -0500
Received: (qmail 13135 invoked from network); 22 Nov 2007 18:58:36 +0900
Received: from unknown (HELO localhost) (218.100.15.124)
	by umi.kikuken.org with SMTP; 22 Nov 2007 18:58:36 +0900
Date: Thu, 22 Nov 2007 18:58:44 +0900 (JST)
Message-Id: <20071122.185844.68026528.yu@kikuken.org>
To: opsawg@ietf.org
From: KIKUCHI Yutaka <yu@kikuken.org>
In-Reply-To: <20071122.144552.44275045.yu@kikuken.org>
References: <20071107034206.00F7961B682@newdev.eecs.harvard.edu>
	<20071108.132548.94837533.yu@kikuken.org>
	<20071122.144552.44275045.yu@kikuken.org>
Organization: Kochi Univ. of Tech.
X-Mailer: Mew version 4.2.53 on Emacs 22.0.50 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: zin@jaist.ac.jp, satoru@ft.solteria.net, nagami@inetcore.com
Subject: [OPSAWG] tunnel quality measurement I-Ds
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Folks,

> I am going to state the rest issues later.

The main change of the structure from the original I-D
is splitting it into two I-Ds, one for the requirements
and the other for the metrics and measurement method.
The first two issues are related to the requirements draft
draft-kikuchi-tunnel-measure-req-02.txt.

> 1. why tunnel specific?

The original draft did not describe the purpose of
measurement well, so we had improved the description
of section 3 "Motivations". The most important point
is that TSPs must maintain each one of flows with SLA.

> 2. when used? testing or all time?

The point did not exist explicitly in the original draft,
so the newest version has an explicit description
in the second paragraph of section 4 "Requirements".

The answer is "all time". All time for every tunnels
that you want to OAM in the real networks.
This requires the mechanism should be very lightweight,
so we introduce a new metrics for measurement
described in draft-kikuchi-passive-measure-01.txt.

The next issue refer this draft.

> 3. reuse IPPM metrics, do not produce a new one

The draft proposes a measurement mechanism with
sequence numbers. For scalability and make it lightweight,
measuring egress routers have only one register
that keeps next number of incoming packets.
Therefore, the algorithm can detect that a flow
is whether in-sequence or out-of-sequence,
but cannot accurately determine error reasons.

If we use the metrics duplicate, loss and reordering
defined in IPPM, the proposed mechanism must not
work well with the metrics.

We had used the words "duplicate", "loss" and "reordering"
in the older draft, but this use has confused the reader
and cause misunderstanding, so we named different names
to the similar metrics as "dup-train", "skipping" and "astern".

See section 2 "Metrics" of draft-kikuchi-passive-measure-01.txt
to see the metrics definition, the difference
from the legacy metrics and the detail reason.

> 4. sequence number overhead, happens fragmentation

Yes, sequence number field makes headers long
and enlarged packets may fragment.

But this issue is mostly independent from our proposal.
We do not aim to extend existing protocols but
just use protocols that already have sequence numbers.

See detail in section 4.5 "Header Information" of the
requirements draft draft-kikuchi-tunnel-measure-req-02.txt.

> 5. the use of "passive" seems not accurate

The issue may come from our algorithm uses sequence number
that seems to inject some extra information for measurement.
I think this method is completely passive because of the same
reason above. The measurement mechanism does not inject
any information into flows.

> 6. how this secured?

This issue is discussed in the "Security Considerations" sections
of both I-Ds since the original version.

Of course fraud sequence numbers cause the measurement error.
But I think we should not prepare additional security armour.

The first reason is such the responsibility should be done
by less under layers. The second reason is that new armours
may make other security issues and security holes.

The third reason is that it is difficult to let a disordered
flow seems to be in-sequence. It might be possible to let
a ordering flow seems to be out-of-sequence though,
the operator can easily detect such a trouble with the flow.

The last reason is not described in the I-D yet.


One more issue.
http://www1.ietf.org/mail-archive/web/opsawg/current/msg00014.html

Yes, I followed the suggestion to write the latest version.


Thank you very much for reading my long message.
Please give us any advice, comments and questions.

-- Best regards, Yu.


> Hi,
> 
> The chairs advised us that we should explain how the past suggestions
> had been addressed here before the determination of the final agenda.
> 
> The following are suggestions and questions already we received
> (not in the appearance order).
> 1. why tunnel specific?
> 2. when used? testing or all time?
> 3. reuse IPPM metrics, do not produce a new one
> 4. sequence number overhead, happens fragmentation
> 5. the use of "passive" seems not accurate
> 6. how this secured?
> 7. discusstion should be in IPPM
> 
> The last one has been discussed in the PMOL mailing list.
> I am going to state the rest issues later.
> 
> Please see also for detail:
> http://www1.ietf.org/mail-archive/web/opsawg/current/msg00015.html
> http://www1.ietf.org/mail-archive/web/opsawg/current/msg00017.html
> http://www1.ietf.org/mail-archive/web/opsawg/current/msg00018.html
> http://www3.ietf.org/proceedings/07mar/minutes/opsarea.txt
> http://www3.ietf.org/proceedings/07jul/minutes/opsawg.txt
> 
> http://www.ietf.org/internet-drafts/draft-kikuchi-tunnel-measure-req-02.txt
> http://www.ietf.org/internet-drafts/draft-kikuchi-passive-measure-01.txt
> 
> -- Yu.


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Thu Nov 22 09:36:33 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IvDAO-0008Eo-EX; Thu, 22 Nov 2007 09:36:32 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IvDAO-0008Ej-0s
	for opsawg-confirm+ok@megatron.ietf.org; Thu, 22 Nov 2007 09:36:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IvDAN-0008Eb-L5
	for opsawg@ietf.org; Thu, 22 Nov 2007 09:36:31 -0500
Received: from newdev.eecs.harvard.edu ([140.247.60.212])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IvDAL-0002Oy-0B
	for opsawg@ietf.org; Thu, 22 Nov 2007 09:36:31 -0500
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501)
	id A2D4E6518E4; Thu, 22 Nov 2007 09:35:43 -0500 (EST)
To: opsawg@ietf.org
Subject: Re: [OPSAWG] tunnel quality measurement I-Ds
Message-Id: <20071122143543.A2D4E6518E4@newdev.eecs.harvard.edu>
Date: Thu, 22 Nov 2007 09:35:43 -0500 (EST)
From: sob@harvard.edu (Scott O. Bradner)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org


KIKUCHI Yutaka <yu at kikuken.org> writes:
> > 5. the use of "passive" seems not accurate
> 
> The issue may come from our algorithm uses sequence number
> that seems to inject some extra information for measurement.
> I think this method is completely passive because of the same
> reason above. The measurement mechanism does not inject
> any information into flows.

I will admit to maybe being somewhet confused - this proposal seems to 
modify the packets to insert then remove sequence numbers - calling
this "passive" seems inaccurate  - am I misunderstanding it?

Scott


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Thu Nov 22 10:44:44 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IvEEO-0006M9-Cg; Thu, 22 Nov 2007 10:44:44 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IvEEM-0006M3-QS
	for opsawg-confirm+ok@megatron.ietf.org; Thu, 22 Nov 2007 10:44:42 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IvEEM-0006Ll-Fx
	for opsawg@ietf.org; Thu, 22 Nov 2007 10:44:42 -0500
Received: from umi.kikuken.org ([202.126.16.27] helo=ari.kikuken.org)
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IvEEL-0002qW-7K
	for opsawg@ietf.org; Thu, 22 Nov 2007 10:44:41 -0500
Received: (qmail 32429 invoked from network); 23 Nov 2007 00:44:39 +0900
Received: from unknown (HELO localhost) (218.100.15.124)
	by umi.kikuken.org with SMTP; 23 Nov 2007 00:44:39 +0900
Date: Fri, 23 Nov 2007 00:44:46 +0900 (JST)
Message-Id: <20071123.004446.139022679.yu@kikuken.org>
To: sob@harvard.edu
Subject: Re: [OPSAWG] tunnel quality measurement I-Ds
From: KIKUCHI Yutaka <yu@kikuken.org>
In-Reply-To: <20071122143543.A2D4E6518E4@newdev.eecs.harvard.edu>
References: <20071122143543.A2D4E6518E4@newdev.eecs.harvard.edu>
Organization: Kochi Univ. of Tech.
X-Mailer: Mew version 4.2.53 on Emacs 22.0.50 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: opsawg@ietf.org
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Scott-san,

> KIKUCHI Yutaka <yu at kikuken.org> writes:
> > > 5. the use of "passive" seems not accurate
> > 
> > The issue may come from our algorithm uses sequence number
> > that seems to inject some extra information for measurement.
> > I think this method is completely passive because of the same
> > reason above. The measurement mechanism does not inject
> > any information into flows.
> 
> I will admit to maybe being somewhet confused - this proposal seems to 
> modify the packets to insert then remove sequence numbers - calling
> this "passive" seems inaccurate  - am I misunderstanding it?

I got why your question and my answer had not been in gear
at the 68th and 69th IETF meetings.

The proposal does not mean to modify the packets in the ingress of flows
and either not to eliminate anything from the packets in the egress.
The method uses protocols that already have sequence numbering functions
therefore it is not able to adapt protocols without the function e.g. IP-in-IP.

Please let us know where the draft had lead you to make misunderstanding.
It is an important point to be revised because many people
might understand in a wrong way.

Thank you very much in advance.

-- Regards, Yu.



_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



From opsawg-bounces@ietf.org Sun Nov 25 23:04:59 2007
Return-path: <opsawg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IwVDP-0004Tr-D7; Sun, 25 Nov 2007 23:04:59 -0500
Received: from opsawg by megatron.ietf.org with local (Exim 4.43)
	id 1IwVDO-0004Tl-RS
	for opsawg-confirm+ok@megatron.ietf.org; Sun, 25 Nov 2007 23:04:58 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IwVDJ-0004TO-Iz
	for opsawg@ietf.org; Sun, 25 Nov 2007 23:04:53 -0500
Received: from umi.kikuken.org ([202.126.16.27] helo=ari.kikuken.org)
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IwVDI-0003yR-13
	for opsawg@ietf.org; Sun, 25 Nov 2007 23:04:52 -0500
Received: (qmail 12803 invoked from network); 26 Nov 2007 13:04:49 +0900
Received: from unknown (HELO localhost) (218.100.15.124)
	by umi.kikuken.org with SMTP; 26 Nov 2007 13:04:49 +0900
Date: Mon, 26 Nov 2007 13:05:02 +0900 (JST)
Message-Id: <20071126.130502.83602870.yu@kikuken.org>
To: opsawg@ietf.org
Subject: Re: [OPSAWG] agenda requests for opsawg in Vancouver
From: KIKUCHI Yutaka <yu@kikuken.org>
In-Reply-To: <20071122.144552.44275045.yu@kikuken.org>
References: <20071107034206.00F7961B682@newdev.eecs.harvard.edu>
	<20071108.132548.94837533.yu@kikuken.org>
	<20071122.144552.44275045.yu@kikuken.org>
Organization: Kochi Univ. of Tech.
X-Mailer: Mew version 4.2.53 on Emacs 22.0.50 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: zin@jaist.ac.jp, satoru@ft.solteria.net, nagami@inetcore.com
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/opsawg>,
	<mailto:opsawg-request@ietf.org?subject=subscribe>
Errors-To: opsawg-bounces@ietf.org

Hi,

The chairs had also advised us to check the interest of people
on the mailing list. Folks, please respond about your thought,
e.g. interested or not, important or not, understandable or not
and/or should be discussed here or not.
Of course, negative responses are welcome. If so, could you append the
reason after seeing the description below (and the I-Ds if possible)?


Background:

Overlay network techniques have increased and will increase
because some applications require new functions that the legacy
transports do not serve, i.e. to guarantee some quality, policy
routing, mobility, multi-homing, and hiding structure of underlayers.

The tunneling technologies support the overlay network concept,
therefore the net people will possibly operate and manage plenty of
tunnels as well as the legacy transports and the current IP networks.

About the I-Ds:

Our proposal aims to state one of basic tunnel OAM methods
independently from specific tunnel techniques.
The details are not described here but I am showing
a typical use case of the drafts...

0. operators in an xSP (and/or an iDC)...
1. after setting up for watching every one of tunnel flows,
2. while working with other tasks and listening music with iPod,
3. to get an alarm on a failure of some tunnels, and
4. to check the reason whether equipment fault, route changed or the other.
5. The xSP will (or will not) refund money according as the SLA
   with the measured tunnels' quality.

History and the current situation:

We has been searching for an appropriate WG to discuss the proposal
for a year. The first time we asked was in the OPS-area open meeting
of 68th IETF because we thought the proposal was an operational issue.
As you know, OPSAWG had been opened since the 69th IETF,
so we also had a good opportunity to discuss our I-Ds there.

Now the original draft had been splitted into two drafts,
because the original draft was made from both requirements
and one of their solutions. Now the requirements draft needs
discussion to be improved and deployed, so we would like to discuss here.

Note that the other I-D, had been splited from the original I-D and
describing concrete metrics and method, had lost the place to discuss. 
I thought the new PMOL would accept any discussion of performance metrics
that were not suitable to IPPM and BMWG, but it was my misunderstanding.
This issue has still been discussed in the PMOL mailing list.

-- Best Regards, Yu.

> Hi,
> 
> The chairs advised us that we should explain how the past suggestions
> had been addressed here before the determination of the final agenda.
> 
> The following are suggestions and questions already we received
> (not in the appearance order).
> 1. why tunnel specific?
> 2. when used? testing or all time?
> 3. reuse IPPM metrics, do not produce a new one
> 4. sequence number overhead, happens fragmentation
> 5. the use of "passive" seems not accurate
> 6. how this secured?
> 7. discusstion should be in IPPM
> 
> The last one has been discussed in the PMOL mailing list.
> I am going to state the rest issues later.
> 
> Please see also for detail:
> http://www1.ietf.org/mail-archive/web/opsawg/current/msg00015.html
> http://www1.ietf.org/mail-archive/web/opsawg/current/msg00017.html
> http://www1.ietf.org/mail-archive/web/opsawg/current/msg00018.html
> http://www3.ietf.org/proceedings/07mar/minutes/opsarea.txt
> http://www3.ietf.org/proceedings/07jul/minutes/opsawg.txt
> 
> http://www.ietf.org/internet-drafts/draft-kikuchi-tunnel-measure-req-02.txt
> http://www.ietf.org/internet-drafts/draft-kikuchi-passive-measure-01.txt
> 
> -- Yu.
> 
> > Hi,
> > 
> > We would like to discuss about our I-D
> > draft-kikuchi-tunnel-measure-req-02.txt
> > ``Quality Measurement Requirements for Tunneling Protocols''.
> > The newest version will be appeared later.
> > 
> > -- Best Regards, Yu.
> > 
> > > 
> > > this is a first call for timeslots on the opsawg session in Vancouver
> > > 
> > > we are currently scheduled for tuesday afternoon from 1520 to 1720
> > > 
> > > Scott & Ted
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > OPSAWG mailing list
> > > OPSAWG@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/opsawg
> > > 
> > 
> 


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www1.ietf.org/mailman/listinfo/opsawg



