ITU Telecommunication Standardization Sector (ITU-T). Information Technology - Open Systems Interconnection - The Directory: Authentication Framework. Recommendation X.509 (03/00), International Telecommunication Union, 2000.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....concerning likely behaviour; identity therefore does not imply privilege. We assume virtual anonymity and therefore we do not require (but do allow) the ability to establish the identity of a given entity in absolute terms, e.g. through globally unique and meaningful X. 500 distinguished names [10]. The nature of MANETs makes it inherently di#cult to rely on centralized or online servers. As an example, consider authentication based on Kerberos, which is based on the idea of having a global hierarchy of trust, where leaf and interior nodes trust their superior. This model does not work when ....

ITU: The Directory: Overview of Concepts, Models and Service. ITU-T Rec. X.500, Information Technology - Open Systems Interconnection, (1993), http://www.itu.int/home/index.html.

.... IN functions [Service Control Function (SCF) Specialised Resource Function (SRF) using the IN Application Protocol (INAP) 2] The TMN Operations System Functions (OSFs) manage the IN entities through q reference points supported by the Common Management Information Service Protocol (CMIS P) [11]. Manageable aspects of those entities are modelled as Managed Objects (MOs) specified in the Guidelines for the Definition of Managed Objects (GDMO) object oriented specification language. Figure 1 depicts IN functional entities as managed network elements and represents the current thinking in ....

ITU-T X.710 / X.711, Information Technology - Open Systems Interconnection - Common Management Information Service/Protocol, Version 2

....resources while applications in manager roles access these objects in order to implement management policies. Managed objects are formally specified in GDMO [X722] which is a formal object oriented specification language with emphasis in management. The associated service protocol (CMIS P) [X710] has essentially remote method call semantics. The separation between manager and agent roles serves the purpose of the model and it is not strong in engineering terms: applications and even objects may be in both roles and this is in fact the norm in a hierarchical layered architecture such as ....

ITU-T X.710 / X.711, Information Technology - Open Systems Interconnection - Common Management Information Service/Protocol, Version 2

....and destination of all event reports that the agent generates. A related SMF is the Log Control function [X735] which permits event logging according to manager configurable criteria. To reduce requirements for remote polling and data retrieval the Metric Monitor [X738] and Summarization SMFs[X739] have been developed. Together they permit manager app[X722] ITU X.722,Information Technology Structure of Management Information: Guidelines For The Definition of Managed Objects, January 1992.lications to configure agents to undertake localised polling, threshold checking, data summarization ....

....model e.g. scoping, filtering and multiple replies. A primary advantage in selecting the OSIMIS platform is the provision of a large number of Systems Management Functions (SMFs) These include the Event Report Management [X734] Log Control[X735] Object Management [X730] Metric Monitor [X739] and Summarization [X738] SMFs. 8 4.1 Support for event driven system organisation The Coordinator Knowledge Source abstraction may be used to realise OSI s event driven infrastructure. An OSI agent can be implemented with one Coordinator object instance listening to all external communication ....

ITU Draft Recommendation X.739, Information Technology - Open Systems Interconnection - Systems Management - Metric Objects And Attributes, September 1993.

....distinction between the service offered by a layer and the underlying protocol that achieves those services, whilst SNMP makes no such distinction. OSI management s services and protocol are defined by the Common Management Information Service [X710] and the Common Management Information Protocol [X711] respectively. In placing the emphasis for Manager Agent communications between asynchronous interrupt driven and polling based approaches, SNMP selected trap directed polling , whilst OSI adopted an event driven approach. Upon an extraordinary event the SNMP agent emits a simple Trap ....

ITU X.711, Information Technology - Open Systems Interconnection - Common Management Information Protocol Definition, Version 2, 7/91

