Report of ACP, WG-I-04 Meeting
(Montreal, 3-7 December 2007)
ACP-WGI04-REPORT07December 2007
AERONAUTICAL COMMUNICATIONS PANEL (ACP)
WG I – Internet Protocol Suite – 4th Meeting
Montreal, Canada,3-7December 2007
Report of ACP WGI-04Meeting
Presented by the Rapporteur (Andy Colón)
WGI WP413 Meeting Report Final WG I-04 Page1
Report of ACP, WG-I-04 Meeting
(Montreal, 3-7 December 2007)
Table of Contents
1.AGENDA ITEM 1: MEETING ORGANIZATIONAL ISSUES
2.AGENDA ITEM 2: APPROVAL OF THE AGENDA
3.AGENDA ITEM 3: OUTCOME OF WG-I/02 MEETING
3.1 Action Items from WG-I/03 Meeting
3.2Review WG-I/02 Meeting Report
4.AGENDA ITEM 4: DEVELOPMENT OF TECHNICAL MATERIAL ARISING FROM ANY NEW/REVISED REQUIREMENTS
4.1 Receive status and discuss new material from Internet Subgroup
4.2Receive status and discuss new material from GM and VoIP Subgroup
4.3Receive status and discuss new material from Security and Mobility Subgroup
4.4Discuss status of Application work;
4.5New Papers
5.AGENDA ITEM 5: FUTURE WORK FOR NEXT MEETING
6.AGENDA ITEM 6: OUTPUT OF WG I TO OTHER GROUPS
7.AGENDA ITEM 7: NEW BUSINESS
APPENDIX A
ACP WGI AGENDA
APPENDIX B WORKING PAPER LIST
APPENDIX C LIST OF ATTENDEES
WGI WP413 Meeting Report Final WG I-04 Page1
Report of ACP, WG-I-04 Meeting
(Montreal, 3-7 December 2007)
1.AGENDA ITEM 1: MEETING ORGANIZATIONAL ISSUES
1.1The Working Group Rapporteur, Andy Colón, welcomed the participants to the 4th meeting of Working Group I of the ICAO Aeronautical Communications Panel (ACP). (Hereafter “the Meeting”). A list of participants is in Appendix C.
1.2The fourth meeting of Working Group I was held in Montreal, Canada from the3rd to 7th ofDecember 2007 at the offices of ICAO. WG I is responsible for continuing the work assigned by ACP/1 for the development of the ICAO ATN to be based on Internet Protocol Suite (IPS) standards.
1.3The meeting was attended by 9 experts and the Panel Secretary, Mr.L. Jonasson. The list of participants is in Appendix C of this report. Fifteen working papers andfour information papers were presented at the meeting. The working papers are listed in Appendix B to this report. These papers are available on the ACP website (
2.AGENDA ITEM 2: APPROVAL OF THE AGENDA
2.1The draft agenda, as communicated by the Rapporteur to the memberswas approved. The agenda is in Appendix A to this report.
3.AGENDA ITEM 3: OUTCOME OF WG-I/02MEETING
3.1 Action Items from WG-I/03 Meeting
3.1.1Terry Davis provided IP06 via Greg Saccone, which will provide input on the ICAO request of allocating a block of IPv6 addresses and a block of 32 bit AS numbers to ICAO. With IP06, this action is closed.
3.2Review WG-I/02 Meeting Report
3.2.1Kelly Kitchens presented WP12, the WG-I03 Report. During the review of the meeting report, the working group took an action to update section 5 with the appropriate work plan items. The report was accepted as presented with no additions or corrections.
4.AGENDA ITEM 4: DEVELOPMENT OF TECHNICAL MATERIAL ARISING FROM ANY NEW/REVISED REQUIREMENTS
4.1 Receive status and discuss new material from Internet Subgroup
4.1.1Eivan Cerasi presented WP02 which introduces application related provisions for the ATNIPS, thereby aligning the nature of its content with the ATNOSI Manual (Doc 9705{edi3}/9880). As a first step, provisions for legacy ATN ground applications (defined in 9705/9880) are made. For ATSMHS, compliance to Doc 9705/9880 is foreseen with the exception of the interface to the transport service. RFC2126 for native IPv6 support or RFC1006 combined with additional IPv6 conversion mechanism is mandated. For AIDC, it is recalled that no implementation of Doc 9705/9880 has been identified; it is understood that there is an ASIA/PAC regional implementation which is not IP-based. The EUR regional implementation of OLDI/FMTP is therefore proposed as it complies with the AIDC operational function while operating over TCP/IPv6. After discussion it is agreed to use the term “may” indicating that it is a possible approach to enable AIDC services over IP. An alternative to the AIDC specification approach was proposed. This proposal was to require the following: “For operation in the ATN/IPS, the AIDC application shall be adapted to run over TCP/IP”. After some discussion, the Working Group decided against this alternative proposal in favor of specifying the optional use of the OLDI protocol for AIDC. Further editorials were made on the paper which has been updated as WP02a. The group agreed to baseline the new version of the ATNIPS manual on the basis of WP02a.
4.1.2Tom McParland presented WP 13, “Administrative Domains and Routing Domains”. This paper suggests modifications for the IPS Technical Manual related to the definitions and use of the terms “Administrative Domain” and “Routing Domain". During review of the paper several modifications were agreed to. The changes are incorporated in a new version of the Working Paper (13a).
4.2Receive status and discuss new material from GM and VoIP Subgroup
4.2.1Eivan Cerasi presented WP03, which is a review of the guidance material. Previous extensive sections on multicast are removed and replaced by external references. The addressing scheme section is reduced. Additional inputs in the GM involve the addition of preliminary TCP/UDP port numbers, ATNIPS policies, AS numbering plan and IPv4/IPv6 transition material. Discussion on the IPv4/IPv6 transitional section occurs in view of the IPv4 current limitation of AMHS systems and on-going implementations (further guidance on this issue is to be integrated). It was agreed to accept the changes as a new draft of the GM and use that as a basis to capture further comment. Kelly Kitchens will further consolidate the document. It is understood that the present status of the GM material is too immature for external circulation.
4.2.2Eivan Cerasi presented IP01, which is a EUROCAE status report of WG67 dealing with VoIP. IP01 indicates availability of four ED documents in early 2008 for wide circulation within the aeronautical community. ICAO is investigating the possibility to reference RTCA/EUROCAE material in it’s documents. However, the group is concerned that the EUROCAE 67 documents would be too specific to the European environment. Eivan Cerasi will request that these documents are forwarded to the WGI in order to determine which parts could be useful reference for WGI guidance material.
4.2.3Christian Kissling of the German Aerospace Centre (DLR) Institute of communication and Navigation presented WP06, a paper on “QoS architectures for the ATN/IPS” . This paper provides an overview of possible IPS QoS architectures and their implications on system complexity and suitability for the ATN/IPS scenario, as also investigated in the NEWSKY project. For provision of QoS in a heterogeneous environment (i.e. a network consisting of different network portions) the importance of a conformal definition of QoS priority tags among the network portions (horizontal mapping) as well as mapping of QoS from the higher to the lower layers (vertical mapping) was pointed out. Moreover the paper presented different architectures such as IntServ, DiffServ and variants, MPLS and IPv6 centric solutions. The importance of a homogeneous treatment of traffic classes over the different networks was pointed out and will be specified in the technical manual for the next meeting. In addition, selected QoS architectures will be included in the IPS Guidance Material for the next meeting. Eivan Cerasi took the action to make a proposal for the specification of requirements for mapping of priority classes to the IPS traffic classes.
.
4.3Receive status and discuss new material from Security and Mobility Subgroup
4.3.1Tom McParland presented WP10, “Draft Requirements for Local Mobility Management”. This paper provides draft requirements for local mobility management for the IPS Technical Manual. The paper specifies the use of network-based local moblity management within an access network. There was discussion on whether the approach had enough detail since the actual mobility management protocol was left to the service provider to decide. The majority of the Working Group agreed that this would be the most flexible approach. On the air-ground interface it was suggested that the use of ES-IS and the Mobile SNDCF not be specified. For VDL-2 futher investigation is required to determine if 8208 or AVLC handover should be used. There was also discussion on whether or not to specify the requirements in terms of the IETF NETLMM WG specifications since that working group is developing a specific mobility management protocol, namely Proxy Mobile IP. It was agreed to change the specification to have functional requirements rather than require the entities defined by the NETLMM WG (i.e., a Local Mobility Anchor (LMA) and Mobility Access Gateway (MSG)). EUROCONTROL also reported that they were investigating an approach developed by the Military to operate IP over Link-16.
4.3.2Vic Patel presented WP11,”IPS Air-Ground Security Options”. This paper identifies several options for air-ground security in the Internet Protocol Suite (IPS) environment and suggests which options are suitable for legacy ATN applications, for standard TCP/IP applications, and for future service oriented applications. The working group agreed with the papers recommendation that operation of IPsec, SSL/TLS, and ATN security be further investigated for possible inclusion in the IPS Technical Manual for air-ground security and that XML Signature, XML Encryption and WS-security be investigated further for possible inclusion in the Guidance Material. The chairman expressed concern on having actual requirements available for the Technical Manual in time for publication. It was noted that the requirements would most likely end up at a high level. The results of the investigation would be reported, in the form of guidance material.
4.4Discuss status of Application work;
4.4.1Greg Saccone presented WP7. WP7 give a listing of the legacy ATN applications and services, and options for providing support for IPv6. It was agreed that the paper would be modified to clarify the differences between services and applications. One of the questions brought up by the paper was where to capture changes necessary to make to the existing applications support the IPS. It was decided that these changes would be put into the Technical Manual “Part 2”, which would leave “Part 1” as a smaller document. As the approaches to accommodate the legacy applications were discussed, the need for keeping CM was questioned. For some regions, the use of CM has become optional at best, so the group discussed whether CM should not be migrated to support IPS. This led to a larger discussion on what exactly the group should be doing regarding applications. Although this is an opportunity to change applications, given the time constraints it would be difficult to completely re-define the applications at this point. The group agreed that the application enhancements should be limited to providing IPS accommodation for the legacy applications, including all of the air-ground applications. It was noted that any large changes to applications (e.g. making an application native IP) should be studied under an expanded terms of reference, either within the ACP or within another group. The paper will be refined for the next meeting, including the draft of the “IPS Dialogue Service” which is intended to replace the ULCS as the interface to the transport layer.
4.4.2Greg Saccone presented WP8, which discussed the usage of XML. There had been previous papers noting the growing acceptance and use of XML as an industry standard. This paper discussed pros and cons of using XML in place of ASN.1 for data representation. Usage of both ASN.1 and XML are similar from a programming standpoint, so it therefore basically becomes a question of bandwidth usage, architecture impacts and tools availability. It was also noted that many ASN.1 compilers can generate XML schemas automatically. The group agreed that the ASN.1 continue to be supported in the near term, and as part of the expanded terms of reference to investigate new applications, XML would be further investigated for future applications.
4.4.3Greg Saccone presented WP9, giving the modifications to ASN.1 that would be necessary for CM to support IPS. The group agreed that the full ASN.1 should be included in Part 2 of the manual for the next meeting.
4.5New Papers
4.5.1Eivan Cerasi presents WP05 which is a draft presentation on ACP/WGI activities to a European workshop on AMHS (Dec 12th). Comments on the presentation were invited, integrated into the presentation and forwarded to the workshop chairman.
4.5.2Eivan Cerasi presents IP02 which is a EUROCONTROL press release concerning the European legislative material relating to CPDLC deployment above FL285. The press release contains proposed implementation dates after the result of a formal consultation procedure to develop regulation. The set of deliverables are available at It is recalled that EUROCONTROL prepared the material following a mandate from the European Union. The proposed legislative material has been forwarded to the European Union for further consideration and approval by the Single European Sky committee.
4.5.3Gregg Saccone presented IP6, the paper is a request of IP address information. It gives an outline of a letter to be sent by ICAO requesting a block of addresses. The outline was agreed to be a good starting point, and some editorials expanding on definitions and putting the letter in the context of ICAO terminology were proposed. There are questions as to who this letter should be sent to, i.e. should it go to IANA instead. The paper also referenced numbers of nodes that are envisioned to exist. The working group believes that taking a more generic approach, and referring to the general complexity of the ICAO domain, would be better than trying to quantify specific numbers. The working group also believes the size of the request should be specified, instead of “as large as possible”. Based on the equivalent OSI space, it is believed that requesting a /16 or /19 space would be reasonable. Lastly, Terry Davis, the author of the paper is still waiting for further input from IETF as well.
5.AGENDA ITEM 5: FUTURE WORK FOR NEXT MEETING
5.1The future work plans, and recommendations are listed below.
Following is part of the Manual for ATN using IPS Standards and Protocols Doc 9896
- ATN/IPSRequirements for VoIP and Mobility
- ATNIPSRequirements on Detailed Technical Specifications
- Develop ATNIPS Guidance Material
- Develop ATNIPS Addressing Plan
- Develop ATNIPS Security Material
- Develop ATN/IPS accommodations for Legacy Applications
6.AGENDA ITEM 6: OUTPUT OF WG I TO OTHER GROUPS
6.1The following items where identified as items which will be distributed from WG-I to other group:
- The January and June 2008 WG-I Meetings are being planned to occur with regional meetings to facilitate coordination.
7.AGENDA ITEM 7: NEW BUSINESS
7.1 The tentative meeting schedule for 2007 and 2008 is listed below, please note that all meeting are in Montreal, unless specifically identified as other:
- January 14-18Bangkok
- March 17-21Miami (planned)
- June 2-6 Paris
- August 25-29Montreal
- October 27-31Montreal
END
WGI WP413 Meeting Report Final WG I-04 Page1
Report of ACP, WG-I-04 Meeting
(Montreal, 3-7 December 2007)
APPENDIX A
ACP WGI AGENDA
AERONAUTICAL COMMUNICATION PANEL
Working Group I – Internet Protocol Suite
4thMeeting
3rd – 7th December 2007
Montreal, Canada
Agenda
- Meeting Organizational Issues
- Approval of the Agenda
- Discuss 3rdWG-I Meeting
- Discuss Action Items from WG-I Meeting
- Review WG-I 3rdMeeting Report
- Development of technical material arising from any new/revised requirements
- Receive status and discuss new material from Internet Subgroup
- Receive status and discuss new material from GM and VoIP Subgroup
- Receive status and discuss new material from Security and Mobility Subgroup
- Discuss status of Application Work
- Review the latest version of the IPS G-G Manual on Detailed Technical Specifications
- New Papers
- Future work for next meeting - allocate actions
- Output of WG-I to other Groups
- New Business
***END***
WGI WP413 Meeting Report Final WG I-04 Page1
Report of ACP, WG-I-04 Meeting
(Montreal, 3-7 December 2007)
APPENDIX B WORKING PAPER LIST
WG-I – Internet Protocol Suite
4thMeeting
3rd7th December2007
Montreal, Canada
WP No. / Agenda Item / Presenter / WP TitleWP0401 / 1 / Rapporteur / Invitation, Nomination Form, Meeting Bulletin and Draft Agenda
WP0402 / 2 / Eivan Cerasi / Draft Manual on the Detailed Technical Specifications for the ATN using the Internet Protocol Suite (IPS); GG Apps added.
WP0403 / 2 / Eivan Cerasi / ATN IPS Guidance Material
WP0404 / 2 / Rapporteur / Working paper list for 4th WG I Meeting
WP0405 / 4.5 / Eivan Cerasi / Proposed presentation for European AMHS Community Specification Workshop, 12 Dec 2007
WP0406 / 4.2 / Christian Kissling / QoS Architectures for the ATN/IPS
WP0407 / 4.4 / Greg Saccone / Application IP Migration Comparison
WP0408 / 4.4 / Greg Saccone / XML Discussion
WP0409 / 4.4 / Greg Saccone / CM ASN.1 Additions for Support of IP
WP0410 / 4.3 / Vic Patel and Tom McParland / Draft Requirements for Local Mobility Management
WP0411 / 4.3 / Vic Patel and Tom McParland / IPS A-G Security Options
WP0412 / 3 / Rapporteur / Meeting Report 3rd Meeting
WP0413 / 4. / Tom McParland / Administrative and Routing Domains
IP0401 / 4.2 / Eivan Cerasi / EUROCAE WG-67 – VOICE OVER INTERNET PROTOCOL FOR ATM
IP0402 / 4.5 / Eivan Cerasi / Proposed CPDLC Rule dates
IP-406 / 4.5 / Greg Saccone / ICAO IP Notice of Intent to Request Address Allocation
WGI WP413 Meeting Report Final WG I-04 Page1
APPENDIX C LIST OF ATTENDEES
ACP WGI-4 – Montreal, Canada – 3rd – 7th December 2007
LIST OF ATTENDEES
ICAO ACP-WG I - Internet Protocol Suite (IPS): Meeting 4, Montreal, Canada
NAME / ORGANIZATION NAME / ADDRESS / PHONE / FAX / E-MAILCOLÓN, Andy / FAA/USA / FAA Technical Ctr. AJP-7150 Atlantic CityInt.Airport, Atlantic CityNJ08405 / +1 609-485-4348 /
McParland, Thomas / BCI/FAA / 304 Harper Drive Suite 203
Moorestown, NJ08057 / 1-609-425-4410 /
KITCHENS, Kelly / BAE/FAA/USA / 901 D Street, Suite 850, Washington, DC20024, USA / +1 202-646 5931
+1 202-646 5815 / mailto:
Abudaowd, Hazim / Saudi Arabia Civil Aviation Authority / P.O.Box 6496
Jeddah, Saudi Arabia / +96 626 717 717
+96626719041 (fax) /
PATEL, Vidyut / FAA/USA / FAA Technical Ctr. AJP-7150 Atlantic CityInt.Airport, Atlantic CityNJ08405 / +16094855046
+6094855630 /
Jonasson, Loftur / ICAO
Panel Secretary / 999 University Street, Montreal, Quebec, Canada, H3C 5H7 / +1-514-954 8219
x 7130
+1-514-954 6759 /
SACCONE; Greg / The Boeing Company / The Boeing Company
PO Box 3707 MC 8R079
SeattleUSA / +1 253 657 6370
+1 253 657 3346 /
Kissling, Christian / German Aerospace Centre (DLR) / Institute of Communications and Navigation
Oberpfaffenhofen
82234 Wessling Germany /
Cerasi, Evian / EUROCONTROL / EUROCONTROL DAP/CSP
96 Ruede la Fusee
B-1130
Brussels, Belgium / +3227293791 /
Olive, Mike / Honeywell /
Page 1 of 11