Deleted Added
full compact
1a2,4
> .\" Copyright (c) 2004-2005
> .\" Hartmut Brandt.
> .\" All rights reserved.
29c32
< .\" $Begemot: libunimsg/man/unisap.3,v 1.4 2005/05/23 12:00:10 brandt_h Exp $
---
> .\" $Begemot: libunimsg/man/unisap.3,v 1.5 2005/06/15 11:37:11 brandt_h Exp $
31c34
< .Dd May 23, 2005
---
> .Dd June 14, 2005
91,93c94,97
< SAPs are the analog of TCP and UDP ports in the ATM world. As usually in ATM
< they are a couple of orders of magnitude more complex as their Internet
< equivalent. See the ATM Forum document for a description.
---
> SAPs are the analog of TCP and UDP ports in the ATM world.
> As usually in ATM they are a couple of orders of magnitude more complex as
> their Internet equivalent.
> See the ATM Forum document for a description.
107,108c111,114
< the SETUP message. Each of these elements has a tag that defines how
< the SVE is to be matched with the information element. The tag is one of
---
> the SETUP message.
> Each of these elements has a tag that defines how the SVE is to be matched
> with the information element.
> The tag is one of
126c132
< u_int32_t len; /* length of address */
---
> uint32_t len; /* length of address */
145c151
< u_int8_t selector;
---
> uint8_t selector;
155c161,162
< and one for layer 3 options. The layer 2 SVE is:
---
> and one for layer 3 options.
> The layer 2 SVE is:
159,160c166,167
< u_int8_t proto:5;/* the protocol */
< u_int8_t user:7; /* user specific protocol */
---
> uint8_t proto:5;/* the protocol */
> uint8_t user:7; /* user specific protocol */
174,179c181,186
< u_int8_t proto:5;/* L3 protocol */
< u_int8_t user:7; /* user specific protocol */
< u_int8_t ipi:8; /* ISO/IEC TR 9557 IPI */
< u_int32_t oui:24; /* IEEE 802.1 OUI */
< u_int32_t pid:16; /* IEEE 802.1 PID */
< u_int32_t noipi; /* ISO/IEC TR 9557 per frame */
---
> uint8_t proto:5;/* L3 protocol */
> uint8_t user:7; /* user specific protocol */
> uint8_t ipi:8; /* ISO/IEC TR 9557 IPI */
> uint32_t oui:24; /* IEEE 802.1 OUI */
> uint32_t pid:16; /* IEEE 802.1 PID */
> uint32_t noipi; /* ISO/IEC TR 9557 per frame */
190,191c197,198
< u_int32_t len; /* length of info */
< u_int8_t info[8];/* info itself */
---
> uint32_t len; /* length of info */
> uint8_t info[8];/* info itself */
196c203,204
< specified. The functions
---
> specified.
> The functions
230,234c238,243
< The ATM Forum document defines the concept of overlaping SAPs. This basically
< means, that an incoming SETUP could match more than one SAP (and more than
< one application) to receive the SETUP. For each SVE type there is a function
< that checks whether two SVEs overlap and there is a function that checks whether
< two SAPs overlap. The functions
---
> The ATM Forum document defines the concept of overlaping SAPs.
> This basically means, that an incoming SETUP could match more than one SAP
> (and more than one application) to receive the SETUP.
> For each SVE type there is a function that checks whether two SVEs overlap
> and there is a function that checks whether two SAPs overlap.
> The functions
241,242c250,251
< return 1 if the SVEs or SAPs overlap and 0 if they do not. They assume, that
< the SAPs are correct.
---
> return 1 if the SVEs or SAPs overlap and 0 if they do not.
> They assume, that the SAPs are correct.
244c253,254
< The ATM Forum document specifies a catch-all SAP. The function
---
> The ATM Forum document specifies a catch-all SAP.
> The function