From ops-nm-bounces@ietf.org Fri Jun 01 04:27:01 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hu2TA-0000WN-DR; Fri, 01 Jun 2007 04:26:48 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1Hu2T8-0000W2-D7
	for ops-nm-confirm+ok@megatron.ietf.org; Fri, 01 Jun 2007 04:26:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hu2Sz-0000UE-Ps; Fri, 01 Jun 2007 04:26:37 -0400
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 1Hu2Sz-0006kO-Dk; Fri, 01 Jun 2007 04:26:37 -0400
Received: from 12.140.64.135.in-addr.arpa (HELO 307622ANEX5.global.avaya.com)
	([135.64.140.12])
	by nj300815-nj-outbound.avaya.com with ESMTP; 01 Jun 2007 04:26:36 -0400
X-IronPort-AV: i="4.16,371,1175486400"; d="scan'208"; a="22381610:sNHT9705624"
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: Fri, 1 Jun 2007 10:26:36 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04092559@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for June 7, 2007 Telechat 
Thread-Index: Acej3dUV2yNFxNJZRoO4cnLadwAkogASEnEA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>, <ops-nm@ietf.org>,
	"MIB Doctors (E-mail)" <mib-doctors@ietf.org>,
	"Aaa-Doctors (E-mail)" <aaa-doctors@ops.ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd
Cc: 
Subject: [OPS-NM] FW: PRELIMINARY Agenda and Package for June 7,
	2007 Telechat 
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Please see below the preliminary agenda for the 6/7 IESG Telechat. If
there are any questions or concerns, please let me know before Wednesday
6/6 COB.

Thanks and Regards,

Dan

=20


2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-ips-iscsi-impl-guide-08.txt
    iSCSI Corrections and Clarifications (Proposed Standard) - 1 of 7=20
    Note: Document Shepherd: David Black=20
    Token: Lars Eggert
  o draft-ietf-atompub-protocol-15.txt
    The Atom Publishing Protocol (Proposed Standard) - 2 of 7=20
    Token: Lisa Dusseault
  o draft-ietf-dhc-dhcpv6-leasequery-00.txt
    DHCPv6 Leasequery (Proposed Standard) - 3 of 7=20
    Note: Document Shepherd is Ralph Droms <rdroms@cisco.com>=20
    Token: Jari Arkko
  o draft-ietf-rohc-sigcomp-sip-06.txt
    Applying Signaling Compression (SigComp) to the Session Initiation
Protocol=20
    (SIP) (Proposed Standard) - 4 of 7=20
    Token: Magnus Westerlund
  o draft-ietf-dnsext-nsec3-10.txt
    DNSSEC Hashed Authenticated Denial of Existence (Proposed Standard)
-
5 of=20
    7=20
    Note: Exiting IETF LC 5/23=20
    Token: Mark Townsley
  o draft-ietf-dhc-dhcpv6-ero-01.txt
    DHCPv6 Relay Agent Echo Request Option (Proposed Standard) - 6 of 7=20
    Note: Document Shepherd is Stig Venaas <stig.venaas@uninett.no>

    Token: Jari Arkko
  o draft-ietf-midcom-rfc3989-bis-00.txt
    Middlebox Communications (MIDCOM) Protocol Semantics (Proposed
Standard) -=20
    7 of 7=20
    Note: This document is an draft update of the process of taking RFC
3989 to=20
    proposed standard. It inherits the state RFC3989 to proposed had.. .
The=20
    ones that has reviewed it before should just copy their ballot
position to=20
    this new ballot.=20
    Token: Magnus Westerlund

2.1.2 Returning Item
  o draft-ietf-dnsext-nsid-02.txt
    DNS Name Server Identifier Option (NSID) (Proposed Standard) - 1 of
1

    Token: Mark Townsley


2.2 Individual Submissions
2.2.1 New Item
NONE
2.2.2 Returning Item
NONE

3. Document Actions

3.1 WG Submissions
	Reviews should focus on these questions: "Is this document a
reasonable
contribution to the area of Internet engineering which it covers? If
not,
what changes would make it so?"

3.1.1 New Item
  o draft-ietf-hip-dns-09.txt
    Host Identity Protocol (HIP) Domain Name System (DNS) Extensions=20
    (Experimental) - 1 of 6=20
    Token: Mark Townsley
  o draft-ietf-sipping-dialogusage-06.txt
    Multiple Dialog Usages in the Session Initiation Protocol
(Informational) -=20
    2 of 6=20
    Token: Jon Peterson
  o draft-ietf-nemo-multihoming-issues-07.txt
    Analysis of Multihoming in Network Mobility Support (Informational)
-
3 of=20
    6=20
    Note: Proto shepherd is TJ Kniveton <tj@kniveton.com>=20
    Token: Jari Arkko
  o draft-ietf-hip-applications-01.txt
    Using the Host Identity Protocol with Legacy Applications
(Experimental) -=20
    4 of 6=20
    Token: Mark Townsley
  o draft-ietf-ccamp-gmpls-addressing-07.txt
    Use of Addresses in Generalized Multi-Protocol Label Switching
(GMPLS)
=20
    Networks (Informational) - 5 of 6=20
    Token: Ross Callon
  o draft-ietf-mip4-fmipv4-07.txt
    Mobile IPv4 Fast Handovers (Experimental) - 6 of 6=20
    Note: Document Shepherd is Pete McCann=20
    Token: Jari Arkko

3.1.2 Returning Item
  o draft-ietf-mip6-dsmip-problem-03.txt
    Problem Statement: Dual Stack Mobility (Informational) - 1 of 1=20
    Note: PROTO shepherd is Basavaraj Patil
<basavaraj.patil@nokia.com>.=20
    NOTE 1: There are significant RFC Editor notes!. NOTE 2: Bringing
back
to=20
    agenda to resolve discusses and get more votes=20
    Token: Jari Arkko


3.2 Individual Submissions Via AD
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.2.1 New Item
  o draft-chakrabarti-ipv6-addrselect-api-06.txt
    IPv6 Socket API for Address Selection (Informational) - 1 of 1=20
    Token: Jari Arkko

3.2.2 Returning Item
NONE
3.3 Independent Submissions Via RFC Editor
	The IESG will use RFC 3932 responses: 1) The IESG has not
	found any conflict between this document and IETF work; 2) The
	IESG thinks that this work is related to IETF work done in WG
	<X>, but this does not prevent publishing; 3) The IESG thinks
	that publication is harmful to work in WG <X> and recommends
	not publishing at this time; 4) The IESG thinks that this
	document violates the IETF procedures for <X> and should
	therefore not be published without IETF review and IESG
	approval; 5) The IESG thinks that this document extends an
	IETF protocol in a way that requires IETF review and should
	therefore not be published without IETF review and IESG
approval.
=20

                   =20
	Other matters may be recorded in comments to be passed on
	to the RFC Editor as community review of the document.


3.3.1 New Item
NONE
3.3.2 Returning Item
  o draft-ooms-xcast-basic-spec-11.txt
    Explicit Multicast (Xcast) Concepts and Options (Experimental) - 1
of
1=20
    Token: Ross Callon

3.3.3 For Action
  o draft-jurski-pppext-iphc-02.txt
    Limited IP Header Compression over PPP (Informational) - 1 of 1=20
    Token: Russ Housley

4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
    NONE
4.1.2 Proposed for Approval
  o Operations and Management Area Working Group (opsawg) - 1 of 2
    Token: Dan Romascanu
  o Basic Level of Interoperability for SIP Services (bliss) - 2 of 2
    Token: Cullen Jennings
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
  o Mobility for IP: Performance, Signaling and Handoff Optimization
(mipshop) - 1 of 1
    Token: Jari Arkko
4.2.2 Proposed for Approval
    NONE


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Mon Jun 04 13:16:15 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvGA1-0005pA-Rl; Mon, 04 Jun 2007 13:16:05 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1HvGA0-0005p4-QB
	for ops-nm-confirm+ok@megatron.ietf.org; Mon, 04 Jun 2007 13:16:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvG9x-0005ly-5r
	for ops-nm@ietf.org; Mon, 04 Jun 2007 13:16:01 -0400
Received: from smtp104.sbc.mail.mud.yahoo.com ([68.142.198.203])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HvG9v-0004jh-Ol
	for ops-nm@ietf.org; Mon, 04 Jun 2007 13:16:01 -0400
Received: (qmail 8730 invoked from network); 4 Jun 2007 17:15:59 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@76.195.156.84
	with plain)
	by smtp104.sbc.mail.mud.yahoo.com with SMTP; 4 Jun 2007 17:15:58 -0000
X-YMail-OSG: gF4Af.IVM1mxhtw1tx0IMS0U7u.UKj.xoaryDb4HnGltkhwFB.s17nhLAChcKe.ff50OsUPXGDEIEVueYvlyCvoAtw--
Message-ID: <4664489B.1000406@andybierman.com>
Date: Mon, 04 Jun 2007 10:15:07 -0700
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Ops-Nm <ops-nm@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Subject: [OPS-NM] Comments on XSDMI BoF proposal
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Hi,

Here is the BoF proposal for reference:

XSD for accessing SMIv2 data models (xsdmi) BOF
Status: request submitted including proposed WG charter
Discussions: NETCONF WG list netconf@ops.ietf.org
Responsible AD: Dan Romascanu
BOF Chair: David Harrington (ietfdbh@comcast.net)
Internet-Drafts:
draft-romascanu-netconf-datatypes-02 (XSD for SMIv2 Data Types and
Textual Conventions)
draft-li-ngo-access-mib-01 (SMIv2 Data Access for NETCONF)
Summary and Scope: Future WG Formation - The XSDMI WG will undertake the
following work items:
(A) Development of a standard XML Schema Definition [XSD] to specify the
XML encoding of the core SMIv2 data types defined in RFC2578.
(B) Development of a standard XML Schema Definition [XSD] to specify the
XML encoding of some generic and common SMIv2 textual conventions, as
identified at http://www.ops.ietf.org/mib-common-tcs.html.
(C) Definition of a standard set of security requirements for accessing
MIB management data by potentially multiple protocols.
(D) Development of a standard set of algorithms for accessing SMIv2
management information, possibly using the NETCONF <get> operation
and/or <notification> data delivery mechanism.

---------------------------------------

General:

I strongly support the formation of this WG, and think
it should be the "only next step" in NETCONF Data Modeling
standards development.

Trying to standardize too much at once without enough implementation
experience is not going to help.  The most critical DM need is to
figure out how to use the standard NM data definitions we already have.

Nit: The WG acronym is kind of cryptic and I'm not sure what
it supposed to mean.  Also, the WG name only describes work items
(A) and (B).  Security requirements for multi-protocol access
to MIB data is definitely not covered by the title, and (D)
is 'possibly' NETCONF protocol-specific. (?? XSMI ?? SMIX ?? SMINET ??)

Milestones:  Any idea how long you think it will take to do
all this work?

Work items:

(A)(B)
The XSD for SMIv2 data types and TCs draft has been reviewed and refined
over
a couple years, and it is very much needed, and ready, for standardization.

(C)
This work item is a bit vague.  I'm not sure if it means
a mapping between an SNMP EngineID to a NETCONF session identity,
or something to do with VACM, or something else undefined.
I think it is a smart idea to understand all the security issues
associated with (D).

(D)
I support a standard algorithmic translation between SMIv2 conceptual
data models and NETCONF configuration databases, which includes
data organization and standard protocol operation mappings.
I think read-only access instead of full access will be easier
to achieve, so it should be done first.  The use case for
write access is not as strong, and the multi-protocol access and
security issues are harder.

I do not support a generic XSD representation of SMIv2 macros,
without consideration of the specific XML-based protocol being used.
The 'embedded' SNMP protocol operations in SMIv2, as well as the explicit
SNMP operations discussed in MIB object DESCRIPTION clauses, RowPointer,
RowStatus, StorageType, etc., all have to be explicitly mapped to the
specific NETCONF (or whatever) protocol operations and
architecture assumptions.


Andy




_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Tue Jun 05 15:50:11 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hvf2T-0006wf-CV; Tue, 05 Jun 2007 15:49:57 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1Hvf2S-0006wQ-9z
	for ops-nm-confirm+ok@megatron.ietf.org; Tue, 05 Jun 2007 15:49:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hvf2R-0006wH-VI; Tue, 05 Jun 2007 15:49:55 -0400
Received: from sccrmhc14.comcast.net ([204.127.200.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hvf2R-0002WC-Hc; Tue, 05 Jun 2007 15:49:55 -0400
Received: from harrington73653
	(c-24-128-104-207.hsd1.nh.comcast.net[24.128.104.207])
	by comcast.net (sccrmhc14) with SMTP
	id <2007060519495501400deje2e>; Tue, 5 Jun 2007 19:49:55 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Andy Bierman'" <ietf@andybierman.com>,
	"'Ops-Nm'" <ops-nm@ietf.org>
References: <4664489B.1000406@andybierman.com>
Subject: RE: [OPS-NM] Comments on XSDMI BoF proposal
Date: Tue, 5 Jun 2007 15:49:46 -0400
Message-ID: <02c901c7a7aa$ab924fc0$0600a8c0@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: <4664489B.1000406@andybierman.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AcemzA59oB5ulVZRR7W5+F6lyv4NKQAzMFkA
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7698d1420ecbbce1995432e99bb6d1a1
Cc: ops-area@ietf.org
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Hi,

comments inline 

(I am cross-posting to the ops-area mailing list because no official
decision was made to relocate discussion for XSDMI to the ops-nm list.
I will ask Dan to change the BOF page to direct discussion to the
ops-nm list. Interested parties please find XSDMI discussion on the
ops-nm list.)

dbh

> -----Original Message-----
> From: Andy Bierman [mailto:ietf@andybierman.com] 
> Sent: Monday, June 04, 2007 1:15 PM
> To: Ops-Nm
> Subject: [OPS-NM] Comments on XSDMI BoF proposal
> 
> General:
> 
> I strongly support the formation of this WG, and think
> it should be the "only next step" in NETCONF Data Modeling
> standards development.

> Trying to standardize too much at once without enough implementation
> experience is not going to help.  The most critical DM need is to
> figure out how to use the standard NM data definitions we 
> already have.

My intention is to develop a way to access MIB data via XML-based NM
protocols,
to take advantage of the existing NM data definitions in the MIB. 

This is a migration strategy to move from a mainly-SNMP-and-MIB
management framework to a multi-protocol-and-multi-data-model
management framework. 

I do not think MIB access is enough. A binary data-based approach like
the MIB is fine for automated management, but it is not good for
operator-interactive management, and it fails to take advantage of
advances in computer networking technology like WWW technologies.

For operator-interactice NM, I think we need task-based NM interfaces.
The CLI is one approach, and standardizing it would probably be
helpful, but the engineering departments of vendors are not very
cooperative on doing that; it is easier for engineers to use freeform
text when developing CLIs and syslog-style reporting than to use
standardized content. 

XML-based management leverages lessons learned from the WWW. While
document-based rather than command-based, tasks can often be grouped
into a document-type interface, such as a web page. With automated
translation from XML into HTML (and related technologies), we can work
on developing task-based-document NM interfaces. 

I think we need to spend more time thinking about operator use-cases,
not just technical designs of SMIs. I think it would help to start
thinking in terms of modular data models similar to MIB modules, not
just a <running> config,  but we need to develop an SMI that helps to
differentiate config and state info, which SMIv2 doesn't do, Maybe all
we need to do is recommend that MIB modules have separate subtrees for
config and for state, much as we now recommend separate subtrees for
objects and notifications. 

While I would like to see the reuse of existing standards, such as
XSD, we need to support programmatic interfaces to allow (incremental)
automation of repetitive tasks. That means we need to provide
machine-readable "clues" about the meta-nature of management
information. Maybe that can be done in XML using attributes, or
namespaces, or hierarchical organization. Maybe it will require a new
SMI with all the special fields found in SMIv2 - and more. 

I think one of the big questions we need to address is whether a new
SMI should be developed that is an extension/superset of SMIv2, or is
distinct from SMIv2. I think that work involves getting operator
feedback of how they work, so we can understand whether we should be
trying to merge the existing NM protocols, or should keep them (and
their data) distinct. I think we should be considering how to
componentize existing standards work, so we can reuse some parts, such
as secure transport, while keeping other parts distinct. 

That work can advance while we work on developing support for one or
more XML-based interfaces to SMIv2 data models, as a migratory step
toward multi-protocol management.

> 
> Nit: The WG acronym is kind of cryptic and I'm not sure what
> it supposed to mean.  Also, the WG name only describes work items
> (A) and (B).  Security requirements for multi-protocol access
> to MIB data is definitely not covered by the title, and (D)
> is 'possibly' NETCONF protocol-specific. (?? XSMI ?? SMIX ?? 
> SMINET ??)

I deliberately avoided the use of SMI. As somebody pointed out (you?),
this work (A and B) is not developing a new SMI, it is merely
translating elements of SMIv2 from one language to another.

> 
> Milestones:  Any idea how long you think it will take to do
> all this work?
> 
> Work items:
> 
> (A)(B)
> The XSD for SMIv2 data types and TCs draft has been reviewed 
> and refined
> over
> a couple years, and it is very much needed, and ready, for 
> standardization.

Yan will be publishing a base datatype translation document, based on
libsmi translations. Since this has been defined and used(?) fo
ryears, I expect this should be fast - in IETF terms, we can probably
finish in seven or eight years ;-). Seriously, I hope this can be done
in six months or so, if there is enough interest to work on it.

That will be supplemented by the (romascanu) TC translations document.
We need to decide whether XSD can express the restrictions adequately
to support machine-validation, and whether the amount of
machine-validation supported justifies having an XSD for the TC.
Having TC translations might be helpful for netconf to go read existng
MIB data, without having to also parse SMIv2 MIB documents to
understand what the values mean. I think the bigger benefit is
defining TCs that can be used by multiple protocols to support
consistent semantics across protocols, and XML is the preferred
language for most new protocols.

This will require case-by-case analysis, and might take time to reach
consensus. Of course, not every contentious TC must be included in
this document, so if we cut out the contentious ones, this should be
able to be wrapped up within a year, I hope.

> 
> (C)
> This work item is a bit vague.  I'm not sure if it means
> a mapping between an SNMP EngineID to a NETCONF session identity,
> or something to do with VACM, or something else undefined.
> I think it is a smart idea to understand all the security issues
> associated with (D).

I'm looking at the bigger picture of multi-protocol management. There
are lots of protocols being developed, both inside and outside IETF,
to perform management functionality. As Bob Natale pointed out, the
MIB is the "crown jewel" of IETF Management (I think SNMP is as well,
when used for what it is good at). I think lots of WGs and lots of
other SDOs are going to look at the MIB and say "gee, we should
leverage that!"

I think we need to set some guidelines about how protocols should deal
with the MIB, so that it is not ruined by unconstrained access by
multiple protocols, especially write access.

But even read-access can be problematic. Security is a process, not a
product. The IETF needs to decide how to "balance" security in an
environment of multi-protocol management. It makes no sense to protect
your house with a front door that has multiple deadbolt locks, if your
back door has no locks. 

It makes no sense to expect operators to go to the trouble of
configuring VACM to protect the data in the MIB when using SNMP, if
the operator's VACM configuration will just be ignored by netconf and
other protocols accessing the MIB. I think we need some guidelines
that provide for a more consistent approach to multi-protocol MIB
access, than VACM-for-SNMP and nothing-for-others. 

Personally, I would like to see VACM not be mandatory-to-implement for
SNMP, if there is no corresponding mandatory-to-implement access
control for other protocols. I don't think the operator community is
actually ready for standardized cross-protocol access control, and if
it isn't balanced across protocols, then we shouldn't require any NM
protocol standards to have a mandatory-to-implement access control
model.

> 
> (D)
> I support a standard algorithmic translation between SMIv2
conceptual
> data models and NETCONF configuration databases, which includes
> data organization and standard protocol operation mappings.
> I think read-only access instead of full access will be easier
> to achieve, so it should be done first.  The use case for
> write access is not as strong, and the multi-protocol access and
> security issues are harder.

I agree that read-only access would probably be sufficient for netconf
to gather state information, statistical information, and
notifications. I do not see a lot of reason to support write access to
the MIB via netconf.

> 
> I do not support a generic XSD representation of SMIv2 macros,
> without consideration of the specific XML-based protocol being used.
> The 'embedded' SNMP protocol operations in SMIv2, as well as 
> the explicit
> SNMP operations discussed in MIB object DESCRIPTION clauses, 
> RowPointer,
> RowStatus, StorageType, etc., all have to be explicitly mapped to
the
> specific NETCONF (or whatever) protocol operations and
> architecture assumptions.

I think these need to be supported to understand the values of certain
fields that might be read from the MIB. 

RowStatus reflects the operational state of the row, and if netconf is
accessing the MIB to determine operational state of the thing
represented by that row, it is an important piece of information. But
if netconf has no write capability to the MIB, it does not need to
know how to manipulate the values.

StorageType is also state information about a row that might be
important for a netconf client to understand; it might be helpful to
know that the MIB representation (or the underlying instrumentation)
is in ROM. But if it has no write capability, it does not need to know
how to manipulate the row within the constraints of StorageType. 

The MIB is more or less a relational database, where the relations
between rows is important information. If netconf reads a row that has
a relationship to another row via a RowPointer, netconf better know
how to interpret a RowPointer.

(It is important to understand that I make no assumptions that a
netconf-client will have a direct connection to an SNMP manager that
knows how to parse this information from an SMIv2  MIB module
document.)

I think we need to walk through these TCs on a case-by-case basis to
decide whether we need each one for use with netconf, and what XSD
restrictions apply.

David Harrington
dharrington@huawei.com 
dbharrington@comcast.net
ietfdbh@comcast.net




_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Wed Jun 06 01:57:25 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvoW5-0000wv-Eh; Wed, 06 Jun 2007 01:57:09 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1HvoW4-0000wn-8F
	for ops-nm-confirm+ok@megatron.ietf.org; Wed, 06 Jun 2007 01:57:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvoW3-0000wf-S1
	for ops-nm@ietf.org; Wed, 06 Jun 2007 01:57:07 -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 1HvoW1-0007Ng-3w
	for ops-nm@ietf.org; Wed, 06 Jun 2007 01:57:07 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12])
	by co300216-co-outbound.avaya.com with ESMTP; 06 Jun 2007 01:57:04 -0400
X-IronPort-AV: i="4.16,388,1175486400"; 
	d="scan'208"; a="25615866:sNHT12262854"
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: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
Date: Wed, 6 Jun 2007 07:56:29 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com>
In-Reply-To: <02c901c7a7aa$ab924fc0$0600a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
Thread-Index: AcemzA59oB5ulVZRR7W5+F6lyv4NKQAzMFkAABh/jXA=
References: <4664489B.1000406@andybierman.com>
	<02c901c7a7aa$ab924fc0$0600a8c0@china.huawei.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "David Harrington" <ietfdbh@comcast.net>,
	"Andy Bierman" <ietf@andybierman.com>, "Ops-Nm" <ops-nm@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 83867a50fd8f547996ccdaf89af24437
Cc: 
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org


See in-line a few comments from a contributor perspective.=20

Dan

=20
=20

> -----Original Message-----
> From: David Harrington [mailto:ietfdbh@comcast.net]=20
> >=20
> > I strongly support the formation of this WG, and think it should be=20
> > the "only next step" in NETCONF Data Modeling standards development.
>=20
> > Trying to standardize too much at once without enough=20
> implementation=20
> > experience is not going to help.  The most critical DM need is to=20
> > figure out how to use the standard NM data definitions we already=20
> > have.
>=20
> My intention is to develop a way to access MIB data via=20
> XML-based NM protocols, to take advantage of the existing NM=20
> data definitions in the MIB.=20
>=20
> This is a migration strategy to move from a=20
> mainly-SNMP-and-MIB management framework to a=20
> multi-protocol-and-multi-data-model
> management framework.=20
>=20
> I do not think MIB access is enough. A binary data-based=20
> approach like the MIB is fine for automated management, but=20
> it is not good for operator-interactive management, and it=20
> fails to take advantage of advances in computer networking=20
> technology like WWW technologies.
>=20
> For operator-interactice NM, I think we need task-based NM interfaces.
> The CLI is one approach, and standardizing it would probably=20
> be helpful, but the engineering departments of vendors are=20
> not very cooperative on doing that; it is easier for=20
> engineers to use freeform text when developing CLIs and=20
> syslog-style reporting than to use standardized content.=20

I do not believe that a standard CLI is achievable in the IETF. By now
we should assume this is not going to happen.=20

>=20
> XML-based management leverages lessons learned from the WWW.=20
> While document-based rather than command-based, tasks can=20
> often be grouped into a document-type interface, such as a=20
> web page. With automated translation from XML into HTML (and=20
> related technologies), we can work on developing=20
> task-based-document NM interfaces.=20
>=20
> I think we need to spend more time thinking about operator=20
> use-cases, not just technical designs of SMIs. I think it=20
> would help to start thinking in terms of modular data models=20
> similar to MIB modules, not just a <running> config,  but we=20
> need to develop an SMI that helps to differentiate config and=20
> state info, which SMIv2 doesn't do, Maybe all we need to do=20
> is recommend that MIB modules have separate subtrees for=20
> config and for state, much as we now recommend separate=20
> subtrees for objects and notifications.=20

Maybe, but at this point in time all the base of standard MIB modules is
not designed this way. What are we going to do, re-write these MIB
modules, or part of them? This does not seem an achievable task.=20

>=20
> While I would like to see the reuse of existing standards,=20
> such as XSD, we need to support programmatic interfaces to=20
> allow (incremental) automation of repetitive tasks. That=20
> means we need to provide machine-readable "clues" about the=20
> meta-nature of management information. Maybe that can be done=20
> in XML using attributes, or namespaces, or hierarchical=20
> organization. Maybe it will require a new SMI with all the=20
> special fields found in SMIv2 - and more.=20
>=20
> I think one of the big questions we need to address is=20
> whether a new SMI should be developed that is an=20
> extension/superset of SMIv2, or is distinct from SMIv2. I=20
> think that work involves getting operator feedback of how=20
> they work, so we can understand whether we should be trying=20
> to merge the existing NM protocols, or should keep them (and=20
> their data) distinct. I think we should be considering how to=20
> componentize existing standards work, so we can reuse some=20
> parts, such as secure transport, while keeping other parts distinct.=20

I somehow like the paradigm - SNMP for performance monitoring and
alerts, Netconf for configuration and status retrieval. Could we
consider that the current standard MIB modules based would be used for
read configuration operations, like declare it as the status branch in
each MIB, ignoring the configuration objects and build atop of it what
is needed for configuration, even if this means duplication of some
objects. Simple or too simplistic?=20

>=20
> That work can advance while we work on developing support for=20
> one or more XML-based interfaces to SMIv2 data models, as a=20
> migratory step toward multi-protocol management.
>=20
> >=20
> > Nit: The WG acronym is kind of cryptic and I'm not sure what it=20
> > supposed to mean.  Also, the WG name only describes work items
> > (A) and (B).  Security requirements for multi-protocol=20
> access to MIB=20
> > data is definitely not covered by the title, and (D) is 'possibly'=20
> > NETCONF protocol-specific. (?? XSMI ?? SMIX ??
> > SMINET ??)
>=20
> I deliberately avoided the use of SMI. As somebody pointed=20
> out (you?), this work (A and B) is not developing a new SMI,=20
> it is merely translating elements of SMIv2 from one language=20
> to another.
>=20
> >=20
> > Milestones:  Any idea how long you think it will take to do=20
> all this=20
> > work?
> >=20
> > Work items:
> >=20
> > (A)(B)
> > The XSD for SMIv2 data types and TCs draft has been reviewed and=20
> > refined over a couple years, and it is very much needed, and ready,=20
> > for standardization.
>=20
> Yan will be publishing a base datatype translation document,=20
> based on libsmi translations. Since this has been defined and=20
> used(?) fo ryears, I expect this should be fast - in IETF=20
> terms, we can probably finish in seven or eight years ;-).=20
> Seriously, I hope this can be done in six months or so, if=20
> there is enough interest to work on it.
>=20
> That will be supplemented by the (romascanu) TC translations document.
> We need to decide whether XSD can express the restrictions=20
> adequately to support machine-validation, and whether the=20
> amount of machine-validation supported justifies having an=20
> XSD for the TC.
> Having TC translations might be helpful for netconf to go=20
> read existng MIB data, without having to also parse SMIv2 MIB=20
> documents to understand what the values mean. I think the=20
> bigger benefit is defining TCs that can be used by multiple=20
> protocols to support consistent semantics across protocols,=20
> and XML is the preferred language for most new protocols.
>=20
> This will require case-by-case analysis, and might take time=20
> to reach consensus. Of course, not every contentious TC must=20
> be included in this document, so if we cut out the=20
> contentious ones, this should be able to be wrapped up within=20
> a year, I hope.

I would try to push for a more aggressive schedule, even if it's a
smaller set of TCs. It's not that all needs to be standardized in RFC
form, but it is better to have this in a stable format for other work to
re-use it including proprietary implementations to deploy this.=20

>=20
> >=20
> > (C)
> > This work item is a bit vague.  I'm not sure if it means a mapping=20
> > between an SNMP EngineID to a NETCONF session identity, or=20
> something=20
> > to do with VACM, or something else undefined.
> > I think it is a smart idea to understand all the security issues=20
> > associated with (D).
>=20
> I'm looking at the bigger picture of multi-protocol=20
> management. There are lots of protocols being developed, both=20
> inside and outside IETF, to perform management functionality.=20
> As Bob Natale pointed out, the MIB is the "crown jewel" of=20
> IETF Management (I think SNMP is as well, when used for what=20
> it is good at). I think lots of WGs and lots of other SDOs=20
> are going to look at the MIB and say "gee, we should leverage that!"
>=20
> I think we need to set some guidelines about how protocols=20
> should deal with the MIB, so that it is not ruined by=20
> unconstrained access by multiple protocols, especially write access.
>=20
> But even read-access can be problematic. Security is a=20
> process, not a product. The IETF needs to decide how to=20
> "balance" security in an environment of multi-protocol=20
> management. It makes no sense to protect your house with a=20
> front door that has multiple deadbolt locks, if your back=20
> door has no locks.=20
>=20
> It makes no sense to expect operators to go to the trouble of=20
> configuring VACM to protect the data in the MIB when using=20
> SNMP, if the operator's VACM configuration will just be=20
> ignored by netconf and other protocols accessing the MIB. I=20
> think we need some guidelines that provide for a more=20
> consistent approach to multi-protocol MIB access, than=20
> VACM-for-SNMP and nothing-for-others.=20
>=20
> Personally, I would like to see VACM not be=20
> mandatory-to-implement for SNMP, if there is no corresponding=20
> mandatory-to-implement access control for other protocols. I=20
> don't think the operator community is actually ready for=20
> standardized cross-protocol access control, and if it isn't=20
> balanced across protocols, then we shouldn't require any NM=20
> protocol standards to have a mandatory-to-implement access=20
> control model.

I confess that this is confuse for me too. I am not sure that I
understand what is the deliverable here, or whether the problem can be
solved within the context of this working group.=20

>=20
> >=20
> > (D)
> > I support a standard algorithmic translation between SMIv2
> conceptual
> > data models and NETCONF configuration databases, which=20
> includes data=20
> > organization and standard protocol operation mappings.
> > I think read-only access instead of full access will be easier to=20
> > achieve, so it should be done first.  The use case for=20
> write access is=20
> > not as strong, and the multi-protocol access and security=20
> issues are=20
> > harder.
>=20
> I agree that read-only access would probably be sufficient=20
> for netconf to gather state information, statistical=20
> information, and notifications. I do not see a lot of reason=20
> to support write access to the MIB via netconf.

Yes, see the above.

>=20
> >=20
> > I do not support a generic XSD representation of SMIv2=20
> macros, without=20
> > consideration of the specific XML-based protocol being used.
> > The 'embedded' SNMP protocol operations in SMIv2, as well as the=20
> > explicit SNMP operations discussed in MIB object=20
> DESCRIPTION clauses,=20
> > RowPointer, RowStatus, StorageType, etc., all have to be explicitly=20
> > mapped to
> the
> > specific NETCONF (or whatever) protocol operations and architecture=20
> > assumptions.
>=20
> I think these need to be supported to understand the values=20
> of certain fields that might be read from the MIB.=20
>=20
> RowStatus reflects the operational state of the row, and if=20
> netconf is accessing the MIB to determine operational state=20
> of the thing represented by that row, it is an important=20
> piece of information. But if netconf has no write capability=20
> to the MIB, it does not need to know how to manipulate the values.
>=20
> StorageType is also state information about a row that might=20
> be important for a netconf client to understand; it might be=20
> helpful to know that the MIB representation (or the=20
> underlying instrumentation) is in ROM. But if it has no write=20
> capability, it does not need to know how to manipulate the=20
> row within the constraints of StorageType.=20
>=20
> The MIB is more or less a relational database, where the=20
> relations between rows is important information. If netconf=20
> reads a row that has a relationship to another row via a=20
> RowPointer, netconf better know how to interpret a RowPointer.
>=20
> (It is important to understand that I make no assumptions=20
> that a netconf-client will have a direct connection to an=20
> SNMP manager that knows how to parse this information from an=20
> SMIv2  MIB module
> document.)
>=20
> I think we need to walk through these TCs on a case-by-case=20
> basis to decide whether we need each one for use with=20
> netconf, and what XSD restrictions apply.

Agree with David on this one.=20

>=20
> David Harrington
> dharrington@huawei.com
> dbharrington@comcast.net
> ietfdbh@comcast.net
>=20
>=20
>=20
>=20
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www1.ietf.org/mailman/listinfo/ops-area
>=20


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Wed Jun 06 06:06:10 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvsOv-0001KN-3y; Wed, 06 Jun 2007 06:06:01 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1HvsOt-0001IX-H0
	for ops-nm-confirm+ok@megatron.ietf.org; Wed, 06 Jun 2007 06:05:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvsOs-0001FY-Tb
	for ops-nm@ietf.org; Wed, 06 Jun 2007 06:05:58 -0400
Received: from rs32.luxsci.com ([65.61.166.73])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvsOs-0000OY-40
	for ops-nm@ietf.org; Wed, 06 Jun 2007 06:05:58 -0400
Received: from [192.168.20.100] (c-24-218-138-247.hsd1.ma.comcast.net
	[24.218.138.247]) (authenticated bits=0)
	by rs32.luxsci.com (8.13.1/8.13.7) with ESMTP id l56A5pr3016019
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 6 Jun 2007 05:05:52 -0500
Message-ID: <466686FF.3090906@jdscons.com>
Date: Wed, 06 Jun 2007 06:05:51 -0400
From: Jon Saperia <saperia@jdscons.com>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
References: <4664489B.1000406@andybierman.com>	<02c901c7a7aa$ab924fc0$0600a8c0@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com>
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 4ec58ef3f343ebf5ac40a04538f9a6fc
Cc: Ops-Nm <ops-nm@ietf.org>
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1714086940=="
Errors-To: ops-nm-bounces@ietf.org

--===============1714086940==
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
One comment/question in line below:<br>
<br>
Romascanu, Dan (Dan) wrote:
<blockquote
 cite="midEDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com"
 type="cite">
  <pre wrap="">See in-line a few comments from a contributor perspective. 

Dan

 
 

  </pre>
  <blockquote type="cite">
    <pre wrap="">-----Original Message-----
From: David Harrington [<a class="moz-txt-link-freetext" href="mailto:ietfdbh@comcast.net">mailto:ietfdbh@comcast.net</a>] 
    </pre>
    <blockquote type="cite">
      <pre wrap="">I strongly support the formation of this WG, and think it should be 
the "only next step" in NETCONF Data Modeling standards development.
      </pre>
    </blockquote>
    <blockquote type="cite">
      <pre wrap="">Trying to standardize too much at once without enough 
      </pre>
    </blockquote>
    <pre wrap="">implementation 
    </pre>
    <blockquote type="cite">
      <pre wrap="">experience is not going to help.  The most critical DM need is to 
figure out how to use the standard NM data definitions we already 
have.
      </pre>
    </blockquote>
    <pre wrap="">My intention is to develop a way to access MIB data via 
XML-based NM protocols, to take advantage of the existing NM 
data definitions in the MIB. 

This is a migration strategy to move from a 
mainly-SNMP-and-MIB management framework to a 
multi-protocol-and-multi-data-model
management framework. 

I do not think MIB access is enough. A binary data-based 
approach like the MIB is fine for automated management, but 
it is not good for operator-interactive management, and it 
fails to take advantage of advances in computer networking 
technology like WWW technologies.

For operator-interactice NM, I think we need task-based NM interfaces.
The CLI is one approach, and standardizing it would probably 
be helpful, but the engineering departments of vendors are 
not very cooperative on doing that; it is easier for 
engineers to use freeform text when developing CLIs and 
syslog-style reporting than to use standardized content. 
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I do not believe that a standard CLI is achievable in the IETF. By now
we should assume this is not going to happen. 

  </pre>
  <blockquote type="cite">
    <pre wrap="">XML-based management leverages lessons learned from the WWW. 
While document-based rather than command-based, tasks can 
often be grouped into a document-type interface, such as a 
web page. With automated translation from XML into HTML (and 
related technologies), we can work on developing 
task-based-document NM interfaces. 

I think we need to spend more time thinking about operator 
use-cases, not just technical designs of SMIs. I think it 
would help to start thinking in terms of modular data models 
similar to MIB modules, not just a &lt;running&gt; config,  but we 
need to develop an SMI that helps to differentiate config and 
state info, which SMIv2 doesn't do, Maybe all we need to do 
is recommend that MIB modules have separate subtrees for 
config and for state, much as we now recommend separate 
subtrees for objects and notifications. 
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Maybe, but at this point in time all the base of standard MIB modules is
not designed this way. What are we going to do, re-write these MIB
modules, or part of them? This does not seem an achievable task. 
  </pre>
</blockquote>
<br>
I have seen a couple of references in the discussion to State and
netconf.&nbsp; Can we be more specific about what we mean by state here.&nbsp;
Configuration state?&nbsp; When I think of other types of state such as
operational state or quality state I think of either read MIB objects
or notifications (traps/informs).<br>
<br>
The suggestion of using subtrees for functional (e.g., FCAPS)
separation has worked well in some cases (we use 0 for notifications
right).&nbsp; <br>
<br>
<blockquote
 cite="midEDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com"
 type="cite">
  <pre wrap="">
  </pre>
  <blockquote type="cite">
    <pre wrap="">While I would like to see the reuse of existing standards, 
such as XSD, we need to support programmatic interfaces to 
allow (incremental) automation of repetitive tasks. That 
means we need to provide machine-readable "clues" about the 
meta-nature of management information. Maybe that can be done 
in XML using attributes, or namespaces, or hierarchical 
organization. Maybe it will require a new SMI with all the 
special fields found in SMIv2 - and more. 

I think one of the big questions we need to address is 
whether a new SMI should be developed that is an 
extension/superset of SMIv2, or is distinct from SMIv2. I 
think that work involves getting operator feedback of how 
they work, so we can understand whether we should be trying 
to merge the existing NM protocols, or should keep them (and 
their data) distinct. I think we should be considering how to 
componentize existing standards work, so we can reuse some 
parts, such as secure transport, while keeping other parts distinct. 
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I somehow like the paradigm - SNMP for performance monitoring and
alerts, Netconf for configuration and status retrieval. Could we
consider that the current standard MIB modules based would be used for
read configuration operations, like declare it as the status branch in
each MIB, ignoring the configuration objects and build atop of it what
is needed for configuration, even if this means duplication of some
objects. Simple or too simplistic? 

  </pre>
  <blockquote type="cite">
    <pre wrap="">That work can advance while we work on developing support for 
one or more XML-based interfaces to SMIv2 data models, as a 
migratory step toward multi-protocol management.

    </pre>
    <blockquote type="cite">
      <pre wrap="">Nit: The WG acronym is kind of cryptic and I'm not sure what it 
supposed to mean.  Also, the WG name only describes work items
(A) and (B).  Security requirements for multi-protocol 
      </pre>
    </blockquote>
    <pre wrap="">access to MIB 
    </pre>
    <blockquote type="cite">
      <pre wrap="">data is definitely not covered by the title, and (D) is 'possibly' 
NETCONF protocol-specific. (?? XSMI ?? SMIX ??
SMINET ??)
      </pre>
    </blockquote>
    <pre wrap="">I deliberately avoided the use of SMI. As somebody pointed 
out (you?), this work (A and B) is not developing a new SMI, 
it is merely translating elements of SMIv2 from one language 
to another.

    </pre>
    <blockquote type="cite">
      <pre wrap="">Milestones:  Any idea how long you think it will take to do 
      </pre>
    </blockquote>
    <pre wrap="">all this 
    </pre>
    <blockquote type="cite">
      <pre wrap="">work?

Work items:

(A)(B)
The XSD for SMIv2 data types and TCs draft has been reviewed and 
refined over a couple years, and it is very much needed, and ready, 
for standardization.
      </pre>
    </blockquote>
    <pre wrap="">Yan will be publishing a base datatype translation document, 
based on libsmi translations. Since this has been defined and 
used(?) fo ryears, I expect this should be fast - in IETF 
terms, we can probably finish in seven or eight years ;-). 
Seriously, I hope this can be done in six months or so, if 
there is enough interest to work on it.

That will be supplemented by the (romascanu) TC translations document.
We need to decide whether XSD can express the restrictions 
adequately to support machine-validation, and whether the 
amount of machine-validation supported justifies having an 
XSD for the TC.
Having TC translations might be helpful for netconf to go 
read existng MIB data, without having to also parse SMIv2 MIB 
documents to understand what the values mean. I think the 
bigger benefit is defining TCs that can be used by multiple 
protocols to support consistent semantics across protocols, 
and XML is the preferred language for most new protocols.

This will require case-by-case analysis, and might take time 
to reach consensus. Of course, not every contentious TC must 
be included in this document, so if we cut out the 
contentious ones, this should be able to be wrapped up within 
a year, I hope.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I would try to push for a more aggressive schedule, even if it's a
smaller set of TCs. It's not that all needs to be standardized in RFC
form, but it is better to have this in a stable format for other work to
re-use it including proprietary implementations to deploy this. 

  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">(C)
This work item is a bit vague.  I'm not sure if it means a mapping 
between an SNMP EngineID to a NETCONF session identity, or 
      </pre>
    </blockquote>
    <pre wrap="">something 
    </pre>
    <blockquote type="cite">
      <pre wrap="">to do with VACM, or something else undefined.
I think it is a smart idea to understand all the security issues 
associated with (D).
      </pre>
    </blockquote>
    <pre wrap="">I'm looking at the bigger picture of multi-protocol 
management. There are lots of protocols being developed, both 
inside and outside IETF, to perform management functionality. 
As Bob Natale pointed out, the MIB is the "crown jewel" of 
IETF Management (I think SNMP is as well, when used for what 
it is good at). I think lots of WGs and lots of other SDOs 
are going to look at the MIB and say "gee, we should leverage that!"

I think we need to set some guidelines about how protocols 
should deal with the MIB, so that it is not ruined by 
unconstrained access by multiple protocols, especially write access.

But even read-access can be problematic. Security is a 
process, not a product. The IETF needs to decide how to 
"balance" security in an environment of multi-protocol 
management. It makes no sense to protect your house with a 
front door that has multiple deadbolt locks, if your back 
door has no locks. 

It makes no sense to expect operators to go to the trouble of 
configuring VACM to protect the data in the MIB when using 
SNMP, if the operator's VACM configuration will just be 
ignored by netconf and other protocols accessing the MIB. I 
think we need some guidelines that provide for a more 
consistent approach to multi-protocol MIB access, than 
VACM-for-SNMP and nothing-for-others. 

Personally, I would like to see VACM not be 
mandatory-to-implement for SNMP, if there is no corresponding 
mandatory-to-implement access control for other protocols. I 
don't think the operator community is actually ready for 
standardized cross-protocol access control, and if it isn't 
balanced across protocols, then we shouldn't require any NM 
protocol standards to have a mandatory-to-implement access 
control model.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I confess that this is confuse for me too. I am not sure that I
understand what is the deliverable here, or whether the problem can be
solved within the context of this working group. 

  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">(D)
I support a standard algorithmic translation between SMIv2
      </pre>
    </blockquote>
    <pre wrap="">conceptual
    </pre>
    <blockquote type="cite">
      <pre wrap="">data models and NETCONF configuration databases, which 
      </pre>
    </blockquote>
    <pre wrap="">includes data 
    </pre>
    <blockquote type="cite">
      <pre wrap="">organization and standard protocol operation mappings.
I think read-only access instead of full access will be easier to 
achieve, so it should be done first.  The use case for 
      </pre>
    </blockquote>
    <pre wrap="">write access is 
    </pre>
    <blockquote type="cite">
      <pre wrap="">not as strong, and the multi-protocol access and security 
      </pre>
    </blockquote>
    <pre wrap="">issues are 
    </pre>
    <blockquote type="cite">
      <pre wrap="">harder.
      </pre>
    </blockquote>
    <pre wrap="">I agree that read-only access would probably be sufficient 
for netconf to gather state information, statistical 
information, and notifications. I do not see a lot of reason 
to support write access to the MIB via netconf.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Yes, see the above.

  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">I do not support a generic XSD representation of SMIv2 
      </pre>
    </blockquote>
    <pre wrap="">macros, without 
    </pre>
    <blockquote type="cite">
      <pre wrap="">consideration of the specific XML-based protocol being used.
The 'embedded' SNMP protocol operations in SMIv2, as well as the 
explicit SNMP operations discussed in MIB object 
      </pre>
    </blockquote>
    <pre wrap="">DESCRIPTION clauses, 
    </pre>
    <blockquote type="cite">
      <pre wrap="">RowPointer, RowStatus, StorageType, etc., all have to be explicitly 
mapped to
      </pre>
    </blockquote>
    <pre wrap="">the
    </pre>
    <blockquote type="cite">
      <pre wrap="">specific NETCONF (or whatever) protocol operations and architecture 
assumptions.
      </pre>
    </blockquote>
    <pre wrap="">I think these need to be supported to understand the values 
of certain fields that might be read from the MIB. 

RowStatus reflects the operational state of the row, and if 
netconf is accessing the MIB to determine operational state 
of the thing represented by that row, it is an important 
piece of information. But if netconf has no write capability 
to the MIB, it does not need to know how to manipulate the values.

StorageType is also state information about a row that might 
be important for a netconf client to understand; it might be 
helpful to know that the MIB representation (or the 
underlying instrumentation) is in ROM. But if it has no write 
capability, it does not need to know how to manipulate the 
row within the constraints of StorageType. 

The MIB is more or less a relational database, where the 
relations between rows is important information. If netconf 
reads a row that has a relationship to another row via a 
RowPointer, netconf better know how to interpret a RowPointer.

(It is important to understand that I make no assumptions 
that a netconf-client will have a direct connection to an 
SNMP manager that knows how to parse this information from an 
SMIv2  MIB module
document.)

I think we need to walk through these TCs on a case-by-case 
basis to decide whether we need each one for use with 
netconf, and what XSD restrictions apply.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Agree with David on this one. 

  </pre>
  <blockquote type="cite">
    <pre wrap="">David Harrington
<a class="moz-txt-link-abbreviated" href="mailto:dharrington@huawei.com">dharrington@huawei.com</a>
<a class="moz-txt-link-abbreviated" href="mailto:dbharrington@comcast.net">dbharrington@comcast.net</a>
<a class="moz-txt-link-abbreviated" href="mailto:ietfdbh@comcast.net">ietfdbh@comcast.net</a>




_______________________________________________
OPS-AREA mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/ops-area">https://www1.ietf.org/mailman/listinfo/ops-area</a>

    </pre>
  </blockquote>
  <pre wrap=""><!---->

_______________________________________________
OPS-NM mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OPS-NM@ietf.org">OPS-NM@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/ops-nm">https://www1.ietf.org/mailman/listinfo/ops-nm</a>


  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
Jon Saperia
(cell) 617-201-2655
(Eve.) 978-461-0264</pre>
</body>
</html>



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

_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm

--===============1714086940==--



From ops-nm-bounces@ietf.org Wed Jun 06 08:48:23 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hvuvs-0001wv-TL; Wed, 06 Jun 2007 08:48:12 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1Hvuvr-0001wn-Vh
	for ops-nm-confirm+ok@megatron.ietf.org; Wed, 06 Jun 2007 08:48:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvuvr-0001wf-M8
	for ops-nm@ietf.org; Wed, 06 Jun 2007 08:48:11 -0400
