[midcom] RFC 5190 on Definitions of Managed Objects for Middlebox Communication

rfc-editor@rfc-editor.org Tue, 25 March 2008 21:50 UTC

Return-Path: <midcom-bounces@ietf.org>
X-Original-To: ietfarch-midcom-archive@core3.amsl.com
Delivered-To: ietfarch-midcom-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC93428C5BC; Tue, 25 Mar 2008 14:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.311
X-Spam-Level:
X-Spam-Status: No, score=-100.311 tagged_above=-999 required=5 tests=[AWL=-0.474, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_93=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q3srsP3AA8Xz; Tue, 25 Mar 2008 14:50:46 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C680328C425; Tue, 25 Mar 2008 14:50:40 -0700 (PDT)
X-Original-To: midcom@core3.amsl.com
Delivered-To: midcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E1F23A6B59; Tue, 25 Mar 2008 14:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gvW-NH0vr1Bu; Tue, 25 Mar 2008 14:50:38 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id C495428C10F; Tue, 25 Mar 2008 14:49:50 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id E5D1212105D; Tue, 25 Mar 2008 14:47:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080325214731.E5D1212105D@bosco.isi.edu>
Date: Tue, 25 Mar 2008 14:47:31 -0700
Cc: midcom@ietf.org, rfc-editor@rfc-editor.org
Subject: [midcom] RFC 5190 on Definitions of Managed Objects for Middlebox Communication
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <midcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: midcom-bounces@ietf.org
Errors-To: midcom-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5190

        Title:      Definitions of Managed Objects for 
                    Middlebox Communication 
        Author:     J. Quittek, M. Stiemerling, P. Srisuresh
        Status:     Standards Track
        Date:       March 2008
        Mailbox:    quittek@nw.neclab.eu, 
                    stiemerling@nw.neclab.eu, 
                    srisuresh@yahoo.com
        Pages:      92
        Characters: 204929
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-midcom-mib-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5190.txt

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 5189.  [STANDARDS TRACK]

This document is a product of the Middlebox Communication Working Group 
of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


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