From owner-disman@dorothy.bmc.com Fri Jan 3 19:56:55 2003 Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22750 for ; Fri, 3 Jan 2003 19:56:54 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id h040wCo03055; Fri, 3 Jan 2003 18:58:12 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA15860 for disman-list; Fri, 3 Jan 2003 16:55:19 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA15854 for disman@dorothy.bmc.com; Fri, 3 Jan 2003 16:55:15 -0800 (PST) Date: Fri, 3 Jan 2003 16:55:15 -0800 (PST) From: Randy Presuhn Message-Id: <200301040055.QAA15854@dorothy.bmc.com> To: disman@dorothy.bmc.com Subject: Disman Note Well Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-disman@dorothy.bmc.com Precedence: bulk List-Id: IETF disman Working Group mailing list Content-Transfer-Encoding: 7bit Hi - This message is sent to all subscribers of the Disman mailing list. To unsubscribe, send a message with a body consisting of the word "unsubscribe" to disman-request@dorothy.bmc.com. If you would like to be able to post from addresses other than your subscription request, or for other administrative requests, please contact disman-owner@dorothy.bmc.com. **************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. **************************************************************** From owner-disman@dorothy.bmc.com Thu Jan 9 21:06:16 2003 Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03742 for ; Thu, 9 Jan 2003 21:06:16 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id h0A26wQ07248; Thu, 9 Jan 2003 20:06:59 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id SAA16124 for disman-list; Thu, 9 Jan 2003 18:03:21 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id SAA16118 for disman@dorothy.bmc.com; Thu, 9 Jan 2003 18:03:14 -0800 (PST) Date: Thu, 9 Jan 2003 18:03:14 -0800 (PST) From: Randy Presuhn Message-Id: <200301100203.SAA16118@dorothy.bmc.com> To: disman@dorothy.bmc.com Subject: Disman in San Francisco? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-disman@dorothy.bmc.com Precedence: bulk List-Id: IETF disman Working Group mailing list Content-Transfer-Encoding: 7bit Hi - It's time to start thinking about whether a disman meeting would be necessary in San Francisco. Since we've completed all our current milestones, and no one has proposed new ones, it seems to me that no meeting will be necessary. Other thoughts? ------------------------------------------------------ Randy Presuhn BMC Software, Inc. SJC-1.3141 randy_presuhn@bmc.com 2141 North First Street Tel: +1 408 546-1006 San José, California 95131 USA ------------------------------------------------------ My opinions and BMC's are independent variables. ------------------------------------------------------ > From owner-wgchairs@ietf.org Tue Jan 7 13:18:49 PST 2003 > Message-Id: <200301071554.KAA18973@ietf.org> > To: wgchairs@ietf.org, bofchairs@ietf.org > From: agenda@ietf.org > Cc: iesg@ietf.org, dinaras@ietf.org > Subject: 56th IETF WG/BOF Scheduling > Date: Tue, 07 Jan 2003 10:54:00 -0500 > > 56th IETF in San Francisco, CA > Meeting Dates: March 16-21, 2003 > > We will be taking scheduling requests for ALL Working Groups and BOFs starting today. > The cut-off for requesting a slot is Tuesday, February 25 at 17:00 ET. > The agenda for the Working Group is due by Thursday, March 13 at 12:00 ET, > please submit the agenda to: agenda@ietf.org. > > 1. ALL scheduling requests must be sent to: agenda@ietf.org with a copy to > the appropriate Area Director(s). > > 2. BOFs will not be scheduled unless the Area Director(s) approved request > is accompanied by a BOF FULL NAME AND ACRONYM, AREA, CHAIRS NAME(s) (given > together with e-mail address(es)), AN AGENDA AND FULL DESCRIPTION. > (Please read the BOF Procedure at ftp://ftp.ietf.org/ietf/1bof-procedures.txt > before requesting a slot for a BOF.) > > 3. WORKING GROUPs will be allowed a maximum of TWO slots (second slot has to be > approved by AD). If your WG will need more, please let us know. > Additional slots will be available after agenda scheduling has closed > (February 25 at 17:00 ET) and with approval from the AREA DIRECTOR(s) > if there is any possibility to do this. Should you need some > information for your WG session scheduling send us questions or visit the IETF > Working Group guidelines at http://www.ietf.org/rfc/rfc2418.txt. > > 4. You MUST provide the following information before the meeting will be scheduled: > a. Working Group or BOF full name with acronym in brackets: > b. AREA under which Working Group or BOF appears: > c. CONFLICTS you wish to avoid, please be as specific as possible: > d. Expected Attendance (figures from the 55th IETF are at the end of this message): > e. Special requests (i.e. multicast): > f. Number of slots: > g. Length of slot: > - 1 hour > - 2 hours > - 2 1/2 hours > > ================================================= > > For your convenience please find here the list of the AREA Directors with > their e-mail addresses: > > IETF Chair > Harald Alvestrand > > Applications Area (app) > Patrik Faltstrom > Ned Freed > > Internet Area (int) > Thomas Narten > Erik Nordmark > > Operations & Management Area (ops) > Randy Bush > Bert Wijnen > > Routing Area (rtg) > Bill Fenner > Alex Zinin > > Security Area (sec) > Jeffrey Schiller > Steve Bellovin > > Sub-IP Area (sub) > Scott Bradner > Bert Wijnen > > Transport Area (tsv) > Scott Bradner > Allison Mankin > > ================================================= > > Figures from the 55th IETF, Atlanta, GA > aaa 127 > adslmib 10 > apparea 146 > atommib 10 > avt 141 > bmwg 21 > calsch 25 > ccamp 158 > crisp 39 > dccp 93 > dhc 112 > dnsext 167 > dnsop 153 > eap 199 > entmib 24 > enum 78 > fax+vpim 23 > forces 70 > geopriv 44 > gsec 67 > gsmp 34 > idr 179 > idwg 33 > ieprep 128 > imapext 14 > impp 77 > inch 37 > ipcdn 22 > ipfix 49 > ipo 66 > ipoib 21 > ippm 74 > ipr 118 > ips 96 > ipsec 222 > ipseckey 118 > ipsp 88 > iptel 103 > krb-wg 63 > l2tpext 27 > ldapbis 33 > ldup 31 > lemonade 85 > magma 119 > manet 167 > mboned 101 > midcom 149 > mmusic 88 > mobileip 192 > mpls 207 > msec 96 > nemo 186 > nfsv4 17 > nomcom 44 > nsis 276 > opes 59 > ospf 76 > pana 246 > pim 78 > pkix 97 > ppvpn 211 > provreg 46 > psamp 61 > ptomaine 84 > pwe3 156 > rddp 59 > rmonmib 35 > rmt 48 > rohc 34 > rpsec 150 > rserpool 24 > rtgarea 118 > saag 163 > sacred 23 > seamoby 84 > secsh 36 > send 64 > simple 139 > sip 161 > sipping 220 > smime 38 > sming 35 > speechsc 47 > spirits 22 > sub-ip 88 > syslog 40 > tewg 115 > tls 61 > trade 10 > trigtran 149 > tsvwg 203 > udlr 33 > v6ops 261 > webdav 29 > xmpp 125 > zerouter 223 > > > > > > > From owner-disman@dorothy.bmc.com Fri Jan 10 14:44:07 2003 Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13985 for ; Fri, 10 Jan 2003 14:44:06 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id h0AJiPp10453; Fri, 10 Jan 2003 13:44:25 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA20006 for disman-list; Fri, 10 Jan 2003 11:43:02 -0800 (PST) Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id LAA19998; Fri, 10 Jan 2003 11:42:54 -0800 (PST) Received: from mx-us-hou-1-int.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id h0AJg2B13716; Fri, 10 Jan 2003 13:42:02 -0600 (CST) Received: from sj-msg-core-3.cisco.com (unknown [171.70.157.152]) by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 5D8C520F15F; Fri, 10 Jan 2003 19:38:37 -0600 (CST) Received: from niraj-w2k3.cisco.com (dhcp-171-71-137-59.cisco.com [171.71.137.59]) by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id h0AJggjT013291; Fri, 10 Jan 2003 11:42:42 -0800 (PST) Message-Id: <4.3.2.7.2.20030110112704.05794e10@mira-linc3-1.cisco.com> X-Sender: niraj@mira-linc3-1.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 10 Jan 2003 11:43:16 -0800 To: Randy Presuhn , disman@dorothy.bmc.com From: Niraj Gopal Subject: Re: Disman in San Francisco? In-Reply-To: <200301100203.SAA16118@dorothy.bmc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by dorothy.bmc.com id LAA19999 Sender: owner-disman@dorothy.bmc.com Precedence: bulk List-Id: IETF disman Working Group mailing list Content-Transfer-Encoding: 8bit Hi, >It's time to start thinking about whether a disman meeting >would be necessary in San Francisco. Since we've completed >all our current milestones, and no one has proposed new >ones, it seems to me that no meeting will be necessary. >Other thoughts? I did a presentation on a MIB to track modifications in the data of MIB tables implemented on an agent at Yokohama meeting. I recently submitted a newer version of this draft addressing the comments I received on this mailing list and at the Yokohama meeting and is available at: http://www.ietf.org/internet-drafts/draft-niraj-tmt-mib-01.txt Can I propose this to be taken up as a new disman WG item? What does the working group this about it? Thanks&Regards, -Niraj > ------------------------------------------------------ > Randy Presuhn BMC Software, Inc. SJC-1.3141 > randy_presuhn@bmc.com 2141 North First Street > Tel: +1 408 546-1006 San José, California 95131 USA > ------------------------------------------------------ > My opinions and BMC's are independent variables. > ------------------------------------------------------ > > > From owner-wgchairs@ietf.org Tue Jan 7 13:18:49 PST 2003 > > Message-Id: <200301071554.KAA18973@ietf.org> > > To: wgchairs@ietf.org, bofchairs@ietf.org > > From: agenda@ietf.org > > Cc: iesg@ietf.org, dinaras@ietf.org > > Subject: 56th IETF WG/BOF Scheduling > > Date: Tue, 07 Jan 2003 10:54:00 -0500 > > > > 56th IETF in San Francisco, CA > > Meeting Dates: March 16-21, 2003 > > > > We will be taking scheduling requests for ALL Working Groups and BOFs > starting today. > > The cut-off for requesting a slot is Tuesday, February 25 at 17:00 ET. > > The agenda for the Working Group is due by Thursday, March 13 at 12:00 ET, > > please submit the agenda to: agenda@ietf.org. > > > > 1. ALL scheduling requests must be sent to: agenda@ietf.org with a copy to > > the appropriate Area Director(s). > > > > 2. BOFs will not be scheduled unless the Area Director(s) approved request > > is accompanied by a BOF FULL NAME AND ACRONYM, AREA, CHAIRS NAME(s) (given > > together with e-mail address(es)), AN AGENDA AND FULL DESCRIPTION. > > (Please read the BOF Procedure at > ftp://ftp.ietf.org/ietf/1bof-procedures.txt > > before requesting a slot for a BOF.) > > > > 3. WORKING GROUPs will be allowed a maximum of TWO slots (second slot > has to be > > approved by AD). If your WG will need more, please let us know. > > Additional slots will be available after agenda scheduling has closed > > (February 25 at 17:00 ET) and with approval from the AREA DIRECTOR(s) > > if there is any possibility to do this. Should you need some > > information for your WG session scheduling send us questions or visit > the IETF > > Working Group guidelines at http://www.ietf.org/rfc/rfc2418.txt. > > > > 4. You MUST provide the following information before the meeting will > be scheduled: > > a. Working Group or BOF full name with acronym in brackets: > > b. AREA under which Working Group or BOF appears: > > c. CONFLICTS you wish to avoid, please be as specific as possible: > > d. Expected Attendance (figures from the 55th IETF are at the end of > this message): > > e. Special requests (i.e. multicast): > > f. Number of slots: > > g. Length of slot: > > - 1 hour > > - 2 hours > > - 2 1/2 hours > > > > ================================================= > > > > For your convenience please find here the list of the AREA Directors with > > their e-mail addresses: > > > > IETF Chair > > Harald Alvestrand > > > > Applications Area (app) > > Patrik Faltstrom > > Ned Freed > > > > Internet Area (int) > > Thomas Narten > > Erik Nordmark > > > > Operations & Management Area (ops) > > Randy Bush > > Bert Wijnen > > > > Routing Area (rtg) > > Bill Fenner > > Alex Zinin > > > > Security Area (sec) > > Jeffrey Schiller > > Steve Bellovin > > > > Sub-IP Area (sub) > > Scott Bradner > > Bert Wijnen > > > > Transport Area (tsv) > > Scott Bradner > > Allison Mankin > > > > ================================================= > > > > Figures from the 55th IETF, Atlanta, GA > > aaa 127 > > adslmib 10 > > apparea 146 > > atommib 10 > > avt 141 > > bmwg 21 > > calsch 25 > > ccamp 158 > > crisp 39 > > dccp 93 > > dhc 112 > > dnsext 167 > > dnsop 153 > > eap 199 > > entmib 24 > > enum 78 > > fax+vpim 23 > > forces 70 > > geopriv 44 > > gsec 67 > > gsmp 34 > > idr 179 > > idwg 33 > > ieprep 128 > > imapext 14 > > impp 77 > > inch 37 > > ipcdn 22 > > ipfix 49 > > ipo 66 > > ipoib 21 > > ippm 74 > > ipr 118 > > ips 96 > > ipsec 222 > > ipseckey 118 > > ipsp 88 > > iptel 103 > > krb-wg 63 > > l2tpext 27 > > ldapbis 33 > > ldup 31 > > lemonade 85 > > magma 119 > > manet 167 > > mboned 101 > > midcom 149 > > mmusic 88 > > mobileip 192 > > mpls 207 > > msec 96 > > nemo 186 > > nfsv4 17 > > nomcom 44 > > nsis 276 > > opes 59 > > ospf 76 > > pana 246 > > pim 78 > > pkix 97 > > ppvpn 211 > > provreg 46 > > psamp 61 > > ptomaine 84 > > pwe3 156 > > rddp 59 > > rmonmib 35 > > rmt 48 > > rohc 34 > > rpsec 150 > > rserpool 24 > > rtgarea 118 > > saag 163 > > sacred 23 > > seamoby 84 > > secsh 36 > > send 64 > > simple 139 > > sip 161 > > sipping 220 > > smime 38 > > sming 35 > > speechsc 47 > > spirits 22 > > sub-ip 88 > > syslog 40 > > tewg 115 > > tls 61 > > trade 10 > > trigtran 149 > > tsvwg 203 > > udlr 33 > > v6ops 261 > > webdav 29 > > xmpp 125 > > zerouter 223 > > > > > > > > > > > > > > From mailnull@www1.ietf.org Tue Jan 14 15:23:02 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10337 for ; Tue, 14 Jan 2003 15:23:02 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0EKbKF29761 for disman-archive@odin.ietf.org; Tue, 14 Jan 2003 15:37:20 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EKbKJ29758 for ; Tue, 14 Jan 2003 15:37:20 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10299 for ; Tue, 14 Jan 2003 15:22:31 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EKbJJ29737 for ; Tue, 14 Jan 2003 15:37:19 -0500 Date: Tue, 14 Jan 2003 15:37:19 -0500 Message-ID: <20030114203719.29727.4445.Mailman@www1.ietf.org> Subject: Welcome to the "Disman" mailing list From: disman-request@ietf.org To: disman-web-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: disman-admin@ietf.org Errors-To: disman-admin@ietf.org X-BeenThere: disman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Distributed Management List-Post: List-Help: List-Subscribe: , Welcome to the Disman@ietf.org mailing list! To post to this list, send your email to: disman@ietf.org General information about the mailing list is at: https://www1.ietf.org/mailman/listinfo/disman ************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. ************************************************************************** If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: https://www1.ietf.org/mailman/options/disman/disman-web-archive%40ietf.org You can also make such adjustments via email by sending a message to: Disman-request@ietf.org with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is: carehu If you forget your password, don't worry, you will receive a monthly reminder telling you what all your ietf.org mailing list passwords are, and how to unsubscribe or change your options. There is also a button on your options page that will email your current password to you. You may also have your password mailed to you automatically off of the Web page noted above. From mailnull@www1.ietf.org Tue Jan 14 15:26:45 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10443 for ; Tue, 14 Jan 2003 15:26:45 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0EKf2B30277 for disman-archive@odin.ietf.org; Tue, 14 Jan 2003 15:41:02 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EKf2J30265 for ; Tue, 14 Jan 2003 15:41:02 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10434 for ; Tue, 14 Jan 2003 15:26:13 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EKf1J30259 for ; Tue, 14 Jan 2003 15:41:01 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EKeGJ30206 for ; Tue, 14 Jan 2003 15:40:16 -0500 Received: from cnri.reston.va.us (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10381 for ; Tue, 14 Jan 2003 15:25:28 -0500 (EST) Received: from hubris.cnri.reston.va.us (cnri-7-65.cnri.reston.va.us [132.151.7.65]) by cnri.reston.va.us (8.11.6+Sun/8.11.3) with ESMTP id h0EKSn824767 for ; Tue, 14 Jan 2003 15:28:49 -0500 (EST) Message-Id: <5.0.0.25.2.20030114152652.00ae0e98@mailbox.cnri.reston.va.us> X-Sender: gcunning@mailbox.cnri.reston.va.us X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Tue, 14 Jan 2003 15:27:37 -0500 To: disman@ietf.org From: Greg Cunningham Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Disman] Test Message #1 Sender: disman-admin@ietf.org Errors-To: disman-admin@ietf.org X-BeenThere: disman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Distributed Management List-Post: List-Help: List-Subscribe: , The disman WG mailing list is being moved to the ietf. This is a test message to check the archiv _______________________________________________ Disman mailing list Disman@ietf.org https://www1.ietf.org/mailman/listinfo/disman From mailnull@www1.ietf.org Wed Jan 15 19:08:55 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15430 for ; Wed, 15 Jan 2003 19:08:55 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0G0Njj24230 for disman-archive@odin.ietf.org; Wed, 15 Jan 2003 19:23:45 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G0NjJ24227 for ; Wed, 15 Jan 2003 19:23:45 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15423 for ; Wed, 15 Jan 2003 19:08:24 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G0MrJ24192; Wed, 15 Jan 2003 19:22:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G0LhJ24136 for ; Wed, 15 Jan 2003 19:21:43 -0500 Received: from babbler.bmc.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15388 for ; Wed, 15 Jan 2003 19:06:22 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id h0G09xd26450 for ; Wed, 15 Jan 2003 18:09:59 -0600 (CST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA22448 for disman@ietf.org; Wed, 15 Jan 2003 16:09:06 -0800 (PST) From: Randy Presuhn Message-Id: <200301160009.QAA22448@dorothy.bmc.com> To: disman@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Disman] Disman list mas moved! Sender: disman-admin@ietf.org Errors-To: disman-admin@ietf.org X-BeenThere: disman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Distributed Management List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 15 Jan 2003 16:09:06 -0800 (PST) Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi - If you receive this message, you have been successfully subscribed to the *new* Disman WG mailing list, disman@ietf.org. The old list will soon be deactivated. I have *not* moved the "posters" file. If you routinely post from addresses other than the one where you received this message, here's what you should do: 1) go to https://www1.ietf.org/mailman/listinfo/disman 2) follow the subscription process to subscribe the "poster" address you'd like to use 3) after you've replied to the email confirmation, return to https://www1.ietf.org/mailman/listinfo/disman and select "edit options" for your posting address 4) Find the "Disable mail delivery" option, turn it on, and then click "Submit My Changes". I will send a message to the old list to pick up any stragglers, and update the WG home page with the new list information. ------------------------------------------------------ Randy Presuhn BMC Software, Inc. SJC-1.3141 randy_presuhn@bmc.com 2141 North First Street Tel: +1 408 546-1006 San José, California 95131 USA ------------------------------------------------------ My opinions and BMC's are independent variables. ------------------------------------------------------ From disman-admin@ietf.org Wed Jan 15 19:09:07 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15443 for ; Wed, 15 Jan 2003 19:09:06 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G0MrJ24192; Wed, 15 Jan 2003 19:22:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G0LhJ24136 for ; Wed, 15 Jan 2003 19:21:43 -0500 Received: from babbler.bmc.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15388 for ; Wed, 15 Jan 2003 19:06:22 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id h0G09xd26450 for ; Wed, 15 Jan 2003 18:09:59 -0600 (CST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA22448 for disman@ietf.org; Wed, 15 Jan 2003 16:09:06 -0800 (PST) From: Randy Presuhn Message-Id: <200301160009.QAA22448@dorothy.bmc.com> To: disman@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Disman] Disman list mas moved! Sender: disman-admin@ietf.org Errors-To: disman-admin@ietf.org X-BeenThere: disman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Distributed Management List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 15 Jan 2003 16:09:06 -0800 (PST) Content-Transfer-Encoding: 7bit Hi - If you receive this message, you have been successfully subscribed to the *new* Disman WG mailing list, disman@ietf.org. The old list will soon be deactivated. I have *not* moved the "posters" file. If you routinely post from addresses other than the one where you received this message, here's what you should do: 1) go to https://www1.ietf.org/mailman/listinfo/disman 2) follow the subscription process to subscribe the "poster" address you'd like to use 3) after you've replied to the email confirmation, return to https://www1.ietf.org/mailman/listinfo/disman and select "edit options" for your posting address 4) Find the "Disable mail delivery" option, turn it on, and then click "Submit My Changes". I will send a message to the old list to pick up any stragglers, and update the WG home page with the new list information. ------------------------------------------------------ Randy Presuhn BMC Software, Inc. SJC-1.3141 randy_presuhn@bmc.com 2141 North First Street Tel: +1 408 546-1006 San José, California 95131 USA ------------------------------------------------------ My opinions and BMC's are independent variables. ------------------------------------------------------ From owner-disman@dorothy.bmc.com Wed Jan 15 19:18:03 2003 Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15655 for ; Wed, 15 Jan 2003 19:18:02 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id h0G0GQN28408; Wed, 15 Jan 2003 18:16:26 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA22466 for disman-list; Wed, 15 Jan 2003 16:12:27 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA22459 for disman@dorothy.bmc.com; Wed, 15 Jan 2003 16:12:24 -0800 (PST) Date: Wed, 15 Jan 2003 16:12:24 -0800 (PST) From: Randy Presuhn Message-Id: <200301160012.QAA22459@dorothy.bmc.com> To: disman@dorothy.bmc.com Subject: Disman list is moving Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-disman@dorothy.bmc.com Precedence: bulk List-Id: IETF disman Working Group mailing list Content-Transfer-Encoding: 7bit Hi - If you don't receive a message "Disman list has moved!", please go to https://www1.ietf.org/mailman/listinfo/disman to subscribe to the new Disman WG mailing list. The old disman@dorothy.bmc.com list will be going down shortly. ------------------------------------------------------ Randy Presuhn BMC Software, Inc. SJC-1.3141 randy_presuhn@bmc.com 2141 North First Street Tel: +1 408 546-1006 San José, California 95131 USA ------------------------------------------------------ My opinions and BMC's are independent variables. ------------------------------------------------------