draft-ietf-issll-atm-imp-req-02.txt   draft-ietf-issll-atm-imp-req-03.txt 
Internet Draft L. Berger Internet Draft L. Berger
Expires: July 1998 FORE Systems Expires: October 1998 FORE Systems
File: draft-ietf-issll-atm-imp-req-02.txt File: draft-ietf-issll-atm-imp-req-03.txt
RSVP over ATM Implementation Requirements RSVP over ATM Implementation Requirements
January 5, 1998 April 3, 1998
Status of Memo Status of Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
To learn the current status of any Internet-Draft, please check the To view the entire list of current Internet-Drafts, please check
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow the "1id-abstracts.txt" listing contained in the Internet-Drafts
Directories on ds.internic.net (US East Coast), nic.nordu.net Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net
(Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au
Rim). (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu
(US West Coast).
Abstract Abstract
This note presents specific implementation requirements for running This memo presents specific implementation requirements for running
RSVP over ATM switched virtual circuits (SVCs). It presents RSVP over ATM switched virtual circuits (SVCs). It presents
requirements that ensure interoperability between multiple requirements that ensure interoperability between multiple
implementations and conformance to the RSVP and Integrated Services implementations and conformance to the RSVP and Integrated Services
specifications. A separate document [5] provides specific guidelines specifications. A separate document [5] provides specific guidelines
for running over today's ATM networks. The general problem is for running over today's ATM networks. The general problem is
discussed in [9]. Integrated Services to ATM service mappings are discussed in [9]. Integrated Services to ATM service mappings are
covered in [6]. The full set of documents present the background and covered in [6]. The full set of documents present the background and
information needed to implement Integrated Services and RSVP over information needed to implement Integrated Services and RSVP over
ATM. ATM.
skipping to change at page 3, line 7 skipping to change at page 3, line 7
3.1 Data VC Management for Heterogeneous Sessions ...................8 3.1 Data VC Management for Heterogeneous Sessions ...................8
3.2 Multicast End-Point Identification ..............................9 3.2 Multicast End-Point Identification ..............................9
3.3 Multicast Data Distribution .....................................10 3.3 Multicast Data Distribution .....................................10
3.4 Receiver Transitions ............................................12 3.4 Receiver Transitions ............................................12
4. Security ............................................................12 4. Security ............................................................12
5. Acknowledgments .....................................................12 5. Acknowledgments .....................................................12
6. Author's Address ....................................................13 6. Author's Address ....................................................13
1. Introduction 1. Introduction
This note discusses running IP over ATM in an environment where SVCs This memo discusses running IP over ATM in an environment where SVCs
are used to support QoS flows and RSVP is used as the internet level are used to support QoS flows and RSVP is used as the internet level
QoS signaling protocol. It applies when using CLIP/ION, LANE2.0 and QoS signaling protocol. It applies when using CLIP/ION, LANE2.0 and
MPOA[4] methods for supporting IP over ATM. The general issues MPOA[4] methods for supporting IP over ATM. The general issues
related to running RSVP[8] over ATM have been covered in several related to running RSVP[8] over ATM have been covered in several
papers including [9] and other earlier work. This document is papers including [9] and other earlier work. This document is
intended as a companion to [9,5]. The reader should be familiar with intended as a companion to [9,5]. The reader should be familiar with
both documents. both documents.
This document defines the specific requirements for implementations This document defines the specific requirements for implementations
using ATM UNI3.x and 4.0. These requirements must be adhered to by using ATM UNI3.x and 4.0. These requirements must be adhered to by
skipping to change at page 13, line 42 skipping to change at page 13, line 42
Guaranteed-Service with ATM," Internet Draft, November 1997. Guaranteed-Service with ATM," Internet Draft, November 1997.
[7] Bradner, S., "Key words for use in RFCs to Indicate Requirement [7] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels," RFC 2119, March 1997. Levels," RFC 2119, March 1997.
[8] Braden, R., Zhang, L., Berson, S., Herzog, S., and Jamin, S., [8] Braden, R., Zhang, L., Berson, S., Herzog, S., and Jamin, S.,
"Resource ReSerVation Protocol (RSVP) -- Version 1 Functional "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional
Specification," RFC 2205, September 1997. Specification," RFC 2205, September 1997.
[9] Crawley, E., Berger, L., Berson, S., Baker, F., Borden, M., and [9] Crawley, E., Berger, L., Berson, S., Baker, F., Borden, M., and
Krawczyk, J, "Issues for Integrated Services and RSVP over ATM," Krawczyk, J, "A Framework for Integrated Services and RSVP over
Internet Draft, Novemver 1997. ATM," Internet Draft, February 1998.
[10] Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation [10] Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation
Layer 5," RFC 1483. Layer 5," RFC 1483.
[11] Perez, M., Liaw, F., Grossman, D., Mankin, A., Hoffman, E., and [11] Perez, M., Liaw, F., Grossman, D., Mankin, A., Hoffman, E., and
Malis, A., "ATM Signalling Support for IP over ATM," RFC 1755. Malis, A., "ATM Signalling Support for IP over ATM," RFC 1755.
[12] Maher, M., "ATM Signalling Support for IP over ATM - UNI 4.0 [12] Maher, M., "ATM Signalling Support for IP over ATM - UNI 4.0
Update" Internet Draft, May 1997. Update" Internet Draft, May 1997.
 End of changes. 6 change blocks. 
12 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/