RSPlib Discussions

Text archives Help


Re: [RSPlib-Discusssion] Asap Server Announces


Chronological Thread 
  • From: Thomas Dreibholz <dreibh AT iem.uni-due.de>
  • To: rsplib-discussion AT sctp.de
  • Subject: Re: [RSPlib-Discusssion] Asap Server Announces
  • Date: Thu, 6 Dec 2007 08:23:43 +0100
  • List-archive: <http://lists.franken.de/pipermail/rsplib-discussion>
  • List-id: RSPlib Discussions <rsplib-discussion.sctp.de>
  • Organization: University of Duisburg-Essen, Institute for Experimental Mathematics

On Donnerstag, 6. Dezember 2007, Frank Volkmer wrote:
> Hello,
>
> at the time I am working on an ASAP interface for a registrar server.
> I use the rsplib to test my own implementation.
>
> From what I get out of my traces and the source code I see that you
> assume that a registrar server should be reachable via SCTP under the
> source address and the source port of the multicast message. But you
> completly ignore any present SCTP transport parameter which would
> provide that information. Wy is that so?

This handling of the optional transport parameters has not been implemented
yet. But it is not very difficult. I will do this soon.


Best regards
--
=======================================================================
Dr. Thomas Dreibholz

University of Duisburg-Essen, Room ES210
Inst. for Experimental Mathematics Ellernstraße 29
Computer Networking Technology Group D-45326 Essen/Germany
-----------------------------------------------------------------------
E-Mail:
dreibh AT iem.uni-due.de
Homepage: http://www.iem.uni-due.de/~dreibh
=======================================================================

Attachment: signature.asc
Description: This is a digitally signed message part.




Archive powered by MHonArc 2.6.19+.

Top of page