From ietfmibs-bounces@ietf.org Tue Dec 2 13:08:35 2008 Return-Path: X-Original-To: ietfmibs-archive@optimus.ietf.org Delivered-To: ietfarch-ietfmibs-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E88628C1DA; Tue, 2 Dec 2008 13:08:35 -0800 (PST) X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86CA328C1DA for ; Tue, 2 Dec 2008 13:08:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.87 X-Spam-Level: X-Spam-Status: No, score=-1.87 tagged_above=-999 required=5 tests=[AWL=-0.729, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457] 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 yvrsZ8Igs12B for ; Tue, 2 Dec 2008 13:08:32 -0800 (PST) Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by core3.amsl.com (Postfix) with ESMTP id EA9783A67B5 for ; Tue, 2 Dec 2008 13:08:32 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 6681C1ECB20; Tue, 2 Dec 2008 13:08:29 -0800 (PST) Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08895-08; Tue, 2 Dec 2008 13:08:29 -0800 (PST) Received: from [155.53.44.238] (nurnberg.redback.com [155.53.44.238]) by prattle.redback.com (Postfix) with ESMTP id 501741ECB1F; Tue, 2 Dec 2008 13:08:29 -0800 (PST) Message-ID: <4935A3CD.4000504@redback.com> Date: Tue, 02 Dec 2008 13:08:29 -0800 From: Michael Thatcher User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: ietfmibs@ietf.org X-Virus-Scanned: by amavisd-new at redback.com Subject: [IETFMIBS] a question about the Entity MIB X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0202777397==" Sender: ietfmibs-bounces@ietf.org Errors-To: ietfmibs-bounces@ietf.org --===============0202777397== Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Is there some way to extend the PhysicalClass Textual Convention to include disks & memory, & other removable physical devices. Since this TC is not supported by IANA, is there some other authority which can "easily" extend this

mike thatcher
--===============0202777397== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IETFMIBS mailing list IETFMIBS@ietf.org https://www.ietf.org/mailman/listinfo/ietfmibs --===============0202777397==-- From ietfmibs-bounces@ietf.org Wed Dec 3 02:07:00 2008 Return-Path: X-Original-To: ietfmibs-archive@optimus.ietf.org Delivered-To: ietfarch-ietfmibs-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 389A63A68B1; Wed, 3 Dec 2008 02:07:00 -0800 (PST) X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A2A33A6B4F for ; Wed, 3 Dec 2008 02:06:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.408 X-Spam-Level: X-Spam-Status: No, score=-2.408 tagged_above=-999 required=5 tests=[AWL=0.190, BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 3r9r-k8oSj-2 for ; Wed, 3 Dec 2008 02:06:57 -0800 (PST) Received: from co300216-co-outbound.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 5EEAA3A68B1 for ; Wed, 3 Dec 2008 02:06:57 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.33,708,1220241600"; d="scan'208,217";a="153160509" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.avaya.com with ESMTP; 03 Dec 2008 05:06:52 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 03 Dec 2008 05:06:52 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 3 Dec 2008 11:06:50 +0100 Message-ID: In-Reply-To: <4935A3CD.4000504@redback.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IETFMIBS] a question about the Entity MIB Thread-Index: AclUwiSEP1+zaGRsSW61icJpkPOZ7gAaizTg References: <4935A3CD.4000504@redback.com> From: "Romascanu, Dan (Dan)" To: "Michael Thatcher" , Subject: Re: [IETFMIBS] a question about the Entity MIB X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2116740914==" Sender: ietfmibs-bounces@ietf.org Errors-To: ietfmibs-bounces@ietf.org This is a multi-part message in MIME format. --===============2116740914== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9552E.DCD5F4BA" This is a multi-part message in MIME format. ------_=_NextPart_001_01C9552E.DCD5F4BA Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Hi Mike, =20 You are correct, the PhysicalClass TC does not cover disks and memory or other removable devices. The work-around with the current TC is to use one of the values other(1) or module(9) and provide more detailed information in a proprietary object. Extending this TC is not possible unless the MIB module defined in RFC4133 is revised.=20 =20 Dan =20 ________________________________ From: ietfmibs-bounces@ietf.org [mailto:ietfmibs-bounces@ietf.org] On Behalf Of Michael Thatcher Sent: Tuesday, December 02, 2008 11:08 PM To: ietfmibs@ietf.org Subject: [IETFMIBS] a question about the Entity MIB =09 =09 Is there some way to extend the PhysicalClass Textual Convention to include disks & memory, & other removable physical devices. Since this TC is not supported by IANA, is there some other authority which can "easily" extend this =09 mike thatcher =09 ------_=_NextPart_001_01C9552E.DCD5F4BA Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Hi Mike,

