Browse Prior Art Database

RSVP Extensions for IPSEC Data Flows (RFC2207)

IP.com Disclosure Number: IPCOM000002765D
Original Publication Date: 1997-Sep-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 11 page(s) / 28K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L. Berger: AUTHOR [+2]

Abstract

This document presents extensions to Version 1 of RSVP. These extensions permit support of individual data flows using RFC 1826, IP Authentication Header (AH) or RFC 1827, IP Encapsulating Security Payload (ESP). RSVP Version 1 as currently specified can support the IPSEC protocols, but only on a per address, per protocol basis not on a per flow basis. The presented extensions can be used with both IPv4 and IPv6.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 10% of the total text.

Network Working Group L. Berger

Request for Comments: 2207 FORE Systems

Category: Standards Track T. O'Malley

BBN

September 1997

RSVP Extensions for IPSEC Data Flows

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Abstract

This document presents extensions to Version 1 of RSVP. These

extensions permit support of individual data flows using RFC 1826, IP

Authentication Header (AH) or RFC 1827, IP Encapsulating Security

Payload (ESP). RSVP Version 1 as currently specified can support the

IPSEC protocols, but only on a per address, per protocol basis not on

a per flow basis. The presented extensions can be used with both

IPv4 and IPv6.

Table of Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 2

2 Overview of Extensions . . . . . . . . . . . . . . . . . . 3

3 Object Definition. . . . . . . . . . . . . . . . . . . . . 4

3.1 SESSION Class . . . . . . . . . . . . . . . . . . . . 5

3.2 FILTER_SPEC Class . . . . . . . . . . . . . . . . . . 5

3.3 SENDER_TEMPLATE Class . . . . . . . . . . . . . . . . 6

4 Processing Rules . . . . . . . . . . . . . . . . . . . . . 6

4.1 Required Changes. . . . . . . . . . . . . . . . . . . 6

4.2 Merging Flowspecs . . . . . . . . . . . . . . . . . . 7

4.2.1 FF and SE Styles. . . . . . . . . . . . . . . . . . 7

4.2.2 WF Styles . . . . . . . . . . . . . . . . . . . . . 8

5 IANA Considerations. . . . . . . . . . . . . . . . . . . . 8

6 Security Considerations. . . . . . . . . . . . . . . . . . 8

7 References . . . . . . . . . . . . . . . . . . . . . . . .10

8 Acknowledgments . . . . . . . . . . . . . . . . . . . . .10

9 Authors' Addresses . . . . . . . . . . . . . . . . . . . .10

A Options Considered . . . . . . . . . . . . . . . . . . . .11

A.1 UDP Encapsulation . . . . . . . . . . . . . . . . . .11

A.2 FlowID Header Encapsulation . . . . . . . . . . . . .12

A.3 IPSEC Protocol Modification . . . . . . . . . . . . .12

A.4 AH Transparency . . . . . . . . . . . . . . . . . . .13

1 Introduction

Recently published Standards Track RFCs specify protocol mechanisms

to provide IP level security. These IP Security, or IPSEC, protocols

support packet level authentication, [RFC 1826], and integrity and

confidentiality [RFC 1827]. A number of interoperable

implementations already exist and several vendors have announced

commercial products that...