Re: [tcmtf] About the possibility of having a BOF about TCMTF in IETF87

"Jose Saldana" <jsaldana@unizar.es> Fri, 22 February 2013 10:39 UTC

Return-Path: <jsaldana@unizar.es>
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 483D921F8E2C; Fri, 22 Feb 2013 02:39:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.527
X-Spam-Level:
X-Spam-Status: No, score=-6.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6UIHP8wvIV4K; Fri, 22 Feb 2013 02:39:24 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 6D84021F8E20; Fri, 22 Feb 2013 02:39:24 -0800 (PST)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r1MAd9LR012037; Fri, 22 Feb 2013 11:39:15 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'ken carlberg'" <carlberg@g11.org.uk>
References: <003001cdff0e$33658a50$9a309ef0$@unizar.es> <008601ce0db4$e4af6f60$ae0e4e20$@unizar.es> <50F486E8-69AA-4A9D-970C-1F8EC1372B8D@g11.org.uk>
In-Reply-To: <50F486E8-69AA-4A9D-970C-1F8EC1372B8D@g11.org.uk>
Date: Fri, 22 Feb 2013 11:39:16 +0100
Organization: Universidad de Zaragoza
Message-ID: <002801ce10e8$e070f7c0$a152e740$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH4VYfsQr5DqoVbCGYPdBLd2Eoe0AJlfa8LAYNeKsOYEd4jcA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, tsv-area@ietf.org
Subject: Re: [tcmtf] About the possibility of having a BOF about TCMTF in IETF87
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 22 Feb 2013 10:39:25 -0000

Hi Ken,

Sorry for the delay. I think you are talking about Paragraph 5:

5. So the first objective of this group is to specify the protocol stack for
tunneling, compressing and multiplexing traffic flows (TCMTF). Since
standard protocols are being used at each layer, the signaling methods of
those protocols will be used. Interactions with the Working Groups and Areas
in which these protocols are developed can be expected. However, the
development of new compressing, multiplexing or tunneling protocols is not
an objective of this Working Group. In addition, since the current RFC 4170
would be considered as one of the options, this RFC could be obsoleted.

Perhaps this is a bit confusing. When we say "at each layer", we are talking
about "tunneling, compressing and multiplexing" layers. Perhaps this can be
a bit confusing. What about this?:

5. So the first objective of this group is to specify the protocol stack for
tunneling, compressing and multiplexing traffic flows (TCMTF). Since
standard protocols are being used for tunneling, compressing and
multiplexing layers, the signaling methods of those protocols will be used.
Interactions with the Working Groups and Areas in which these protocols are
developed can be expected. However, the development of new compressing,
multiplexing or tunneling protocols is not an objective of this Working
Group. In addition, since the current RFC 4170 would be considered as one of
the options, this RFC could be obsoleted.

Is this what you were asking?

Thanks for your feedback.

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
> ken carlberg
> Enviado el: martes, 19 de febrero de 2013 14:17
> Para: jsaldana@unizar.es
> CC: tcmtf@ietf.org; tsv-area@ietf.org
> Asunto: Re: [tcmtf] About the possibility of having a BOF about TCMTF in
> IETF87
> 
> Hola Jose,
> 
> could you expand a bit more on your text in the proposed charter regarding
> "signaling methods".  Are you speaking in the more general context of
> information stored in headers of various protocol up and down the stack
(ie,
> layers 3, 4, and 5/app)?  Or, are you  speaking of concurrent resource
> signaling protocols like RSVP/RSVP-TE, or path establishment protocols
like
> MPLS?  Or, some combination of both?
> 
> -ken
> 
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf