rfc5447.Diameter Mobile IPv6 Support for Network A

NetworkWorkingGroupJ.Korhonen,Ed.RequestforComments:5447NokiaSiemensNetworksCategory:StandardsTrackJ.BournelleOrangeLabsH.TschofenigNokiaSiemensNetworksC.PerkinsWiChorusK.ChowdhuryStarentNetworksFebruary2009DiameterMobileIPv6:SupportforNetworkAccessServertoDiameterServerInteractionStatusofThisMemoThisdocumentspecifiesanInternetstandardstrackprotocolfortheInternetcommunity,andrequestsdiscussionandsuggestionsforimprovements.PleaserefertothecurrenteditionoftheInternetOfficialProtocolStandards(STD1)forthestandardizationstateandstatusofthisprotocol.Distributionofthismemoisunlimited.CopyrightNoticeCopyright(c)2009IETFTrustandthepersonsidentifiedasthedocumentauthors.Allrightsreserved.ThisdocumentissubjecttoBCP78andtheIETFTrust’sLegalProvisionsRelatingtoIETFDocuments()ineffectonthedateofpublicationofthisdocument.Pleasereviewthesedocumentscarefully,astheydescribeyourrightsandrestrictionswithrespecttothisdocument.AbstractAMobileIPv6noderequiresahomeagentaddress,ahomeaddress,andasecurityassociationwithitshomeagentbeforeitcanstartutilizingMobileIPv6.RFC3775requiresthatsomeoralloftheseparametersbestaticallyconfigured.MobileIPv6bootstrappingworkaimstomakethisinformationdynamicallyavailabletothemobilenode.AnimportantaspectoftheMobileIPv6bootstrappingsolutionistosupportinterworkingwithexistingAuthentication,Authorization,andAccounting(AAA)infrastructures.ThisdocumentdescribesMIPv6bootstrappingusingtheDiameterNetworkAccessServertohomeAAAserverinterface.Korhonen,etal.StandardsTrack[Page1]RFC5447DiameterMIPv6NAS-to-HAAAInteractionFebruary2009TableofContents1.Introduction.........................32.TerminologyandAbbreviations................33.Overview...........................54.Commands,Attribute-ValuePairs,andAdvertisingApplicationSupport.....................64.1.AdvertisingApplicationSupport.............64.2.Attribute-ValuePairDefinitions.............64.2.1.MIP6-Agent-InfoAVP.................64.2.2.MIP-Home-Agent-AddressAVP..............74.2.3.MIP-Home-Agent-HostAVP...............74.2.4.MIP6-Home-Link-PrefixAVP..............84.2.5.MIP6-Feature-VectorAVP...............85.Examples...........................105.1.HomeAgentAssignmentbytheNAS.............105.2.HomeAgentAssignmentbytheDiameterServer.......115.3.HomeAgentAssignmentbytheNASorDiameterServer...116.Attribute-ValuePairOccurrenceTables............127.IANAConsiderations.....................137.1.RegistrationofNewAVPs.................137.2.NewRegistry:MobilityCapability............138.SecurityConsiderations...................149.Acknowledgments.......................1410.References..........................1510.1.NormativeReferences...................1510.2.InformativeReferences..................15Korhonen,etal.StandardsTrack[Page2]RFC5447DiameterMIPv6NAS-to-HAAAInteractionFebruary20091.IntroductionTheMobileIPv6(MIPv6)specification[RFC3775]requiresamobilenode(MN)toperformregistrationwithahomeagent(HA)withinformationaboutitscurrentpointofattachment(care-ofaddress).TheHAcreatesandmaintainsthebindingbetweentheMN’shomeaddressandtheMN’scare-ofaddress.InordertoregisterwithanHA,theMNneedstoknowsomeinformation,suchasthehomelinkprefix,theHAaddress,thehomeaddress(es),thehomelinkprefixlength,andsecurity-association-relatedinformation.Theaforementionedinformationmaybestaticallyconfigured.However,staticprovisioningbecomesanadministrativeburdenforanoperator.Moreover,itdoesnotaddressloadbalancing,failover,opportunistichomelinkassignment,orassignmentoflocalHAsincloseproximitytotheMN.Also,theabilitytoreacttosuddenenvironmentalortopologicalchangesisminimal.Staticprovisioningmaynotbedesirable,inlightoftheselimitations.DynamicassignmentofMIPv6homeregistrationinformationisadesirablefeatureforeaseofdeploymentandnetworkmaintenance.Forthispurpose,theAAAinfrastructure,whichisusedforaccessauthentication,canbeleveragedtoassignsomeorallofthenecessaryparameters.TheDiameterserverintheAccessServiceProvider’s(ASP’s)orMobilityServiceProvider’s(MSP’s)networkmayreturntheseparameterstotheAAAclient.Regardingthebootstrappingprocedures,theAAAclientmighteitherbetheNetworkAccessServer,incaseoftheintegratedscenario,ortheHA,incaseofthesplitscenario[RFC5026].Thetermsintegratedandsplitaredescribedinthefollowingterminologysectionandwereintroducedin[RFC4640]and[AAA].2.TerminologyandAbbreviationsThekeywordsMUST,MUSTNOT,REQUIRED,SHALL,SHALLNOT,SHOULD,SHOULDNOT,RECOMMENDED,MAY,andOPTIONALinthisdocumentaretobeinterpretedasdescribedinRFC2119[RFC2119].Generalmobilityterminologycanbefoundin[RFC3753].Thefollowingadditionaltermsareeitherborrowedfrom[RFC4640]or[RFC5026]orareintroducedinthisdocument:AccessServiceAuthorizer(ASA):AnetworkoperatorthatauthenticatesanMNandestablishestheMN’sauthorizationtoreceiveInternetservice.Korhonen,etal.StandardsTrack[Page3]RFC5447DiameterMIPv6NAS-to-HAAAInteractionFebruary2009AccessServiceProvider(ASP):AnetworkoperatorthatprovidesdirectIPpacket-forwardingtoandfromtheMN.MobilityServiceAuthorizer(MSA):AserviceproviderthatauthorizesMIPv6service.MobilityServiceP