Re: [Tsvwg] SCTP applicability statement

"Brian F. G. Bidulock" <bidulock@openss7.org> Sun, 04 November 2001 21:47 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16806 for <tsvwg-archive@odin.ietf.org>; Sun, 4 Nov 2001 16:47:22 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id QAA08162 for tsvwg-archive@odin.ietf.org; Sun, 4 Nov 2001 16:47:24 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA08070; Sun, 4 Nov 2001 16:34:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA08038 for <tsvwg@optimus.ietf.org>; Sun, 4 Nov 2001 16:34:27 -0500 (EST)
Received: from bfgbhome.inetint.com (IDENT:root@tnt-dal-42-209.dallas.net [209.44.42.209]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16638 for <tsvwg@ietf.org>; Sun, 4 Nov 2001 16:34:24 -0500 (EST)
Received: (from brian@localhost) by bfgbhome.inetint.com (8.9.3/8.9.3) id PAA30462; Sun, 4 Nov 2001 15:33:57 -0600
Date: Sun, 04 Nov 2001 15:33:57 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Allison Mankin <mankin@isi.edu>
Cc: sigtran <sigtran@lyris.nortelnetworks.com>, RJ Atkinson <rja@inet.org>, "Transport Area wg (E-mail)" <tsvwg@ietf.org>
Subject: Re: [Tsvwg] SCTP applicability statement
Message-ID: <20011104153357.I3223@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Allison Mankin <mankin@isi.edu>, sigtran <sigtran@lyris.nortelnetworks.com>, RJ Atkinson <rja@inet.org>, "Transport Area wg (E-mail)" <tsvwg@ietf.org>
References: <20011104145819.F3223@openss7.org> <LYRIS-1825-44360-2001.11.04-16.22.33--bidulock#OPENSS7.ORG@lyris.nortelnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <LYRIS-1825-44360-2001.11.04-16.22.33--bidulock#OPENSS7.ORG@lyris.nortelnetworks.com>; from mankin@isi.edu on Sun, Nov 04, 2001 at 04:22:14PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: tsvwg-admin@ietf.org
Errors-To: tsvwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
X-BeenThere: tsvwg@ietf.org

Allison,

So, is your answer no?

Is it fair to say that SCTP does not support failover between
multi-homed hosts, between associations, your second case?

Are you saying that applications such as SIGTRAN, RSERPOOL, AAA,
must implement their own sequence numbers and acknowledgements
and retransmission queues between associations?

--brian

Allison Mankin wrote:                                     (Sun, 04 Nov 2001 16:22:14)
>
> > Does SCTP support failover between multi-homed hosts?
> > 
> > 
> > Is failover between multi-homed hosts within the scope of SCTP?
> 
> Brian,
> 
> SCTP's multi-homing has no relation to anything between*
> hosts, only between interfaces of one host.  There might be
> some kind of cluster that appears to its SCTP peer be one host 
> with multiple interfaces, but it would not be within the scope
> of SCTP to know about the cluster. 
> 
> In draft-ietf-aaa-transport-04.txt, section 3.2. there's a 
> good discussion of failover/failback, which distinguishes
> among:
> 
> - what a cluster does in its cluster OS or cluster communication
>   system 
> - what application-level watchdogs do, where the failover is among
>   multiple potential peers (here AAA servers)
> - what SCTP does
> 
> If all interfaces of an SCTP host are down, that's the second case.
> 
> Allison
> 
> 
> ---
> You are currently subscribed to sigtran as: bidulock@OPENSS7.ORG
> To unsubscribe send a blank email to leave-sigtran-1825X@lyris.nortelnetworks.com

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
http://www1.ietf.org/mailman/listinfo/tsvwg