From mailman-owner@ietf.org  Fri Feb  1 05:30:15 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13310
	for <hubmib-archive@odin.ietf.org>; Fri, 1 Feb 2002 05:30:14 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA22364
	for <hubmib-archive@lists.ietf.org>; Fri, 1 Feb 2002 05:30:17 -0500 (EST)
Date: Fri, 1 Feb 2002 05:30:17 -0500 (EST)
Message-Id: <200202011030.FAA22364@optimus.ietf.org>
From: mailman-owner@ietf.org
Subject: ietf.org mailing list memberships reminder
To: hubmib-archive@ietf.org
X-No-Archive: yes
Precedence: bulk
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, hubmib-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for hubmib-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
hubmib@ietf.org                          XUKx      
https://www1.ietf.org/mailman/options/hubmib/hubmib-archive@lists.ietf.org


From hubmib-admin@ietf.org  Fri Feb  1 07:07:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19568
	for <hubmib-archive@odin.ietf.org>; Fri, 1 Feb 2002 07:07:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA09847;
	Fri, 1 Feb 2002 07:07:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA09820
	for <hubmib@optimus.ietf.org>; Fri, 1 Feb 2002 07:07:16 -0500 (EST)
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19559
	for <hubmib@ietf.org>; Fri, 1 Feb 2002 07:07:11 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by ihemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g11C7D026973
	for <hubmib@ietf.org>; Fri, 1 Feb 2002 07:07:14 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21)
	id <1ACQBQVX>; Fri, 1 Feb 2002 13:07:13 +0100
Message-ID: <2413FED0DFE6D111B3F90008C7FA61FB0E69B884@nl0006exch002u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: RJ Atkinson <rja@extremenetworks.com>,
        Erik Nordmark
	 <Erik.Nordmark@eng.sun.com>
Cc: AToMMIB Mailing List <atommib@research.telcordia.com>,
        Hubmib Mailing List <hubmib@ietf.org>
Subject: RE: [Hubmib] Re: 53rd AToMIB agenda items
Date: Fri, 1 Feb 2002 13:06:33 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Inline

> -----Original Message-----
> From: RJ Atkinson [mailto:rja@extremenetworks.com]
> Sent: Thursday, January 31, 2002 10:48 PM
> To: Erik Nordmark
> Cc: bwijnen@lucent.com; AToMMIB Mailing List; Hubmib Mailing List
> Subject: Re: [Hubmib] Re: 53rd AToMIB agenda items
> 
> On Thursday, January 31, 2002, at 09:42 , Erik Nordmark wrote:
> >> the problem with the sonetVTStuff2 and sonetFarEndVTStuff2
> >> is that, as per the conformance clause, you dont implement
> >> it when you dont support VTs. so its optional in the sense of
> >> you only support it when you need it. i see your logic but
> >> i havent seen this logic applied in other cases yet.
> >> it would be both a pity and a problem if you cant advance the
> >> spec because of this; if you dont get the implementation feedback
> >> now you may not get it two years from now either. in that case
> >> the logical conclusion would be to dump the sonetVTStuff2 and
> >> sonetFarEndVTStuff2? lets hope we can get some additional
> >> implementation feedback.
> >
> > Perhaps Bert can comment on the MIB specific issues of how to handle
> > this.
> >
> > In cases where there are some parts of a proposed standard that do not
> > have multiple interoperable implementations where the result has been
> > that those pieces have been lifted out of into a separate specification.
> >
> > Then the core part can be advanced to draft standard while the other
> > specification can be a proposed standard.
> 
This generic approach of splitting out the pieces that seem to not have
been implemented (or at least for which we did not get reports) is
one approach for MIB documents too.

Another approach is to deprecate or even obsolete those objects.
In fact, if we cannot find any implementation feedback, then they
may not be generically usefull and if only one vendor implemented
them, then they seem to belong in an enterprise specific MIB.
So I would then obsolete them.

> I'm wondering if the pain of splitting the stuff into separate documents
> might be avoidable in this case by editing the MIB document to indicate
> which OIDs are mandatory-to-implement and which are optional-to-implement.
> I thought that was one use of the Conformance Clause, but might be 
> confused.
> 
Yes... but the optional to implement would be "generally optional", but
optional in the sens that you would only have to implement objects for
feasture X if you also have feature X on you system. But if feature X 
is only on 1 vendors system, then feature X is probably not an IETF
DS or STD and so the MIB objects for feature X should also not show
up at DS or STD level.

Bert
> Ran
> rja@extremenetworks.com
> 

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Fri Feb  1 07:07:39 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19575
	for <hubmib-archive@odin.ietf.org>; Fri, 1 Feb 2002 07:07:38 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA09882
	for hubmib-archive@odin.ietf.org; Fri, 1 Feb 2002 07:07:42 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA09847;
	Fri, 1 Feb 2002 07:07:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA09820
	for <hubmib@optimus.ietf.org>; Fri, 1 Feb 2002 07:07:16 -0500 (EST)
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19559
	for <hubmib@ietf.org>; Fri, 1 Feb 2002 07:07:11 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by ihemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g11C7D026973
	for <hubmib@ietf.org>; Fri, 1 Feb 2002 07:07:14 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21)
	id <1ACQBQVX>; Fri, 1 Feb 2002 13:07:13 +0100
Message-ID: <2413FED0DFE6D111B3F90008C7FA61FB0E69B884@nl0006exch002u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: RJ Atkinson <rja@extremenetworks.com>,
        Erik Nordmark
	 <Erik.Nordmark@eng.sun.com>
Cc: AToMMIB Mailing List <atommib@research.telcordia.com>,
        Hubmib Mailing List <hubmib@ietf.org>
Subject: RE: [Hubmib] Re: 53rd AToMIB agenda items
Date: Fri, 1 Feb 2002 13:06:33 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Inline

> -----Original Message-----
> From: RJ Atkinson [mailto:rja@extremenetworks.com]
> Sent: Thursday, January 31, 2002 10:48 PM
> To: Erik Nordmark
> Cc: bwijnen@lucent.com; AToMMIB Mailing List; Hubmib Mailing List
> Subject: Re: [Hubmib] Re: 53rd AToMIB agenda items
> 
> On Thursday, January 31, 2002, at 09:42 , Erik Nordmark wrote:
> >> the problem with the sonetVTStuff2 and sonetFarEndVTStuff2
> >> is that, as per the conformance clause, you dont implement
> >> it when you dont support VTs. so its optional in the sense of
> >> you only support it when you need it. i see your logic but
> >> i havent seen this logic applied in other cases yet.
> >> it would be both a pity and a problem if you cant advance the
> >> spec because of this; if you dont get the implementation feedback
> >> now you may not get it two years from now either. in that case
> >> the logical conclusion would be to dump the sonetVTStuff2 and
> >> sonetFarEndVTStuff2? lets hope we can get some additional
> >> implementation feedback.
> >
> > Perhaps Bert can comment on the MIB specific issues of how to handle
> > this.
> >
> > In cases where there are some parts of a proposed standard that do not
> > have multiple interoperable implementations where the result has been
> > that those pieces have been lifted out of into a separate specification.
> >
> > Then the core part can be advanced to draft standard while the other
> > specification can be a proposed standard.
> 
This generic approach of splitting out the pieces that seem to not have
been implemented (or at least for which we did not get reports) is
one approach for MIB documents too.

Another approach is to deprecate or even obsolete those objects.
In fact, if we cannot find any implementation feedback, then they
may not be generically usefull and if only one vendor implemented
them, then they seem to belong in an enterprise specific MIB.
So I would then obsolete them.

> I'm wondering if the pain of splitting the stuff into separate documents
> might be avoidable in this case by editing the MIB document to indicate
> which OIDs are mandatory-to-implement and which are optional-to-implement.
> I thought that was one use of the Conformance Clause, but might be 
> confused.
> 
Yes... but the optional to implement would be "generally optional", but
optional in the sens that you would only have to implement objects for
feasture X if you also have feature X on you system. But if feature X 
is only on 1 vendors system, then feature X is probably not an IETF
DS or STD and so the MIB objects for feature X should also not show
up at DS or STD level.

Bert
> Ran
> rja@extremenetworks.com
> 

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Sat Feb  2 06:53:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02311
	for <hubmib-archive@odin.ietf.org>; Sat, 2 Feb 2002 06:53:27 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA23738;
	Sat, 2 Feb 2002 06:52:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA23711
	for <hubmib@optimus.ietf.org>; Sat, 2 Feb 2002 06:52:48 -0500 (EST)
Received: from auemail1.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02296
	for <hubmib@ietf.org>; Sat, 2 Feb 2002 06:52:46 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g12BqkN03731
	for <hubmib@ietf.org>; Sat, 2 Feb 2002 06:52:46 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21)
	id <1ACQCCW0>; Sat, 2 Feb 2002 12:52:45 +0100
Message-ID: <2413FED0DFE6D111B3F90008C7FA61FB0E69BAA1@nl0006exch002u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Hubmib Mailing List <hubmib@ietf.org>
Date: Sat, 2 Feb 2002 12:52:43 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Subject: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

HUBMIBbers...

Any input or answer on this question?

Bert
--- original email -------

Date: Fri, 01 Feb 2002 10:33:05 -0500
From: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
Organization: Dept. of Computer Science, Columbia University
To: iab@ISI.EDU
Subject: Ethernet switch forwarding table MIB?

I normally don't get close to MIBs, but here's a problem that I found
surprisingly difficult to solve in a vendor-independent way:

For emergency calls, some countries mandate that you can figure out
which room a call originates from, if the emergency call originates from
within a large enterprise or campus, so that emergency help can be
provided more expeditiously. For example, in the US (and, I believe,
Canada), it's the law that large PBXs must provide this information to a
semi-national database.

One approach to solving this for IP-over-802 devices is to backtrack a
MAC address to the switch and switch port, using switch forwarding
tables. This applies to VoIP, naturally, but it's only a matter of time
before the first 911/112-over-IM "call

" happens.

However, while most managed Ethernet switches have such tables (and we
apparently locally have tools to use them, primarily to track down
systems that have been compromised and are spewing attack packets),
there doesn't seem to be a standard MIB for that. I may well have missed
this in my quick browsing of the RFC MIB list, but that's what our local
network admin claimed.

Is there a standard way of solving the same problem? If not, should
there be?

Henning
- -- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Sat Feb  2 06:53:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02322
	for <hubmib-archive@odin.ietf.org>; Sat, 2 Feb 2002 06:53:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA23778
	for hubmib-archive@odin.ietf.org; Sat, 2 Feb 2002 06:53:30 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA23738;
	Sat, 2 Feb 2002 06:52:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA23711
	for <hubmib@optimus.ietf.org>; Sat, 2 Feb 2002 06:52:48 -0500 (EST)
Received: from auemail1.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02296
	for <hubmib@ietf.org>; Sat, 2 Feb 2002 06:52:46 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g12BqkN03731
	for <hubmib@ietf.org>; Sat, 2 Feb 2002 06:52:46 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21)
	id <1ACQCCW0>; Sat, 2 Feb 2002 12:52:45 +0100
Message-ID: <2413FED0DFE6D111B3F90008C7FA61FB0E69BAA1@nl0006exch002u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Hubmib Mailing List <hubmib@ietf.org>
Date: Sat, 2 Feb 2002 12:52:43 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Subject: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

HUBMIBbers...

Any input or answer on this question?

Bert
--- original email -------

Date: Fri, 01 Feb 2002 10:33:05 -0500
From: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
Organization: Dept. of Computer Science, Columbia University
To: iab@ISI.EDU
Subject: Ethernet switch forwarding table MIB?

I normally don't get close to MIBs, but here's a problem that I found
surprisingly difficult to solve in a vendor-independent way:

For emergency calls, some countries mandate that you can figure out
which room a call originates from, if the emergency call originates from
within a large enterprise or campus, so that emergency help can be
provided more expeditiously. For example, in the US (and, I believe,
Canada), it's the law that large PBXs must provide this information to a
semi-national database.

One approach to solving this for IP-over-802 devices is to backtrack a
MAC address to the switch and switch port, using switch forwarding
tables. This applies to VoIP, naturally, but it's only a matter of time
before the first 911/112-over-IM "call

" happens.

However, while most managed Ethernet switches have such tables (and we
apparently locally have tools to use them, primarily to track down
systems that have been compromised and are spewing attack packets),
there doesn't seem to be a standard MIB for that. I may well have missed
this in my quick browsing of the RFC MIB list, but that's what our local
network admin claimed.

Is there a standard way of solving the same problem? If not, should
there be?

Henning
- -- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Thu Feb  7 17:20:19 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11442
	for <hubmib-archive@odin.ietf.org>; Thu, 7 Feb 2002 17:20:14 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA20430;
	Thu, 7 Feb 2002 17:11:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA20399
	for <hubmib@ns.ietf.org>; Thu, 7 Feb 2002 17:10:58 -0500 (EST)
