ARINC 664P3-2-2009协议完整版本

AIRCRAFTDATANETWORKPART3

INTERNET-BASEDPROTOCOLSANDSERVICES

ARINCSPECIFICATION664P3-2

PUBLISHED:February16,2009

ANDOCUMENT

PreparedbyAEECPublishedby

AERONAUTICALRADIO,INC.

2551RIVAROAD,ANNAPOLIS,MARYLAND21401-7435

DISCLAIMER

THISDOCUMENTISBASEDONMATERIALSUBMITTEDBYVARIOUSPARTICIPANTSDURINGTHEDRAFTINGPROCESS.NEITHERAEEC,AMC,FSEMCNORARINCHASMADEANYDETERMINATIONWHETHERTHESEMATERIALSCOULDBESUBJECTTOVALIDCLAIMSOFPATENT,COPYRIGHTOROTHERPROPRIETARYRIGHTSBYTHIRDPARTIES,ANDNOREPRESENTATIONORWARRANTY,EXPRESSORIMPLIED,ISMADEINTHISREGARD.

ARINCINDUSTRYACTIVITIESUSESREASONABLEEFFORTSTODEVELOPANDMAINTAINTHESEDOCUMENTS.HOWEVER,NOCERTIFICATIONORWARRANTYISMADEASTOTHETECHNICALACCURACYORSUFFICIENCYOFTHEDOCUMENTS,THEADEQUACY,MERCHANTABILITY,FITNESSFORINTENDEDPURPOSEORSAFETYOFANYPRODUCTS,COMPONENTS,ORSYSTEMSDESIGNED,TESTED,RATED,INSTALLEDOROPERATEDINACCORDANCEWITHANYASPECTOFTHISDOCUMENTORTHEABSENCEOFRISKORHAZARDASSOCIATEDWITHSUCHPRODUCTS,COMPONENTS,ORSYSTEMS.THEUSEROFTHISDOCUMENTACKNOWLEDGESTHATITSHALLBESOLELYRESPONSIBLEFORANYLOSS,CLAIMORDAMAGETHATITMAYINCURINCONNECTIONWITHITSUSEOFORRELIANCEONTHISDOCUMENT,ANDSHALLHOLDARINC,AEEC,AMC,FSEMCANDANYPARTYTHATPARTICIPATEDINTHEDRAFTINGOFTHEDOCUMENTHARMLESSAGAINSTANYCLAIMARISINGFROMITSUSEOFTHESTANDARD.

THEUSEINTHISDOCUMENTOFANYTERM,SUCHASSHALLORMUST,ISNOTINTENDEDTOAFFECTTHESTATUSOFTHISDOCUMENTASAVOLUNTARYSTANDARDORINANYWAYTOMODIFYTHEABOVEDISCLAIMER.NOTHINGHEREINSHALLBEDEEMEDTOREQUIREANYPROVIDEROFEQUIPMENTTOINCORPORATEANYELEMENTOFTHISSTANDARDINITSPRODUCT.HOWEVER,VENDORSWHICHREPRESENTTHATTHEIRPRODUCTSARECOMPLIANTWITHTHISSTANDARDSHALLBEDEEMEDALSOTOHAVEREPRESENTEDTHATTHEIRPRODUCTSCONTAINORCONFORMTOTHEFEATURESTHATAREDESCRIBEDASMUSTORSHALLINTHESTANDARD.

ANYUSEOFORRELIANCEONTHISDOCUMENTSHALLCONSTITUTEANACCEPTANCETHEREOF“ASIS”ANDBESUBJECTTOTHISDISCLAIMER.

Thisdocumentispublishedinformationasdefinedby15CFRSection734.7oftheExportAdministrationRegulations(EAR).Aspubliclyavailabletechnologyunder15CFR74.3(b)(3),itisnotsubjecttotheEARanddoesnothaveanECCN.Itmaybeexportedwithoutanexportlicense.