....naming tree 2.2 Protocol Operations OSI makes a distinction between the service offered by a layer and the underlying protocol that achieves those services, whilst SNMP makes no such distinction. OSI management s services and protocol are defined by the Common Management Information Service [X710] and the Common Management Information Protocol [X711] respectively. In placing the emphasis for Manager Agent communications between asynchronous interrupt driven and polling based approaches, SNMP selected trap directed polling , whilst OSI adopted an event driven approach. Upon an ....

ITU X.710, Information Technology - Open Systems Interconnection - Common Management Information Service Definition, Version 2, 7/91

.... technological merit, simplicity of development or Government profiles, considerable investments have been made and will continue to be made into the provision of network management solutions based on the two dominant management protocol architectures, namely SNMPv1[RFC1155,RFC1157,RFC1212] and OSI[X701,720]. They exist together so they must be made to co exist, so as to achieve global inter working across heterogeneous platforms in the management domain. It is the authors contention that co existence can most readily be achieved by selecting a semantically rich reference model as the basis for ....

ITU X.701, Information Technology - Open Systems Interconnection - Systems Management Overview, 7/91

....approach. The key question to be asked in the case of OSI management is where exactly the line between generic and specific infrastructure should be drawn in order to result in industry standard APIs. Initiatives in this area have drawn the line too low, exactly at the management service level [X710]. The current widely acceptable API is X Open s XOM XMP [XOpen] XOM being the abstract syntax API while XMP the management service one, commonly designed for both the OSI CMIS and the Internet SNMP. Though this allows for the provision of conformant management protocol stacks, it does very little ....

ITU X.710, Information Technology - Open Systems Interconnection - Common Management Information Service Definition, Version 2, 7/91

....can also be used to provide autonomous control within a managed system. 2.2 Access to Remote Managed Systems An example of this is shown in Figure 3. Here the managed system marked A in the centre of the figure contains an AMO which controls an interpreter offering the full CMIS client service[14]. This service is being used to manage a subordinate managed system. At the same time, A is itself being managed by a higher level managing system. Figure 3 Hierarchical Management viaAMOs. This gives fully hierarchical management controlled by scripts which can be downloaded at runtime. ....

ITU-T X.710 - Information Technology - Open Systems Interconnection - Common Management Information Service/Protocol, Version 2.

....in which all of the parties are known. Trust management systems generalize traditional mechanisms by operating in distributed systems and eliminating the closed world assumption. Over the last ten years, a number of trust management systems have been developed, some focusing on authentication [20, 21, 22], others for specialized purposes [3, 8, 18] others for general purpose authorization [4, 6, 13] and others based on logics [1, 2, 17] Because of the wide range in precision in the specification of these systems and the wide variety of trust management languages, it is difficult to compare the ....

....contains an authmap consisting of the least upper bound of all of the assertions applied to the authmap in the previous row. The final row is the least fixpoint authmap of the set of assertions. The examples give some idea of how least fixpoint computation can express concepts like path validation [20], chaining and five tuple reduction [13] and interassertion communication [7] A trust management engine makes a decision based on a request, an authorizing principal, and a set of assertions. The authorizing principal reflects the policy governing the request. A request is expressed as an ....

I. T. Union. ITU-T recommendation X.509 (08/97) -- information technology -- open systems interconnection -- the directory: Authentication framework, Aug. 1997.

....time a decision is required. Through this approach it is possible for a remote client to deploy management behaviour and algorithms inside the remote server. This concept has its parallel in traditional management systems through the use of the OSI management Systems Management Functions (SMFs) [17] for event forwarding and logging, resource monitoring, and testing, albeit in a more limited way. Previous research work [18] 19] has demonstrated how clients can take advantage of these generic facilities to simplify the construction of intelligent clients. Rather than being restricted to ....

ITU-T Recommendations X.730-750, Information Technology - Open Systems Interconnection - Systems Management Functions.

.... management co operation respectively; it also defines the ConS reference point for providing connectivity services to Retailers and the Ret and TCon reference points for providing services to end users [3] While the TMN currently uses the manager agent model and OSI Systems Management (OSI SM) [4] protocols as the basis for its interoperable interfaces, TINA advocates the use of more general purpose distributed processing technologies such as OMG s Common Object Request Broker Architecture (CORBA) 5] The recent emergence of execute anywhere languages like Java has made code mobility ....

