RE: [midcom] Midcom protocol specification and status
"Mary Barnes"<mbarnes@nortelnetworks.com> Fri, 24 May 2002 21:59 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16703 for <midcom-archive@odin.ietf.org>; Fri, 24 May 2002 17:59:01 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id RAA24351 for midcom-archive@odin.ietf.org; Fri, 24 May 2002 17:59:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA24186; Fri, 24 May 2002 17:56:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA24158 for <midcom@optimus.ietf.org>; Fri, 24 May 2002 17:55:57 -0400 (EDT)
Received: from zrc2s0jx.us.nortel.com (zrc2s0jx.nortelnetworks.com [47.103.122.112]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16539 for <midcom@ietf.org>; Fri, 24 May 2002 17:55:31 -0400 (EDT)
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51]) by zrc2s0jx.us.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g4OLtRQ15375; Fri, 24 May 2002 16:55:28 -0500 (CDT)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19) id <KKXXVHXW>; Fri, 24 May 2002 16:55:15 -0500
Message-ID: <1B54FA3A2709D51195C800508BF9386A03DE3B65@zrc2c000.us.nortel.com>
From: Mary Barnes <mbarnes@nortelnetworks.com>
To: "'thuang@codentnetworks.com'" <thuang@codentnetworks.com>, Mark Pietras <mpietras@aravox.com>, midcom@ietf.org
Subject: RE: [midcom] Midcom protocol specification and status
Date: Fri, 24 May 2002 16:55:13 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2036D.AECE4EF0"
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <midcom.ietf.org>
X-BeenThere: midcom@ietf.org
The MIDCOM protocol evaluation document (for which I'm the editor) will be submitted very soon - I'm in the midst of completing edits. It should be in your mailbox by Monday morning. The purpose of this evaluation was to evaluate existing protocols as the MIDCOM protocol with the following being considered: SNMP: http://www.ietf.org/internet-drafts/draft-quittek-midcom-snmp-eval-00.txt DIAMETER: http://www.ietf.org/internet-drafts/draft-taylor-midcom-diameter-eval-01.txt RSIP: http://www.ietf.org/internet-drafts/draft-renkel-rsip-midcom-eval-01.txt MEGACO: http://www.ietf.org/internet-drafts/draft-sct-midcom-megaco-02.txt COPS: http://www.ietf.org/internet-drafts/draft-aoun-midcom-cops-02.txt I would suggest that you wait till Monday rather than review these individual drafts as the majority of the content is being edited into the WG draft and comments need to be directed at that document rather than to the individual ones going forward. Regards, Mary H. Barnes mbarnes@nortelnetworks.com 972-684-5432 Wireless 817-703-4806 -----Original Message----- From: Thomas Huang [mailto:thuang@codentnetworks.com] Sent: Friday, May 24, 2002 12:23 PM To: Mark Pietras; midcom@ietf.org Subject: RE: [midcom] Midcom protocol specification and status Hello Mark, Thank you very much for the info and update. Would you be kind enough to email some proposed protocol drafts that may make their way to publication? I got the impression that you are involved in the reviewing them and drafting. It apears that this MIDCOM framework/architecture would provide the solution for complete new deployment using this type of controllable middlebox. However are there efforts also in the making also addressing the deployment of voip in existing FW/NAT environment? I studied some sip/rtp proxy drafts from SIP/SIPPING group as well as some early packet relay in MGCP drafts. Is this group trying to consolidate the different approaches? as the one I mentioned? You said companies have started to build the boxes based on midcom architecture and some in production. I know Cisco doesn't offer it yet (to my limited knowledge). How could customers be assured that the boxes/hardware they buy today will be upgradable when there is a standard? Could you please kindly tell me if I could find the active member list of this midcom working group? Regards, Thomas -----Original Message----- From: midcom-admin@ietf.org [mailto:midcom-admin@ietf.org]On Behalf Of Mark Pietras Sent: Friday, May 24, 2002 7:42 AM To: thuang@codentnetworks.com; midcom@ietf.org Subject: RE: [midcom] Midcom protocol specification and status Thomas, - There is no protocol specification at this point. The work is in progress. Currently the working group is doing two things: 1) working the STUN portion of the current charter which addresses short-term needs and a specific market, and 2) working the protocol portion of the current charter by evaluating several different protocol proposals against the framework/requirements docs as candidates for the actual Midcom protocol. - There are several vendors developing "Midcom boxes" currently. Some even have some in production networks. They generally follow the Midcom architecture, but currently use different protocols for policy control as there is no standard yet. Hence the current charter of this working group. Most of the vendors actively work in or at least follow this group, so I'm sure each would suggest they "lead the pack." Mark. -----Original Message----- From: midcom-admin@ietf.org [mailto:midcom-admin@ietf.org] On Behalf Of Thomas Huang Sent: Friday, May 24, 2002 11:23 AM To: midcom@ietf.org Subject: [midcom] Midcom protocol specification and status I have studied the three major doc in the repository: - Midcom architecture and framework - Midcom requirement - STUN But I can't find the MidCom protocol specification itself. Could you please help? - any draft spec that this group is working on - what's the concensus among the group and other related groups about midcom (SIP, MGCP, MEGACO) - Are there vendors starting to develop midcom boxes following the architecture? I am in the process of meeting a couple of vendors, but they don't say in literature what they follow. If yes, who are leading the pack? Thanks for any help. Thomas _______________________________________________ midcom mailing list midcom@ietf.org https://www1.ietf.org/mailman/listinfo/midcom _______________________________________________ midcom mailing list midcom@ietf.org https://www1.ietf.org/mailman/listinfo/midcom _______________________________________________ midcom mailing list midcom@ietf.org https://www1.ietf.org/mailman/listinfo/midcom
- [midcom] Midcom protocol specification and status Thomas Huang
- RE: [midcom] Midcom protocol specification and st… Mark Pietras
- RE: [midcom] Midcom protocol specification and st… Thomas Huang
- RE: [midcom] Midcom protocol specification and st… Mark Pietras
- RE: [midcom] Midcom protocol specification and st… Mary Barnes