©2009BYAERONAUTICALRADIO,INC.

2551RIVAROADANNAPOLIS,MARYLAND

21401-7435USA

ARINCSPECIFICATION664P3-2

AIRCRAFTDATANETWORKPART3

INTERNET-BASEDPROTOCOLSANDSERVICES

Published:February16,2009

PreparedbytheAEEC

Specification664P3

AdoptedbytheAEECExecutiveCommittee

October24,2001

SummaryofDocumentSupplements

Supplement

AdoptionDate

Published

Specification664P3-1

July15,2004

December22,2004

Specification664P3-2

April15,2008

February16,2009

AdescriptionofthechangesintroducedbyeachsupplementisincludedonGoldenrodpaperattheendofthisdocument.

FOREWORD

AeronauticalRadio,Inc.,theAEEC,andARINCStandards

ARINCorganizesaviationindustrycommitteesandparticipatesinrelatedindustryactivitiesthatbenefitaviationatlargebyprovidingtechnicalleadershipandguidance.Theseactivitiesdirectlysupportaviationindustrygoals:promotesafety,efficiency,regularity,andcost-effectivenessinaircraftoperations.

ARINCIndustryActivitiesorganizesandprovidesthesecretariatforinternationalaviationorganizations(AEEC,AMC,FSEMC)whichcoordinatetheworkofaviationindustrytechnicalprofessionalsandleadthedevelopmentoftechnicalstandardsforairborneelectronicequipment,aircraftmaintenanceequipmentandpracticesandflightsimulatorequipmentandusedincommercial,military,andbusinessaviation.TheAEEC,AMC,andFSEMCdevelopconsensus-based,voluntarystandardsthatarepublishedbyARINCandareknownasARINCStandards.TheuseofARINCStandardsresultsinsubstantialbenefitstotheaviationindustrybyallowingavionicsinterchangeabilityandcommonalityandreducingavionicscostbypromotingcompetition.

TherearethreeclassesofARINCStandards:

ARINCCharacteristics–Definetheform,fit,function,andinterfacesofavionicsandotherairlineelectronicequipment.ARINCCharacteristicsindicatetoprospectivemanufacturersofairlineelectronicequipmenttheconsideredandcoordinatedopinionoftheairlinetechnicalcommunityconcerningtherequisitesofnewequipmentincludingstandardizedphysicalandelectricalcharacteristicstofosterinterchangeabilityandcompetition.

ARINCSpecifications–Areprincipallyusedtodefineeitherthephysicalpackagingormountingofavionicsequipment,datacommunicationstandards,orahigh-levelcomputerlanguage.

ARINCReports–Provideguidelinesorgeneralinformationfoundbytheairlinestobegoodpractices,oftenrelatedtoavionicsmaintenanceandsupport.

ThereleaseofanARINCStandarddoesnotobligateanyorganizationorARINCtopurchaseequipmentsodescribed,nordoesitestablishorindicaterecognitionortheexistenceofanoperationalrequirementforsuchequipment,nordoesitconstituteendorsementofanymanufacturer’sproductdesignedorbuilttomeettheARINCStandard.

--`,`,,``,````,`,`,``,,`,`,`,``-`-`,,`,,`,`,,`

InordertofacilitatethecontinuousproductimprovementofthisARINCStandard,twoitemsareincludedinthebackofthisvolume:

AnErrataReportsolicitsanycorrectionstothetextordiagramsinthisARINCStandard.

AnARINCIAProjectInitiation/Modification(APIM)formsolicitsanyrecommendationsforadditionofsubstantivematerialtothisvolumewhichwouldbethesubjectofanewSupplement.

ii

ARINCSPECIFICATION664P3TABLEOFCONTENTS

INTRODUCTION 1

PurposeofDocument 1

Scope 1

DocumentOrganization 2

AircraftDataNetwork 2

Internet-BasedProtocolsandServices 3

RelatedDocuments 3

RelationshipofthisDocumenttoOtherARINCStandards 3

RelationshiptoIndustryStandards 4

RTCAandEUROCAEDocuments 5

--`,`,,``,````,`,`,``,,`,`,`,``-`-`,,`,,`,`,,`

IEEEandANSIDocuments 5

ISOandIECDocuments 5

DocumentPrecedence 5

RegulatoryApproval 6

INTERNET-BASEDSERVICES 7

Introduction 7

InteroperabilityIssues 7

ServicestoProtocolsMapping 8

PhysicalandDataLinkLayer 9

Broadcast 9

Multicast 9

NetworkLayer 10

DataTransport 10

MapIPAddresstoIEEE802.3MAC 10

MapHostNametoIPAddress 11

NetworkDiagnostics 11

NetworkConfiguration 11

Routing 12

FileTransfer 12

RemoteUserAccess 12

NetworkManagement 12

SimpleRemoteDataAccess 12

ARINC615ADataLoader 12

INTERNET-BASEDPROTOCOL 13

Introduction 13

iii

ARINCSPECIFICATION664P3TABLEOFCONTENTS

SecurityConsiderations 13

Layer7(Application)andLayer5(Session)Protocols. 14

FileTransferProtocol 14

TrivialFileTransferProtocol 14

DataLoader-TrivialFileTransferProtocol 14

Telnet 14

SecureShell 14

HypertextTransferProtocol 15

DomainNameSystem 15

SimpleNetworkManagementProtocol 15

Netconf 17

TransportLayerSecurity 18

DynamicHostConfigurationProtocol 18

Layer4(Transport)Protocols 18

TransmissionControlProtocol 19

UserDatagramProtocol 23

IP-RouterRequirements 25

Layer3(Network)Protocols 25

InternetProtocolVersion4(IPv4) 25

TimetoLive 30

MaximumTransmissionUnit 30

MeetGatewaySpecificationsifForwardingDatagrams 30

InternetGroupManagementProtocol 30

InternetControlMessageProtocol 31

InternetProtocolVersion6(IPv6) 31

IPv6InteroperabilitywithIPv4 33

SecurityArchitecturefortheInternetProtocol 33

Layer2(LinkLayer)Protocols 50

AddressResolutionProtocol 51

ReserveAddressResolutionProtocol 51

ATTACHMENTS

--`,`,,``,````,`,`,``,,`,`,`,``-`-`,,`,,`,`,,`

ExampleofanARINC664CompliantNetworkUsingIPv4ServicesImplementationConformanceStatement(SICS) 52

ExampleofanARINC664CompliantNetworkProtocolImplementationConformanceStatement(PICS) 53

iv

ARINCSPECIFICATION664P3TABLEOFCONTENTS

ExampleofanARINC664CompliantNetworkUsingIPv6ServicesImplementationConformanceStatement(SICS) 70

APPENDICES

Glossary 71

AcronymList 72

v

--`,`,,``,````,`,`,``,,`,`,`,``-`-`,,`,,`,`,,`

ARINCSPECIFICATION664,PART3–Page1

INTRODUCTION

PurposeofDocument

Scope

ThisdocumentspecifiesaprofileofInternetEngineeringTaskForce(IETF)standardprotocolsandservicesforuseonboardaircraft.ItistheintentofthisspecificationtodefinethefunctionalityofstandardInternetprotocolsandservicesinamannerthatallowsinteroperabilityofcomponentsconnectedtoonboarddatanetworkswhilesimultaneouslybeingtotallyindependentoffunctionality.Notallfunctionsofa“standard”CommercialOfftheShelf(COTS)implementationmaybeuseful,orappropriate,forallonboardnetworks.However,byimplementinga“propersubset”ofInternetstandardsthegoalofmaximuminteroperabilitybalancedwithcostofimplementationandcertificationcanbeachieved.

