IPv6 Security & QoS Babu Ram Dawadi

Outline IP Security Overview IP Security Architecture Authentication Header Encapsulating Security Payload Combinations of Security Associations Key Management QoS Overview

The need... the most serious involving: IP spoofing intruders creating packets with false address then taking advantages of OS exploits eavesdropping and sniffing attackers listen for userids and passwords and then just walk into target systems as a result the IAB included authentication and encryption in the next generation IP (IPv6)

IP Security We’ve considered some application specific security mechanisms eg. S/MIME, PGP, Kerberos, SSL/HTTPS however there are security concerns that cut across protocol layers would like security implemented by the network for all applications

IP Security Overview Applications of IPSec IPSec is not a single protocol. Instead, IPSec provides a set of security algorithms plus a general framework that allows a pair of communicating entities to use whichever algorithms to provide security appropriate for the communication. Applications of IPSec Secure branch office connectivity over the Internet Secure remote access over the Internet Establisihing extranet and intranet connectivity with partners Enhancing electronic commerce security

IP Security Scenario

IPSec general IP Security mechanisms provides authentication Confidentiality Integrity Obligation key management applicable to use over LANs, across public & private WANs, & for the Internet

Benefits of IPSec in a firewall/router provides strong security to all traffic crossing the perimeter is resistant to bypass is below transport layer, hence transparent to applications can be transparent to end users can provide security for individual users if desired additionally in routing applications: assure that router advertisments come from authorized routers neighbor advertisments come from authorized Neighbors insure redirect messages come from the router to which initial packet was sent insure no forgoing of router update

IPSec Services Two protocols are used to provide security: Authentication Header Protocol (AH) Encapsulation Security Payload (ESP) Services provided are: Access control integrity Data origin authentication Rejection of replayed packets a form of partial sequence integrity Confidentiality (encryption) Limited traffic flow confidentiality

Security Associations a one-way relationship between sender & receiver that affords security for traffic flow defined by 3 parameters: Security Parameters Index (SPI) a bit string (which algorithm to use?) IP Destination Address only unicast allowed could be end user, firewall, router Security Protocol Identifier indicates if SA is AH or ESP has a number of other parameters seq no, AH & EH info, lifetime etc have a database of Security Associations

Authentication Header (AH) RFC 2402 provides support for data integrity & authentication of IP packets end system/router can authenticate user/app prevents address spoofing attacks by tracking sequence numbers based on use of a MAC (message authentication code) HMAC-MD5-96 or HMAC-SHA-1-96 MAC is calculated: immutable IP header fields AH header (except for Authentication Data field) the entire upper-level protocol data (immutable) parties must share a secret key

Authentication Header Stallings Fig 16-3.

Transport and Tunnel Modes Both AH and ESP have two modes transport mode is used to encrypt & optionally authenticate IP data data protected but header left in clear can do traffic analysis but is efficient good for ESP host to host traffic tunnel mode encrypts entire IP packet add new header for next hop good for VPNs, gateway to gateway security

Transport & Tunnel Modes Stallings Fig 16-5.

Encapsulating Security Payload (ESP) RFC 2406 provides message content confidentiality & limited traffic flow confidentiality can optionally provide the same authentication services as AH supports range of ciphers, modes, padding incl. DES, Triple-DES, RC5, IDEA, CAST etc CBC most common pad to meet blocksize, for traffic flow

Encapsulating Security Payload Stallings Fig 16-7.

Combining Security Associations SA’s can implement either AH or ESP to implement both need to combine SA’s form a security bundle have 4 cases (see next)