ITU-T Rec. X.701, Information Technology - Open Systems Interconnection, Systems Management Overview, 1992.

....worked on relationships and dependencies. In the work of the TeleManagement Forum [Tel00] dependencies are identified but not further studied. They included the requirement that the dependent object must publish its dependencies, just as we did in our work. The General Relationship Model (GRM) IT95] describes an architecture for arbitrary relationships as well as methods to define and represent them in the TMN framework. The model does not specifically address service dependencies. These could be modeled with the methods of the GRM, though. The CIM model [Dis99] defines dependencies between ....

ITU-T. Recommendation X.725 (11/95) -- Information technology -- Open Systems Interconnection -- Structure of management information: General relationship model. November 1995.

....connection graph has to be issued (SETUP) These negotiation and atomicity principles are well known from other complex signaling systems. In 1993 the ITU T has already standardized a protocol for commitment, concurrency and recovery during capability exchange in its recommendations X. 851 852 [9]. IV. RELATED WORK The use of SIP as a general transaction protocol for service signaling has also been recognized by other approaches, but with a different focus, as we will discuss in the following. In IETF PINT [8] SIP is used for the transfer of session description in IP networks between a ....

ITU-T Recommendations X.851/2. Information Technology Open Systems Interconnection - Protocol For The Commitment, Concurrency And Recovery Service Element. ITU-T, 1993.