ThisspecificationisbasedonIETFRequestforComments(RFC).ApplicableRFCsusedinthisspecificationarelistedinSection1.4.Exceptwherenecessary,informationalreadycontainedinanyRFCisnotduplicatedwithinthisspecification,anditisrecommendedthatthereaderobtainacopyoftheapplicableRFCwhennecessary.

Thisspecificationdefinesthebroadcharacteristicsoftwotypesofnetworks:

CompliantAircraftDataNetwork,referredtoasCompliantNetwork.

ProfiledAircraftDataNetwork,referredtoasProfiledNetwork.

Insummary,aCompliantAircraftDataNetworkoperatesfullywithintheapplicableInternetspecificationsasdefinedintherelevantIETFRFCs.AProfiledAircraftDataNetworkisoneinwhichoneormoreindustrystandardprotocolshavebeenextendedtoaddressuniqueproblemsoftheavionicsindustry.

InteroperabilitybetweenaCompliantNetworkandaProfiledNetwork,orbetweenProfiledNetworksystemswithdifferentcharacteristics,isnotassuredwithouttheuseofanintermediatesystem,suchasarouterorgateway.Inaddition,aProfiledNetworkmayprovidesomecharacteristicstypicalofaCompliantNetworktoaUserApplication(UA);butthefundamentalorunderlyingbehaviorofthenetworkmaynotbeidentical.

COMMENTARY

--`,`,,``,````,`,`,``,,`,`,`,``-`-`,,`,,`,`,,`

Forexample,aUAneednotknowthenumericaladdressofatargetfunction,ratherthenameofthetargetfunctioncanbesent“down”intotheprotocolstackwhereitisresolvedintotheappropriatesetofnumericaladdresses.InaCompliantNetwork,thisresolutiontakesplacethroughtheuseofinternallook-uptablesandthroughdomainnameservers(DNS)onthenetworkiftheinformationisnotfoundinthelook-uptables.InaProfiledNetworkwhereresolutionisperformedthroughtheuseofonlystatictables,makingaDNSunnecessary.Thatis,ifthetargetnameisnotfoundinthepre-configuredtables,thenthedatacannotbesent.Directlyinterconnectingthesetwodevicesonthesamenetworkshouldnotresultintheabilitytoexchangedatauntilthenetworkadministratorappropriatelyconfiguresbothdevices.BothCompliantandProfiledNetworksprovidethesameservicetotheUA.However,the

ARINCSPECIFICATION664,PART3–Page2

INTRODUCTION

implementationisdifferentandhastobeaccommodatedbeforetheycaninteroperate.

ThisspecificationprovidesafunctionsimilartoRFC-1122,thatis,aspecificationthatisintendedtosupportandfacilitateinteroperabilityofend-systemsconnectedbystandardInternetbasedprotocols.

CompliantAircraftDataNetworksshouldbeinfullcompliancewithIETFRFCsapplicabletotheirpurpose.Suchnetworksarenotaddressedfurtherinthisspecification.

--`,`,,``,````,`,`,``,,`,`,`,``-`-`,,`,,`,`,,`

ProfiledAircraftDataNetworksshouldimplementatleasttheminimumsetoffeatures,services,andprotocolscontainedinthisspecification.IndividualimplementationsofsystemsandnetworksmaychoosetoincludeadditionalCompliantNetworkfunctions,services,andprotocolswhichextendthedefinitionoftheminimumsetbutwhicharenotintotalcompliancewithapplicableInternetStandardsandRFCs.Withintheconstraintsdiscussedinthisspecification,aircraftdatanetworkinstantiationsthatimplementthedefinedminimumsetoffeatures,services,andprotocolscontainedinthisspecificationshouldinteroperatewithintheconstraintsdefinedinthisspecification.Whenproperlyconfigured,aminimumaircraftdatanetworkshouldinteroperatewithsystemsthatcontainadditionalfeaturesorcharacteristics.However,thebehavioroftheminimumnetworksmaycauseproblemswiththe“extended”networks,iftheextendedorCompliantNetworkcannotaccommodatetherestrictedsetoffunctions,services,andprotocolsimplementedintheminimumsystem.

DocumentOrganization

AircraftDataNetwork

TheAircraftDataNetworkspecificationconsistsofmultipleparts,eachpartspecifyingdifferentlayersoftheOpenSystemInterconnectReferenceModel(OSIRM)orotherinterfacestotheaircraftdatanetwork.Thepartsofthisspecificationarelistedasfollows:

Part1-SystemsConceptsandOverview

Part2-EthernetPhysicalandDataLinkLayerSpecification

Part3-Internet-BasedProtocolsandServices

Part4-Internet-BasedAddressStructureandAssignedNumbers

Part5-NetworkDomainCharacteristicsandFunctionalElements

Part6-Reserved

Part7-AvionicsFull-DuplexSwitched(AFDX)EthernetNetwork

Part8-InteroperationwithNon-IPProtocolsandServices

Systemconsiderationsandothercommunicationnetworktopicsarespecifiedinotherparts.Eachpartisindependentandshouldevolveonitsowntimeline.

ARINCSPECIFICATION664,PART3–Page3

INTRODUCTION

Internet-BasedProtocolsandServices

Thisspecificationisorganizedasfollows:

Chapter1.0,Introduction,providesanintroductiontothisspecification.

Chapter2.0,Internet-basedServices,providesadescriptionofInternet-basedservicesandtheirapplicationtoaProfiledNetwork.

Chapter3.0,Internet-basedProtocols,providesadescriptionofInterned-basedprotocolsandtheirapplicationtoaProfiledNetwork.

Attachment1providesaServicesImplementationConformanceStatement(SICS)asanindependenttemplateforasystemintegratortousetodocumentcompliancewiththeservicesthattheirequipmentsupportsandtheprotocol(s)usedtosupportthoseservices.

Attachment2providesaProtocolImplementationConformanceStatement(PICS)asanindependenttemplateforasystemsintegratortousetodocumentcompliancewiththeprovisionsofthisspecificationforaProfiledNetwork.

ThisspecificationassumestheorganizationillustratedinFigure1.3.2.

NETWORKLAYERN

USER

NETWORKLAYERN-1

NETWORKLAYERN

USER

NETWORKLAYERN-1

PROTOCOLS

SERVICES SERVICES

PROTOCOLS

SERVICES SERVICES

PROTOCOLS

Figure1.3.2–RelationshipbetweenProtocolsandServices

Servicesareusedtoprovideinformationandcontrolbetweendifferentlocalentities.Protocolsareusedtoexchangeinformationandcontrolbetweendifferentremotepeerentities.

RelatedDocuments

RelationshipofthisDocumenttoOtherARINCStandards

OtherARINCdocumentsthatarerelatedtothisspecificationarelistedbelow.Whenavionicssystemsandsubsystemsaredesignedtousethecapabilitiesprovidedbythisspecification,theyshouldincorporatetheprovisionsofthisspecificationbyreference.Referencestothisspecificationshouldassumetheapplicationofthemostrecentversion.

--`,`,,``,````,`,`,``,,`,`,`,``-`-`,,`,,`,`,,`

--`,`,,``,````,`,`,``,,`,`,`,``-`-`,,`,,`,`,,`

ARINCSPECIFICATION664,PART3–Page4

INTRODUCTION

ARINCSpecification615A:SoftwareDataLoaderUsingEthernetInterface

ARINCSpecification646:EthernetLocalAreaNetwork(ELAN)

ARINCSpecification656:AvionicsInterfaceDefinitionforFlightManagementandCommunicationManagementFunctions.

ARINCCharacteristic763:NetworkServerSystem

RelationshiptoIndustryStandards