Combining Security Associations Stallings Fig 16-10. a. AH in transport mode b.ESP in transport mode c. AH followed by ESP in transport mode(ESP SA inside an AH SA d. any one a, b, c inside an AH or ESP in tunnel mode

Key Management Two types: Manual Automated Oakley Key Determination Protocol Internet Security Association and Key Management Protocol (ISAKMP)

Key Management handles key generation & distribution typically need 2 pairs of keys 2 per direction for AH & ESP manual key management sysadmin manually configures every system automated key management automated system for on demand creation of keys for SA’s in large systems has Oakley & ISAKMP elements

ISAKMP Internet Security Association and Key Management Protocol (RFC 2407) provides framework for key management defines procedures and packet formats to establish, negotiate, modify and delete SAs independent of key exchange protocol, encryption algorithm and authentication method

IP Security Architecture Internet Key Exchange (IKE) A method for establishing a security association (SA) that authenticates users, negotiates the encryption method and exchanges the secret key. IKE is used in the IPsec protocol. Derived from the ISAKMP framework for key exchange and the Oakley and SKEME key exchange techniques, IKE uses public key cryptography to provide the secure transmission of the secret key to the recipient so that the encrypted data may be decrypted at the other end. (http://computing-dictionary.thefreedictionary.com/IKE)

IPSec Document Overview

ESP with authentication Transport Mode SA Tunnel Mode SA AH Authenticates IP payload and selected portions of IP header and IPv6 extension headers Authenticates entire inner IP packet plus selected portions of outer IP header ESP Encrypts IP payload and any IPv6 extesion header Encrypts inner IP packet ESP with authentication Encrypts IP payload and any IPv6 extesion header. Authenticates IP payload but no IP header Encrypts inner IP packet. Authenticates inner IP packet.

Before applying AH

Transport Mode (AH Authentication)

Tunnel Mode (AH Authentication)

ESP Encryption and Authentication

ESP Encryption and Authentication

Quality–of–Service (QoS) Different semantics or classes of QoS: determines reliability of offered service utilization of resources time resources max reserved B unused reserved C available resources reserved A

Per Packet QoS: (IPv6) Traffic class Interpret like IPv4’s DS field +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Version| Traffic Class | Flow Label | | Payload Length | Next Header | Hop Limit | | | + + + Source Address + + Destination Address + Traffic class Interpret like IPv4’s DS field

Resource Reservation Reservation is fundamental for reliable enforcement of QoS guarantees per-resource data structure (information about all usage) QoS calculations and resource scheduling may be done based on the resource usage pattern reservation protocols negotiate desired QoS transfer information about resource requirements and usage between the end-systems and all intermediate systems reservation operation calculate necessary amount of resources based on the QoS specifications reserve resources according to the calculation (or reject request) resource scheduling enforce resource usage with respect to resource administration decisions

Resource Management Phases user’s QoS requirements specification time rejection or renegotiation admission test and calculation of QoS guarantees negotiation resource reservation QoS guarantees to user confirmation renegotiation Phase 2: data transmission QoS enforcement by proper scheduling enforcement monitoring and adaptation “notification” renegotiation Phase 3: stream termination resource deallocation termination

Reservation Directions sender Sender oriented: sender (initiates reservation) must know target addresses (participants) in-scalable good security 1. reserve data flow 2. reserve 3. reserve receiver

Reservation Directions sender Receiver oriented: receiver (initiates reservation) needs advertisement before reservation must know “flow” addresses sender need not to know receivers more scalable in-secure 3. reserve data flow 2. reserve 1. reserve receiver

Reservation Directions sender Combination? start sender oriented reservation additional receivers join at routers (receiver based) 1. reserve data flow 2. reserve reserve from nearest router 3. reserve receiver

QoS in IPv6 Protocols IPv6 protocols carry a small number of QoS-Specific service elements in the IP based & Extension Header Flows Sequence of packets sent from a particular source to a particular destination(s) for which the source require special handling in intermediate routers by control protocols like RSVP

Flows Packets that do not belongs to a flow carry a flow level of all zeros. All packets belonging to the same flow must be sent with same IP source address and destination address with non-zero flow label. The Flow label field in IPv6 may be used by source to label packets for which it request special handling by the IPv6 routers like real time service.

IPv6 extension Headers Two external headers to signal QoS requirements The Routing extension header can be used to request a specific route by indicating a sequence of IP address. HOP-by-HOP extension headers can be used to transport a maximum of one router alert signaling message per IP packet to every router on the path of QoS-sensitive traffic, indicating that each router should specifically process the packets