| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 515.1 | | RMULAC::S_WATTUM | Scott Wattum - FTAM/VT/OSAK Engineering (303) 840-2986 | Mon Jun 02 1997 10:48 | 9 |
| We don't have any doc writers, and the documentation is still kindof in limbo as
a result of the transition, however, there is a documentation coordinator who
provided the following pointers:
TNPUBS::DISK$PROJECT7:[2KW3292.PUBLIC.VMS]
TNPUBS::DISK$PROJECT7:[2KW3292.PUBLIC.OSF]
--Scott
|
| 515.2 | Thanks - references to RFC1006 still missing | BIKINI::DITE | John Dite@RTO DTN 865-4065 | Tue Jun 03 1997 06:42 | 7 |
| Thanks for the info. It was spot on.
What still needs to be takled in the documentation is the references to
the use of the OSAK API over RFC1006.
John
|
| 515.3 | | RMULAC::S_WATTUM | Scott Wattum - FTAM/VT/OSAK Engineering (303) 840-2986 | Tue Jun 03 1997 08:59 | 7 |
| >What still needs to be takled in the documentation is the references to
>the use of the OSAK API over RFC1006.
Can you be more specific about what you think is required? We can probably put
something in the release notes, but since we don't have any doc writers (at this
point), it's unlikely that the documentation will be updated.
|
| 515.4 | A small list | BIKINI::DITE | John Dite@RTO DTN 865-4065 | Tue Jun 03 1997 11:18 | 59 |
| Scott,
basically the differences to OSI communications.
As far as I know the following are valid, but please correct me and extend the
list.
For DIGITAL UNIX
================
Initiator:
1. Address form
a. IP address as hex value with port id
(eg. 00661024708E for 16.36.112.142 port 102).
2. NSAP type must be set to OSAK_C_RFC1006
3. The field transport_template in the OSAK parameter block must point
to the ficticious '1006' template.
Responder:
1. The field transport_template in the OSAK parameter block must point
to the ficticious '1006' template.
For DIGITAL OpenVMS
===================
Initiator:
1. Address form
a. IP address as hex value with port id
(eg. 00661024708E for 16.36.112.142 port 102).
b. IP address as a hex value witout port id.
(eg. 1024708E for 16.36.112.142).
c. IP address as an ASCII string
(eg. "16.36.112.142").
2. NSAP type must be set to OSAK_C_RFC1006
3. The field transport_template in the OSAK parameter block must point
to a real OSI Transport template where Network Service = RFC1006.
Responder:
1. I'm not aware that an existing OSI Application has to be changed to receive
Association Indications over RFC1006.
Then the differences have to be mentioned between OpenVMS and UNIX V3.*
as far as writing OSAK applications that deal with OSI as well as RFC1006
connections.
Then the fact that OSAK for DIGITAL UNIX V4.0 does not(?) require
two OSAK_OPEN_RESPONDER calls for RFC1006 and OSI.
Last, but not least updated example programs illustrating OSAK interworking
over RFC1006.
|