Re: updated draft for path failure detection in SCTP
"James M. Polk" <jmpolk@cisco.com> Wed, 24 February 2010 17:35 UTC
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E556228C224 for <tsvwg@core3.amsl.com>; Wed, 24 Feb 2010 09:35:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id thH+aiz1A8b8 for <tsvwg@core3.amsl.com>; Wed, 24 Feb 2010 09:35:36 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id E9EC928C21D for <tsvwg@ietf.org>; Wed, 24 Feb 2010 09:35:35 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJDyhEurRN+J/2dsb2JhbACbEHOkQZhBhHIEgxY
X-IronPort-AV: E=Sophos;i="4.49,533,1262563200"; d="scan'208";a="92042230"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-4.cisco.com with ESMTP; 24 Feb 2010 17:37:43 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8711.cisco.com [10.99.80.18]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o1OHbgLu029422; Wed, 24 Feb 2010 17:37:43 GMT
Message-Id: <201002241737.o1OHbgLu029422@sj-core-3.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 24 Feb 2010 11:37:41 -0600
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: updated draft for path failure detection in SCTP
In-Reply-To: <20100224.173744.65949807.nishida@sfc.wide.ad.jp>
References: <201002240006.o1O06K81013880@sj-core-3.cisco.com> <20100224.095432.212440055.nishida@sfc.wide.ad.jp> <201002240223.o1O2N39x014124@sj-core-3.cisco.com> <20100224.173744.65949807.nishida@sfc.wide.ad.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 17:35:37 -0000
At 02:37 AM 2/24/2010, Yoshifumi Nishida wrote: >Hello, >I've submitted new one. The new url for the draft is >http://www.ietf.org/internet-drafts/draft-nishida-tsvwg-sctp-failover-00.txt thank you >If it's possible, we would like to give a presentation. I will >likely present it. sure, you'll have time to present. I don't know whether it will be 5 minutes or 10 minutes -- but likely not any more than that, as we have a very full schedule now. James >Thanks, >-- >Yoshifumi Nishida >nishida@sfc.wide.ad.jp > >From: "James M. Polk" <jmpolk@cisco.com> >Subject: Re: updated draft for path failure detection in SCTP >Date: Tue, 23 Feb 2010 20:23:01 -0600 >Message-ID: <201002240223.o1O2N39x014124@sj-core-3.cisco.com> > > > It's no inconvenience. This is for chair tracking purposes. Without > > -tsvwg- in the filename, it's nearly impossible to track (i.e., sort) > > all the IDs coming out near a meeting. > > > > Will you want to present this ID during IETF77 (Anaheim)? > > > > If so, I need that request, along with who will likely present > > it. We're really tight on time already, which is unfortunate (we > > chairs tried to get two meeting slots - but failed). > > > > James > > > > At 06:54 PM 2/23/2010, Yoshifumi Nishida wrote: > > > > >OK. We will resubmit. Sorry for the inconvenience. > > > > > >Thanks, > > >-- > > >Yoshifumi Nishida > > >nishida@sfc.wide.ad.jp > > > > > >From: "James M. Polk" <jmpolk@cisco.com> > > >Subject: Re: updated draft for path failure detection in SCTP > > >Date: Tue, 23 Feb 2010 18:06:19 -0600 > > >Message-ID: <201002240006.o1O06K81013880@sj-core-3.cisco.com> > > > > > > > Authors > > > > > > > > I'd really prefer that IDs into this WG (i.e., wanting to > be discussed > > > > in TSVWG) have filenames in the following format: > > > > > > > > draft-<name>-tsvwg-<more stuff>-00.txt > > > > > > > > This is for chair tracking purposes. > > > > > > > > There is still time before the deadline (Monday March 1st) > to fix this > > > > by resubmitting this ID with an adjusted filename. > > > > > > > > Thank you > > > > > > > > James > > > > <obviously with my chair hat on> > > > > > > > > At 12:43 PM 2/23/2010, Yoshifumi Nishida wrote: > > > > > > > > >Hello, > > > > >Preethi and I submitted the updated I-D for path failure > detection in > > > > >SCTP. > > > > >We believe this proposal is useful and impotant for SCTP. We hope we > > > > >will > > > > >be allowed to give a presentation for this at Anaheim. > > > > >If you have any commnets, suggestions, please let us know! > > > > > > > > > >Thanks, > > > > >-- > > > > >Yoshifumi Nishida > > > > >nishida@sfc.wide.ad.jp > > > > > > > > > > > > > > >From: Internet-Drafts@ietf.org > > > > >Subject: I-D ACTION:draft-nishida-natarajan-sctp-failover-00.txt > > > > >Date: Tue, 23 Feb 2010 08:45:01 -0800 (PST) > > > > >Message-ID: <20100223164501.B966C28C310@core3.amsl.com> > > > > > > > > > > > A New Internet-Draft is available from the on-line > Internet-Drafts > > > > > > directories. > > > > > > > > > > > > > > > > > > Title : Quick Failover Algorithm in SCTP > > > > > > Author(s) : Y. Nishida, P. Natarajan > > > > > > Filename : > draft-nishida-natarajan-sctp-failover-00.txt > > > > > > Pages : 13 > > > > > > Date : 2010-2-22 > > > > > > > > > > > > One of the major advantages in SCTP is supporting > multi-homing > > > > > > communication. If an multi-homed end-point has > redundant network > > > > > > connections, sctp sessions can have a good chance > to survive from > > > > > > network failures by migrating inactive network to active one. > > > > > > However, if we follow the SCTP standard, there can > be significant > > > > > > delay for the network migration. During this > migration period, SCTP > > > > > > cannot transmit much data to the destination. This > issue drastically > > > > > > impairs the usability of SCTP in some situations. This memo > > > > > > describes the issue of SCTP failover mechanism and > discuss its > > > > > > solutions which require minimal modification to the > current standard. > > > > > > > > > > > > A URL for this Internet-Draft is: > > > > > > > http://www.ietf.org/internet-drafts/draft-nishida-natarajan-sctp-failover-00.txt > > > > > > > > > > > > Internet-Drafts are also available by anonymous FTP at: > > > > > > ftp://ftp.ietf.org/internet-drafts/ > > > > > > > > > > > > Below is the data which will enable a MIME compliant mail reader > > > > > > implementation to automatically retrieve the ASCII > version of the > > > > > > Internet-Draft. > > > > > >
- Quick Failover in SCTP Yoshifumi Nishida
- updated draft for path failure detection in SCTP Yoshifumi Nishida
- Re: updated draft for path failure detection in S… James M. Polk
- Re: updated draft for path failure detection in S… Yoshifumi Nishida
- Re: updated draft for path failure detection in S… James M. Polk
- Re: updated draft for path failure detection in S… Yoshifumi Nishida
- Re: updated draft for path failure detection in S… James M. Polk
- Re: Quick Failover in SCTP Scott Brim
- Re: Quick Failover in SCTP Yoshifumi Nishida
- RE: Quick Failover in SCTP Preethi Natarajan
- RE: Quick Failover in SCTP Preethi Natarajan
- Re: Quick Failover in SCTP Brian F. G. Bidulock
- RE: Quick Failover in SCTP Preethi Natarajan
- Re: Quick Failover in SCTP Brian F. G. Bidulock
- Re: Quick Failover in SCTP Yoshifumi Nishida
- Re: Quick Failover in SCTP Brian F. G. Bidulock
- RE: Quick Failover in SCTP Preethi Natarajan
- Re: Quick Failover in SCTP Yoshifumi Nishida
- Re: Quick Failover in SCTP Chris Benson