Report of ACP, WG-I-06 Meeting
(Montreal, 17-20 March 2008)
ACP-WGI06-REPORT20March 2008
AERONAUTICAL COMMUNICATIONS PANEL (ACP)
WG I – Internet Protocol Suite – 6th Meeting
Montreal, Canada,17-20 March 2008
Report of ACP WGI-06Meeting
Presented by the Rapporteur (Andy Colón)
WG_I_6_Meeting Report mar_17_2008Page1
Report of ACP, WG-I-06 Meeting
(Montreal, 17-20 March 2008)
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/05 MEETING REPORT
3.1 Action Items from WG-I/05 Meeting Report
3.2Review WG-I/05 Meeting Report , revised as WP12
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
5.AGENDA ITEM 5: FUTURE WORK FOR NEXT MEETING
6.AGENDA ITEM 6: COORDINATION WITH OTHER GROUPS
7.AGENDA ITEM 7: NEW BUSINESS
APPENDIX A
ACP WGI AGENDA
APPENDIX B WORKING PAPER LIST
APPENDIX C LIST OF ATTENDEES
WG_I_6_Meeting Report mar_17_2008Page1
Report of ACP, WG-I-06 Meeting
(Montreal, 17-20 March 2008)
1.AGENDA ITEM 1: MEETING ORGANIZATIONAL ISSUES
1.1The Working Group Rapporteur, Andy Colón, welcomed the participants to the 6th meeting of Working Group I of the ICAO Aeronautical Communications Panel (ACP).Loftur Jonasson is the ACP Secretary.
1.2The sixth meeting of Working Group I was held in Montreal, Canada from the17th to 20thofMarch 2008, at the ICAO Office in Montreal. WG-I is responsible for continuing the work assigned by ACP/1 for the development of the ICAO Aeronautical Telecommunication Network (ATN), to be based on Internet Protocol Suite (IPS) standards.
1.3The meeting was attended by 12 experts and the Panel Secretary, Mr.L. Jonasson. The list of participants is in Appendix C of this report. Fifteen working papers,one information paper, and one flimsy 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, as presented. The agenda is in Appendix A to this report.
3.AGENDA ITEM 3: OUTCOME OF WG-I/05MEETING REPORT
3.1 Action Items from WG-I/05 Meeting Report
3.1.1Eivan Cerasi will make a request to EUROCAE WG-67 Chairman to forward VoIP documents to WG-I for review. EUROCAE-67 documents are being reviewed to be considered for reference in the Manual for the ATN using IPS Standards and Protocols DOC 9896, in support of VoIP. A link for the EUROCAE-67 documents was forwarded to the WG-I Chairman, closing this action.
3.2Review WG-I/05 Meeting Report , revised as WP12
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.1The Rappatoure presented WP06, Doc 9896 v13f. WP06 is the most current DOC 9896, it has been formatted to support the recommendations of the Secretary as a result of the outcome of WGI05_WP_04. The current format in line with the AMS(R)S Manual.
4.2Receive status and discuss new material from GM and VoIP Subgroup
4.2.1Eivan Cerasi presents WP02which proposes a definition of ATNIPS CoS to be applied at network ingress. The paper proposes a mapping of Annex 10 priorities to two key AF classes with the understanding that the Annex priority tables are met by TCP/IP or UDP/IP protocol elements. Discussion also focused on the priority tables in Annex 10 concerning the A/G subnetworks but was agreed that this subnetwork-dependent and did not influence the CoS definitions. It was also commented that service provider should be given the ability to define additional AF classes other than the two presented in the paper. The mapping table would need to be complemented in order that all applications are properly identified at ingress (port numbers, network prefixes, etc.). With regard to the recommendations within WP03 the following conclusions were reached:
- WGI confirmed the approach to define CoS for the ATNIPS
- Agree that the CoS table is to be integrated into Part I of the IPS manual
- Agreed to document the ATNIPS CoS approach, additional AF class definitions and traffic characterization information as part of the Guidance Material.
It was further commented that between AF classes, different levels of priority may exist and this will be investigated. Eivan Cerasi will prepare contributions for inclusion into Part I and Part II of the IPS Manual.
4.2.2Eivan Cerasi presentedWP11 which is proposed guidance material concerning OLDI/FMTP implementations to enable AIDC services. Reference was made to existing ICAO document in which a mapping between AIDC and OLDI operational messages is documented. Eivan Cerasi will update WP11 with this information and will forward the paper to Kelly Kitchens for inclusion in the Part III Guidance Material.
.
4.3Receive status and discuss new material from Security and Mobility Subgroup
4.3.1Evian Cerasi presented WP03 which builds on the current progress of WGI and proposes to consider Mobile IPv6 as a convergence layer for mobile nodes i.e. aircraft. In viewing Mobile IPv6 as a convergence layer, it allows service providers to select the technologies of their choice to enable service provision and de-couples on-board IP capabilities from IP service provision. From the aircraft perspective, it will either detect that it is at home and not send any binding updates or it will detect that it is attached to a visited network and trigger the binding updates. This topic was well debated within the group and with regard to the recommendations within WP02 the following conclusions were reached:
1)Support for local network mobility will be documented in guidance as a means to enable service provision;
2)Mandate Mobile IPv6 for mobile nodes in the ATNIPS manual;
3)In parallel to (1), agree to insert guidance material to document service flexibility for service providers (PMIP, Layer 2/3)
4)Agree to insert guidance material to document that global mobility options other than MIP may be standardized and referred in future editions of the manual
5)Agree to insert guidance material to document mobile node evolutions through IETF Mobile IPv6 extensions
6)Agree to prepare guidance material indicating that route optimization can be achieved in several ways and that no requirements will be mandated on the CN;
7)Definition of a security model is WGI work in progress.
.
4.3.2Daniel Medina presented WP7 "Impact of Home Agent (HA) based Global Mobility on the ATN IPv6 Address Allocation Plan" (including a companion presentation). The paper first explains how Global Mobility management approaches have evolved from BGP routing based to anchor point (HA) based. The impact of the HA approach on the address allocation plan is discussed. A number of considerations are raised in the paper, leading to a proposal for the airborne address allocation plan shown in the figure below.
Proposed Airborne IPv6 Address Allocation Strategy
Note.- Colors indicate safety-related (red) vs non-safety-related (blue) airborne equipment address allocation. AAC may fall into any of these categories.
In particular:
a. ICAO reserves a specific block for airborne addressing, and allocates sub-blocks from it to ICAOStates and ACSPs (or airlines).
b. Different Mobile Network Prefixes (MNPs) are used for the different airborne domains (ATS, AOC, AAC, APC). The APC domain may have more than one MNP, e.g. one for IFE systems and one for passenger owned devices.
The paper recommends that HAs for a specific MNP be deployed by the network entity (organization) that assigns the MNP.
In addition, the paper recommends inclusion of material on the Global HAHA protocol (draft-thubert-mext-global-haha-00) into the Guidance Material for CSPs.
4.3.3TomMcParland presented Working Paper 08, Updated Mobility Management Requirements. This paper is an update of working paper 8 from the 5th meeting of Working Group I. Several changes suggested during the 5th meeting were incorporated. In addition this paper adopts Mobile IPv6 as the baseline mobility management protocol. The proposed approach to local mobility in this paper was to make node-based and network-based local mobility management optional, i.e., “may” statements in Section 1 of the Doc 9896. For node-based mobility management, Mobile IPv6 would be required. For network-based there was no specifc requirement such as PMIP. For global mobility management, Mobile IPv6 was required. After considerable discussion it was decided to only have a requirement for a Mobile Node to implement Mobile IPv6 in accordance with RFC 3775. This was the major recommendation of Working Paper 03. The remaining portions of the proposed section would be incorporated in Guidance.
.
4.3.4Vic Patel presented Working Paper 09, Updated Security Requirements. This paper is an update of working paper 9 from the 5th meeting of Working Group I. It incorporates changes suggested during the 5th meeting and incorporates chages based on the adoption of Mobile IPv6 for air-ground mobility. During the discussion it was decided to add a clarification regarding the difference between provisions that were mandatory to implement but optional for use. It was agreed to provide a reference to the Certificate Practice being developed by the Airline Transport Association (ATA) Digital Security Working Group (DSWG). This was based on IP 03. It was also agreed to clarify that requirement 2.6.2.4.3 was intended for bandwidth-limited environments. Vic Patel took an action to make these updates.
4.3.5Tom McParland presented Informaton Paper 02, Application of Mobile IP (MIP) and Proxy Mobile IP (PMIP) Security. This paper summarizes the approaches and identifies the main RFCs used for authentication of MIP and PMIP signaling and for key establishment and entity authentication of MIP and PMIP.
4.3.6Tom McParland presented Informaton Paper 04, IP Mobility Management in 3GPP2 Networks. The paper first provides a generic network reference architecture which describes the general use of MIP and PMIP mobility management. The paper then describes the architecture and operation of the 3GPP2 Converged Access Network as specified in the 3GPP2 X.S0054 series of specifications.
4.4Discuss status of Application work;
4.4.1Greg Saccone presented WP10, IPS DS Interface. The paper described the latest version of the proposed new dialogue service that allows legacy ATN applications to run over the IPS protocol stack, including use of either TCP or UDP. An initial header format, called the ATNPKT, was proposed for mapping all of the current ATN OSI dialogue service parameters to corresponding parameters in the header. This header would be used for both TCP and UDP operation. Questions were raised if all of the components were necessary, e.g. the Called and Calling Peer IDs. It was explained that the intent was to allow all current parameters to be exchanged as currently specified in the application sections; if some are no longer necessary (i.e. another way can be found to provide the same parameters to each peer without physically sending them over the link), then they can be removed. However, including them all allows a definitive 1-1 mapping of the parameters without having to resort to local means to provide the values.
Another question was whether the header could be encapsulated in the same kind of simple format as contained in RFC1006/2126. This is possible, although there would be a need for the same type of header format contained within the message of the simplified header.
UDP operation was also discussed. Since many of the ATN services are inherently connection-oriented, and application state checking is done based on the processing of the DS primitives received, there would need to be a way to indicate which primitive was being sent. TCP is able to do this by mapping to the TCP services to the appropriate DS primitive; however UDP cannot since it is inherently stateless. Therefore a DS primitive data field has been added to the ATNPKT header in order to allow unambiguous determination of the type of DS primitive that is supposed to be emulated. A state table for both TCP and UDP operation was given, based in part on the assumption of the availability of the dialogue service information.
There are still additional details necessary to be defined, including port numbers (per application or a single one, as in RFC1006), whether an application needs to give an indication of the type of transport service it wants to use (UDP/TCP), multiple instantiation guidance, and other information that may be helpful to include in the header (e.g. specific flight information, or information on the type of data being carried). The CM ASN.1 will also need to be updated and included in the manual. These will be addressed for the next meeting.
The group agreed to have the material in this WP form the basis of the application parts of the manual.
4.5New Papers
4.5.1The Secretariat presented WP05, IANA response. The WP is an email response from IANA making a request to meet at a future date, once the 5 questions listed below are addressed;
(1) the estimated number of aircraft to which allocations of IPv6 addresses and AS Numbers are planned;
(2) the list of nations involved;
(3) the number of AS Numbers needed and the technical justification to support these projected numbers;
(4) a preliminary network topology plan that includes expected internal and end-user site usage (which, for example, could be broken down by the number of /56s or /48s).
.
Terry Davis, generated an Information paper which will be used to initiate correspondence and dialog with IANA relative to the request of IPv6 Address block and agenda items for a future meeting.
4.5.2Eivan Cerasi presentsIP02 which presents the Pan-European Network Services call for tender initiative which is open for submissions until 31st March 2008. The procured services involve IPv4 and IPv6 services for CFMU, EAD and ANSPs.
4.5.3Terry Davis presented IP05, Draft Agenda for IANA Meeting. The agenda is a working plan for discussion of topics, and answers to IANA requests.
5.AGENDA ITEM 5: FUTURE WORK FOR NEXT MEETING
5.1The future work plans, and recommendations are listed below.
The material to be developed for Manual for ATN using IPS Standards and Protocols Doc 9896:
- ATN/IPSRequirements for VoIP and Mobility
- ATNIPSRequirements on Detailed Technical Specifications
- ATN IPS Guidance Material
- ATN IPS Addressing Plan
- ATN IPS Security Material
- ATN/IPS accommodations for Legacy Applications
6.AGENDA ITEM 6: COORDINATION WITH OTHER GROUPS
6.1WG-I Meeting are being planned to occur in conjunction with regional AMHS Workshop meeting to facilitate coordination.
7.AGENDA ITEM 7: NEW BUSINESS
7.1 The tentative meeting schedule for 2008 is listed below, please note that all meeting are in Montreal, unless specifically identified as other:
- June 2-6 Montreal
- August 25-29Montreal
- October 27-31Montreal
END
WG_I_6_Meeting Report mar_17_2008Page1
Report of ACP, WG-I-06 Meeting
(Montreal, 17-20 March 2008)
APPENDIX A
ACP WGI AGENDA
AERONAUTICAL COMMUNICATION PANEL
Working Group I – Internet Protocol Suite
6th Meeting
17th – 20th March 2008
Montreal, Canada
Agenda
- Meeting Organizational Issues
- Approval of the Agenda
- Discuss 5th WG-I Meeting
- Discuss Action Items from WG-I Meeting
- Review WG-I 5th Meeting 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***
WG_I_6_Meeting Report mar_17_2008Page1
Report of ACP, WG-I-06 Meeting
(Montreal, 17-20 March 2008)
APPENDIX B WORKING PAPER LIST
WG-I – Internet Protocol Suite
6th Meeting
17th – 20th March 2008
Montreall, Canada
WP No. / Agenda Item / Presenter / WP TitleWP0601 / Rapporteur / Invitation / Nomination form / Draft Agenda
WP0602 / Eivan Cerasi / Proposed definition of IPS Classes of Service
WP0603 / 4.3 / Eivan Cerasi / Air/Ground ATN/IPS
WP0604 / 3.1 / Rapporteur / Draft Report ACP WG-I/5 Meeting
WP0605 / 4.5 / Secretary / IANA Response
WP0606 / 4.1 / Rapporteur / Draft "Manual for the ATN using IPS Standards and Protocols (Doc 9896)"
WP0607 / 4.3 / Daniel Medina, Serkan Ayaz and Christian Bauer / Impact of Home Agent (HA) based Global Mobility on the ATN IPv6 Address Allocation Plan (paper+presentation)
WP0608 / 4.3 / Vic Patel & Tom McParland / Updated Mobility Management Requirements for the “Manual for the ATN using IPS Standards and Protocols”
WP0609 / 4.3 / Vic Patel & Tom McParland / Updated Security Requirements for the “Manual for the ATN using IPS Standards and Protocols”
WP0610 / 4.4 / Greg Saccone / IPS Dialogue Service Interface Update
WP0611 / 4.2 / Jacques Mathot and Eivan Cerasi / Guidance material for OLDI/FMTP
WP0612 / 3.1 / Rapporteur / Updated WP4 containing the Approved Report of ACP WG-I/5 Meeting (same as on webpage for WG-I/5)
IP0601 / 4.5 / Eivan Cerasi / Pan-European Network Service (PENS)Leaflet
IP0602 / 4.3 / Vic Patel & Tom McParland / Application of Mobile IP and Proxy Mobile IP Security
IP0603 / 4.3 / Patrick Patterson / PKI deployment in the Aerospace Industry
IP0604 / 4.3 / Tom McParland / IP Mobility Management in 3GPP2 Networks
IP0605 / 4.5 / Terry Davis / ICAO – ARIN IPv6 Address Allocation
WG_I_6_Meeting Report mar_17_2008Page1
APPENDIX C LIST OF ATTENDEES
ACP WGI-6 – Montreal, Canada – 17th – 20th March 2008
LIST OF ATTENDEES
ICAO ACP-WG I - Internet Protocol Suite (IPS): Meeting 6, Montreal, Canada
NAME / ORGANIZATION NAME / ADDRESS / PHONE / FAX / E-MAILColon, 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 /
Davis, Terry / The Boeing Company / The Boeing Company
PO Box 3707 MC 8R079
SeattleUSA /
Olive, Mike / Honeywell International Inc. / 7000 Columbia Gateway Drive
Columbia
Maryland; USA / +1 410 964 7342
+1 410 964 7322 /
BHARJ, Danny / SITA / 770 Sherbroke West, MontrealQC, Canada H42 1M1 / +1-514-982-4374 /
Patterson, Patrick / Carillon Information Security / 514-485-0789
F 450-458-4747
C 514-994-8699 /
Cardwell, Brian
Patel, Vidyut / FAA/USA / FAA Technical Ctr. AJP-7140 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 /
Medina, Daniel / German Aerospace Centre (DLR) / Institute of Communications and Navigation
Oberpfaffenhofen
82234 Wessling Germany / +49 81 5328 2836
Fax
+48 81 5328 1871 /
Cerasi, Evian / EUROCONTROL / EUROCONTROL DAP/CSP
96 Ruede la Fusee
B-1130
Brussels, Belgium / +3227293791 /
Page 1 of 12