1 .\" $NetBSD: iso_addr.3,v 1.9 2009/04/11 15:32:03 joerg Exp $
4 .\" The Regents of the University of California. All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. Neither the name of the University nor the names of its contributors
15 .\" may be used to endorse or promote products derived from this software
16 .\" without specific prior written permission.
18 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30 .\" @(#)iso_addr.3 8.1 (Berkeley) 6/4/93
38 .Nd elementary network address conversion routines for Open System Interconnection
45 .Fn iso_addr "const char *cp"
47 .Fn iso_ntoa "struct iso_addr *isoa"
51 interprets character strings representing
53 addresses, returning binary information suitable
54 for use in system calls.
61 strings representing NSAPs (network service
63 notation inverse to that accepted by
66 Unfortunately, no universal standard exists for representing
70 The format employed by
72 is a sequence of hexadecimal
74 (optionally separated by periods),
76 .Bd -filled -offset indent
77 \*[Lt]hex digits\*[Gt].\*[Lt]hex digits\*[Gt].\*[Lt]hex digits\*[Gt]
80 Each pair of hexadecimal digits represents a byte
81 with the leading digit indicating the higher-ordered bits.
82 A period following an even number of bytes has no
83 effect (but may be used to increase legibility).
84 A period following an odd number of bytes has the
85 effect of causing the byte of address being translated
86 to have its higher order bits filled with zeros.
89 always returns a null terminated string.
91 always returns a pointer to a struct iso_addr.
101 functions appeared in
105 reside in a static memory area.
109 should diagnose improperly formed input, and there should be an unambiguous
110 way to recognize this.