From disman-bounces@ietf.org Thu Jun 01 11:38:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FlpFJ-0002I1-J1; Thu, 01 Jun 2006 11:38:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FlpFI-0002Hw-Pq
	for disman@ietf.org; Thu, 01 Jun 2006 11:38:00 -0400
Received: from co300216-ier2.net.avaya.com ([198.152.13.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlpFG-0007wk-Gj
	for disman@ietf.org; Thu, 01 Jun 2006 11:38:00 -0400
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id k51Fa2Cj024726
	for <disman@ietf.org>; Thu, 1 Jun 2006 11:36:03 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C68591.5A8E80E8"
Date: Thu, 1 Jun 2006 18:37:56 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0A3ADC36@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Index: AcaFkVqMUP9wlWbhSM6fDuBgAAwNywAAAABq
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "disman" <disman@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: [Disman] Out of Office AutoReply: 
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Errors-To: disman-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C68591.5A8E80E8
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

I am out-of-office on vacation and will be back on June 5, 2006.  I will =
not read e-mail during this period.  If you need to contact me urgently, =
please leave a voice mail message at my office number.

Regards,

Dan


------_=_NextPart_001_01C68591.5A8E80E8
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.6617.47">
<TITLE>Out of Office AutoReply: </TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I am out-of-office on vacation and will be back on =
June 5, 2006.&nbsp; I will not read e-mail during this period.&nbsp; If =
you need to contact me urgently, please leave a voice mail message at my =
office number.<BR>
<BR>
Regards,<BR>
<BR>
Dan<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C68591.5A8E80E8--




From disman-bounces@ietf.org Fri Jun 02 01:36:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fm2L7-0003vw-3O; Fri, 02 Jun 2006 01:36:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fm2L5-0003vh-QM; Fri, 02 Jun 2006 01:36:51 -0400
Received: from pop-cowbird.atl.sa.earthlink.net ([207.69.195.68])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fm2L1-0007sY-DG; Fri, 02 Jun 2006 01:36:51 -0400
Received: from h-68-166-189-153.snvacaid.dynamic.covad.net ([68.166.189.153]
	helo=oemcomputer)
	by pop-cowbird.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1Fm2L0-00007S-00; Fri, 02 Jun 2006 01:36:46 -0400
Message-ID: <000701c68607$56c85360$6501a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "LTRU Working Group" <ltru@ietf.org>, "Disman" <disman@ietf.org>,
	<agentx@ietf.org>
Date: Thu, 1 Jun 2006 22:42:29 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: 
Subject: [Disman] Fw: Internet-Drafts Submission Cutoff Dates for the 66th
	IETF Meeting in Montreal, Quebec, Canada 
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Errors-To: disman-bounces@ietf.org

Hi -

A reminder from the secretariat.

Randy

> From: <ietf-secretariat@ietf.org>
> To: <ietf-announce@ietf.org>
> Sent: Thursday, June 01, 2006 9:00 PM
> Subject: Internet-Drafts Submission Cutoff Dates for the 66th IETF Meeting in Montreal, Quebec, Canada 
>
> 
> There are two (2) Internet-Draft cutoff dates for the 66th 
> IETF Meeting in Montreal, Quebec, Canada:
> 
> June 19th: Cutoff Date for Initial (i.e., version -00) 
> Internet-Draft Submissions 
> 
> All initial Internet-Drafts (version -00) must be submitted by Monday, 
> June 19th at 9:00 AM ET. As always, all initial submissions with a 
> filename beginning with "draft-ietf" must be approved by the 
> appropriate WG Chair before they can be processed or announced.  The 
> Secretariat would appreciate receiving WG Chair approval by Monday, 
> June 12th at 9:00 AM ET.
> 
> June 26th: Cutoff Date for Revised (i.e., version -01 and higher) 
> Internet-Draft Submissions 
> 
> All revised Internet-Drafts (version -01 and higher) must be submitted 
> by Monday, June 26th at 9:00 AM ET.
> 
> Initial and revised Internet-Drafts received after their respective 
> cutoff dates will not be made available in the Internet-Drafts 
> directory or announced until on or after Monday, July 10th at 9:00 
> AM ET, when Internet-Draft posting resumes.  Please do not wait until 
> the last minute to submit.
> 
> Thank you for your understanding and cooperation. If you have any 
> questions or concerns, then please send a message to 
> internet-drafts@ietf.org.
> 
> The IETF Secretariat
> 
> FYI: The Internet-Draft cutoff dates as well as other significant dates
> for the 66th IETF Meeting can be found at http://www.ietf.org/meetings/cutoff_dates_66.html.
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce





From disman-bounces@ietf.org Fri Jun 02 22:24:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FmLnx-0000Rs-6V; Fri, 02 Jun 2006 22:23:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FmLnv-0000Pt-Az; Fri, 02 Jun 2006 22:23:55 -0400
Received: from pop-gadwall.atl.sa.earthlink.net ([207.69.195.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FmLnu-0001pC-2h; Fri, 02 Jun 2006 22:23:55 -0400
Received: from h-68-166-189-153.snvacaid.dynamic.covad.net ([68.166.189.153]
	helo=oemcomputer)
	by pop-gadwall.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1FmLns-0000dt-00; Fri, 02 Jun 2006 22:23:52 -0400
Message-ID: <001001c686b5$88a735a0$6501a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman" <disman@ietf.org>,
	<ltru@lists.ietf.org>
Date: Fri, 2 Jun 2006 19:29:25 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: 
Subject: [Disman] Fw: Pre-IPV6 maintenance of one of the www.ietf.org
	servers -2006/06/03 - 12:00am EST
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Errors-To: disman-bounces@ietf.org

Hi -

In case you're not on the ietf@ietf.org or ietf-announce@ietf.org 
distribution lists....

Randy

> From: <ietf-secretariat@ietf.org>
> To: <ietf-announce@ietf.org>; <ietf@ietf.org>
> Sent: Friday, June 02, 2006 6:29 PM
> Subject: Pre-IPV6 maintenance of one of the www.ietf.org servers -2006/06/03 - 12:00am EST
>
> 
> Hi All,
> 
> Tomorrow Saturday June 3 at 12:00am EST, we will be taking down one of
> the round robin www servers for the IETF (209.173.53.180) for
> maintenance in preparation for supporting IPV6.  The outage should be
> less than 1 hour.  This system also serves as the primary site for...
> 
>      noc.ietf.org
>      www.iab.org
>      www.iesg.org
> 
> so those sites will also be down.
> 
> Mail and the mailing lists (and their archives) should no be affected.
> 
> If after 01:00AM EST you experience any difficulties, or notice
> anything amiss with the sites, please send email to ietf-action at
> ietf.org, the IAD at iad at ietf.org, and copy ietf-admin at
> techsquare.com and rpelletier at isoc.org.  In case of an emergency,
> please call the emergency number: +1 301-858-6268.
> 
> Thank you for your patience.
> 
> IETF Secretariat.
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf





From yuaaaqwhoj@write-promotion.com Sat Jun 03 05:18:52 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FmSHU-0003Zd-LS
	for disman-archive@lists.ietf.org; Sat, 03 Jun 2006 05:18:52 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FmSHU-0001QU-Jy
	for disman-archive@lists.ietf.org; Sat, 03 Jun 2006 05:18:52 -0400
Received: from [86.122.207.146] (helo=mnnav)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1FmS7g-0002bn-4o
	for disman-archive@lists.ietf.org; Sat, 03 Jun 2006 05:08:47 -0400
Received: (qmail 25806 invoked from network); Sat, 3 Jun 2006 12:08:22 +0300
Received: from unknown (HELO tc.trykz) (86.122.99.86)
	by mnnav with SMTP; Sat, 3 Jun 2006 12:08:22 +0300
Message-ID: <000e01c686ed$4379ba71$56637a56@tc.trykz>
From: "Katie Vazquez" <yuaaaqwhoj@write-promotion.com>
To: <disman-archive@lists.ietf.org>
Subject: root
Date: Sat, 3 Jun 2006 12:01:40 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="Windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25

Investment Times Alert Issues: (S T R O N G  B U Y)
Sick of hedge funds and flippers getting all the great new issues?
We give it to you again as a gift.
This company is doing incredible things.
The stocks we profile show a significant increase in stock price and
sometimes in days, not months or years.

Trading Date : 05/06/06
Name : Wataire Industries Inc.
S y m b o l  :  W T A F 
Profits of 200-400 % EXPECTED
Current Price : $0.60
2-5 Day Trading : $2
Status : 200-400%





From rpyroa@pvwebs.com Mon Jun 05 15:00:02 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FnKJ0-0000FO-Pz
	for disman-archive@lists.ietf.org; Mon, 05 Jun 2006 15:00:02 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FnKJ0-0001lc-OY
	for disman-archive@lists.ietf.org; Mon, 05 Jun 2006 15:00:02 -0400
Received: from [85.106.164.204] (helo=dsl85-106-42188.ttnet.net.tr)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1FnKIy-0004R6-TT
	for disman-archive@lists.ietf.org; Mon, 05 Jun 2006 15:00:02 -0400
Received: from [85.106.181.163] (helo=matv)
	by dsl85-106-42188.ttnet.net.tr with smtp (Exim 4.43)
	id 1FnRvy-0006ne-Lj; Mon, 5 Jun 2006 22:08:46 -0500
Message-ID: <002301c68915$e4059f26$a3b56a55@matv>
From: "Gregory Gordon" <rpyroa@pvwebs.com>
To: <disman-archive@lists.ietf.org>
Subject: insure martial law
Date: Mon, 5 Jun 2006 22:00:54 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="Windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8

Investor Alert - WE HAVE A RUNNER !
Big news expected.

Trade Date : Monday, June 5, 2006
Company : Amerossi International Group Inc.
Ticker :  A M S N 
Today : $0.05
Tomorrow : $0.40 - $0.60
Rating : 300-500%

WE SEE A RUN STARTING TO HAPPEN.
So if you haven't done your DD yet, you better hurry because it
appears that the huge move is about to start.
We Love this company and at anytime they can put out major news
and the price can triple.
Our mission is to claw our way through the thousands of
underperforming companies out there to find the golden needle
in the haystack.
Do not wait until it is too late!!!




From odiqpfxhqkzc@teamspecialist.com Tue Jun 06 08:08:41 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FnaMT-0001Yx-J1
	for disman-archive@lists.ietf.org; Tue, 06 Jun 2006 08:08:41 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FnaMT-0008Hf-Gu
	for disman-archive@lists.ietf.org; Tue, 06 Jun 2006 08:08:41 -0400
Received: from [213.55.91.42] (helo=ijwcoun)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1FnaMQ-0002C0-Ux
	for disman-archive@lists.ietf.org; Tue, 06 Jun 2006 08:08:40 -0400
Received: from qscsu.qv ([213.55.150.26])
	by ijwcoun (8.13.1/8.13.1) with SMTP id k56C9uL0024645;
	Tue, 6 Jun 2006 15:09:56 +0300
Message-ID: <002201c68961$effd0f5d$1a9637d5@qscsu.qv>
From: "Walt Brooks" <odiqpfxhqkzc@teamspecialist.com>
To: <disman-archive@lists.ietf.org>
Subject: primary school
Date: Tue, 6 Jun 2006 14:59:22 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="Windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3

Trade Date: Tuesday, June 6th, 2006
Company: BioElectronics Corporation
Symbol: BIEL
Price: $0.025

IS MOMENTUM BUILDING FOR THIS STOCK? CAN YOU MAKE SOME FAST MONEY ON IT?
RADAR BIEL FOR TUESDAY'S OPEN RIGHT NOW!!

THE ALERT IS ON!!!

RECENT NEWS HEADLINE: (GO READ ALL THE NEWS ON BIEL RIGHT NOW!)

BioElectronics Corporation Announces New 510(k) Market Clearance Application 
Filed With FDA!!


About BioElectronics Corporation (Source: News 5/18/2006)

BioElectronics currently manufactures and sells ActiPatch(TM), a drug-free 
anti-inflammatory patch with an embedded battery operated microchip that 
delivers weeks of continuous pulsed therapy for less than a dollar a day. 
The unique ActiPatch delivery system, using patented technology, provides 
a cost-effective, patient friendly method to reduce soft tissue pain and 
swelling.


GO READ ALL THE NEWS ON THIS ONE!! DO YOUR DUE DILIGENCE!!
RADAR IT FOR TUESDAY'S OPEN NOW! 


______________



Information within this report contains forward looking statements within 
the meaning of Section 27A of the Securities Act of 1933 and Section 21B 
of the SEC Act of 1934. Statements that involve discussions with respect 
to projections of future events are not statements of historical fact and 
may be  forward looking statements. Don't rely on them to make a decision. 
Past performance is never indicative of future results. We received four 
hundred thousand free trading shares in the past for our services. 
All those shares have been sold. We have received an additional one million 
free trading shares now. We intend to sell all one million shares now, 
which could cause the stock to go down, resulting in losses for you. 
The four hundred thousand shares and one million shares were received from 
two different third parties, not officers, directors or affiliate 
shareholders. This company has: an accumulated deficit, a negative net 
worth, a reliance on loans from officers directors and affiliates to pay 
expenses, and a nominal cash position. These factors raise substantial 
doubt about its ability to continue as a going concern. The company and 
its president are a defendant in a lawsuit. The publicly available float 
of stock is currently increasing. URGENT: Read the company's SEC filing 
before you invest. This report shall not be construed as any kind of 
investment advice or solicitation. WARNING: You can lose all your money 
by investing in this stock.




From romkysu@carin.freeserve.co.uk Wed Jun 07 21:20:44 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fo9CW-0002ms-Bt
	for disman-archive@lists.ietf.org; Wed, 07 Jun 2006 21:20:44 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fo9CW-00008U-A5
	for disman-archive@lists.ietf.org; Wed, 07 Jun 2006 21:20:44 -0400
Received: from [85.104.156.45] (helo=dsl85-104-39981.ttnet.net.tr)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1Fo9CU-0002f2-DC
	for disman-archive@lists.ietf.org; Wed, 07 Jun 2006 21:20:43 -0400
Received: from xhco.kxbzy ([85.104.76.122])
	by dsl85-104-39981.ttnet.net.tr (8.13.2/8.13.2) with SMTP id k581O757022276;
	Thu, 8 Jun 2006 04:24:07 +0300
Message-ID: <000501c68a99$c1e94f19$7a4c6855@xhco.kxbzy>
From: "Amabel Byrne" <romkysu@carin.freeserve.co.uk>
To: <disman-archive@lists.ietf.org>
Subject: A Sterling Stock Report
Date: Thu, 8 Jun 2006 04:15:27 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="Windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.7 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2

WINNER**WINNER**WINNER**WINNER**WINNER

To All Investors.

Put HRRP on your Radar Screens immediately
Now is the time to do your research. 5:1 Forward Split 
The forward stock split will be effective on or about June 15, 2006, at which 
time the additional shares in certificate form will be mailed directly to 
shareholders without action on their part.

Date: Thursday, June 8, 2006
HE-5 Resources, Corp. 
Symbol: HRRP
Price: $0.47
Position: Positive Buy
Gold, Silver, Copper, Zinc and Platinum

Breaking News was Released
HE-5 Resources, Corp. Extends Record Date of Forward Split 

For pennies you can participate in a ST0CK that could yield results over 
and over again just based on the trading patterns if the company is 
able to effectuate it's business model. 

WATCH OUT!!! 
We could see a GREAT STORY IN THE MAKING. 

GOOD LUCK AND TRADE OUT AT THE TOP!!!!

Sincerely,
Jose Mckinley
RVG Group




From disman-bounces@ietf.org Thu Jun 22 15:04:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtUTP-0003ey-H2; Thu, 22 Jun 2006 15:04:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtUTO-0003Yt-28; Thu, 22 Jun 2006 15:04:14 -0400
Received: from pop-satin.atl.sa.earthlink.net ([207.69.195.63])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FtUTM-0002P2-Ra; Thu, 22 Jun 2006 15:04:14 -0400
Received: from h-68-165-4-99.snvacaid.dynamic.covad.net ([68.165.4.99]
	helo=oemcomputer)
	by pop-satin.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1FtUTM-00061X-00; Thu, 22 Jun 2006 15:04:12 -0400
Message-ID: <011901c6962e$b06970c0$6501a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman" <disman@ietf.org>
Date: Thu, 22 Jun 2006 12:04:27 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: agentx@ietf.org
Subject: [Disman] Fw: EDU session for MIB documents editors
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Errors-To: disman-bounces@ietf.org

Hi -

Forwarded for your information.

Randy

----- Original Message ----- 
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <wgchairs@ietf.org>
Cc: <mreview@ops.ietf.org>
Sent: Thursday, June 22, 2006 1:51 AM
Subject: EDU session for MIB documents editors


WG Chairs,

Please note that the agenda for the Montreal meeting includes the
following items for Sunday, July 9:

1300-1445 What MIB Document Editors Need to Know - Room 519B 

If MIB documents are in your charter or in your plans I would recommend
that you distribute this announcement your email lists, inviting all
interested parties to attend this session. Besides the informational
presentation that Bert Wijnen will be giving, a number of MIB Doctors
will attend the meeting and will be happy to engage in a dialog with the
present and future MIB editors. 

Dan


 







From disman-bounces@ietf.org Wed Jun 28 11:30:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fvbzn-00064b-8i; Wed, 28 Jun 2006 11:30:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fvbzl-00064O-T3
	for disman@ietf.org; Wed, 28 Jun 2006 11:30:25 -0400
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fvbzl-0003bP-F4
	for disman@ietf.org; Wed, 28 Jun 2006 11:30:25 -0400
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com
	[47.129.230.99])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	k5SFUMC25985
	for <disman@ietf.org>; Wed, 28 Jun 2006 11:30:23 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C69AC7.BEFE0536"
Date: Wed, 28 Jun 2006 11:30:11 -0400
Message-ID: <713043CE8B8E1348AF3C546DBE02C1B4097A7F4E@zcarhxm2.corp.nortel.com>
In-Reply-To: <BF340756D41B804DA55BA53BAACACC888BAEB6@pwave-exch08.pwav.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RFC 3877 question
Thread-Index: AcaaxsuCqJkFO2r2T6Sw1bZ8V3qj1wAAMNOQ
From: "Sharon Chisholm" <schishol@nortel.com>
To: <disman@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: df1883a27a831c1ea5e8cfe5eb3ad38e
Subject: [Disman] RE: RFC 3877 question
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Errors-To: disman-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C69AC7.BEFE0536
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

hi
=20
All three are indices into the table. It is valid to include as an index
something which isn't in the table. Think about all those tables that
are indexed by ifIndex as good examples.
=20
Sharon

-----Original Message-----
From: Adam Deutsch [mailto:adeutsch@pwav.com]=20
Sent: Wednesday, June 28, 2006 11:23 AM
To: disman@ietf.org
Cc: schishol@nortelnetworks.com; dromasca@avaya.com
Subject: RFC 3877 question



Hello,

=20

I am contemplating implementing the ALARM-MIB on one of our products and
have encountered an entry in the definition of the ALARM-MIB that may be
an error (either that or I am missing something - which is very likely).

=20

The problem I have is with the INDEX statement for the alarmModelEntry,
which I have reproduced below:

=20

=20

alarmModelEntry OBJECT-TYPE

   SYNTAX      AlarmModelEntry

   MAX-ACCESS  not-accessible

   STATUS      current

   DESCRIPTION

       "Entries appear in this table for each possible alarm state.

       This table MUST be persistent across system reboots."

   INDEX       { alarmListName, alarmModelIndex, alarmModelState }

   ::=3D { alarmModelTable 1 }

=20

AlarmModelEntry ::=3D SEQUENCE {

   alarmModelIndex                 Unsigned32,

   alarmModelState                 Unsigned32,

   alarmModelNotificationId        OBJECT IDENTIFIER,

   alarmModelVarbindIndex          Unsigned32,

   alarmModelVarbindValue          Integer32,

   alarmModelDescription           SnmpAdminString,

   alarmModelSpecificPointer       RowPointer,

   alarmModelVarbindSubtree        OBJECT IDENTIFIER,

   alarmModelResourcePrefix        OBJECT IDENTIFIER,

   alarmModelRowStatus             RowStatus

   }

=20

According to this definition, alarmListName is one of three indexes used
for the alarmModelEntry. However, alarmListName is not one of the
objects appearing in the AlarmModelEntry sequence.

=20

I believe that alarmListName was erroneously included in the INDEX
statement, and that only alarmModelIndex and alarmModelState should be
used as indices into the alarmModelEntry. Am I wrong?=20

=20

Any explanations you can offer would be greatly appreciated.

=20

Regards

=20

Adam Deutsch

Powerwave Technologies

+1-905-946-3395

=20


------_=_NextPart_001_01C69AC7.BEFE0536
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1543" name=3DGENERATOR>
<STYLE>@page Section1 {size: 612.0pt 792.0pt; margin: 72.0pt 90.0pt =
72.0pt 90.0pt; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV><SPAN class=3D209512815-28062006><FONT face=3DArial color=3D#0000ff =

size=3D2>hi</FONT></SPAN></DIV>
<DIV><SPAN class=3D209512815-28062006><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D209512815-28062006><FONT face=3DArial color=3D#0000ff =
size=3D2>All=20
three are indices into the table. It is valid to include as an index =
something=20
which isn't in the table. Think about all those tables that are indexed =
by=20
ifIndex as good examples.</FONT></SPAN></DIV>
<DIV><SPAN class=3D209512815-28062006><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D209512815-28062006><FONT face=3DArial color=3D#0000ff =

size=3D2>Sharon</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> Adam =
Deutsch=20
  [mailto:adeutsch@pwav.com] <BR><B>Sent:</B> Wednesday, June 28, 2006 =
11:23=20
  AM<BR><B>To:</B> disman@ietf.org<BR><B>Cc:</B> =
schishol@nortelnetworks.com;=20
  dromasca@avaya.com<BR><B>Subject:</B> RFC 3877 =
question<BR><BR></FONT></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Hello,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I am contemplating =
implementing=20
  the ALARM-MIB on one of our products and have encountered an entry in =
the=20
  definition of the ALARM-MIB that may be an error (either that or I am =
missing=20
  something &#8211; which is very likely).<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The problem I have is =
with the=20
  INDEX statement for the alarmModelEntry, which I have reproduced=20
  below:<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">alarmModelEntry=20
  OBJECT-TYPE<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  AlarmModelEntry<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; =
MAX-ACCESS&nbsp;=20
  not-accessible<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;=20
  STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;=20
  DESCRIPTION<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "Entries appear in this table for each possible alarm=20
  state.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  This table MUST be persistent across system=20
  reboots."<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; =
</SPAN></FONT><FONT=20
  face=3DArial size=3D2><SPAN lang=3DSV=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">INDEX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  { alarmListName, alarmModelIndex, alarmModelState=20
  }<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DSV=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; ::=3D { =
alarmModelTable=20
  1 }<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DSV=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">AlarmModelEntry ::=3D =
SEQUENCE=20
  {<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;=20
  =
alarmModelIndex&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Unsigned32,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;=20
  =
alarmModelState&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Unsigned32,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;=20
  alarmModelNotificationId&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
OBJECT=20
  IDENTIFIER,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;=20
  =
alarmModelVarbindIndex&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
  Unsigned32,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; =
</SPAN></FONT><FONT=20
  face=3DArial size=3D2><SPAN lang=3DSV=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">alarmModelVarbindValue&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
  Integer32,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DSV=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;=20
  =
alarmModelDescription&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
  SnmpAdminString,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DSV=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;=20
  alarmModelSpecificPointer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  RowPointer,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DSV=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; =
</SPAN></FONT><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">alarmModelVarbindSubtree&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  OBJECT IDENTIFIER,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;=20
  alarmModelResourcePrefix&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
OBJECT=20
  IDENTIFIER,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;=20
  =
alarmModelRowStatus&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;=20
  RowStatus<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;=20
  }<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">According to this =
definition,=20
  alarmListName is one of three indexes used for the alarmModelEntry. =
However,=20
  alarmListName is not one of the objects appearing in the =
AlarmModelEntry=20
  sequence.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I believe that =
alarmListName was=20
  erroneously included in the INDEX statement, and that only =
alarmModelIndex and=20
  alarmModelState should be used as indices into the alarmModelEntry. Am =
I=20
  wrong? <o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Any explanations you can =
offer=20
  would be greatly appreciated.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Regards<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Adam=20
  Deutsch<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Powerwave=20
  Technologies<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">+1-905-946-3395<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTM=
L>

------_=_NextPart_001_01C69AC7.BEFE0536--




From disman-bounces@ietf.org Fri Jun 30 19:02:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FwRzx-0004e4-51; Fri, 30 Jun 2006 19:02:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FwRzu-0004cv-IL; Fri, 30 Jun 2006 19:02:02 -0400
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FwRzt-0000NF-6J; Fri, 30 Jun 2006 19:02:02 -0400
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k5UN206B010296; 
	Fri, 30 Jun 2006 16:02:00 -0700
Received: (from apache@localhost)
	by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k5UN209D010295;
	Fri, 30 Jun 2006 16:02:00 -0700
Date: Fri, 30 Jun 2006 16:02:00 -0700
Message-Id: <200606302302.k5UN209D010295@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: disman@ietf.org, rfc-editor@rfc-editor.org
Subject: [Disman] 
	RFC 4560 on Definitions of Managed Objects for Remote Ping,
	Traceroute, and Lookup Operations
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Errors-To: disman-bounces@ietf.org


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

        
        RFC 4560

        Title:      Definitions of Managed Objects for 
                    Remote Ping, Traceroute, and Lookup Operations 
        Author:     J. Quittek, Ed.,
                    K. White, Ed.
        Status:     Standards Track
        Date:       June 2006
        Mailbox:    quittek@netlab.nec.de, 
                    wkenneth@us.ibm.com
        Pages:      100
        Characters: 207956
        Obsoletes:  RFC2925
        See-Also:   

        I-D Tag:    draft-ietf-disman-remops-mib-v2-09.txt

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

This memo defines Management Information Bases (MIBs) for performing
ping, traceroute, and lookup operations at a host.  When managing a
network, it is useful to be able to initiate and retrieve the results
of ping or traceroute operations when they are performed at a remote
host.  A lookup capability is defined in order to enable resolution of 
either an IP address to an DNS name or a DNS name to an IP address at a
remote host.

Currently, there are several enterprise-specific MIBs for performing
remote ping or traceroute operations.  The purpose of this memo is to
define a standards-based solution to enable interoperability.  
[STANDARDS TRACK]

This document is a product of the Distributed Management
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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

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

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

help: ways_to_get_rfcs. For example:

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

        help: ways_to_get_rfcs

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

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


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

...






