Re: [tcmtf] Backwards compatibility with RFC4170

"Jose Saldana" <jsaldana@unizar.es> Wed, 05 March 2014 16:21 UTC

Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 051621A01ED for <tcmtf@ietfa.amsl.com>; Wed, 5 Mar 2014 08:21:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level:
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, 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 LE03JBCjM_GT for <tcmtf@ietfa.amsl.com>; Wed, 5 Mar 2014 08:21:31 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 9895D1A01BF for <tcmtf@ietf.org>; Wed, 5 Mar 2014 08:21:30 -0800 (PST)
Received: from jsaldanapc (dhcp-a32b.meeting.ietf.org [31.133.163.43]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id s25GLNZt011610; Wed, 5 Mar 2014 17:21:24 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Brian Trammell'" <ietf@trammell.ch>, <tcmtf@ietf.org>
Date: Wed, 5 Mar 2014 16:21:25 -0000
Message-ID: <011b01cf388e$f5155080$df3ff180$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac84jLntXgvsinnZTxGcjVHdIZypUw==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Archived-At: http://mailarchive.ietf.org/arch/msg/tcmtf/o7Gan8wY2z8vaqWOKnKJXim9caw
Subject: Re: [tcmtf] Backwards compatibility with RFC4170
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf/>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Mar 2014 16:21:33 -0000

Hi, Brian, thanks for the summary of the BoF:

It is clear that RFC4170 is one of the options of the tcmtf stack. If people
think we should maintain backwards compatibility instead of obsoleting it,
we should modify three sentences of the draft:
(http://www.ietf.org/mail-archive/web/tcmtf/current/msg00493.html) 

The current charter draft (v11) says:

"3. So there is a need of replacing RFC4170 with an extended solution able
to optimize these new flows ..."

"5. (...) In addition, since the current RFC 4170 would be considered as one
of the options, this RFC would be obsoleted."

"Goals and Milestones
	
Specification of TCM-TF reference model and the scenarios of interest. This
would obsolete RFC4170."


The new version could say instead:

"3. So there is a need of adding new options to the one considered in
RFC4170, thus building an extended solution able to optimize these new
flows..."

"5. (...) In addition, backwards compatibility with RFC 4170 will be
granted, since it will be considered as one of the optimization options."

"Goals and Milestones
	
Specification of TCM-TF reference model and the scenarios of interest.
Backwards compatibility with RFC4170 will be granted."


What do you think?

Jose

> -----Mensaje original-----
> De: tcmtf [mailto:tcmtf-bounces@ietf.org] En nombre de Brian Trammell
> Enviado el: miƩrcoles, 05 de marzo de 2014 13:51
> Para: tcmtf@ietf.org
> Asunto: [tcmtf] Thank you for a great BoF!
> 
> Greetings, all,
> 
> Thanks to everyone for yesterday's BoF. We got lots of good input, and a
> better handle on what a future TCMTF WG might look like.
> 
> There are a few issues we identified that we'll have to take into
> consideration for a new draft of the charter:
> 
> (1) make it clear that backward compatibility with RFC 4170 is a goal.
> 
> (2) an applicability statement, which explains applications that benefit
from
>     TCMTF and the situations for which it is likely useful, and
applications
>     and situations for which it is not. This should address interactions
between
>     TCMTF tunnels and TCP cross traffic sharing a bottleneck link.
> 
> (3) interactions with how this interacts with diverse lower layers,
especially
>     with respect to different delay tolerances, will have to be
considered.
> 
> And we'd really more input from vendors already building boxes in this
> space, and operators deploying them, as input to scoping and
applicability.
> 
> Best regards,
> 
> Mirja and Brian (second TCMTF BoF chairs)
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf