------------------------------------------------------------------------ ATM UNI Signaling Support for IP over ATM Work By: Maryann Perez Dan Grossman Fong Liaw Allison Mankin Eric Hoffman Andy Malis ------------------------------------------------------------------------ Goals - Implementors guide on the use of UNI signaling to support Classical IP over ATM - Promote interoperability - Start with RFC 1577 (RFC 1483 LLC/SNAP) - also support RFC 1483 null encapsulation - Evolve... -1- ------------------------------------------------------------------------ Signaling Procedures - Host A sends "setup" via ATM switch to Host B. Host B "connects" to confirm connection Hosts can then later "release" the connection -2- ------------------------------------------------------------------------ Overview of Draft - Information Elements - Significance to ATM endpoints Encapsulation Protocol Layering - Significance to ATM network and endpoints - Protocol Procedures - VCs handling procedures (as per Andy Malis) - Call failure procedures -3- ------------------------------------------------------------------------ Information Elements - Mandatory - AAL Parameters - ATM Traffic Descriptor (ATM User Cell Rate) - Broadband Bearer Capability - Broadband Low Layer Information - QOS Parameters - Called Party Number - Calling Party Number - Optional - Transit Network Selection - Called Party Subaddress - Calling Party Subaddress -4- ------------------------------------------------------------------------ A Sample Setup +-----------------------------------------------------------------+ Information Elements/ Fields Value/(Meaning) -------------------- --------------- aal_params aal_type 5 (AAL 5) fwd_max_sdu_size_ident 140 fwd_max_sdu_size 9188 (default, send IP MTU value) bkw_max_sdu_size_ident 129 bkw_max_sdu_size 9188 (default, recv IP MTU value) mode identifier 131 * mode message * sscs_type identifier 132 sscs_type 0 (null SSCS) user_cell_rate fwd_peak_cell_rate_0_1_ident 132 fwd_peak_cell_rate_0_1 (link rate) bkw_peak_cell_rate_0_1_ident 133 bkw_peak_cell_rate_0_1 (link rate) best_effort_indication - bb_bearer_capab spare 0 bearer_class 16 (BCOC-X) spare 0 traffic_type 0 (no indication) susceptibility_to_clipping 0 (not_susceptible_to_clipping) timing_reqs 0 (no indication) bb_low_layer_info layer_2_id 2 user_information_layer 12 (lan_llc (ISO 8802/2) qos_params qos_class_fwd 0 (class_0) qos_class_bkw 0 (class_0) called_party_number type_of_number (international_number / unknown) addr_plan_ident (ISDN / ISO NSAPA) number (E.164 / OSI NSAPA) calling_party_number type_of_number (international_number / unknown) addr_plan_ident (ISDN / ISO NSAPA) presentation_indic (presentation_allowed) spare 0 screening_indic (user_provided_verified_and_passed) number (E.164 / OSI NSAPA) +--------------------------------------------------------------------+ Sample contents of SETUP message [* : optional, ignored if present] -5- ------------------------------------------------------------------------ VC management | | APPLICATION --> UUI | |-------- |TCP|UDP| --> B-HLI |---------------------- | IP + | ARP | --> B-LLI, ONLI |--------\------------------- | \ LLC + | --> B-LLI |----------\---------\--------------- | \ ATM \ | |------------\---------\------------- \ \ \ \ \ VC'' VC' + bind -6- ------------------------------------------------------------------------ What next? - Information RFC - Support only RFC 1577? Multiprotocol? - More difficult signaling issues ahead as ATM Forum's specification progresses -7- ------------------------------------------------------------------------