From brusil@snad.ncsl.nist.gov Tue Nov 1 13:01:52 1994 id AA22661; Tue, 1 Nov 94 13:01:07 EST Date: Tue, 1 Nov 94 13:01:07 EST From: Dr. Paul J. Brusil - Consultant Message-Id: <9411011801.AA22661@snad.ncsl.nist.gov> Subject: NMSIG-94/376 EWSO EGLL POSITION ON LL ENSEMBLES & MO PROFILES Status: R NMSIG-94/376 EWOS EGLL POSITION ON TAXONOMY & PROPOSALS FOR LOWER LAYER MANAGEMENT ENSEMBLES AND MO PROFILES Date: Mon, 24 Oct 94 13:09:39 MET From: "Isabelle VALET, CSAC Europe @VBO, DTN 828-5370" TApparently-To: ewos-egnm@external.iihe.rtt.be Subject: EWOS/EGLL commments on NM/SIG-94/354 and 94/357 From: DECPRL::"magnus@VNET.IBM.COM" "Magnus Stallknecht" 13-OCT-1994 20:43:51. 91 To: kk@arinc.com, valet@prl.dec.com, fred.burg@att.com, Wada@focs.sumiden.co .jp, osamu@isl.ntt.jp, ewos-egll@external.iihe.rtt.b CC: Subj: EWOS/EGLL commments on NM/SIG-94/354 and 94/357 Attached please find a liaison statement on management ensembles and managed object taxonomy which was developed at the October 1994 meeting of EWOS/EGLL. We had the benefit of the editor of the CLNS Management Ensemble, Kedem Kaminsky, participating in the EWOS/EGLL meeting. This was very useful for understanding the ongoing activities an their implications for Lower Layers profiling. Isabelle, please forward to your peer NM groupsas needed, thanks. Best regards, Magnus Stallknecht, EWOS/EGLL ==================================================================== EWOS/EGLL/1994/___ TD18R1, 10/94 Date: October 12, 1994 To: EWOS/EGNM (Isabelle Valet) cc: OIW/LLSIG (Fred Burg) AOW/LAN-SIG (Yutaka Wada) AOW/WAN-SIG(Osamu Takahash) CLNSME Editor (Kedem Kaminsky) From: EWOS/EGLL (Magnus Stallknecht) Subject:Taxonomy and proposals for lower layer management ensembles and managed object profiles Ref. 1: OIW/NMSIG-94/357, Taxonomy for Lower Layer Ensemble and Managed Object Profiles (attached for information) Ref. 2: OIW/NMSIG-94/354, Working Draft 8 ISO/IEC XXXXXX : June 194, International Standardized Profile AOM311, OSI Management Communication - Management Ensembles - Part 1: Connectionless Layer Network Systems Management Enseble At its October 1994 meeting the EWOS/EGLL reviewed the OIW liaison document, NMSIG-94/357, on a proposed taxonomy for lower layers management ensembles and managed objects. The following comments are numbered to correspond to the comment numbers in NMSIG-94/357: 1. The EGLL agrees with the ollowing AOM taxonomy: AOM, OSI Management AOM1, Management Communications AOM2, Management Function AOM3, Management Ensembles AOM31, Ensembles for management of OSI Lower Layers AOM311, Lower Layers Systems and Network Management Ensemble for TA/RA/RD ISPs AOM312, LowerLayers Systems and Network Management Ensemble for TB/TC/TD/TE/RB/RC/RD ISPs 2. EWOS EGLL agrees that the T and R ISPs should refer to management capabilities. The EGLL views management as it does security and routing. Security and routing ISP parts are optional capabilities referenced by a asic ISP. The following diagram illustrates the ISP structure when it references optional anagement, security, and routing capabilities: TA or RA ISP: +---------+ | | | | <--- Managed object ISP parts | | | | <--- Security capability ISP parts | | | | <--- Dynamic routeing capability ISP parts | | +---------+ 3. EGLL proposes that lower layer managed object profile parts be developed as ISP parts inthe existing TA, RA and RD profiles series, and not as FOM specifications. The EGLL agrees tat the FOM taxonomy is a feasible alternative. EGLL proposes that the lower layer managed object ISP parts be structured in a manner equivalent to security and routing ISP parts. Lower layer security and routing capabilities are described in ISP parts. EGLL is of the opinion that loer layer management capacities also be described in ISP parts. In addition, EGLL recommends grouping of managed object requirements into those requirements that are common to severalor all profiles, and those that are specific to particular profiles. Such grouping would inimize duplicate text and be consistent with current practice for multi-part lower layers ISPs. The following diagram illustrates how the TA51 ISP would reference common and specific managed object requirements. TA51 profile Managed object specifications +----------+ TL | TP4 | <---- Common part for all TL Managed Objects | | <---- Specific requirements for TP over CLNS +----------+ NL | ES-IS | <---- Common part for all NL Managed Objects | CLNP | <---- Specific reqirements for CLNS over LAN +----------+ DLL| LLC1 | <---- Common part for all DLL Managd Objects | CSMA/CD | <---- Specific requirements for LAN | | <---- Specific requirements for CSMA/CD LAN +----------+ The EGLL offers to assist in the grouping of managed objects into those that are common and those that are profile specific. EWOS/EGLL also briefy reviewed OIW/NMSIG-94/354 (CLNSME.R08) and found several issues of an editorial nature. A maked-up version of NMSIG-94/354 was provided to the editor, Kedem Kaminsky, for his consideration n preparation of the next draft (CLNSME.R09). EWOS/EGLL expects to receive a revised draft fr review and comments prior to the January 1995 meeting of EWOS/EGLL. ============ END OF EWOS/EGLL LIAISON ========================== Attached NMSIG-94/357 To: OIW SNMSIG (nmsigxics.uci.edu) OIW LLSIG (oiw-llsigxosi.ncsl.nist.gov) EWOS EGNM (ewos-egnmxextenal.iiag.ac.ve) EWOS LLSIG (magnusxvnet.ibm.com) AOW NMSIG (aownmsigxstc.ipa.go.jp) AOW LLSIG CC: Ted Lanberg, OIW Chair (landbergxsst.ncsl.nist.gov Brenda Gray, OIW Secretariat (bgrayxsst.ncsl.nist.gov) Teresa Bolton, OIW Secretariat (boltonxsst.ncsl.nist.gov) From: OIW Systmm and Network Management SIG (SNMSIG) (Contact: Kedem Kaminsky 2551 Riva Road Annapolis, Md. 21401 USA EMAIL: kkxarinc.com Phone: (410)-266-2989 FAX: (410)-266-4499) Subject: Taxonomy for Lower Layer Ensemble and Managed Object Profiles The OIW appreciates EWOS EGNM comments on Ensemble and MO Profile Taxonomy. At the September 94 OIW workshop the OIW SNMSIG reviewed the EWOS contribution (NMSIG-94/238) on Ensemble and MO Profile taxonomy. This liaison coveys comments of OIW LLSIG, EWOS EGLL, OIW SNMSIG, and EWOS EGNM experts identifying other, more desirable, alternatives (other than proposed by the RW NM groups) for the Lower Layer Ensemble Taxonomy. The comment numbers correspond to the attached EWOS document (NMSIG-94/238). 1. The OIW agrees that Ensembles should be developed as a AOM3 taxonomy. The OIW also agrees with the proposed AOM3 taxonomy. The OIW also agrees that AOM311 should be the Connectionless Transport, Network, and Datalink Systems Management Ensemble for TA/RA/RD ISP and AOM312 should be the Connection Oriented Transport, Network, and Datalink Systems Management Ensemble for TB/TB/TC/TD/TE ISPs. Please note the change in title per the AOW comments about the title. 2. The OIW NMSIG is of the opinion the each T and R ISP should be updated to include an optional management capability. The Ensemble will make support of the management capability mandatory. Ensemble -------- Y Y------> Set of AOM for X.700 capabilities Y Y Y Y------> Set of ISP for MIB capabilities -------- T or R ISP -------- Y Y------> Management Object Profile (ISP Part) Y Y Y Y------> T or R resource requirements -------- 3. The OIW is of the opinion that there is no need for the FOM taxonomy because the requirements list is derived on from the ISP. An example of how this works is as follows: Set of MOCS are reference by a MO Profile MOCS TL <----------- CO TL Objects Part A MOCS ISIS PART B MOCS IDRP Part C MOCS NL <----------- CLNS NL Objects Part D MOCS DL <----------- CSMA/CD Objects Part E A System Management Functions (SMF) requires the use of TL MOCS Part A, and NL MOCS part D, and DL MOCS Part E. SMF Y requires the use of MOCS IRDP Part C, NL MOCS Part D, and DL MOCS Part E. Shown in a diagram: SMF X SMF Y SMF Z ----- ------ ------ Y Y---->A Y Y---->C Y Y Y Y---->D Y Y---->D Y Y---->D Y Y---->E Y Y---->E Y Y---->E ----- ----- ------ We can then describe Ensembles in the 4 environments CO, CL, CL transport, and convergence. From a system view we envisioned and ensemble to manage one of these environments. We described the following diagram: TA51 TA53 ---- ----- Y Y----> SMF X Y Y---> SMF X Y Y----> SMF Z RA Y Y---> SMF Y Y Y ---- Y Y Y Y-----------> Y Y-------->Y Y ---- ---- ----- Y Y TA53 Y ----- Y RD Y Y Y ----- Y Y -------------->Y Y -----> Y Y ----- ----- ===================================================================== Attached --------- Begin NMSIG/94-238 NMSIG-94/238 Title: Comments related to MO Profile/Ensemble taxonomy Source: Erik Jonsson (EWOS EG NM) Status: Input to interim meeting on OSI Lower Layer Ensembles (Aug. 1994) An area that will require some work before the profile abstracts for the MO Profiles and Ensembles can be finalised is the related taxonomy. We need to define a general structure for the FOM taxonomy and for the AOM3 taxonomy. This document contains a first proposal for initial discussion. Taxonomy for FOM ---------------- FOM profiles (Managed Object Profiles) can be expected for a variety of resources in the future. The taxonomy should give room for extensions in the future, but at the same time provide short taxonomy identifiers for ease of reference. In this proposal, actual profiles are marked with a (*) to separate the profiles from the taxonomy structure FOM - Managed Object Profiles FOM1 - MO Profiles related to Management Support Objects -- This branch could be used for FOM profiles related to management support objects (such as Security, Performance, Testing) if we choose to develop FOM profiles instead of AOM2x profiles. FOM2 - MO Profiles related to OSI Lower Layers FOM21 - Transport Layer MO Profiles *FOM211 - Connectionless transport *FOM212 - Connection-oriented transport FOM22 - Network Layer MO Profiles *FOM221 - Connectionless Network layer *FOM222 - Connection-oriented Network layer *FOM223 - ISIS *FOM224 - IDRP FOM23 - Data Link Layer MO Profiles *FOM231 - ?? *FOM232 - ?? -- Further brances at this level could be used for physical layer MO profiles and MO profiles with combinations of Os from more than one layer. FOM3 - MO Profiles related to OSI Upper Layers (including OSI Applications) -- This branch could be subdivided in different application areas (MHS, Directory) Taxonomy for AOM3 ----------------- AOM3 is expected to be used for all Ensembles published as ISPs. Room must be given for possible extensions in the future. We have no clear picture today on future possible use of the AOM3x taxonomy. AOM - OSI Management AOM1 - Management Communications AOM2 - Management Function AOM3 - Management Ensembles AOM31 - Ensembles for management of OSI Lower Layers *AOM311 - Connectionless environment *AOM312 - Connection-oriented environment AOM32 - Ensembles for management of OSI application - This branch could be used for ensembles related to management of complete OSI applications (including any management support objects necessary) -- Further branches could be added for other types of ensembles. Depending on the scope of NM EG/SIGs. It is also possible to open up the use of some brances to other organisations (such as NM Forum). ======================================================================