Received: from de307622-de-outbound.net.avaya.com ([198.152.71.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hvuvq-0001wG-5v
	for ops-nm@ietf.org; Wed, 06 Jun 2007 08:48:11 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	06 Jun 2007 08:48:09 -0400
X-IronPort-AV: i="4.16,389,1175486400"; 
	d="scan'208,217"; a="23848553:sNHT16041300"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
Date: Wed, 6 Jun 2007 14:47:28 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040D8023@307622ANEX5.global.avaya.com>
In-Reply-To: <466686FF.3090906@jdscons.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
Thread-Index: AceoIlt8+hi60PIOQrK6rKB1RKK9nwAFivkg
References: <4664489B.1000406@andybierman.com>	<02c901c7a7aa$ab924fc0$0600a8c0@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com>
	<466686FF.3090906@jdscons.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Jon Saperia" <saperia@jdscons.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Cc: Ops-Nm <ops-nm@ietf.org>
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1130395102=="
Errors-To: ops-nm-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1130395102==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7A838.D794CB3A"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A838.D794CB3A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20
=20
=20
=20


________________________________

	From: Jon Saperia [mailto:saperia@jdscons.com]=20
=09

			XML-based management leverages lessons learned
from the WWW.=20
			While document-based rather than command-based,
tasks can=20
			often be grouped into a document-type interface,
such as a=20
			web page. With automated translation from XML
into HTML (and=20
			related technologies), we can work on developing

			task-based-document NM interfaces.=20
		=09
			I think we need to spend more time thinking
about operator=20
			use-cases, not just technical designs of SMIs. I
think it=20
			would help to start thinking in terms of modular
data models=20
			similar to MIB modules, not just a <running>
config,  but we=20
			need to develop an SMI that helps to
differentiate config and=20
			state info, which SMIv2 doesn't do, Maybe all we
need to do=20
			is recommend that MIB modules have separate
subtrees for=20
			config and for state, much as we now recommend
separate=20
			subtrees for objects and notifications.=20
			   =20

	=09
		Maybe, but at this point in time all the base of
standard MIB modules is
		not designed this way. What are we going to do, re-write
these MIB
		modules, or part of them? This does not seem an
achievable task.=20
		 =20


	I have seen a couple of references in the discussion to State
and netconf.  Can we be more specific about what we mean by state here.
Configuration state?  When I think of other types of state such as
operational state or quality state I think of either read MIB objects or
notifications (traps/informs).
	[DR] =20
	[DR] My interpretation was state as in state of the system which
is the super-set of configuration state, but not limited to
configuration state. It is David however who introduced the term in the
thread, so I would rather have him answer.=20
	=20
	Dan
	=20
=09
=09


------_=_NextPart_001_01C7A838.D794CB3A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3086" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><STRONG><EM><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></EM></STRONG>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Jon Saperia =
[mailto:saperia@jdscons.com]=20
  <BR></FONT></DIV>
  <BLOCKQUOTE=20
  =
cite=3DmidEDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya=
.com=20
  type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">XML-based management =
leverages lessons learned from the WWW.=20
While document-based rather than command-based, tasks can=20
often be grouped into a document-type interface, such as a=20
web page. With automated translation from XML into HTML (and=20
related technologies), we can work on developing=20
task-based-document NM interfaces.=20

I think we need to spend more time thinking about operator=20
use-cases, not just technical designs of SMIs. I think it=20
would help to start thinking in terms of modular data models=20
similar to MIB modules, not just a &lt;running&gt; config,  but we=20
need to develop an SMI that helps to differentiate config and=20
state info, which SMIv2 doesn't do, Maybe all we need to do=20
is recommend that MIB modules have separate subtrees for=20
config and for state, much as we now recommend separate=20
subtrees for objects and notifications.=20
    </PRE></BLOCKQUOTE><PRE wrap=3D""><!---->
Maybe, but at this point in time all the base of standard MIB modules is
not designed this way. What are we going to do, re-write these MIB
modules, or part of them? This does not seem an achievable task.=20
  </PRE></BLOCKQUOTE>
  <DIV><BR>I have seen a couple of references in the discussion to State =
and=20
  netconf.&nbsp; Can we be more specific about what we mean by state =
here.&nbsp;=20
  Configuration state?&nbsp; When I think of other types of state such =
as=20
  operational state or quality state I think of either read MIB objects =
or=20
  notifications (traps/informs).<BR><SPAN=20
  class=3D626144512-06062007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>[DR]&nbsp;&nbsp;</FONT></EM></STRONG></SPAN><BR><SPAN=20
  class=3D626144512-06062007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>[DR]&nbsp;My interpretation was state as in state of the =
system which=20
  is the super-set of configuration state, but not limited to =
configuration=20
  state. It is David however who introduced the term in the thread, so=20
  I&nbsp;would rather have&nbsp;him=20
  answer.&nbsp;</FONT></EM></STRONG></SPAN></DIV>
  <DIV><SPAN class=3D626144512-06062007></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D626144512-06062007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
  <DIV><SPAN=20
class=3D626144512-06062007>&nbsp;</SPAN><BR><BR></DIV></BLOCKQUOTE></BODY=
></HTML>

------_=_NextPart_001_01C7A838.D794CB3A--



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

_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm

--===============1130395102==--





From ops-nm-bounces@ietf.org Wed Jun 06 08:52:26 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hvuzv-0004wR-Kt; Wed, 06 Jun 2007 08:52:23 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1Hvuzu-0004wM-5w
	for ops-nm-confirm+ok@megatron.ietf.org; Wed, 06 Jun 2007 08:52:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvuzt-0004wE-Sn
	for ops-nm@ietf.org; Wed, 06 Jun 2007 08:52:21 -0400
Received: from rs32.luxsci.com ([65.61.166.73])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hvuzs-0002jo-Ie
	for ops-nm@ietf.org; Wed, 06 Jun 2007 08:52:21 -0400
Received: from [192.168.5.101] (static-72-93-205-34.bstnma.fios.verizon.net
	[72.93.205.34]) (authenticated bits=0)
	by rs32.luxsci.com (8.13.1/8.13.7) with ESMTP id l56CqEiu007224
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 6 Jun 2007 07:52:14 -0500
Message-ID: <4666ADF5.8010008@jdscons.com>
Date: Wed, 06 Jun 2007 08:52:05 -0400
From: Jon Saperia <saperia@jdscons.com>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
References: <4664489B.1000406@andybierman.com>	<02c901c7a7aa$ab924fc0$0600a8c0@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com>
	<466686FF.3090906@jdscons.com>
	<EDC652A26FB23C4EB6384A4584434A040D8023@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A040D8023@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: b280b4db656c3ca28dd62e5e0b03daa8
Cc: Ops-Nm <ops-nm@ietf.org>
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Thanks for the clarification, lets see what Dave says.  If it is as you 
say, then I would say what is the justification for introducing 
duplication of information?
/jon

Romascanu, Dan (Dan) wrote:
>  
>  
>  
>  
>
>
> ________________________________
>
> 	From: Jon Saperia [mailto:saperia@jdscons.com] 
> 	
>
> 			XML-based management leverages lessons learned
> from the WWW. 
> 			While document-based rather than command-based,
> tasks can 
> 			often be grouped into a document-type interface,
> such as a 
> 			web page. With automated translation from XML
> into HTML (and 
> 			related technologies), we can work on developing
>
> 			task-based-document NM interfaces. 
> 			
> 			I think we need to spend more time thinking
> about operator 
> 			use-cases, not just technical designs of SMIs. I
> think it 
> 			would help to start thinking in terms of modular
> data models 
> 			similar to MIB modules, not just a <running>
> config,  but we 
> 			need to develop an SMI that helps to
> differentiate config and 
> 			state info, which SMIv2 doesn't do, Maybe all we
> need to do 
> 			is recommend that MIB modules have separate
> subtrees for 
> 			config and for state, much as we now recommend
> separate 
> 			subtrees for objects and notifications. 
> 			    
>
> 		
> 		Maybe, but at this point in time all the base of
> standard MIB modules is
> 		not designed this way. What are we going to do, re-write
> these MIB
> 		modules, or part of them? This does not seem an
> achievable task. 
> 		  
>
>
> 	I have seen a couple of references in the discussion to State
> and netconf.  Can we be more specific about what we mean by state here.
> Configuration state?  When I think of other types of state such as
> operational state or quality state I think of either read MIB objects or
> notifications (traps/informs).
> 	[DR]  
> 	[DR] My interpretation was state as in state of the system which
> is the super-set of configuration state, but not limited to
> configuration state. It is David however who introduced the term in the
> thread, so I would rather have him answer. 
> 	 
> 	Dan
> 	 
> 	
> 	
>
>
>   

-- 
Jon Saperia
(cell) 617-201-2655
(Eve.) 978-461-0264



_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Wed Jun 06 09:08:02 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvvEw-0005an-Hl; Wed, 06 Jun 2007 09:07:54 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1HvvEv-0005ai-D0
	for ops-nm-confirm+ok@megatron.ietf.org; Wed, 06 Jun 2007 09:07:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvvEv-0005aZ-3T
	for ops-nm@ietf.org; Wed, 06 Jun 2007 09:07:53 -0400
Received: from sccrmhc15.comcast.net ([63.240.77.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvvEu-0006Ws-S7
	for ops-nm@ietf.org; Wed, 06 Jun 2007 09:07:53 -0400
Received: from harrington73653
	(c-24-128-104-207.hsd1.nh.comcast.net[24.128.104.207])
	by comcast.net (sccrmhc15) with SMTP
	id <2007060613075201500cedh1e>; Wed, 6 Jun 2007 13:07:52 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Ops-Nm'" <ops-nm@ietf.org>
References: <4664489B.1000406@andybierman.com>	<02c901c7a7aa$ab924fc0$0600a8c0@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com>
	<466686FF.3090906@jdscons.com>
	<EDC652A26FB23C4EB6384A4584434A040D8023@307622ANEX5.global.avaya.com>
	<4666ADF5.8010008@jdscons.com>
Subject: RE: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
Date: Wed, 6 Jun 2007 09:07:43 -0400
Message-ID: <038e01c7a83b$ab683aa0$0600a8c0@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: <4666ADF5.8010008@jdscons.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AceoOYTrUjnoPSF1R1yw7fJXgAZ0twAAMuhQ
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Hi,

I was referring to the separation of config and state data, as
described in RFC4741.
I do think the distinction made in rfc4741 is not very clear, so work
would need to be done.

Would this result in duplication of information? Without a draft
making a specific proposal for this, I cannot say. It might.

dbh

> -----Original Message-----
> From: Jon Saperia [mailto:saperia@jdscons.com] 
> Sent: Wednesday, June 06, 2007 8:52 AM
> To: Romascanu, Dan (Dan)
> Cc: David Harrington; Andy Bierman; Ops-Nm
> Subject: Re: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
> 
> Thanks for the clarification, lets see what Dave says.  If it 
> is as you 
> say, then I would say what is the justification for introducing 
> duplication of information?
> /jon
> 
> Romascanu, Dan (Dan) wrote:
> >  
> >  
> >  
> >  
> >
> >
> > ________________________________
> >
> > 	From: Jon Saperia [mailto:saperia@jdscons.com] 
> > 	
> >
> > 			XML-based management leverages lessons learned
> > from the WWW. 
> > 			While document-based rather than
command-based,
> > tasks can 
> > 			often be grouped into a document-type
interface,
> > such as a 
> > 			web page. With automated translation from XML
> > into HTML (and 
> > 			related technologies), we can work on
developing
> >
> > 			task-based-document NM interfaces. 
> > 			
> > 			I think we need to spend more time thinking
> > about operator 
> > 			use-cases, not just technical designs of SMIs.
I
> > think it 
> > 			would help to start thinking in terms of
modular
> > data models 
> > 			similar to MIB modules, not just a <running>
> > config,  but we 
> > 			need to develop an SMI that helps to
> > differentiate config and 
> > 			state info, which SMIv2 doesn't do, Maybe all
we
> > need to do 
> > 			is recommend that MIB modules have separate
> > subtrees for 
> > 			config and for state, much as we now recommend
> > separate 
> > 			subtrees for objects and notifications. 
> > 			    
> >
> > 		
> > 		Maybe, but at this point in time all the base of
> > standard MIB modules is
> > 		not designed this way. What are we going to do,
re-write
> > these MIB
> > 		modules, or part of them? This does not seem an
> > achievable task. 
> > 		  
> >
> >
> > 	I have seen a couple of references in the discussion to State
> > and netconf.  Can we be more specific about what we mean by 
> state here.
> > Configuration state?  When I think of other types of state such as
> > operational state or quality state I think of either read 
> MIB objects or
> > notifications (traps/informs).
> > 	[DR]  
> > 	[DR] My interpretation was state as in state of the system
which
> > is the super-set of configuration state, but not limited to
> > configuration state. It is David however who introduced the 
> term in the
> > thread, so I would rather have him answer. 
> > 	 
> > 	Dan
> > 	 
> > 	
> > 	
> >
> >
> >   
> 
> -- 
> Jon Saperia
> (cell) 617-201-2655
> (Eve.) 978-461-0264
> 
> 




_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Wed Jun 06 11:47:50 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hvxjb-0000Qj-9B; Wed, 06 Jun 2007 11:47:43 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1Hvxja-0000QW-7y
	for ops-nm-confirm+ok@megatron.ietf.org; Wed, 06 Jun 2007 11:47:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvxjZ-0000QD-T8
	for ops-nm@ietf.org; Wed, 06 Jun 2007 11:47:41 -0400
Received: from sccrmhc11.comcast.net ([63.240.77.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvxjY-0004ng-GI
	for ops-nm@ietf.org; Wed, 06 Jun 2007 11:47:41 -0400
Received: from harrington73653
	(c-24-128-104-207.hsd1.nh.comcast.net[24.128.104.207])
	by comcast.net (sccrmhc11) with SMTP
	id <2007060615474001100i00dbe>; Wed, 6 Jun 2007 15:47:40 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Ops-Nm'" <ops-nm@ietf.org>
References: <4664489B.1000406@andybierman.com>
	<02c901c7a7aa$ab924fc0$0600a8c0@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com>
Subject: RE: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
Date: Wed, 6 Jun 2007 11:47:30 -0400
Message-ID: <039501c7a851$fe245600$0600a8c0@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: <EDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AcemzA59oB5ulVZRR7W5+F6lyv4NKQAzMFkAABh/jXAAEC8R0A==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a743e34ab8eb08259de9a7307caed594
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

 Hi,

Dan, Thanks for changing the list.

> See in-line a few comments from a contributor perspective. 
> 
> Dan
 
> > I think we need to spend more time thinking about operator 
> > use-cases, not just technical designs of SMIs. I think it 
> > would help to start thinking in terms of modular data models 
> > similar to MIB modules, not just a <running> config,  but we 
> > need to develop an SMI that helps to differentiate config and 
> > state info, which SMIv2 doesn't do, Maybe all we need to do 
> > is recommend that MIB modules have separate subtrees for 
> > config and for state, much as we now recommend separate 
> > subtrees for objects and notifications. 
> 
> Maybe, but at this point in time all the base of standard MIB 
> modules is
> not designed this way. What are we going to do, re-write these MIB
> modules, or part of them? This does not seem an achievable task. 

SMIv1 MIB modules did not organize notifications in a separate
subtree, and it wasn't even done in the earlier SMIv2 MIB modules.
Over time (about twelve years), we have migrated MIB design in that
direction. 

There has been strong demand from operators for a distinction between
config and state data.
>From operator requirements documented in RFC3535: 

   3.  It is required to be able to fetch separately configuration
data,
       operational state data, and statistics from devices, and to be
       able to compare these between devices.
 
Now would seem a good time to establish new guidelines about how to
differentiate these, so over time, existing MIB modules can be
migrated in that direction. Or we could just provide guidelines for
XML-based representations, and migrate away from SMIv2 to the
XML-based schemas for SNMP as well. Now is the time when we have a
"destructive technology shift" under way from ASN.1 to XML, that could
provide a good opportunity for starting the gradual re-definition of
existing MIB modules, based on the lessons learned over the past
twenty years.

So I think the separation is an achievable task, just not a short-term
task. We could try to define some guidelines as a short-term task, but
that is not part of this BOF.

> > I think one of the big questions we need to address is 
> > whether a new SMI should be developed that is an 
> > extension/superset of SMIv2, or is distinct from SMIv2. I 
> > think that work involves getting operator feedback of how 
> > they work, so we can understand whether we should be trying 
> > to merge the existing NM protocols, or should keep them (and 
> > their data) distinct. I think we should be considering how to 
> > componentize existing standards work, so we can reuse some 
> > parts, such as secure transport, while keeping other parts 
> distinct. 
> 
> I somehow like the paradigm - SNMP for performance monitoring and
> alerts, Netconf for configuration and status retrieval. Could we
> consider that the current standard MIB modules based would be used
for
> read configuration operations, like declare it as the status branch
in
> each MIB, ignoring the configuration objects and build atop of it
what
> is needed for configuration, even if this means duplication of some
> objects. Simple or too simplistic? 

We could separate the config and state in MIB modules, by declaring a
new subtree  (iso.org.dod.internet.config(7), or
iso.org.dod.internet.<mgmt>.<config>, and then deprecate the
configuration-specific objects that exist in current MIB modules and
redefine them in the new subtree (if there is any demand to keep
them.)

If SNMP is just for performance monitoring and alerts, would you
recommend we remove the SET capability from SNMP? or make it an
optional "capability" of SNMP? That might be more reflective of real
world implementations. I don't necessarily favor that idea, but it is
something to consider.

This is not part of this BOF, however.

> > > Milestones:  Any idea how long you think it will take to do 
> > all this 
> > > work?
> > > 
> > > Work items:
> > > 
> > > (A)(B)
> > > The XSD for SMIv2 data types and TCs draft has been reviewed and

> > > refined over a couple years, and it is very much needed, 
> and ready, 
> > > for standardization.
> > 
> > Yan will be publishing a base datatype translation document, 
[..]
> > That will be supplemented by the (romascanu) TC 
> translations document.
> > 
> > This will require case-by-case analysis, and might take time 
> > to reach consensus. Of course, not every contentious TC must 
> > be included in this document, so if we cut out the 
> > contentious ones, this should be able to be wrapped up within 
> > a year, I hope.
> 
> I would try to push for a more aggressive schedule, even if it's a
> smaller set of TCs. It's not that all needs to be standardized in
RFC
> form, but it is better to have this in a stable format for 
> other work to
> re-use it including proprietary implementations to deploy this. 
> 

> > > (C)
> > > This work item is a bit vague.  [...]
> > > I think it is a smart idea to understand all the security issues

> > > associated with (D).
> > 
> I confess that this is confuse for me too. I am not sure that I
> understand what is the deliverable here, or whether the problem can
be
> solved within the context of this working group. 

A few years ago, as IP became recognized as the IETF's crown jewel,
there were many layer2 protocols whose proponents wanted IP to run
over their layer2 protocol. Rather than having the IETF do the work 
to make IP work with every layer 2 protocol requested, the IETF 
created guidelines on how layer 2 protocols should interface to IP, 
so others could define how their layer 2 protocol could be used with 
IP, within those guidelines. 

I would like to see a similar approach for the
MIB - define guidelines about how protocols from various sources
can work well with the MIB, rather than being tied down doing the
translations to use the MIB with protocols from many different
sources, such as netconf and RDML.

Since we are providing a base set of SMIv2-to-XSD translations to
allow MIB access, it would seem to be in scope of the BOF to discuss
the guidelines for MIB access.

The MIB Access over Netconf document is a (useful) pilot project to
test that the concepts in the guidelines are viable.

--
I don't have a clear proposal for (C). I see the issue; I don't favor
a specific answer; there are multiple approaches with tradeoffs, and
different people will prefer different approaches depending on their
own motivations. I think we as a community need to discuss how we want
this issue approached, what guidelines we agree upon, and then we need
to document the guidelines. Call them crappy BIG rules ;-)

I see a variety of potential solutions (not all mutually exclusive):
1) Separate databases: other protocols go directly to the
instrumentation, ignoring anything related to SNMP or the MIB, using
their own virtual database, i.e. not using the MIB. 

2) shared databases: other protocols go directly to the
instrumentation, ignoring anything related to SNMP, but using the same
virtual database (the MIB), e.g., using similar hierarchal addressing
for the data, and, if they want, the same access routine libraries as
SNMP. 

3) shared databases and access controls: other protocols are required
to authenticate the <user>, and check authorization via
SNMP-compatible access control models, such as VACM, to access the
MIB. 

4) shared databases and different required access controls: other
protocols are required to authenticate the <user>, and required to
check authorization, but they can use their own access control
approach, e.g. task-based rather than data-based, which may or may not
be compatible with, and provide the same access control strength as,
existing SNMP access control models.

and so on ...
--
SNMPv3 got into trouble for not leveraging existing security
functionality, which forced operators to deal with an additional
methodology for configuring security. SNMP defined VACM, the only IETF
standard for access control to MIB data at this point. ISMS is
discussing how to define a RADIUS-based access control model for MIB
management information. And vendors have their own ideas about how to
provide access control to management information, often specific to
their CLI system but applied to MIB data as well. 

Should MIB access be required to utilize some type of access control?
Should the access control model be protocol-specific, which would
require operators to configure yet-another access control protocol?
Should it be MIB-specific, e.g., VACM? Should it be a new MIB-specific
access control standard, such as RADIUS/ISMS? Should it be a new
access control standard that could provide fairly-consistent access
controls for different virtual databases of management information
(e.g., draft-nelson-radius-management-authorization-04.txt)? Should
access control be implementation-specific? 

What does the community, especially the operator community, want to
see here?

David Harrington
dharrington@huawei.com 
dbharrington@comcast.net
ietfdbh@comcast.net




_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Wed Jun 06 11:56:32 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hvxs7-0007zF-9T; Wed, 06 Jun 2007 11:56:31 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1Hvxs5-0007z5-Aw
	for ops-nm-confirm+ok@megatron.ietf.org; Wed, 06 Jun 2007 11:56:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvxs4-0007yk-WF
	for ops-nm@ietf.org; Wed, 06 Jun 2007 11:56:29 -0400
Received: from smtp104.sbc.mail.re2.yahoo.com ([68.142.229.101])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Hvxs2-0006Tu-8N
	for ops-nm@ietf.org; Wed, 06 Jun 2007 11:56:28 -0400
Received: (qmail 28698 invoked from network); 6 Jun 2007 15:55:57 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@76.195.156.84
	with plain)
	by smtp104.sbc.mail.re2.yahoo.com with SMTP; 6 Jun 2007 15:55:56 -0000
X-YMail-OSG: taIO1uYVM1kyEkHeRNItWzjSdzPhysHWgLBOvBK1wav6tvO7
Message-ID: <4666D8D7.80807@andybierman.com>
Date: Wed, 06 Jun 2007 08:55:03 -0700
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
Subject: Re: [OPS-NM] Comments on XSDMI BoF proposal
References: <4664489B.1000406@andybierman.com>
	<02c901c7a7aa$ab924fc0$0600a8c0@china.huawei.com>
In-Reply-To: <02c901c7a7aa$ab924fc0$0600a8c0@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: 8d89ee9312a95de8ee48d1c94511f1bb
Cc: 'Ops-Nm' <ops-nm@ietf.org>, ops-area@ietf.org
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

David Harrington wrote:
> Hi,
> 
> comments inline 
> 

ditto

> (I am cross-posting to the ops-area mailing list because no official
> decision was made to relocate discussion for XSDMI to the ops-nm list.
> I will ask Dan to change the BOF page to direct discussion to the
> ops-nm list. Interested parties please find XSDMI discussion on the
> ops-nm list.)
> 
> dbh
> 
>> -----Original Message-----
>> From: Andy Bierman [mailto:ietf@andybierman.com] 
>> Sent: Monday, June 04, 2007 1:15 PM
>> To: Ops-Nm
>> Subject: [OPS-NM] Comments on XSDMI BoF proposal
>>
>> General:
>>
>> I strongly support the formation of this WG, and think
>> it should be the "only next step" in NETCONF Data Modeling
>> standards development.
> 
>> Trying to standardize too much at once without enough implementation
>> experience is not going to help.  The most critical DM need is to
>> figure out how to use the standard NM data definitions we 
>> already have.
> 
> My intention is to develop a way to access MIB data via XML-based NM
> protocols,
> to take advantage of the existing NM data definitions in the MIB. 
> 

This is fine, but it should be based on use cases, as you say later on.
IMO, there is a use case to read MIB data via a NETCONF session.
The goal can be abstract, but the solutions has to be specific,
in order to have an inter-operable standard.


> This is a migration strategy to move from a mainly-SNMP-and-MIB
> management framework to a multi-protocol-and-multi-data-model
> management framework. 
> 
> I do not think MIB access is enough. A binary data-based approach like
> the MIB is fine for automated management, but it is not good for
> operator-interactive management, and it fails to take advantage of
> advances in computer networking technology like WWW technologies.
> 

I am not interested in an SNMP-like interface to SMI data, encoded in XML.
IMO, via NETCONF <get>, the access should be per-row-instance, via subtree
and Xpath filters, not per-column-instance, via lexi-next (getnext).

Other protocols will have completely different requirements and
retrieval operations, and the solution might not be the same.


> For operator-interactice NM, I think we need task-based NM interfaces.
> The CLI is one approach, and standardizing it would probably be
> helpful, but the engineering departments of vendors are not very
> cooperative on doing that; it is easier for engineers to use freeform
> text when developing CLIs and syslog-style reporting than to use
> standardized content. 
> 
> XML-based management leverages lessons learned from the WWW. While
> document-based rather than command-based, tasks can often be grouped
> into a document-type interface, such as a web page. With automated
> translation from XML into HTML (and related technologies), we can work
> on developing task-based-document NM interfaces. 
> 
> I think we need to spend more time thinking about operator use-cases,
> not just technical designs of SMIs. I think it would help to start
> thinking in terms of modular data models similar to MIB modules, not
> just a <running> config,  but we need to develop an SMI that helps to
> differentiate config and state info, which SMIv2 doesn't do, Maybe all
> we need to do is recommend that MIB modules have separate subtrees for
> config and for state, much as we now recommend separate subtrees for
> objects and notifications. 
> 
> While I would like to see the reuse of existing standards, such as
> XSD, we need to support programmatic interfaces to allow (incremental)
> automation of repetitive tasks. That means we need to provide
> machine-readable "clues" about the meta-nature of management
> information. Maybe that can be done in XML using attributes, or
> namespaces, or hierarchical organization. Maybe it will require a new
> SMI with all the special fields found in SMIv2 - and more. 
> 
> I think one of the big questions we need to address is whether a new
> SMI should be developed that is an extension/superset of SMIv2, or is
> distinct from SMIv2. I think that work involves getting operator
> feedback of how they work, so we can understand whether we should be
> trying to merge the existing NM protocols, or should keep them (and
> their data) distinct. I think we should be considering how to
> componentize existing standards work, so we can reuse some parts, such
> as secure transport, while keeping other parts distinct. 
> 
> That work can advance while we work on developing support for one or
> more XML-based interfaces to SMIv2 data models, as a migratory step
> toward multi-protocol management.
> 
>> Nit: The WG acronym is kind of cryptic and I'm not sure what
>> it supposed to mean.  Also, the WG name only describes work items
>> (A) and (B).  Security requirements for multi-protocol access
>> to MIB data is definitely not covered by the title, and (D)
>> is 'possibly' NETCONF protocol-specific. (?? XSMI ?? SMIX ?? 
>> SMINET ??)
> 
> I deliberately avoided the use of SMI. As somebody pointed out (you?),
> this work (A and B) is not developing a new SMI, it is merely
> translating elements of SMIv2 from one language to another.
> 


I do not think this limited and generalized translation (D) is very useful,
or realistically possible to do well in the IETF, in finite time.

I prefer to view the Network Management problem in specific terms, e.g.,
understanding how conceptual data defined in SMIv2 can be mapped
into a NETCONF Configuration Database, and accessed with NETCONF
protocol operations.

Abstracting the NM problem as if there was nothing going on beyond
editing the XML instance document itself does not really help.


>> Milestones:  Any idea how long you think it will take to do
>> all this work?
>>
>> Work items:
>>
>> (A)(B)
>> The XSD for SMIv2 data types and TCs draft has been reviewed 
>> and refined
>> over
>> a couple years, and it is very much needed, and ready, for 
>> standardization.
> 
> Yan will be publishing a base datatype translation document, based on
> libsmi translations. Since this has been defined and used(?) fo
> ryears, I expect this should be fast - in IETF terms, we can probably
> finish in seven or eight years ;-). Seriously, I hope this can be done
> in six months or so, if there is enough interest to work on it.
> 
> That will be supplemented by the (romascanu) TC translations document.
> We need to decide whether XSD can express the restrictions adequately
> to support machine-validation, and whether the amount of
> machine-validation supported justifies having an XSD for the TC.
> Having TC translations might be helpful for netconf to go read existng
> MIB data, without having to also parse SMIv2 MIB documents to
> understand what the values mean. I think the bigger benefit is
> defining TCs that can be used by multiple protocols to support
> consistent semantics across protocols, and XML is the preferred
> language for most new protocols.
> 
> This will require case-by-case analysis, and might take time to reach
> consensus. Of course, not every contentious TC must be included in
> this document, so if we cut out the contentious ones, this should be
> able to be wrapped up within a year, I hope.
> 
>> (C)
>> This work item is a bit vague.  I'm not sure if it means
>> a mapping between an SNMP EngineID to a NETCONF session identity,
>> or something to do with VACM, or something else undefined.
>> I think it is a smart idea to understand all the security issues
>> associated with (D).
> 
> I'm looking at the bigger picture of multi-protocol management. There
> are lots of protocols being developed, both inside and outside IETF,
> to perform management functionality. As Bob Natale pointed out, the
> MIB is the "crown jewel" of IETF Management (I think SNMP is as well,
> when used for what it is good at). I think lots of WGs and lots of
> other SDOs are going to look at the MIB and say "gee, we should
> leverage that!"
> 
> I think we need to set some guidelines about how protocols should deal
> with the MIB, so that it is not ruined by unconstrained access by
> multiple protocols, especially write access.
> 
> But even read-access can be problematic. Security is a process, not a
> product. The IETF needs to decide how to "balance" security in an
> environment of multi-protocol management. It makes no sense to protect
> your house with a front door that has multiple deadbolt locks, if your
> back door has no locks. 
> 
> It makes no sense to expect operators to go to the trouble of
> configuring VACM to protect the data in the MIB when using SNMP, if
> the operator's VACM configuration will just be ignored by netconf and
> other protocols accessing the MIB. I think we need some guidelines
> that provide for a more consistent approach to multi-protocol MIB
> access, than VACM-for-SNMP and nothing-for-others. 
> 
> Personally, I would like to see VACM not be mandatory-to-implement for
> SNMP, if there is no corresponding mandatory-to-implement access
> control for other protocols. I don't think the operator community is
> actually ready for standardized cross-protocol access control, and if
> it isn't balanced across protocols, then we shouldn't require any NM
> protocol standards to have a mandatory-to-implement access control
> model.
> 


