RE: FCoverSCTP/IP specification

["Douglas Otis" <dotis@sanlight.net>]

Marjorie Krueger,

As SCTP can establish a connection as server using a single Well-Known-Port,
the next level of configuration can happen within stream 0 as a convention.
(A nice feature for embedded adapters as there is less OS interaction.)
Don't embed url stuff into these configuration structures but instead leave
that to LDAP and then IT managers have tools to configure the equipment.
This keeps real-time configuration quick using binary structures and you can
fix configuration security issues without rewriting this spec as it would be
a different spec describing the LDAP structures and how they are used.
Setting up FC domains and attributes on streams would be the configuration
process based on structures found within LDAP as well as defining SCTP
authentication.  Looking at SCTP should help with most details, as it is
fairly complete.

With your help I will continue this process as a group effort.

Doug

> -----Original Message-----
> From: Marjorie Krueger [mailto:Marjorie.Krueger@Vixel.com]
> Sent: Monday, August 21, 2000 3:43 PM
> To: Douglas Otis
> Cc: Ips
> Subject: Re: FCoverSCTP/IP specification
>
>
> Where have you interjected SCTP, other than the title?  Seems
> like somethings missing
> from this proposal...
>
> Marjorie Krueger
> Vixel Corp.
>
> Douglas Otis wrote:
>
> > Lifting from the FCoverIP specification, FCoverSCTP/IP could look even
> > simpler.
> > As example:
> >
> >
> ------------------------------------------------------------------
> --------------
> >                         Name: FCoverSCTP-IP.txt
> >    FCoverSCTP-IP.txt    Type: Plain Text (text/plain)
> >                     Encoding: 7bit
>