Re: [tsvwg] IETF WG state changed to In WG Last Call from WG Document [rev. 08]

Jeff Morriss <jeff.morriss.ws@gmail.com> Tue, 18 November 2014 18:37 UTC

Return-Path: <jeff.morriss.ws@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E95A91A1AF0 for <tsvwg@ietfa.amsl.com>; Tue, 18 Nov 2014 10:37:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d5MvVBiwotpQ for <tsvwg@ietfa.amsl.com>; Tue, 18 Nov 2014 10:37:37 -0800 (PST)
Received: from mail-qg0-x22a.google.com (mail-qg0-x22a.google.com [IPv6:2607:f8b0:400d:c04::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B92191A001E for <tsvwg@ietf.org>; Tue, 18 Nov 2014 10:37:36 -0800 (PST)
Received: by mail-qg0-f42.google.com with SMTP id i50so17730614qgf.15 for <tsvwg@ietf.org>; Tue, 18 Nov 2014 10:37:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=dqfsMRqg7Nu0ISUx8luH2uf4KSh/9gMSxaFfSCrLHbk=; b=CUEuUUAEb1nsJpEZv3l5Mf29q37TstvSJ5uAEUKPzJox69eaWFglf93Yg1cYgCW4FB FcniR621X8O5O06qBykSGKOUzwani44hGBI2ZUN47qkdqPYTnTM7stdfmXs5fwxITET0 j84DwtoyXdb3pm7MQVntKGoXPZILmVIx6TQAYGZo1oIVEzZkBT9iBbRQWO8/Hnh/1EIz r0oTfGf+ZGr8Il4unxZ4BR89m4Pqzko8q34wtDijZ0oFjYxmiW1IpECSZGVFv3GwW9tl 5R9MbfsHGGiAdO5SURRglIo++X7krkJrJ+zSIdwtl3kMw26UqzNl3rDPVLTZac778W4p 3MsA==
X-Received: by 10.224.40.202 with SMTP id l10mr21698120qae.7.1416335855955; Tue, 18 Nov 2014 10:37:35 -0800 (PST)
Received: from mtl-morriss-d1.ulticom.com (74-8-208-5.ulticom.com. [74.8.208.5]) by mx.google.com with ESMTPSA id e2sm20910206qac.34.2014.11.18.10.37.35 for <tsvwg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Nov 2014 10:37:35 -0800 (PST)
Message-ID: <546B91EE.4000008@gmail.com>
Date: Tue, 18 Nov 2014 13:37:34 -0500
From: Jeff Morriss <jeff.morriss.ws@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <B91AB8217303A246B7C0455B8229639F2885E2FF@ESESSMB203.ericsson.se> <e4c19dd34a0b4e53c6ac6599de25feee.squirrel@spey.erg.abdn.ac.uk>
In-Reply-To: <e4c19dd34a0b4e53c6ac6599de25feee.squirrel@spey.erg.abdn.ac.uk>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/CGBA5IAgICDkJSkLDOZIeHDTDNE
Subject: Re: [tsvwg] IETF WG state changed to In WG Last Call from WG Document [rev. 08]
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 18 Nov 2014 18:37:39 -0000

In that case I would remind the group of David's email indicating that 
Ulticom's SCTP has had a (simplified, compared to what is in the draft) 
version of fast path failover since ~2001:

http://www.ietf.org/mail-archive/web/tsvwg/current/msg10526.html

It was found long ago to be necessary, as stated below, to avoid 
congestion and delays during path failover.

I agree it is important for this draft to progress: there are 
environments where it is important to maintain throughput even during 
path failover.

On 11/18/14 09:17, gorry@erg.abdn.ac.uk wrote:
> Thanks,
>
> It is really helpful to hear implementation feedback during a LC.
>
> Best wishes,
>
> Gorry
>
> (TSVWG Co-Chair)
>
>
>> Hi TSV Working Group,
>>
>> I have read the WGLC version of the PF draft i.e. Quick Failover Algorithm
>> in SCTP draft-ietf-tsvwg-sctp-failover-08,
>> and I support its progression to RFC.
>>
>> The SCTP PF function is running successfully in various variants in the
>> deployment of the signaling products to alleviate congestion at SCTP path
>> failure. When this WGLC becomes RFC, we will fulfill the RFC in Ericsson's
>> product lines.
>>
>> Many thanks  for the WG work on this draft!
>>
>> Best regards
>>
>> Jun
>> Jun Cheng, Ph.D.
>> Ericsson AB
>> DU Core Networks, PDU Evolved Infrastructure
>> Kistavägen 25
>> 164 80 Stockholm, Sweden
>>
>
>