SCTP Discussions

Text archives Help


Re: [SCTP-Discussion] ADDIP implementation


Chronological Thread 
  • From: Andreas Jungmaier <ajung AT exp-math.uni-essen.de>
  • To: "Eng Se-Hsieng" <g0202512 AT nus.edu.sg>, <discussion AT sctp.de>
  • Subject: Re: [SCTP-Discussion] ADDIP implementation
  • Date: Fri Apr 11 10:12:07 2003
  • List-id: SCTP Discussions <discussion.sctp.de>
  • Organization: University Duisburg-Essen

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 11 April 2003 06:05, Eng Se-Hsieng wrote:
> Dear all,
>
> I would like to enquire if the ADDIP extension is implemented in your
> prototype implementation.

That will be in the next release. When *that* is due, I do not know.
I suspect that we will release a version 1.0.0 based on the latest
sctplib-1.0.0-a16, when enough people have reported that it works
as well as expected. This version then will NOT have ADD-IP
(but PR-SCTP).

A new version (now named pre20) will be released as
sctplib-1.1.0 probably some time after the next bakeoff.
Realistically, that probably means not before the end of June.

> Secondly, do you currently authorise connections from a private IP behind a
> NAT towards a global IP?

Do we ? Or does our implementation ?

NATs with multi-homing probably breaks the protocol...as a server
behind a NAT has no way of finding out, that it is behind a NAT, it
will happily send out its private adresses in the INIT-ACK. Since
that information is protected by a signature (i.e. the COOKIE),
this will not work (at least with our implementation).

A client with multi-homing will send its private addresses in the
INIT chunk. A NAT would have to replace these by its own addresses,
and that might then work. Single-homing probably works fine, as
a client will not send its address in the INIT.

If you try this out, please let us know how it worked !

Regards,
Andreas

- --
Dipl.-Ing. Andreas Jungmaier
Computer Networking Technology Group
University of Duisburg-Essen
http://www.exp-math.uni-essen.de/~ajung
My PGP Key-ID: D3824AC0

My PGP Key-Fingerprint: 228C 7C2C 3381 2DD4 9998 2812 5C0B 0B04 D382 4AC0
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+lng2XAsLBNOCSsARAm97AKDSJOil+3j+mwUILNsbZyc3jxelcgCgnZjt
4ZtoNbr+yLJz9Cj5XQCkrlQ=
=Zdxp
-----END PGP SIGNATURE-----





Archive powered by MHonArc 2.6.19+.

Top of page