ThisspecificationfocusesontheprotocolsandservicesprovidedbytheOpenSystemInterconnectReferenceModel(OSIRM)inLayers3(IP)and4(TransmissionControlProtocol/UserDatagramProtocol(TCP/UDP))aswellassupportingservicesandprotocolsassociatedwiththeselayers.AdditionalinformationontheOSIRMisprovidedinARINCSpecification664,Part1.

Table1.4.2identifiesreferencedRFCsinthisspecification,unlessotherwisenoted:

Table1.4.2–ReferencedRFCs

RFCNo.

RFCTitle

RFC-768

UserDatagramProtocol

RFC-792

InternetControlMessageProtocol

RFC-793

TransmissionControlProtocol

RFC-826

AnEthernetAddressResolutionProtocol

RFC-854

TelnetProtocolSpecificationSeealsoRFC-855,RFC-856,RFC-857,RFC-858,RFC-859,RFC-860,RFC-861

RFC-903

AReverseAddressResolutionProtocol

RFC-950

InternetStandardSubnettingProcedure

RFC-951

BootstrapProtocol(BOOTP)

RFC-959

FileTransferProtocol(FTP)

RFC-1034

DomainNames-ConceptsandFacilities

RFC-1035

DomainNames-ImplementationandSpecification

RFC-1042

AStandardfortheTransmissionofIPDatagramsoverIEEE802NetworksSeealsoRFC-894

RFC-1112

HostExtensionsforIPMulticasting

RFC-1122

RequirementsforInternetHosts--CommunicationLayers

RFC-1155

StructureandIdentificationofManagementInformationforTCP/IP-basedInternets

RFC-1157

ASimpleNetworkManagementProtocol(SNMP)

RFC-1212

ConciseMIBDefinitions

RFC-1213

ManagementInformationBaseforNetworkManagementofTCP/IP-basedinternets:MIB-II

RFC-1215

AConventionforDefiningTrapsforusewiththeSNMP

RFC-1350

TheTFTPProtocol(Revision2)SeealsoRFC-2347,RFC-2348,RFC-2349

RFC-1908

CoexistencebetweenVersion1andVersion2oftheInternet-standardNetworkManagementFramework

RFC-1983

InternetUsers'Glossary

RFC-2131

DynamicHostControlProtocol–SeealsoRFC-2132

RFC-2236

InternetGroupManagementProtocol,Version2

RFC-2246

TheTLSProtocol

RFC-2616

HypertextTransferProtocol--HTTP/1.1

RFC-4741

NETCONFConfigurationProtocol