Received: from ctron-dnm.ctron.com (firewall-user@ctron-dnm.enterasys.com [12.25.1.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11295
	for <hubmib@ietf.org>; Thu, 7 Feb 2002 17:10:56 -0500 (EST)
Received: (from uucp@localhost)
	by ctron-dnm.ctron.com (8.8.7/8.8.7) id RAA28850
	for <hubmib@ietf.org>; Thu, 7 Feb 2002 17:20:21 -0500 (EST)
Received: from cnc-exc2(134.141.77.103) by ctron-dnm.ctron.com via smap (4.1)
	id xma028842; Thu, 7 Feb 02 17:19:34 -0500
Received: by cnc-exc2.enterasys.com with Internet Mail Service (5.5.2653.19)
	id <D55NZ83S>; Thu, 7 Feb 2002 17:09:25 -0500
Message-ID: <0BF8B32B723ED5119E0B0002A551748B01FA0886@corp-exc3.ctron.com>
From: "Harrington, David" <dbh@enterasys.com>
To: Hubmib Mailing List <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Date: Thu, 7 Feb 2002 17:09:19 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1B024.174F2AA0"
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1B024.174F2AA0
Content-Type: text/plain

Hi,

The phrasing of your question is a bit ambiguous - a standard mib for what? 

There is no standard mib to my knowledge designed to solve the 911 location
issue directly.

identifying the room a switch is in? The system MIB contains an object
(sysLocation) where an operator can specify the device location.

the backtracking of MAC addresses? I don't think there is a standard mib for
this directly, but there are some mibs with data that could be used to
backtrack MAC addresses. PTOPO (RFC2922) contains physical topology
connections. 

I hope this helps,
dbh

> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> Sent: Saturday, February 02, 2002 6:53 AM
> To: Hubmib Mailing List
> Subject: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
> 
> 
> HUBMIBbers...
> 
> Any input or answer on this question?
> 
> Bert
> --- original email -------
> 
> Date: Fri, 01 Feb 2002 10:33:05 -0500
> From: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
> Organization: Dept. of Computer Science, Columbia University
> To: iab@ISI.EDU
> Subject: Ethernet switch forwarding table MIB?
> 
> I normally don't get close to MIBs, but here's a problem that I found
> surprisingly difficult to solve in a vendor-independent way:
> 
> For emergency calls, some countries mandate that you can figure out
> which room a call originates from, if the emergency call 
> originates from
> within a large enterprise or campus, so that emergency help can be
> provided more expeditiously. For example, in the US (and, I believe,
> Canada), it's the law that large PBXs must provide this 
> information to a
> semi-national database.
> 
> One approach to solving this for IP-over-802 devices is to backtrack a
> MAC address to the switch and switch port, using switch forwarding
> tables. This applies to VoIP, naturally, but it's only a 
> matter of time
> before the first 911/112-over-IM "call
> 
> " happens.
> 
> However, while most managed Ethernet switches have such tables (and we
> apparently locally have tools to use them, primarily to track down
> systems that have been compromised and are spewing attack packets),
> there doesn't seem to be a standard MIB for that. I may well 
> have missed
> this in my quick browsing of the RFC MIB list, but that's 
> what our local
> network admin claimed.
> 
> Is there a standard way of solving the same problem? If not, should
> there be?
> 
> Henning
> - -- 
> Henning Schulzrinne   http://www.cs.columbia.edu/~hgs
> 
> _______________________________________________
> Hubmib mailing list
> Hubmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/hubmib
> 

------_=_NextPart_001_01C1B024.174F2AA0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Hubmib] FW: Ethernet switch forwarding table MIB? =
(fwd)</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi,</FONT>
</P>

<P><FONT SIZE=3D2>The phrasing of your question is a bit ambiguous - a =
standard mib for what? </FONT>
</P>

<P><FONT SIZE=3D2>There is no standard mib to my knowledge designed to =
solve the 911 location issue directly.</FONT>
</P>

<P><FONT SIZE=3D2>identifying the room a switch is in? The system MIB =
contains an object (sysLocation) where an operator can specify the =
device location.</FONT></P>

<P><FONT SIZE=3D2>the backtracking of MAC addresses? I don't think =
there is a standard mib for this directly, but there are some mibs with =
data that could be used to backtrack MAC addresses. PTOPO (RFC2922) =
contains physical topology connections. </FONT></P>

<P><FONT SIZE=3D2>I hope this helps,</FONT>
<BR><FONT SIZE=3D2>dbh</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Wijnen, Bert (Bert) [<A =
HREF=3D"mailto:bwijnen@lucent.com">mailto:bwijnen@lucent.com</A>]</FONT>=

<BR><FONT SIZE=3D2>&gt; Sent: Saturday, February 02, 2002 6:53 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Hubmib Mailing List</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [Hubmib] FW: Ethernet switch =
forwarding table MIB? (fwd)</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; HUBMIBbers...</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Any input or answer on this question?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Bert</FONT>
<BR><FONT SIZE=3D2>&gt; --- original email -------</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Date: Fri, 01 Feb 2002 10:33:05 -0500</FONT>
<BR><FONT SIZE=3D2>&gt; From: &quot;Henning G. Schulzrinne&quot; =
&lt;hgs@cs.columbia.edu&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Organization: Dept. of Computer Science, =
Columbia University</FONT>
<BR><FONT SIZE=3D2>&gt; To: iab@ISI.EDU</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Ethernet switch forwarding table =
MIB?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I normally don't get close to MIBs, but here's =
a problem that I found</FONT>
<BR><FONT SIZE=3D2>&gt; surprisingly difficult to solve in a =
vendor-independent way:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; For emergency calls, some countries mandate =
that you can figure out</FONT>
<BR><FONT SIZE=3D2>&gt; which room a call originates from, if the =
emergency call </FONT>
<BR><FONT SIZE=3D2>&gt; originates from</FONT>
<BR><FONT SIZE=3D2>&gt; within a large enterprise or campus, so that =
emergency help can be</FONT>
<BR><FONT SIZE=3D2>&gt; provided more expeditiously. For example, in =
the US (and, I believe,</FONT>
<BR><FONT SIZE=3D2>&gt; Canada), it's the law that large PBXs must =
provide this </FONT>
<BR><FONT SIZE=3D2>&gt; information to a</FONT>
<BR><FONT SIZE=3D2>&gt; semi-national database.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; One approach to solving this for IP-over-802 =
devices is to backtrack a</FONT>
<BR><FONT SIZE=3D2>&gt; MAC address to the switch and switch port, =
using switch forwarding</FONT>
<BR><FONT SIZE=3D2>&gt; tables. This applies to VoIP, naturally, but =
it's only a </FONT>
<BR><FONT SIZE=3D2>&gt; matter of time</FONT>
<BR><FONT SIZE=3D2>&gt; before the first 911/112-over-IM =
&quot;call</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &quot; happens.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; However, while most managed Ethernet switches =
have such tables (and we</FONT>
<BR><FONT SIZE=3D2>&gt; apparently locally have tools to use them, =
primarily to track down</FONT>
<BR><FONT SIZE=3D2>&gt; systems that have been compromised and are =
spewing attack packets),</FONT>
<BR><FONT SIZE=3D2>&gt; there doesn't seem to be a standard MIB for =
that. I may well </FONT>
<BR><FONT SIZE=3D2>&gt; have missed</FONT>
<BR><FONT SIZE=3D2>&gt; this in my quick browsing of the RFC MIB list, =
but that's </FONT>
<BR><FONT SIZE=3D2>&gt; what our local</FONT>
<BR><FONT SIZE=3D2>&gt; network admin claimed.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Is there a standard way of solving the same =
problem? If not, should</FONT>
<BR><FONT SIZE=3D2>&gt; there be?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Henning</FONT>
<BR><FONT SIZE=3D2>&gt; - -- </FONT>
<BR><FONT SIZE=3D2>&gt; Henning Schulzrinne&nbsp;&nbsp; <A =
HREF=3D"http://www.cs.columbia.edu/~hgs" =
TARGET=3D"_blank">http://www.cs.columbia.edu/~hgs</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Hubmib mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; Hubmib@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/hubmib" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/hubmib</A></FON=
T>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1B024.174F2AA0--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@ns.ietf.org  Thu Feb  7 17:20:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11452
	for <hubmib-archive@odin.ietf.org>; Thu, 7 Feb 2002 17:20:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA20692
	for hubmib-archive@odin.ietf.org; Thu, 7 Feb 2002 17:20:21 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA20430;
	Thu, 7 Feb 2002 17:11:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA20399
	for <hubmib@ns.ietf.org>; Thu, 7 Feb 2002 17:10:58 -0500 (EST)
Received: from ctron-dnm.ctron.com (firewall-user@ctron-dnm.enterasys.com [12.25.1.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11295
	for <hubmib@ietf.org>; Thu, 7 Feb 2002 17:10:56 -0500 (EST)
Received: (from uucp@localhost)
	by ctron-dnm.ctron.com (8.8.7/8.8.7) id RAA28850
	for <hubmib@ietf.org>; Thu, 7 Feb 2002 17:20:21 -0500 (EST)
Received: from cnc-exc2(134.141.77.103) by ctron-dnm.ctron.com via smap (4.1)
	id xma028842; Thu, 7 Feb 02 17:19:34 -0500
Received: by cnc-exc2.enterasys.com with Internet Mail Service (5.5.2653.19)
	id <D55NZ83S>; Thu, 7 Feb 2002 17:09:25 -0500
Message-ID: <0BF8B32B723ED5119E0B0002A551748B01FA0886@corp-exc3.ctron.com>
From: "Harrington, David" <dbh@enterasys.com>
To: Hubmib Mailing List <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Date: Thu, 7 Feb 2002 17:09:19 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1B024.174F2AA0"
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1B024.174F2AA0
Content-Type: text/plain

Hi,

The phrasing of your question is a bit ambiguous - a standard mib for what? 

There is no standard mib to my knowledge designed to solve the 911 location
issue directly.

identifying the room a switch is in? The system MIB contains an object
(sysLocation) where an operator can specify the device location.

the backtracking of MAC addresses? I don't think there is a standard mib for
this directly, but there are some mibs with data that could be used to
backtrack MAC addresses. PTOPO (RFC2922) contains physical topology
connections. 

I hope this helps,
dbh

> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> Sent: Saturday, February 02, 2002 6:53 AM
> To: Hubmib Mailing List
> Subject: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
> 
> 
> HUBMIBbers...
> 
> Any input or answer on this question?
> 
> Bert
> --- original email -------
> 
> Date: Fri, 01 Feb 2002 10:33:05 -0500
> From: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
> Organization: Dept. of Computer Science, Columbia University
> To: iab@ISI.EDU
> Subject: Ethernet switch forwarding table MIB?
> 
> I normally don't get close to MIBs, but here's a problem that I found
> surprisingly difficult to solve in a vendor-independent way:
> 
> For emergency calls, some countries mandate that you can figure out
> which room a call originates from, if the emergency call 
> originates from
> within a large enterprise or campus, so that emergency help can be
> provided more expeditiously. For example, in the US (and, I believe,
> Canada), it's the law that large PBXs must provide this 
> information to a
> semi-national database.
> 
> One approach to solving this for IP-over-802 devices is to backtrack a
> MAC address to the switch and switch port, using switch forwarding
> tables. This applies to VoIP, naturally, but it's only a 
> matter of time
> before the first 911/112-over-IM "call
> 
> " happens.
> 
> However, while most managed Ethernet switches have such tables (and we
> apparently locally have tools to use them, primarily to track down
> systems that have been compromised and are spewing attack packets),
> there doesn't seem to be a standard MIB for that. I may well 
> have missed
> this in my quick browsing of the RFC MIB list, but that's 
> what our local
> network admin claimed.
> 
> Is there a standard way of solving the same problem? If not, should
> there be?
> 
> Henning
> - -- 
> Henning Schulzrinne   http://www.cs.columbia.edu/~hgs
> 
> _______________________________________________
> Hubmib mailing list
> Hubmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/hubmib
> 

------_=_NextPart_001_01C1B024.174F2AA0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Hubmib] FW: Ethernet switch forwarding table MIB? =
(fwd)</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi,</FONT>
</P>

<P><FONT SIZE=3D2>The phrasing of your question is a bit ambiguous - a =
standard mib for what? </FONT>
</P>

<P><FONT SIZE=3D2>There is no standard mib to my knowledge designed to =
solve the 911 location issue directly.</FONT>
</P>

<P><FONT SIZE=3D2>identifying the room a switch is in? The system MIB =
contains an object (sysLocation) where an operator can specify the =
device location.</FONT></P>

<P><FONT SIZE=3D2>the backtracking of MAC addresses? I don't think =
there is a standard mib for this directly, but there are some mibs with =
data that could be used to backtrack MAC addresses. PTOPO (RFC2922) =
contains physical topology connections. </FONT></P>

<P><FONT SIZE=3D2>I hope this helps,</FONT>
<BR><FONT SIZE=3D2>dbh</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Wijnen, Bert (Bert) [<A =
HREF=3D"mailto:bwijnen@lucent.com">mailto:bwijnen@lucent.com</A>]</FONT>=

<BR><FONT SIZE=3D2>&gt; Sent: Saturday, February 02, 2002 6:53 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Hubmib Mailing List</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [Hubmib] FW: Ethernet switch =
forwarding table MIB? (fwd)</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; HUBMIBbers...</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Any input or answer on this question?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Bert</FONT>
<BR><FONT SIZE=3D2>&gt; --- original email -------</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Date: Fri, 01 Feb 2002 10:33:05 -0500</FONT>
<BR><FONT SIZE=3D2>&gt; From: &quot;Henning G. Schulzrinne&quot; =
&lt;hgs@cs.columbia.edu&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Organization: Dept. of Computer Science, =
Columbia University</FONT>
<BR><FONT SIZE=3D2>&gt; To: iab@ISI.EDU</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Ethernet switch forwarding table =
MIB?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I normally don't get close to MIBs, but here's =
a problem that I found</FONT>
<BR><FONT SIZE=3D2>&gt; surprisingly difficult to solve in a =
vendor-independent way:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; For emergency calls, some countries mandate =
that you can figure out</FONT>
<BR><FONT SIZE=3D2>&gt; which room a call originates from, if the =
emergency call </FONT>
<BR><FONT SIZE=3D2>&gt; originates from</FONT>
<BR><FONT SIZE=3D2>&gt; within a large enterprise or campus, so that =
emergency help can be</FONT>
<BR><FONT SIZE=3D2>&gt; provided more expeditiously. For example, in =
the US (and, I believe,</FONT>
<BR><FONT SIZE=3D2>&gt; Canada), it's the law that large PBXs must =
provide this </FONT>
<BR><FONT SIZE=3D2>&gt; information to a</FONT>
<BR><FONT SIZE=3D2>&gt; semi-national database.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; One approach to solving this for IP-over-802 =
devices is to backtrack a</FONT>
<BR><FONT SIZE=3D2>&gt; MAC address to the switch and switch port, =
using switch forwarding</FONT>
<BR><FONT SIZE=3D2>&gt; tables. This applies to VoIP, naturally, but =
it's only a </FONT>
<BR><FONT SIZE=3D2>&gt; matter of time</FONT>
<BR><FONT SIZE=3D2>&gt; before the first 911/112-over-IM =
&quot;call</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &quot; happens.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; However, while most managed Ethernet switches =
have such tables (and we</FONT>
<BR><FONT SIZE=3D2>&gt; apparently locally have tools to use them, =
primarily to track down</FONT>
<BR><FONT SIZE=3D2>&gt; systems that have been compromised and are =
spewing attack packets),</FONT>
<BR><FONT SIZE=3D2>&gt; there doesn't seem to be a standard MIB for =
that. I may well </FONT>
<BR><FONT SIZE=3D2>&gt; have missed</FONT>
<BR><FONT SIZE=3D2>&gt; this in my quick browsing of the RFC MIB list, =
but that's </FONT>
<BR><FONT SIZE=3D2>&gt; what our local</FONT>
<BR><FONT SIZE=3D2>&gt; network admin claimed.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Is there a standard way of solving the same =
problem? If not, should</FONT>
<BR><FONT SIZE=3D2>&gt; there be?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Henning</FONT>
<BR><FONT SIZE=3D2>&gt; - -- </FONT>
<BR><FONT SIZE=3D2>&gt; Henning Schulzrinne&nbsp;&nbsp; <A =
HREF=3D"http://www.cs.columbia.edu/~hgs" =
TARGET=3D"_blank">http://www.cs.columbia.edu/~hgs</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Hubmib mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; Hubmib@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/hubmib" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/hubmib</A></FON=
T>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1B024.174F2AA0--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Thu Feb  7 21:07:08 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15745
	for <hubmib-archive@odin.ietf.org>; Thu, 7 Feb 2002 21:07:08 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA29636;
	Thu, 7 Feb 2002 21:00:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA29610
	for <hubmib@ns.ietf.org>; Thu, 7 Feb 2002 20:59:58 -0500 (EST)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15618
	for <hubmib@ietf.org>; Thu, 7 Feb 2002 20:59:56 -0500 (EST)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id UAA06176
	for <hubmib@ietf.org>; Thu, 7 Feb 2002 20:58:29 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id UAA06146
	for <hubmib@ietf.org>; Thu, 7 Feb 2002 20:58:27 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1B044.2EFE967B"
Subject: RE: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Date: Fri, 8 Feb 2002 03:59:03 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F60D09A@IS0004AVEXU1.global.avaya.com>
Thread-Topic: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Thread-Index: AcGwJRVku6FWQ4yAQwSf+broRIxwvgAHPFXw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Harrington, David" <dbh@enterasys.com>,
        "Hubmib Mailing List" <hubmib@ietf.org>, <hgs@cs.columbia.edu>
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1B044.2EFE967B
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The issue of localization of an IP phone for emergency calls ('E911') is
more complex then MIB support. There is work done in other standard
bodies, for example in TIA Standards Committee TR-41. Some of the
contributions in TIA refer standard SNMP MIBs, but the solution is more
complex as it needs to include interfaces with the emergency system and
update of users and location data-bases.
=20
I would observe that the use of sysLocation of the switch would not
help. What is needed is the location of the IP phone, and not of the
switch. So assuming that the ptopo or Bridge MIBs would locate an IP
phone by its MAC address at the port of the bridge, the exact location
of the phone cannot be retrieved from any objects in existing standard
MIBs that I am aware about.
=20
Regards,
=20
Dan
=20
=20

-----Original Message-----
From: Harrington, David [mailto:dbh@enterasys.com]
Sent: Friday, February 08, 2002 12:09 AM
To: Hubmib Mailing List
Subject: RE: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)



Hi,=20

The phrasing of your question is a bit ambiguous - a standard mib for
what?=20

There is no standard mib to my knowledge designed to solve the 911
location issue directly.=20

identifying the room a switch is in? The system MIB contains an object
(sysLocation) where an operator can specify the device location.

the backtracking of MAC addresses? I don't think there is a standard mib
for this directly, but there are some mibs with data that could be used
to backtrack MAC addresses. PTOPO (RFC2922) contains physical topology
connections.=20

I hope this helps,=20
dbh=20

> -----Original Message-----=20
> From: Wijnen, Bert (Bert) [ mailto:bwijnen@lucent.com]=20
> Sent: Saturday, February 02, 2002 6:53 AM=20
> To: Hubmib Mailing List=20
> Subject: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)=20
>=20
>=20
> HUBMIBbers...=20
>=20
> Any input or answer on this question?=20
>=20
> Bert=20
> --- original email -------=20
>=20
> Date: Fri, 01 Feb 2002 10:33:05 -0500=20
> From: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>=20
> Organization: Dept. of Computer Science, Columbia University=20
> To: iab@ISI.EDU=20
> Subject: Ethernet switch forwarding table MIB?=20
>=20
> I normally don't get close to MIBs, but here's a problem that I found=20
> surprisingly difficult to solve in a vendor-independent way:=20
>=20
> For emergency calls, some countries mandate that you can figure out=20
> which room a call originates from, if the emergency call=20
> originates from=20
> within a large enterprise or campus, so that emergency help can be=20
> provided more expeditiously. For example, in the US (and, I believe,=20
> Canada), it's the law that large PBXs must provide this=20
> information to a=20
> semi-national database.=20
>=20
> One approach to solving this for IP-over-802 devices is to backtrack a

> MAC address to the switch and switch port, using switch forwarding=20
> tables. This applies to VoIP, naturally, but it's only a=20
> matter of time=20
> before the first 911/112-over-IM "call=20
>=20
> " happens.=20
>=20
> However, while most managed Ethernet switches have such tables (and we

> apparently locally have tools to use them, primarily to track down=20
> systems that have been compromised and are spewing attack packets),=20
> there doesn't seem to be a standard MIB for that. I may well=20
> have missed=20
> this in my quick browsing of the RFC MIB list, but that's=20
> what our local=20
> network admin claimed.=20
>=20
> Is there a standard way of solving the same problem? If not, should=20
> there be?=20
>=20
> Henning=20
> - --=20
> Henning Schulzrinne   http://www.cs.columbia.edu/~hgs=20
>=20
> _______________________________________________=20
> Hubmib mailing list=20
> Hubmib@ietf.org=20
> https://www1.ietf.org/mailman/listinfo/hubmib=20
>=20


------_=_NextPart_001_01C1B044.2EFE967B
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>RE: [Hubmib] FW: Ethernet switch forwarding table MIB? =
(fwd)</TITLE>

<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D608374301-08022002>The=20
issue of localization of an IP phone for emergency calls =
('E911')&nbsp;is more=20
complex then MIB support. There is work done in other standard bodies, =
for=20
example in TIA Standards Committee TR-41. Some of the contributions in =
TIA refer=20
standard SNMP MIBs, but the solution is more complex as it needs to =
include=20
interfaces with the emergency system and update of users and location=20
data-bases.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D608374301-08022002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D608374301-08022002>I=20
would observe that the use of sysLocation of the switch would not help. =
What is=20
needed is the location of the IP phone, and not of the switch. So =
assuming that=20
the ptopo or Bridge MIBs would locate an IP phone by its MAC address at =
the port=20
of the bridge, the exact location of the phone cannot be retrieved from =
any=20
objects in existing standard MIBs that I am aware =
about.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D608374301-08022002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D608374301-08022002>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D608374301-08022002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D608374301-08022002>Dan</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D608374301-08022002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D608374301-08022002>&nbsp;</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Harrington, David=20
  [mailto:dbh@enterasys.com]<BR><B>Sent:</B> Friday, February 08, 2002 =
12:09=20
  AM<BR><B>To:</B> Hubmib Mailing List<BR><B>Subject:</B> RE: [Hubmib] =
FW:=20
  Ethernet switch forwarding table MIB? (fwd)<BR><BR></FONT></DIV>
  <P><FONT size=3D2>Hi,</FONT> </P>
  <P><FONT size=3D2>The phrasing of your question is a bit ambiguous - a =
standard=20
  mib for what? </FONT></P>
  <P><FONT size=3D2>There is no standard mib to my knowledge designed to =
solve the=20
  911 location issue directly.</FONT> </P>
  <P><FONT size=3D2>identifying the room a switch is in? The system MIB =
contains=20
  an object (sysLocation) where an operator can specify the device=20
  location.</FONT></P>
  <P><FONT size=3D2>the backtracking of MAC addresses? I don't think =
there is a=20
  standard mib for this directly, but there are some mibs with data that =
could=20
  be used to backtrack MAC addresses. PTOPO (RFC2922) contains physical =
topology=20
  connections. </FONT></P>
  <P><FONT size=3D2>I hope this helps,</FONT> <BR><FONT =
size=3D2>dbh</FONT> </P>
  <P><FONT size=3D2>&gt; -----Original Message-----</FONT> <BR><FONT =
size=3D2>&gt;=20
  From: Wijnen, Bert (Bert) [<A=20
  =
href=3D"mailto:bwijnen@lucent.com">mailto:bwijnen@lucent.com</A>]</FONT> =

  <BR><FONT size=3D2>&gt; Sent: Saturday, February 02, 2002 6:53 =
AM</FONT>=20
  <BR><FONT size=3D2>&gt; To: Hubmib Mailing List</FONT> <BR><FONT =
size=3D2>&gt;=20
  Subject: [Hubmib] FW: Ethernet switch forwarding table MIB? =
(fwd)</FONT>=20
  <BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; HUBMIBbers...</FONT> <BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; Any input or answer on this question?</FONT> <BR><FONT =
size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; Bert</FONT> <BR><FONT size=3D2>&gt; --- =
original=20
  email -------</FONT> <BR><FONT size=3D2>&gt; </FONT><BR><FONT =
size=3D2>&gt; Date:=20
  Fri, 01 Feb 2002 10:33:05 -0500</FONT> <BR><FONT size=3D2>&gt; From: =
"Henning G.=20
  Schulzrinne" &lt;hgs@cs.columbia.edu&gt;</FONT> <BR><FONT =
size=3D2>&gt;=20
  Organization: Dept. of Computer Science, Columbia University</FONT> =
<BR><FONT=20
  size=3D2>&gt; To: iab@ISI.EDU</FONT> <BR><FONT size=3D2>&gt; Subject: =
Ethernet=20
  switch forwarding table MIB?</FONT> <BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; I normally don't get close to MIBs, but here's a problem =
that I=20
  found</FONT> <BR><FONT size=3D2>&gt; surprisingly difficult to solve =
in a=20
  vendor-independent way:</FONT> <BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; For emergency calls, some countries mandate that you can =
figure=20
  out</FONT> <BR><FONT size=3D2>&gt; which room a call originates from, =
if the=20
  emergency call </FONT><BR><FONT size=3D2>&gt; originates from</FONT> =
<BR><FONT=20
  size=3D2>&gt; within a large enterprise or campus, so that emergency =
help can=20
  be</FONT> <BR><FONT size=3D2>&gt; provided more expeditiously. For =
example, in=20
  the US (and, I believe,</FONT> <BR><FONT size=3D2>&gt; Canada), it's =
the law=20
  that large PBXs must provide this </FONT><BR><FONT size=3D2>&gt; =
information to=20
  a</FONT> <BR><FONT size=3D2>&gt; semi-national database.</FONT> =
<BR><FONT=20
  size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; One approach to solving =
this for=20
  IP-over-802 devices is to backtrack a</FONT> <BR><FONT size=3D2>&gt; =
MAC address=20
  to the switch and switch port, using switch forwarding</FONT> =
<BR><FONT=20
  size=3D2>&gt; tables. This applies to VoIP, naturally, but it's only a =

  </FONT><BR><FONT size=3D2>&gt; matter of time</FONT> <BR><FONT =
size=3D2>&gt;=20
  before the first 911/112-over-IM "call</FONT> <BR><FONT size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; " happens.</FONT> <BR><FONT =
size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; However, while most managed Ethernet =
switches=20
  have such tables (and we</FONT> <BR><FONT size=3D2>&gt; apparently =
locally have=20
  tools to use them, primarily to track down</FONT> <BR><FONT =
size=3D2>&gt;=20
  systems that have been compromised and are spewing attack =
packets),</FONT>=20
  <BR><FONT size=3D2>&gt; there doesn't seem to be a standard MIB for =
that. I may=20
  well </FONT><BR><FONT size=3D2>&gt; have missed</FONT> <BR><FONT =
size=3D2>&gt;=20
  this in my quick browsing of the RFC MIB list, but that's =
</FONT><BR><FONT=20
  size=3D2>&gt; what our local</FONT> <BR><FONT size=3D2>&gt; network =
admin=20
  claimed.</FONT> <BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; =
Is there a=20
  standard way of solving the same problem? If not, should</FONT> =
<BR><FONT=20
  size=3D2>&gt; there be?</FONT> <BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; Henning</FONT> <BR><FONT size=3D2>&gt; - -- =
</FONT><BR><FONT=20
  size=3D2>&gt; Henning Schulzrinne&nbsp;&nbsp; <A target=3D_blank=20
  =
href=3D"http://www.cs.columbia.edu/~hgs">http://www.cs.columbia.edu/~hgs<=
/A></FONT>=20
  <BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt;=20
  _______________________________________________</FONT> <BR><FONT =
size=3D2>&gt;=20
  Hubmib mailing list</FONT> <BR><FONT size=3D2>&gt; =
Hubmib@ietf.org</FONT>=20
  <BR><FONT size=3D2>&gt; <A target=3D_blank=20
  =
href=3D"https://www1.ietf.org/mailman/listinfo/hubmib">https://www1.ietf.=
org/mailman/listinfo/hubmib</A></FONT>=20
  <BR><FONT size=3D2>&gt; </FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1B044.2EFE967B--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@ns.ietf.org  Thu Feb  7 21:07:09 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15759
	for <hubmib-archive@odin.ietf.org>; Thu, 7 Feb 2002 21:07:09 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA00195
	for hubmib-archive@odin.ietf.org; Thu, 7 Feb 2002 21:07:11 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA29636;
	Thu, 7 Feb 2002 21:00:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA29610
	for <hubmib@ns.ietf.org>; Thu, 7 Feb 2002 20:59:58 -0500 (EST)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15618
	for <hubmib@ietf.org>; Thu, 7 Feb 2002 20:59:56 -0500 (EST)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id UAA06176
	for <hubmib@ietf.org>; Thu, 7 Feb 2002 20:58:29 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id UAA06146
	for <hubmib@ietf.org>; Thu, 7 Feb 2002 20:58:27 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1B044.2EFE967B"
Subject: RE: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Date: Fri, 8 Feb 2002 03:59:03 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F60D09A@IS0004AVEXU1.global.avaya.com>
Thread-Topic: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Thread-Index: AcGwJRVku6FWQ4yAQwSf+broRIxwvgAHPFXw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Harrington, David" <dbh@enterasys.com>,
        "Hubmib Mailing List" <hubmib@ietf.org>, <hgs@cs.columbia.edu>
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1B044.2EFE967B
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The issue of localization of an IP phone for emergency calls ('E911') is
more complex then MIB support. There is work done in other standard
bodies, for example in TIA Standards Committee TR-41. Some of the
contributions in TIA refer standard SNMP MIBs, but the solution is more
complex as it needs to include interfaces with the emergency system and
update of users and location data-bases.
=20
I would observe that the use of sysLocation of the switch would not
help. What is needed is the location of the IP phone, and not of the
switch. So assuming that the ptopo or Bridge MIBs would locate an IP
phone by its MAC address at the port of the bridge, the exact location
of the phone cannot be retrieved from any objects in existing standard
MIBs that I am aware about.
=20
Regards,
=20
Dan
=20
=20

-----Original Message-----
From: Harrington, David [mailto:dbh@enterasys.com]
Sent: Friday, February 08, 2002 12:09 AM
To: Hubmib Mailing List
Subject: RE: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)



Hi,=20

The phrasing of your question is a bit ambiguous - a standard mib for
what?=20

There is no standard mib to my knowledge designed to solve the 911
location issue directly.=20

identifying the room a switch is in? The system MIB contains an object
(sysLocation) where an operator can specify the device location.

the backtracking of MAC addresses? I don't think there is a standard mib
for this directly, but there are some mibs with data that could be used
to backtrack MAC addresses. PTOPO (RFC2922) contains physical topology
connections.=20

I hope this helps,=20
dbh=20

> -----Original Message-----=20
> From: Wijnen, Bert (Bert) [ mailto:bwijnen@lucent.com]=20
> Sent: Saturday, February 02, 2002 6:53 AM=20
> To: Hubmib Mailing List=20
> Subject: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)=20
>=20
>=20
> HUBMIBbers...=20
>=20
> Any input or answer on this question?=20
>=20
> Bert=20
> --- original email -------=20
>=20
> Date: Fri, 01 Feb 2002 10:33:05 -0500=20
> From: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>=20
> Organization: Dept. of Computer Science, Columbia University=20
> To: iab@ISI.EDU=20
> Subject: Ethernet switch forwarding table MIB?=20
>=20
> I normally don't get close to MIBs, but here's a problem that I found=20
> surprisingly difficult to solve in a vendor-independent way:=20
>=20
> For emergency calls, some countries mandate that you can figure out=20
> which room a call originates from, if the emergency call=20
> originates from=20
> within a large enterprise or campus, so that emergency help can be=20
> provided more expeditiously. For example, in the US (and, I believe,=20
> Canada), it's the law that large PBXs must provide this=20
> information to a=20
> semi-national database.=20
>=20
> One approach to solving this for IP-over-802 devices is to backtrack a

> MAC address to the switch and switch port, using switch forwarding=20
> tables. This applies to VoIP, naturally, but it's only a=20
> matter of time=20
> before the first 911/112-over-IM "call=20
>=20
> " happens.=20
>=20
> However, while most managed Ethernet switches have such tables (and we

> apparently locally have tools to use them, primarily to track down=20
> systems that have been compromised and are spewing attack packets),=20
> there doesn't seem to be a standard MIB for that. I may well=20
> have missed=20
> this in my quick browsing of the RFC MIB list, but that's=20
> what our local=20
> network admin claimed.=20
>=20
> Is there a standard way of solving the same problem? If not, should=20
> there be?=20
>=20
> Henning=20
> - --=20
> Henning Schulzrinne   http://www.cs.columbia.edu/~hgs=20
>=20
> _______________________________________________=20
> Hubmib mailing list=20
> Hubmib@ietf.org=20
> https://www1.ietf.org/mailman/listinfo/hubmib=20
>=20


------_=_NextPart_001_01C1B044.2EFE967B
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>RE: [Hubmib] FW: Ethernet switch forwarding table MIB? =
(fwd)</TITLE>

<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D608374301-08022002>The=20
issue of localization of an IP phone for emergency calls =
('E911')&nbsp;is more=20
complex then MIB support. There is work done in other standard bodies, =
for=20
example in TIA Standards Committee TR-41. Some of the contributions in =
TIA refer=20
standard SNMP MIBs, but the solution is more complex as it needs to =
include=20
interfaces with the emergency system and update of users and location=20
data-bases.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D608374301-08022002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D608374301-08022002>I=20
would observe that the use of sysLocation of the switch would not help. =
What is=20
needed is the location of the IP phone, and not of the switch. So =
assuming that=20
the ptopo or Bridge MIBs would locate an IP phone by its MAC address at =
the port=20
of the bridge, the exact location of the phone cannot be retrieved from =
any=20
objects in existing standard MIBs that I am aware =
about.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D608374301-08022002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D608374301-08022002>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D608374301-08022002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D608374301-08022002>Dan</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D608374301-08022002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D608374301-08022002>&nbsp;</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Harrington, David=20
  [mailto:dbh@enterasys.com]<BR><B>Sent:</B> Friday, February 08, 2002 =
12:09=20
  AM<BR><B>To:</B> Hubmib Mailing List<BR><B>Subject:</B> RE: [Hubmib] =
FW:=20
  Ethernet switch forwarding table MIB? (fwd)<BR><BR></FONT></DIV>
  <P><FONT size=3D2>Hi,</FONT> </P>
  <P><FONT size=3D2>The phrasing of your question is a bit ambiguous - a =
standard=20
  mib for what? </FONT></P>
  <P><FONT size=3D2>There is no standard mib to my knowledge designed to =
solve the=20
  911 location issue directly.</FONT> </P>
  <P><FONT size=3D2>identifying the room a switch is in? The system MIB =
contains=20
  an object (sysLocation) where an operator can specify the device=20
  location.</FONT></P>
  <P><FONT size=3D2>the backtracking of MAC addresses? I don't think =
there is a=20
  standard mib for this directly, but there are some mibs with data that =
could=20
  be used to backtrack MAC addresses. PTOPO (RFC2922) contains physical =
topology=20
  connections. </FONT></P>
  <P><FONT size=3D2>I hope this helps,</FONT> <BR><FONT =
size=3D2>dbh</FONT> </P>
  <P><FONT size=3D2>&gt; -----Original Message-----</FONT> <BR><FONT =
size=3D2>&gt;=20
  From: Wijnen, Bert (Bert) [<A=20
  =
href=3D"mailto:bwijnen@lucent.com">mailto:bwijnen@lucent.com</A>]</FONT> =

  <BR><FONT size=3D2>&gt; Sent: Saturday, February 02, 2002 6:53 =
AM</FONT>=20
  <BR><FONT size=3D2>&gt; To: Hubmib Mailing List</FONT> <BR><FONT =
size=3D2>&gt;=20
  Subject: [Hubmib] FW: Ethernet switch forwarding table MIB? =
(fwd)</FONT>=20
  <BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; HUBMIBbers...</FONT> <BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; Any input or answer on this question?</FONT> <BR><FONT =
size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; Bert</FONT> <BR><FONT size=3D2>&gt; --- =
original=20
  email -------</FONT> <BR><FONT size=3D2>&gt; </FONT><BR><FONT =
size=3D2>&gt; Date:=20
  Fri, 01 Feb 2002 10:33:05 -0500</FONT> <BR><FONT size=3D2>&gt; From: =
"Henning G.=20
  Schulzrinne" &lt;hgs@cs.columbia.edu&gt;</FONT> <BR><FONT =
size=3D2>&gt;=20
  Organization: Dept. of Computer Science, Columbia University</FONT> =
<BR><FONT=20
  size=3D2>&gt; To: iab@ISI.EDU</FONT> <BR><FONT size=3D2>&gt; Subject: =
Ethernet=20
  switch forwarding table MIB?</FONT> <BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; I normally don't get close to MIBs, but here's a problem =
that I=20
  found</FONT> <BR><FONT size=3D2>&gt; surprisingly difficult to solve =
in a=20
  vendor-independent way:</FONT> <BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; For emergency calls, some countries mandate that you can =
figure=20
  out</FONT> <BR><FONT size=3D2>&gt; which room a call originates from, =
if the=20
  emergency call </FONT><BR><FONT size=3D2>&gt; originates from</FONT> =
<BR><FONT=20
  size=3D2>&gt; within a large enterprise or campus, so that emergency =
help can=20
  be</FONT> <BR><FONT size=3D2>&gt; provided more expeditiously. For =
example, in=20
  the US (and, I believe,</FONT> <BR><FONT size=3D2>&gt; Canada), it's =
the law=20
  that large PBXs must provide this </FONT><BR><FONT size=3D2>&gt; =
information to=20
  a</FONT> <BR><FONT size=3D2>&gt; semi-national database.</FONT> =
<BR><FONT=20
  size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; One approach to solving =
this for=20
  IP-over-802 devices is to backtrack a</FONT> <BR><FONT size=3D2>&gt; =
MAC address=20
  to the switch and switch port, using switch forwarding</FONT> =
<BR><FONT=20
  size=3D2>&gt; tables. This applies to VoIP, naturally, but it's only a =

  </FONT><BR><FONT size=3D2>&gt; matter of time</FONT> <BR><FONT =
size=3D2>&gt;=20
  before the first 911/112-over-IM "call</FONT> <BR><FONT size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; " happens.</FONT> <BR><FONT =
size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; However, while most managed Ethernet =
switches=20
  have such tables (and we</FONT> <BR><FONT size=3D2>&gt; apparently =
locally have=20
  tools to use them, primarily to track down</FONT> <BR><FONT =
size=3D2>&gt;=20
  systems that have been compromised and are spewing attack =
packets),</FONT>=20
  <BR><FONT size=3D2>&gt; there doesn't seem to be a standard MIB for =
that. I may=20
  well </FONT><BR><FONT size=3D2>&gt; have missed</FONT> <BR><FONT =
size=3D2>&gt;=20
  this in my quick browsing of the RFC MIB list, but that's =
</FONT><BR><FONT=20
  size=3D2>&gt; what our local</FONT> <BR><FONT size=3D2>&gt; network =
admin=20
  claimed.</FONT> <BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; =
Is there a=20
  standard way of solving the same problem? If not, should</FONT> =
<BR><FONT=20
  size=3D2>&gt; there be?</FONT> <BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; Henning</FONT> <BR><FONT size=3D2>&gt; - -- =
</FONT><BR><FONT=20
  size=3D2>&gt; Henning Schulzrinne&nbsp;&nbsp; <A target=3D_blank=20
  =
href=3D"http://www.cs.columbia.edu/~hgs">http://www.cs.columbia.edu/~hgs<=
/A></FONT>=20
  <BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt;=20
  _______________________________________________</FONT> <BR><FONT =
size=3D2>&gt;=20
  Hubmib mailing list</FONT> <BR><FONT size=3D2>&gt; =
Hubmib@ietf.org</FONT>=20
  <BR><FONT size=3D2>&gt; <A target=3D_blank=20
  =
href=3D"https://www1.ietf.org/mailman/listinfo/hubmib">https://www1.ietf.=
org/mailman/listinfo/hubmib</A></FONT>=20
  <BR><FONT size=3D2>&gt; </FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1B044.2EFE967B--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Fri Feb  8 11:37:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14061
	for <hubmib-archive@odin.ietf.org>; Fri, 8 Feb 2002 11:37:35 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18899;
	Fri, 8 Feb 2002 11:36:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18869
	for <hubmib@optimus.ietf.org>; Fri, 8 Feb 2002 11:36:57 -0500 (EST)
Received: from creeper.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14028
	for <hubmib@ietf.org>; Fri, 8 Feb 2002 11:36:54 -0500 (EST)
Received: from ec03-hou.bmc.com (localhost [127.0.0.1])
	by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id g18Ga7f10024;
	Fri, 8 Feb 2002 10:36:07 -0600 (CST)
Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2653.19)
	id <D1F84R3P>; Fri, 8 Feb 2002 10:36:25 -0600
Message-ID: <D77353F1D8FCD411AC3400105A640BB5710778@es01-sjc.bmc.com>
From: "Ayers, Mike" <Mike_Ayers@bmc.com>
To: Hubmib Mailing List <hubmib@ietf.org>, hgs@cs.columbia.edu
Subject: RE: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Date: Fri, 8 Feb 2002 10:36:18 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org


	The problem of physically locating terminal devices is very complex
and it isn't.

	Huh?

	Okay, let me put it this way.

	Untangling the network to determine the path to the originating
device is a very complex problem, which is addressed in part by RFC2922.

	However, this does not tell you anything about where the terminal
device is in physical space, just logical space.  You may know which router
it's connected to, you may know where that router is, but how long is the
cable between the router and the terminal device?

	For the time being, only a simple solution is implementable.  The
upside is that you can do this with little or no technical change (I would
recommend using sysLocation for the information).  The downside is that you
need absolute discipline in order for such a system to work - any time a
machine is moved, the location information would need to be double checked,
or else you may have bad location information.

	What would be a long term solution?  I don't know.  Even embedded
GPS encoded into the VoIP stream would not be able to tell you which floor
the device is on, so I don't hold out much hope for a purely technical
solution. Maybe there's no time like the present to start practicing
discipline.


/|/|ike

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Fri Feb  8 11:37:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14071
	for <hubmib-archive@odin.ietf.org>; Fri, 8 Feb 2002 11:37:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA18955
	for hubmib-archive@odin.ietf.org; Fri, 8 Feb 2002 11:37:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18899;
	Fri, 8 Feb 2002 11:36:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18869
	for <hubmib@optimus.ietf.org>; Fri, 8 Feb 2002 11:36:57 -0500 (EST)
Received: from creeper.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14028
	for <hubmib@ietf.org>; Fri, 8 Feb 2002 11:36:54 -0500 (EST)
Received: from ec03-hou.bmc.com (localhost [127.0.0.1])
	by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id g18Ga7f10024;
	Fri, 8 Feb 2002 10:36:07 -0600 (CST)
Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2653.19)
	id <D1F84R3P>; Fri, 8 Feb 2002 10:36:25 -0600
Message-ID: <D77353F1D8FCD411AC3400105A640BB5710778@es01-sjc.bmc.com>
From: "Ayers, Mike" <Mike_Ayers@bmc.com>
To: Hubmib Mailing List <hubmib@ietf.org>, hgs@cs.columbia.edu
Subject: RE: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Date: Fri, 8 Feb 2002 10:36:18 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org


	The problem of physically locating terminal devices is very complex
and it isn't.

	Huh?

	Okay, let me put it this way.

	Untangling the network to determine the path to the originating
device is a very complex problem, which is addressed in part by RFC2922.

	However, this does not tell you anything about where the terminal
device is in physical space, just logical space.  You may know which router
it's connected to, you may know where that router is, but how long is the
cable between the router and the terminal device?

	For the time being, only a simple solution is implementable.  The
upside is that you can do this with little or no technical change (I would
recommend using sysLocation for the information).  The downside is that you
need absolute discipline in order for such a system to work - any time a
machine is moved, the location information would need to be double checked,
or else you may have bad location information.

	What would be a long term solution?  I don't know.  Even embedded
GPS encoded into the VoIP stream would not be able to tell you which floor
the device is on, so I don't hold out much hope for a purely technical
solution. Maybe there's no time like the present to start practicing
discipline.


/|/|ike

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Sat Feb  9 13:16:39 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18477
	for <hubmib-archive@odin.ietf.org>; Sat, 9 Feb 2002 13:16:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27583;
	Sat, 9 Feb 2002 13:08:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27551
	for <hubmib@optimus.ietf.org>; Sat, 9 Feb 2002 13:08:46 -0500 (EST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18393
	for <hubmib@ietf.org>; Sat, 9 Feb 2002 13:08:43 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id NAA29679;
	Sat, 9 Feb 2002 13:08:38 -0500 (EST)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g19I8bJ2000191
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 9 Feb 2002 13:08:38 -0500 (EST)
Message-ID: <3C6565A3.BAB5ABA0@cs.columbia.edu>
Date: Sat, 09 Feb 2002 13:08:35 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ayers, Mike" <Mike_Ayers@bmc.com>
CC: Hubmib Mailing List <hubmib@ietf.org>
Subject: Re: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
References: <D77353F1D8FCD411AC3400105A640BB5710778@es01-sjc.bmc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 7bit

Do you happen to know if RFC 2922 is widely implemented in standard
switched Ethernet (say) LAN switches?

"Ayers, Mike" wrote:
> 
>         Untangling the network to determine the path to the originating
> device is a very complex problem, which is addressed in part by RFC2922.
> 
>         However, this does not tell you anything about where the terminal
> device is in physical space, just logical space.  You may know which router
> it's connected to, you may know where that router is, but how long is the
> cable between the router and the terminal device?

Fortunately, a large fraction of the cables are limited to 100' or so
and a single floor, so even without a good jack-to-room database, that
beats searching a whole building or, worse, a campus with dozens of
buildings.

>         What would be a long term solution?  I don't know.  Even embedded
> GPS encoded into the VoIP stream would not be able to tell you which floor
> the device is on, so I don't hold out much hope for a purely technical

Plus, GPS tends not to work well indoors.

> solution. Maybe there's no time like the present to start practicing
> discipline.
> 
> /|/|ike

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Sat Feb  9 13:16:39 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18487
	for <hubmib-archive@odin.ietf.org>; Sat, 9 Feb 2002 13:16:39 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA27949
	for hubmib-archive@odin.ietf.org; Sat, 9 Feb 2002 13:16:41 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27583;
	Sat, 9 Feb 2002 13:08:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27551
	for <hubmib@optimus.ietf.org>; Sat, 9 Feb 2002 13:08:46 -0500 (EST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18393
	for <hubmib@ietf.org>; Sat, 9 Feb 2002 13:08:43 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id NAA29679;
	Sat, 9 Feb 2002 13:08:38 -0500 (EST)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g19I8bJ2000191
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 9 Feb 2002 13:08:38 -0500 (EST)
Message-ID: <3C6565A3.BAB5ABA0@cs.columbia.edu>
Date: Sat, 09 Feb 2002 13:08:35 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ayers, Mike" <Mike_Ayers@bmc.com>
CC: Hubmib Mailing List <hubmib@ietf.org>
Subject: Re: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
References: <D77353F1D8FCD411AC3400105A640BB5710778@es01-sjc.bmc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 7bit

Do you happen to know if RFC 2922 is widely implemented in standard
switched Ethernet (say) LAN switches?

"Ayers, Mike" wrote:
> 
>         Untangling the network to determine the path to the originating
> device is a very complex problem, which is addressed in part by RFC2922.
> 
>         However, this does not tell you anything about where the terminal
> device is in physical space, just logical space.  You may know which router
> it's connected to, you may know where that router is, but how long is the
> cable between the router and the terminal device?

Fortunately, a large fraction of the cables are limited to 100' or so
and a single floor, so even without a good jack-to-room database, that
beats searching a whole building or, worse, a campus with dozens of
buildings.

>         What would be a long term solution?  I don't know.  Even embedded
> GPS encoded into the VoIP stream would not be able to tell you which floor
> the device is on, so I don't hold out much hope for a purely technical

Plus, GPS tends not to work well indoors.

> solution. Maybe there's no time like the present to start practicing
> discipline.
> 
> /|/|ike

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Sat Feb  9 13:21:13 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18570
	for <hubmib-archive@odin.ietf.org>; Sat, 9 Feb 2002 13:21:12 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27829;
	Sat, 9 Feb 2002 13:14:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27803
	for <hubmib@optimus.ietf.org>; Sat, 9 Feb 2002 13:14:31 -0500 (EST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18454
	for <hubmib@ietf.org>; Sat, 9 Feb 2002 13:14:28 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id NAA00043;
	Sat, 9 Feb 2002 13:13:51 -0500 (EST)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g19IDoJ2000309
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 9 Feb 2002 13:13:50 -0500 (EST)
Message-ID: <3C6566DB.3BAEF118@cs.columbia.edu>
Date: Sat, 09 Feb 2002 13:13:47 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Harrington, David" <dbh@enterasys.com>
CC: Hubmib Mailing List <hubmib@ietf.org>
Subject: Re: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
References: <0BF8B32B723ED5119E0B0002A551748B01FA0886@corp-exc3.ctron.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 7bit

> "Harrington, David" wrote:
> 
> Hi,
> 
> The phrasing of your question is a bit ambiguous - a standard mib for
> what?
> 

Basically, what I'm looking for is something that says "MAC address X
was seen on port Y of this switch".

> 
> the backtracking of MAC addresses? I don't think there is a standard
> mib for this directly, but there are some mibs with data that could be
> used to backtrack MAC addresses. PTOPO (RFC2922) contains physical
> topology connections.

Is this something implemented by Ethernet LANs?

>

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Sat Feb  9 13:21:13 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18580
	for <hubmib-archive@odin.ietf.org>; Sat, 9 Feb 2002 13:21:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA28181
	for hubmib-archive@odin.ietf.org; Sat, 9 Feb 2002 13:21:15 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27829;
	Sat, 9 Feb 2002 13:14:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27803
	for <hubmib@optimus.ietf.org>; Sat, 9 Feb 2002 13:14:31 -0500 (EST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18454
	for <hubmib@ietf.org>; Sat, 9 Feb 2002 13:14:28 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id NAA00043;
	Sat, 9 Feb 2002 13:13:51 -0500 (EST)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g19IDoJ2000309
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 9 Feb 2002 13:13:50 -0500 (EST)
Message-ID: <3C6566DB.3BAEF118@cs.columbia.edu>
Date: Sat, 09 Feb 2002 13:13:47 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Harrington, David" <dbh@enterasys.com>
CC: Hubmib Mailing List <hubmib@ietf.org>
Subject: Re: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
References: <0BF8B32B723ED5119E0B0002A551748B01FA0886@corp-exc3.ctron.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 7bit

> "Harrington, David" wrote:
> 
> Hi,
> 
> The phrasing of your question is a bit ambiguous - a standard mib for
> what?
> 

Basically, what I'm looking for is something that says "MAC address X
was seen on port Y of this switch".

> 
> the backtracking of MAC addresses? I don't think there is a standard
> mib for this directly, but there are some mibs with data that could be
> used to backtrack MAC addresses. PTOPO (RFC2922) contains physical
> topology connections.

Is this something implemented by Ethernet LANs?

>

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Mon Feb 11 04:33:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27148
	for <hubmib-archive@odin.ietf.org>; Mon, 11 Feb 2002 04:33:36 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA25946;
	Mon, 11 Feb 2002 04:25:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA25917
	for <hubmib@ns.ietf.org>; Mon, 11 Feb 2002 04:25:06 -0500 (EST)
Received: from columba.eur.3com.com (columba.eur.3com.com [161.71.169.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27061
	for <hubmib@ietf.org>; Mon, 11 Feb 2002 04:25:03 -0500 (EST)
Received: from toucana.eur.3com.com (toucana.EUR.3Com.COM [140.204.220.50])
	by columba.eur.3com.com  with ESMTP id g1B9QpU16758;
	Mon, 11 Feb 2002 09:26:51 GMT
Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206])
	by toucana.eur.3com.com  with SMTP id g1B9OmQ13623;
	Mon, 11 Feb 2002 09:24:49 GMT
Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 80256B5D.0033BC6D ; Mon, 11 Feb 2002 09:25:05 +0000
X-Lotus-FromDomain: 3COM
From: "Les Bell" <Les_Bell@eur.3com.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: "Harrington, David" <dbh@enterasys.com>,
        Hubmib Mailing List <hubmib@ietf.org>
Message-ID: <80256B5D.0033BB3C.00@notesmta.eur.3com.com>
Date: Mon, 11 Feb 2002 09:20:27 +0000
Subject: Re: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org




"Henning Schulzrinne" wrote:

> Basically, what I'm looking for is something that says "MAC address X
> was seen on port Y of this switch".

This is available in the Bridge MIBs:

dot1dTpFdbTable  (RFC 1493)
This table is indexed by MAC address.
dot1dTpFdbPort returns the port number the MAC address was seen on.

dot1qTpFdbTable  (RFC 2674)
This table is indexed by VLAN and MAC address.
dot1qTpFdbPort returns the port number the MAC address was seen on,
within the given VLAN.

Les...





Henning Schulzrinne <hgs@cs.columbia.edu> on 09/02/2002 18:13:47

Sent by:  Henning Schulzrinne <hgs@cs.columbia.edu>


To:   "Harrington, David" <dbh@enterasys.com>
cc:   Hubmib Mailing List <hubmib@ietf.org> (Les Bell/GB/3Com)
Subject:  Re: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)




> "Harrington, David" wrote:
>
> Hi,
>
> The phrasing of your question is a bit ambiguous - a standard mib for
> what?
>

Basically, what I'm looking for is something that says "MAC address X
was seen on port Y of this switch".

>
> the backtracking of MAC addresses? I don't think there is a standard
> mib for this directly, but there are some mibs with data that could be
> used to backtrack MAC addresses. PTOPO (RFC2922) contains physical
> topology connections.

Is this something implemented by Ethernet LANs?

>

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib





_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@ns.ietf.org  Mon Feb 11 04:33:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27158
	for <hubmib-archive@odin.ietf.org>; Mon, 11 Feb 2002 04:33:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA26657
	for hubmib-archive@odin.ietf.org; Mon, 11 Feb 2002 04:33:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA25946;
	Mon, 11 Feb 2002 04:25:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA25917
	for <hubmib@ns.ietf.org>; Mon, 11 Feb 2002 04:25:06 -0500 (EST)
Received: from columba.eur.3com.com (columba.eur.3com.com [161.71.169.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27061
	for <hubmib@ietf.org>; Mon, 11 Feb 2002 04:25:03 -0500 (EST)
Received: from toucana.eur.3com.com (toucana.EUR.3Com.COM [140.204.220.50])
	by columba.eur.3com.com  with ESMTP id g1B9QpU16758;
	Mon, 11 Feb 2002 09:26:51 GMT
Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206])
	by toucana.eur.3com.com  with SMTP id g1B9OmQ13623;
	Mon, 11 Feb 2002 09:24:49 GMT
Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 80256B5D.0033BC6D ; Mon, 11 Feb 2002 09:25:05 +0000
X-Lotus-FromDomain: 3COM
From: "Les Bell" <Les_Bell@eur.3com.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: "Harrington, David" <dbh@enterasys.com>,
        Hubmib Mailing List <hubmib@ietf.org>
Message-ID: <80256B5D.0033BB3C.00@notesmta.eur.3com.com>
Date: Mon, 11 Feb 2002 09:20:27 +0000
Subject: Re: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org




"Henning Schulzrinne" wrote:

> Basically, what I'm looking for is something that says "MAC address X
> was seen on port Y of this switch".

This is available in the Bridge MIBs:

dot1dTpFdbTable  (RFC 1493)
This table is indexed by MAC address.
dot1dTpFdbPort returns the port number the MAC address was seen on.

dot1qTpFdbTable  (RFC 2674)
This table is indexed by VLAN and MAC address.
dot1qTpFdbPort returns the port number the MAC address was seen on,
within the given VLAN.

Les...





Henning Schulzrinne <hgs@cs.columbia.edu> on 09/02/2002 18:13:47

Sent by:  Henning Schulzrinne <hgs@cs.columbia.edu>


To:   "Harrington, David" <dbh@enterasys.com>
cc:   Hubmib Mailing List <hubmib@ietf.org> (Les Bell/GB/3Com)
Subject:  Re: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)




> "Harrington, David" wrote:
>
> Hi,
>
> The phrasing of your question is a bit ambiguous - a standard mib for
> what?
>

Basically, what I'm looking for is something that says "MAC address X
was seen on port Y of this switch".

>
> the backtracking of MAC addresses? I don't think there is a standard
> mib for this directly, but there are some mibs with data that could be
> used to backtrack MAC addresses. PTOPO (RFC2922) contains physical
> topology connections.

Is this something implemented by Ethernet LANs?

>

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib





_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Mon Feb 11 17:50:13 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19904
	for <hubmib-archive@odin.ietf.org>; Mon, 11 Feb 2002 17:50:13 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA06970;
	Mon, 11 Feb 2002 17:38:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA06943
	for <hubmib@optimus.ietf.org>; Mon, 11 Feb 2002 17:38:53 -0500 (EST)
Received: from creeper.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19745
	for <hubmib@ietf.org>; Mon, 11 Feb 2002 17:38:50 -0500 (EST)
Received: from ec03-hou.bmc.com (localhost [127.0.0.1])
	by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id g1BMbIo10991;
	Mon, 11 Feb 2002 16:37:18 -0600 (CST)
Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2653.19)
	id <D1F8V3M8>; Mon, 11 Feb 2002 16:37:35 -0600
Message-ID: <D77353F1D8FCD411AC3400105A640BB571077D@es01-sjc.bmc.com>
From: "Ayers, Mike" <Mike_Ayers@bmc.com>
To: "'Henning Schulzrinne'" <hgs@cs.columbia.edu>
Cc: Hubmib Mailing List <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Date: Mon, 11 Feb 2002 16:37:34 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org


> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu] 
> Sent: Saturday, February 09, 2002 10:09 AM

> Fortunately, a large fraction of the cables are limited to 100' or so
> and a single floor, so even without a good jack-to-room database, that
> beats searching a whole building or, worse, a campus with dozens of
> buildings.

	100 feet is five floors - in either direction.  Then there's fiber
links, which I believe (I haven't had time to look it up), are limited to a
few miles.

	It was my understanding that you were trying to locate the device,
not just narrow down the search.  The less accurate you need to be, the
easier to find a solution!


/|/|ike

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Mon Feb 11 17:50:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19914
	for <hubmib-archive@odin.ietf.org>; Mon, 11 Feb 2002 17:50:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA07441
	for hubmib-archive@odin.ietf.org; Mon, 11 Feb 2002 17:50:15 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA06970;
	Mon, 11 Feb 2002 17:38:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA06943
	for <hubmib@optimus.ietf.org>; Mon, 11 Feb 2002 17:38:53 -0500 (EST)
Received: from creeper.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19745
	for <hubmib@ietf.org>; Mon, 11 Feb 2002 17:38:50 -0500 (EST)
Received: from ec03-hou.bmc.com (localhost [127.0.0.1])
	by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id g1BMbIo10991;
	Mon, 11 Feb 2002 16:37:18 -0600 (CST)
Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2653.19)
	id <D1F8V3M8>; Mon, 11 Feb 2002 16:37:35 -0600
Message-ID: <D77353F1D8FCD411AC3400105A640BB571077D@es01-sjc.bmc.com>
From: "Ayers, Mike" <Mike_Ayers@bmc.com>
To: "'Henning Schulzrinne'" <hgs@cs.columbia.edu>
Cc: Hubmib Mailing List <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Date: Mon, 11 Feb 2002 16:37:34 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org


> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu] 
> Sent: Saturday, February 09, 2002 10:09 AM

> Fortunately, a large fraction of the cables are limited to 100' or so
> and a single floor, so even without a good jack-to-room database, that
> beats searching a whole building or, worse, a campus with dozens of
> buildings.

	100 feet is five floors - in either direction.  Then there's fiber