Previous discussions wrt/ NETCONF access control have indicated
that a simple solution allowed just 2 access levels (read and write)
is favored.  Perhaps as a backlash to VACM.


>> (D)
>> I support a standard algorithmic translation between SMIv2
> conceptual
>> data models and NETCONF configuration databases, which includes
>> data organization and standard protocol operation mappings.
>> I think read-only access instead of full access will be easier
>> to achieve, so it should be done first.  The use case for
>> write access is not as strong, and the multi-protocol access and
>> security issues are harder.
> 
> I agree that read-only access would probably be sufficient for netconf
> to gather state information, statistical information, and
> notifications. I do not see a lot of reason to support write access to
> the MIB via netconf.
> 
>> I do not support a generic XSD representation of SMIv2 macros,
>> without consideration of the specific XML-based protocol being used.
>> The 'embedded' SNMP protocol operations in SMIv2, as well as 
>> the explicit
>> SNMP operations discussed in MIB object DESCRIPTION clauses, 
>> RowPointer,
>> RowStatus, StorageType, etc., all have to be explicitly mapped to
> the
>> specific NETCONF (or whatever) protocol operations and
>> architecture assumptions.
> 
> I think these need to be supported to understand the values of certain
> fields that might be read from the MIB. 
> 
> RowStatus reflects the operational state of the row, and if netconf is
> accessing the MIB to determine operational state of the thing
> represented by that row, it is an important piece of information. But
> if netconf has no write capability to the MIB, it does not need to
> know how to manipulate the values.
> 
> StorageType is also state information about a row that might be
> important for a netconf client to understand; it might be helpful to
> know that the MIB representation (or the underlying instrumentation)
> is in ROM. But if it has no write capability, it does not need to know
> how to manipulate the row within the constraints of StorageType. 
> 
> The MIB is more or less a relational database, where the relations
> between rows is important information. If netconf reads a row that has
> a relationship to another row via a RowPointer, netconf better know
> how to interpret a RowPointer.
> 
> (It is important to understand that I make no assumptions that a
> netconf-client will have a direct connection to an SNMP manager that
> knows how to parse this information from an SMIv2  MIB module
> document.)
> 
> I think we need to walk through these TCs on a case-by-case basis to
> decide whether we need each one for use with netconf, and what XSD
> restrictions apply.

I was pointing these complexities out as a reason not to deal
with write access.  If there are products used by operators someday,
that have some sort of XML-based "set" operation for MIB data,
then maybe it would be interesting to standardize it.


> 
> David Harrington

Andy



_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Wed Jun 06 12:06:37 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hvy1r-0007Gl-Tx; Wed, 06 Jun 2007 12:06:35 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1Hvy1q-0007Gg-4w
	for ops-nm-confirm+ok@megatron.ietf.org; Wed, 06 Jun 2007 12:06:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvy1p-0007GX-Ri
	for ops-nm@ietf.org; Wed, 06 Jun 2007 12:06:33 -0400
Received: from smtp107.sbc.mail.mud.yahoo.com ([68.142.198.206])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Hvy1o-0008E2-ID
	for ops-nm@ietf.org; Wed, 06 Jun 2007 12:06:33 -0400
Received: (qmail 77092 invoked from network); 6 Jun 2007 16:06:32 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@76.195.156.84
	with plain)
	by smtp107.sbc.mail.mud.yahoo.com with SMTP; 6 Jun 2007 16:06:31 -0000
X-YMail-OSG: 7.xlxTYVM1kOt9MKMrB65pjXFrvQpPvrA_rS1HtNsEB9PkMk
Message-ID: <4666DB53.5040700@andybierman.com>
Date: Wed, 06 Jun 2007 09:05:39 -0700
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Jon Saperia <saperia@jdscons.com>
Subject: Re: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
References: <4664489B.1000406@andybierman.com>	<02c901c7a7aa$ab924fc0$0600a8c0@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com>
	<466686FF.3090906@jdscons.com>
	<EDC652A26FB23C4EB6384A4584434A040D8023@307622ANEX5.global.avaya.com>
	<4666ADF5.8010008@jdscons.com>
In-Reply-To: <4666ADF5.8010008@jdscons.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: Ops-Nm <ops-nm@ietf.org>
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Jon Saperia wrote:
> Thanks for the clarification, lets see what Dave says.  If it is as you 
> say, then I would say what is the justification for introducing 
> duplication of information?

What duplication are you talking about?

BTW, I do not agree with the RFC 4741 definition of config
because it is incomplete.

I use a very NETCONF-centric definition, with 3 states:

   config: Persistent Configuration
           * saved in NV-storage
           * included in <get-config>, <edit-config>, <copy-config>

   tconfig: Transient Configuration (e.g., per-session configuration)
           * not saved in NV-storage
           * included in <get-config>, <edit-config>, <copy-config>

   state: Non-Configuration Data
           * not saved in NV-storage
           * not included in <get-config>, <edit-config>, <copy-config>


> /jon


Andy


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Wed Jun 06 13:11:23 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hvz2S-0000Vc-EI; Wed, 06 Jun 2007 13:11:16 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1Hvz2R-0000VU-Il
	for ops-nm-confirm+ok@megatron.ietf.org; Wed, 06 Jun 2007 13:11:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvz2R-0000VM-9J
	for ops-nm@ietf.org; Wed, 06 Jun 2007 13:11:15 -0400
Received: from rs32.luxsci.com ([65.61.166.73])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hvz2P-0006Pq-Lt
	for ops-nm@ietf.org; Wed, 06 Jun 2007 13:11:15 -0400
Received: from [10.130.58.92] (static-71-248-182-50.bstnma.fios.verizon.net
	[71.248.182.50]) (authenticated bits=0)
	by rs32.luxsci.com (8.13.1/8.13.7) with ESMTP id l56HAxHD018526
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 6 Jun 2007 12:10:59 -0500
Message-ID: <4666EAA3.5060003@jdscons.com>
Date: Wed, 06 Jun 2007 13:10:59 -0400
From: Jon Saperia <saperia@jdscons.com>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: Andy Bierman <ietf@andybierman.com>
Subject: Re: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
References: <4664489B.1000406@andybierman.com>	<02c901c7a7aa$ab924fc0$0600a8c0@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com>
	<466686FF.3090906@jdscons.com>
	<EDC652A26FB23C4EB6384A4584434A040D8023@307622ANEX5.global.avaya.com>
	<4666ADF5.8010008@jdscons.com> <4666DB53.5040700@andybierman.com>
In-Reply-To: <4666DB53.5040700@andybierman.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: Ops-Nm <ops-nm@ietf.org>
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org



Andy Bierman wrote:
> Jon Saperia wrote:
>> Thanks for the clarification, lets see what Dave says.  If it is as 
>> you say, then I would say what is the justification for introducing 
>> duplication of information?
>
> What duplication are you talking about?
>
> BTW, I do not agree with the RFC 4741 definition of config
> because it is incomplete.
>
> I use a very NETCONF-centric definition, with 3 states:
>
>   config: Persistent Configuration
>           * saved in NV-storage
>           * included in <get-config>, <edit-config>, <copy-config>
>
>   tconfig: Transient Configuration (e.g., per-session configuration)
>           * not saved in NV-storage
>           * included in <get-config>, <edit-config>, <copy-config>
>
>   state: Non-Configuration Data
>           * not saved in NV-storage
>           * not included in <get-config>, <edit-config>, <copy-config>
>
>