--`,`,,``,````,`,`,``,,`,`,`,``-`-`,,`,,`,`,,`

ARINCSPECIFICATION664,PART3–Page5

INTRODUCTION

AlthoughRFC-1983,InternetGlossary,isnotanormativestandard,itprovidesadefinitionoftermsusedintheRFCsandisaveryusefulreference.

RFCsareinthepublicdomainandareavailableontheInternetatthefollowingURL:

RTCAandEUROCAEDocuments

ThefollowingRTCAandEUROCAEdocumentspertaintothisspecification:

RTCA,DO-178B,SoftwareGuidelines

IEEEandANSIDocuments

IEEEdevelopsstandardsforanumberofcommercialindustries,includingthecomputerandtelecommunicationsindustries.SomeofthesestandardsaresharedwithAmericanNationalStandardsInstitute(ANSI).Onoccasion,thesestandardsareendorsedasinternationalstandardsundertheISOandInternationalElectrotechnicalCommittee(IEC)standardizationprogram.ThefollowinglistofIEEEandANSIdocumentspertaintothisspecification:

IEEEStd802.3,2000Edition,InformationTechnology-Telecommunicationsandinformationexchangebetweensystems-LocalandMetropolitanareanetworks-SpecificRequirements-Part3:CarrierSenseMultipleAccesswithCollisionDetection(CSMA/CD)AccessMethodandPhysicalLayerSpecifications

IEEEStd802.2,1998Release,alsoANSIStd802.2,Release1998,InformationTechnology-Telecommunicationsandinformationexchangebetweensystems-LocalandMetropolitanareanetworks-SpecificRequirements-Part2:LogicalLinkControl

IEEEStd802,Release1990,IEEEStandardsforLocalandMetropolitanAreaNetworks:OverviewandArchitecture

IEEEStandard802.3,2000Edition,isconsideredanintegralpartofthisspecificationandisconsideredrequiredreading.Inthisdocument,whenreferencingthisstandard,thetitleisshortenedtosimply“IEEE802.3.”AccesstoIEEE802.3maybeobtainedthroughtheInternetatthefollowingURL:

ANSIX3.263,1995Edition,isanintegralpartofIEEE802.3;itspecifiesthe100BASE-TXPMDandchannelperformancerequirements.Itshouldalsobeconsideredrequiredreading.Inthisdocument,whenreferencingthisstandard,thetitleisshortenedtosimply“ANSIX3.263.”

ISOandIECDocuments

NoISOorIECdocumentsarespecificallyreferencedwithinthisspecification.

DocumentPrecedence

ThisspecificationisbasedontheIETFRFCs.ThephilosophybehindthedevelopmentofthisspecificationistomakechangestotheprovisionsofIETFRFCsonlywhentheaeronauticalenvironmentoruser/regulatoryrequirementconflictswiththerequirementofIETFRFCs,orwhenitisnecessarytoremoveambiguitybyrestrictingtheoptionsavailabletoimplementers.Thecontentsofthisspecification

ARINCSPECIFICATION664,PART3–Page6

INTRODUCTION

arelimitedtodescribingthesechangesandoptionrestrictions.IncaseofaconflictbetweenthisspecificationandtheapplicableRFCs,ISOandIEEEstandards,thisspecificationshouldhaveprecedence.

RegulatoryApproval

Implementationofthisstandardshouldmeetallapplicableregulatoryrequirements.Manufacturersareurgedtoobtainallnecessaryinformationforsuchregulatoryapproval.Thisinformationisnotcontainedinthisspecification,norisitavailablefromARINC.

ARINCSPECIFICATION664,PART3–Page7

INTERNET-BASEDSERVICES

Introduction

Thisspecificationdifferentiatesbetween“service”and“protocol.”Internet-basedservicesdescribewhatfunctionalityisprovidedbythenetwork.Internet-basedprotocolsdescribehowthatfunctionalityisimplemented.Thereisnoauthoritativelistofinternet-basedservicesbecausetheengineerswhohavecreatedtheinternetservicesandprotocolshaveconcentratedondefiningtheprotocolsandhavenotformallyspecifiedtheservicesprovidedbythoseprotocols.

Servicesdonotnecessarilyrequireanetwork-basedprotocoltoimplementthem.ThisdocumentusesthenameVirtualInternetProtocol(VIP)todenoteavirtualprotocol,i.e.anabsenceofanetwork-basedprotocol,toprovideaservice.Thereareseveralservicesthatcanbeimplementedeithervianetworkcommunicationstoaremotehostorentirelywithinthelocalhost.Aclassicexampleofthisisthe“mapahostnametoanIPaddress”(i.e.gethostbyname())servicewhichcanbeprovidedviatheDomainNameService(DNS)protocolorlocallybyastaticlookuptable.

Thissectiondescribesprofilingofthenetworkservicesbyassumingthesystemintegratorincludesorexcludesservices.Thedetailedprofilingoccursattheprotocollevelfortheprotocolswhichimplementtheselectedservices.TheprofilingofprotocolsisaddressedinChapter3.0.

InteroperabilityIssues

Interoperabilityissuesshouldbeaddressedinacasebycasemanner.Thebestwaytodiscussinteroperabilityistoexaminetheconsequenceofeachdissimilarity.

Interoperabilityissuesarecreatedbytwotypesofdissimilarities:

Existencedissimilarity:Acommunicationserviceisprovidedinonehostandnotprovidedinanotherone,ordifferentprotocolsareusedtoprovidethesameservice.

Implementationdissimilarity:Acommunicationprotocolisprovidedinadifferentmannerintwodifferenthosts.

Asanexample,fragmentationisaservicethattheIPprovides.TheSystemIntegratormaydecidenottoimplementIPfragmentationinagivendomain.Inthiscase,aninteroperabilityissuemayberaisedwhenadevicesendsfragmenteddatagramstoanotherdevice,whichisunabletoreassemblethem.Also,aninteroperabilityissuemayariseifanapplicationexpectsthatthefragmentationserviceisperformedwhenitisnot.Re-hostingasoftwareapplicationfromonedomaintoanothermightcreatethissituation.

Anotherexampleisthe“mapanIPaddresstoan803.2MACaddress”service.ThisistraditionallyaccomplishedbytheARPprotocol.However,inahighlyconstrainednetworkthatlimitsbroadcastmessages,thiswouldbedoneusingstaticlookuptablesinthehost.

SincemanyprotocolsandservicesareoptionalintheRFCs,itispossibletohaveexistencedissimilaritiesinthecommercialworld,thatis,CompliantNetworks.

Likewise,manyoftheprotocoldefinitionsinRFCscontainoptionalparts,potentiallycausingimplementationdissimilarities.InProfiledNetworks,thepotentialnumberof

--`,`,,``,````,`,`,``,,`,`,`,``-`-`,,`,,`,`,,`

