IETF Logo Mail Archive

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

ken carlberg <carlberg@g11.org.uk> Tue, 19 February 2013 13:17 UTC

Return-Path: <carlberg@g11.org.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 9330521F8CBF; Tue, 19 Feb 2013 05:17:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
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 3bCZf-TLC0iD; Tue, 19 Feb 2013 05:17:18 -0800 (PST)
Received: from portland.eukhosting.net (portland.eukhosting.net [92.48.97.5]) by ietfa.amsl.com (Postfix) with ESMTP id A3C6E21F8CB1; Tue, 19 Feb 2013 05:17:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=g11.org.uk; s=default; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=lmMmwltiqZIfgDLUSCw71VK1hTWi/YfiIdKGnWDrBwo=; b=xq5ZgxFyfegkrScX+lCOPR0kOooxs5UZhmezNN/vw5yi23XmA9k2DhAwSO1z38hstX7maorbuQJhhQT4keQrVJCiaoW3neW7Qa87cu5jzmdu2NMGQ5EfpGF2Euk3lVda;
Received: from c-98-218-170-72.hsd1.va.comcast.net ([98.218.170.72]:33293 helo=[10.0.1.20]) by portland.eukhosting.net with esmtp (Exim 4.80) (envelope-from <carlberg@g11.org.uk>) id 1U7n4M-000Yl7-Fl; Tue, 19 Feb 2013 13:17:14 +0000
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: ken carlberg <carlberg@g11.org.uk>
In-Reply-To: <008601ce0db4$e4af6f60$ae0e4e20$@unizar.es>
Date: Tue, 19 Feb 2013 08:17:13 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <50F486E8-69AA-4A9D-970C-1F8EC1372B8D@g11.org.uk>
References: <003001cdff0e$33658a50$9a309ef0$@unizar.es> <008601ce0db4$e4af6f60$ae0e4e20$@unizar.es>
To: jsaldana@unizar.es
X-Mailer: Apple Mail (2.1499)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - portland.eukhosting.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - g11.org.uk
X-Get-Message-Sender-Via: portland.eukhosting.net: acl_c_relayhosts_text_entry: carlberg@g11.org.uk|g11.org.uk
X-Mailman-Approved-At: Tue, 19 Feb 2013 10:46:36 -0800
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
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: Tue, 19 Feb 2013 13:17:19 -0000

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

v2.8.7 | Report a Bug | By Email