p702 project internet protocol version 6 - new opportunities for european pnos- - end-user bandwidth...
TRANSCRIPT
1
P702 Project
Internet Protocol version 6
- New Opportunities for European PNOs-
- End-User Bandwidth on Demand -
Telebit Communications A/S
March 1998
2
Profile -Telebit Communications A/S
• Europe’s only independent router manufacturer• Design and shipment of ATM Switches and MPR Routers• Technological leadership in IPv6 and integration of routing
and switching• Successful bespoke development projects• World-wide customer base• Based in Denmark
3
Profile -Telebit Communications A/S
•Tele Denmark (DK)
•DSC Communications (US/DK)
•UNI-C (DK)
•European Commission (EU)
•France Telecom (F)
•EURESCOM (EU)
•Internet For Business (UK)
•Microsoft (US)
•DFN (D)
•Ellemtel (S)
•NIST (US)
•University of Lancaster•CSELT (IT)•FAA (US)•ARINC (US)•AEROTHAI (THAI)•Nav Canada (CAN)•Politecnico di Torino•EENET•LATNET•LITNET•ARNES
Customers and Partners:
4
Profile -Telebit Communications A/S
5
Profile -Telebit Communications A/S
UNI-C:
6
P702 - Why IPv6 ?
IPv4 Problems:
• Lack of class B IPv4 address space => CIDR addressing
• Circa 1,800 active Autonomous Systems
• Inject nearly 43,000 Routable Prefixes
• Inadequate address aggregation
• Ballooning BGP databases, and Router memory exhaustion
• Increased forwarding table look up time
• Ubiquitous but simplistic
7
P702 - Why IPv6 ?
• Expanded Routing and Addressing capabilities– Relief of address shortage
– Support of more addressing hierarchy
– Addition of anycast address to give multicast efficiencies
• Header length fixed to 40 bytes – 64 bits + 128 bits source & destination address
– Easier to process in hardware and easier to compress.
• Improved support for Options– Use of Extension Headers and improved coding give more efficient
forwarding
• Multihoming possibilities– Enables users to switch between providers (auto-readdressing)
– Offers increased security and cost optimisation
8
P702 - Why IPv6 ?
IPv6 Mandates Auto-Address Configuration:
• IPv4 Configuration Process : 1) IPv4 Address
2) Default Gateway
3) Subnet Mask / Prefix Number
4) Domain Name Server and Domain Name
5) Solutions => Bootstrap (Static) & DHCP (Dynamic / Server based
• IPv6 Configuration Process:1) Neighbour Discovery (stateless configuration)
2) DHCPv6 (statefull configuration)
9
P702 - Why IPv6 ?
Security:• IPv4 Security Problems:
1) Denial of service attack (BGP / RIP hijacking)
2) Address spoofing
3) Use of source routing defeats address authentication
• IPv6 Security:1) Mandated at the Kernel level => IPSEC
2) Authentication Header (Default to MD5)
3) Encryption ( Default to DES-CBC)
4) Security Parameter Index (Defines non-default security association)
5) Repudiation features
10
P702 - Why IPv6 ?
IPv6 QoS Advantages:• QoS becoming an issue as real time services emerge:
1) Need for lower latency and jitter, but improved tolerance to lost packets
2) Less emphasis on re-transmission of lost data
3) More emphasis on timing relationships (time-stamping)
• 20-bit Flow Label enables identification of traffic flows• Class of Service field to manage conflicts• RSVP used by routers to deal with requests
11
P702 - Why IPv6 ?
How will the transition work ?• Simple Internet Transition (SIT) Mechanisms:
– Dual IP Stack in Hosts and Routers
– Dual IPv6 and IPv4 forwarding tables during transition
– Avoidance of ‘Flag-Day’
• Tunnelling ( IPv6 => IPv4 => IPv6):– Configured (encapsulating tunnel configured statically)
– Automatic (encapsulating tunnel configured automatically)
• Address Translation:– Dual IPv4 and IPv6 address not be possible after IPv4 exhaustion
– NAT boxes being developed
12
P702 - Why IPv6 ?
Why Users Want IPv6:• Innovators:
– Who: Research networks & labs, standards institutes, Universities, military
– Why: To become IPv6 ready and to explore strategic possibilities
• Early adopters:– Who: Telcos, advanced ISPs, advanced corporates
– Why: To position themselves as leading edge
• Followers:– Who: Telcos, ISPs, corporates
– Why: Customer demand and new service possibilities
13
P702 - Why IPv6 ?
Why use IP at all ?• Largest installed base of any protocol • An easy to deploy technology• User pull, rather then vendor push• Based on Software and not hardware =>cheaper• It works
14
P702 - Why IPv6 ?
Why IP / ATM Integration ?
• Move away from IP vs ATM arguments:
– Bandwidth in the LAN is/will be plentiful => IP
– When data aggregated from multiple LANs /ISPs => ATM
– They must be integrated.
• Possibility to exchange QoS information between IP and ATM
– IP signalling protocols (RSVP) allow BW specification
– IPv6 allows tagging of flows.
15
P702 - Objectives
Motivators and Objectives:• Most general voice/video/data services available with IP• Need for user-initiated multiple service levels with
QoS/CoS• Integration of IP services with all backbone/trunking
technologies• Needed to make optimum use of network resources and
facilitate growth in multimedia services.– Doesn’t ADSL promise 6 Mbps to everyone ?– But how will the backbone network carry traffic ?
• Pay-as-you go OR subscription to service levels to restrict usage
16
P702 - How it works
The Concept:
D
Internet
ATM
Policy Flow spec
Cut-through Data
Signal decision
Signal data
Policy
ISDN
D
© EURESCOM
17
P702 - How it works
ATM Switch
SerialLine
SerialLine
1xTBC2000/31xTBC1181xTBC1071xTBI104SWIP & SWATM
H1
1xTBC2000/31xTBC101SWIP
H2
H3
1xTBC2000/32xTBC1182xTBI1041xTBB102DSWIP & SWATM
Public switchedISDN network
ATM Line(155 Mbps)
IPv6 Router
DP1
IPv6 Router
DP3
IPv6 Router
DP2
ATM Line(155 Mbps)
Marlin 3030 Marlin 3030
1xTBC2000/31xTBC1181xTBC1071xTBI104SWIP & SWATM
Ethernet
Ethernet
Ethernet Ethernet
Ethernet
DP: Decision PointH : Host (PC or Sun SPARC)
ISDN2IPv4 Router
ISDN1IPv4 Router
The Demonstrator:
18
P702 - How it works
1) Customer selects video from menu, and clicks on PLAY
2) Client in host signals to the server to start video
Video Select Service Select
Video 1 Default
Video 2 Bronze
Video 3 Gold
Video 4 Platinum
PLAY
19
P702 - How it works
3) Video server starts and assigns random flow label. This is combined with the destination address => unique Flow ID
4) Client initiates RSVP sequence specifying required BW
5) Server sends RSVP PATH_MESSAGE, signalling the BW requirement to the first Decision Point (DP1).
6) PATH_MESSAGE routed using QoS Routing Table mapping BW to port no.
7) Path through network installed.
20
P702 - How it works
QoS Routing table:
Source Prefix Dest Prefix BW Interface Next Hop
Max Min
xxxxxxx xxxxxx 64K 8K Internet ::
xxxxxxx xxxxxx 2M 64K ISDN ::
xxxxxxx xxxxxx 8M 2M ATM ::
21
P702 - How it works
8) Client then sends reservation message back through network following the initial RSVP PATH_MESSAGE
9) Remote Decision Point then sets up connection and installs reservation
10) All subsequent packets with identical Flow ID are identified and forwarded using the Reservation Table
- Note: Service provision under the control of policy and subscription information held by a PNO controlled NMC.
- Full accounting facilities available
22
P702 - How it works
Envisaged Use:• Flat-rate subscription (as per today)• Options for spontaneous purchase (entry of payment
details)• Option to upgrade quality on the fly (if for instance
ambient traffic volumes increase)– Tear down messages, and new reservation established
• Facilitates grown in PUSH / PULL services
23
P702 - Other Technologies
CISCOs tag switching /IPSILONS IP flows:• Work at an IP level with few ATM / FR / ISDN possibilities
• Signalling not extended to the user, so no bandwidth on demand facility
• Focus on priority access to finite resource - overbooking problems not resolved
• Do not consider ITU / ATM forum standards, thus ill suited to broader telco environments
• Until MPLS is ratified by the IETF, they are proprietary solutions
• Little opportunity for system administrator to control user access
• Rely on point-point soft-state connections throughout a network, and distribution of QoS information - scalability ?
24
P702 - Conclusion
• Could revolutionise relationship between PNO & End-User• Facilitates new and differentiated services:
– High bandwidth on demand with existing infrastructures
– Real time services (Voice over IP / Video)
– Multicast Services
– Data transfer
• Could easily be deployed• Standards based implementation:
– Non-proprietary solution
• Software developed by group available for experimentation