A reasonable interpretation of the last would be that it includes 
counters of various things, gauges , etc. Right?
>> /jon
>
>
> Andy
>

-- 
Jon Saperia
(cell) 617-201-2655
(Eve.) 978-461-0264



_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Wed Jun 06 13:29:29 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvzK2-00056z-CY; Wed, 06 Jun 2007 13:29:26 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1HvzK1-00056u-5y
	for ops-nm-confirm+ok@megatron.ietf.org; Wed, 06 Jun 2007 13:29:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvzK0-00056m-Sb
	for ops-nm@ietf.org; Wed, 06 Jun 2007 13:29:24 -0400
Received: from smtp108.sbc.mail.mud.yahoo.com ([68.142.198.207])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HvzJz-0002nX-JX
	for ops-nm@ietf.org; Wed, 06 Jun 2007 13:29:24 -0400
Received: (qmail 98526 invoked from network); 6 Jun 2007 17:29:23 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@76.195.156.84
	with plain)
	by smtp108.sbc.mail.mud.yahoo.com with SMTP; 6 Jun 2007 17:29:22 -0000
X-YMail-OSG: CoVmyyIVM1ncChjNpG5rHfF522N.rOHJVElPWxjgJ7lmDkxO
Message-ID: <4666EEBE.1050102@andybierman.com>
Date: Wed, 06 Jun 2007 10:28:30 -0700
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Jon Saperia <saperia@jdscons.com>
Subject: Re: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
References: <4664489B.1000406@andybierman.com>	<02c901c7a7aa$ab924fc0$0600a8c0@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com>
	<466686FF.3090906@jdscons.com>
	<EDC652A26FB23C4EB6384A4584434A040D8023@307622ANEX5.global.avaya.com>
	<4666ADF5.8010008@jdscons.com> <4666DB53.5040700@andybierman.com>
	<4666EAA3.5060003@jdscons.com>
In-Reply-To: <4666EAA3.5060003@jdscons.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: Ops-Nm <ops-nm@ietf.org>
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Jon Saperia wrote:
> 
> 
> Andy Bierman wrote:
>> Jon Saperia wrote:
>>> Thanks for the clarification, lets see what Dave says.  If it is as 
>>> you say, then I would say what is the justification for introducing 
>>> duplication of information?
>>
>> What duplication are you talking about?
>>
>> BTW, I do not agree with the RFC 4741 definition of config
>> because it is incomplete.
>>
>> I use a very NETCONF-centric definition, with 3 states:
>>
>>   config: Persistent Configuration
>>           * saved in NV-storage
>>           * included in <get-config>, <edit-config>, <copy-config>
>>
>>   tconfig: Transient Configuration (e.g., per-session configuration)
>>           * not saved in NV-storage
>>           * included in <get-config>, <edit-config>, <copy-config>
>>
>>   state: Non-Configuration Data
>>           * not saved in NV-storage
>>           * not included in <get-config>, <edit-config>, <copy-config>
>>
>>
> 
> A reasonable interpretation of the last would be that it includes 
> counters of various things, gauges , etc. Right?

right.
counters, ifOperStatus, timestamps, etc.

However, there are corner-cases which could be used to argue
that MAX-ACCESS of read-only does not always mean the object
is classified as 'state' (e.g., agent-generated key or row index
could be saved in NV-storage).

>>> /jon
>>
>>
>> Andy
>>
> 

Andy


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Wed Jun 06 13:32:23 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvzMs-0006fD-WA; Wed, 06 Jun 2007 13:32:23 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1HvzMs-0006f5-6a
	for ops-nm-confirm+ok@megatron.ietf.org; Wed, 06 Jun 2007 13:32:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvzMr-0006eu-T9
	for ops-nm@ietf.org; Wed, 06 Jun 2007 13:32:21 -0400
Received: from rs32.luxsci.com ([65.61.166.73])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvzMq-0002wO-Iw
	for ops-nm@ietf.org; Wed, 06 Jun 2007 13:32:21 -0400
Received: from [10.130.58.92] (static-71-248-182-50.bstnma.fios.verizon.net
	[71.248.182.50]) (authenticated bits=0)
	by rs32.luxsci.com (8.13.1/8.13.7) with ESMTP id l56HWGh2001630
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 6 Jun 2007 12:32:16 -0500
Message-ID: <4666EFA0.7010109@jdscons.com>
Date: Wed, 06 Jun 2007 13:32:16 -0400
From: Jon Saperia <saperia@jdscons.com>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: Andy Bierman <ietf@andybierman.com>
Subject: Re: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
References: <4664489B.1000406@andybierman.com>	<02c901c7a7aa$ab924fc0$0600a8c0@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com>
	<466686FF.3090906@jdscons.com>
	<EDC652A26FB23C4EB6384A4584434A040D8023@307622ANEX5.global.avaya.com>
	<4666ADF5.8010008@jdscons.com> <4666DB53.5040700@andybierman.com>
	<4666EAA3.5060003@jdscons.com> <4666EEBE.1050102@andybierman.com>
In-Reply-To: <4666EEBE.1050102@andybierman.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: Ops-Nm <ops-nm@ietf.org>
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Again thanks for the clarification.  I was less concerned about the 
finer point of what to represent than with the larger implication of 
doing all this via netconf instead of netconf and snmp.
/jon
Andy Bierman wrote:
> Jon Saperia wrote:
>>
>>
>> Andy Bierman wrote:
>>> Jon Saperia wrote:
>>>> Thanks for the clarification, lets see what Dave says.  If it is as 
>>>> you say, then I would say what is the justification for introducing 
>>>> duplication of information?
>>>
>>> What duplication are you talking about?
>>>
>>> BTW, I do not agree with the RFC 4741 definition of config
>>> because it is incomplete.
>>>
>>> I use a very NETCONF-centric definition, with 3 states:
>>>
>>>   config: Persistent Configuration
>>>           * saved in NV-storage
>>>           * included in <get-config>, <edit-config>, <copy-config>
>>>
>>>   tconfig: Transient Configuration (e.g., per-session configuration)
>>>           * not saved in NV-storage
>>>           * included in <get-config>, <edit-config>, <copy-config>
>>>
>>>   state: Non-Configuration Data
>>>           * not saved in NV-storage
>>>           * not included in <get-config>, <edit-config>, <copy-config>
>>>
>>>
>>
>> A reasonable interpretation of the last would be that it includes 
>> counters of various things, gauges , etc. Right?
>
> right.
> counters, ifOperStatus, timestamps, etc.
>
> However, there are corner-cases which could be used to argue
> that MAX-ACCESS of read-only does not always mean the object
> is classified as 'state' (e.g., agent-generated key or row index
> could be saved in NV-storage).
>
>>>> /jon
>>>
>>>
>>> Andy
>>>
>>
>
> Andy
>

-- 
Jon Saperia
(cell) 617-201-2655
(Eve.) 978-461-0264



_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Wed Jun 06 14:17:30 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hw040-0003K8-Pt; Wed, 06 Jun 2007 14:16:56 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1Hw03y-0003Jz-Ul
	for ops-nm-confirm+ok@megatron.ietf.org; Wed, 06 Jun 2007 14:16:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw03y-0003Jr-L9
	for ops-nm@ietf.org; Wed, 06 Jun 2007 14:16:54 -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 1Hw03v-0008Ep-5A
	for ops-nm@ietf.org; Wed, 06 Jun 2007 14:16:54 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12])
	by co300216-co-outbound.avaya.com with ESMTP; 06 Jun 2007 14:16:48 -0400
X-IronPort-AV: i="4.16,390,1175486400"; d="scan'208"; a="25865253:sNHT9976974"
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: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
Date: Wed, 6 Jun 2007 20:16:06 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040D8144@307622ANEX5.global.avaya.com>
In-Reply-To: <039501c7a851$fe245600$0600a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
Thread-Index: AcemzA59oB5ulVZRR7W5+F6lyv4NKQAzMFkAABh/jXAAEC8R0AAKpTYg
References: <4664489B.1000406@andybierman.com><02c901c7a7aa$ab924fc0$0600a8c0@china.huawei.com><EDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com>
	<039501c7a851$fe245600$0600a8c0@china.huawei.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "David Harrington" <ietfdbh@comcast.net>,
	"Ops-Nm" <ops-nm@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: 
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org



=20
=20

> -----Original Message-----
> From: David Harrington [mailto:ietfdbh@comcast.net]=20
> Sent: Wednesday, June 06, 2007 6:48 PM
> To: 'Ops-Nm'
> Subject: RE: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
>=20
>=20
>  Hi,
>=20
> Dan, Thanks for changing the list.
>=20
> > See in-line a few comments from a contributor perspective.=20
> >=20
> > Dan
> =20
> > > I think we need to spend more time thinking about operator=20
> > > use-cases, not just technical designs of SMIs. I think it=20
> would help=20
> > > to start thinking in terms of modular data models similar to MIB=20
> > > modules, not just a <running> config,  but we need to=20
> develop an SMI=20
> > > that helps to differentiate config and state info, which SMIv2=20
> > > doesn't do, Maybe all we need to do is recommend that MIB modules=20
> > > have separate subtrees for config and for state, much as we now=20
> > > recommend separate subtrees for objects and notifications.
> >=20
> > Maybe, but at this point in time all the base of standard=20
> MIB modules=20
> > is not designed this way. What are we going to do, re-write=20
> these MIB=20
> > modules, or part of them? This does not seem an achievable task.
>=20
> SMIv1 MIB modules did not organize notifications in a=20
> separate subtree, and it wasn't even done in the earlier=20
> SMIv2 MIB modules.
> Over time (about twelve years), we have migrated MIB design=20
> in that direction.=20
>=20
> There has been strong demand from operators for a distinction=20
> between config and state data.
> >From operator requirements documented in RFC3535:=20
>=20
>    3.  It is required to be able to fetch separately=20
> configuration data,
>        operational state data, and statistics from devices, and to be
>        able to compare these between devices.
> =20
> Now would seem a good time to establish new guidelines about=20
> how to differentiate these, so over time, existing MIB=20
> modules can be migrated in that direction. Or we could just=20
> provide guidelines for XML-based representations, and migrate=20
> away from SMIv2 to the XML-based schemas for SNMP as well.=20
> Now is the time when we have a "destructive technology shift"=20
> under way from ASN.1 to XML, that could provide a good=20
> opportunity for starting the gradual re-definition of=20
> existing MIB modules, based on the lessons learned over the=20
> past twenty years.
>=20
> So I think the separation is an achievable task, just not a=20
> short-term task. We could try to define some guidelines as a=20
> short-term task, but that is not part of this BOF.


Sure, if we are talking about a mid-long term task we are in agreement.=20

Dan


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Fri Jun 15 02:57:49 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz5kT-0004Af-Vi; Fri, 15 Jun 2007 02:57:34 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1Hz5kS-0004AQ-TE
	for ops-nm-confirm+ok@megatron.ietf.org; Fri, 15 Jun 2007 02:57:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz5kK-00046J-Rq; Fri, 15 Jun 2007 02:57:24 -0400
