Re[2]: int-serv over e.g. ATM

[Charlie Tai <[e-mail]>]

Text item: 

     The ATM Forum API semantic description document exposes in essence all 
     the UNI 3.1 signaling information, which includes the traffic 
     descriptor and QOS classes that are supposed to be used to support the 
     RSVP flow spec.  Note that this is only the semantic definition and it 
     is up to the OS vendors to realize this ATM API in their respective 
     OS's. 
     
     In the case of Windows PC environment, version 2 of the WinSock 
     (Windows Sockets) interface was designed from its inception to support 
     QOS-aware applications and transports.  The WinSock 2 spec took into 
     account emerging networking technologies such as RSVP and ATM among 
     others.  The semantic description of WinSock 2 was submitted to the 
     ATM Forum a year ago as a joint contribution from Intel, Microsoft and 
     IBM, and was adopted as the ATM Forum API baseline text.
     
     WinSock 2 incorporates a general QOS structure which could be mapped 
     to RSVP or ATM QOS mechanism by the transport providers.  In addition, 
     the RSVP and ATM specific QOS extensions will enable RSVP and ATM 
     specific applications, respectively.  Detailed information about 
     WinSock 2 is available via WWW (http://www.intel.com/IAL/winsock2) or 
     anonymous ftp (ftp.intel.com:/pub/winsock2/spec).
     
     As for the mapping from RSVP to ATM, it is up to the RSVP layer to do 
     the conversion.  Some issues have been discussed in RFC 1821.
     
     
     -- Charlie Tai
        Intel Architecture Labs
        e-mail: [e-mail]
     
______________________________ Forward Header __________________________________
Subject: Re: int-serv over e.g. ATM
Author:  [e-mail] at Internet_Gateway 
Date:    11/6/95 9:18 PM
     
     
At 12:18 PM 11/6/95, Mark W Garrett wrote: 
>
>Can people comment on what work is going on in any of {RSVP, 
>int-serv, rolc, IPATM, MPOA (ATM Forum)} working groups 
>toward creating such an API or the QOS-translation 
>interface?  (I know of one item, which is rfc1821 by Borden 
>Crawley, Davie, and Batsell, which discusses the two types
>of QOS descriptions and lays out some issues for interoperation). 
>
>
     
The ATM Forum recently completed an ATM API document, 
"Native ATM Services: Semantic Description", atm95-0008. 
This will go for final vote shortly.
     
The ATM API document lays out the scheme to be used for
call distribution within an ATM endsystem. As far as "QOS" type 
parameters go, the API will essentially allow access to all the ATM 
signaling parameters. It is up to the API user to use them 
appropriately.
     
In this case it is up to the IP layer to map the RSVP flowspecs 
to ATM QOS and traffic parameters.
     
In addition to the above work, there is currently work in progress in 
the X/Open XNET group to map the ATM Forum API to the XTI syntax. 
(XTI is the X/Open Transport Interface.) This will enable native ATM 
applications using XTI.
     
     
     
     
     
Alagu Periyannan                   [e-mail]
     
Communications Products and Technology 
Apple Computer, Inc.

Text item: External Message Header

The following mail header is for administrative use
and may be ignored unless there are problems.

***IF THERE ARE PROBLEMS SAVE THESE HEADERS***.

Content-Length: 1276
Subject: Re: int-serv over e.g. ATM
From: [e-mail] (Alagu Periyannan)
To: [e-mail] (Mark W Garrett), [e-mail], [e-mail],
        [e-mail]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0
Message-Id: <v02110111acc428919900@[17.255.9.131]>
Date: Mon, 6 Nov 1995 21:18:43 -0800
Received: from [17.255.9.131] (skylawn.atg.apple.com [17.255.9.131]) by taurus.a
pple.com (8.6.12/8.6.10) with SMTP id VAA23817; Mon, 6 Nov 1995 21:18:43 -0800
Received: from taurus.apple.com by federal-excess.apple.com (5.0/1-Nov-1994-eef)

     id AA29605; Mon, 6 Nov 1995 21:17:57 +0800
     for [e-mail]
Received: from federal-excess.apple.com by alink-gw.apple.com with SMTP (921113.
SGI.UNSUPPORTED_PROTOTYPE/7-Oct-1993-eef)
     id AA26046; Mon, 6 Nov 95 21:19:21 -0800
     for [e-mail]
Received: from alink-gw.apple.com by venera.isi.edu (5.65c/5.61+local-22)
     id <AA11676>; Mon, 6 Nov 1995 21:19:22 -0800
Received: by venera.isi.edu (5.65c/5.61+local-22)
     id <AA11683>; Mon, 6 Nov 1995 21:19:27 -0800
Received: from venera.isi.edu by hermes.intel.com (5.65/10.0i); Mon, 6 Nov 95 22
:38:46 -0800
Received: from hermes.intel.com by relay.jf.intel.com with smtp
     (Smail3.1.28.1 #2) id m0tChgJ-000twWC; Mon, 6 Nov 95 22:38 PST