Search

Scope: Core (OPC-10000-*) All specs

19 result(s) for HostName

OPC-10000-4 – OPC Unified Architecture - Part 4: Services

3.1.9 HostName

HostName unique identifier for a machine on a network Note 1 to entry: This identifier is unique within a local network; however, it may also be globally unique. The identifier
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

3.1.4 Endpoint

Note 1 to entry: Each Server may have multiple Endpoints . Each Endpoint includes a HostName
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.5.1 Overview

Client shall close the SecureChannel and report an error. A Client shall verify the HostName specified in the Server Certificate is the same as the HostName contained in the endpointUrl ... MyHost.local into the Server Certificate . This includes IP addresses of the host or the HostName exposed by a NAT router used to connect to the Server
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.5.2.2 Parameters

Server should return a suitable default URL if it does not recognize the HostName in the URL. localeIds [] LocaleId List of locales to use. The Server should return the applicationName
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.5.4.2 Parameters

Server should return a suitable default URL if it does not recognize the HostName in the URL. localeIds [] LocaleId List of locales to use. See locale negotiation in 5.4 which
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.6.2.1 Description

securityPolicyUri is None. If the securityPolicyUri is not None, a Client shall verify the HostName specified in the Server Certificate is the same as the HostName contained in the endpointUrl ... MyHost.mycompany.com into the Server Certificate . This includes IP addresses of the host or the HostName exposed by a NAT router used to connect to the Server . Servers shall not append
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.7.2.2 Parameters

Server should return a suitable default URL if it does not recognize the HostName in the URL sessionName String Human readable string that identifies the Session . The Server makes this
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.38.2 Common StatusCodes

complete asynchronously. Good_SubscriptionTransferred The Subscription was transferred to another session. Bad_CertificateHostNameInvalid The HostName used to connect to a Server does not match a HostName in the Certificate
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

4.3.1 Overview

installed on the Client host; Calling FindServers on a remote LDS, where the HostName for the remote host is manually entered ; Calling FindServersOnNetwork
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

4.3.6 Combined Discovery Process for Clients

band mechanism is a way to find a URL or a HostName that is not described by this standard. For example, a user could manually enter
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

5.3.3 Multiple MulticastSubnet

remote MulticastSubnet shall use out of band discovery (i.e. manual entry) of a HostName or DiscoveryUrl . Once a Client finds an LDS-ME on a remote MulticastSubnet
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

5.3.4 No MulticastSubnet

that wants to discover applications uses an out of band mechanism to find the HostName and call FindServers on the LDS of that host . FindServersOnNetwork may also work
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

A.1 Firewalls and Discovery

GetEndpoints or CreateSession services and return EndpointDescriptions with URLs that use the same HostName . A Server with multiple HostNames shall also return an ApplicationInstance Certificate that specifies the HostName used ... create a single Certificate with multiple HostNames or assign different Certificates for each HostName that the Server supports . Note that Servers may not be aware of all HostNames which
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.4 Acquiring and Validating Tickets

however, checks that are specific to Application Instance Certificates do not apply (e.g. the HostName and ApplicationUri checks). Trusted root CertificateAuthorities used to issue Ticket signing Certificates are companies that
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.1 Overview

scalable, and manageable network, certain networking services need to be standardised, including address assignment, HostName resolution, and topology discovery. In addition, limits on various network quantities, such as the number
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.3.1 Overview

addresses. Since the underlying transport protocols (e.g., TCP and UDP) use IP addresses, a HostName needs to first be resolved to an IP address before initiating communications. In both ... networks, the Domain Name System (DNS) is commonly used when HostName resolution is required. By virtue of using OPC UA transport mechanisms, UAFX makes provisions for using HostNames , as described
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.3.2 HostName resolution using DNS

HostName resolution using DNS There are two UAFX communication scenarios where HostName resolution could be used: with UA Client Server communications, such as during UAFX connection establishment, and PubSub communications ... address of the DNS server(s). The DNS server is contacted to resolve the HostName of Controller B, if not already resolved as part of UA session establishment, before issuing
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.3.3 HostName resolution using multicast DNS (mDNS)

HostName resolution using multicast DNS (mDNS) Multicast DNS (mDNS), as specified in IETF RFC 6762 , provides HostName resolution without needing a DNS server. Hosts needing to resolve HostNames issue mDNS ... described in OPC 10000‑12 . Figure 4 illustrates the use of mDNS for HostName resolution during UAFX connection establishment. Figure 4 - Client Server with mDNS resolution
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.4 Server announcement and discovery using mDNS

capability in its mDNS announcements and responses. Note This capability is different from the HostName resolution capability described in 5.3 . In discovering UAFX servers, clients may either use mDNS directly