Re: [nmrg] SCTP

Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de> Thu, 13 April 2000 16:16 UTC

Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id SAA22312 for nmrg-outgoing; Thu, 13 Apr 2000 18:16:35 +0200 (MET DST)
Received: from henkell.ibr.cs.tu-bs.de (schoenw@henkell [134.169.34.191]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id SAA22291; Thu, 13 Apr 2000 18:16:27 +0200 (MET DST)
Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id SAA25690; Thu, 13 Apr 2000 18:16:27 +0200
Date: Thu, 13 Apr 2000 18:16:27 +0200
Message-Id: <200004131616.SAA25690@henkell.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: jp.martin-flatin@ieee.org
CC: nmrg@ibr.cs.tu-bs.de
In-reply-to: <200004121722.TAA27161@icasun1.epfl.ch> (jp.martin-flatin@ieee.org)
Subject: Re: [nmrg] SCTP
References: <200004121722.TAA27161@icasun1.epfl.ch>
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

>>>>> J P Martin-Flatin writes:

JP> You might be interested in reading about SCTP, which lies
JP> somewhere between TCP and UDP:

JP> draft-ietf-sigtran-sctp-08.txt
JP> draft-ietf-sigtran-sctp-applicability-00.txt

JP> Perhaps a good candidate to transport policies.

JP> Juergen, what about an SNMP over SCTP mapping?  ;-)

Go ahead if you think this makes sense.

(Personally, I have no clue how to implement something like this 
since a new transport protocol will take years to become universally
available. But this is of course not an argument for not doing a
transport mapping for SCTP or even implementing SCTP in your 
favourite kernel.)

/js