DOC PREVIEW
U of I CS 438 - IPv6, MPLS

This preview shows page 1-2-3-24-25-26 out of 26 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 26 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 26 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 26 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 26 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 26 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 26 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 26 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

IPv6, MPLSIPv6Slide 3IPv6 AddressesSlide 5IPv4 Packet FormatIPv6 Packet FormatSlide 8Slide 9IPv6 Extension HeadersSlide 11Slide 12Slide 13Slide 14IPv6 Design ControversiesSlide 16Slide 17Slide 18Slide 19Slide 20Transition From IPv4 To IPv6TunnelingSlide 23Multiprotocol label switching (MPLS)MPLS capable routersMPLS forwarding tablesIPv6, MPLSIPv6HistoryNext generation IP (AKA IPng)Intended to extend address space and routing limitations of IPv4Requires header changeAttempted to include everything new in one changeIETF moderatedBased on Simple Internet Protocol Plus (SIPP)IPv6Wish list128-bit addressesMulticast trafficMobilityReal-time traffic/quality of service guaranteesAuthentication and securityAutoconfiguration for local IP addressesEnd-to-end fragmentationProtocol extensionsSmooth transition!NoteMany of these functionalities have been retrofit into IPv4IPv6 Addresses128-bit3.4 x 1038 addresses (as compared to 4 x 109)Classless addressing/routing (similar to CIDR)Address notationString of eight 16-bit hex values separated by colons5CFA:0002:0000:0000:CF07:1234:5678:FFCDSet of contiguous 0’s can be elided5CFA:0002::CF07:1234:5678:FFCDAddress assignmentProvider-basedgeographic010 Region ID Provider ID Subscriber ID Subnet Host3 m n o p 125-m-n-o-pIPv6Prefix Address type0000 0000 Reserved (includes transition addresses)0000 0001 ISO NSAP (Network Service Point) Allocation0000 010 Novell IPX allocation010 Provider-based unicast100 Geographic multicast1111 1110 10 Link local address1111 1110 11 Site local address1111 1111 Multicast addressOther unassignedIPv4 Packet Format20 Byte minimumMandatory fields are not always usede.g. fragmentationOptions are an unordered list of (name, value) pairsTTLsource addressdestination addressoptions (variable)version length offsetident 0 8 16 31hdr len TOSflagschecksumprotocolpad (variable)IPv6 Packet Formatdestination address word 4options (variable number, usually fixed length)version flow label hop limitpayload length 0 8 16 31prioritynext headersource address word 1source address word 2source address word 3source address word 4destination address word 1destination address word 2destination address word 3IPv6 Packet Format40 Byte minimumMandatory fields (almost) always usedStrict order on options reduces processing timeNo need to parse irrelevant optionsoptions (variable number, usually fixed length)version flow label hop limitpayload length 0 8 16 31prioritynext headersource address 4 words destination address 4 wordsIPv6 Packet FormatVersion6Priority and Flow LabelSupport service guaranteesAllow “fair” bandwidth allocationPayload LengthHeader not includedNext HeaderCombines options and protocolLinked list of optionsEnds with higher-level protocol header (e.g. TCP)Hop LimitTTL renamed to match usageIPv6 Extension HeadersMust appear in orderHop-by-hop optionsMiscellaneous information for routersRoutingFull/partial route to followFragmentationIP fragmentation infoAuthenticationSender identificationEncrypted security payloadInformation about contentsDestination optionsInformation for destinationIPv6 Extension HeadersHop-by-Hop extensionLength is in bytes beyond mandatory 8next header typevalue0 8 16 31lengthnext header 194Payload length in bytes0 8 16 310 0Jumbogram option (packet longer than 65,535 bytes)Payload length in main header set to 0IPv6 Extension HeadersRouting extensionUp to 24 “anycast” addresses target AS’s/providersNext address tracks current targetStrict routing requires direct linkLoose routing allows intermediate nodesnext header # of addressesstrict/loose routing bitmap0 8 16 310 next address1 – 24 addressesIPv6 Extension HeadersFragmentation extensionSimilar to IPv4 fragmentation13-bit offsetLast fragment mark (M)Larger fragment identification fieldnext header offsetident0 8 16 31reserved reserved MIPv6 Extension HeadersAuthentication extensionDesigned to be very flexibleIncludesSecurity parameters index (SPI)Authentication dataEncryption ExtensionCalled encapsulating security payload (ESP)Includes an SPIAll headers and data after ESP are encryptedIPv6 Design ControversiesAddress length8 byteMight run out in a few decadesLess header overhead16 byteMore overheadGood for foreseeable future20 byteEven more overheadCompatible with OSIVariable lengthIPv6 Design ControversiesHop limit65,53532 hop paths are common nowIn a decade, we may see much longer paths255Objective is to limit lost packet lifetimeGood network design makes long paths unlikelySource to backboneAcross backboneBackbone to destinationIPv6 Design ControversiesGreater than 64KB dataGood for supercomputer/high bandwidth applicationsToo much overhead to fragment large data packets64 KB dataMore compatible with low-bandwidth lines1 MB packet ties up a 1.5MBps line for more than 5 secondsInconveniences interactive usersIPv6 Design ControversiesKeep checksumRemoving checksum from IP is analogous to removing brakes from a carLight and fasterUnprepared for the unexpectedRemove checksumTypically duplicated in data link and transport layersVery expensive in IPv4IPv6 Design ControversiesMobile hostsDirect or indirect connectivityReconnect directly using canonical addressUse home and foreign agents to forward trafficMobility introduces asymmetryBase station signal is strong, heard by mobile unitsMobile unit signal is weak and susceptible to interference, may not be heard by base stationIPv6 Design ControversiesSecurityWhere?Network layerA standard serviceApplication layerNo viable standardApplication susceptible to errors in network implementationExpensive to turn on and offHow?Political import/export issuesCryptographic strength issuesTransition From IPv4 To IPv6Not all routers can be upgraded simultaneousno “flag days”How will the network operate with mixed IPv4 and IPv6 routers? Tunneling: IPv6 carried as payload in IPv4 datagram among IPv4 routersTunnelingABEFIPv6IPv6IPv6IPv6tunnelLogical view:Physical view:ABEFIPv6IPv6IPv6IPv6IPv4IPv4TunnelingABEFIPv6IPv6IPv6IPv6tunnelLogical view:Physical view:ABEFIPv6IPv6IPv6IPv6CDIPv4IPv4Flow:


View Full Document

U of I CS 438 - IPv6, MPLS

Documents in this Course
Routing

Routing

5 pages

TCP

TCP

26 pages

TROLL

TROLL

3 pages

Load more
Download IPv6, MPLS
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view IPv6, MPLS and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view IPv6, MPLS 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?