disrupt免费dns
免费dns 时间:2021-04-20 阅读:()
1464XLAT:BreakingFreeofIPv4Cameron.
Byrne@T-Mobile.
comAPRICOT2014BackgroundT-MobileUSisaGSM/UMTS/LTEproviderintheUSAwith45+MillionsubscribersIn2008,T-MobilelaunchedthefirstAndroidphone.
Thisdramaticallychangedthemobiledatadynamics–moredevices,connectedforalongertime,allneedingIPaddressesT-MobileembracedtheconceptofIPv6-only,sincedual-stackrequiredIPv4thatwasnotavailableNAT64/DNS64wasagoodsolutionthatdidnotrequireIPv4oneachclient,butsomeapplicationsfailedtoworkonIPv6-onlynetworks.
ItisnotacceptabletobreakSkypeorNetflix,applicationsthatrequireIPv4T-Mobile,inpartnershipwithNECandJPIX,documented464XLATintheIETFasRFC6877toovercomethelimitationsofNAT64byaddingaNAT46intotheclient(CLAT)Android4.
3introducedsupportfor464XLATinOctober20132ResultsAreImportantT-MobileUSlaunched5Androidphoneswith464XLATasthedefaultinthelast5months,allAndroid4.
3+phoneswillbe464XLATinthefutureatT-MobileUS3.
6millionuniqueIPv6subscribersinthefirst5monthsareactiveonthenetworkhttp://www.
worldipv6launch.
org/measurements/measurementsshow15.
76%ofallT-MobileconnectionsarenowIPv6,asofFebruary21,2014Over50%ofIPv6-usertrafficisend-to-endIPv6(notranslationneeded)Thissavesmoneyandmakesthenetworksimpler315.
76ofT-MobileUSConnectionsuse464XLAT4Default464XLATPhonesatT-MobileUS5SamsungNote3Google/LGNexus5SamsungMega464XLATPhones6SonyZ1sGalaxyLight464XLATallowsforfullfunctionalityonIPv6-onlynetworksDual-stackdoesnotsolvetheIPv4numberscarcityissueIPv6-only+NAT64/DNS64isverygood,butnotgoodenoughforfullIPv4replacement(webandemailwork,butSkypedoesnotwork)IPv6-only+464XLATSolvesIPv4numberingissuebynotassigningIPv4toclientsDecouplesedgegrowthfromIPv4availabilityIPv4-onlyapplicationslikeSkypeworkonanIPv6-onlynetworkbecause464XLATtranslatesIPv4onthephonetoIPv6onthenetwork7IPv6deploymentiseasyachievableT-MobileUSAdidnotspendanyCapExonIPv6Onlyintroduce464XLATonnewphones,sowedonotdisruptanyexistingservicesInnovativethinkinghelpsreducedeploymentcosts(hash128bitnumbersinto32bitfieldsinbillingrecords)IPv6willsavemoneyinyournetwork(lessNAT/CGN,noneedtobuyIPv4addresses,…)8Infact,withroaming,wecanshowChunghwainTaiwanandMYMAXISinMalaysiasupportIPv6todayintheRadioAccessNetwork(RAN)9WhichPlatformsSupports464XLATTodayYESAndroid4.
3+NOBlackberryAppleWindowsPhone()10IMPORTANT!
AnythingthatisnativelyIPv6enableddoesnotrequireanysortoftranslation,464XLATisidleandtransparentforanyIPv6end-to-endflowIPv6end-to-endjustworks!
464XLATisonlyforserviceandapplicationsthatareusingLEGACYIPV4AsmoreandmoreservicestransitiontoIPv6,464XLATisengagedlessandless464XLATisanIPv4EXITSTRATEGY11THETECHNICALDETAILS12464XLATisjustasetofbuildingblocksStatelessNAT64(RFC6145)ClientsidetranslationCLATStatefullNAT64(RFC6146)ProvidersitetranslationPLATDNS64(RFC6147)WhentheFQDNdoesnothaveaAAAArecord,DNS64dynamicallycreatesonethatallowstheclienttouseIPv6andthenetworktranslatesfromIPv6toIPv4attheNAT64Prefix64Discovery(RFC7050)Queriesforthewell-knownFQDNipv4only.
arpa,whichisbydefinitionIPv4-only.
IfthereisaAAAAresponseprovided,thenitisknownthataDNS64isinthepath133Scenariosin464XLAT1.
End-to-endIPv6:Facebook,Google,Wikipedia,Yahoo,Youtube…IPv6->IPv62.
ApplicationsupportsIPv6(webbrowser)buttheserverisonlyIPv4(www.
amazon.
com,www.
myspace.
com,…),soDNS64/NAT64translatesIPv6->IPv43.
ApplicationdoesnotsupportIPv6(Skype,Whatsapp,…),theclientmustprovideastatelessNAT46totheapplicationandstatefulNAT64mustbeinthenetwork:IPv4->IPv6->IPv414HowdoesStatelessNAT64workAlgorithmicallymapIPv4addressestoIPv6addresses,bidirectional,1to1NotdynamicDeterministicMapsallofIPv4's32bitsintoanIPv6/96(orlargerprefix)DefinedinRFC6145Example2001:db8::10.
1.
1.
110.
1.
1.
12001:db8::10.
2.
2.
210.
2.
2.
22001:db8::www.
example.
comipv4www.
example.
com15HowdoesStatefulNAT64work16DynamicallytranslateIPv6packetstoIPv4packetsDynamicNotdeterministic(translationbasedonavailableIPv4pool)Translationstateisshort-livedandbasedonsessioncreationandterminationDefinedinRFC6146ExampleBeforetranslationTCPsource2001:db8:abcd::ffffport555#clientaddressTCPdestination2001:db8:1234::10.
1.
1.
1port80#NAT64addressAftertranslationTCPsource192.
168.
1.
1port555#192.
168.
1.
1availablefromNAT64poolTCPdestination10.
1.
1.
1port80#Last32bitsofIPv6destinationHowdoesDNS64workWhenanFQDNdoesnothaveaAAAArecord,theDNS64willsyntheticallycreateonebasedonanetworkdefinedPref64Thepref64isaprefixhostedontheNAT64fortranslationExamplewithoutDNS64Query=aandaaaaforwww.
example.
comAnswer=a=10.
1.
1.
1,aaaa=NOERRORExamplewithDNS64Query=aandaaaaforwww.
example.
comAnswer=a=10.
1.
1.
1ANDaaaa=2001:db8::10.
1.
1.
117HowisthePref64discoveredontheclientPref64istopologicallylocatedontheNAT64TheDNS64forcesclientstosendtraffictotheNAT64fortranslationfromIPv6toIPv4AutomaticdiscoveryofPref64isdefinedinRFC7050Theclientwilllookupthewell-knownFQDNipv4only.
arpa.
IfaAAAArecordispresentedforthiswell-knowIPv4-onlyFQDN,theclientcanparsetheresponsetofindthePref64usedwithinthisnetwork18Pref64ConfigurationInformationFlow19HowtomakeEVERYTHINGworkonIPv6-only20ZoomOut:Whatdoesthislooklikeinthecontextof3GPPGSM/UMTS/LTE21HighLevelViewofIPv6deployment:Phone,HLRprofile,GGSN,NAT64,IPv6ISP2223ImpacttoNetworkEntitiesImpacttoNetworkEntitiesZoomin:WhatdoesthedefaultAndroidconfigurationlooklike:clatd.
conf24Zoomin:Whatdoesthephoneconfigurationlooklike:APNSettings25InAndroid4.
3,"APNProtocolIPv6"forthe"APNTypedefault"triggerstheuseof464XLATbydefaultIPv6=464XLATTIMEFORWIRESHARK26Likemostthings,westartwithDNSTheclientisIPv6-onlytowardsthenetwork,butthehostOSthinksitisdual-stacksinceithasanIPv4CLATinterfaceandanativeIPv6radiointerfaceSo,theclientdoesaqueryforDNS"A"and"AAAA"recordsTheDNS64respondswithasynthesizedAAAAandtherealAThesynthesizedAAAA=Pref64+realIPv427QuickCheckDoesthesynthesizedAAAAmatchthepref64+realA28pref64RealIPv4Next,theUEselectstheIPv6DNSresponse,andstartsTCPFromtheclientperspective,thisisanativeIPv6end-to-endflowBut,weknowthattheDNSisasynthesizedAAAAandtheclientisactuallysendingitspacketstotheNAT64forIPv6->IPv4statefultranslationThisisjustDNS64/NAT64,noclient-sidetranslationneededforthisscenario29Thefullcaseof464XLATdoubletranslation:WhatsApp30SYNissentfromtheCLATaddress31Remember,wesettheclatd.
conftousetheIIDof::464forCLATtranslationsTheMMSsituationTheAndroidMMSfunctioncommunicatesdirectlytothemodemandby-passesthenormalOSnetworkingstackFrequentlyMMSisitsownAPNThismeans464XLATisbypassed,464XLATonlyworksonthedefaultAPN,notspecialAPNslikeSUPLandMMSSolutionsUseanFQDN,DNS64stillworksfineIfyoucannotuseanFQDN,manuallyuseaNAT64literalinsteadoftheIPv4literal(pref64+ipv4literal)32Security:FollowtheruleofleastprivilegeFilteraccesstotheDNSseverFilteraccesstothePref64ontheNAT64UsingULAPref64willNOTworkwellsinceAndroidprefersIPv4overIPv6ULA.
Thisresultsin100%CLATtranslationsforIPv4resources33SummaryIPv4doesnotfitthebusinessneedstogrowtheedgeofournetworksfueledbygrowthfrominternetofthingsandcloudIPv6workstodayandisdeployedonsomeofthelargestedgenetworks464XLATallowsnetworkstogrowwithoutmanypublicIPv4addressesIPv6deploymentin3GPPGSM/UMTS/LTEisachievabletoday34BigPicture:WemustavoidtheInternet'slargestgrowthengine(mobile)frombeingindefinitelytiedtoscarceIPv4andfragilestatefulNAT44.
Byrne@T-Mobile.
comAPRICOT2014BackgroundT-MobileUSisaGSM/UMTS/LTEproviderintheUSAwith45+MillionsubscribersIn2008,T-MobilelaunchedthefirstAndroidphone.
Thisdramaticallychangedthemobiledatadynamics–moredevices,connectedforalongertime,allneedingIPaddressesT-MobileembracedtheconceptofIPv6-only,sincedual-stackrequiredIPv4thatwasnotavailableNAT64/DNS64wasagoodsolutionthatdidnotrequireIPv4oneachclient,butsomeapplicationsfailedtoworkonIPv6-onlynetworks.
ItisnotacceptabletobreakSkypeorNetflix,applicationsthatrequireIPv4T-Mobile,inpartnershipwithNECandJPIX,documented464XLATintheIETFasRFC6877toovercomethelimitationsofNAT64byaddingaNAT46intotheclient(CLAT)Android4.
3introducedsupportfor464XLATinOctober20132ResultsAreImportantT-MobileUSlaunched5Androidphoneswith464XLATasthedefaultinthelast5months,allAndroid4.
3+phoneswillbe464XLATinthefutureatT-MobileUS3.
6millionuniqueIPv6subscribersinthefirst5monthsareactiveonthenetworkhttp://www.
worldipv6launch.
org/measurements/measurementsshow15.
76%ofallT-MobileconnectionsarenowIPv6,asofFebruary21,2014Over50%ofIPv6-usertrafficisend-to-endIPv6(notranslationneeded)Thissavesmoneyandmakesthenetworksimpler315.
76ofT-MobileUSConnectionsuse464XLAT4Default464XLATPhonesatT-MobileUS5SamsungNote3Google/LGNexus5SamsungMega464XLATPhones6SonyZ1sGalaxyLight464XLATallowsforfullfunctionalityonIPv6-onlynetworksDual-stackdoesnotsolvetheIPv4numberscarcityissueIPv6-only+NAT64/DNS64isverygood,butnotgoodenoughforfullIPv4replacement(webandemailwork,butSkypedoesnotwork)IPv6-only+464XLATSolvesIPv4numberingissuebynotassigningIPv4toclientsDecouplesedgegrowthfromIPv4availabilityIPv4-onlyapplicationslikeSkypeworkonanIPv6-onlynetworkbecause464XLATtranslatesIPv4onthephonetoIPv6onthenetwork7IPv6deploymentiseasyachievableT-MobileUSAdidnotspendanyCapExonIPv6Onlyintroduce464XLATonnewphones,sowedonotdisruptanyexistingservicesInnovativethinkinghelpsreducedeploymentcosts(hash128bitnumbersinto32bitfieldsinbillingrecords)IPv6willsavemoneyinyournetwork(lessNAT/CGN,noneedtobuyIPv4addresses,…)8Infact,withroaming,wecanshowChunghwainTaiwanandMYMAXISinMalaysiasupportIPv6todayintheRadioAccessNetwork(RAN)9WhichPlatformsSupports464XLATTodayYESAndroid4.
3+NOBlackberryAppleWindowsPhone()10IMPORTANT!
AnythingthatisnativelyIPv6enableddoesnotrequireanysortoftranslation,464XLATisidleandtransparentforanyIPv6end-to-endflowIPv6end-to-endjustworks!
464XLATisonlyforserviceandapplicationsthatareusingLEGACYIPV4AsmoreandmoreservicestransitiontoIPv6,464XLATisengagedlessandless464XLATisanIPv4EXITSTRATEGY11THETECHNICALDETAILS12464XLATisjustasetofbuildingblocksStatelessNAT64(RFC6145)ClientsidetranslationCLATStatefullNAT64(RFC6146)ProvidersitetranslationPLATDNS64(RFC6147)WhentheFQDNdoesnothaveaAAAArecord,DNS64dynamicallycreatesonethatallowstheclienttouseIPv6andthenetworktranslatesfromIPv6toIPv4attheNAT64Prefix64Discovery(RFC7050)Queriesforthewell-knownFQDNipv4only.
arpa,whichisbydefinitionIPv4-only.
IfthereisaAAAAresponseprovided,thenitisknownthataDNS64isinthepath133Scenariosin464XLAT1.
End-to-endIPv6:Facebook,Google,Wikipedia,Yahoo,Youtube…IPv6->IPv62.
ApplicationsupportsIPv6(webbrowser)buttheserverisonlyIPv4(www.
amazon.
com,www.
myspace.
com,…),soDNS64/NAT64translatesIPv6->IPv43.
ApplicationdoesnotsupportIPv6(Skype,Whatsapp,…),theclientmustprovideastatelessNAT46totheapplicationandstatefulNAT64mustbeinthenetwork:IPv4->IPv6->IPv414HowdoesStatelessNAT64workAlgorithmicallymapIPv4addressestoIPv6addresses,bidirectional,1to1NotdynamicDeterministicMapsallofIPv4's32bitsintoanIPv6/96(orlargerprefix)DefinedinRFC6145Example2001:db8::10.
1.
1.
110.
1.
1.
12001:db8::10.
2.
2.
210.
2.
2.
22001:db8::www.
example.
comipv4www.
example.
com15HowdoesStatefulNAT64work16DynamicallytranslateIPv6packetstoIPv4packetsDynamicNotdeterministic(translationbasedonavailableIPv4pool)Translationstateisshort-livedandbasedonsessioncreationandterminationDefinedinRFC6146ExampleBeforetranslationTCPsource2001:db8:abcd::ffffport555#clientaddressTCPdestination2001:db8:1234::10.
1.
1.
1port80#NAT64addressAftertranslationTCPsource192.
168.
1.
1port555#192.
168.
1.
1availablefromNAT64poolTCPdestination10.
1.
1.
1port80#Last32bitsofIPv6destinationHowdoesDNS64workWhenanFQDNdoesnothaveaAAAArecord,theDNS64willsyntheticallycreateonebasedonanetworkdefinedPref64Thepref64isaprefixhostedontheNAT64fortranslationExamplewithoutDNS64Query=aandaaaaforwww.
example.
comAnswer=a=10.
1.
1.
1,aaaa=NOERRORExamplewithDNS64Query=aandaaaaforwww.
example.
comAnswer=a=10.
1.
1.
1ANDaaaa=2001:db8::10.
1.
1.
117HowisthePref64discoveredontheclientPref64istopologicallylocatedontheNAT64TheDNS64forcesclientstosendtraffictotheNAT64fortranslationfromIPv6toIPv4AutomaticdiscoveryofPref64isdefinedinRFC7050Theclientwilllookupthewell-knownFQDNipv4only.
arpa.
IfaAAAArecordispresentedforthiswell-knowIPv4-onlyFQDN,theclientcanparsetheresponsetofindthePref64usedwithinthisnetwork18Pref64ConfigurationInformationFlow19HowtomakeEVERYTHINGworkonIPv6-only20ZoomOut:Whatdoesthislooklikeinthecontextof3GPPGSM/UMTS/LTE21HighLevelViewofIPv6deployment:Phone,HLRprofile,GGSN,NAT64,IPv6ISP2223ImpacttoNetworkEntitiesImpacttoNetworkEntitiesZoomin:WhatdoesthedefaultAndroidconfigurationlooklike:clatd.
conf24Zoomin:Whatdoesthephoneconfigurationlooklike:APNSettings25InAndroid4.
3,"APNProtocolIPv6"forthe"APNTypedefault"triggerstheuseof464XLATbydefaultIPv6=464XLATTIMEFORWIRESHARK26Likemostthings,westartwithDNSTheclientisIPv6-onlytowardsthenetwork,butthehostOSthinksitisdual-stacksinceithasanIPv4CLATinterfaceandanativeIPv6radiointerfaceSo,theclientdoesaqueryforDNS"A"and"AAAA"recordsTheDNS64respondswithasynthesizedAAAAandtherealAThesynthesizedAAAA=Pref64+realIPv427QuickCheckDoesthesynthesizedAAAAmatchthepref64+realA28pref64RealIPv4Next,theUEselectstheIPv6DNSresponse,andstartsTCPFromtheclientperspective,thisisanativeIPv6end-to-endflowBut,weknowthattheDNSisasynthesizedAAAAandtheclientisactuallysendingitspacketstotheNAT64forIPv6->IPv4statefultranslationThisisjustDNS64/NAT64,noclient-sidetranslationneededforthisscenario29Thefullcaseof464XLATdoubletranslation:WhatsApp30SYNissentfromtheCLATaddress31Remember,wesettheclatd.
conftousetheIIDof::464forCLATtranslationsTheMMSsituationTheAndroidMMSfunctioncommunicatesdirectlytothemodemandby-passesthenormalOSnetworkingstackFrequentlyMMSisitsownAPNThismeans464XLATisbypassed,464XLATonlyworksonthedefaultAPN,notspecialAPNslikeSUPLandMMSSolutionsUseanFQDN,DNS64stillworksfineIfyoucannotuseanFQDN,manuallyuseaNAT64literalinsteadoftheIPv4literal(pref64+ipv4literal)32Security:FollowtheruleofleastprivilegeFilteraccesstotheDNSseverFilteraccesstothePref64ontheNAT64UsingULAPref64willNOTworkwellsinceAndroidprefersIPv4overIPv6ULA.
Thisresultsin100%CLATtranslationsforIPv4resources33SummaryIPv4doesnotfitthebusinessneedstogrowtheedgeofournetworksfueledbygrowthfrominternetofthingsandcloudIPv6workstodayandisdeployedonsomeofthelargestedgenetworks464XLATallowsnetworkstogrowwithoutmanypublicIPv4addressesIPv6deploymentin3GPPGSM/UMTS/LTEisachievabletoday34BigPicture:WemustavoidtheInternet'slargestgrowthengine(mobile)frombeingindefinitelytiedtoscarceIPv4andfragilestatefulNAT44.
- disrupt免费dns相关文档
- IP免费dns
- features免费dns
- 支持免费dns
- Users免费dns
- 域名免费dns
- drop免费dns
鲸云10美元,香港BGPRM 1核 1G 10Mbps峰值带宽 1TB流量,江西CN2-NAT 1核 512MB内存 100M带宽 ,
WHloud Official Notice(鲸云官方通知)(鲸落 梦之终章)]WHloud RouMu Cloud Hosting若木产品线云主机-香港节点上新预售本次线路均为电信CN2 GIA+移动联通BGP，此机型为正常常规机，建站推荐。本次预售定为国庆后开通，据销售状况决定，照以往经验或有咕咕的可能性，但是大多等待时间不长。均赠送2个快照 2个备份，1个默认ipv4官方网站：https:/...
6元虚拟主机是否值得购买
6元虚拟主机是否值得购买？近期各商家都纷纷推出了优质便宜的虚拟主机产品，其中不少6元的虚拟主机，这种主机是否值得购买，下面我们一起来看看。1、百度云6元体验三个月（活动时间有限抓紧体验）体验地址：https://cloud.baidu.com/campaign/experience/index.html?from=bchPromotion20182、Ucloud 10元云主机体验地址：https:...
[黑五]ProfitServer新加坡/德国/荷兰/西班牙VPS五折,不限流量KVM月付2.88美元起
ProfitServer已开启了黑色星期五的促销活动，一直到本月底，商家新加坡、荷兰、德国和西班牙机房VPS直接5折，无码直购最低每月2.88美元起，不限制流量，提供IPv4+IPv6。这是一家始于2003年的俄罗斯主机商，提供虚拟主机、VPS、独立服务器、SSL证书、域名等产品，可选数据中心包括俄罗斯、法国、荷兰、美国、新加坡、拉脱维亚、捷克、保加利亚等多个国家和地区。我们随便以一个数据中心为例...
免费dns为你推荐
-
outlookexpressOUTLOOK EXPRESS作用是什么？我想删除它会不会影响系统波音737起飞爆胎为什么客机每次起飞都要先跑一段距离www.topit.mehttp://www.topit.me/ 中自己上传的照片如何删除35互联在中国哪家服务商提供的企业邮箱好呢?社区动力你为什么想当一名社区工作者无忧登陆器无忧登陆器加载数据异常.无法登陆江苏网上营业厅要登录江苏电信网上营业厅怎么登上海电信上海联通，移动，电信哪个信号好代理网址谁知到能用的代理ip地址啊???泡泡堂服务器连接中断为什么泡泡堂老是服务器中断连接？