.... system specifications with the 1992 edition of the Specification and Description Language (SDL 92) and test purpose descriptions with the 1996 version of Message Sequence Charts (MSC 96) as input and produce test suites based on the second edition of the Tree and Tabular Combined Notation (TTCN 2) [14]. Meanwhile, the standards of both SDL and MSC have been updated (SDL2000 [16] MSC 2000 [15] and a thoroughly new version of TTCN has been standardized (TTCN 3 [7] In addition, the European Commission has set up the Interval project [21] to prototype an SDL, MSC and TTCN based tool chain for ....

ITU-T, Geneva, Switzerland. Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 3: The Tree and Tabular Combined Notation, 1997. ITU-T Recommendation X.293-ISO/IEC 9646-3.

....and authorization steps . A protection state represents the active permissions of each step. While this helps to link authorizations to specific tasks, it needs a consistent way to control the operations to be authorized to prevent any kind of abuse. SPKI [3] and X. 509 Attribute Authorities [7] allow a fine grained access control by signed attributes that specify the access rights. Both consider concepts for delegation of rights. However, it is very hard to bring the delegation into the context of a specific task. Thus, the problem remains that rights are passed independently from a ....

ITU-T Recommendation X.509, ISO/IEC 9594-8. Information Technology -- Open Systems Interconnection -- The Directory: Public-Key and Attribute Certificate Frameworks. 4th Edition, Draft V7. February, 2001.

.... actual amount authorized, other payment, transaction and protocol details. SigPayAckObject should also bear the certificate of the merchant signed by MFI in order to allow the consumer to check the validity of the merchant s signature over SigPayAckObject. The standard X. 509 [9] certificate lists are proposed for this purpose in [5] However, this proposal is vague and the details are missing in [5] Thus we propose a novel method for merchant s public key transfer from MFI to consumer. This method will be described in Section 3.5. X9.59 standard also defines a signed ....

ITU-T Recommendation X.509, ISO/IEC 9594-8, Information Technology - Open Systems Interconnection - The Directory: Public-key and Attribute Certificate Frameworks, 2000 (fourth) edition.

....(CO) are identified. First, the Accountable Object (AO) represents sources from which the network and other resource usage measurement is obtained. An AO is a generic object which may be an information object such as a VOD server or representing a resource layer component such as defined in X. 742 [12]. Second, one Metering Manager exists in each accounting management domain. The Metering Manager receives and logs the accounting events reported by the Accountable Object. Finally, one Accounting Policy Manager exists in each accounting management domain to maintain the accounting policies for ....

ITU-T, "Information Technology, Open Systems Interconnection, Systems Management: Usage Metering Function for Accounting Purposes", ITU-T Recommendations X.742, April 1995.

....and digital signature transfers for client and server authentication. The SSL session is established when the initial handshake between client and server takes place. The message flow during this handshake operation is represented in figure 3. SSL authentication uses X. 509 certificates standard [9] to transfer an application s public key information. SSL v3 uses X.509 v3 certificates to ensure RSA keys, and a modified X.509 certificates to ensure public keys used by the key distribution protocol of the US Department of Defense (DoD) the Fortezza DMS. The X.509 certificates have certifying ....

ITU-T, "Information Technology -- The Open Systems Interconnection -- The Directory: Autentication Framework", ITU-T Recommendation X509, Nov. 1993.

....List, CRL) Maintaining the strictest possible security for the CA s private key Ensure that the CA s own certificate is widely distributed Establishing trust among the members of the infrastructure Providing risk management The digital certificates are based on the X. 509 standard [3]. X.509 is the authentication framework designed to support X.500 directory [4] its part of the X series of international standards proposed by the ISO and ITU. X.500 was designed to provide directory services on large computer networks. X.509 provides a PKI framework for authenticating X.500 ....

ITU /ISO Recommendation X.509. - Information technology - Open Systems Interconnection - The Directory: Authentication framework. August 1997. http://www.itu.int//itudoc/itu-t/rec/x/x500up/x509.html

....numerous encryption and digest mechanisms that the client and the server negotiate during the SSL handshake. Figure 2 shows the exchange of messages in the handshake, details of which are discussed in Section 3.2. Authentication is based on a public key challenge response protocol and X. 509 [5] identity certi cates. SSL supports mutual authentication. First, a user authenticates the server. The user has the responsibility to make sure it can trust the certi cate it received in Certificate message from the server. That responsibility includes verifying the certi cate signatures, validity ....

ITU-T (formerly CCITT) Information technology Open Systems Interconnection. Recommendation x.509: The directory authentication framework, December 1988.

....are read out by the transport layer service Data are written into the adapter s memory Data are sent out over the connection 1 2 3 4 5 6 Figure 3 Interactions among the framework planes. plane data movement data processing End user of them specifically the OSI reference model (ITU T X.200, 1994) and QoS A from Lancaster University, UK, Campbell, et al. 1994) show many architectural similarities with the framework proposed in this paper. Our framework may relate, at first sight, to the OSI model (ITU T X.200, 1994) However, the two architectures do differ in their underlying ....

....processing End user of them specifically the OSI reference model (ITU T X.200, 1994) and QoS A from Lancaster University, UK, Campbell, et al. 1994) show many architectural similarities with the framework proposed in this paper. Our framework may relate, at first sight, to the OSI model (ITU T X.200, 1994). However, the two architectures do differ in their underlying philosophies and layerings. The OSI philosophy consists in describing the interfaces between the layers exhibited by the architecture, some of which are termed the same in our architecture. On the other hand, our framework depicts a ....

[Article contains additional citation context not shown here]

ITU-T Rec. X.200. (July 1994) Information Technology - Open Systems Interconnection - Basic Reference Model: The Basic Model. Also known as ISO/IEC 7498-1.

....for example different coding algorithms and presentation qualities. Signaling primitives allow the construction, modification and deletion of elementary call objects. In order to reduce the number of information flows and to handle multiparty relations, a generic atomic action mechanism is used [3,8]. Atomic actions allow to group operations, that can only succeed or fail as a unit. Further, it uses a two phase commit procedure, which includes a roll back in the case of rejection. 2.2 An Example Multimedia Call The following example call clarifies the described call model. In Figure 1, an ....

ITU-T Recommendation X.851: Information Technology - Open Systems Interconnection - Service Definition for the Commitment, Concurrency and Recovery Service Element. ITU-T, March 1993.