ARINCSPECIFICATION664,PART3–Page8

INTERNET-BASEDSERVICES

dissimilaritiesincreases.ItisrecognizedthattherearesetsofoptionsthatareroutinelyimplementedtoenhancetheinteroperabilityofhostsinaCompliantNetwork.Thesesetsofoptionscanbeabbreviatedtosimplifyagivenhost'ssoftware,butattheriskofcausinginteroperabilityproblems.

InCompliantNetworks,interoperabilityproblemsshouldbemanagedbythesystemintegrators.ThismanagementisexpectedtocontinueinProfiledNetworks.

Someservicesareimplementedwhileothersarenot.Bydefinition,inadomainwhereaCompliantNetworkisimplemented,thefullcompliancetoRFCsismandatedbycommonusage.Therefore,nofurtherdescriptionordiscussionofaCompliantNetworkisrequiredorprovidedinthisspecification.

InadomainwhereaProfiledNetworkistobeimplemented,thesystemintegratormayimplementaspecificserviceinawaywhichdoesnotcomplywiththeRFCs.Inthiscase,iftheimplementationofaserviceisdoneaccordingtospecialavionicsrulesdefinedbythisspecification,itshouldimplementatleasttheminimumprovisionsofthisspecification.Inotherwords,thereareonlytwowaystoimplementaservice:

InfullconformancewithRFCs,thuscreatingaCompliantAircraftDataNetwork.

Inconformancewiththisspecification,thuscreatingaProfiledAircraftDataNetwork.

ServicestoProtocolsMapping

TheservicesdiscussedinthissectionareidentifiedinTable2.3-1.Theservicesandprotocolsreferencedinthistableareprimarilyonesdiscussedinotherplacesandpartsofthisspecification.Therearemanyadditionalservicesandprotocolsthatareusefuland/orpermissible,butarenotreferencedinthetable.However,forthepurposeofdefiningaProfiledNetwork(seeARINC664,Part1,Section3.2),theprotocolsspecifiedinthetablearetheonlyonespermissibleforimplementingtheserviceslisted.

COMMENTARY

Duetothedynamicnatureofthecommercialnetworkingindustry,itislikelythatthistablewillrequirefrequentrevisiontoincludenewservice-protocolco