ISO_ADDR(3) BSD Library Functions Manual ISO_ADDR(3)NAME
iso_addr, iso_ntoa -- elementary network address conversion routines for Open System Interconnection
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/types.h>
#include <netiso/iso.h>
struct iso_addr *
iso_addr(const char *cp);
char *
iso_ntoa(struct iso_addr *isoa);
DESCRIPTION
The routine iso_addr() interprets character strings representing OSI addresses, returning binary information suitable for use in system
calls. The routine iso_ntoa() takes OSI addresses and returns ASCII strings representing NSAPs (network service access points) in a notation
inverse to that accepted by iso_addr().
Unfortunately, no universal standard exists for representing OSI network addresses.
The format employed by iso_addr() is a sequence of hexadecimal ``digits'' (optionally separated by periods), of the form:
<hex digits>.<hex digits>.<hex digits>
Each pair of hexadecimal digits represents a byte with the leading digit indicating the higher-ordered bits. A period following an even num-
ber of bytes has no effect (but may be used to increase legibility). A period following an odd number of bytes has the effect of causing the
byte of address being translated to have its higher order bits filled with zeros.
RETURN VALUES
iso_ntoa() always returns a null terminated string. iso_addr() always returns a pointer to a struct iso_addr. (See BUGS.)
SEE ALSO iso(4)HISTORY
The iso_addr() and iso_ntoa() functions appeared in 4.3BSD-Reno.
BUGS
The returned values reside in a static memory area.
The function iso_addr() should diagnose improperly formed input, and there should be an unambiguous way to recognize this.
BSD June 4, 1993 BSD
Check Out this Related Man Page
ISO(4) BSD Kernel Interfaces Manual ISO(4)NAME
iso -- ISO protocol family
SYNOPSIS
#include <sys/types.h>
#include <netiso/iso.h>
DESCRIPTION
The ISO protocol family is a collection of protocols that uses the ISO address format. The ISO family provides protocol support for the
SOCK_SEQPACKET abstraction through the TP protocol (ISO 8073), for the SOCK_DGRAM abstraction through the connectionless transport protocol
(ISO 8602), and for the SOCK_RAW abstraction by providing direct access (for debugging) to the CLNP (ISO 8473) network layer protocol.
ADDRESSING
ISO addresses are based upon ISO 8348/AD2, Addendum to the Network Service Definition Covering Network Layer Addressing.
Sockets bound to the OSI protocol family use the following address structure:
struct iso_addr {
u_char isoa_len; /* length, not including this byte */
char isoa_genaddr[20]; /* general opaque address */
};
struct sockaddr_iso {
u_char siso_len; /* size of this sockaddr */
sa_family_t siso_family; /* addressing domain, AF_ISO */
u_char siso_plen; /* presentation selector length */
u_char siso_slen; /* session selector length */
u_char siso_tlen; /* transport selector length */
struct iso_addr siso_addr; /* network address */
u_char siso_pad[6]; /* space for gosip v2 SELs */
};
#define siso_nlen siso_addr.isoa_len
#define siso_data siso_addr.isoa_genaddr
The fields of this structure are:
siso_len:
Length of the entire address structure, in bytes, which may grow to be longer than the 32 bytes shown above.
siso_family:
Identifies the domain: AF_ISO.
siso_tlen:
Length of the transport selector.
siso_slen:
Length of the session selector. This is not currently supported by the kernel and is provided as a convenience for user level pro-
grams.
siso_plen:
Length of the presentation selector. This is not currently supported by the kernel and is provided as a convenience for user level
programs.
siso_addr:
The network part of the address, described below.
TRANSPORT ADDRESSING
An ISO transport address is similar to an Internet address in that it contains a network-address portion and a portion that the transport
layer uses to multiplex its services among clients. In the Internet domain, this portion of the address is called a port. In the ISO
domain, this is called a transport selector (also known at one time as a transport suffix). While ports are always 16 bits, transport selec-
tors may be of (almost) arbitrary size.
Since the C language does not provide convenient variable length structures, we have separated the selector lengths from the data themselves.
The network address and various selectors are stored contiguously, with the network address first, then the transport selector, and so on.
Thus, if you had a network address of less than 20 bytes, the transport selector would encroach on space normally reserved for the network
address.
NETWORK ADDRESSING
ISO network addresses are limited to 20 bytes in length. ISO network addresses can take any format.
PROTOCOLS
The ARGO 1.0 implementation of the ISO protocol family comprises the Connectionless-Mode Network Protocol (CLNP), and the Transport Protocol
(TP), classes 4 and 0, and X.25. TP is used to support the SOCK_SEQPACKET abstraction. A raw interface to CLNP is available by creating an
ISO socket of type SOCK_RAW. This is used for CLNP debugging only.
SEE ALSO clnp(4), cltp(4), tp(4)BSD November 30, 1993 BSD