....2.1 Identity Identity is fundamental to higher level security services such as access control. Every Legion object is identified by a unique, multi field, location independent Legion Object Identifier, or LOID. One of the LOID fields contains security information such as an X. 509 certificate [3] or more simply just an RSA public key. The X.509 certificate in the LOID is not an X9.57 attribute certificate [16] but rather an ID certificate (also referred to as a public key certificate [4] and pairs a public key with a person s name, organization, identification of the public key ....

ITU-T Recommendation X.509 (1997 E). Information technology - open systems interconnection - the directory: Authentication framework.

.... of managed objects manifest themselves implicitly through their names i.e. there is no explicit information in an object s attributes denoting the containing and contained objects [6] Other relationships manifest themselves as pointer attributes that contain the name of a related managed object [8]. Managed objects in a MIT may be accessed either individually or collectively, through an object oriented database query facility. Many objects may be selected by traversing containment relationships through scoping. The selection may be further eliminated by specifying a filter expression to be ....

....extension. In the case of CMIP though, this means the OSI SM MIM should be slightly modified. In general, MOs are linked through generic relationships, rather than through the simple containment relationship, as shown in Fig. 2. Object references are supported through pointer attributes [8]. Therefore, no extension is required with respect to the data definition language provided, in this context, through the Guidelines for the Definition of Managed 0 7803 4386 7 98 10.00 (c) 1998 IEEE 0 7803 4386 7 98 10.00 (c) 1998 IEEE Objects (GDMO) 7] In the following sub sections we ....

ITU-T Rec. X.720, Information Technology - Open Systems Interconnection - Structure of Management Information - General Relationship Model, 1992.

....resources at various levels of abstraction. Applications in manager roles access these objects in order to realize management policies. Managed objects conform to the Management Information Model [6] and are formally specified using the Guidelines for the Definition of Managed Objects (GDMO) [7]; the latter is an object oriented information specification language. The CMIS access service [3] has remote method call semantics and allows also operations on multiple objects. The OSI manager agent model is shown in Figure 1. Managed Objects (MOs) Managing Objects (M Os) Management ....

.... are supported through pointer attributes [8] Therefore, no extension is required with respect to the data definition language provided, in this context, through the Guidelines for the Definition of Managed 0 7803 4386 7 98 10.00 (c) 1998 IEEE 0 7803 4386 7 98 10.00 (c) 1998 IEEE Objects (GDMO) [7]. In the following sub sections we propose to extend CMIS with path expressions in order to enhance its expressive power for retrieving interconnected objects. Each path expression consists basically of a sequence of attribute names, represented through a dot notation , that gives the way to ....

ITU-T Rec. X.732, Information Technology - Open Systems Interconnection - Structure of Management Information - Guidelines for the Definition of Managed Objects, 1992.

....model, with applications in agent roles exporting Managed Objects (MOs) that encapsulate managed resources at various levels of abstraction. Applications in manager roles access these objects in order to realize management policies. Managed objects conform to the Management Information Model [6] and are formally specified using the Guidelines for the Definition of Managed Objects (GDMO) 7] the latter is an object oriented information specification language. The CMIS access service [3] has remote method call semantics and allows also operations on multiple objects. The OSI ....

....in the agent and the access management service and supporting protocol stack. The containment relationships of managed objects manifest themselves implicitly through their names i.e. there is no explicit information in an object s attributes denoting the containing and contained objects [6]. Other relationships manifest themselves as pointer attributes that contain the name of a related managed object [8] Managed objects in a MIT may be accessed either individually or collectively, through an object oriented database query facility. Many objects may be selected by traversing ....

[Article contains additional citation context not shown here]

ITU-T Rec. X.720, Information Technology - Open Systems Interconnection - Structure of Management Information-Management Information Model, 1992.

