17th meeting of Carriers Working Group

17th Carrier Working Group 23 November 2022 Handling instructions for SENSITIVE information are given at https://europa.eu/!qG39Vd Carrier meetings - Calendar 2 Carrier meetings – calendar 1/2 May 2022 • 4th of May: Carrier Awareness session • 2nd of May: Technical Connectivity Session March 2022 with Carriers • 2nd of March: Carrier • 11th of May: Ad-hoc Awareness session meeting with Ryanair • 3rd of March: Adhoc and Navitaire meeting with Amadeus • 13th of May: Ad-hoc • 10th of March: Adhoc meeting with MSC July 2022 meeting with Res2 cruises • 6th of July: Carrier • 16th of March: Carrier • 18th of May: Carrier Awareness session Awareness session Awareness session • 14th of July : High level • 24th of March: Adhoc • 24th of May: EBAA meeting with Air Industry meeting with Sabre meeting - EBACE • 26th of July: Carrier Working • 30th of March: Carrier • 25th of May: Carrier Group Day Working Group Day Working Group Day February 2022 April 2022 June 2022 • 6th of April: Carrier • 1st of June: Carrier • 16th of Feb: Carrier Awareness session Awareness session Awareness session • 12th of April: Ad-hoc • 10th of June: UK • 23rd of Feb: Adhoc meeting on NIKO DCS Chamber of Shipping meeting with CLIA • 20th of April: Carrier meeting • 28th of Feb: Carrier Awareness session • 15th of June: Carrier Working Group Day • 21st of April: Ad-hoc Awareness session meeting with United • 27th of June: Carrier • 27th of April: Carrier identification - Working Group Day Business aviation operators • 29th of June: Carrier Working Group Day • 29th of June: Meeting with Airlines for America (A4A) 3 Carrier meetings – calendar 2/2 October 2022 December 2022 • 11-12 October Industry • 14th of December: Round Table Carrier Working Group Day • 27th of October: Carrier Working Group Day November August-September 2022 2022 • 23rd of November :Carrier Working Group Day • 29th of August: Ad-hoc Technical meeting on connectivity and testing • 7th of September: Awareness Session • 30th of September: Carrier Working Group Day 4  eu-LISA Carrier Meetings • Dates are finalized through December 2022: ✓ The Carrier Working Group (once per month) • In addition, ad-hoc meetings could be organized upon request after submission of an agenda to eu-LISA, for evaluation 5  Crew exceptions Carriers Working Group 23 November 2022 1  Exemptions for crew • Article 2(2)(i) of the ETIAS Regulation excepts from its application persons referred to in Article 4(1) of Regulation 539/2001: “persons or categories of persons referred to in points (a) to (f) of Article 4(1) of Regulation (EC) No 539/2001;” 2  Exemptions for crew • Article 4(1) of Regulation 539/2001 was repealed and replaced by Article 6(1) of Regulation (EU) 2018/1806: (b) civilian air and sea crew members in the performance of their duties; (c) civilian sea crew members, when they go ashore, who hold a seafarer's identity document issued in accordance with the International Labour Organisation Conventions No 108 of 13 May 1958 or No 185 of 19 June 2003 or the International Maritime Organization Convention on Facilitation of International Maritime Traffic of 9 April 1965; (d) crew and members of emergency or rescue missions in the event of a disaster or an accident; (e) civilian crew of ships navigating in international inland waters; 3  Exemptions for crew • The exact scope of the exceptions under this provision is determined by Member States: “A Member State may provide for exceptions from the visa requirement” • Member States have communicated the measures they have taken pursuant to Article 6, to the Commission and these were published at https://ec.europa.eu/home-affairs/pages/document/information-national- derogations-visa-requirement_en • The exact scope of 2(2)(i) of the ETIAS Regulation is therefore determined by the content of the notified MS measures referred to above. • Thus, the same exemptions applied now for visas (for VR countries) are to be applied in future for ETIAS (for VE countries) 4  Web site with measures communicated • https://ec.europa.eu/home-affairs/pages/document/information-national- derogations-visa-requirement_en includes an Excel file • Excel file contains a sheet Exemptions Article 6(1) • As from row 348, 1.2. Visa exemptions for other categories mentioned in Article 6(1) can be found, indicating the way each MS allows the exemptions 5  Performance of their duties • In COM view, shared by the MS, sea crew members are never in the performance of their duties when leaving a ship to transit home, or when arriving at an airport to transit to a ship. The duty only starts when a crew member signs on at the ship, and ends when the crew members signs off and leaves the ship. The transit is not part of the duty (which is a significant difference compared to air crew). Sea crew members are only “in the performance of their duties” while on board a ship, and possibly (although MS interpretations vary) during short periods of shore leave in the area of the port and the immediately surrounding area. 6  Going ashore (1 of 2) • Many, but not all MS interpret that the exception of “going ashore” provides a legal basis for waiving the visa requirement for qualifying seafarers in transit to/from a ship. Several MS provide such visa waivers but attach strict conditions: usually the visa-free transit between ship and airport (or vice versa) is restricted in time (e.g., 5 days max), and often, only selected nationalities qualify for the visa-free transit for seafarers. Other MS consider that there is no legal basis for waiving the visa requirement for seafarers in transit. • In all cases sea crew members must hold the necessary ILO documents and documentation proving that they are in transit to take up duty. Often, the shipping company or crewing agency needs to provide name lists 24 hours or more in advance to the border guards (at the airport or port) as a condition for the visa waiver. All this is regulated in national law.  Going ashore (2 of 2) • There is no legal basis, neither in b) or c), for any sort of visa waiver if the sea crew member stays in the EU for purposes not related to seafaring (e.g., holidays).  Who is crew • In the PHB, “Crew members include all persons actually employed for duties on board during a voyage in the working or service of a ship and included in the crew list” (point 1.3). For example, an engineer positioning to an EU state to repair an aircraft and return to the UK exempt? → Such an engineer is NOT crew, for above reasons. Could we have some more detail about the requirements regarding Crew, and also confirmation whether the carrier is responsible for checking against the CI for crew on chartered vessels (i.e. not employed by the carrier) → Either carrier or chartered vessels must check the carrier interface for passengers holding a single/double entry visa or ETIAS. In principle, it is the carrier responsible for the transport of the passengers.  Conclusion • Do they need an ETIAS? • A person falling within the scope of Article 2(2)(i) ETIAS Reg does not need an ETIAS.  Thank you © European Union 2020 Unless otherwise noted the reuse of this presentation is authorised under the CC BY 4.0 license. For any use or reproduction of elements that are not owned by the EU, permission may need to be sought directly from the respective right holders. 11 xx: element concerned, source: e.g. Fotolia.com; Slide xx: element concerned, source: e.g. iStock.com Slide  Sea routes scenarios 23 November 2022 1  Svalbard Status • Svalbard is under Norwegian sovereignty, but with limitations as defined by the Spitsbergen Treaty of 1920. (Russian/Norwegian condominium) • Due to the treaty regulations, Svalbard is not treated as part of Norway by customs. • Flights from Oslo to Longyearbyen start at the international part of the airport Oslo Gardermoen. • Norway is part of the Schengen treaty area, Svalbard is not, and this means that you are crossing a Schengen boundary when traveling to or from Svalbard. 2  Greenland Status Legal base: Memorandum from the implementation in Greenland of Article 5(2) of the Agreement on the Accession of the Kingdom of Denmark to the CISA 11488/99 Brussels, 30 September 1999 We can consider Greenland de facto as within the area without internal border controls (DK border guards carry out Schengen border controls at Greenland airports and ports for flights/ships coming from third countries and there are no border checks for flights/ships arriving from Schengen). Caveat: Security checks based on an analysis of risks to internal security or illegal immigration may be conducted (as mentioned in Annex VI) 3  FAQ (1 of 2) • IE is EU, so no ETIAS nor visa needed. • EES is only for short stays, not long stays • Citizens from MS do not require EES and ETIAS and this includes from territories for these MS (eg: Faore Islands, DK; Aruba, NL; etc) • → IE citizen travels without ETIAS to any MS or Schengen Associated Country: • Even if IE is out of scope of both EES and ETIAS, meaning that • IE does not register entry or exits of TCNs entering or leaving IE • IE does not require ETIAS to enter IE IE citizens, as EU citizens are not registered and do not need an ETIAS 4  FAQ (2 of 2) • → VE citizen (eg: UK) needs an ETIAS to enter the ETIAS area (all MS except IE plus Schengen Associated Countries) • UK citizens require ETIAS to MS (except IE) or Schengen Associated Country • UK citizens are registered when entering/leaving MS in scope of EES • Citizens with USA or UK (Isle of Man, Jersey, etc) passports require and ETIAS • Sudan, Sri Lanka appear in Annex I 5  Scenario 0 • If a ship sails from Rome to Dubrovnik and then to Turkey and to Malta, passengers with a multiple entry Schengen visa can do excursions freely, although Croatia or Turkey are not part of Schengen. However, what happens if a passenger boards the ship in Dubrovnik or Izmir? Surely, Croatia or Turkey will have checked their Schengen visas – but they will not have used the EES system. Therefore, will the carriers have to check the website 48 hours before embarkation, although the passengers have spent time in a country that accepts Schengen visa? • VR TCNs with a multiple entry Schengen visa can indeed do daily excursions in UE. We cannot answer about Turkey • As for a trip from HR to Izmir, this is outside the Schengen area, carriers need not perform any check. Checks are to be done when entering the Schengen area 6  Scenario 1 • If a USA guest for example arrives with a flight in Barcelona, gets checked by the Airline and receives an “ok ETIAS” from the Airline, sleeps 1 night in Hotel in Barcelona and then embarks onboard of an MSC Cruise ship from Barcelona with below itinerary calling only “Schengen Ports”, will MSC have to send again the ETIAS query though the related portal in order to check again if ok ETIAS or not? Itinerary: Barcelona – Marseille – Genoa – Naples – Messina – Valletta - Barcelona • Reply: NO 7  Scenario 2 • Chinese guest arrives in Barcelona with multiple schengen VISA with a flight, receives “ok EES” after check done by the Airline, also in this case sleeps in Hotel in Barcelona for 1 night and then embarks onboard of an MSC Cruise ship from Barcelona with below itinerary, will MSC have to send again the EES query though the related portal in order to check again if ok EES or not? Itinerary: Barcelona – Marseille – Genoa – Naples – Messina – Valletta - Barcelona • Reply: NO • 8  Scenario 3 • A USA guest for example arrives with a flight in Piraeus, gets checked by the Airline and receives an “ok ETIAS” from the Airline, sleeps 1 night in Hotel in Piraeus and then embarks onboard of an MSC Cruise ship from Piraeus with below itinerary calling also “Extra Schengen Ports”. MSC will have to send again the ETIAS query though the related portal in order to check again if ok ETIAS ? Itinerary: Piraeus – Santorini – Kusadasi – Haifa – Limassol – Mykonos - Piraeus • Reply: As the boat will leave the Schengen area and enter Cyprus, this American citizen needs to have an ETIAS to enter Cyprus. The ETIAS must be valid for the whole duration of the cruise, so the ETIAS must be valid for the last port in EU, ie, Pireus. The ETIAS must be checked for Limassol (as ETIAS is also required in CY) and for Mykonos (entering the ETIAS area). • 9  Scenario 4 • Chinese guest arrives in Piraeus with multiple Schengen VISA with a flight, receives “ok EES” after check done by the Airline, also in this case sleeps in Hotel in Piraeus for 1 night and then embarks onboard of an MSC Cruise ship from Piraeus with below itinerary calling “Extra Schengen Ports” MSC will have to send again the EES query though the related portal in order to check again if ok EES or not? Itinerary: Piraeus – Santorini – Kusadasi – Haifa – Limassol – Mykonos - Piraeus • Reply: Multiple entry visas are not yet in the scope of EES, so far therefore they should only be checked manually (visually) to ensure they are valid for the dates of entry in the EU ports (including Limassol). • 10  Scenario 5 Joe is a UK citizen. He flies from London Gatwick to Croatia. Upon arrival in Croatia, he goes straight to the cruise terminal and boards our ship. He then makes day visits to ports in and out of the Schengen area, for instance, in Portugal, Spain and Turkey, but does not permanently leave the vessel. He then disembarks permanently in Italy, whereupon he takes a flight back to the UK. • Please can you clarify, in no uncertain terms, if we (the ship carrier) need to check EES / ETIAS in this situation, and at what stages? • For the itinerary between UK and Croatia, the verification of the ETIAS status is indeed under the responsibility of the air carrier. • This being said, the cruise needs to checks the ETIAS for the visits/permanent entry in Schengen area at the end of the passenger’s itinerary. It must be checked from Croatia to Portugal (entering the Schengen area) and from Turkey to 11 Italy (re-entering the Schengen area).  UK nationals • “Does a UK national, who embarks on a vessel in the UK, sails to Barcelona, enjoys a day trip in Barcelona, and returns to UK on the ship: would they need an ETIAS?” • “An ETIAS is required of UK nationals, with the exception of those who are beneficiaries of the Withdrawal Agreement”. 12  Carrier Interface vs EES Checks Carrier Interface is to be queried only when arriving: For single/double entry visas from outside Schengen area in the Schengen area For ETIAS from outside ETIAS area into the ETIAS area But Entry Exit Checks (as the name indicates) take place both at Entry and at Exit - Recommendation to MS on cruise ships harmonises the EES checks but Obligations 13 on TCN to have their visa or ETIAS remain irrespective of the reduced EES checks  Scenarios / Checks Itinerary 1: Southampton, Hamburg, Southampton. No Way port leavers or joiners For guest who require a Visa and hold a single or double one: Check EES Carrier Interface (prior to first boarding at Southampton) For guest who require an ETIAS Check ETIAS Carrier Interface (prior to first boarding at Southampton) 14  Scenarios / Checks Itinerary 2: Southampton, La Coruna, Barcelona. Joiners only in Southampton, leavers only in Barcelona For guest who require a Visa and hold a single or double one: Check EES Carrier Interface (prior to first boarding at Southampton) For guest who require an ETIAS Check ETIAS Carrier Interface (prior to first boarding at Southampton) 15  Scenarios / Checks Itinerary 3: Southampton, Hamburg, Southampton. But we have leavers and joiners in Hamburg For guest who require a Visa and hold a single or double one: Check EES Carrier Interface (prior to first boarding at Southampton) For guest who require an ETIAS Check ETIAS Carrier Interface (prior to first boarding at Southampton) 16  Scenarios / Checks Itinerary 4: Suez, Barcelona, La Coruna, Southampton. Only leavers in Southampton For guest who require a Visa and hold a single or double one: Check EES Carrier Interface (prior to first boarding at Suez) For guest who require an ETIAS Check ETIAS Carrier Interface (prior to first boarding at Suez) 17  Scenarios / Checks Itinerary 5: Barcelona, La Coruna, Southampton. Joiners only in Barcelona, leavers only in Southampton For guest who require a Visa and hold a single or double one: For guest who require an ETIAS No interface check, as trip not from outside the Schengen area to a Schengen destination 18  Scenarios / Checks Itinerary 6: Barcelona, Naples, Barcelona For guest who require a Visa and hold a single or double one: For guest who require an ETIAS No interface check, as trip not from outside the Schengen area to a Schengen destination 19  Thank you © European Union 2020 Unless otherwise noted the reuse of this presentation is authorised under the CC BY 4.0 license. For any use or reproduction of elements that are not owned by the EU, permission may need to be sought directly from the respective right holders. 20 xx: element concerned, source: e.g. Fotolia.com; Slide xx: element concerned, source: e.g. iStock.com Slide  Carrier Working Group Technical updates November 2022 Handling instructions for SENSITIVE information are given at https://europa.eu/!qG39Vd An overview of the forms and details of the REST Option  1. Introduction - Connection Options : S2S / Web Portal / Mobile App 08/12/2022 3  2. Review of the Forms to be completed by carriers choosing S2S option 1. Registration Form for Carrier and eventually the Service Provider Contacts (F03) • Can be found in the Welcome Pack, which carrier will receive after the carrier SPOC has signed the NDA 2. Form for Details of System to Be Connected to eu-LISA’s Carrier Interface (F04) • Can be found in the Welcome Pack, which carrier will receive after the carrier SPOC has signed the NDA 3. Forms for the Interface Technical Information (F04a and F04b for xSIM) • Summarizes all the technical details required for configuration of the system to be interfaced • eu-LISA and Carrier’s interfaces parameters are organized in two distinct files: 1. MQ (UN / EDIFACT) over IPsec VPN option (F04a) 2. API REST/JSON or /XML over mTLS option (F04b)  presentation focus • Technical Information Form to be completed (with the help of the Service Provider depending IF any was declared in F03) • Returned to the Carrier in a final communication to the SPOC with ALL the info required to implement the S2S connection (this will be the entry criteria for the start of the next phases i.e. Pre-CT / Certification Testing) 08/12/2022 4  3. Forms exchange for REST details - Communication flow 2. REST Form 4b to be filled (includes Public Carrier with 1. Completed Form 3 and Form 4 Carrier with Certificate) S2S option REST selected Interface Eu-LISA 4. Completed REST Form Onboarding (incl. additional information) Team 3a. Filled REST Form 4b (Yellow cells) Eu-LISA Technical Team 3b. Filled REST Form 4b (Yellow cells) 5. REST connection ready communication 08/12/2022 5 4. Security - REST API (JSON or XML) over mTLS – Pre-CT and CT eu-LISA xSIM Public Carrier1 certificate Public certificate nnnnn.travel-europe.europa.eu API Gateway Internet API Gateway Firewall Carrier2 Public certificate API Gateway eu-LISA PGD Private Private Carrier1 certificate nnnnn.travel-europe.europa.eu certificate API Gateway Internet API Gateway Firewall Carrier2 Private certificate API Gateway The API gateway is a generic term for the API Gateway Carrier endpoint for REST connectivity 5. Security - REST API (JSON or XML) over mTLS – Production eu-LISA PRD main site Carrier1 Private certificate API Gateway API Gateway Firewall Carrier2 Private certificate API Gateway nnnn.travel-europe.europa.eu Internet Private certificate eu-LISA PRD backup site API Gateway Firewall The API gateway is a generic term for the API Gateway Carrier endpoint for REST connectivity 6. Connectivity - REST Channel  7. Carrier registration form API Form structure • API connection details Object Description Value Please be aware that the yellow fields are mandatory Carrier or Service Provider connection Carrier or Service Provider details Nr. Name IP Address Hostname (FQDN) Details Name, IPv4/IPv6 address, Hostname 1 myname 1.2.3.4 test.mycompany.com 2 <to be filled-in by the carrier/service provider> <to be filled-in by the carrier/service provider><to be filled-in by the carrier/service provider> 3 <to be filled-in by the carrier/service provider> <to be filled-in by the carrier/service provider><to be filled-in by the carrier/service provider> 4 <to be filled-in by the carrier/service provider> <to be filled-in by the carrier/service provider><to be filled-in by the carrier/service provider> Certificate authority name - The certificates are obtained Public certificate issuer name from a third-party certificate authority (CA) containing <to be filled-in by the carrier/service provider> verified public keys. - used for mTLS authentification Public certificate common name CN of the client <to be filled-in by the carrier/service provider> Public certificate validity Expiration date <to be filled-in by the carrier/service provider> Estimated number of request Estimation of how many requests per day (if possible) <to be filled-in by the carrier/service provider> Endpoint Endpoint for XML and JSON requestes https://name.travel-europe.europa.eu/eulisa/example/example-verification <----- not the real one Public certificate of the endpoint Certificate will be attached with the form CN - SIMAPI.travel-europe.europa.eu ; Issuer - BE, GlobalSign nv-sa Public certificate validity Expiration date 07/02/1980 06:23 Key name to be added into the header Client ID Key X-ABC-Client-ID *ID value will be sent after onboarding* Please note all carrier mandatory fields are marked with yellow background. 9  8. What form for which connection Carrier Interface Option F01 F02 F03 F04 F04a F04b F05 F06 MQ Client – Server Carrier Choice for Data Type of Exchange Channels = connection = System-to-System MQ/EDIFACT MQ Server – Server Carrier Choice for Data Type of Exchange Channels = connection = System-to-System MQ/EDIFACT REST JSON Carrier Choice for Data Type of Exchange Channels = connection = System-to-System REST/JSON REST XML Carrier Choice for Data Type of Exchange Channels = connection = System-to-System REST/XML Carrier Web Portal Carrier Choice for Data Exchange Channels = Web Browser Carrier Mobile Application Carrier Choice for Data Exchange Channels = Mobile Application = Form to be completed 10 Passenger in transit indicator in the PAXLST query Submitted by KLM Royal Dutch Airlines 12  Country of destination as per legal base Article 5 of EES COMMISSION IMPLEMENTING REGULATION Article 5 of ETIAS COMMISSION IMPLEMENTING (EU) 2021/1224 of 27 July 202 REGULATION (EU) 2021/1217 of 26 July 2021 f) one of the following: f) one of the following: (1) the scheduled Member State of entry which applies the Schengen acquis in full; (i) the scheduled Member State of entry; (2) where possible to identify the scheduled Member State of entry, an airport in the Member State of entry which applies the (ii) where possible to identify the scheduled Member State of entry, Schengen acquis in full; an airport in the Member State of entry; (3) the scheduled Member State of entry which does not apply the Schengen acquis in full but operates the Entry/Exit System; 3. Where the passenger is exempt from the scope of Regulation (4) where possible to identify the scheduled Member State of (EU) 2018/1240 in accordance with Article 2 of that entry, an airport in the Member State of entry which does not Regulation or is in airport transit, the carrier shall be able to specify apply the Schengen acquis in full but operates the Entry/Exit it in the verification query System; 4. Where the passenger is exempt from the scope of Regulation (EU) 2017/2226 in accordance with Article 2 of that Regulation or is in airport transit, the carrier shall be able to specify it in the verification query. 13  Use Case 1: Netherlands Austria JFK-AMS-VIE Both EES and Both EES and ETIAS apply ETIAS apply ❑ For the itinerary JFK-AMS-VIE, the below case is possible: • The passenger enters the Schengen area in AMS, and then takes a new flight to VIE → The carrier shall submit the query for relevant passengers considering AMS or Netherlands as destination → The Carrier Interface will evaluate the query and provides the reply based on traveller information: OK, Not OK EES, Not OK ETIAS or NA. 14  Use Case 2a – before ETIAS entry into operation: Netherlands Cyprus JFK-AMS-LCA Both EES and ETIAS applies ETIAS apply but not EES ❑ For the itinerary JFK-AMS-LCA, two cases are possible: • Case 1: The passenger enters the Schengen area in AMS, and then takes a new flight to LCA booked separately (different PNRs) → The carrier operating the flight from JFK to AMS, shall submit the query for relevant passengers considering AMS or Netherlands as destination. Then, the Carrier Interface will evaluate the query and provides the reply based on traveller information: OK, Not OK EES or NA. → The carrier operating the flight AMS to LCA, does not need to submit a query to the CI 15  Use Case 2a – before ETIAS entry into operation: Netherlands Cyprus JFK-AMS-LCA Both EES and ETIAS applies ETIAS apply but not EES ❑ For the itinerary JFK-AMS-LCA, two cases are possible: • Case 2: The passenger remains in the transit area and does not cross the Schengen area in AMS. Then various options are possible, before ETIAS go live: → Option 1: the carrier does not send this itinerary as not part of EES scope → Option 2: the carrier sends the itinerary but puts the flag ‘in transit’, NA will be sent In case the carrier sends the full itinerary; the first entry will be checked and the verification of the ! visa will be done considering AMS or Netherland as destination country. For passengers with Cyprus National Visa, a NOT OK EES can be sent as not under the scope. ! 16  Use Case 2a – after ETIAS entry into operation: Netherlands Cyprus JFK-AMS-LCA Both EES and ETIAS applies ETIAS apply but not EES ❑ For the itinerary JFK-AMS-LCA, two cases are possible: • Case 1: The passenger enters the Schengen area in AMS, and then takes a new flight to LCA booked separately ( different PNRs) → The carrier operating the flight from JFK to AMS, shall submit the query for relevant passengers considering AMS or Netherlands as destination. Then, the Carrier Interface will evaluate the query and provides the reply based on traveller information: OK, Not OK EES, Not OK ETIAS or NA. → The carrier operating the flight AMS to LCA, does not need to submit a query to the CI 17  Use Case 2a – after ETIAS entry into operation: Netherlands Cyprus JFK-AMS-LCA Both EES and ETIAS applies ETIAS apply but not EES ❑ For the itinerary JFK-AMS-LCA, two cases are possible: • Case 2: The passenger remains in the transit area and does not cross the Schengen area in AMS. The below options could be considered (to be confirmed after the end of the analysis): → For PAXLST EDIFACT, it can be possible to implement a verification of both LOC 87 (Indicates the first airport of arrival in Schengen) and the LOC 130 (Indicates the final destination airport in the country of destination). → For XML/JSON, no change as the country of destination should be Cyprus 18 Carrier Interface responses Carrier Interface (CI) responses Scenarios Scenario Scenario CI responses CI responses after ETIAS EiO Number before ETIAS EiO 1 Carrier query with EU/Schengen citizens: Not Not applicable Schengen citizens + Schengen Associated applicable countries citizens + RO, BG, HR, CY, IE citizens 2 Carrier query with visa exempt traveller Not OK or Not OK ETIAS based on the data under the scope of ETIAS applicable Travel authorization validation 3 Carrier query with a non-Schengen Not The CI will check both EES and ETIAS Member State destination where ETIAS is applicable systems. In case of negative answer required ( ex: Cyprus) from both ETIAS and EES, then the CI checks the traveller nationality (not applicable for Visa Required, NOT OK ETIAS for Visa Exempt) 20 Carrier Interface (CI) responses Scenarios Scenario Scenario CI responses before CI responses after ETIAS EiO Number ETIAS EiO 4 Carrier query with a trip starting CI verification For passenger under the scope of from a non-Schengen MS to a performed and one of ETIAS, travel authorisation verification Schengen State the following reply sent not needed but acceptable based on based on passenger carrier system logic. type: OK, Not OK EES For passenger under the scope of EES, or NA a verification of single and double entries visa is needed. 5 Carrier query with a destination The CI will send 422 The CI will send 422 error as the country in Ireland error as the country of country of destination is not under the destination is not under scope the scope 21 THANK YOU! eu-LISA European Union Agency for the Operational Management of Large-Scale IT Systems in the Area of Freedom, Security and Justice Vesilennuki 5, 10415 Tallinn, Estonia www.eulisa.europa.eu  Carrier Working Group Technical updates November 2022 Handling instructions for SENSITIVE information are given at https://europa.eu/!qG39Vd  An overview of the forms and details of the REST Option 23/11/2022 2  1. Introduction - Connection Options : S2S / Web Portal / Mobile App 23/11/2022 3  2. Review of the Forms to be completed by the carriers choosing S2S option 1. Registration Form for Carrier and eventually the Service Provider Contacts (F03) • Can be found in the Welcome Pack, which carrier will receive after the carrier SPOC has signed the NDA 2. Form for Details of System to Be Connected to eu-LISA’s Carrier Interface (F04) • Can be found in the Welcome Pack, which carrier will receive after the carrier SPOC has signed the NDA 3. Forms for the Interface Technical Information (F04a and F04b for xSIM) • Summarizes all the technical details required for configuration of the system to be interfaced • eu-LISA and Carrier’s interfaces parameters are organized in two distinct files: 1. MQ (UN / EDIFACT) over IPsec VPN option (F04a) 2. API REST/JSON or /XML over mTLS option (F04b)  presentation focus • Technical Information Form to be completed (with the help of the Service Provider depending IF any was declared in F03) • Returned to the Carrier in a final communication to the SPOC with ALL the info required to implement the S2S connection (this will be the entry criteria for the start of the next phases i.e. Pre-CT / Certification Testing) 23/11/2022 4  3. Forms exchange for REST details - Communication flow 2. REST Form 4b to be filled (includes Public Carrier with 1. Completed Form 3 and Form 4 Carrier with Certificate) S2S option REST selected Interface Eu-LISA 4. Completed REST Form Onboarding (incl. additional information) Team 3a. Filled REST Form 4b (Yellow cells) Eu-LISA Technical Team 3b. Filled REST Form 4b (Yellow cells) 5. REST connection ready communication 23/11/2022 5 4. Security - REST API (JSON or XML) over mTLS – Pre-CT and CT eu-LISA xSIM Public Carrier1 certificate Public certificate nnnnn.travel-europe.europa.eu API Gateway Internet API Gateway Firewall Carrier2 Public certificate API Gateway eu-LISA PGD Private Private Carrier1 certificate nnnnn.travel-europe.europa.eu certificate API Gateway Internet API Gateway Firewall Carrier2 Private certificate API Gateway The API gateway is a generic term for the API Gateway Carrier endpoint for REST connectivity 6 5. Security - REST API (JSON or XML) over mTLS – Production eu-LISA PRD main site Carrier1 Private certificate API Gateway API Gateway Firewall Carrier2 Private certificate API Gateway nnnn.travel-europe.europa.eu Internet Private certificate eu-LISA PRD backup site API Gateway Firewall The API gateway is a generic term for the API Gateway Carrier endpoint for REST connectivity 7 6. Connectivity - REST Channel 23/11/2022 8  7. Carrier registration form API Form structure • API connection details Object Description Value Please be aware that the yellow fields are mandatory Carrier or Service Provider connection Carrier or Service Provider details Nr. Name IP Address Hostname (FQDN) Details Name, IPv4/IPv6 address, Hostname 1 myname 1.2.3.4 test.mycompany.com 2 <to be filled-in by the carrier/service provider> <to be filled-in by the carrier/service provider><to be filled-in by the carrier/service provider> 3 <to be filled-in by the carrier/service provider> <to be filled-in by the carrier/service provider><to be filled-in by the carrier/service provider> 4 <to be filled-in by the carrier/service provider> <to be filled-in by the carrier/service provider><to be filled-in by the carrier/service provider> Certificate authority name - The certificates are obtained Public certificate issuer name from a third-party certificate authority (CA) containing <to be filled-in by the carrier/service provider> verified public keys. - used for mTLS authentification Public certificate common name CN of the client <to be filled-in by the carrier/service provider> Public certificate validity Expiration date <to be filled-in by the carrier/service provider> Estimated number of request Estimation of how many requests per day (if possible) <to be filled-in by the carrier/service provider> Endpoint Endpoint for XML and JSON requestes https://name.travel-europe.europa.eu/eulisa/example/example-verification <----- not the real one Public certificate of the endpoint Certificate will be attached with the form CN - SIMAPI.travel-europe.europa.eu ; Issuer - BE, GlobalSign nv-sa Public certificate validity Expiration date 07/02/1980 06:23 Key name to be added into the header Client ID Key X-ABC-Client-ID *ID value will be sent after onboarding* Please note all carrier mandatory fields are marked with yellow background. 23/11/2022 9  8. What form for which connection Carrier Interface Option F01 F02 F03 F04 F04a F04b F05 F06 MQ Client – Server Carrier Choice for Data Type of Exchange Channels = connection = System-to-System MQ/EDIFACT MQ Server – Server Carrier Choice for Data Type of Exchange Channels = connection = System-to-System MQ/EDIFACT REST JSON Carrier Choice for Data Type of Exchange Channels = connection = System-to-System REST/JSON REST XML Carrier Choice for Data Type of Exchange Channels = connection = System-to-System REST/XML Carrier Web Portal Carrier Choice for Data Exchange Channels = Web Browser Carrier Mobile Application Carrier Choice for Data Exchange Channels = Mobile Application = Form to be completed 23/11/2022 10  Carrier Interface responses 23/11/2022 11  Carrier Interface (CI) responses Scenarios Scenario Scenario CI responses CI responses after ETIAS EiO Number before ETIAS EiO 1 Carrier query with EU/Schengen citizens: Not Not applicable Schengen citizens + Schengen Associated applicable countries citizens + RO, BG, HR, CY, IE citizens 2 Carrier query with visa exempt traveller Not OK or Not OK ETIAS based on the data under the scope of ETIAS applicable Travel authorization validation 3 Carrier query with a non-Schengen Not The CI will check both EES and ETIAS Member State destination where ETIAS is applicable systems. In case of negative answer required ( ex: Cyprus) from both ETIAS and EES, then the CI checks the traveller nationality (not applicable for Visa Required, NOT OK ETIAS for Visa Exempt) 23/11/2022 12  Carrier Interface (CI) responses Scenarios Scenario Scenario CI responses before CI responses after ETIAS EiO Number ETIAS EiO 4 Carrier query with a trip starting CI verification For passenger under the scope of from a non-Schengen MS to a performed and one of ETIAS, travel authorisation verification Schengen State the following reply sent not needed but acceptable based on based on passenger carrier system logic. type: OK, Not OK EES For passenger under the scope of EES, or NA a verification of single and double entries visa is needed. 5 Carrier query with a destination The CI will send 422 The CI will send 422 error as the country in Ireland error as the country of country of destination is not under the destination is not under scope the scope 23/11/2022 13 THANK YOU! eu-LISA European Union Agency for the Operational Management of Large-Scale IT Systems in the Area of Freedom, Security and Justice Vesilennuki 5, 10415 Tallinn, Estonia www.eulisa.europa.eu  ETIAS Central Unit - Operational updates 17th meeting of the informal ad hoc Working Group for Carriers November 23rd 2022 ETIAS Central Unit Division Assistance Centre Unit  Agenda ▪ Frequently Asked Questions(FAQs) – state of play ▪ Standard Operating Procedures (SOPs) – state of play ▪ Way Forward 2  Frequently Asked Questions (FAQs) - State of Play ▪ The 3rd version of FAQs, divided into public and private with around 40 additional questions, is currently under revision to be published before the end of the year ▪ The latest version will be translated into all official EU languages ▪ The new Q&A will be marked in green ▪ https://www.eulisa.europa.eu/Organisation/GoverningBodies/Documents/WG%20Carriers/Docu ments/Carrier_FAQ.pdf 3  Standard Operating Procedures (SOPs) - State of Play ▪ The draft version of SOPs for carriers is being finalized in cooperation with eu-LISA ▪ After the review by COM, SOPs document will be shared with carriers ▪ Alongside with the publication of SOPs for carriers, a survey will be distributed to carriers to provide their input 4  Way Forward ▪ Frontex continues to work on the FAQs by collecting and adding questions, raised during the Carrier Working Groups and posed by the carriers ▪ Frontex will continue its close cooperation with eu-LISA on finalizing the SOPs draft that will be shared with carriers ▪ For any questions related to the FAQs, please contact us at: [email protected] 5 Thank you for your attention!  DRAFT AGENDA 17th Carriers Working Group Air Session Video conference meeting 23 November 2022 1. Introduction a. Agenda b. Carriers meeting calendar 2. Technical updates (eu-LISA) 3. Legal updates (European Commission) 4. Operational updates (Frontex) 5. Q&A End of the meeting EUROPEAN UNION AGENCY FOR THE OPERATIONAL MANAGEMENT OF LARGE-SCALE Vesilennuki 5, 10415 Tallinn, Estonia IT SYSTEMS IN THE AREA OF FREEDOM, SECURITY AND JUSTICE www.eulisa.europa.eu  Video conference, 23 November 2022 Carriers Working Group of 23 of November 2022 Summary Subject: Monthly Carriers Working Group meeting 1st Session – Sea and Land Carriers at 10:00– 12:00 CET Participants: Carriers for the sea and land industry, carrier associations, European Commission (DG HOME), Member State (MS) experts, Frontex and eu-LISA 1. Introduction The agenda of the 17th Carriers Working Group was presented to the participants. The WG took note of the carriers meeting calendar with a. Agenda highlights of the dates of previous and upcoming meetings. The next b. Carriers Carriers Working Group will take place on 14 December. Ad hoc meetings meeting calendar can be organised upon request. 2. Legal Updates DG HOME informed the WG that the Practical Handbook for Border (European Guards has been published. The Handbook is available online at: https://home-affairs.ec.europa.eu/policies/schengen-borders-and-visa/border- Commission) crossing_en The definition of the crew of a ship was provided, as defined by the Handbook: “Crew members include all persons actually employed for duties on board during a voyage in the working or service of a ship and included in the crew list”. In the context of EES, DG HOME reminded carriers the obligation, as from EES EiO, to check through the carrier interface the validity of single and double-entry visas for third country nationals holding such visas. Visual inspection of the validity of multi-entry visas shall continue until further enhancement of the Carrier Interface to support such checks in the future. The Agency specified that following the ETIAS Entry into Operation, the carrier interface should also be used to check the ETIAS travel authorisations. European Union Agency for the Operational Management of Large-Scale Vesilennuki 5, 10415 Tallinn, Estonia IT Systems in the Area of Freedom, Security and Justice www.eulisa.europa.eu 1  Thereafter some of the frequently asked questions posed by carriers were presented. The cases of IE and UK citizens were explained. While the citizens from IE, being EU citizens,are out of scope of any such check, the UK citizens are in scope of ETIAS regulations and verifications should take place like any other Visa exempt passenger. On the other hand, all passengers travelling to IE shall not be checked . 3. Technical The Agency outlined that it will be possible to use three types of interfaces Updates (eu- - System to System (S2S), web portal and mobile application – to connect LISA) to the carrier interface, and that it will be possible to use all the three in parallel. Thereafter, technical updates regarding setting up and testing the S2S connection were provided by eu-LISA. An overview of the forms and details of the option of the REST interface for the S2S connection were presented in detail. The way to select this option and to provide all the information needed in the corresponding forms was depicted. The form containing the REST interface technical details is the form F04b, that should be first filled by carriers and then completed by the agency’s technical team and returned to carriers. Diagrams detailing the connection between eu-LISA and carriers, using REST, during testing and production, were presented. Furthermore, an overview of the content of the F04b form was provided. The cells to be completed by the carriers are highlighted in yellow. The forms needed for each type of connection were recalled. eu-LISA also presented a complete overview of forms that the carriers should fill throughout the process. The number of forms to be filled depends on the choice of connection channels for each carrier. If the carrier chooses several types of connectivity, they will need to fill the forms accordingly. As a response to a question, eu-LISA specified that certain information will be sent by the agency only after the carrier has submitted the necessary forms. 4. Operational Frontex informed the Carriers WG about the updates to the Frequently Updates (Frontex) Asked Questions (FAQ) document and the Standard Operating Procedures (SOP). Frontex has added 40 questions to the FAQ document and the new questions have been highlighted. The 3rd version of the document is currently under revision and is to be published before the end of the year. That version will be translated into all EU languages in Q1 2023. Frontex invited carriers to support Frontex and eu-LISA with the drafting of the document by sending in questions and comments. This way the document will be of maximum value when the systems enter into operation. European Union Agency for the Operational Management of Large-Scale Vesilennuki 5, 10415 Tallinn, Estonia IT Systems in the Area of Freedom, Security and Justice www.eulisa.europa.eu 2  The draft version of the Standard Operating Procedures (SOP) for carriers is being finalised in cooperation with eu-LISA, and after a review by COM it will be shared with carriers (tentatively by the end of the year). Carriers will be invited to provide input to a survey on the SOP document in due time. Questions regarding the document should be directed to Frontex to [email protected]. Frontex will continue to update the document. 5. Q&A During the Q&A session, questions from the carriers were answered by COM and eu-LISA. Clarifications on cases of the crew members of ships not leaving the ship or port vicinities were provided. Member States have different rules for crew, which are documented in section 10.2 of the Carrier_FAQ.pdf (europa.eu).. Also, the scenarios of ships changing route to a Schengen port, and the procedures to be done regarding obtaining visas were discussed. The Commission shall examine the procedures to be followed when crew requests visas at arrival. It was explained that cargo ships are also obliged to check status of passengers via the Carrier Interface. The scenarios of when carriers shall query the Carrier Interface, and its responses before and after ETIAS entry into operation, were presented. European Union Agency for the Operational Management of Large-Scale Vesilennuki 5, 10415 Tallinn, Estonia IT Systems in the Area of Freedom, Security and Justice www.eulisa.europa.eu 3  2nd Session – Air Carriers at 13:00–16:00 CET Participants: Carriers for the air industry, carrier associations, European Commission (DG HOME), Member State (MS) experts, Frontex and eu-LISA 1. Introduction The agenda of the 17th Carriers Working Group was presented to the participants. The WG took note of the carriers meeting calendar with a. Agenda highlights of the dates of previous and upcoming meetings. The next b. Carriers Carriers Working Group will take place on 14 December. Ad hoc meetings meeting calendar can be organised upon request. 2. Technical The Agency outlined that it will be possible to use three types of interfaces Updates (eu- - System to System (S2S), web portal and mobile application – to connect LISA) to the carrier interface, and that it will be possible to use all the three in parallel. Thereafter, technical updates regarding setting up and testing the S2S connection were provided by eu-LISA. An overview of the forms and details of the option of the REST interface for the S2S connection were presented in detail. The way to select this option and to provide all the information needed in the corresponding forms was depicted. The form containing the REST interface technical details is the form F04b, that should be first filled by carriers and then completed by the agency’s technical team and returned to carriers. Diagrams detailing the connection between eu-LISA and carriers, using REST, during testing and production, were presented. Furthermore, an overview of the content of the F04b form was provided. The cells to be completed by the carriers are highlighted in yellow. The forms needed for each type of connection were recalled. eu-LISA also presented a complete overview of forms that the carriers should fill throughout the process. The number of forms to be filled depends on the choice of connection channels for each carrier. If the carrier chooses several types of connectivity, they will need to fill the forms accordingly. As a response to a question, eu-LISA specified that certain information will be sent by the agency only after the carrier has submitted the necessary forms. Furthermore, the specific scenario submitted by KLM Royal Dutch Airlines of passenger in transit indicator in the PAXLST query was discussed. The point in discussion was related to specific passengers with a final travel destination in countries not fully implementing the Schengen acquis or using EES, but with an itinerary which includes a first stop in another MS. As an explanation, the understanding of “country of destination” in the legal base European Union Agency for the Operational Management of Large-Scale Vesilennuki 5, 10415 Tallinn, Estonia IT Systems in the Area of Freedom, Security and Justice www.eulisa.europa.eu 4  was presented. The itineraries of JFK-AMS-VIE and JFK-AMS-LCA were considered for the discussion of what type of queries shall be made before and after the ETIAS entry into operation. A dedicated discussion regarding the topic raised by KLM will be scheduled, in order to examine possible solutions. eu-LISA and COM shall discuss a table of EES/ETIAS territorial scope/scenarios and provide additional clarifications. The scenarios of when carriers shall query the Carrier Interface, and its responses before and after ETIAS entry into operation, were presented to the WG. 3. Legal Updates DG HOME informed the WG that the Practical Handbook for Border Guards (European has been published. The Handbook is available online:https://home- Commission) affairs.ec.europa.eu/policies/schengen-borders-and-visa/border-crossing_en It was noted that the secondary legislation for VIS Recast is being drafted and that the EES/ETIAS website is open to the public. Work continues on the specific handbook for EES and ETIAS and on the Entry into Operation of EES with progressive application. Material for the public communication campaign is being prepared. 4. Operational Frontex informed the Carriers WG about the updates to the Frequently Updates (Frontex) Asked Questions (FAQ) document and the Standard Operating Procedures (SOP). Frontex has added 40 questions to the FAQ document and the new questions have been highlighted. The 3rd version of the document is currently under revision and is to be published before the end of the year. That version will be translated into all EU languages in Q1 2023. Frontex invited carriers to support Frontex and eu-LISA with the drafting of the document by sending in questions and comments. This way the document will be of maximum value when the systems enter into operation. The draft version of the Standard Operating Procedures (SOP) for carriers is being finalised in cooperation with eu-LISA, and after a review by COM it will be shared with carriers (tentatively by the end of the year). Carriers will be invited to provide input to a survey on the SOP document in due time. Questions regarding the document should be directed to Frontex to [email protected]. Frontex will continue to update the document. 5. Q&A During the Q&A session, questions from the carriers were answered. European Union Agency for the Operational Management of Large-Scale Vesilennuki 5, 10415 Tallinn, Estonia IT Systems in the Area of Freedom, Security and Justice www.eulisa.europa.eu 5  The cases of business jets were discussed, on the obligations of this type of carrier . A dedicated session focused on these cases should be scheduled in the upcoming weeks. It was also clarified that the web portal and mobile application will not be tested by carriers. Their only obligation will be to train staff once the training environment has been provided to them. European Union Agency for the Operational Management of Large-Scale Vesilennuki 5, 10415 Tallinn, Estonia IT Systems in the Area of Freedom, Security and Justice www.eulisa.europa.eu 6  DRAFT AGENDA 17th Carriers Working Group Sea and Land Session Video conference meeting 23 November 2022 1. Introduction a. Agenda b. Carriers meeting calendar 2. Legal updates (European Commission) 3. Technical updates (eu-LISA) 4. Operational updates (Frontex) 5. Q&A End of the meeting EUROPEAN UNION AGENCY FOR THE OPERATIONAL MANAGEMENT OF LARGE-SCALE Vesilennuki 5, 10415 Tallinn, Estonia IT SYSTEMS IN THE AREA OF FREEDOM, SECURITY AND JUSTICE www.eulisa.europa.eu Saatja: EULISA CARRIERS <[email protected]> Saadetud: 12.12.2022 09:30 Adressaat: EULISA CARRIERS <[email protected]> Teema: [Carriers]: 17th meeting of Carriers Working Group - meeting materials SENSITIVE Dear Madam, Dear Sir, Thank you for attending the 17th Carriers Working Group meeting held on November 23, 2022. Please find attached for your reference the meeting documents (including the presentations, meeting agenda and summary). Please keep in mind that information provided by eu-LISA and the European Commission is considered sensitive, and can be distributed only on a need-to-know basis; it is not to be released outside of the information stakeholders. In addition, as mentioned previously, please note that a number of carrier related presentations have been published on the eu-LISA . There you will find a FAQ document, which includes answers to the most frequently asked questions , as well as several Explanatory Presentations. Please feel free to make reference to the presentations or share the link further as you find relevant. Should you have any question please contact . Kind regards, on behalf of the eu-LISA Carriers team ----------------------------- eu-LISA / European Union Agency for the Operational Managementof Large- Scale IT Systems in the Area of Freedom, Security and Justice Disclaimer: This message is sent in confidence and is only intended for the named recipient. If you received this message by mistake, you may not use, copy or distribute this message or any part of its contents or rely upon theinformation contained in it. Please kindly notify the sender immediately by email and delete the relevant emails from any computer. This message does not constitute a commitment by eu-LISA unless otherwise indicated. Handling instructions for SENSITIVE information are given at