links, which I believe (I haven't had time to look it up), are limited to a
few miles.

	It was my understanding that you were trying to locate the device,
not just narrow down the search.  The less accurate you need to be, the
easier to find a solution!


/|/|ike

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Mon Feb 11 19:05:43 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20637
	for <hubmib-archive@odin.ietf.org>; Mon, 11 Feb 2002 19:05:43 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA10011;
	Mon, 11 Feb 2002 18:58:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA09981
	for <hubmib@optimus.ietf.org>; Mon, 11 Feb 2002 18:58:30 -0500 (EST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20544
	for <hubmib@ietf.org>; Mon, 11 Feb 2002 18:58:27 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id SAA01136;
	Mon, 11 Feb 2002 18:58:07 -0500 (EST)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g1BNw6J2012760
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Mon, 11 Feb 2002 18:58:06 -0500 (EST)
Message-ID: <3C685A88.F124F9C9@cs.columbia.edu>
Date: Mon, 11 Feb 2002 18:58:00 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ayers, Mike" <Mike_Ayers@bmc.com>
CC: Hubmib Mailing List <hubmib@ietf.org>
Subject: Re: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
References: <D77353F1D8FCD411AC3400105A640BB571077D@es01-sjc.bmc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 7bit


>         100 feet is five floors - in either direction.  Then there's fiber
> links, which I believe (I haven't had time to look it up), are limited to a
> few miles.
> 
>         It was my understanding that you were trying to locate the device,
> not just narrow down the search.  The less accurate you need to be, the
> easier to find a solution!

Actually, while accuracy is good, this is a game of probability: I want
to get the smallest likely error. After all, it's much better to know
that, with high probability, a device is within a few dozen feet of the
wall jack or Ethernet switch than just knowing that it's somewhere on a
squaremile corporate or university campus.

Practically speaking, I would imagine that some devices will allow or
force the user to enter her current location, but that information is
not always accurate, either. (For example, we have two buildings called
Schapiro on campus - about half a mile apart, to the perpetual
frustration of the pizza delivery service and UPS.)

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Mon Feb 11 19:05:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20650
	for <hubmib-archive@odin.ietf.org>; Mon, 11 Feb 2002 19:05:44 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA10593
	for hubmib-archive@odin.ietf.org; Mon, 11 Feb 2002 19:05:44 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA10011;
	Mon, 11 Feb 2002 18:58:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA09981
	for <hubmib@optimus.ietf.org>; Mon, 11 Feb 2002 18:58:30 -0500 (EST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20544
	for <hubmib@ietf.org>; Mon, 11 Feb 2002 18:58:27 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id SAA01136;
	Mon, 11 Feb 2002 18:58:07 -0500 (EST)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g1BNw6J2012760
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Mon, 11 Feb 2002 18:58:06 -0500 (EST)
Message-ID: <3C685A88.F124F9C9@cs.columbia.edu>
Date: Mon, 11 Feb 2002 18:58:00 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ayers, Mike" <Mike_Ayers@bmc.com>
CC: Hubmib Mailing List <hubmib@ietf.org>
Subject: Re: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
References: <D77353F1D8FCD411AC3400105A640BB571077D@es01-sjc.bmc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 7bit


>         100 feet is five floors - in either direction.  Then there's fiber
> links, which I believe (I haven't had time to look it up), are limited to a
> few miles.
> 
>         It was my understanding that you were trying to locate the device,
> not just narrow down the search.  The less accurate you need to be, the
> easier to find a solution!

Actually, while accuracy is good, this is a game of probability: I want
to get the smallest likely error. After all, it's much better to know
that, with high probability, a device is within a few dozen feet of the
wall jack or Ethernet switch than just knowing that it's somewhere on a
squaremile corporate or university campus.

Practically speaking, I would imagine that some devices will allow or
force the user to enter her current location, but that information is
not always accurate, either. (For example, we have two buildings called
Schapiro on campus - about half a mile apart, to the perpetual
frustration of the pizza delivery service and UPS.)

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Tue Feb 12 01:52:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27245
	for <hubmib-archive@odin.ietf.org>; Tue, 12 Feb 2002 01:52:31 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA04078;
	Tue, 12 Feb 2002 01:45:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA04047
	for <hubmib@optimus.ietf.org>; Tue, 12 Feb 2002 01:45:36 -0500 (EST)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27182
	for <hubmib@ietf.org>; Tue, 12 Feb 2002 01:45:35 -0500 (EST)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id BAA11764
	for <hubmib@ietf.org>; Tue, 12 Feb 2002 01:44:06 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id BAA11755
	for <hubmib@ietf.org>; Tue, 12 Feb 2002 01:44:04 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Date: Tue, 12 Feb 2002 08:44:40 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F60D0A8@IS0004AVEXU1.global.avaya.com>
Thread-Topic: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Thread-Index: AcGzV/A4CaAcsBjVTrGdqsOyPzHECwAN+qjw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>,
        "Ayers, Mike" <Mike_Ayers@bmc.com>
Cc: "Hubmib Mailing List" <hubmib@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id BAA04048
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 8bit

> 
> >         100 feet is five floors - in either direction.  
> Then there's fiber
> > links, which I believe (I haven't had time to look it up), 
> are limited to a
> > few miles.
> > 
> >         It was my understanding that you were trying to 
> locate the device,
> > not just narrow down the search.  The less accurate you 
> need to be, the
> > easier to find a solution!
> 
> Actually, while accuracy is good, this is a game of 
> probability: I want
> to get the smallest likely error. After all, it's much better to know
> that, with high probability, a device is within a few dozen 
> feet of the
> wall jack or Ethernet switch than just knowing that it's 
> somewhere on a
> squaremile corporate or university campus.
> 
> Practically speaking, I would imagine that some devices will allow or
> force the user to enter her current location, but that information is
> not always accurate, either. (For example, we have two 
> buildings called
> Schapiro on campus - about half a mile apart, to the perpetual
> frustration of the pizza delivery service and UPS.)
> 

If I want my pizza hot I should rather specify that I mean the 'tall
Shapiro building'!

As with any data base that includes location information, it is as
accurate as the data you input in the records. AFAIK an emergency data
base should include accurate location and the number of the closest
callback emergency phone (typically analog line, direct POTS connection)
for the area - there is some regulatory terminology for this. It should
be no problem to include this info in the sysLocation field, but again
the sysadm has the responsibility of accuracy and completeness of the
information.


Regards,

Dan
 
> 

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Tue Feb 12 01:52:34 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27259
	for <hubmib-archive@odin.ietf.org>; Tue, 12 Feb 2002 01:52:34 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA04276
	for hubmib-archive@odin.ietf.org; Tue, 12 Feb 2002 01:52:32 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA04078;
	Tue, 12 Feb 2002 01:45:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA04047
	for <hubmib@optimus.ietf.org>; Tue, 12 Feb 2002 01:45:36 -0500 (EST)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27182
	for <hubmib@ietf.org>; Tue, 12 Feb 2002 01:45:35 -0500 (EST)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id BAA11764
	for <hubmib@ietf.org>; Tue, 12 Feb 2002 01:44:06 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id BAA11755
	for <hubmib@ietf.org>; Tue, 12 Feb 2002 01:44:04 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Date: Tue, 12 Feb 2002 08:44:40 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F60D0A8@IS0004AVEXU1.global.avaya.com>
Thread-Topic: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Thread-Index: AcGzV/A4CaAcsBjVTrGdqsOyPzHECwAN+qjw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>,
        "Ayers, Mike" <Mike_Ayers@bmc.com>
Cc: "Hubmib Mailing List" <hubmib@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id BAA04048
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 8bit

> 
> >         100 feet is five floors - in either direction.  
> Then there's fiber
> > links, which I believe (I haven't had time to look it up), 
> are limited to a
> > few miles.
> > 
> >         It was my understanding that you were trying to 
> locate the device,
> > not just narrow down the search.  The less accurate you 
> need to be, the
> > easier to find a solution!
> 
> Actually, while accuracy is good, this is a game of 
> probability: I want
> to get the smallest likely error. After all, it's much better to know
> that, with high probability, a device is within a few dozen 
> feet of the
> wall jack or Ethernet switch than just knowing that it's 
> somewhere on a
> squaremile corporate or university campus.
> 
> Practically speaking, I would imagine that some devices will allow or
> force the user to enter her current location, but that information is
> not always accurate, either. (For example, we have two 
> buildings called
> Schapiro on campus - about half a mile apart, to the perpetual
> frustration of the pizza delivery service and UPS.)
> 

If I want my pizza hot I should rather specify that I mean the 'tall
Shapiro building'!

As with any data base that includes location information, it is as
accurate as the data you input in the records. AFAIK an emergency data
base should include accurate location and the number of the closest
callback emergency phone (typically analog line, direct POTS connection)
for the area - there is some regulatory terminology for this. It should
be no problem to include this info in the sysLocation field, but again
the sysadm has the responsibility of accuracy and completeness of the
information.


Regards,

Dan
 
> 

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Tue Feb 12 14:18:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22715
	for <hubmib-archive@odin.ietf.org>; Tue, 12 Feb 2002 14:18:56 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA09328;
	Tue, 12 Feb 2002 14:11:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA09298
	for <hubmib@optimus.ietf.org>; Tue, 12 Feb 2002 14:11:55 -0500 (EST)
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22527
	for <hubmib@ietf.org>; Tue, 12 Feb 2002 14:11:53 -0500 (EST)
Received: from ec03-hou.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g1CJCrq00495;
	Tue, 12 Feb 2002 13:12:53 -0600 (CST)
Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2653.19)
	id <D1F8V6JC>; Tue, 12 Feb 2002 13:09:49 -0600
Message-ID: <D77353F1D8FCD411AC3400105A640BB5710781@es01-sjc.bmc.com>
From: "Ayers, Mike" <Mike_Ayers@bmc.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Cc: Hubmib Mailing List <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Date: Tue, 12 Feb 2002 13:09:49 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org


> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] 
> Sent: Monday, February 11, 2002 10:45 PM

> As with any data base that includes location information, it is as
> accurate as the data you input in the records. AFAIK an emergency data
> base should include accurate location and the number of the closest
> callback emergency phone (typically analog line, direct POTS 
> connection)
> for the area - there is some regulatory terminology for this. 
> It should
> be no problem to include this info in the sysLocation field, but again
> the sysadm has the responsibility of accuracy and completeness of the
> information.

	Let me strengthen my earlier statement:  If you are looking to use
some sort of topology algorithm as a substitute for carefully and properly
logging the location of terminal equipment, you are probably making a
mistake.  Strict discipline in tracking the location of the equipment is the
cornerstone of a system to locate that equipment, and there is no way around
it - it is how the telcos track their phones.  Topology data may play a role
in finding the equipment within your database, or sysLocation may be a good
way to store such info, but no algorithm can replace the discipline.

	Perhaps a more salient question is what system will have the lowest
overhead maintenance yet still yield very high probability of an accurate
location.  That, however, is probably drifting a little too far off topic
for this list.


/|/|ike

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Tue Feb 12 14:18:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22726
	for <hubmib-archive@odin.ietf.org>; Tue, 12 Feb 2002 14:18:56 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA09689
	for hubmib-archive@odin.ietf.org; Tue, 12 Feb 2002 14:18:58 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA09328;
	Tue, 12 Feb 2002 14:11:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA09298
	for <hubmib@optimus.ietf.org>; Tue, 12 Feb 2002 14:11:55 -0500 (EST)
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22527
	for <hubmib@ietf.org>; Tue, 12 Feb 2002 14:11:53 -0500 (EST)
Received: from ec03-hou.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g1CJCrq00495;
	Tue, 12 Feb 2002 13:12:53 -0600 (CST)
Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2653.19)
	id <D1F8V6JC>; Tue, 12 Feb 2002 13:09:49 -0600
Message-ID: <D77353F1D8FCD411AC3400105A640BB5710781@es01-sjc.bmc.com>
From: "Ayers, Mike" <Mike_Ayers@bmc.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Cc: Hubmib Mailing List <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: Ethernet switch forwarding table MIB? (fwd)
Date: Tue, 12 Feb 2002 13:09:49 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org


> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] 
> Sent: Monday, February 11, 2002 10:45 PM

> As with any data base that includes location information, it is as
> accurate as the data you input in the records. AFAIK an emergency data
> base should include accurate location and the number of the closest
> callback emergency phone (typically analog line, direct POTS 
> connection)
> for the area - there is some regulatory terminology for this. 
> It should
> be no problem to include this info in the sysLocation field, but again
> the sysadm has the responsibility of accuracy and completeness of the
> information.

	Let me strengthen my earlier statement:  If you are looking to use
some sort of topology algorithm as a substitute for carefully and properly
logging the location of terminal equipment, you are probably making a
mistake.  Strict discipline in tracking the location of the equipment is the
cornerstone of a system to locate that equipment, and there is no way around
it - it is how the telcos track their phones.  Topology data may play a role
in finding the equipment within your database, or sysLocation may be a good
way to store such info, but no algorithm can replace the discipline.

	Perhaps a more salient question is what system will have the lowest
overhead maintenance yet still yield very high probability of an accurate
location.  That, however, is probably drifting a little too far off topic
for this list.


/|/|ike

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Wed Feb 13 08:21:49 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00687
	for <hubmib-archive@odin.ietf.org>; Wed, 13 Feb 2002 08:21:49 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA02355;
	Wed, 13 Feb 2002 08:09:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA02328
	for <hubmib@optimus.ietf.org>; Wed, 13 Feb 2002 08:09:26 -0500 (EST)
Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00344
	for <hubmib@ietf.org>; Wed, 13 Feb 2002 08:09:23 -0500 (EST)
Received: from iere.net.avaya.com (localhost [127.0.0.1])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g1DD82H01201
	for <hubmib@ietf.org>; Wed, 13 Feb 2002 08:08:02 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g1DD81T01172
	for <hubmib@ietf.org>; Wed, 13 Feb 2002 08:08:02 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1B48F.88DA3A0E"
Date: Wed, 13 Feb 2002 15:08:31 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2FF542B1@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Ethernet Interfaces and Hub MIB WG Milestones Update
Thread-Index: AcG0j6AnagoSy5sESE6wxA7DSFjQvw==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
Subject: [Hubmib] Ethernet Interfaces and Hub MIB WG Milestones Update
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1B48F.88DA3A0E
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Hub MIB-ers,

We need to update our Charter milestones. Here is the status of our
deliverables:

Ethernet-like Interfaces and MAU MIB - the Internet-Drafts are ready for
last call. We are waiting for the tests to be performed by InterWorking
Labs to see if they affect in any way the Ethernet-like Interfaces MIB.
We can go to Last Call immediately after Minneapolis

WIS MIB - new draft is expected in the next two weeks. We can go to Last
Call immediately after.

Power Ethernet MIB - The IEEE 802.3af is still making changes to the
standard that may affect the MIB. I suggest to request an extension of
the milestones until July, to allow for a new version of the I-D to be
issued=20

Here are the milestones that I propose:

February 2002 - Issue new WIS MIB Internet-Draft
March 2002 - Meet in Minneapolis to discuss implementation results for
the Ethernet-like Interfaces MIB, and the last I-D for the WIS MIB
(joint meeting with AToM MIB WG)
March 2002 - New WIS MIB and Ethernet-like Interfaces MIB I-Ds (if
needed)
April 2002 - Last Call for the Ethernet-like Interfaces MIB, MAU MIB,
and WIS MIB
May 2002 - Submit the Ethernet-like Interfaces MIB, MAU MIB, and WIS MIB
to the IESG for consideration as Proposed Standard
July 2002 - New Internet-Draft for the Power Ethernet MIB
August 2002 - Last Call for the Power Ethernet MIB
September 2002 - Submit the Power Ethernet MIB to the IESG for
consideration as Proposed Standard

Please comment on the status and the proposed milestones.

Regards,

Dan


------_=_NextPart_001_01C1B48F.88DA3A0E
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DWINDOWS-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Ethernet Interfaces and Hub MIB WG Milestones Update</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Hub MIB-ers,</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">We need to update our Charter =
milestones. Here is the status of our deliverables:</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Ethernet-like Interfaces and =
MAU MIB - the Internet-Drafts are ready for last call. We are waiting =
for the tests to be performed by InterWorking Labs to see if they affect =
in any way the Ethernet-like Interfaces MIB. We can go to Last Call =
immediately after Minneapolis</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">WIS MIB - new draft is =
expected in the next two weeks. We can go to Last Call immediately =
after.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Power Ethernet MIB - The IEEE =
802.3af is still making changes to the standard that may affect the MIB. =
I suggest to request an extension of the milestones until July, to allow =
for a new version of the I-D to be issued </FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Here are the milestones that =
I propose:</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">February 2002 - Issue new WIS =
MIB Internet-Draft</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">March 2002 - Meet in =
Minneapolis to discuss implementation results for the Ethernet-like =
Interfaces MIB, and the last I-D for the WIS MIB (joint meeting with =
AToM MIB WG)</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">March 2002 - New WIS MIB and =
Ethernet-like Interfaces MIB I-Ds (if needed)</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">April 2002 - Last Call for =
the Ethernet-like Interfaces MIB, MAU MIB, and WIS MIB</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">May 2002 - Submit the =
Ethernet-like Interfaces MIB, MAU MIB, and WIS MIB to the IESG for =
consideration as Proposed Standard</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">July 2002 - New =
Internet-Draft for the Power Ethernet MIB</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">August 2002 - Last Call for =
the Power Ethernet MIB</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">September 2002 - Submit the =
Power Ethernet MIB to the IESG for consideration as Proposed =
Standard</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Please comment on the status =
and the proposed milestones.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Dan</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C1B48F.88DA3A0E--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Wed Feb 13 08:21:50 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00696
	for <hubmib-archive@odin.ietf.org>; Wed, 13 Feb 2002 08:21:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA02857
	for hubmib-archive@odin.ietf.org; Wed, 13 Feb 2002 08:21:52 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA02355;
	Wed, 13 Feb 2002 08:09:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA02328
	for <hubmib@optimus.ietf.org>; Wed, 13 Feb 2002 08:09:26 -0500 (EST)
Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00344
	for <hubmib@ietf.org>; Wed, 13 Feb 2002 08:09:23 -0500 (EST)
Received: from iere.net.avaya.com (localhost [127.0.0.1])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g1DD82H01201
	for <hubmib@ietf.org>; Wed, 13 Feb 2002 08:08:02 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g1DD81T01172
	for <hubmib@ietf.org>; Wed, 13 Feb 2002 08:08:02 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1B48F.88DA3A0E"
Date: Wed, 13 Feb 2002 15:08:31 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2FF542B1@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Ethernet Interfaces and Hub MIB WG Milestones Update
Thread-Index: AcG0j6AnagoSy5sESE6wxA7DSFjQvw==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
Subject: [Hubmib] Ethernet Interfaces and Hub MIB WG Milestones Update
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1B48F.88DA3A0E
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Hub MIB-ers,

We need to update our Charter milestones. Here is the status of our
deliverables:

Ethernet-like Interfaces and MAU MIB - the Internet-Drafts are ready for
last call. We are waiting for the tests to be performed by InterWorking
Labs to see if they affect in any way the Ethernet-like Interfaces MIB.
We can go to Last Call immediately after Minneapolis

WIS MIB - new draft is expected in the next two weeks. We can go to Last
Call immediately after.

Power Ethernet MIB - The IEEE 802.3af is still making changes to the
standard that may affect the MIB. I suggest to request an extension of
the milestones until July, to allow for a new version of the I-D to be
issued=20

Here are the milestones that I propose:

February 2002 - Issue new WIS MIB Internet-Draft
March 2002 - Meet in Minneapolis to discuss implementation results for
the Ethernet-like Interfaces MIB, and the last I-D for the WIS MIB
(joint meeting with AToM MIB WG)
March 2002 - New WIS MIB and Ethernet-like Interfaces MIB I-Ds (if
needed)
April 2002 - Last Call for the Ethernet-like Interfaces MIB, MAU MIB,
and WIS MIB
May 2002 - Submit the Ethernet-like Interfaces MIB, MAU MIB, and WIS MIB
to the IESG for consideration as Proposed Standard
July 2002 - New Internet-Draft for the Power Ethernet MIB
August 2002 - Last Call for the Power Ethernet MIB
September 2002 - Submit the Power Ethernet MIB to the IESG for
consideration as Proposed Standard

Please comment on the status and the proposed milestones.

Regards,

Dan


------_=_NextPart_001_01C1B48F.88DA3A0E
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DWINDOWS-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Ethernet Interfaces and Hub MIB WG Milestones Update</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Hub MIB-ers,</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">We need to update our Charter =
milestones. Here is the status of our deliverables:</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Ethernet-like Interfaces and =
MAU MIB - the Internet-Drafts are ready for last call. We are waiting =
for the tests to be performed by InterWorking Labs to see if they affect =
in any way the Ethernet-like Interfaces MIB. We can go to Last Call =
immediately after Minneapolis</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">WIS MIB - new draft is =
expected in the next two weeks. We can go to Last Call immediately =
after.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Power Ethernet MIB - The IEEE =
802.3af is still making changes to the standard that may affect the MIB. =
I suggest to request an extension of the milestones until July, to allow =
for a new version of the I-D to be issued </FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Here are the milestones that =
I propose:</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">February 2002 - Issue new WIS =
MIB Internet-Draft</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">March 2002 - Meet in =
Minneapolis to discuss implementation results for the Ethernet-like =
Interfaces MIB, and the last I-D for the WIS MIB (joint meeting with =
AToM MIB WG)</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">March 2002 - New WIS MIB and =
Ethernet-like Interfaces MIB I-Ds (if needed)</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">April 2002 - Last Call for =
the Ethernet-like Interfaces MIB, MAU MIB, and WIS MIB</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">May 2002 - Submit the =
Ethernet-like Interfaces MIB, MAU MIB, and WIS MIB to the IESG for =
consideration as Proposed Standard</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">July 2002 - New =
Internet-Draft for the Power Ethernet MIB</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">August 2002 - Last Call for =
the Power Ethernet MIB</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">September 2002 - Submit the =
Power Ethernet MIB to the IESG for consideration as Proposed =
Standard</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Please comment on the status =
and the proposed milestones.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Dan</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C1B48F.88DA3A0E--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Wed Feb 13 15:02:34 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19268
	for <hubmib-archive@odin.ietf.org>; Wed, 13 Feb 2002 15:02:34 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA27323;
	Wed, 13 Feb 2002 14:51:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA02141
	for <hubmib@optimus.ietf.org>; Wed, 13 Feb 2002 08:03:48 -0500 (EST)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00248
	for <hubmib@ietf.org>; Wed, 13 Feb 2002 08:03:44 -0500 (EST)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id IAA06200
	for <hubmib@ietf.org>; Wed, 13 Feb 2002 08:02:16 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id IAA06154
	for <hubmib@ietf.org>; Wed, 13 Feb 2002 08:02:12 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1B48E.BA464367"
Date: Wed, 13 Feb 2002 15:02:44 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F60D0AF@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Ethernet Interfaces and hub MIB Milestones Update
Thread-Index: AcG0jtFxPLySe5A6SsKd+mXTeZFEcw==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
Cc: "C. M. Heard" <heard@pobox.com>, "Nathan Kohn" <mvnk@lucent.com>,
        "Faye Ly" <fayely98@hotmail.com>, "Thomas Narten" <narten@us.ibm.com>,
        "Erik Nordmark" <nordmark@eng.sun.com>, "Randy Bush" <randy@psg.com>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Erik Nordmark" <Erik.Nordmark@eng.sun.com>,
        <atommib@research.telcordia.com>, "Avi Berger" <avib@voltaire.com>,
        "Chris Wellens" <chrisw@iwl.com>
Subject: [Hubmib] Ethernet Interfaces and hub MIB Milestones Update
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1B48E.BA464367
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Hub MIB-ers,

We need to update our Charter milestones. Here is the status of our
deliverables:

Ethernet-like Interfaces and MAU MIB - the Internet-Drafts are ready for
last call. We are waiting for the tests to be performed by InterWorking
Labs to see if they affect in any way the Ethernet-like Interfaces MIB.
We can go to Last Call immediately after Minneapolis

WIS MIB - new draft is expected in the next two weeks. We can go to Last
Call immediately after.

Power Ethernet MIB - The IEEE 802.3af is still making changes to the
standard that may affect the MIB. I suggest to request an extension of
the milestones until July, to allow for a new version of the I-D to be
issued=20

Here are the milestones that I propose:

February 2002 - Issue new WIS MIB Internet-Draft
March 2002 - Meet in Minneapolis to discuss implementation results for
the Ethernet-like Interfaces MIB, and the last I-D for the WIS MIB
(joint meeting with AToM MIB WG)
March 2002 - New WIS MIB and Ethernet-like Interfaces MIB I-Ds (if
needed)
April 2002 - Last Call for the Ethernet-like Interfaces MIB, MAU MIB,
and WIS MIB
May 2002 - Submit the Ethernet-like Interfaces MIB, MAU MIB, and WIS MIB
to the IESG for consideration as Proposed Standard
July 2002 - New Internet-Draft for the Power Ethernet MIB
August 2002 - Last Call for the Power Ethernet MIB
September 2002 - Submit the Power Ethernet MIB to the IESG for
consideration as Proposed Standard

Please comment on the status and the proposed milestones.

Regards,

Dan
=20


------_=_NextPart_001_01C1B48E.BA464367
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DWINDOWS-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Ethernet Interfaces and hub MIB Milestones Update</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Hub MIB-ers,</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">We need to update our Charter =
milestones. Here is the status of our deliverables:</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Ethernet-like Interfaces and =
MAU MIB - the Internet-Drafts are ready for last call. We are waiting =
for the tests to be performed by InterWorking Labs to see if they affect =
in any way the Ethernet-like Interfaces MIB. We can go to Last Call =
immediately after Minneapolis</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">WIS MIB - new draft is =
expected in the next two weeks. We can go to Last Call immediately =
after.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Power Ethernet MIB - The IEEE =
802.3af is still making changes to the standard that may affect the MIB. =
I suggest to request an extension of the milestones until July, to allow =
for a new version of the I-D to be issued </FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Here are the milestones that =
I propose:</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">February 2002 - Issue new WIS =
MIB Internet-Draft</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">March 2002 - Meet in =
Minneapolis to discuss implementation results for the Ethernet-like =
Interfaces MIB, and the last I-D for the WIS MIB (joint meeting with =
AToM MIB WG)</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">March 2002 - New WIS MIB and =
Ethernet-like Interfaces MIB I-Ds (if needed)</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">April 2002 - Last Call for =
the Ethernet-like Interfaces MIB, MAU MIB, and WIS MIB</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">May 2002 - Submit the =
Ethernet-like Interfaces MIB, MAU MIB, and WIS MIB to the IESG for =
consideration as Proposed Standard</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">July 2002 - New =
Internet-Draft for the Power Ethernet MIB</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">August 2002 - Last Call for =
the Power Ethernet MIB</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">September 2002 - Submit the =
Power Ethernet MIB to the IESG for consideration as Proposed =
Standard</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Please comment on the status =
and the proposed milestones.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Dan</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C1B48E.BA464367--


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Wed Feb 13 15:02:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19281
	for <hubmib-archive@odin.ietf.org>; Wed, 13 Feb 2002 15:02:34 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA28091
	for hubmib-archive@odin.ietf.org; Wed, 13 Feb 2002 15:02:37 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA27323;
	Wed, 13 Feb 2002 14:51:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA02141
	for <hubmib@optimus.ietf.org>; Wed, 13 Feb 2002 08:03:48 -0500 (EST)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00248
	for <hubmib@ietf.org>; Wed, 13 Feb 2002 08:03:44 -0500 (EST)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id IAA06200
	for <hubmib@ietf.org>; Wed, 13 Feb 2002 08:02:16 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id IAA06154
	for <hubmib@ietf.org>; Wed, 13 Feb 2002 08:02:12 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1B48E.BA464367"
Date: Wed, 13 Feb 2002 15:02:44 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F60D0AF@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Ethernet Interfaces and hub MIB Milestones Update
Thread-Index: AcG0jtFxPLySe5A6SsKd+mXTeZFEcw==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
Cc: "C. M. Heard" <heard@pobox.com>, "Nathan Kohn" <mvnk@lucent.com>,
        "Faye Ly" <fayely98@hotmail.com>, "Thomas Narten" <narten@us.ibm.com>,
        "Erik Nordmark" <nordmark@eng.sun.com>, "Randy Bush" <randy@psg.com>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Erik Nordmark" <Erik.Nordmark@eng.sun.com>,
        <atommib@research.telcordia.com>, "Avi Berger" <avib@voltaire.com>,
        "Chris Wellens" <chrisw@iwl.com>
Subject: [Hubmib] Ethernet Interfaces and hub MIB Milestones Update
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1B48E.BA464367
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Hub MIB-ers,

We need to update our Charter milestones. Here is the status of our
deliverables:

Ethernet-like Interfaces and MAU MIB - the Internet-Drafts are ready for
last call. We are waiting for the tests to be performed by InterWorking
Labs to see if they affect in any way the Ethernet-like Interfaces MIB.
We can go to Last Call immediately after Minneapolis

WIS MIB - new draft is expected in the next two weeks. We can go to Last
Call immediately after.

Power Ethernet MIB - The IEEE 802.3af is still making changes to the
standard that may affect the MIB. I suggest to request an extension of
the milestones until July, to allow for a new version of the I-D to be
issued=20

Here are the milestones that I propose:

February 2002 - Issue new WIS MIB Internet-Draft
March 2002 - Meet in Minneapolis to discuss implementation results for
the Ethernet-like Interfaces MIB, and the last I-D for the WIS MIB
(joint meeting with AToM MIB WG)
March 2002 - New WIS MIB and Ethernet-like Interfaces MIB I-Ds (if
needed)
April 2002 - Last Call for the Ethernet-like Interfaces MIB, MAU MIB,
and WIS MIB
May 2002 - Submit the Ethernet-like Interfaces MIB, MAU MIB, and WIS MIB
to the IESG for consideration as Proposed Standard
July 2002 - New Internet-Draft for the Power Ethernet MIB
August 2002 - Last Call for the Power Ethernet MIB
September 2002 - Submit the Power Ethernet MIB to the IESG for
consideration as Proposed Standard

Please comment on the status and the proposed milestones.

Regards,

Dan
=20


------_=_NextPart_001_01C1B48E.BA464367
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DWINDOWS-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Ethernet Interfaces and hub MIB Milestones Update</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Hub MIB-ers,</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">We need to update our Charter =
milestones. Here is the status of our deliverables:</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Ethernet-like Interfaces and =
MAU MIB - the Internet-Drafts are ready for last call. We are waiting =
for the tests to be performed by InterWorking Labs to see if they affect =
in any way the Ethernet-like Interfaces MIB. We can go to Last Call =
immediately after Minneapolis</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">WIS MIB - new draft is =
expected in the next two weeks. We can go to Last Call immediately =
after.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Power Ethernet MIB - The IEEE =
802.3af is still making changes to the standard that may affect the MIB. =
I suggest to request an extension of the milestones until July, to allow =
for a new version of the I-D to be issued </FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Here are the milestones that =
I propose:</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">February 2002 - Issue new WIS =
MIB Internet-Draft</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">March 2002 - Meet in =
Minneapolis to discuss implementation results for the Ethernet-like =
Interfaces MIB, and the last I-D for the WIS MIB (joint meeting with =
AToM MIB WG)</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">March 2002 - New WIS MIB and =
Ethernet-like Interfaces MIB I-Ds (if needed)</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">April 2002 - Last Call for =
the Ethernet-like Interfaces MIB, MAU MIB, and WIS MIB</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">May 2002 - Submit the =
Ethernet-like Interfaces MIB, MAU MIB, and WIS MIB to the IESG for =
consideration as Proposed Standard</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">July 2002 - New =
Internet-Draft for the Power Ethernet MIB</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">August 2002 - Last Call for =
the Power Ethernet MIB</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">September 2002 - Submit the =
Power Ethernet MIB to the IESG for consideration as Proposed =
Standard</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Please comment on the status =
and the proposed milestones.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Dan</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C1B48E.BA464367--


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Sun Feb 17 14:16:11 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10144
	for <hubmib-archive@odin.ietf.org>; Sun, 17 Feb 2002 14:16:11 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA23080;
	Sun, 17 Feb 2002 14:09:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA23053
	for <hubmib@optimus.ietf.org>; Sun, 17 Feb 2002 14:09:04 -0500 (EST)
Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10005
	for <hubmib@ietf.org>; Sun, 17 Feb 2002 14:09:01 -0500 (EST)
Received: from user-vcaulvl.dsl.mindspring.com ([216.175.87.245] helo=ANDREWHOME)
	by snipe.prod.itd.earthlink.net with smtp (Exim 3.33 #1)
	id 16cWgE-0001Uj-00; Sun, 17 Feb 2002 11:08:58 -0800
From: "Andrew Smith" <ah_smith@acm.org>
To: <hubmib@ietf.org>
Cc: <mattsquire@acm.org>
Date: Sun, 17 Feb 2002 11:37:31 -0800
Message-ID: <KIEAIFILPFNLNGMKLEMGMEBNDBAA.ah_smith@acm.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-reply-to: <3C6FDDAD.237AF2EA@acm.org>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Hubmib] RE: [EFM] Performance monitoring, installation, trouble shooting .
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 7bit

Forgive my ignorance on the history of the following statement in RFC2665:

"Note that the ifTestTable is now deprecated.  Work is underway to
   define a replacement MIB for system and interface testing.  It is
   expected that the tests defined in this document will be usable in
   this replacement MIB."

The "Ethernet in the First Mile" group in IEEE 802.3 is looking at
requirements for management; specific requirements are for the minimisation
of "truck-rolls" (see message thread below - it talks about a PHY-level
loopback requirement). Has there been any further work on this in any IETF
WG? Was the ifTest stuff thrown out because it might do strange un-SNMP-like
things like cut off connectivity for some (arbitrary? predetermined?) period
of time?

Could someone fill me in on the history here?

Thanks,

Andrew Smith



-----Original Message-----
From: owner-stds-802-3-efm@majordomo.ieee.org
[mailto:owner-stds-802-3-efm@majordomo.ieee.org]On Behalf Of Matt Squire
Sent: Sunday, February 17, 2002 8:43 AM
To: Roy Bynum
Cc: kmccammon@tri.sbc.com; stds-802-3-efm@ieee.org
Subject: Re: [EFM] Performance monitoring, installation, trouble
shooting .




I'll repeat the current status of loopback within OAM.
- A ping connectivity test is a requirement.
- A loopback mode is a requirement.
- Controlling the state of the loopback mode at the other end of a link
is a requirement.

There is also a group of people that believe that the functionality of
loopback can be achieved without a loopback mode, but enhancing the MIBS
and the PHY functionality.  They are actively investigating the
possibility.  When and if they think they can show equivalent
functionality, the results will be presented to the reflector.  At that
point everyone can judge whether the alternate method provides
equivalent function.

Loopback itself is a function.  The function is used to fulfill certain
operational requirements.  If those requirements can be met with other
methods, and this point can be provent to the group as whole (including
Kent), then the other methods deserve consideration.  I don't think this
is in any way conflicts with Kent's statement (though I'm sure he'll
correct me if I'm wrong).

Loopback will remain a requirement until someone can prove to the OAM
group that there is a better way.

- Matt


Roy Bynum wrote:
>
> Kent,
>
> I have found that if you do not use strong enough language, the vendors
> that may not have what you require, will attempt to "interpret" your words
> so that they can mean something totally different than what you
> intended.  If I am correct, you may want to resend your comment and use
the
> words "our operations requires that ability".  If you check with your
> equipment "certification" people for edge access infrastructure, you may
> find that loop back functionality at the physical layer is a hard
> requirement, just like it is on T1/T3 infrastructure today.  I know that
it
> was a requirement the large service provider that I was previously with.
>
> Thank you,
> Roy Bynum
>
> At 04:18 PM 2/15/2002 -0800, kmccammon@tri.sbc.com wrote:
>
> >Bob,
> >Loopback functionality is important for SBC, our operations need that
> >ability.
> >-Kent
> >
> >Kent G. McCammon
> >Broadband Access Group
> >SBC Technology Resources, Inc
> >4698 Willow Road
> >Pleasanton, CA 94588
> >925-598-1246
> >kmccammon@tri.sbc.com
> >


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Sun Feb 17 14:16:12 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10155
	for <hubmib-archive@odin.ietf.org>; Sun, 17 Feb 2002 14:16:12 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA23382
	for hubmib-archive@odin.ietf.org; Sun, 17 Feb 2002 14:16:14 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA23080;
	Sun, 17 Feb 2002 14:09:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA23053
	for <hubmib@optimus.ietf.org>; Sun, 17 Feb 2002 14:09:04 -0500 (EST)
Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10005
	for <hubmib@ietf.org>; Sun, 17 Feb 2002 14:09:01 -0500 (EST)
Received: from user-vcaulvl.dsl.mindspring.com ([216.175.87.245] helo=ANDREWHOME)
	by snipe.prod.itd.earthlink.net with smtp (Exim 3.33 #1)
	id 16cWgE-0001Uj-00; Sun, 17 Feb 2002 11:08:58 -0800
From: "Andrew Smith" <ah_smith@acm.org>
To: <hubmib@ietf.org>
Cc: <mattsquire@acm.org>
Date: Sun, 17 Feb 2002 11:37:31 -0800
Message-ID: <KIEAIFILPFNLNGMKLEMGMEBNDBAA.ah_smith@acm.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-reply-to: <3C6FDDAD.237AF2EA@acm.org>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Hubmib] RE: [EFM] Performance monitoring, installation, trouble shooting .
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 7bit

Forgive my ignorance on the history of the following statement in RFC2665:

"Note that the ifTestTable is now deprecated.  Work is underway to
   define a replacement MIB for system and interface testing.  It is
   expected that the tests defined in this document will be usable in
   this replacement MIB."

The "Ethernet in the First Mile" group in IEEE 802.3 is looking at
requirements for management; specific requirements are for the minimisation
of "truck-rolls" (see message thread below - it talks about a PHY-level
loopback requirement). Has there been any further work on this in any IETF
WG? Was the ifTest stuff thrown out because it might do strange un-SNMP-like
things like cut off connectivity for some (arbitrary? predetermined?) period
of time?

Could someone fill me in on the history here?

Thanks,

Andrew Smith



-----Original Message-----
From: owner-stds-802-3-efm@majordomo.ieee.org
[mailto:owner-stds-802-3-efm@majordomo.ieee.org]On Behalf Of Matt Squire
Sent: Sunday, February 17, 2002 8:43 AM
To: Roy Bynum
Cc: kmccammon@tri.sbc.com; stds-802-3-efm@ieee.org
Subject: Re: [EFM] Performance monitoring, installation, trouble
shooting .




I'll repeat the current status of loopback within OAM.
- A ping connectivity test is a requirement.
- A loopback mode is a requirement.
- Controlling the state of the loopback mode at the other end of a link
is a requirement.

There is also a group of people that believe that the functionality of
loopback can be achieved without a loopback mode, but enhancing the MIBS
and the PHY functionality.  They are actively investigating the
possibility.  When and if they think they can show equivalent
functionality, the results will be presented to the reflector.  At that
point everyone can judge whether the alternate method provides
equivalent function.

Loopback itself is a function.  The function is used to fulfill certain
operational requirements.  If those requirements can be met with other
methods, and this point can be provent to the group as whole (including
Kent), then the other methods deserve consideration.  I don't think this
is in any way conflicts with Kent's statement (though I'm sure he'll
correct me if I'm wrong).

Loopback will remain a requirement until someone can prove to the OAM
group that there is a better way.

- Matt


Roy Bynum wrote:
>
> Kent,
>
> I have found that if you do not use strong enough language, the vendors
> that may not have what you require, will attempt to "interpret" your words
> so that they can mean something totally different than what you
> intended.  If I am correct, you may want to resend your comment and use
the
> words "our operations requires that ability".  If you check with your
> equipment "certification" people for edge access infrastructure, you may
> find that loop back functionality at the physical layer is a hard
> requirement, just like it is on T1/T3 infrastructure today.  I know that
it
> was a requirement the large service provider that I was previously with.
>
> Thank you,
> Roy Bynum
>
> At 04:18 PM 2/15/2002 -0800, kmccammon@tri.sbc.com wrote:
>
> >Bob,
> >Loopback functionality is important for SBC, our operations need that
> >ability.
> >-Kent
> >
> >Kent G. McCammon
> >Broadband Access Group
> >SBC Technology Resources, Inc
> >4698 Willow Road
> >Pleasanton, CA 94588
> >925-598-1246
> >kmccammon@tri.sbc.com
> >


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Sun Feb 17 15:47:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11289
	for <hubmib-archive@odin.ietf.org>; Sun, 17 Feb 2002 15:47:13 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27096;
	Sun, 17 Feb 2002 15:40:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27069
	for <hubmib@optimus.ietf.org>; Sun, 17 Feb 2002 15:40:22 -0500 (EST)
Received: from gnat.inet.org (gnat.inet.org [63.108.254.91])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11175
	for <hubmib@ietf.org>; Sun, 17 Feb 2002 15:40:18 -0500 (EST)
Received: from mosquito.inet.org (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 4941D67103; Sun, 17 Feb 2002 15:58:08 -0500 (EST)
Date: Sun, 17 Feb 2002 15:39:43 -0500
Subject: Re: [Hubmib] RE: [EFM] Performance monitoring, installation, trouble shooting .
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v480)
Cc: <hubmib@ietf.org>
To: "Andrew Smith" <ah_smith@acm.org>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <KIEAIFILPFNLNGMKLEMGMEBNDBAA.ah_smith@acm.org>
Message-Id: <795AD1C4-23E6-11D6-9D63-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.480)
Content-Transfer-Encoding: 7bit
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 7bit


On Sunday, February 17, 2002, at 02:37 , Andrew Smith wrote:
> The "Ethernet in the First Mile" group in IEEE 802.3 is looking
> at requirements for management; specific requirements are for
> the minimisation of "truck-rolls" (see message thread below - it
> talks about a PHY-level loopback requirement). Has there been
> any further work on this in any IETF WG?

Andrew,

	A bunch of OIDs in the DOCSIS 1.0 MIBs exist primarily
for the purpose of troubleshooting layer-1 plant
(== minimising truck rolls).  So those MIBs might represent
a useful point of reference for Ethernet in the First Mile
folks.  DOCSIS is not 802.3, but it does provide transmission
for Ethernet/802.3 frames over HFC cabling.

Ran
rja@extremenetworks.com


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Sun Feb 17 15:47:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11299
	for <hubmib-archive@odin.ietf.org>; Sun, 17 Feb 2002 15:47:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA27318
	for hubmib-archive@odin.ietf.org; Sun, 17 Feb 2002 15:47:18 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27096;
	Sun, 17 Feb 2002 15:40:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27069
	for <hubmib@optimus.ietf.org>; Sun, 17 Feb 2002 15:40:22 -0500 (EST)
Received: from gnat.inet.org (gnat.inet.org [63.108.254.91])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11175
	for <hubmib@ietf.org>; Sun, 17 Feb 2002 15:40:18 -0500 (EST)
Received: from mosquito.inet.org (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 4941D67103; Sun, 17 Feb 2002 15:58:08 -0500 (EST)
Date: Sun, 17 Feb 2002 15:39:43 -0500
Subject: Re: [Hubmib] RE: [EFM] Performance monitoring, installation, trouble shooting .
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v480)
Cc: <hubmib@ietf.org>
To: "Andrew Smith" <ah_smith@acm.org>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <KIEAIFILPFNLNGMKLEMGMEBNDBAA.ah_smith@acm.org>
Message-Id: <795AD1C4-23E6-11D6-9D63-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.480)
Content-Transfer-Encoding: 7bit
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 7bit


On Sunday, February 17, 2002, at 02:37 , Andrew Smith wrote:
> The "Ethernet in the First Mile" group in IEEE 802.3 is looking
> at requirements for management; specific requirements are for
> the minimisation of "truck-rolls" (see message thread below - it
> talks about a PHY-level loopback requirement). Has there been
> any further work on this in any IETF WG?

Andrew,

	A bunch of OIDs in the DOCSIS 1.0 MIBs exist primarily
for the purpose of troubleshooting layer-1 plant
(== minimising truck rolls).  So those MIBs might represent
a useful point of reference for Ethernet in the First Mile
folks.  DOCSIS is not 802.3, but it does provide transmission
for Ethernet/802.3 frames over HFC cabling.

Ran
rja@extremenetworks.com


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Mon Feb 18 01:59:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19728
	for <hubmib-archive@odin.ietf.org>; Mon, 18 Feb 2002 01:59:28 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA01662;
	Mon, 18 Feb 2002 01:52:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA01598
	for <hubmib@optimus.ietf.org>; Mon, 18 Feb 2002 01:52:38 -0500 (EST)
Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19650;
	Mon, 18 Feb 2002 01:52:34 -0500 (EST)
Received: from iere.net.avaya.com (localhost [127.0.0.1])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g1I6pD728059;
	Mon, 18 Feb 2002 01:51:13 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g1I6pCc28053;
	Mon, 18 Feb 2002 01:51:13 -0500 (EST)
content-class: urn:content-classes:message
Subject: RE: [Hubmib] RE: [EFM] Performance monitoring, installation, trouble shooting .
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Mon, 18 Feb 2002 08:51:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F60D0C6@IS0004AVEXU1.global.avaya.com>
Thread-Topic: [Hubmib] RE: [EFM] Performance monitoring, installation, trouble shooting .
Thread-Index: AcG35qJhjiltHJLDR7WreEhGsvti+AAXv3oQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Andrew Smith" <ah_smith@acm.org>, <hubmib@ietf.org>, <ifmib@ietf.org>
Cc: <mattsquire@acm.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id BAA01599
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 8bit

The statement in RFC 2665 refers at the work that was being done at that
time (around 1998-99) in the Interfaces MIB (ifmib) WG. The assessment
of the editors of the Ethernet-like interfaces MIB was that if a more
generic interface test MIB will be defined, there is no need for an
Ethernet-specific interface test table.

The ifTest table is deprecated in the latest version of the Interfaces
MIB successor - RFC 2663. The editor of the Ethernet-like MIB should
correct the text referred by Andy in the new revision of the MIB
occasioned by the 10GBE support.

AFAIK, there is no replacement for ifTest. Actually the definition of
ifTest was generic enough for 'strange un-SNMP-like things'. I do not
remember all discussions that led to the deprecation of ifTest table,
but the lack of implementation reports might have been part of this.

I do think that there is a need for such a function. Still, I prefer it
to be generic, and not Ethernet-specific. If there is a broader
interest, ifmib is IMO the place to (re)-do it.

Regards,

Dan
 

> -----Original Message-----
> From: Andrew Smith [mailto:ah_smith@acm.org]
> Sent: Sunday, February 17, 2002 9:38 PM
> To: hubmib@ietf.org
> Cc: mattsquire@acm.org
> Subject: [Hubmib] RE: [EFM] Performance monitoring, 
> installation, trouble shooting .
> 
> 
> Forgive my ignorance on the history of the following 
> statement in RFC2665:
> 
> "Note that the ifTestTable is now deprecated.  Work is underway to
>    define a replacement MIB for system and interface testing.  It is
>    expected that the tests defined in this document will be usable in
>    this replacement MIB."
> 
> The "Ethernet in the First Mile" group in IEEE 802.3 is looking at
> requirements for management; specific requirements are for 
> the minimisation
> of "truck-rolls" (see message thread below - it talks about a 
> PHY-level
> loopback requirement). Has there been any further work on 
> this in any IETF
> WG? Was the ifTest stuff thrown out because it might do 
> strange un-SNMP-like
> things like cut off connectivity for some (arbitrary? 
> predetermined?) period
> of time?
> 
> Could someone fill me in on the history here?
> 
> Thanks,
> 
> Andrew Smith
> 
> 
> 
> -----Original Message-----
> From: owner-stds-802-3-efm@majordomo.ieee.org
> [mailto:owner-stds-802-3-efm@majordomo.ieee.org]On Behalf Of 
> Matt Squire
> Sent: Sunday, February 17, 2002 8:43 AM
> To: Roy Bynum
> Cc: kmccammon@tri.sbc.com; stds-802-3-efm@ieee.org
> Subject: Re: [EFM] Performance monitoring, installation, trouble
> shooting .
> 
> 
> 
> 
> I'll repeat the current status of loopback within OAM.
> - A ping connectivity test is a requirement.
> - A loopback mode is a requirement.
> - Controlling the state of the loopback mode at the other end 
> of a link
> is a requirement.
> 
> There is also a group of people that believe that the functionality of
> loopback can be achieved without a loopback mode, but 
> enhancing the MIBS
> and the PHY functionality.  They are actively investigating the
> possibility.  When and if they think they can show equivalent
> functionality, the results will be presented to the 
> reflector.  At that
> point everyone can judge whether the alternate method provides
> equivalent function.
> 
> Loopback itself is a function.  The function is used to 
> fulfill certain
> operational requirements.  If those requirements can be met with other
> methods, and this point can be provent to the group as whole 
> (including
> Kent), then the other methods deserve consideration.  I don't 
> think this
> is in any way conflicts with Kent's statement (though I'm sure he'll
> correct me if I'm wrong).
> 
> Loopback will remain a requirement until someone can prove to the OAM
> group that there is a better way.
> 
> - Matt
> 
> 
> Roy Bynum wrote:
> >
> > Kent,
> >
> > I have found that if you do not use strong enough language, 
> the vendors
> > that may not have what you require, will attempt to 
> "interpret" your words
> > so that they can mean something totally different than what you
> > intended.  If I am correct, you may want to resend your 
> comment and use
> the
> > words "our operations requires that ability".  If you check 
> with your
> > equipment "certification" people for edge access 
> infrastructure, you may
> > find that loop back functionality at the physical layer is a hard
> > requirement, just like it is on T1/T3 infrastructure today. 
>  I know that
> it
> > was a requirement the large service provider that I was 
> previously with.
> >
> > Thank you,
> > Roy Bynum
> >
> > At 04:18 PM 2/15/2002 -0800, kmccammon@tri.sbc.com wrote:
> >
> > >Bob,
> > >Loopback functionality is important for SBC, our 
> operations need that
> > >ability.
> > >-Kent
> > >
> > >Kent G. McCammon
> > >Broadband Access Group
> > >SBC Technology Resources, Inc
> > >4698 Willow Road
> > >Pleasanton, CA 94588
> > >925-598-1246
> > >kmccammon@tri.sbc.com
> > >
> 
> 
> _______________________________________________
> Hubmib mailing list
> Hubmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/hubmib
> 

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Mon Feb 18 01:59:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19738
	for <hubmib-archive@odin.ietf.org>; Mon, 18 Feb 2002 01:59:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA02032
	for hubmib-archive@odin.ietf.org; Mon, 18 Feb 2002 01:59:31 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA01662;
	Mon, 18 Feb 2002 01:52:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA01598
	for <hubmib@optimus.ietf.org>; Mon, 18 Feb 2002 01:52:38 -0500 (EST)
Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19650;
	Mon, 18 Feb 2002 01:52:34 -0500 (EST)
Received: from iere.net.avaya.com (localhost [127.0.0.1])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g1I6pD728059;
	Mon, 18 Feb 2002 01:51:13 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g1I6pCc28053;
	Mon, 18 Feb 2002 01:51:13 -0500 (EST)
content-class: urn:content-classes:message
Subject: RE: [Hubmib] RE: [EFM] Performance monitoring, installation, trouble shooting .
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Mon, 18 Feb 2002 08:51:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F60D0C6@IS0004AVEXU1.global.avaya.com>
Thread-Topic: [Hubmib] RE: [EFM] Performance monitoring, installation, trouble shooting .
Thread-Index: AcG35qJhjiltHJLDR7WreEhGsvti+AAXv3oQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Andrew Smith" <ah_smith@acm.org>, <hubmib@ietf.org>, <ifmib@ietf.org>
Cc: <mattsquire@acm.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id BAA01599
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 8bit

The statement in RFC 2665 refers at the work that was being done at that
time (around 1998-99) in the Interfaces MIB (ifmib) WG. The assessment
of the editors of the Ethernet-like interfaces MIB was that if a more
generic interface test MIB will be defined, there is no need for an
Ethernet-specific interface test table.

The ifTest table is deprecated in the latest version of the Interfaces
MIB successor - RFC 2663. The editor of the Ethernet-like MIB should
correct the text referred by Andy in the new revision of the MIB
occasioned by the 10GBE support.

AFAIK, there is no replacement for ifTest. Actually the definition of
ifTest was generic enough for 'strange un-SNMP-like things'. I do not
remember all discussions that led to the deprecation of ifTest table,
but the lack of implementation reports might have been part of this.

I do think that there is a need for such a function. Still, I prefer it
to be generic, and not Ethernet-specific. If there is a broader
interest, ifmib is IMO the place to (re)-do it.

Regards,

Dan
 

> -----Original Message-----
> From: Andrew Smith [mailto:ah_smith@acm.org]
> Sent: Sunday, February 17, 2002 9:38 PM
> To: hubmib@ietf.org
> Cc: mattsquire@acm.org
> Subject: [Hubmib] RE: [EFM] Performance monitoring, 
> installation, trouble shooting .
> 
> 
> Forgive my ignorance on the history of the following 
> statement in RFC2665:
> 
> "Note that the ifTestTable is now deprecated.  Work is underway to
>    define a replacement MIB for system and interface testing.  It is
>    expected that the tests defined in this document will be usable in
>    this replacement MIB."
> 
> The "Ethernet in the First Mile" group in IEEE 802.3 is looking at
> requirements for management; specific requirements are for 
> the minimisation
> of "truck-rolls" (see message thread below - it talks about a 
> PHY-level
> loopback requirement). Has there been any further work on 
> this in any IETF
> WG? Was the ifTest stuff thrown out because it might do 
> strange un-SNMP-like
> things like cut off connectivity for some (arbitrary? 
> predetermined?) period
> of time?
> 
> Could someone fill me in on the history here?
> 
> Thanks,
> 
> Andrew Smith
> 
> 
> 
> -----Original Message-----
> From: owner-stds-802-3-efm@majordomo.ieee.org
> [mailto:owner-stds-802-3-efm@majordomo.ieee.org]On Behalf Of 
> Matt Squire
> Sent: Sunday, February 17, 2002 8:43 AM
> To: Roy Bynum
> Cc: kmccammon@tri.sbc.com; stds-802-3-efm@ieee.org
> Subject: Re: [EFM] Performance monitoring, installation, trouble
> shooting .
> 
> 
> 
> 
> I'll repeat the current status of loopback within OAM.
> - A ping connectivity test is a requirement.
> - A loopback mode is a requirement.
> - Controlling the state of the loopback mode at the other end 
> of a link
> is a requirement.
> 
> There is also a group of people that believe that the functionality of
> loopback can be achieved without a loopback mode, but 
> enhancing the MIBS
> and the PHY functionality.  They are actively investigating the
> possibility.  When and if they think they can show equivalent
> functionality, the results will be presented to the 
> reflector.  At that
> point everyone can judge whether the alternate method provides
> equivalent function.
> 
> Loopback itself is a function.  The function is used to 
> fulfill certain
> operational requirements.  If those requirements can be met with other
> methods, and this point can be provent to the group as whole 
> (including
> Kent), then the other methods deserve consideration.  I don't 
> think this
> is in any way conflicts with Kent's statement (though I'm sure he'll
> correct me if I'm wrong).
> 
> Loopback will remain a requirement until someone can prove to the OAM
> group that there is a better way.
> 
> - Matt
> 
> 
> Roy Bynum wrote:
> >
> > Kent,
> >
> > I have found that if you do not use strong enough language, 
> the vendors
> > that may not have what you require, will attempt to 
> "interpret" your words
> > so that they can mean something totally different than what you
> > intended.  If I am correct, you may want to resend your 
> comment and use
> the
> > words "our operations requires that ability".  If you check 
> with your
> > equipment "certification" people for edge access 
> infrastructure, you may
> > find that loop back functionality at the physical layer is a hard
> > requirement, just like it is on T1/T3 infrastructure today. 
>  I know that
> it
> > was a requirement the large service provider that I was 
> previously with.
> >
> > Thank you,
> > Roy Bynum
> >
> > At 04:18 PM 2/15/2002 -0800, kmccammon@tri.sbc.com wrote:
> >
> > >Bob,
> > >Loopback functionality is important for SBC, our 
> operations need that
> > >ability.
> > >-Kent
> > >
> > >Kent G. McCammon
> > >Broadband Access Group
> > >SBC Technology Resources, Inc
> > >4698 Willow Road
> > >Pleasanton, CA 94588
> > >925-598-1246
> > >kmccammon@tri.sbc.com
> > >
> 
> 
> _______________________________________________
> Hubmib mailing list
> Hubmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/hubmib
> 

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Mon Feb 18 08:01:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01599
	for <hubmib-archive@odin.ietf.org>; Mon, 18 Feb 2002 08:01:31 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18013;
	Mon, 18 Feb 2002 07:54:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17949
	for <hubmib@optimus.ietf.org>; Mon, 18 Feb 2002 07:54:51 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01363;
	Mon, 18 Feb 2002 07:54:46 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g1ICsIv00721;
	Mon, 18 Feb 2002 07:54:18 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21)
	id <1Z89LVW4>; Mon, 18 Feb 2002 13:54:17 +0100
