The following notes apply:
The ATM network address is expressed by either the t_atm_addr structure or the t_atm_sap structure, depending on the context. The t_atm_addr structure is used to query and negotiate options with the transport provider, whereas the t_atm_sap structure is used for any function that requires an ATM address as a parameter.
The
t_atm_addr
structure is defined in the options section. The
t_atm_sap
structure is defined in
-
-
struct t_atm_sap {
struct t_atm_sap_addr {
int8_t SVE_tag_addr;
int8_t SVE_tag_selector;
uint8_t address_format;
uint8_t address_length;
uint8_t address [20];
} t_atm_sap_addr;
struct t_atm_sap_layer2 {
int8_t SVE_tag;
uint8_t ID_type;
union {
uint8_t simple_ID;
uint8_t user_defined_ID;
} ID;
} t_atm_sap_layer2;
struct t_atm_sap_layer3 {
int8_t SVE_tag;
uint8_t ID_type;
union {
uint8_t simple_ID;
int32_t IPI_ID;
struct {
uint8_t OUI [3];
uint8_t PID [2];
} SNAP_ID;
uint8_t user_defined_ID;
} ID;
} t_atm_sap_layer3;
struct t_atm_sap_appl {
int8_t SVE_tag;
uint8_t ID_type;
union {
uint8_t T_ISO_ID [8];
struct {
uint8_t OUI [3];
uint8_t app_ID [4];
} vendor_ID;
uint8_t user_defined_ID[8];
} ID;
} t_atm_sap_appl;
}
Legal values for the field t_atm_sap_addr.SVE_tag_addr are T_ATM_PRESENT and T_ATM_ANY. The semantic meaning of this field is found in section 4.4 of referenced document ATMNAS.
Legal values for the field t_atm_sap_addr.SVE_tag_selector are T_ATM_PRESENT, T_ATM_ABSENT, and T_ATM_ANY. Note that T_ATM_PRESENT is valid only for ATM Endsystem addresses, and T_ATM_ABSENT is valid only for E.164 addresses. The semantic meaning of this field is found in section 4.4 of referenced document ATMNAS.
Legal values for the field t_atm_sap_addr.address_format are T_ATM_ENDSYS_ADDR and T_ATM_E164_ADDR. This field is mapped to octet 5 of the Q.2931 "Called Party Number" information element.
Legal values for the field t_atm_sap_addr.address_length are 0 thru 20. This field is not mapped to any octets of a Q.2931 information element. Instead, it specifies the valid number of array elements in field t_atm_sap_addr.address.
Legal values for the field t_atm_sap_addr.address can be found in section 5.1.3 of the referenced UNI specification (versions 3.0 and 3.1). This field is mapped to octets 6 and beyond of the Q.2931 "Called Party Number" information element.
Legal values for the field t_atm_sap_layer2.SVE_tag are T_ATM_PRESENT, T_ATM_ABSENT, and T_ATM_ANY. The semantic meaning of this field is found in section 4.4 of referenced document ATMNAS.
Legal values for the field t_atm_sap_layer2.ID_type are:
This field is not mapped to any octets of a Q.2931 information element. Instead, it specifies the proper union member in the t_atm_layer2 structure.
Legal values for the field t_atm_sap_layer2.ID.simple_ID are:
This field is mapped to octet 6 (bits 1 thru 5) of the Q.2931 BLLI ("Broadband Low Layer Information") information element.
Legal values for the field t_atm_sap_layer2.ID.user_defined_ID are 0 thru 127. This field is mapped to octet 6a (bits 1 thru 7) of the Q.2931 BLLI information element.
Legal values for the field t_atm_sap_layer3.SVE_tag are T_ATM_PRESENT, T_ATM_ABSENT, and T_ATM_ANY. The semantic meaning of this field is found in section 4.4 of referenced document ATMNAS.
Legal values for the field t_atm_sap_layer3.ID_type are:
This field is not mapped to any octets of a Q.2931 information element. Instead, it specifies the proper union member in the t_atm_layer3 structure.
Legal values for the field t_atm_sap_layer3.ID.simple_ID are:
Note that a value of T_ATM_BLLI3_I9577 in this field indicates that the identification of the layer 3 protocol is done in the user (data) plane, as specified in ISO/IEC TR 9577. This field is mapped to octet 7 (bits 1 thru 5) of the Q.2931 BLLI information element.
Legal values for the field t_atm_sap_layer3.ID.IPI_ID are those values defined by ISO/IEC TR 9577. This field is mapped to octet 7a (bits 1 thru 7) and octet 7b (bit 7) of the Q.2931 BLLI information element.
Legal values for the field t_atm_sap_layer3.ID.SNAP_ID.OUI are the 24-bit Organization Unique Identifiers assigned by the IEEE. This field is mapped to octets 8.1 thru 8.3 of the Q.2931 BLLI information element.
Legal values for the field t_atm_sap_layer3.ID.SNAP_ID.PID are defined by the organization identified in the preceding field. This field is mapped to octets 8.4 thru 8.5 of the Q.2931 BLLI information element.
Legal values for the field t_atm_sap_layer3.ID.user_defined_ID are 0 thru 127. This field is mapped to octet 7a (bits 1 thru 7) of the Q.2931 BLLI information element.
Legal values for the field t_atm_sap_appl.SVE_tag are T_ATM_PRESENT, T_ATM_ABSENT, and T_ATM_ANY. The semantic meaning of this field is found in section 4.4 of referenced document ATMNAS.
Legal values for the field t_atm_sap_appl.ID_type are:
This field is mapped to octet 5 (bits 1 thru 7) of the Q.2931 BHLI information element. It also specifies the proper union member in the t_atm_sap_appl structure.
Legal values for the field t_atm_sap_appl.ID.T_ISO_ID are reserved for specification by ISO. At the time of publication, this was an area of further study for ISO. This field is mapped to octets 6 thru 13 of the Q.2931 BHLI information element.
Legal values for the field t_atm_sap_appl.ID.vendor_ID.OUI are the 24-bit Organizationally Unique Identifiers assigned by the IEEE. This field is mapped to octets 6 thru 8 of the Q.2931 BHLI information element.
Legal values for the field t_atm_sap_appl.ID.vendor_ID.app_ID are specified by the vendor identified in the vendor_ID.OUI field. The vendor_ID.app_ID field is mapped to octets 9 thru 12 of the Q.2931 BHLI information element.
Legal values for the field t_atm_sap_appl.ID.user_defined_ID are 0 through 127. This field is mapped to octets 6 thru 13 of the Q.2931 BHLI information element.
| Option Name | Type of | Legal Option | Meaning |
|---|---|---|---|
| Option Value | Value | ||
| T_ATM_AAL5 | struct t_atm_aal5 | see text | ATM adaptation layer 5 |
| T_ATM_TRAFFIC | struct t_atm_traffic | see text | data traffic descriptor |
| T_ATM_BEARER_CAP | struct t_atm_bearer | see text | ATM service capabilities |
| T_ATM_BHLI | struct t_atm_bhli | see text | higher-layer protocol |
| T_ATM_BLLI | struct t_atm_blli | see text | lower-layer protocol (1st choice) |
| T_ATM_DEST_ADDR | struct t_atm_addr | see text | call responder’s network address |
| T_ATM_DEST_SUB | struct t_atm_addr | see text | call responder's subaddress |
| T_ATM_ORIG_ADDR | struct t_atm_addr | see text | call initiator’s network address |
| T_ATM_ORIG_SUB | struct t_atm_addr | see text | call initiator's subaddress |
| T_ATM_CALLER_ID | struct t_atm_caller_id | see text | caller's identification attributes |
| T_ATM_CAUSE | struct t_atm_cause | see text | cause of disconnection |
| T_ATM_QOS | struct t_atm_qos | see text | desired quality of service |
| T_ATM_TRANSIT | struct t_atm_transit | see text | public carrier transit network |
These options are all association-related.
See
With the exception of option T_ATM_CAUSE, each of these options may be negotiated for a connection initiated by the transport user. The results of any such negotiation are signalled to the remote device during connection establishment. The negotiation could be done in either of the following ways:
The first of the above two methods is recommended, since some of the option values can change during
connection establishment. Use of the first method returns the updated options to the transport user as
parameters of the
For the case of a transport user passively awaiting incoming calls, only the T_ATM_AAL5 and T_ATM_BLLI options may be negotiated. The results of any such negotiation are signalled to the remote device during connection establishment. The negotiation could be done in either of the following ways:
The first of the above two methods is recommended,
since the options proposed by the initiating party are
not associated with the responding transport endpoint prior to
The above listed options can be negotiated down by the ATM transport provider or peer endsystem if necessary and when appropriate.
When an incoming connection indication is present, the transport user optionally negotiates this option, which is signalled to the ATM device originating the ATM call. The specific fields within this option that may be modified by the transport user are forward_max_SDU_size and backward_max_SDU_size. The negotiation could be done in either of the following ways:
The option value consists of a structure t_atm_aal5 declared as:
-
-
struct t_atm_aal5 {
int32_t forward_max_SDU_size;
int32_t backward_max_SDU_size;
int32_t SSCS_type;
}
Legal values for the field forward_max_SDU_size are T_ATM_ABSENT, and 0 through (2**16 - 1). This field is mapped to octets 6.1 and 6.2 of the Q.2931 information element.
Legal values for the field backward_max_SDU_size are T_ATM_ABSENT, and 0 thru (2**16 - 1). This field is mapped to octets 7.1 and 7.2 of the Q.2931 information element.
Legal values for the field SSCS_type are:
This field is mapped to octet 8.1 of the Q.2931 information element. If, as a
default, the transport provider causes this Q.2931 information element field to be
present in the connection setup, then this field shall default to a value consistent
with the parameter
name
that was specified for
| t_open() name parameter | default SSCS_type |
|---|---|
| AAL5 | T_ATM_NULL |
| SSCOP/AAL5 | T_ATM_SSCS_SSCOP_REL |
Note that if all fields of the option have a value of T_ATM_ABSENT, then this denotes that the entire information element is not present in the Q.2931 network message.
The option value consists of a structure t_atm_traffic declared as:
-
-
struct t_atm_traffic_substruct {
int32_t PCR_high_priority;
int32_t PCR_all_traffic;
int32_t SCR_high_priority;
int32_t SCR_all_traffic;
int32_t MBS_high_priority;
int32_t MBS_all_traffic;
int32_t tagging;
}
struct t_atm_traffic {
struct t_atm_traffic_substruct forward;
struct t_atm_traffic_substruct backward;
uint8_t best_effort;
}
Legal values for the field forward.PCR_high_priority are T_ATM_ABSENT, and 0 thru (2**24 - 1). This field is mapped to octets 5.1 thru 5.3 of the Q.2931 information element.
Legal values for the field forward.PCR_all_traffic are 0 thru (2**24 - 1). This field is mapped to octets 7.1 thru 7.3 of the Q.2931 information element.
Legal values for the field forward.SCR_high_priority are T_ATM_ABSENT, and 0 thru (2**24 - 1). This field is mapped to octets 9.1 thru 9.3 of the Q.2931 information element.
Legal values for the field forward.SCR_all_traffic are T_ATM_ABSENT, and 0 thru (2**24 - 1). This field is mapped to octets 11.1 thru 11.3 of the Q.2931 information element.
Legal values for the field forward.MBS_high_priority are T_ATM_ABSENT, and 0 thru (2**24 - 1). This field is mapped to octets 13.1 thru 13.3 of the Q.2931 information element.
Legal values for the field forward.MBS_all_traffic are T_ATM_ABSENT, and 0 thru (2**24 - 1). This field is mapped to octets 15.1 thru 15.3 of the Q.2931 information element.
Legal values for the field forward.tagging are T_YES and T_NO. This field is mapped to octet 18.1 (bit 1) of the Q.2931 information element.
Legal values for the field backward.PCR_high_priority are T_ATM_ABSENT, and 0 thru (2**24 - 1). This field is mapped to octets 6.1 thru 6.3 of the Q.2931 information element.
Legal values for the field backward.PCR_all_traffic are 0 thru (2**24 - 1). This field is mapped to octets 8.1 thru 8.3 of the Q.2931 information element.
Legal values for the field backward.SCR_high_priority are T_ATM_ABSENT, and 0 thru (2**24 - 1). This field is mapped to octets 10.1 thru 10.3 of the Q.2931 information element.
Legal values for the field backward.SCR_all_traffic are T_ATM_ABSENT, and 0 thru (2**24 - 1). This field is mapped to octets 12.1 thru 12.3 of the Q.2931 information element.
Legal values for the field backward.MBS_high_priority are T_ATM_ABSENT, and 0 thru (2**24 - 1). This field is mapped to octets 14.1 thru 14.3 of the Q.2931 information element.
Legal values for the field backward.MBS_all_traffic are T_ATM_ABSENT, and 0 thru (2**24 - 1). This field is mapped to octets 16.1 thru 16.3 of the Q.2931 information element.
Legal values for the field backward.tagging are T_YES and T_NO. This field is mapped to octet 18.1 (bit 2) of the Q.2931 information element.
Legal values for the field best_effort are T_YES and T_NO. This field is mapped to octet 17 of the Q.2931 information element.
The option value consists of a structure t_atm_bearer declared as:
-
-
struct t_atm_bearer {
uint8_t bearer_class;
uint8_t traffic_type;
uint8_t timing_requirements;
uint8_t clipping_susceptibility;
uint8_t connection_configuration;
}
Legal values for the field bearer_class (see ITU Recommendation F.811) are:
This field is mapped to octet 5 (bits 1 thru 5) of the Q.2931 information element.
Legal values for the field traffic_type are:
This field is mapped to octet 5a (bits 3 thru 5) of the Q.2931 information element.
Legal values for the field timing_requirements are:
This field is mapped to octet 5a (bits 1 and 2) of the Q.2931 information element.
Legal values for the field clipping_susceptibility are:
This field is mapped to octet 6 (bits 6 and 7) of the Q.2931 information element.
Legal values for the field connection_configuration are:
This field is mapped to octet 6 (bits 1 and 2) of the Q.2931 information element.
For the transport user initiating the connection, the option values pertaining to
the specification of the remote ATM protocol address are overwritten with the
corresponding parameters of the
The option value consists of a structure t_atm_bhli declared as:
-
-
struct t_atm_bhli {
int32_t ID_type;
union {
uint8_t T_ISO_ID [8];
struct {
uint8_t OUI [3];
uint8_t app_ID [4];
} vendor_ID;
uint8_t user_defined_ID[8];
} ID;
}
Legal values for the field ID_type are:
This field is mapped to octet 5 (bits 1 thru 7) of the Q.2931 information element. The value T_ATM_ABSENT denotes that the entire information element is not present in the Q.2931 network message.
Legal values for the field ID.T_ISO_ID are reserved for specification by ISO. At the time of publication, this was an area of further study for ISO. This field is mapped to octets 6 thru 13 of the Q.2931 information element.
Legal values for the field ID.vendor_ID.OUI are the 24-bit Organization Unique Identifiers assigned by the IEEE. This field is mapped to octets 6 thru 8 of the Q.2931 information element.
Legal values for the field ID.vendor_ID.app_ID are specified by the vendor identified in the ID.vendor_ID.OUI field. The ID.vendor_ID.app_ID field is mapped to octets 9 thru 12 of the Q.2931 information element.
Legal values for the field ID.user_defined_ID are 0 through 127. This field is mapped to octets 6 thru 13 of the Q.2931 BHLI information element.
For the transport user initiating the connection, the option values pertaining to
the specification of the remote ATM protocol address are overwritten with the
corresponding parameters of the
When an incoming connection indication is present, the transport user optionally negotiates this option, which is signalled to the ATM device originating the ATM call. The specific fields within this option that may be modified by the transport user are:
The option negotiation could be done in either of the following ways:
The transport user accepting the incoming connection indication must perform any negotiation according to the guidelines described in section C.3, Annex C of the referenced UNI specification, versions 3.0 and 3.1. Support of negotiation described in section C.4 of Annex C is for further study.
The option value consists of a structure t_atm_blli declared as:
-
-
struct t_atm_blli {
struct {
int8_t ID_type;
union {
uint8_t simple_ID;
uint8_t user_defined_ID;
} ID;
int8_t mode;
int8_t window_size;
} layer_2_protocol;
struct {
int8_t ID_type;
union {
uint8_t simple_ID;
int32_t IPI_ID;
struct {
uint8_t OUI [3];
uint8_t PID [2];
} SNAP_ID;
uint8_t user_defined_ID;
} ID;
int8_t mode;
int8_t packet_size;
int8_t window_size;
} layer_3_protocol;
}
Legal values for the field layer_2_protocol.ID_type are:
This field is not mapped to any octets of a Q.2931 information element. Instead, it specifies the proper union member in the t_atm_layer2 structure.
Legal values for the field layer_2_protocol.ID.simple_ID are:
This field is mapped to octet 6 (bits 1 thru 5) of the Q.2931 information element.
Legal values for the field layer_2_protocol.ID.user_defined_ID are 0 thru 127. This field is mapped to octet 6a (bits 1 thru 7) of the Q.2931 BLLI information element.
Legal values for the field layer_2_protocol.mode are T_ATM_ABSENT, T_ATM_BLLI_NORMAL_MODE, and T_ATM_BLLI_EXTENDED_MODE. This field is mapped to octet 6a (bits 6 and 7) of the Q.2931 information element.
Legal values for the field layer_2_protocol.window_size are T_ATM_ABSENT, and 1 thru 127. This field is mapped to octet 6b (bits 1 thru 7) of the Q.2931 information element.
Legal values for the field layer_3_protocol.ID_type are:
This field is not mapped to any octets of the Q.2931 information element. Instead, it specifies the proper union member in structure t_atm_blli.
Legal values for the field layer_3_protocol.ID.simple_ID are:
Note that a value of T_ATM_BLLI3_I9577 in this field indicates that the identification of the layer 3 protocol is done in the user (data) plane, as specified in ISO/IEC TR 9577. This field is mapped to octet 7 (bits 1 thru 5) of the Q.2931 information element.
Legal values for the field layer_3_protocol.ID.IPI_ID are T_ATM_ABSENT, and those values defined by ISO/IEC TR 9577. This field is mapped to octet 7a (bits 1 thru 7) and octet 7b (bit 7) of the Q.2931 information element. Note that the value T_ATM_ABSENT is used to signal that the identification of the network-layer protocol is carried with each TSDU in the data plane, according to codepoints defined by ISO/IEC TR 9577.
Legal values for the field layer_3_protocol.ID.SNAP_ID.OUI are the 24-bit Organization Unique Identifiers assigned by IEEE. This field is mapped to octets 8.1 thru 8.3 of the Q.2931 information element.
Legal values for the field layer_3_protocol.ID.SNAP_ID.PID are defined by the organization identified in the preceding field. This field is mapped to octets 8.4 thru 8.5 of the Q.2931 information element.
Legal values for the field layer_3_protocol.ID.user_defined_ID are 0 thru 127. This field is mapped to octet 7a (bits 1 thru 7) of the Q.2931 BLLI information element.
Legal values for the field layer_3_protocol.mode are T_ATM_ABSENT, T_ATM_BLLI_NORMAL_MODE, and T_ATM_BLLI_EXTENDED_MODE. This field is mapped to octet 7a (bits 6 and 7) of the Q.2931 information element.
Legal values for the field layer_3_protocol.packet_size are:
This field is mapped to octet 7b (bits 1 thru 4) of the Q.2931 information element.
Legal values for the field layer_3_protocol.window_size are T_ATM_ABSENT, and 1 thru 127. This field is mapped to octet 7c (bits 1 thru 7) of the Q.2931 information element.
For the transport user initiating the connection, the option values pertaining to
the specification of the remote ATM protocol address are overwritten with the
corresponding parameters of the
The option value consists of a structure t_atm_addr declared as:
-
-
struct t_atm_addr {
int8_t address_format;
uint8_t address_length;
uint8_t address [20];
}
Legal values for the field address_format are T_ATM_ENDSYS_ADDR and T_ATM_E164_ADDR. This field is mapped to octet 5 of the Q.2931 information element.
Legal values for the field address_length are 0 thru 20. This field is not mapped to any octets of a Q.2931 information element. Instead, it specifies the valid number of array elements in field address.
Legal values for the field address can be found in section 5.1.3 of the referenced UNI specification (versions 3.0 and 3.1). This field is mapped to octets 6 and beyond of the Q.2931 information element.
The option value consists of a structure t_atm_addr (see option T_ATM_DEST_ADDR for the structure's declaration). Note that for this option, field address_format must have a value of either T_ATM_NSAP_ADDR or T_ATM_ABSENT.
A value of T_ATM_ABSENT in field address_format of structure t_atm_addr indicates that the information element is not present in the Q.2931 signalling message.
The option value consists of a structure t_atm_addr (see option T_ATM_DEST_ADDR for the structure's declaration).
A value of T_ATM_ABSENT in field address_format of structure t_atm_addr indicates that the information element is not present in the Q.2931 signalling message.
The option value consists of a structure t_atm_addr (see option T_ATM_DEST_ADDR for the structure's declaration). Note that for this option, field address_format must have a value of either T_ATM_NSAP_ADDR or T_ATM_ABSENT.
A value of T_ATM_ABSENT in field address_format of structure t_atm_addr indicates that the information element is not present in the Q.2931 signalling message.
The option value consists of a structure t_atm_caller_id declared as:
-
-
struct t_atm_caller_id {
int8_t presentation;
uint8_t screening;
}
Legal values for the field presentation are:
This field is mapped to octet 5a (bits 6 and 7) of the Q.2931 information element.
Legal values for the field screening are:
This field is mapped to octet 5a (bits 1 and 2) of the Q.2931 information element.
Upon disconnection, the transport user optionally negotiates this option, the
results of which are signalled to the remote ATM device. Any such negotiation
must be performed via the
The option value consists of a structure t_atm_cause declared as:
-
-
struct t_atm_cause {
int8_t coding_standard;
uint8_r location;
uint8_r cause_value;
uint8_r diagnostics [4];
}
Legal values for the field coding_standard are T_ATM_ABSENT, T_ATM_ITU_CODING, and T_ATM_NETWORK_CODING. This field is mapped to octet 2 (bits 6 and 7) of the Q.2931 information element. The value of T_ATM_ABSENT denotes that the entire information element is not present in the Q.2931 network message.
Legal values for the field location are:
This field is mapped to octet 5 (bits 1 thru 4) of the Q.2931 information element.
Legal values for the field cause_value are listed in a full-page table in the referenced UNI specification. This field is mapped to octet 6 (bits 1 thru 7) of the Q.2931 information element.
Legal values for the field diagnostics are beyond the scope of this specification. This field is mapped to octets 7 and beyond of the Q.2931 information element.
The option value consists of a structure t_atm_qos declared as:
-
-
struct t_atm_qos_substruct {
int32_t coding_standard;
}
struct t_atm_qos {
int8_t coding_standard;
struct t_atm_qos_substruct forward;
struct t_atm_qos_substruct backward;
}
Legal values for the field coding_standard are T_ATM_ABSENT, T_ATM_ITU_CODING, and T_ATM_NETWORK_CODING. This field is mapped to octet 2 (bits 6 and 7) of the Q.2931 information element. The value of T_ATM_ABSENT denotes that the entire information element is not present in the Q.2931 network message.
Legal values for the field forward.qos_class are:
This field is mapped to octet 5 of the Q.2931 information element.
Legal values for the field backward.qos_class are the same as those specified for field forward.qos_class above. This field ( backward.qos_class) is mapped to octet 6 of the Q.2931 information element.
The option value consists of a structure t_atm_transit declared as:
-
-
struct t_atm_transit {
uint8_t length;
uint8_t network_id[];
}
The field
length
specifies how many characters in array
network_id
are valid.
Legal values for the field length are 0 thru 255. The value of 0 denotes that the entire information element is not present in the Q.2931 network message.
Legal values for the field network_id are beyond the scope of this document. This field is mapped to octets 6 and beyond of the Q.2931 information element.
The parameter call->opt is used only to set negotiable ATM connection attributes. These attributes (and XTI options) are T_ATM_AAL5 and T_ATM_BLLI.
Note that the transport provider must queue data sent via
An implementation may optionally allow at most one application to bind to the "wildcard catch-all" SAP of (T_ATM_ANY, T_ATM_ANY, T_ATM_ANY, T_ATM_ANY, T_ATM_ANY) for the 5 SAP vector elements.
When a transport user wishes to initiate outgoing connect requests through a transport
endpoint, it is recommended that
If
| After Call | |||
|---|---|---|---|
| Parameters | Before | _ | |
| Call | AAL-5 | SSCOP / AAL-5 | |
| fd | x | / | / |
| info->addr | / | x | x |
| info->options | / | x | x |
| info->tsdu | / | 1 & | 60;= x & |
| info->etsdu | / | -2 | -2 |
| info->connect | / | -2 | -2 |
| info->discon | / | -2 | -2 |
| info->servtype | / | T_COTS | T_COTS |
| info->flags | / | 0 | 0 |
Upon successful return of
ATM does not support a zero-length TSDU. If parameter nbytes is zero, then [TBADDATA] is returned if either:
When the connection present at the transport endpoint is a leaf on a point-to-multipoint
connection, the transport provider returns [TNOTSUPPORT] for
The return of this function can be mapped to the following ATM Forum primitives:
Note that parameter
queue_size
of the ATM Forum's
ATM_prepare_incoming_call
primitive is different to XTI's
qlen:
The parameter
queue_size
is the maximum number
of incoming calls that have arrived but have not yet been presented to the transport user,
while the parameter
qlen
is the maximum number of incoming calls that have been presented to
the transport user but not yet accepted. Therefore,
queue_size
cannot be set via the
Additionally, when the transport endpoint is in synchronous mode, the return of this function can be mapped to the following ATM Forum primitives:
The ATM network address (of the calling user) returned in parameter call->addr is an implementation of the ATM Forum's ATM_query_connection_attributes primitive, where the connection attribute (and XTI option) being queried is T_ATM_ORIG_ADDR. If any options are present in parameter call->opt, then each of these options is an implementation of the ATM Forum's ATM_query_connection_attributes primitive.
If any options are present in parameter call->opt, then each of these options is an implementation of the ATM Forum's ATM_query_connection_attributes primitive.
| Contents | Next section | Index |