Re: [tcmtf] Showing the interest of the Industry on TCMTF
gorry@erg.abdn.ac.uk Fri, 17 May 2013 14:16 UTC
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id B382C21F8895 for <tcmtf@ietfa.amsl.com>;
Fri, 17 May 2013 07:16:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nixRKP3HukEU for
<tcmtf@ietfa.amsl.com>; Fri, 17 May 2013 07:16:30 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by
ietfa.amsl.com (Postfix) with ESMTP id 57B3A21F896B for <tcmtf@ietf.org>;
Fri, 17 May 2013 07:16:30 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by
spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 80C7E2B44A7;
Fri, 17 May 2013 15:16:29 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by
www.erg.abdn.ac.uk with HTTP; Fri, 17 May 2013 15:16:29 +0100
Message-ID: <611de400a979a43b57417b2c1ecf3945.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <00d601ce52d6$7bd5a100$7380e300$@unizar.es>
References: <00d601ce52d6$7bd5a100$7380e300$@unizar.es>
Date: Fri, 17 May 2013 15:16:29 +0100
From: gorry@erg.abdn.ac.uk
To: jsaldana@unizar.es
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Showing the interest of the Industry on TCMTF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 17 May 2013 14:16:36 -0000
That's interesting to discuss the existing vendor specs. So, if (for example CISCO) is able to invest energy in writing and implementing the spec - it could be useful to know who else also wants interoperability with a new Spec? Gorry > Hi all, > > Gorry raised this question: we have to show the interest of the Industry > on the standardization of TCMTF. > > Some Cisco devices implement similar (proprietary) multiplexing schemes, > mainly with the idea of saving pps in VoIP for pps-constrained links (e.g. > satellites): > > > http://www.cisco.com/web/strategy/docs/gov/data_sheet_c78-697643_v1.pdf > > > http://www.cisco.com/web/strategy/docs/gov/aag_c45-697642_v2.pdf > > > > So an IETF standard would be interesting for > > - interoperating with other manufacturers' devices. > > - defining a standard way for multiplexing non-RTP flows > > > > Best regards, > > > > Jose > > > > _______________________________________________ > tcmtf mailing list > tcmtf@ietf.org > https://www.ietf.org/mailman/listinfo/tcmtf >