Message-ID: <114DE1AABD7DD41189B600508BAF1271054888F1@nl0006exch005u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>,
        Andrew Smith
	 <ah_smith@acm.org>, hubmib@ietf.org, ifmib@ietf.org
Cc: mattsquire@acm.org
Subject: RE: [Hubmib] RE: [EFM] Performance monitoring, installation, trou
	ble shooting .
Date: Mon, 18 Feb 2002 13:54:14 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

> The ifTest table is deprecated in the latest version of the Interfaces
> MIB successor - RFC 2663. The editor of the Ethernet-like MIB should
> correct the text referred by Andy in the new revision of the MIB
> occasioned by the 10GBE support.
> 
> AFAIK, there is no replacement for ifTest. Actually the definition of
> ifTest was generic enough for 'strange un-SNMP-like things'. I do not
> remember all discussions that led to the deprecation of ifTest table,
> but the lack of implementation reports might have been part of this.
> 
> I do think that there is a need for such a function. Still, I prefer it
> to be generic, and not Ethernet-specific. If there is a broader
> interest, ifmib is IMO the place to (re)-do it.
> 
The ifTestTable was already deprecated in RFC2233. So this goes back to
1997. I believe there was some talk (back then) that such a generic
test MIB would be useful, but that it better be defined outside
of the IF-MIB. I have not seen any work on that since then.

