IETF Logo Mail Archive

Re: [midcom] clarification requested on middlebox concept

Melinda Shore <mshore@cisco.com> Wed, 27 November 2002 15:50 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15768 for <midcom-archive@odin.ietf.org>; Wed, 27 Nov 2002 10:50:23 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gARFqeL02848 for midcom-archive@odin.ietf.org; Wed, 27 Nov 2002 10:52:40 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARFqAv02808; Wed, 27 Nov 2002 10:52:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARFpYv02719 for <midcom@optimus.ietf.org>; Wed, 27 Nov 2002 10:51:34 -0500
Received: from sj-msg-core-4.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15648 for <midcom@ietf.org>; Wed, 27 Nov 2002 10:48:47 -0500 (EST)
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-msg-core-4.cisco.com (8.12.2/8.12.2) with ESMTP id gARFpUcb004610; Wed, 27 Nov 2002 07:51:30 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA) with ESMTP id ABA24192; Wed, 27 Nov 2002 07:51:29 -0800 (PST)
Message-Id: <200211271551.ABA24192@mira-sjc5-c.cisco.com>
To: Jerome Moisand <jmoisand@yahoo.com>
cc: midcom@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: [midcom] clarification requested on middlebox concept
In-Reply-To: Message from "Jerome Moisand" <jmoisand@yahoo.com> of "Wed, 27 Nov 2002 10:40:25 EST." <002501c2962b$4ee6bda0$8482accf@cable.rcn.com>
Date: Wed, 27 Nov 2002 10:51:29 -0500
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Id: <midcom.ietf.org>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=subscribe>

> In any case, it seems to me that we should keep in mind a bigger picture =
> where such 'midcom' transaction (say triggered by a SIP proxy of some =
> sort, or a Video app server, etc) would not only act in the NAT/FW side =
> of things, but also on the QoS side of things.

QoS is specifically out of scope.

> Sure, in such a larger picture, some may argue that the RSVP scheme from =
> a CPE device is the way to go. 

The NSIS working group is discussing an RSVP-like protocol
that will be used for QoS signaling and also middlebox
communication. 

> PS. going down this "multimedia control" route also begs the question of =
> why MGCP/Megaco was not considered as a possible 'midcom' protocol =
> candidate? 

It is still in the running - please read draft-ietf-midcom-
protocol-eval-06.txt.

Melinda
_______________________________________________
midcom mailing list
midcom@ietf.org
https://www1.ietf.org/mailman/listinfo/midcom

v2.23.0 | Report a Bug | By Email