From Ted.Hardie at nominum.com Wed Jan 2 19:46:27 2002 From: Ted.Hardie at nominum.com (Ted Hardie) Date: Wed, 2 Jan 2002 11:46:27 -0800 Subject: New version of longest match draft Message-ID: <20020102114627.A38371@shell.nominum.com> Hi, Below is the URL for a new version of the "Bounding Longest Match Considered" draft. It has benefited greatly from the addition of a new co-author, Russ White. Discussion to the authors or the list would be appreciated. regards, Ted Hardie http://www.ietf.org/internet-drafts/draft-hardie-bounded-longest-match-02.txt From mknopper at cisco.com Mon Jan 28 20:38:14 2002 From: mknopper at cisco.com (Mark Knopper) Date: Mon, 28 Jan 2002 15:38:14 -0500 Subject: ptomaine wg In-Reply-To: <200201101618.LAA17713@ietf.org> References: <200201101618.LAA17713@ietf.org> Message-ID: Hi. The PTOMAINE WG should have a session at Minneapolis, as follows: > a. Working Group or BOF full name with acronym in brackets: Prefix Taxonomy Ongoing Measurement & Inter Network Experiment [ptomaine] > b. AREA under which Working Group or BOF appears: Operations and Management Area > c. CONFLICTS you wish to avoid, please be as specific as possible: Routing protocol WGs: IDR, ISIS, OSPF, MSDP > d. Expected Attendance (figures from the 51st IETF are at the end >of this message): 76 people (precisely ;-) > e. Special requests (i.e. multicast): > f. Number of slots: 1 > g. Length of slot: > - 1 hour > - 2 hours > - 2 1/2 hours 1 hour Thanks, Mark At 11:18 AM -0500 1/10/02, agenda at ietf.org wrote: >53rd IETF in Minneapolis, Minnesota >Meeting Dates: March 17-22, 2002 > >We will be taking scheduling requests for ALL Working Groups and >BOFs starting today. >The cut-off for requesting a slot is Friday, February 22 at 17:00 ET. >The agenda for the Working Group is due by Wednesday, March 13 at 12:00 ET, >please submit the agenda to: agenda at ietf.org. > >1. ALL scheduling requests must be sent to: agenda at 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 22 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 51st 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) >Erik Nordmark >Thomas Narten > >Operations & Management Area (ops) >Randy Bush >Bert Wijnen > >Routing Area (rtg) >Randy Bush >Bill Fenner > >Security Area (sec) >Jeff Schiller >Marcus Leech > >Transport Area (tsv) >Scott Bradner >Allison Mankin > >User Services Area (usv) >April Marine > >Temporary Sub-IP Area (sub) >Scott Bradner >Bert Wijnen > >================================================= > >Figures from 52nd IETF > >aaaarch 53 >adslmib 8 >apparea 185 >atommib 79 >avt 137 >bmwg 46 >bridge 9 >calsch 23 >ccamp 190 >cdi 87 >dcp 182 >dhc 37 >disman 29 >dnsext 135 >dnsmeas 110 >dnsop 115 >entmib 15 >fax 16 >forces 77 >geopriv 136 >gsec 83 >gsmp 41 >hubmib 17 >hubmib&atommib 10 >idn 117 >idr 105 >idrm 102 >idwg 22 >ieprep 116 >imapext 27 >inch 50 >intloc 116 >ipcdn 29 >ipfix 96 >ipngwg 364 >ipo 111 >ipoib 60 >ippm 96 >ips 172 >ipsec 400 >ipsp 93 >iptel 200 >kink 58 >krb-wg 44 >l2tpext 68 >ldapbis 34 >ldup 25 >magma 98 >manet 107 >mboned 76 >megaco 45 >midcom 159 >mmusic 148 >mobileip 247 >mpls 250 >mplsoam 192 >msec 88 >multi6 >ndmp 54 >nfsv4 19 >ngtrans 191 >nmsec 108 >nntpext 10 >nsis 162 >opes 126 >ops-nm 102 >pana 94 >pilc 69 >pim 76 >pkix 113 >policy 28 >ppvpn 291 >provreg 46 >ptomaine 76 >pwe3 174 >rap 63 >rmonmib 41 >rmt 170 >rohc 54 >roi 129 >rrg 144 >rserpool 30 >saag 177 >sacred 73 >seamoby 82 >secsh 75 >simple 149 >sip 264 >sipping 261 >smime 35 >sming 53 >snmpv3 70 >spirits 18 >subarea 279 >tewg 188 >trade 12 >tsvwg 168 >udlr 37 >vpim 23 >vrrp 53 >webdav 14 -- Cisco Systems, Inc. +1 734-302-4125 phone 100 S. Main, Suite 200 +1 734-302-4170 fax Ann Arbor, MI 48104 USA