You are correct, the PhysicalClass TC does not cover disks and = memory or=20 other removable devices. The work-around with the current TC is to use = one of=20 the values other(1) or module(9) and provide more detailed information = in a=20 proprietary object. Extending this TC is not possible unless the MIB = module=20 defined in RFC4133 is revised.

Dan

From: ietfmibs-bounces@ietf.org=20 [mailto:ietfmibs-bounces@ietf.org] On Behalf Of Michael=20 Thatcher
Sent: Tuesday, December 02, 2008 11:08 = PM
To:=20 ietfmibs@ietf.org
Subject: [IETFMIBS] a question about the = Entity=20 MIB

Is there some way to extend the=20 PhysicalClass Textual Convention to include disks & memory, & = other=20 removable physical devices. Since this TC is not supported by = IANA, is=20 there some other authority which can "easily" extend this

mike=20 thatcher
------_=_NextPart_001_01C9552E.DCD5F4BA-- --===============2116740914== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IETFMIBS mailing list IETFMIBS@ietf.org https://www.ietf.org/mailman/listinfo/ietfmibs --===============2116740914==-- From ietfmibs-bounces@ietf.org Wed Dec 3 06:14:21 2008 Return-Path: X-Original-To: ietfmibs-archive@optimus.ietf.org Delivered-To: ietfarch-ietfmibs-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF4263A6A00; Wed, 3 Dec 2008 06:14:21 -0800 (PST) X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BFC243A6A00 for ; Wed, 3 Dec 2008 06:14:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 DjCkTiMirpAg for ; Wed, 3 Dec 2008 06:14:17 -0800 (PST) Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 0EBC43A68C5 for ; Wed, 3 Dec 2008 06:14:16 -0800 (PST) Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id mB3EECle020364 for ; Wed, 3 Dec 2008 09:14:12 -0500 Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id mB3EECsM020343; Wed, 3 Dec 2008 09:14:12 -0500 Received: from IMCMBX2.MITRE.ORG ([129.83.29.209]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Wed, 3 Dec 2008 09:14:11 -0500 From: "Natale, Bob" To: "Romascanu, Dan (Dan)" , Michael Thatcher Date: Wed, 3 Dec 2008 09:14:11 -0500 Thread-Topic: [IETFMIBS] a question about the Entity MIB Thread-Index: AclUwiSEP1+zaGRsSW61icJpkPOZ7gAaizTgAAk9FnA= Message-ID: <17969D855F28964C88D177D45B6CDF11CF5A0A96@IMCMBX2.MITRE.ORG> References: <4935A3CD.4000504@redback.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "ietfmibs@ietf.org" Subject: Re: [IETFMIBS] a question about the Entity MIB X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1054011499==" Sender: ietfmibs-bounces@ietf.org Errors-To: ietfmibs-bounces@ietf.org --===============1054011499== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_17969D855F28964C88D177D45B6CDF11CF5A0A96IMCMBX2MITREORG_" --_000_17969D855F28964C88D177D45B6CDF11CF5A0A96IMCMBX2MITREORG_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable What does it mean to say "Since this TC is not supported by IANA"? From: ietfmibs-bounces@ietf.org [mailto:ietfmibs-bounces@ietf.org] On Behal= f Of Romascanu, Dan (Dan) Sent: Wednesday, December 03, 2008 5:07 AM To: Michael Thatcher; ietfmibs@ietf.org Subject: Re: [IETFMIBS] a question about the Entity MIB Hi Mike, You are correct, the PhysicalClass TC does not cover disks and memory or ot= her removable devices. The work-around with the current TC is to use one of= the values other(1) or module(9) and provide more detailed information in = a proprietary object. Extending this TC is not possible unless the MIB modu= le defined in RFC4133 is revised. Dan ________________________________ From: ietfmibs-bounces@ietf.org [mailto:ietfmibs-bounces@ietf.org] On Behal= f Of Michael Thatcher Sent: Tuesday, December 02, 2008 11:08 PM To: ietfmibs@ietf.org Subject: [IETFMIBS] a question about the Entity MIB Is there some way to extend the PhysicalClass Textual Convention to include= disks & memory, & other removable physical devices. Since this TC is not = supported by IANA, is there some other authority which can "easily" extend = this mike thatcher --_000_17969D855F28964C88D177D45B6CDF11CF5A0A96IMCMBX2MITREORG_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

What does it mean to say “Since this TC is not supporte= d by IANA”?

