From ifmib-admin@ietf.org Wed Oct 15 21:11:58 2003 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01778; Wed, 15 Oct 2003 21:11:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9wgO-00069i-00; Wed, 15 Oct 2003 21:12:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A9wgO-00069d-00; Wed, 15 Oct 2003 21:12:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9wgM-0003MR-R4; Wed, 15 Oct 2003 21:12:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9wfO-0003IQ-Sz for ifmib@optimus.ietf.org; Wed, 15 Oct 2003 21:11:02 -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 VAA01763; Wed, 15 Oct 2003 21:10:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9wfL-00069O-00; Wed, 15 Oct 2003 21:11:00 -0400 Received: from mail1.microsoft.com ([131.107.3.125]) by ietf-mx with esmtp (Exim 4.12) id 1A9wfL-000699-00; Wed, 15 Oct 2003 21:10:59 -0400 Received: from inet-vrs-01.redmond.corp.microsoft.com ([157.54.8.27]) by mail1.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 15 Oct 2003 18:11:16 -0700 Received: from 157.54.8.155 by inet-vrs-01.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 15 Oct 2003 18:10:29 -0700 Received: from RED-IMC-04.redmond.corp.microsoft.com ([157.54.2.168]) by inet-hub-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 15 Oct 2003 18:10:29 -0700 Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by RED-IMC-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 15 Oct 2003 18:10:28 -0700 Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069); Wed, 15 Oct 2003 18:10:27 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7097.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 15 Oct 2003 18:10:27 -0700 Message-ID: Thread-Topic: FW: I-D ACTION:draft-thaler-inet-tunnel-mib-00.txt thread-index: AcOTgkkiKz8LLHKNRBu5B6Bhh1pt5w== From: "Dave Thaler" To: , , X-OriginalArrivalTime: 16 Oct 2003 01:10:27.0860 (UTC) FILETIME=[49237D40:01C39382] Content-Transfer-Encoding: quoted-printable Subject: [ifmib] FW: I-D ACTION:draft-thaler-inet-tunnel-mib-00.txt Sender: ifmib-admin@ietf.org Errors-To: ifmib-admin@ietf.org X-BeenThere: ifmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Interfaces MIB working group mailing list. List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Forwarding this announcement to the most relevant WG's... RFC 2667, entitled "IP Tunnel MIB", only supported=20 point-to-point tunnels over IPv4. This draft updates=20 RFC 2667 to also support tunnels over IPv6, as well as=20 tunnels which aren't just point-to-point (e.g. 6to4). It also clarifies the use of the ifRcvAddressTable for all tunnels. It uses the InetAddress types like the other MIBs that have been done by the IPv6MIB Design Team. -Dave * To: IETF-Announce: ;=20 * Subject: I-D ACTION:draft-thaler-inet-tunnel-mib-00.txt=20 * From: Internet-Drafts@ietf.org=20 * Date: Tue, 14 Oct 2003 15:35:25 -0400=20 * Reply-to: Internet-Drafts@ietf.org=20 * Sender: owner-ietf-announce@ietf.org=20 ________________________________________ A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IP Tunnel MIB Author(s) : D. Thaler Filename : draft-thaler-inet-tunnel-mib-00.txt Pages : 26 Date : 2003-10-14 =09 This memo defines a Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing tunnels of any type over IPv4 and IPv6 networks. Extension MIBs may be designed for managing protocol-specific objects. Likewise, extension MIBs may be designed for managing security-specific objects. This MIB does not support tunnels over non-IP networks. Management of such tunnels may be supported by other MIBs. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-thaler-inet-tunnel-mib-00.txt To remove yourself from the IETF Announcement list, send a message to=20 ietf-announce-request with the word unsubscribe in the body of the message. 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-thaler-inet-tunnel-mib-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html=20 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-thaler-inet-tunnel-mib-00.txt". =09 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. =09 =09 Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ ifmib mailing list ifmib@ietf.org https://www1.ietf.org/mailman/listinfo/ifmib