RE: [midcom] I-D ACTION:draft-ietf-midcom-mib-01.txt
Martin Stiemerling <stiemerling@netlab.nec.de> Thu, 13 May 2004 21:16 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15334 for <midcom-archive@odin.ietf.org>; Thu, 13 May 2004 17:16:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOMsq-00074M-ID for midcom-archive@odin.ietf.org; Thu, 13 May 2004 16:32:49 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DKWmO2027175 for midcom-archive@odin.ietf.org; Thu, 13 May 2004 16:32:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOMkU-0004jM-8A; Thu, 13 May 2004 16:24:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOLip-0006uO-DV for midcom@optimus.ietf.org; Thu, 13 May 2004 15:18:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07468 for <midcom@ietf.org>; Thu, 13 May 2004 15:18:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOLin-00027T-W6 for midcom@ietf.org; Thu, 13 May 2004 15:18:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOLht-0001ai-00 for midcom@ietf.org; Thu, 13 May 2004 15:17:26 -0400
Received: from ftp.netlab.nec.de ([195.37.70.21] helo=ftp.ccrle.nec.de) by ietf-mx with esmtp (Exim 4.12) id 1BOLhH-00013o-00 for midcom@ietf.org; Thu, 13 May 2004 15:16:47 -0400
Received: from [10.1.1.109] (p50840594.dip0.t-ipconnect.de [80.132.5.148]) by ftp.ccrle.nec.de (Postfix) with ESMTP id 8CB6EF674; Thu, 13 May 2004 21:21:51 +0200 (CEST)
Date: Thu, 13 May 2004 21:16:31 +0200
From: Martin Stiemerling <stiemerling@netlab.nec.de>
To: mbhatia@nextone.com, midcom@ietf.org
Subject: RE: [midcom] I-D ACTION:draft-ietf-midcom-mib-01.txt
Message-ID: <2147483647.1084482991@[10.0.1.2]>
In-Reply-To: <200405130218.WAA09404@warspite.cnchost.com>
References: <200405130218.WAA09404@warspite.cnchost.com>
X-Mailer: Mulberry/3.1.2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit
Hi, There is now parameter/option to tell the middlebox how it should allocated IP addresses/port numbers. This is up to the actual implementation of the box and/or the MIDCOM stack. Martin --On Mittwoch, 12. Mai 2004 22:18 Uhr -0400 Medhavi Bhatia <mbhatia@nextone.com> wrote: | 7bit | MIME-Version: 1.0 | Content-Type: text/plain; charset="us-ascii" | Content-Transfer-Encoding: 7bit | 7bit | | I have not completely gone through the mib yet, but going through the | semantics documents and the requirements, I did not see anything which | points to how the midcom agent can direct the middlebox to use symmetric | ip/port (ie., the address from which the middle box sends traffic towards | an endpoint A is the same as the address where traffic is being received | from A). None of the signaling protocols (SIP etc) require this, but it | would be interesting to see if there is any option provided for this. | | -Medhavi. | |> -----Original Message----- |> From: midcom-admin@ietf.org [mailto:midcom-admin@ietf.org] On Behalf Of | Melinda |> Shore |> Sent: Wednesday, May 12, 2004 2:21 PM |> To: midcom@ietf.org |> Subject: Fwd: [midcom] I-D ACTION:draft-ietf-midcom-mib-01.txt |> |> This is our final deliverable - the end is in sight. Please give the |> draft a careful read and post comments to the mailing list. WG review |> is, |> perhaps, the most important stage in moving documents towards |> publication, |> and this is the time to catch and fix any problems that may lurk in the |> draft. |> |> Thanks, |> |> Melinda |> |> |> Begin forwarded message: |> |> > From: Internet-Drafts@ietf.org |> > Date: Wed May 12, 2004 9:41:12 AM US/Eastern |> > To: i-d-announce@ietf.org |> > Cc: midcom@ietf.org |> > Subject: [midcom] I-D ACTION:draft-ietf-midcom-mib-01.txt |> > |> > A New Internet-Draft is available from the on-line Internet-Drafts |> > directories. |> > This draft is a work item of the Middlebox Communication Working Group |> > of the IETF. |> > |> > Title : Definitions of Managed Objects for Middlebox |> > Communication |> > Author(s) : J. Quittek, et al. |> > Filename : draft-ietf-midcom-mib-01.txt |> > Pages : 82 |> > Date : 2004-5-11 |> > |> > This memo defines a portion of the Management Information Base (MIB) |> > for use with network management protocols in the Internet community. |> > In particular, it describes a set of managed objects that allow |> > configuring middleboxes, such as firewalls and network address |> > translators, in order to enable communication across these devices. |> > The definitions of managed objects in this documents follow closely |> > the MIDCOM semantics defined in RFC XXXX. |> > |> > A URL for this Internet-Draft is: |> > http://www.ietf.org/internet-drafts/draft-ietf-midcom-mib-01.txt |> > |> > To remove yourself from the I-D Announcement list, send a message to |> > i-d-announce-request@ietf.org with the word unsubscribe in the body of |> > the message. |> > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce |> > to change your subscription settings. |> > |> > |> > Internet-Drafts are also available by anonymous FTP. Login with the |> > username |> > "anonymous" and a password of your e-mail address. After logging in, |> > type "cd internet-drafts" and then |> > "get draft-ietf-midcom-mib-01.txt". |> > |> > A list of Internet-Drafts directories can be found in |> > http://www.ietf.org/shadow.html |> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt |> > |> > |> > Internet-Drafts can also be obtained by e-mail. |> > |> > Send a message to: |> > mailserv@ietf.org. |> > In the body type: |> > "FILE /internet-drafts/draft-ietf-midcom-mib-01.txt". |> > |> > NOTE: The mail server at ietf.org can return the document in |> > MIME-encoded form by using the "mpack" utility. To use this |> > feature, insert the command "ENCODING mime" before the "FILE" |> > command. To decode the response(s), you will need "munpack" or |> > a MIME-compliant mail reader. Different MIME-compliant mail readers |> > exhibit different behavior, especially when dealing with |> > "multipart" MIME messages (i.e. documents which have been split |> > up into multiple messages), so check your local documentation on |> > how to manipulate these messages. |> > |> > |> > Below is the data which will enable a MIME compliant mail reader |> > implementation to automatically retrieve the ASCII version of the |> > Internet-Draft. |> > Content-Type: text/plain |> > Content-ID: <2004-5-12094156.I-D@ietf.org> |> |> |> _______________________________________________ |> 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] I-D ACTION:draft-ietf-midcom-mib-01.txt Internet-Drafts
- Fwd: [midcom] I-D ACTION:draft-ietf-midcom-mib-01… Melinda Shore
- RE: [midcom] I-D ACTION:draft-ietf-midcom-mib-01.… Medhavi Bhatia
- RE: [midcom] I-D ACTION:draft-ietf-midcom-mib-01.… Christopher A. Martin
- RE: [midcom] I-D ACTION:draft-ietf-midcom-mib-01.… Martin Stiemerling
- RE: [midcom] I-D ACTION:draft-ietf-midcom-mib-01.… Harrington, David
- Re: [midcom] I-D ACTION:draft-ietf-midcom-mib-01.… Juergen Schoenwaelder
- RE: [midcom] I-D ACTION:draft-ietf-midcom-mib-01.… Christopher A. Martin
- RE: [midcom] I-D ACTION:draft-ietf-midcom-mib-01.… Christopher A. Martin