From: ietfmibs-bounces@ietf.org [mailto:ietfmibs-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)=
Sent: Wednesday, December 03, 2008 5:07 AM
To: Michael Thatcher; ietfmibs@ietf.org
Subject: Re: [IETFMIBS] a question about the Entity MIB

Hi Mike,<= /o:p>

You are correct, the PhysicalC= lass TC does not cover disks and memory or other removable devices. The work-aro= und with the current TC is to use one of the values other(1) or module(9) and provide more detailed information in a proprietary object. Extending this T= C is not possible unless the MIB module defined in RFC4133 is revised.

Dan=

From: ietfmibs-boun= ces@ietf.org [mailto:ietfmibs-bounces@ietf.org] On Behalf Of Michael Thatcher
Sent: Tuesday, December 02, 2008 11:08 PM
To: ietfmibs@ietf.org
Subject: [IETFMIBS] a question about the Entity MIB

Is there some way to extend the PhysicalClass Textual Convention to include di= sks & memory, & other removable physical devices. Since this TC i= s not supported by IANA, is there some other authority which can "easily" extend this

mike thatcher

--_000_17969D855F28964C88D177D45B6CDF11CF5A0A96IMCMBX2MITREORG_-- --===============1054011499== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IETFMIBS mailing list IETFMIBS@ietf.org https://www.ietf.org/mailman/listinfo/ietfmibs --===============1054011499==-- From ietfmibs-bounces@ietf.org Wed Dec 3 08:16:10 2008 Return-Path: X-Original-To: ietfmibs-archive@optimus.ietf.org Delivered-To: ietfarch-ietfmibs-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D58913A68FE; Wed, 3 Dec 2008 08:16:10 -0800 (PST) X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 462873A68FE for ; Wed, 3 Dec 2008 08:16:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.506 X-Spam-Level: X-Spam-Status: No, score=-1.506 tagged_above=-999 required=5 tests=[AWL=-0.365, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457] 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 s5TwUB9MI3jV for ; Wed, 3 Dec 2008 08:16:05 -0800 (PST) Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by core3.amsl.com (Postfix) with ESMTP id E2E933A680A for ; Wed, 3 Dec 2008 08:16:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 2F42BBE1F49; Wed, 3 Dec 2008 08:16:02 -0800 (PST) Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27103-09; Wed, 3 Dec 2008 08:16:02 -0800 (PST) Received: from [155.53.44.238] (nurnberg.redback.com [155.53.44.238]) by prattle.redback.com (Postfix) with ESMTP id 01B83BE1F48; Wed, 3 Dec 2008 08:16:01 -0800 (PST) Message-ID: <4936B0C1.4090600@redback.com> Date: Wed, 03 Dec 2008 08:16:01 -0800 From: Michael Thatcher User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: "Natale, Bob" References: <4935A3CD.4000504@redback.com> <17969D855F28964C88D177D45B6CDF11CF5A0A96@IMCMBX2.MITRE.ORG> In-Reply-To: <17969D855F28964C88D177D45B6CDF11CF5A0A96@IMCMBX2.MITRE.ORG> X-Virus-Scanned: by amavisd-new at redback.com Cc: "ietfmibs@ietf.org" Subject: Re: [IETFMIBS] a question about the Entity MIB X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2032718840==" Sender: ietfmibs-bounces@ietf.org Errors-To: ietfmibs-bounces@ietf.org --===============2032718840== Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit a number of textual conventions (TC), such as ifTypes, are maintained by IANA. See http://www.iana.org/protocols/

miket

Natale, Bob wrote:

What does it mean to say “Since this TC is not supported by IANA”?