....[2] as the means to model manageable resources and the associated access service and protocol to standardize interactions across management interfaces. The OSI SM access service and protocol are the Common Management Information Service (CMIS) 3] and Common Management Information Protocol (CMIP) [4] respectively. Managed elements and management applications acting in agent roles contain clusters of Managed Objects (MOs) organized in a Management Information Tree (MIT) according to containment relationships. MOs exhibit hierarchical names that are based on the containment relationships. ....

....procedures and, as such, CMIS supports a combination of the two, adding also multiple step evaluation within a single request. Naturally, CMIP is only different to CMIP in the sense that scope and filter have been replaced by the objectSelection parameter. The CMIP protocol data units [4] are specified in the Abstract Syntax Notation One (ASN.1) language [11] CMIP retains that specification but replaces scope and filter with the new objectSelection parameter which is also specified in ASN.1. The exact object selection syntax is presented in appendix. The structure of this ....

ITU-T Rec. X.710, Information Technology - Open Systems Interconnection - Common Management Information Protocol Specification, Version 2, 1991.

....architecture of OSI System Management (OSI SM) 2] as the means to model manageable resources and the associated access service and protocol to standardize interactions across management interfaces. The OSI SM access service and protocol are the Common Management Information Service (CMIS) [3] and Common Management Information Protocol (CMIP) 4] respectively. Managed elements and management applications acting in agent roles contain clusters of Managed Objects (MOs) organized in a Management Information Tree (MIT) according to containment relationships. MOs exhibit hierarchical names ....

....in order to realize management policies. Managed objects conform to the Management Information Model [6] and are formally specified using the Guidelines for the Definition of Managed Objects (GDMO) 7] the latter is an object oriented information specification language. The CMIS access service [3], has remote method call semantics and allows also operations on multiple objects. The OSI manager agent model is shown in Figure 1. Managed Objects (MOs) Managing Objects (M Os) Management Interface (CMIS P) operations notifications M A application in Manager role application in Agent ....

[Article contains additional citation context not shown here]

ITU-T Rec. X.710, Information Technology - Open Systems Interconnection - Common Management Information Service Definition, Version 2, 1991.

....the basis of future telecommunication infrastructures poses complex management requirements. ITU T has developed the Telecommunication Management Network (TMN) 1] as the framework for their management. The latter uses the objectoriented information architecture of OSI System Management (OSI SM) [2] as the means to model manageable resources and the associated access service and protocol to standardize interactions across management interfaces. The OSI SM access service and protocol are the Common Management Information Service (CMIS) 3] and Common Management Information Protocol (CMIP) ....

....federation and discussing also implementation issues. We finally close with a summary and our conclusions, while we briefly discuss potential alternative approaches. 0 7803 4386 7 98 10.00 (c) 1998 IEEE 0 7803 4386 7 98 10.00 (c) 1998 IEEE The OSI System Management Model OSI System Management [2] projects an object oriented model, with applications in agent roles exporting Managed Objects (MOs) that encapsulate managed resources at various levels of abstraction. Applications in manager roles access these objects in order to realize management policies. Managed objects conform to the ....

[Article contains additional citation context not shown here]

ITU-T Rec. X.701, Information Technology - Open Systems Interconnection - Systems Management Overview, 1991.