Bert
> Regards,
> 
> Dan
>  
> 
> > -----Original Message-----
> > From: Andrew Smith [mailto:ah_smith@acm.org]
> > Sent: Sunday, February 17, 2002 9:38 PM
> > To: hubmib@ietf.org
> > Cc: mattsquire@acm.org
> > Subject: [Hubmib] RE: [EFM] Performance monitoring, 
> > installation, trouble shooting .
> > 
> > 
> > Forgive my ignorance on the history of the following 
> > statement in RFC2665:
> > 
> > "Note that the ifTestTable is now deprecated.  Work is underway to
> >    define a replacement MIB for system and interface testing.  It is
> >    expected that the tests defined in this document will be 
> usable in
> >    this replacement MIB."
> > 
> > The "Ethernet in the First Mile" group in IEEE 802.3 is looking at
> > requirements for management; specific requirements are for 
> > the minimisation
> > of "truck-rolls" (see message thread below - it talks about a 
> > PHY-level
> > loopback requirement). Has there been any further work on 
> > this in any IETF
> > WG? Was the ifTest stuff thrown out because it might do 
> > strange un-SNMP-like
> > things like cut off connectivity for some (arbitrary? 
> > predetermined?) period
> > of time?
> > 
> > Could someone fill me in on the history here?
> > 
> > Thanks,
> > 
> > Andrew Smith
> > 
> > 
> > 
> > -----Original Message-----
> > From: owner-stds-802-3-efm@majordomo.ieee.org
> > [mailto:owner-stds-802-3-efm@majordomo.ieee.org]On Behalf Of 
> > Matt Squire
> > Sent: Sunday, February 17, 2002 8:43 AM
> > To: Roy Bynum
> > Cc: kmccammon@tri.sbc.com; stds-802-3-efm@ieee.org
> > Subject: Re: [EFM] Performance monitoring, installation, trouble
> > shooting .
> > 
> > 
> > 
> > 
> > I'll repeat the current status of loopback within OAM.
> > - A ping connectivity test is a requirement.
> > - A loopback mode is a requirement.
> > - Controlling the state of the loopback mode at the other end 
> > of a link
> > is a requirement.
> > 
> > There is also a group of people that believe that the 
> functionality of
> > loopback can be achieved without a loopback mode, but 
> > enhancing the MIBS
> > and the PHY functionality.  They are actively investigating the
> > possibility.  When and if they think they can show equivalent
> > functionality, the results will be presented to the 
> > reflector.  At that
> > point everyone can judge whether the alternate method provides
> > equivalent function.
> > 
> > Loopback itself is a function.  The function is used to 
> > fulfill certain
> > operational requirements.  If those requirements can be met 
> with other
> > methods, and this point can be provent to the group as whole 
> > (including
> > Kent), then the other methods deserve consideration.  I don't 
> > think this
> > is in any way conflicts with Kent's statement (though I'm sure he'll
> > correct me if I'm wrong).
> > 
> > Loopback will remain a requirement until someone can prove 
> to the OAM
> > group that there is a better way.
> > 
> > - Matt
> > 
> > 
> > Roy Bynum wrote:
> > >
> > > Kent,
> > >
> > > I have found that if you do not use strong enough language, 
> > the vendors
> > > that may not have what you require, will attempt to 
> > "interpret" your words
> > > so that they can mean something totally different than what you
> > > intended.  If I am correct, you may want to resend your 
> > comment and use
> > the
> > > words "our operations requires that ability".  If you check 
> > with your
> > > equipment "certification" people for edge access 
> > infrastructure, you may
> > > find that loop back functionality at the physical layer is a hard
> > > requirement, just like it is on T1/T3 infrastructure today. 
> >  I know that
> > it
> > > was a requirement the large service provider that I was 
> > previously with.
> > >
> > > Thank you,
> > > Roy Bynum
> > >
> > > At 04:18 PM 2/15/2002 -0800, kmccammon@tri.sbc.com wrote:
> > >
> > > >Bob,
> > > >Loopback functionality is important for SBC, our 
> > operations need that
> > > >ability.
> > > >-Kent
> > > >
> > > >Kent G. McCammon
> > > >Broadband Access Group
> > > >SBC Technology Resources, Inc
> > > >4698 Willow Road
> > > >Pleasanton, CA 94588
> > > >925-598-1246
> > > >kmccammon@tri.sbc.com
> > > >
> > 
> > 
> > _______________________________________________
> > Hubmib mailing list
> > Hubmib@ietf.org
> > https://www1.ietf.org/mailman/listinfo/hubmib
> > 
> 
> _______________________________________________
> Hubmib mailing list
> Hubmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/hubmib
> 

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Mon Feb 18 08:01:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01611
	for <hubmib-archive@odin.ietf.org>; Mon, 18 Feb 2002 08:01:31 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA18725
	for hubmib-archive@odin.ietf.org; Mon, 18 Feb 2002 08:01:35 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18013;
	Mon, 18 Feb 2002 07:54:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17949
	for <hubmib@optimus.ietf.org>; Mon, 18 Feb 2002 07:54:51 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01363;
	Mon, 18 Feb 2002 07:54:46 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g1ICsIv00721;
	Mon, 18 Feb 2002 07:54:18 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21)
	id <1Z89LVW4>; Mon, 18 Feb 2002 13:54:17 +0100
Message-ID: <114DE1AABD7DD41189B600508BAF1271054888F1@nl0006exch005u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>,
        Andrew Smith
	 <ah_smith@acm.org>, hubmib@ietf.org, ifmib@ietf.org
Cc: mattsquire@acm.org
Subject: RE: [Hubmib] RE: [EFM] Performance monitoring, installation, trou
	ble shooting .
Date: Mon, 18 Feb 2002 13:54:14 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

> The ifTest table is deprecated in the latest version of the Interfaces
> MIB successor - RFC 2663. The editor of the Ethernet-like MIB should
> correct the text referred by Andy in the new revision of the MIB
> occasioned by the 10GBE support.
> 
> AFAIK, there is no replacement for ifTest. Actually the definition of
> ifTest was generic enough for 'strange un-SNMP-like things'. I do not
> remember all discussions that led to the deprecation of ifTest table,
> but the lack of implementation reports might have been part of this.
> 
> I do think that there is a need for such a function. Still, I prefer it
> to be generic, and not Ethernet-specific. If there is a broader
> interest, ifmib is IMO the place to (re)-do it.
> 
The ifTestTable was already deprecated in RFC2233. So this goes back to
1997. I believe there was some talk (back then) that such a generic
test MIB would be useful, but that it better be defined outside
of the IF-MIB. I have not seen any work on that since then.

Bert
> Regards,
> 
> Dan
>  
> 
> > -----Original Message-----
> > From: Andrew Smith [mailto:ah_smith@acm.org]
> > Sent: Sunday, February 17, 2002 9:38 PM
> > To: hubmib@ietf.org
> > Cc: mattsquire@acm.org
> > Subject: [Hubmib] RE: [EFM] Performance monitoring, 
> > installation, trouble shooting .
> > 
> > 
> > Forgive my ignorance on the history of the following 
> > statement in RFC2665:
> > 
> > "Note that the ifTestTable is now deprecated.  Work is underway to
> >    define a replacement MIB for system and interface testing.  It is
> >    expected that the tests defined in this document will be 
> usable in
> >    this replacement MIB."
> > 
> > The "Ethernet in the First Mile" group in IEEE 802.3 is looking at
> > requirements for management; specific requirements are for 
> > the minimisation
> > of "truck-rolls" (see message thread below - it talks about a 
> > PHY-level
> > loopback requirement). Has there been any further work on 
> > this in any IETF
> > WG? Was the ifTest stuff thrown out because it might do 
> > strange un-SNMP-like
> > things like cut off connectivity for some (arbitrary? 
> > predetermined?) period
> > of time?
> > 
> > Could someone fill me in on the history here?
> > 
> > Thanks,
> > 
> > Andrew Smith
> > 
> > 
> > 
> > -----Original Message-----
> > From: owner-stds-802-3-efm@majordomo.ieee.org
> > [mailto:owner-stds-802-3-efm@majordomo.ieee.org]On Behalf Of 
> > Matt Squire
> > Sent: Sunday, February 17, 2002 8:43 AM
> > To: Roy Bynum
> > Cc: kmccammon@tri.sbc.com; stds-802-3-efm@ieee.org
> > Subject: Re: [EFM] Performance monitoring, installation, trouble
> > shooting .
> > 
> > 
> > 
> > 
> > I'll repeat the current status of loopback within OAM.
> > - A ping connectivity test is a requirement.
> > - A loopback mode is a requirement.
> > - Controlling the state of the loopback mode at the other end 
> > of a link
> > is a requirement.
> > 
> > There is also a group of people that believe that the 
> functionality of
> > loopback can be achieved without a loopback mode, but 
> > enhancing the MIBS
> > and the PHY functionality.  They are actively investigating the
> > possibility.  When and if they think they can show equivalent
> > functionality, the results will be presented to the 
> > reflector.  At that
> > point everyone can judge whether the alternate method provides
> > equivalent function.
> > 
> > Loopback itself is a function.  The function is used to 
> > fulfill certain
> > operational requirements.  If those requirements can be met 
> with other
> > methods, and this point can be provent to the group as whole 
> > (including
> > Kent), then the other methods deserve consideration.  I don't 
> > think this
> > is in any way conflicts with Kent's statement (though I'm sure he'll
> > correct me if I'm wrong).
> > 
> > Loopback will remain a requirement until someone can prove 
> to the OAM
> > group that there is a better way.
> > 
> > - Matt
> > 
> > 
> > Roy Bynum wrote:
> > >
> > > Kent,
> > >
> > > I have found that if you do not use strong enough language, 
> > the vendors
> > > that may not have what you require, will attempt to 
> > "interpret" your words
> > > so that they can mean something totally different than what you
> > > intended.  If I am correct, you may want to resend your 
> > comment and use
> > the
> > > words "our operations requires that ability".  If you check 
> > with your
> > > equipment "certification" people for edge access 
> > infrastructure, you may
> > > find that loop back functionality at the physical layer is a hard
> > > requirement, just like it is on T1/T3 infrastructure today. 
> >  I know that
> > it
> > > was a requirement the large service provider that I was 
> > previously with.
> > >
> > > Thank you,
> > > Roy Bynum
> > >
> > > At 04:18 PM 2/15/2002 -0800, kmccammon@tri.sbc.com wrote:
> > >
> > > >Bob,
> > > >Loopback functionality is important for SBC, our 
> > operations need that
> > > >ability.
> > > >-Kent
> > > >
> > > >Kent G. McCammon
> > > >Broadband Access Group
> > > >SBC Technology Resources, Inc
> > > >4698 Willow Road
> > > >Pleasanton, CA 94588
> > > >925-598-1246
> > > >kmccammon@tri.sbc.com
> > > >
> > 
> > 
> > _______________________________________________
> > Hubmib mailing list
> > Hubmib@ietf.org
> > https://www1.ietf.org/mailman/listinfo/hubmib
> > 
> 
> _______________________________________________
> Hubmib mailing list
> Hubmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/hubmib
> 

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Tue Feb 19 10:01:40 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22268
	for <hubmib-archive@odin.ietf.org>; Tue, 19 Feb 2002 10:01:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA09985;
	Tue, 19 Feb 2002 09:54:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA09942
	for <hubmib@optimus.ietf.org>; Tue, 19 Feb 2002 09:54:04 -0500 (EST)
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21790;
	Tue, 19 Feb 2002 09:54:00 -0500 (EST)
Received: from shannon.research.telcordia.com (shannon [128.96.73.2])
	by thumper.research.telcordia.com (8.12.1/8.12.1) with ESMTP id g1JEpjjP010089;
	Tue, 19 Feb 2002 09:51:45 -0500 (EST)
Received: from kaj-100.research.telcordia.com (nv-ktesink.cc.telcordia.com [128.96.82.9])
	by shannon.research.telcordia.com (8.8.8/8.8.8) with ESMTP id JAA12368;
	Tue, 19 Feb 2002 09:51:44 -0500 (EST)
Message-Id: <4.3.2.7.0.20020219093756.02021820@shannon.research.telcordia.com>
X-Sender: kaj@shannon.research.telcordia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 19 Feb 2002 09:41:34 -0500
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Romascanu, Dan (Dan)" <dromasca@avaya.com>,
        Andrew Smith <ah_smith@acm.org>, hubmib@ietf.org, ifmib@ietf.org
From: Kaj Tesink <kaj@research.telcordia.com>
Subject: Re: [ifmib] RE: [Hubmib] RE: [EFM] Performance monitoring,
  installation, trou ble shooting .