From: ietfmibs-bounces@ietf.org [mailto:ietfmibs-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Wednesday, December 03, 2008 5:07 AM
To: Michael Thatcher; ietfmibs@ietf.org
Subject: Re: [IETFMIBS] a question about the Entity MIB

Hi Mike,

You are correct, the PhysicalClass TC does not cover disks and memory or other removable devices. The work-around with the current TC is to use one of the values other(1) or module(9) and provide more detailed information in a proprietary object. Extending this TC is not possible unless the MIB module defined in RFC4133 is revised.

Dan

From: ietfmibs-bounces@ietf.org [mailto:ietfmibs-bounces@ietf.org] On Behalf Of Michael Thatcher
Sent: Tuesday, December 02, 2008 11:08 PM
To: ietfmibs@ietf.org
Subject: [IETFMIBS] a question about the Entity MIB

Is there some way to extend the PhysicalClass Textual Convention to include disks & memory, & other removable physical devices. Since this TC is not supported by IANA, is there some other authority which can "easily" extend this

mike thatcher

--===============2032718840== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IETFMIBS mailing list IETFMIBS@ietf.org https://www.ietf.org/mailman/listinfo/ietfmibs --===============2032718840==-- From ietfmibs-bounces@ietf.org Thu Dec 11 15:55:11 2008 Return-Path: X-Original-To: ietfmibs-archive@optimus.ietf.org Delivered-To: ietfarch-ietfmibs-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BAD1F3A699C; Thu, 11 Dec 2008 15:55:11 -0800 (PST) X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA1A43A699C for ; Thu, 11 Dec 2008 15:55:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.64 X-Spam-Level: X-Spam-Status: No, score=-0.64 tagged_above=-999 required=5 tests=[AWL=-0.988, BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457] 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 MFLXDndBBCUU for ; Thu, 11 Dec 2008 15:55:10 -0800 (PST) Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by core3.amsl.com (Postfix) with ESMTP id 5F1D23A6833 for ; Thu, 11 Dec 2008 15:55:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 7FA7978F37E; Thu, 11 Dec 2008 15:55:03 -0800 (PST) Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27944-03; Thu, 11 Dec 2008 15:55:03 -0800 (PST) Received: from [155.53.44.238] (nurnberg.redback.com [155.53.44.238]) by prattle.redback.com (Postfix) with ESMTP id C9787C067CF; Thu, 11 Dec 2008 15:55:00 -0800 (PST) Message-ID: <4941A854.10502@redback.com> Date: Thu, 11 Dec 2008 15:55:00 -0800 From: Michael Thatcher User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: ietfmibs@ietf.org X-Virus-Scanned: by amavisd-new at redback.com Subject: [IETFMIBS] is there a V6 equivalent to snmpUDPDomain define somewhere? X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0851302625==" Sender: ietfmibs-bounces@ietf.org Errors-To: ietfmibs-bounces@ietf.org --===============0851302625== Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I'm looking for the v6 equivalent to snmpUDPDomain defined in SNMPv2-TM.my.

mike thatcher
--===============0851302625== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IETFMIBS mailing list IETFMIBS@ietf.org https://www.ietf.org/mailman/listinfo/ietfmibs --===============0851302625==-- From ietfmibs-bounces@ietf.org Thu Dec 11 23:32:21 2008 Return-Path: X-Original-To: ietfmibs-archive@optimus.ietf.org Delivered-To: ietfarch-ietfmibs-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE00B3A6A83; Thu, 11 Dec 2008 23:32:21 -0800 (PST) X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A33DC3A6A83 for ; Thu, 11 Dec 2008 23:32:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.236 X-Spam-Level: X-Spam-Status: No, score=-2.236 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, HELO_EQ_DE=0.35] 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 A-X8wwmXvNhI for ; Thu, 11 Dec 2008 23:32:20 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id D45EB3A69EC for ; Thu, 11 Dec 2008 23:32:19 -0800 (PST) Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 918FAC0048; Fri, 12 Dec 2008 08:32:13 +0100 (CET) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id Gm63zhMymyIz; Fri, 12 Dec 2008 08:32:08 +0100 (CET) Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 612A6C0045; Fri, 12 Dec 2008 08:32:08 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id A62A68AE107; Fri, 12 Dec 2008 08:32:07 +0100 (CET) Date: Fri, 12 Dec 2008 08:32:07 +0100 From: Juergen Schoenwaelder To: Michael Thatcher Message-ID: <20081212073207.GB28977@elstar.local> References: <4941A854.10502@redback.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4941A854.10502@redback.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: ietfmibs@ietf.org Subject: Re: [IETFMIBS] is there a V6 equivalent to snmpUDPDomain define somewhere? X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: j.schoenwaelder@jacobs-university.de List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietfmibs-bounces@ietf.org Errors-To: ietfmibs-bounces@ietf.org On Thu, Dec 11, 2008 at 03:55:00PM -0800, Michael Thatcher wrote: > I'm looking for the v6 equivalent to snmpUDPDomain defined in > SNMPv2-TM.my. You should use transportDomainUdpIpv6 defined in TRANSPORT-ADDRESS-MIB published in RFC 3419. See section 3.1.2 for more details. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 _______________________________________________ IETFMIBS mailing list IETFMIBS@ietf.org https://www.ietf.org/mailman/listinfo/ietfmibs From ietfmibs-bounces@ietf.org Wed Dec 24 04:51:23 2008 Return-Path: X-Original-To: ietfmibs-archive@optimus.ietf.org Delivered-To: ietfarch-ietfmibs-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD17628C1B0; Wed, 24 Dec 2008 04:51:23 -0800 (PST) X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2D6E3A6B5A for ; Wed, 24 Dec 2008 00:15:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.873 X-Spam-Level: X-Spam-Status: No, score=-1.873 tagged_above=-999 required=5 tests=[AWL=0.725, BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 buZZI-C5ZcrF for ; Wed, 24 Dec 2008 00:15:25 -0800 (PST) Received: from eu1sys200aog113.obsmtp.com (eu1sys200aog113.obsmtp.com [207.126.144.135]) by core3.amsl.com (Postfix) with ESMTP id 2F23F3A67AF for ; Wed, 24 Dec 2008 00:15:24 -0800 (PST) Received: from source ([164.129.1.35]) (using TLSv1) by eu1sys200aob113.postini.com ([207.126.147.11]) with SMTP ID DSNKSVHvi1Q+fFKCgnWFHZJTpbqYj9tKE4fO@postini.com; Wed, 24 Dec 2008 08:15:16 UTC Received: from zeta.dmz-eu.st.com (ns2.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 1E869DAC5 for ; Wed, 24 Dec 2008 08:14:37 +0000 (GMT) Received: from mail1.dlh.st.com (mail1.dlh.st.com [10.199.8.21]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 3B4E64BEA7 for ; Wed, 24 Dec 2008 08:14:49 +0000 (GMT) Received: from dlhpc1320 (dlhgn53dhcp75.dlh.st.com [10.199.53.75]) by mail1.dlh.st.com (MOS 3.8.7a) with ESMTP id DAH42604 (AUTH ajain); Wed, 24 Dec 2008 13:44:48 +0530 (IST) From: Aditya JAIN To: Date: Wed, 24 Dec 2008 13:44:48 +0530 Message-ID: <001601c9659f$b0a07140$1edda8c0@dlh.st.com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: Aclln6/jw6bgVICNQe+P/aQ3NkNiGA== X-Mailman-Approved-At: Wed, 24 Dec 2008 04:51:22 -0800 Subject: [IETFMIBS] Query regarding scope of ifInUnknownProtos X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0376688585==" Sender: ietfmibs-bounces@ietf.org Errors-To: ietfmibs-bounces@ietf.org This is a multi-part message in MIME format. --===============0376688585== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0017_01C965CD.CA58AD40" This is a multi-part message in MIME format. ------=_NextPart_000_0017_01C965CD.CA58AD40 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello, I have a confusion regarding the incrementing of ifInUnknownProtos mib object on a transparent bridging device. Let's say I have a transparent bridging/switching device (layer 2 device) confirming to ANSI/IEEE Std 802.1D, 1993 Edition, which can forward 802.3/DIX packets. The device itself supports a full TCP/IP stack, which means I can query the device through SNMP. The device does not support replying to IPX packets. Now, since the device itself does not support responding to IPX packets, does it also enforce that it cannot forward IPX packets through the device, thus resulting in the increase of ifInUnknownProtos mib object? Or, if it has the liberty to still forward IPX from one interface to the other, then will the counter of ifInUnknownProtos for this device interface always remain 0? Or does confirming to ANSI/IEEE Std 802.1D, 1993 Edition implies my transparent bridging device has to take care of IPX packets in the first place? Regards, Aditya ------=_NextPart_000_0017_01C965CD.CA58AD40 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

I have a confusion regarding the incrementing = of ifInUnknownProtos mib object on a transparent bridging device. =

Let's say I have a transparent = bridging/switching device (layer 2 device) confirming to ANSI/IEEE Std 802.1D, 1993 = Edition, which can forward 802.3/DIX packets. The device itself supports a full TCP/IP = stack, which means I can query the device through SNMP. =

The device does not support replying to IPX = packets. Now, since the device itself does not support responding to IPX packets, = does it also enforce that it cannot forward IPX packets through the device, = thus resulting in the increase of ifInUnknownProtos mib object? =

Or, if it has the liberty to still forward = IPX from one interface to the other, then will the counter of ifInUnknownProtos = for this device interface always remain 0?

Or does confirming to ANSI/IEEE Std 802.1D, = 1993 Edition implies my transparent bridging device has to take care of IPX = packets in the first place?

Regards,

Aditya

------=_NextPart_000_0017_01C965CD.CA58AD40-- --===============0376688585== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IETFMIBS mailing list IETFMIBS@ietf.org https://www.ietf.org/mailman/listinfo/ietfmibs --===============0376688585==--