Received: from de307622-de-outbound.net.avaya.com ([198.152.71.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hz5kI-0000Ng-9Q; Fri, 15 Jun 2007 02:57:24 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	15 Jun 2007 02:57:21 -0400
X-IronPort-AV: i="4.16,423,1175486400"; d="scan'208"; a="27044734:sNHT9173490"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 15 Jun 2007 08:56:36 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0412191F@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for June 21, 2007 Telechat 
Thread-Index: Aceu1DHlSwqjbi+aRgS8aMC0+kR0WAARac6A
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>, "Ops-Nm" <ops-nm@ietf.org>,
	"MIB Doctors (E-mail)" <mib-doctors@ietf.org>,
	"Aaa-Doctors (E-mail)" <aaa-doctors@ops.ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
Cc: 
Subject: [OPS-NM] FW: PRELIMINARY Agenda and Package for June 21,
	2007 Telechat 
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org




2. Protocol Actions
	Reviews should focus on these questions: "Is this document a
	reasonable basis on which to build the salient part of the Internet
	infrastructure? If not, what changes would make it so?"

Please find below the preliminary agenda of the June 21 IESG Telechat. =
Please review the documents brought to the approval of the IESG and let =
me know if you have any comments or concerns until COB June 20.=20

Thanks and Regards,

Dan


2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-rtgwg-rfc3682bis-09.txt
    The Generalized TTL Security Mechanism (GTSM) (Proposed Standard) - =
1
of 6=20
    Token: Ross Callon
  o draft-ietf-mpls-lsr-self-test-07.txt
    Label Switching Router Self-Test (Proposed Standard) - 2 of 6=20
    Token: Ross Callon
  o draft-ietf-dccp-rtp-06.txt
    RTP and the Datagram Congestion Control Protocol (DCCP) (Proposed
Standard)=20
    - 3 of 6=20
    Note: Document Shepherd: Tom Phelan (tphelan@sonusnet.com)=20
    Token: Lars Eggert
  o draft-ietf-ecrit-service-urn-06.txt
    A Uniform Resource Name (URN) for Services (Proposed Standard) - 4 =
of
6=20
    Token: Jon Peterson
  o draft-ietf-mip6-bootstrapping-split-05.txt
    Mobile IPv6 bootstrapping in split scenario (Proposed Standard) - 5 =
of
6=20
    Note: Document Shepherd is Basavaraj Patil=20
    <basavaraj.patil@nokia.com>. NOTE: Last Call expires June 25, 4
days=20
    after IESG telechat=20
    Token: Jari Arkko
  o draft-ietf-dhc-relay-agent-flags-03.txt
    DHCPv4 Relay Agent Flags Suboption (Proposed Standard) - 6 of 6=20
    Note: Document Shepherd is <stig.venaas@uninett.no>=20
    Token: Jari Arkko

2.1.2 Returning Item
  o draft-ietf-openpgp-rfc2440bis-22.txt
    OpenPGP Message Format (Proposed Standard) - 1 of 1=20
    Token: Sam Hartman

2.1.3 For Action
  o Two-document ballot:  - 1 of 1
     - draft-ietf-syslog-protocol-21.txt
       The syslog Protocol (Proposed Standard)=20
       Note: The WG chairs believe they may have backed out enough =
changes
=20
       that. this no longer requires an second IETF last call.=A0 In
the=20
       hopes that I. will get a chance to review this weekend and issue =
a

       ballot I'm placining it on the agenda.. If I fail to issue a
ballot by=20
       Monday I will remove.=20
     - draft-ietf-syslog-transport-udp-09.txt
       Transmission of syslog messages over UDP (Proposed Standard)=20
       Note: The WG chairs believe they may have backed out enough =
changes
=20
       that. this no longer requires an second IETF last call.=A0 In
the=20
       hopes that I. will get a chance to review this weekend and issue =
a

       ballot I'm placining it on the agenda.. If I fail to issue a
ballot by=20
       Monday I will remove.=20
    Token: Sam Hartman

2.2 Individual Submissions
2.2.1 New Item
NONE
2.2.2 Returning Item
NONE

3. Document Actions

3.1 WG Submissions
	Reviews should focus on these questions: "Is this document a reasonable
	contribution to the area of Internet engineering which it covers? If
	not, what changes would make it so?"

3.1.1 New Item
  o Two-document ballot:  - 1 of 6
     - draft-ietf-pana-pana-16.txt
       Protocol for Carrying Authentication for Network Access (PANA)
(Proposed=20
       Standard)=20
     - draft-ietf-pana-framework-09.txt
       Protocol for Carrying Authentication for Network Access (PANA)
Framework=20
       (Informational)=20
    Token: Mark Townsley
  o draft-ietf-ipfix-as-11.txt
    IPFIX Applicability (Informational) - 2 of 6=20
    Token: Dan Romascanu
  o draft-ietf-ecrit-security-threats-04.txt
    Security Threats and Requirements for Emergency Call Marking and
Mapping=20
    (Informational) - 3 of 6=20
    Token: Jon Peterson
  o draft-ietf-ecrit-requirements-13.txt
    Requirements for Emergency Context Resolution with Internet
Technologies=20
    (Informational) - 4 of 6=20
    Token: Jon Peterson
  o draft-ietf-ipfix-reducing-redundancy-04.txt
    Reducing Redundancy in IP Flow Information Export (IPFIX) and Packet =

    Sampling (PSAMP) Reports (Informational) - 5 of 6=20
    Note: Nevil Brownlee is the proto-shepherd=20
    Token: Dan Romascanu
  o draft-ietf-mip4-radius-requirements-03.txt
    Mobile IPv4 RADIUS requirements (Informational) - 6 of 6=20
    Note: Document Shepherd is Pete McCann
<pete.mccann@motorola.com>.=20
    NOTE: Last Call ends on June 25th, 4 days after IESG telechat=20
    Token: Jari Arkko

3.1.2 Returning Item
NONE

3.2 Individual Submissions Via AD
	Reviews should focus on these questions: "Is this document a reasonable
	contribution to the area of Internet engineering which it covers? If
	not, what changes would make it so?"

3.2.1 New Item
  o draft-camarillo-sipping-profile-key-02.txt
    The Session Initiation Protocol (SIP) P-Profile-Key Private Header=20
    (P-Header) (Informational) - 1 of 4=20
    Token: Jon Peterson
  o draft-ejzak-sipping-p-em-auth-04.txt
    Private Header (P-Header) Extension to the Session Initiation =
Protocol
=20
    (SIP) for Authorization of Early Media (Informational) - 2 of 4=20
    Token: Jon Peterson
  o draft-chakrabarti-ipv6-addrselect-api-06.txt
    IPv6 Socket API for Address Selection (Informational) - 3 of 4=20
    Note: A new revision is needed to address Last Call comments=20
    Token: Jari Arkko
  o draft-housley-smime-suite-b-02.txt
    Suite B in Secure/Multipurpose Internet Mail Extensions (S/MIME)=20
    (Informational) - 4 of 4=20
    Token: Tim Polk



_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Fri Jun 15 06:07:03 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz8he-00067S-F6; Fri, 15 Jun 2007 06:06:50 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1Hz8hb-0005d0-TV
	for ops-nm-confirm+ok@megatron.ietf.org; Fri, 15 Jun 2007 06:06:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz8hY-0005Fi-LZ; Fri, 15 Jun 2007 06:06:44 -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 1Hz8hY-0001MU-7O; Fri, 15 Jun 2007 06:06:44 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16])
	by co300216-co-outbound.avaya.com with ESMTP; 15 Jun 2007 06:06:42 -0400
X-IronPort-AV: i="4.16,423,1175486400"; 
	d="scan'208"; a="29488801:sNHT12818154"
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: Fri, 15 Jun 2007 12:06:06 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0412197C@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Action: Operations and Management Area Working Group (opsawg)
Thread-Index: Aceth4Kv03PmtY43SjyrSAHAIhik3wBrRh7Q
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>, "Ops-Nm" <ops-nm@ietf.org>,
	"MIB Doctors (E-mail)" <mib-doctors@ietf.org>,
	"Aaa-Doctors (E-mail)" <aaa-doctors@ops.ietf.org>, <nmrg@ibr.cs.tu-bs.de>,
	<ops-dir@ops.ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Cc: 
Subject: [OPS-NM] FW: WG Action: Operations and Management Area Working Group
	(opsawg) 
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

I apologize for cross-posting.=20

Dan



=20

-----Original Message-----
From: IESG Secretary [mailto:iesg-secretary@ietf.org]=20
Sent: Wednesday, June 13, 2007 9:50 AM
To: ietf-announce@ietf.org
Cc: opsawg@ietf.org; Scott Bradner
Subject: WG Action: Operations and Management Area Working Group
(opsawg)=20

A new IETF working group has been formed in the Operations and
Management Area. For additional information, please contact the Area
Directors or the WG Chairs.

+++

Operations and Management Area Working Group (opsawg)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D

Current Status: Active Working Group

Chair(s):
Scott Bradner <sob@harvard.edu>

Operations and Management Area Directors:
Dan Romascanu <dromasca@avaya.com>
Ronald Bonica <rbonica@juniper.net>

General Discussion: opsawg@ietf.org
To Subscribe: https://www1.ietf.org/mailman/listinfo/opsawg
Archive: http://www1.ietf.org/mail-archive/web/opsawg/current/index.html

Description:

The Operations and Management Area receives occasional proposals for the
development and publication of RFCs dealing with operational and
management topics that are not in scope of an existing working group and
do not justify the formation of a new working group. The OPSAWG will
serve as the forum for developing such work items in the IETF.

The OPSAWG mailing list is an open discussion forum for such work items,
when they arise. The working group meets if there are active proposals
that require discussion. The working group milestones are updated as
needed to reflect the current work items and their associated
milestones. All new work items and rechartering proposals will be
brought for approval with the IESG.

The focus of the work will be on topics that govern the behavior or WGs
in the O&M area (e.g., manageability
requirements) and on small, highly focused projects that don't merit a
WG of their own or belong to WGs that have already concluded (e.g.
advancement of documents on the standards track, application statements,
extensions of MIB modules).

The OPSAWG will undertake only work items that are proved to have at
least a reasonable level of interest from the operators and users
community and have a committed number of editors and reviewers. It is
not within the scope of the OPSAWG to pick up failed WG work or parts of
a WG charter items that could not come to convergence on what they were
chartered to do.

The currently active OPSAWG work items mostly fall under the following
topics:

(A) Development of a BCP document that will provide guidelines for
authors and a reference for reviewers of IETF documents that specify new
protocols or protocol extensions about the information about operational
and manageability requirements that needs to be covered in these
documents

(B) Templates and tools for Operations and Management Area Documents

(C) Maintenance and small scale extensions of documents that were
developed in working groups that have concluded (e.g. MIB modules).



Goals and Milestones:

June 2007 - Initial submission for the "Guidelines for Considering
Operations and Management of New Protocols" Internet-Draft

June 2007 - Initial submission for the "SNMP Engine ID Discovery"
Internet-Draft

October 2007 - Initial submission for the "Template for Generic
Management Data Models" Internet-Draft

October 2007 - Initial submission for the "Structured Data Elements
(SDEs) for syslog" Internet-Draft

October 2007 - WGLC for the "SNMP Engine ID Discovery" Internet-Draft

December 2007 - WGLC for the "Guidelines for Considering Operations and
Management of New Protocols" Internet-Draft

December 2007 - Submit the "SNMP Engine ID Discovery" Internet-Draft to
the IESG for consideration as Proposed Standard

February 2008 - Submit the "Guidelines for Considering Operations and
Management of New Protocols" Internet-Draft to the IESG for
consideration as BCP

April 2008 - WGLC for the "Template for Generic Management Data Models"=20

April 2008 - WGLC for the "Structured Data Elements (SDEs) for syslog"

June 2008 - Submit the "Template for Generic Management Data Models" to
the IESG for consideration as BCP

June 2008 - Submit the "Structured Data Elements (SDEs) for syslog" to
the IESG for consideration as Proposed Standard

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Mon Jun 18 02:10:11 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0AR1-0006jv-2A; Mon, 18 Jun 2007 02:09:55 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1I0AQz-0006ic-10
	for ops-nm-confirm+ok@megatron.ietf.org; Mon, 18 Jun 2007 02:09:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0AQt-0006hI-TP; Mon, 18 Jun 2007 02:09:47 -0400
Received: from de307622-de-outbound.net.avaya.com ([198.152.71.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I0AQs-0007sQ-0v; Mon, 18 Jun 2007 02:09:47 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	18 Jun 2007 02:09:44 -0400
X-IronPort-AV: i="4.16,433,1175486400"; 
	d="scan'208"; a="27969696:sNHT12457254"
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: Mon, 18 Jun 2007 08:08:56 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04121C82@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Request to forward the Nomcom 2007-8 Announcement to lists
	youmanage
Thread-Index: AcewN0+aaYBjAEmrQgWJQH6H2csCrwBN4uig
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>, "Ops-Nm" <ops-nm@ietf.org>,
	"MIB Doctors (E-mail)" <mib-doctors@ietf.org>,
	"Aaa-Doctors (E-mail)" <aaa-doctors@ops.ietf.org>, <ngo@ietf.org>,
	<mib2rdml@ietf.org>, <meta-model@ietf.org>, "Hub Mib" <hubmib@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: 
Subject: [OPS-NM] FW: Request to forward the Nomcom 2007-8 Announcement to
	lists youmanage
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Please consider the message below forwarded at the request of the Nomcom
chair.=20

Dan



=20

-----Original Message-----
From: Lakshminath Dondeti [mailto:ldondeti@qualcomm.com]=20
Sent: Saturday, June 16, 2007 7:55 PM
To: wgchairs@ietf.org; irsg@isi.edu; bofchairs@ietf.org
Subject: Request to forward the Nomcom 2007-8 Announcement to lists
youmanage

Folks,

We have around 50 volunteers so far for Nomcom 2007-8 voting member
selection.  We need a lot more!  Not everyone subscribes to the
IETF-Announce list.  Could you please forward the announcement
https://datatracker.ietf.org/public/show_nomcom_message.cgi?id=3D1234 to
WG, RG, BoF, Area lists that you manage?

Thanks in advance.

best regards,
Lakshminath


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Fri Jun 29 06:21:36 2007
Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4DY4-0006iU-WB; Fri, 29 Jun 2007 06:17:57 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43)
	id 1I4DY3-0006dd-My
	for ops-nm-confirm+ok@megatron.ietf.org; Fri, 29 Jun 2007 06:17:55 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4DXy-0006Rz-Ms; Fri, 29 Jun 2007 06:17:50 -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 1I4DXy-0006Lv-CT; Fri, 29 Jun 2007 06:17:50 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by co300216-co-outbound.avaya.com with ESMTP; 29 Jun 2007 06:17:16 -0400
X-IronPort-AV: i="4.16,474,1175486400"; d="scan'208"; a="35529193:sNHT8690886"
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: Fri, 29 Jun 2007 12:16:40 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0419D781@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for July 5, 2007 Telechat 
Thread-Index: Ace51bGZD3VD9TOARX+lQsp8kJaqbgAYHqBg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>, "Ops-Nm" <ops-nm@ietf.org>,
	"Aaa-Doctors (E-mail)" <aaa-doctors@ops.ietf.org>, <mib-doctors@ietf.org>,
	<ipfix@ietf.org>, <radiusext@ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: 
Subject: [OPS-NM] FW: PRELIMINARY Agenda and Package for July 5,
	2007 Telechat 
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Please find below the preliminary agenda for the 7/5 IESG telechat.
Please forward to me all comments and concerns until Wednesday 7/4 COB.=20

Thanks and Regards,

Dan



2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-ipfix-biflow-05.txt
    Bidirectional Flow Export using IPFIX (Proposed Standard) - 1 of 3=20
    Note: Nevil Brownlee is the proto-shepherd=20
    Token: Dan Romascanu
  o draft-ietf-radext-rfc4590bis-01.txt
    RADIUS Extension for Digest Authentication (Proposed Standard) - 2
of
3=20
    Note: A revised version of non-normative Section 6 (Examples) will
be

    provided in order to fix problems detected during the Last Call.=20
    Token: Dan Romascanu
  o draft-ietf-radext-fixes-04.txt
    Common Remote Authentication Dial In User Service (RADIUS)
Implementation=20
    Issues and Suggested Fixes (Proposed Standard) - 3 of 3=20
    Token: Dan Romascanu

2.1.2 Returning Item
  o draft-ietf-dhc-server-override-04.txt
    DHCP Server Identifier Override Suboption (Proposed Standard) - 1 of
2
=20
    Note: Bringing this document back to agenda, hopefully with the past
issue=20
    solved=20
    Token: Jari Arkko
  o draft-ietf-midcom-mib-09.txt
    Definitions of Managed Objects for Middlebox Communication (Proposed

    Standard) - 2 of 2=20
    Note: Needs positions from the new people.. SEC-DIR Reviewer: Radia
Perlman=20
    (Radia.Perlman@sun.com). WG Shephard Melinda Shore.=20
    Token: Magnus Westerlund


2.2 Individual Submissions
2.2.1 New Item
  o draft-williams-on-channel-binding-02.txt
    On the Use of Channel Bindings to Secure Channels (Proposed
Standard)
- 1=20
    of 2=20
    Token: Sam Hartman
  o draft-mcgrew-auth-enc-02.txt
    An Interface and Algorithms for Authenticated Encryption (Proposed=20
    Standard) - 2 of 2=20
    Token: Tim Polk

2.2.2 Returning Item
NONE

3. Document Actions

3.1 WG Submissions
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.1.1 New Item
NONE
3.1.2 Returning Item
NONE

3.2 Individual Submissions Via AD
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.2.1 New Item
  o draft-martin-ibcs-04.txt
    Identity-Based Cryptography Standard (IBCS) #1: Supersingular Curve=20
    Implementations of the BF and BB1 Cryptosystems (Informational) - 1
of
2=20
    Token: Tim Polk
  o draft-mrose-apex-historic-02.txt
    Reclassification of the APEX RFCs to Historic (Informational) - 2 of
2
=20
    Token: Chris Newman

=20


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