Cc: mattsquire@acm.org
In-Reply-To: <114DE1AABD7DD41189B600508BAF1271054888F1@nl0006exch005u.nl
 .lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Virus-Scanned: by AMaViS-perl11-milter
 (http://amavis.org/)
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

At 01:54 PM 2/18/2002 +0100, Wijnen, Bert (Bert) wrote:
> > The ifTest table is deprecated in the latest version of the Interfaces
> > MIB successor - RFC 2663. The editor of the Ethernet-like MIB should
> > correct the text referred by Andy in the new revision of the MIB
> > occasioned by the 10GBE support.
> >
> > AFAIK, there is no replacement for ifTest. Actually the definition of
> > ifTest was generic enough for 'strange un-SNMP-like things'. I do not
> > remember all discussions that led to the deprecation of ifTest table,
> > but the lack of implementation reports might have been part of this.
> >
> > I do think that there is a need for such a function. Still, I prefer it
> > to be generic, and not Ethernet-specific. If there is a broader
> > interest, ifmib is IMO the place to (re)-do it.
> >
>The ifTestTable was already deprecated in RFC2233. So this goes back to
>1997. I believe there was some talk (back then) that such a generic
>test MIB would be useful, but that it better be defined outside
>of the IF-MIB. I have not seen any work on that since then.


there has been work on that; most recent draft was late 1999 with
reasonable consensus level - work was abandoned because of lack of
time by the authors. i have the draft.

kaj



>Bert
> > Regards,
> >
> > Dan
> >
> >
> > > -----Original Message-----
> > > From: Andrew Smith [mailto:ah_smith@acm.org]
> > > Sent: Sunday, February 17, 2002 9:38 PM
> > > To: hubmib@ietf.org
> > > Cc: mattsquire@acm.org
> > > Subject: [Hubmib] RE: [EFM] Performance monitoring,
> > > installation, trouble shooting .
> > >
> > >
> > > Forgive my ignorance on the history of the following
> > > statement in RFC2665:
> > >
> > > "Note that the ifTestTable is now deprecated.  Work is underway to
> > >    define a replacement MIB for system and interface testing.  It is
> > >    expected that the tests defined in this document will be
> > usable in
> > >    this replacement MIB."
> > >
> > > The "Ethernet in the First Mile" group in IEEE 802.3 is looking at
> > > requirements for management; specific requirements are for
> > > the minimisation
> > > of "truck-rolls" (see message thread below - it talks about a
> > > PHY-level
> > > loopback requirement). Has there been any further work on
> > > this in any IETF
> > > WG? Was the ifTest stuff thrown out because it might do
> > > strange un-SNMP-like
> > > things like cut off connectivity for some (arbitrary?
> > > predetermined?) period
> > > of time?
> > >
> > > Could someone fill me in on the history here?
> > >
> > > Thanks,
> > >
> > > Andrew Smith
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: owner-stds-802-3-efm@majordomo.ieee.org
> > > [mailto:owner-stds-802-3-efm@majordomo.ieee.org]On Behalf Of
> > > Matt Squire
> > > Sent: Sunday, February 17, 2002 8:43 AM
> > > To: Roy Bynum
> > > Cc: kmccammon@tri.sbc.com; stds-802-3-efm@ieee.org
> > > Subject: Re: [EFM] Performance monitoring, installation, trouble
> > > shooting .
> > >
> > >
> > >
> > >
> > > I'll repeat the current status of loopback within OAM.
> > > - A ping connectivity test is a requirement.
> > > - A loopback mode is a requirement.
> > > - Controlling the state of the loopback mode at the other end
> > > of a link
> > > is a requirement.
> > >
> > > There is also a group of people that believe that the
> > functionality of
> > > loopback can be achieved without a loopback mode, but
> > > enhancing the MIBS
> > > and the PHY functionality.  They are actively investigating the
> > > possibility.  When and if they think they can show equivalent
> > > functionality, the results will be presented to the
> > > reflector.  At that
> > > point everyone can judge whether the alternate method provides
> > > equivalent function.
> > >
> > > Loopback itself is a function.  The function is used to
> > > fulfill certain
> > > operational requirements.  If those requirements can be met
> > with other
> > > methods, and this point can be provent to the group as whole
> > > (including
> > > Kent), then the other methods deserve consideration.  I don't
> > > think this
> > > is in any way conflicts with Kent's statement (though I'm sure he'll
> > > correct me if I'm wrong).
> > >
> > > Loopback will remain a requirement until someone can prove
> > to the OAM
> > > group that there is a better way.
> > >
> > > - Matt
> > >
> > >
> > > Roy Bynum wrote:
> > > >
> > > > Kent,
> > > >
> > > > I have found that if you do not use strong enough language,
> > > the vendors
> > > > that may not have what you require, will attempt to
> > > "interpret" your words
> > > > so that they can mean something totally different than what you
> > > > intended.  If I am correct, you may want to resend your
> > > comment and use
> > > the
> > > > words "our operations requires that ability".  If you check
> > > with your
> > > > equipment "certification" people for edge access
> > > infrastructure, you may
> > > > find that loop back functionality at the physical layer is a hard
> > > > requirement, just like it is on T1/T3 infrastructure today.
> > >  I know that
> > > it
> > > > was a requirement the large service provider that I was
> > > previously with.
> > > >
> > > > Thank you,
> > > > Roy Bynum
> > > >
> > > > At 04:18 PM 2/15/2002 -0800, kmccammon@tri.sbc.com wrote:
> > > >
> > > > >Bob,
> > > > >Loopback functionality is important for SBC, our
> > > operations need that
> > > > >ability.
> > > > >-Kent
> > > > >
> > > > >Kent G. McCammon
> > > > >Broadband Access Group
> > > > >SBC Technology Resources, Inc
> > > > >4698 Willow Road
> > > > >Pleasanton, CA 94588
> > > > >925-598-1246
> > > > >kmccammon@tri.sbc.com
> > > > >
> > >
> > >
> > > _______________________________________________
> > > Hubmib mailing list
> > > Hubmib@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/hubmib
> > >
> >
> > _______________________________________________
> > Hubmib mailing list
> > Hubmib@ietf.org
> > https://www1.ietf.org/mailman/listinfo/hubmib
> >
>
>_______________________________________________
>ifmib mailing list
>ifmib@ietf.org
>https://www1.ietf.org/mailman/listinfo/ifmib


_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

Kaj Tesink
Telcordia Technologies. In.
331 Newman Springs Road
Red Bank, NJ 07701
Email: kaj @research.telcordia.com
Tel: (732) 758-5254
Fax: (732) 758-4177

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Tue Feb 19 10:01:41 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22278
	for <hubmib-archive@odin.ietf.org>; Tue, 19 Feb 2002 10:01:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA11069
	for hubmib-archive@odin.ietf.org; Tue, 19 Feb 2002 10:01:43 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA09985;
	Tue, 19 Feb 2002 09:54:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA09942
	for <hubmib@optimus.ietf.org>; Tue, 19 Feb 2002 09:54:04 -0500 (EST)
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21790;
	Tue, 19 Feb 2002 09:54:00 -0500 (EST)
Received: from shannon.research.telcordia.com (shannon [128.96.73.2])
	by thumper.research.telcordia.com (8.12.1/8.12.1) with ESMTP id g1JEpjjP010089;
	Tue, 19 Feb 2002 09:51:45 -0500 (EST)
Received: from kaj-100.research.telcordia.com (nv-ktesink.cc.telcordia.com [128.96.82.9])
	by shannon.research.telcordia.com (8.8.8/8.8.8) with ESMTP id JAA12368;
	Tue, 19 Feb 2002 09:51:44 -0500 (EST)
Message-Id: <4.3.2.7.0.20020219093756.02021820@shannon.research.telcordia.com>
X-Sender: kaj@shannon.research.telcordia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 19 Feb 2002 09:41:34 -0500
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Romascanu, Dan (Dan)" <dromasca@avaya.com>,
        Andrew Smith <ah_smith@acm.org>, hubmib@ietf.org, ifmib@ietf.org
From: Kaj Tesink <kaj@research.telcordia.com>
Subject: Re: [ifmib] RE: [Hubmib] RE: [EFM] Performance monitoring,
  installation, trou ble shooting .
Cc: mattsquire@acm.org
In-Reply-To: <114DE1AABD7DD41189B600508BAF1271054888F1@nl0006exch005u.nl
 .lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Virus-Scanned: by AMaViS-perl11-milter
 (http://amavis.org/)
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

At 01:54 PM 2/18/2002 +0100, Wijnen, Bert (Bert) wrote:
> > The ifTest table is deprecated in the latest version of the Interfaces
> > MIB successor - RFC 2663. The editor of the Ethernet-like MIB should
> > correct the text referred by Andy in the new revision of the MIB
> > occasioned by the 10GBE support.
> >
> > AFAIK, there is no replacement for ifTest. Actually the definition of
> > ifTest was generic enough for 'strange un-SNMP-like things'. I do not
> > remember all discussions that led to the deprecation of ifTest table,
> > but the lack of implementation reports might have been part of this.
> >
> > I do think that there is a need for such a function. Still, I prefer it
> > to be generic, and not Ethernet-specific. If there is a broader
> > interest, ifmib is IMO the place to (re)-do it.
> >
>The ifTestTable was already deprecated in RFC2233. So this goes back to
>1997. I believe there was some talk (back then) that such a generic
>test MIB would be useful, but that it better be defined outside
>of the IF-MIB. I have not seen any work on that since then.


there has been work on that; most recent draft was late 1999 with
reasonable consensus level - work was abandoned because of lack of
time by the authors. i have the draft.

kaj



>Bert
> > Regards,
> >
> > Dan
> >
> >
> > > -----Original Message-----
> > > From: Andrew Smith [mailto:ah_smith@acm.org]
> > > Sent: Sunday, February 17, 2002 9:38 PM
> > > To: hubmib@ietf.org
> > > Cc: mattsquire@acm.org
> > > Subject: [Hubmib] RE: [EFM] Performance monitoring,
> > > installation, trouble shooting .
> > >
> > >
> > > Forgive my ignorance on the history of the following
> > > statement in RFC2665:
> > >
> > > "Note that the ifTestTable is now deprecated.  Work is underway to
> > >    define a replacement MIB for system and interface testing.  It is
> > >    expected that the tests defined in this document will be
> > usable in
> > >    this replacement MIB."
> > >
> > > The "Ethernet in the First Mile" group in IEEE 802.3 is looking at
> > > requirements for management; specific requirements are for
> > > the minimisation
> > > of "truck-rolls" (see message thread below - it talks about a
> > > PHY-level
> > > loopback requirement). Has there been any further work on
> > > this in any IETF
> > > WG? Was the ifTest stuff thrown out because it might do
> > > strange un-SNMP-like
> > > things like cut off connectivity for some (arbitrary?
> > > predetermined?) period
> > > of time?
> > >
> > > Could someone fill me in on the history here?
> > >
> > > Thanks,
> > >
> > > Andrew Smith
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: owner-stds-802-3-efm@majordomo.ieee.org
> > > [mailto:owner-stds-802-3-efm@majordomo.ieee.org]On Behalf Of
> > > Matt Squire
> > > Sent: Sunday, February 17, 2002 8:43 AM
> > > To: Roy Bynum
> > > Cc: kmccammon@tri.sbc.com; stds-802-3-efm@ieee.org
> > > Subject: Re: [EFM] Performance monitoring, installation, trouble
> > > shooting .
> > >
> > >
> > >
> > >
> > > I'll repeat the current status of loopback within OAM.
> > > - A ping connectivity test is a requirement.
> > > - A loopback mode is a requirement.
> > > - Controlling the state of the loopback mode at the other end
> > > of a link
> > > is a requirement.
> > >
> > > There is also a group of people that believe that the
> > functionality of
> > > loopback can be achieved without a loopback mode, but
> > > enhancing the MIBS
> > > and the PHY functionality.  They are actively investigating the
> > > possibility.  When and if they think they can show equivalent
> > > functionality, the results will be presented to the
> > > reflector.  At that
> > > point everyone can judge whether the alternate method provides
> > > equivalent function.
> > >
> > > Loopback itself is a function.  The function is used to
> > > fulfill certain
> > > operational requirements.  If those requirements can be met
> > with other
> > > methods, and this point can be provent to the group as whole
> > > (including
> > > Kent), then the other methods deserve consideration.  I don't
> > > think this
> > > is in any way conflicts with Kent's statement (though I'm sure he'll
> > > correct me if I'm wrong).
> > >
> > > Loopback will remain a requirement until someone can prove
> > to the OAM
> > > group that there is a better way.
> > >
> > > - Matt
> > >
> > >
> > > Roy Bynum wrote:
> > > >
> > > > Kent,
> > > >
> > > > I have found that if you do not use strong enough language,
> > > the vendors
> > > > that may not have what you require, will attempt to
> > > "interpret" your words
> > > > so that they can mean something totally different than what you
> > > > intended.  If I am correct, you may want to resend your
> > > comment and use
> > > the
> > > > words "our operations requires that ability".  If you check
> > > with your
> > > > equipment "certification" people for edge access
> > > infrastructure, you may
> > > > find that loop back functionality at the physical layer is a hard
> > > > requirement, just like it is on T1/T3 infrastructure today.
> > >  I know that
> > > it
> > > > was a requirement the large service provider that I was
> > > previously with.
> > > >
> > > > Thank you,
> > > > Roy Bynum
> > > >
> > > > At 04:18 PM 2/15/2002 -0800, kmccammon@tri.sbc.com wrote:
> > > >
> > > > >Bob,
> > > > >Loopback functionality is important for SBC, our
> > > operations need that
> > > > >ability.
> > > > >-Kent
> > > > >
> > > > >Kent G. McCammon
> > > > >Broadband Access Group
> > > > >SBC Technology Resources, Inc
> > > > >4698 Willow Road
> > > > >Pleasanton, CA 94588
> > > > >925-598-1246
> > > > >kmccammon@tri.sbc.com
> > > > >
> > >
> > >
> > > _______________________________________________
> > > Hubmib mailing list
> > > Hubmib@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/hubmib
> > >
> >
> > _______________________________________________
> > Hubmib mailing list
> > Hubmib@ietf.org
> > https://www1.ietf.org/mailman/listinfo/hubmib
> >
>
>_______________________________________________
>ifmib mailing list
>ifmib@ietf.org
>https://www1.ietf.org/mailman/listinfo/ifmib


_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

Kaj Tesink
Telcordia Technologies. In.
331 Newman Springs Road
Red Bank, NJ 07701
Email: kaj @research.telcordia.com
Tel: (732) 758-5254
Fax: (732) 758-4177

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Tue Feb 19 15:40:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04798
	for <hubmib-archive@odin.ietf.org>; Tue, 19 Feb 2002 15:40:53 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA01428;
	Tue, 19 Feb 2002 15:32:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA00737
	for <hubmib@optimus.ietf.org>; Tue, 19 Feb 2002 07:00:58 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14786;
	Tue, 19 Feb 2002 07:00:53 -0500 (EST)
Message-Id: <200202191200.HAA14786@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: hubmib@ietf.org, atommib@research.telcordia.com
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 19 Feb 2002 07:00:48 -0500
Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-wis-mib-02.txt
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Ethernet Interfaces and Hub MIB Working Group of the IETF.

	Title		: Definition of Managed Objects for the Ethernet WAN 
                          Interface Sublayer
	Author(s)	: M. Ayers et al.
	Filename	: draft-ietf-hubmib-wis-mib-02.txt
	Pages		: 39
	Date		: 18-Feb-02
	
This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP based
internets.  In particular, it defines objects for managing the
Ethernet Wide Area Network (WAN) Interface Sublayer (WIS) [P802.3ae].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-02.txt

To remove yourself from the IETF Announcement list, send a message to 
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-ietf-hubmib-wis-mib-02.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-hubmib-wis-mib-02.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020218134013.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-hubmib-wis-mib-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-hubmib-wis-mib-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020218134013.I-D@ietf.org>

--OtherAccess--

--NextPart--




_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Tue Feb 19 16:27:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04815
	for <hubmib-archive@odin.ietf.org>; Tue, 19 Feb 2002 15:40:57 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA01879
	for hubmib-archive@odin.ietf.org; Tue, 19 Feb 2002 15:40:56 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA01428;
	Tue, 19 Feb 2002 15:32:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA00737
	for <hubmib@optimus.ietf.org>; Tue, 19 Feb 2002 07:00:58 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14786;
	Tue, 19 Feb 2002 07:00:53 -0500 (EST)
Message-Id: <200202191200.HAA14786@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: hubmib@ietf.org, atommib@research.telcordia.com
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 19 Feb 2002 07:00:48 -0500
Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-wis-mib-02.txt
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Ethernet Interfaces and Hub MIB Working Group of the IETF.

	Title		: Definition of Managed Objects for the Ethernet WAN 
                          Interface Sublayer
	Author(s)	: M. Ayers et al.
	Filename	: draft-ietf-hubmib-wis-mib-02.txt
	Pages		: 39
	Date		: 18-Feb-02
	
This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP based
internets.  In particular, it defines objects for managing the
Ethernet Wide Area Network (WAN) Interface Sublayer (WIS) [P802.3ae].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-02.txt

To remove yourself from the IETF Announcement list, send a message to 
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-ietf-hubmib-wis-mib-02.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-hubmib-wis-mib-02.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020218134013.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-hubmib-wis-mib-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-hubmib-wis-mib-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020218134013.I-D@ietf.org>

--OtherAccess--

--NextPart--




_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Tue Feb 26 13:19:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14312
	for <hubmib-archive@odin.ietf.org>; Tue, 26 Feb 2002 13:19:31 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA08759;
	Tue, 26 Feb 2002 13:11:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA08731
	for <hubmib@optimus.ietf.org>; Tue, 26 Feb 2002 13:11:02 -0500 (EST)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13871
	for <hubmib@ietf.org>; Tue, 26 Feb 2002 13:10:55 -0500 (EST)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id NAA15623
	for <hubmib@ietf.org>; Tue, 26 Feb 2002 13:09:26 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id NAA15609
	for <hubmib@ietf.org>; Tue, 26 Feb 2002 13:09:25 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1BEF0.BB148B1D"
Date: Tue, 26 Feb 2002 20:09:28 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F60D0DC@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Agenda for the 53rd IETF Meeting
Thread-Index: AcG+8OQ+57aKHXRWSK26Sjny/olMwA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
Subject: [Hubmib] Agenda for the 53rd IETF Meeting
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1BEF0.BB148B1D
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

We will have a one hour meeting in Minneapolis, at the 53rd IETF
meeting. I would like to propose the following agenda. Please comment,
before I submit it to the IESG.
Thanks and Regards,
Dan

TUESDAY, March 19, 2002=20
1300-1400 Afternoon Sessions I=20
WG OPS hubmib Ethernet Interfaces and Hub MIB WG=20

Chair: Dan Romascanu - dromasca@avaya.com

Introductions, Agenda bashing, Minutes Taker - 5 min
IEEE 802.3 status - Dan Romascanu - 10 min
Interworking Labs Testing Results and Impact on the Ethernet-like
Interfaces MIB - Chris Wellens, John Flick - 30 min
Next Steps, How to complete WG Charter - 15 min

Internet-Drafts

http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-ethe
rif-mib-v3-00.txt
http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-mau-
mib-v3-00.txt
http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-powe
r-ethernet-mib-01.txt




------_=_NextPart_001_01C1BEF0.BB148B1D
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Agenda for the 53rd IETF Meeting</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">We will =
have a one hour meeting in Minneapolis, at the 53rd IETF meeting. I =
would like to propose the following agenda. Please comment, before I =
submit it to the IESG.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">Thanks =
and Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New =
Roman">Dan</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New =
Roman">TUESDAY, March 19, 2002 </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New =
Roman">1300-1400 Afternoon Sessions I </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">WG OPS =
hubmib Ethernet Interfaces and Hub MIB WG </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Chair: Dan =
Romascanu - dromasca@avaya.com</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">Introductions, Agenda bashing, Minutes Taker - 5 =
min</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">IEEE 802.3 =
status - Dan Romascanu - 10 min</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">Interworking Labs Testing Results and Impact on the =
Ethernet-like Interfaces MIB - Chris Wellens, John Flick - 30 =
min</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Next Steps, =
How to complete WG Charter - 15 min</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">Internet-Drafts</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubm=
ib-etherif-mib-v3-00.txt">http://www.ietf.cnri.reston.va.us/internet-draf=
ts/draft-ietf-hubmib-etherif-mib-v3-00.txt</A></FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubm=
ib-mau-mib-v3-00.txt">http://www.ietf.cnri.reston.va.us/internet-drafts/d=
raft-ietf-hubmib-mau-mib-v3-00.txt</A></FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubm=
ib-power-ethernet-mib-01.txt">http://www.ietf.cnri.reston.va.us/internet-=
drafts/draft-ietf-hubmib-power-ethernet-mib-01.txt</A></FONT></SPAN></P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C1BEF0.BB148B1D--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Tue Feb 26 13:19:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14322
	for <hubmib-archive@odin.ietf.org>; Tue, 26 Feb 2002 13:19:31 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA09207
	for hubmib-archive@odin.ietf.org; Tue, 26 Feb 2002 13:19:33 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA08759;
	Tue, 26 Feb 2002 13:11:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA08731
	for <hubmib@optimus.ietf.org>; Tue, 26 Feb 2002 13:11:02 -0500 (EST)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13871
	for <hubmib@ietf.org>; Tue, 26 Feb 2002 13:10:55 -0500 (EST)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id NAA15623
	for <hubmib@ietf.org>; Tue, 26 Feb 2002 13:09:26 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id NAA15609
	for <hubmib@ietf.org>; Tue, 26 Feb 2002 13:09:25 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1BEF0.BB148B1D"
Date: Tue, 26 Feb 2002 20:09:28 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F60D0DC@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Agenda for the 53rd IETF Meeting
Thread-Index: AcG+8OQ+57aKHXRWSK26Sjny/olMwA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
Subject: [Hubmib] Agenda for the 53rd IETF Meeting
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1BEF0.BB148B1D
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

We will have a one hour meeting in Minneapolis, at the 53rd IETF
meeting. I would like to propose the following agenda. Please comment,
before I submit it to the IESG.
Thanks and Regards,
Dan

TUESDAY, March 19, 2002=20
1300-1400 Afternoon Sessions I=20
WG OPS hubmib Ethernet Interfaces and Hub MIB WG=20

Chair: Dan Romascanu - dromasca@avaya.com

Introductions, Agenda bashing, Minutes Taker - 5 min
IEEE 802.3 status - Dan Romascanu - 10 min
Interworking Labs Testing Results and Impact on the Ethernet-like
Interfaces MIB - Chris Wellens, John Flick - 30 min
Next Steps, How to complete WG Charter - 15 min

Internet-Drafts

http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-ethe
rif-mib-v3-00.txt
http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-mau-
mib-v3-00.txt
http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-powe
r-ethernet-mib-01.txt




------_=_NextPart_001_01C1BEF0.BB148B1D
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Agenda for the 53rd IETF Meeting</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">We will =
have a one hour meeting in Minneapolis, at the 53rd IETF meeting. I =
would like to propose the following agenda. Please comment, before I =
submit it to the IESG.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">Thanks =
and Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New =
Roman">Dan</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New =
Roman">TUESDAY, March 19, 2002 </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New =
Roman">1300-1400 Afternoon Sessions I </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">WG OPS =
hubmib Ethernet Interfaces and Hub MIB WG </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Chair: Dan =
Romascanu - dromasca@avaya.com</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">Introductions, Agenda bashing, Minutes Taker - 5 =
min</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">IEEE 802.3 =
status - Dan Romascanu - 10 min</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">Interworking Labs Testing Results and Impact on the =
Ethernet-like Interfaces MIB - Chris Wellens, John Flick - 30 =
min</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Next Steps, =
How to complete WG Charter - 15 min</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">Internet-Drafts</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubm=
ib-etherif-mib-v3-00.txt">http://www.ietf.cnri.reston.va.us/internet-draf=
ts/draft-ietf-hubmib-etherif-mib-v3-00.txt</A></FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubm=
ib-mau-mib-v3-00.txt">http://www.ietf.cnri.reston.va.us/internet-drafts/d=
raft-ietf-hubmib-mau-mib-v3-00.txt</A></FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubm=
ib-power-ethernet-mib-01.txt">http://www.ietf.cnri.reston.va.us/internet-=
drafts/draft-ietf-hubmib-power-ethernet-mib-01.txt</A></FONT></SPAN></P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C1BEF0.BB148B1D--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Wed Feb 27 13:15:47 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07625
	for <hubmib-archive@odin.ietf.org>; Wed, 27 Feb 2002 13:15:47 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA08560;
	Wed, 27 Feb 2002 13:15:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA08446
	for <hubmib@optimus.ietf.org>; Wed, 27 Feb 2002 13:15:08 -0500 (EST)
Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07563
	for <hubmib@ietf.org>; Wed, 27 Feb 2002 13:15:03 -0500 (EST)
Received: from iere.net.avaya.com (localhost [127.0.0.1])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g1RIDdA09998
	for <hubmib@ietf.org>; Wed, 27 Feb 2002 13:13:39 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g1RIDcv09986
	for <hubmib@ietf.org>; Wed, 27 Feb 2002 13:13:38 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1BFBA.79645584"
Date: Wed, 27 Feb 2002 20:13:36 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F60D0E9@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Agenda Proposal - Joint Meeting of the atommib and hubmib wgs in Minneapolis
Thread-Index: AcG/uqHXDXSoVniXRGakIUhVncl2WA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>, <atommib@research.telcordia.com>
Subject: [Hubmib] Agenda Proposal - Joint Meeting of the atommib and hubmib wgs in Minneapolis
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1BFBA.79645584
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

We have a one hour joint meeting scheduled for the 53rd IETF. Here is
the proposal for the agenda. Please comment and suggest changes if
needed. Regards, Dan


TUESDAY, March 19, 2002=20
1700-1800 Afternoon Sessions IV
 INT atommib &OPS &hubmib AToM MIB WG & Ethernet Interfaces and Hub MIB
WG=20

Chairs: Dan Romascanu - dromasca@avaya.com, Faye Ly -
fayely98@hotmail.com, Nathan Kohn - mvnk@lucent.com
=20
Introductions, Agenda bashing, Minutes Taker - 5 min
IEEE 802.3 status - Dan Romascanu - 10 min
WIS MIB Status and Open Issues Resolution -  Mike Heard and KC Norseth -
30 min
Next Steps, How to complete WGs Charter - 15 min
=20
Internet-Draft
=20
http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-wis-
mib-02.txt
=20


------_=_NextPart_001_01C1BFBA.79645584
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Agenda Proposal - Joint Meeting of the atommib and hubmib wgs in =
Minneapolis</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">We have a one hour joint =
meeting scheduled for the 53rd IETF. Here is the proposal for the =
agenda. Please comment and suggest changes if needed. Regards, =
Dan</FONT></P>
<BR>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">TUESDAY, March 19, 2002 =
</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">1700-1800 Afternoon Sessions =
IV</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;INT atommib &amp;OPS =
&amp;hubmib AToM MIB WG &amp; Ethernet Interfaces and Hub MIB WG =
</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Chairs: Dan Romascanu - =
dromasca@avaya.com, Faye Ly -</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">fayely98@hotmail.com, Nathan =
Kohn - mvnk@lucent.com</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Introductions, Agenda =
bashing, Minutes Taker - 5 min</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">IEEE 802.3 status - Dan =
Romascanu - 10 min</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">WIS MIB Status and Open =
Issues Resolution -&nbsp; Mike Heard and KC Norseth - 30 min</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Next Steps, How to complete =
WGs Charter - 15 min</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Internet-Draft</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubm=
ib-wis-mib-02.txt">http://www.ietf.cnri.reston.va.us/internet-drafts/draf=
t-ietf-hubmib-wis-mib-02.txt</A></FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C1BFBA.79645584--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Wed Feb 27 13:15:48 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07641
	for <hubmib-archive@odin.ietf.org>; Wed, 27 Feb 2002 13:15:48 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA09873
	for hubmib-archive@odin.ietf.org; Wed, 27 Feb 2002 13:15:50 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA08560;
	Wed, 27 Feb 2002 13:15:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA08446
	for <hubmib@optimus.ietf.org>; Wed, 27 Feb 2002 13:15:08 -0500 (EST)
Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07563
	for <hubmib@ietf.org>; Wed, 27 Feb 2002 13:15:03 -0500 (EST)
Received: from iere.net.avaya.com (localhost [127.0.0.1])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g1RIDdA09998
	for <hubmib@ietf.org>; Wed, 27 Feb 2002 13:13:39 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g1RIDcv09986
	for <hubmib@ietf.org>; Wed, 27 Feb 2002 13:13:38 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1BFBA.79645584"
Date: Wed, 27 Feb 2002 20:13:36 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F60D0E9@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Agenda Proposal - Joint Meeting of the atommib and hubmib wgs in Minneapolis
Thread-Index: AcG/uqHXDXSoVniXRGakIUhVncl2WA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>, <atommib@research.telcordia.com>
Subject: [Hubmib] Agenda Proposal - Joint Meeting of the atommib and hubmib wgs in Minneapolis
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1BFBA.79645584
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

We have a one hour joint meeting scheduled for the 53rd IETF. Here is
the proposal for the agenda. Please comment and suggest changes if
needed. Regards, Dan


TUESDAY, March 19, 2002=20
1700-1800 Afternoon Sessions IV
 INT atommib &OPS &hubmib AToM MIB WG & Ethernet Interfaces and Hub MIB
WG=20

Chairs: Dan Romascanu - dromasca@avaya.com, Faye Ly -
fayely98@hotmail.com, Nathan Kohn - mvnk@lucent.com
=20
Introductions, Agenda bashing, Minutes Taker - 5 min
IEEE 802.3 status - Dan Romascanu - 10 min
WIS MIB Status and Open Issues Resolution -  Mike Heard and KC Norseth -
30 min
Next Steps, How to complete WGs Charter - 15 min
=20
Internet-Draft
=20
http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-wis-
mib-02.txt
=20


------_=_NextPart_001_01C1BFBA.79645584
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Agenda Proposal - Joint Meeting of the atommib and hubmib wgs in =
Minneapolis</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">We have a one hour joint =
meeting scheduled for the 53rd IETF. Here is the proposal for the =
agenda. Please comment and suggest changes if needed. Regards, =
Dan</FONT></P>
<BR>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">TUESDAY, March 19, 2002 =
</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">1700-1800 Afternoon Sessions =
IV</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;INT atommib &amp;OPS =
&amp;hubmib AToM MIB WG &amp; Ethernet Interfaces and Hub MIB WG =
</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Chairs: Dan Romascanu - =
dromasca@avaya.com, Faye Ly -</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">fayely98@hotmail.com, Nathan =
Kohn - mvnk@lucent.com</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Introductions, Agenda =
bashing, Minutes Taker - 5 min</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">IEEE 802.3 status - Dan =
Romascanu - 10 min</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">WIS MIB Status and Open =
Issues Resolution -&nbsp; Mike Heard and KC Norseth - 30 min</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Next Steps, How to complete =
WGs Charter - 15 min</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Internet-Draft</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubm=
ib-wis-mib-02.txt">http://www.ietf.cnri.reston.va.us/internet-drafts/draf=
t-ietf-hubmib-wis-mib-02.txt</A></FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C1BFBA.79645584--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



