| unisap.3 (131823) | unisap.3 (146532) |
|---|---|
| 1.\" 2.\" Copyright (c) 2001-2003 3.\" Fraunhofer Institute for Open Communication Systems (FhG Fokus). 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: --- 12 unchanged lines hidden (view full) --- 21.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 22.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 23.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 24.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 25.\" SUCH DAMAGE. 26.\" 27.\" Author: Hartmut Brandt <harti@freebsd.org> 28.\" | 1.\" 2.\" Copyright (c) 2001-2003 3.\" Fraunhofer Institute for Open Communication Systems (FhG Fokus). 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: --- 12 unchanged lines hidden (view full) --- 21.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 22.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 23.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 24.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 25.\" SUCH DAMAGE. 26.\" 27.\" Author: Hartmut Brandt <harti@freebsd.org> 28.\" |
| 29.\" $Begemot: libunimsg/man/unisap.3,v 1.2 2003/08/21 16:01:08 hbb Exp $ | 29.\" $Begemot: libunimsg/man/unisap.3,v 1.4 2005/05/23 12:00:10 brandt_h Exp $ |
| 30.\" | 30.\" |
| 31.Dd August 23, 2002 32.Dt unisap 3 | 31.Dd May 23, 2005 32.Dt UNISAP 3 |
| 33.Os 34.Sh NAME 35.Nm unimsg , 36.Nm unisve_check_addr , 37.Nm unisve_check_selector , 38.Nm unisve_check_blli_id2 , 39.Nm unisve_check_blli_id3 , 40.Nm unisve_check_bhli , --- 60 unchanged lines hidden (view full) --- 101 struct unisve_blli_id3 blli_id3; 102 struct unisve_bhli bhli; 103}; 104.Ed 105.Pp 106that consists of 5 elements matching different information elements in 107the SETUP message. Each of these elements has a tag that defines how 108the SVE is to be matched with the information element. The tag is one of | 33.Os 34.Sh NAME 35.Nm unimsg , 36.Nm unisve_check_addr , 37.Nm unisve_check_selector , 38.Nm unisve_check_blli_id2 , 39.Nm unisve_check_blli_id3 , 40.Nm unisve_check_bhli , --- 60 unchanged lines hidden (view full) --- 101 struct unisve_blli_id3 blli_id3; 102 struct unisve_bhli bhli; 103}; 104.Ed 105.Pp 106that consists of 5 elements matching different information elements in 107the SETUP message. Each of these elements has a tag that defines how 108the SVE is to be matched with the information element. The tag is one of |
| 109.Bl -tag -widht ".It Dv UNISVE_PRESENT" | 109.Bl -tag -width ".Dv UNISVE_PRESENT" |
| 110.It Dv UNISVE_ABSENT 111The information element has to absent from the SETUP message. 112.It Dv UNISVE_PRESENT 113The information element has to be present in the SETUP message and must 114match the SVE. 115.It Dv UNISVE_ANY 116The information element may be absent from the SETUP message or may 117have any value. --- 42 unchanged lines hidden (view full) --- 160 u_int8_t user:7; /* user specific protocol */ 161}; 162.Ed 163.Pp 164Where the 165.Fa user 166fields is matched only if the 167.Fa proto | 110.It Dv UNISVE_ABSENT 111The information element has to absent from the SETUP message. 112.It Dv UNISVE_PRESENT 113The information element has to be present in the SETUP message and must 114match the SVE. 115.It Dv UNISVE_ANY 116The information element may be absent from the SETUP message or may 117have any value. --- 42 unchanged lines hidden (view full) --- 160 u_int8_t user:7; /* user specific protocol */ 161}; 162.Ed 163.Pp 164Where the 165.Fa user 166fields is matched only if the 167.Fa proto |
| 168field specifies | 168field specifies |
| 169.Dv UNI_BLLI_L2_USER . 170The layer 3 SVE is: 171.Bd -literal -offset indent 172struct unisve_blli_id3 { 173 enum unisve_tag tag; 174 u_int8_t proto:5;/* L3 protocol */ 175 u_int8_t user:7; /* user specific protocol */ 176 u_int8_t ipi:8; /* ISO/IEC TR 9557 IPI */ --- 40 unchanged lines hidden (view full) --- 217A code of 218.Li UNISVE_OK 219means that the SVE has no error. 220The function 221.Fn unisve_check_sap 222checks a complete SAP and returns one of the above codes. 223.Pp 224There is a definition | 169.Dv UNI_BLLI_L2_USER . 170The layer 3 SVE is: 171.Bd -literal -offset indent 172struct unisve_blli_id3 { 173 enum unisve_tag tag; 174 u_int8_t proto:5;/* L3 protocol */ 175 u_int8_t user:7; /* user specific protocol */ 176 u_int8_t ipi:8; /* ISO/IEC TR 9557 IPI */ --- 40 unchanged lines hidden (view full) --- 217A code of 218.Li UNISVE_OK 219means that the SVE has no error. 220The function 221.Fn unisve_check_sap 222checks a complete SAP and returns one of the above codes. 223.Pp 224There is a definition |
| 225.Dv UNISVE_ERRSTR | 225.Dv UNISVE_ERRSTR |
| 226that evaluates to a comma separated list of strings that can be used 227to initializes an array of char pointers to map the error codes into 228human readable strings. 229.Pp 230The ATM Forum document defines the concept of overlaping SAPs. This basically 231means, that an incoming SETUP could match more than one SAP (and more than 232one application) to receive the SETUP. For each SVE type there is a function 233that checks whether two SVEs overlap and there is a function that checks whether --- 11 unchanged lines hidden (view full) --- 245.Fn unisve_is_catchall 246returns 1 if the SAP is the catch-all SAP and 0 otherwise. 247.Pp 248Finally the function 249.Fn unisve_match 250is used to match a SAP against the information elements from a SETUP message. 251It returns 1 if they match and 0 otherwise. 252.Sh SEE ALSO | 226that evaluates to a comma separated list of strings that can be used 227to initializes an array of char pointers to map the error codes into 228human readable strings. 229.Pp 230The ATM Forum document defines the concept of overlaping SAPs. This basically 231means, that an incoming SETUP could match more than one SAP (and more than 232one application) to receive the SETUP. For each SVE type there is a function 233that checks whether two SVEs overlap and there is a function that checks whether --- 11 unchanged lines hidden (view full) --- 245.Fn unisve_is_catchall 246returns 1 if the SAP is the catch-all SAP and 0 otherwise. 247.Pp 248Finally the function 249.Fn unisve_match 250is used to match a SAP against the information elements from a SETUP message. 251It returns 1 if they match and 0 otherwise. 252.Sh SEE ALSO |
| 253.Xr libunimsg 3 , | 253.Xr libunimsg 3 |
| 254.Sh AUTHORS 255.An Hartmut Brandt Aq harti@freebsd.org | 254.Sh AUTHORS 255.An Hartmut Brandt Aq harti@freebsd.org |