.... both object models as, to some extent, the important question is the definition of the interfaces shown by those all object to the outside using CORBA IDL (Interface Definition Language) SMIv2 10 (Structure of Managed Information) 20] or GDMO (Guidelines for the Definition of Managed Objects) [21]. So a conversion among those three objects models seems to be an achievable objective. Regarding this last aspect, there are several ongoing initiatives whose results will be very useful for the deployment of the ABS service management architecture. The XoJIDM (X Open Joint Inter Domain ....

ITU-T Recommendation X.722. "Information technology - Open Systems Interconnection - Structure of management information: Guidelines for the definition of managed objects". January 1992.

....Managing applications may also be distributed so the traditional situation of a centralised managing platform tends to be deprecated. Pure distributed managing solutions have to coexist with other vendor specific or standard management frameworks (mainly SNMP [13] and the OSI System Management [14]) Integrated management in distributed processing environments is a very important research topic nowadays. Several choices have appeared for the establishment of management solutions in different distributed environments and for their coexistence with other management frameworks. For example: ....

ITU-T Recommendation X.701. "Information technology - Open Systems Interconnection - Systems management overview". January 1992.

....(mainly performance management) of the service architectural components related to the brokerage information processing. It has not been decided yet whether the implementation of the storing and management of brokerage information will be based on RDBMS technology, OSI Directory environments [6], etc. So, this aspect will not be discussed in this paper. Nevertheless, what it is clear is that previous works on those subjects (as, for instance [7,8] will be reused. In summary, forgetting about the latter described management requirement, we have to face two main questions in order to ....

ITU-T Recommendation X.500. "Information technology - Open Systems Interconnection - The directory: Overview of concepts, models, and services". November 1993.

....similar to CMIS. Of course, managed objects may be also accessed directly in the standard CORBA fashion. Event management is provided by event discriminators and logs through filtering, in order to overcome the relevant CORBA limitations. Finally, the rest of the OSI Systems Management Functions [SMF] are maintained as generic CORBA objects that may be instantiated within a cluster. This approach essentially maintains the OSI operational model over CORBA but replaces the access (i.e. CMIS P) and distribution (OSI directory) mechanisms. As such, it retains the OSI management expressive power, ....

ITU-T Rec. X.730-750, Information Technology - Open Systems Interconnection - Systems Management Functions.

No context found.

ITU Telecommunication Standardization Sector (ITU-T). Information Technology - Open Systems Interconnection - The Directory: Authentication Framework. Recommendation X.509 (03/00), International Telecommunication Union, 2000.

No context found.

ITU Telecommunication Standardization Sector (ITU-T). Information Technology - Open Systems Interconnection -- The Directory: Authentication Framework. Recommendation X.509 (03/00), International Telecommunication Union, 2000.

No context found.

ITU Recommendation X.509 version 3. Information Technology - Open Systems Interconnection - The Directory Authentication Framework, August 1997.

No context found.

ITU Recommendation X.509 version 3. Information Technology - Open Systems Interconnection - The Directory Authentication Framework, August 1997.

No context found.

ITU X.509. Information technology - open systems interconnection - the directory: Public-key and attribute certificate frameworks. Technical report, ITU, 2000. 23

No context found.

ITU X.509. Information technology - open systems interconnection - the directory: Public-key and attribute certificate frameworks. Technical report, ITU, 2000.

No context found.

ITU. Recommendation X.500 (11/93) - Information technology - Open Systems Interconnection - The directory: Overview of concepts, models, and services, 1993.

No context found.

ITU X.710, Information Technology - Open Systems Interconnection - Common Management Information Service Definition, Version 2, 7/91 16

No context found.

ITU X.701, Information Technology - Open Systems Interconnection - Systems Management Overview, 7/91

No context found.

ITU-T X.711, Information Technology - Open Systems Interconnection - Common Management Information Protocol Specification, Version 2, July 1991.

No context found.

ITU-T X.750, "Information Technology - Open Systems Interconnection - Systems Management - Management Knowledge Management Function," 1995.

No context found.

ITU-T X.711, "Information Technology - Open Systems Interconnection - Common Management Information Protocol Specification," Version 2, 1991.

No context found.

ITU-T X.710, "Information Technology - Open Systems Interconnection - Common Management Information Service Definition," Version 2, 1991.

No context found.

ITU-T X.701, "Information Technology - Open Systems Interconnection - Systems Management Overview," 1991. TMN ARCHITECTURE ISSUES 71

No context found.

ITU Rec. X.701 (1992) | ISO/IEC 10040, Information Technology - Open System Interconnection (OSI) - Systems Management Overview

No context found.

ITU/ISO Recommendation X.500 -- Information technology -- Open Systems Interconnection -- The directory: Overview of concepts, models, and services. November 1993. 84

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC