RFC 4295 on Mobile IPv6 Management Information Base

rfc-editor@rfc-editor.org Tue, 11 April 2006 23:25 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FTSF2-00056J-PN; Tue, 11 Apr 2006 19:25:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FTSF0-00052G-Vv; Tue, 11 Apr 2006 19:25:46 -0400
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTSEz-0001If-KL; Tue, 11 Apr 2006 19:25:46 -0400
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k3BNPjXl023601; Tue, 11 Apr 2006 16:25:45 -0700
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k3BNPj3d023600; Tue, 11 Apr 2006 16:25:45 -0700
Date: Tue, 11 Apr 2006 16:25:45 -0700
Message-Id: <200604112325.k3BNPj3d023600@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: mip6@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4295 on Mobile IPv6 Management Information Base
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
Status: O

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

        
        RFC 4295

        Title:      Mobile IPv6 Management Information Base 
        Author:     G. Keeni, K. Koide,
                    K. Nagami, S. Gundavelli
        Status:     Standards Track
        Date:       April 2006
        Mailbox:    glenn@cysols.com, 
                    koide@shiratori.riec.tohoku.ac.jp, 
                    nagami@inetcore.com,  sgundave@cisco.com
        Pages:      109
        Characters: 209038
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mip6-mipv6-mib-07.txt

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

This memo defines a portion of the Management Information Base (MIB),
the Mobile-IPv6 MIB, for use with network management protocols
in the Internet community.  In particular, the Mobile-IPv6 MIB will be
used to monitor and control the mobile node, home agent, and
correspondent node functions of a Mobile IPv6 (MIPv6) entity.  [STANDARDS 
TRACK]

This document is a product of the Mobility for IPv6
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.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce