Dismiss
InnovationQ/InnovationQ Plus content will be updated on Sunday, June 25, 10am ET, with new patent and non-patent literature collections. Click here to learn more.
Browse Prior Art Database

OSPF over ATM and Proxy-PAR (RFC2844)

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

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Przygienda: AUTHOR [+3]

Abstract

This memo specifies, for OSPF implementors and users, mechanisms describing how the protocol operates in ATM networks over PVC and SVC meshes with the presence of Proxy-PAR. These recommendations require no protocol changes and allow simpler, more efficient and cost- effective network designs. It is recommended that OSPF implementations should be able to support logical interfaces, each consisting of one or more virtual circuits and used either as numbered logical point-to-point links (one VC), logical NBMA networks (more than one VC) or Point-to-MultiPoint networks (more than one VC), where a solution simulating broadcast interfaces is not appropriate. PAR can help distribute across the ATM cloud configuration setup and changes of such interfaces when OSPF capable routers are (re-)configured. Proxy-PAR can in turn be used to exchange this information between the ATM cloud and the routers connected to it.

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

Network Working Group T. Przygienda

Request for Comments: 2844 Siara

Category: Experimental P. Droz

R. Haas

IBM

May 2000

OSPF over ATM and Proxy-PAR

Status of this Memo

This memo defines an Experimental Protocol for the Internet

community. It does not specify an Internet standard of any kind.

Discussion and suggestions for improvement are requested.

Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

Abstract

This memo specifies, for OSPF implementors and users, mechanisms

describing how the protocol operates in ATM networks over PVC and SVC

meshes with the presence of Proxy-PAR. These recommendations require

no protocol changes and allow simpler, more efficient and cost-

effective network designs. It is recommended that OSPF

implementations should be able to support logical interfaces, each

consisting of one or more virtual circuits and used either as

numbered logical point-to-point links (one VC), logical NBMA networks

(more than one VC) or Point-to-MultiPoint networks (more than one

VC), where a solution simulating broadcast interfaces is not

appropriate. PAR can help distribute across the ATM cloud

configuration setup and changes of such interfaces when OSPF capable

routers are (re-)configured. Proxy-PAR can in turn be used to

exchange this information between the ATM cloud and the routers

connected to it.

1 Introduction

Proxy-PAR and PAR have been accepted as standards by the ATM Forum in

January 1999 [1]. A more complete overview of Proxy-PAR than in the

section below is given in [2].

1.1 Introduction to Proxy-PAR

Proxy-PAR [1] is an extension that allows different ATM attached

devices (like routers) to interact with PAR-capable switches and to

query information about non-ATM services without executing PAR

themselves. The Proxy-PAR client side in the ATM attached device is

much simpler in terms of implementation complexity and memory

requirements than a complete PAR protocol stack (which includes the

full PNNI [3] protocol stack) and should allow easy implementation,

e.g. in existing IP routers. In addition, clients can use Proxy-PAR

to register the various non-ATM services and protocols they support.

Proxy PAR has consciously been omitted as part of ILMI [4] due to the

complexity of PAR information passed in the protocol and the fact

that it is intended for integration of non-ATM protocols and services

only. A device that executes Proxy-PAR does not necessarily need to

execute ILMI or UNI signaling, although this normally will be the

case.

The protocol in itself d...