Re: [I2nsf] Conflict sessions to avoid for I2NSF in Buenos Aires ( IETF 95) - Working Group/BOF/IRTF Scheduling
Takeshi Takahashi <tt2@rc5.so-net.ne.jp> Wed, 06 January 2016 03:09 UTC
Return-Path: <tt2@rc5.so-net.ne.jp>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 255CD1A8A63 for <i2nsf@ietfa.amsl.com>; Tue, 5 Jan 2016 19:09:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: YES
X-Spam-Score: 5.563
X-Spam-Level: *****
X-Spam-Status: Yes, score=5.563 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HELO_EQ_NE_JP=1.244, HOST_EQ_JP=1.265, HOST_EQ_NE_JP=2.599, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vN0MSglVCILb for <i2nsf@ietfa.amsl.com>; Tue, 5 Jan 2016 19:09:49 -0800 (PST)
Received: from ms-omx02.so-net.ne.jp (ms-omx02.so-net.ne.jp [202.238.84.152]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CAC51A8A6B for <i2nsf@ietf.org>; Tue, 5 Jan 2016 19:09:47 -0800 (PST)
Received: from ms-omx12.so-net.ne.jp (ms-omx12.plus.so-net.ne.jp [10.240.84.162]) by ms-omx02.plus.so-net.ne.jp with ESMTP id u0639jba005966 for <i2nsf@ietf.org>; Wed, 6 Jan 2016 12:09:45 +0900
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rc5.so-net.ne.jp; s=sn2016; t=1452049785; bh=66UJ/dWF32zmoH7jZSyMCwpBY7gEe9g/AInyiiqv1qM=; h=In-Reply-To:References:Date:Subject:From:To; b=Jv7QMfj7tkhERFgqT/VdT8+ZA4LpSq5PJB+uoPOeEuQ+iVJyskoRDU/Jh0yVJCunM Kh4tEjuFZfvzNGIG5t+klk/G9k+rCDnIKEJfrdFF8CeUHcalWHQStSE1MAISOnQg04 0Q87X7Gva8y0QZxq1fV3ypKITIXhOX9y3kC1k34J1b3PJ8qdiERhM3v74r9H/gApdW 5DzTqXNYp/S9vEGZXQT2oL7rvaOU3Gg4RSafj3t+BDl1D4C4hToLi3KJp8Vy+bI80u Iqij1rdiEsO7yZhCGQs4SuPdVt4DV9mJoyAXBfjOYDMIZX3K891mxv2ixWDZAehrzn 60FGUSYx7oPfA==
Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com [209.85.220.43]) (authenticated) by ms-omx12.plus.so-net.ne.jp with ESMTP id u0639itR016043 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)) for <i2nsf@ietf.org>; Wed, 6 Jan 2016 12:09:45 +0900
Received: by mail-pa0-f43.google.com with SMTP id uo6so206442332pac.1 for <i2nsf@ietf.org>; Tue, 05 Jan 2016 19:09:45 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.66.255.70 with SMTP id ao6mr78881444pad.64.1452049784055; Tue, 05 Jan 2016 19:09:44 -0800 (PST)
Received: by 10.66.229.73 with HTTP; Tue, 5 Jan 2016 19:09:43 -0800 (PST)
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F657DB8A60@dfweml701-chm>
References: <4A95BA014132FF49AE685FAB4B9F17F657DB8685@dfweml701-chm> <BY2PR0301MB0693721DDD3B2BEAE7CDA0AFD6F30@BY2PR0301MB0693.namprd03.prod.outlook.com> <15A587F0-0925-48DB-8B09-0F49AA605053@gmail.com> <022901d14811$4b5b65e0$e21231a0$@ndzh.com> <4A95BA014132FF49AE685FAB4B9F17F657DB8A60@dfweml701-chm>
Date: Wed, 06 Jan 2016 12:09:43 +0900
X-Gmail-Original-Message-ID: <CAMA4c9XLVcsPXWeSiQ7qq=kfk=m935hnOJ2qcEr4aFXE4T=_AQ@mail.gmail.com>
Message-ID: <CAMA4c9XLVcsPXWeSiQ7qq=kfk=m935hnOJ2qcEr4aFXE4T=_AQ@mail.gmail.com>
From: Takeshi Takahashi <tt2@rc5.so-net.ne.jp>
To: i2nsf@ietf.org, linda.dunbar@huawei.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2nsf/WAs2khfWq_736T4AIpr071h7as4>
Subject: Re: [I2nsf] Conflict sessions to avoid for I2NSF in Buenos Aires ( IETF 95) - Working Group/BOF/IRTF Scheduling
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf/>
List-Post: <mailto:i2nsf@ietf.org>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2016 03:09:53 -0000
Hi Linda, I would appreciate if you could avoid MILE as well. regards, Take 2016-01-06 10:57 GMT+09:00 Linda Dunbar <linda.dunbar@huawei.com>: > Sue, Kathleen, LuYuan, etc > > > > Thanks for the note. Here are the updated sessions to avoid: > > > > Routing area: I2RS, SFC, NVO3, IDR, TRILL, RTGarea, > > OpsARea: SUPA, NFVrg, L2SM, NETMOD, NETconf, > > Security Area: DOTS, SACM, SAAG > > > > > > Linda > > > > From: Susan Hares [mailto:shares@ndzh.com] > Sent: Tuesday, January 05, 2016 5:32 PM > To: 'Kathleen Moriarty'; 'Luyuan Fang' > Cc: i2nsf@ietf.org; Linda Dunbar > Subject: RE: [I2nsf] Conflict sessions to avoid for I2NSF in Buenos Aires ( > IETF 95) - Working Group/BOF/IRTF Scheduling > > > > Please avoid IDR. > > > > Thank you, > > > > Sue Hares (co-chair) > > > > -----Original Message----- > From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Kathleen Moriarty > Sent: Tuesday, January 05, 2016 5:53 PM > To: Luyuan Fang > Cc: i2nsf@ietf.org; Linda Dunbar > Subject: Re: [I2nsf] Conflict sessions to avoid for I2NSF in Buenos Aires ( > IETF 95) - Working Group/BOF/IRTF Scheduling > > > > I think SACM would be good to avoid as well. > > > > Thanks, > > Kathleen > > > > Sent from my iPhone > > > >> On Jan 5, 2016, at 5:28 PM, Luyuan Fang <lufang@microsoft.com> wrote: > >> > >> Also avoid DOTS. > >> > >> Happy New Year! > >> Luyuan > >> > >> -----Original Message----- > >> From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Linda Dunbar > >> Sent: Tuesday, January 5, 2016 1:55 PM > >> To: i2nsf@ietf.org > >> Subject: [I2nsf] Conflict sessions to avoid for I2NSF in Buenos Aires ( >> IETF 95) - Working Group/BOF/IRTF Scheduling > >> > >> Happy New Year to all the I2NSF participants. > >> > >> In order to prepare for I2NSF WG session at IETF95- Buenos Aires, we need >> to list down the sessions that I2NSF session should avoid being parallel. > >> Here are some sessions on top of my head that I2NSF should avoid: I2RS, >> SFC, NVO3, SUPA, NFVrg, SAAG, RTGarea, NETMOD, NETconf, and TRILL. > >> > >> Please let us know other sessions I2NSF should avoid (even though it might >> not be possible to avoid all the conflicts). > >> > >> Cheers, > >> > >> Linda & Adrian. > >> > >> > >> > >> > >> > >> -----Original Message----- > >> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of IETF Agenda > >> Sent: Monday, January 04, 2016 3:10 PM > >> To: Working Group Chairs > >> Subject: IETF 95 - Working Group/BOF/IRTF Scheduling > >> > >> ----------------------------------------------------------------- > >> IETF 95 – Buenos Aires, Argentina > >> Meeting Dates: April 3-8, 2016 > >> ----------------------------------------------------------------- > >> > >> We are accepting scheduling requests for all Working Groups, BOFs, and >> Research Groups starting today. > >> > >> The milestones and deadlines for scheduling-related activities are as >> follows: > >> Cut-off dates are subject to change. > >> > >> • 2016-01-04 (Monday): Working Group and BOF scheduling begins. To >> request a Working Group session, use the IETF Meeting Session Request Tool. > >> • 2016-02-19 (Friday): Cut-off date for requests to schedule Working >> Group meetings at UTC 23:59. To request a Working Group session, use the >> IETF Meeting Session Request Tool. > >> • 2016-02-19 (Friday): Cut-off date for BOF proposal requests to Area >> Directors at UTC 23:59. To request a BOF, please see instructions on >> Requesting a BOF. > >> • 2016-02-26 (Friday): Cut-off date for Area Directors to approve BOFs >> at UTC 23:59. > >> • 2016-03-04 (Friday): Preliminary agenda published for comment. > >> • 2016-03-09 (Wednesday): Cut-off date for requests to reschedule >> Working Group and BOF meetings UTC 23:59. > >> • 2016-03-11 (Friday): Final agenda to be published. > >> • 2016-03-21 (Monday): Draft Working Group agendas due by UTC 23:59, >> upload using IETF Meeting Materials Management Tool. > >> • 2016-03-28 (Monday): Revised Working Group agendas due by UTC 23:59, >> upload using IETF Meeting Materials Management Tool. > >> • 2016-04-29 (Friday): Proceedings submission cutoff date by UTC 23:59, >> upload using IETF Meeting Materials Management Tool. > >> • 2016-05-27 (Monday): Proceedings submission corrections cutoff date >> by UTC 23:59, upload using IETF Meeting Materials Management Tool. > >> > >> > >> =============================================================== > >> Comprehensive information on requesting meeting sessions is below: > >> > >> 1. Requests to schedule Working Group sessions should be submitted using >> the "IETF Meeting Session Request Tool," a Web-based tool for submitting all >> of the information required by the Secretariat to schedule your sessions. >> The URL for the tool is: > >> >> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fdatatracker.ietf.org%2fsecr%2fsreq%2f&data=01%7c01%7clufang%40microsoft.com%7c6e1d1c8df494458b5f0408d3161ae157%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ca%2fTGnII8oE8TmcLlC7Jr978pbFiXnG7Ur573FoemdM%3d > >> > >> Instructions for using the tool are available at: > >> >> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.ietf.org%2fwg%2frequest-tool-instructions.html&data=01%7c01%7clufang%40microsoft.com%7c6e1d1c8df494458b5f0408d3161ae157%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=SzKoMGGxlO56Vz7yZdpmeTfCtmqwSUf8KyG8AwqoM1M%3d > >> > >> If you require an account on this tool, or assistance in using it, then >> please send a message to ietf-action@ietf.org. If you are unable to use the >> tool, then you may send your request via e-mail to agenda@ietf.org, with a >> copy to the appropriate Area Director(s). > >> > >> Requests to schedule BOF sessions must be sent to agenda@ietf.org with a >> copy to the appropriate Area Director(s). > >> > >> When submitting a Working Group or BOF session request by e-mail, please >> include the Working Group or BOF acronym in the Subject line. > >> > >> 2. BOFs will NOT be scheduled unless the Area Director approves the BOF. >> The proponents behind a BOF need to contact a relevant Area Director, >> preferably well in advance of the BOF approval deadline date. The AD needs >> to have the full name of the BOF, its acronym, suggested names of chairs, an >> agenda, full description of the BOF and the information covered in item 4. >> Please read RFC 5434 for instructions on how to drive a successful BOF >> effort. > >> > >> 3. A Working Group may request either one or two sessions. If your >> Working Group requires more than two sessions, then your request must be >> approved by an Area Director. Additional sessions will be assigned, based >> on availability, after Wednesday, March 9th, 2016, the cut-off date for >> requests to reschedule a session. > >> > >> 4. You MUST provide the following information before a Working Group or >> BOF session 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: > >> e. Special requests: > >> f. Number of sessions: > >> g. Length of session: 1 hour, 1.5 hours, 2 hours, 2.5 hours > >> > >> For more information on scheduling Working Group and BOF sessions, please >> refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and Procedures" >> (https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.ietf.org%2frfc%2frfc2418.txt&data=01%7c01%7clufang%40microsoft.com%7c6e1d1c8df494458b5f0408d3161ae157%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=35y6cXFo5DbKej7VoIk9D%2beB6h9i1PWV2wdHdGMndLs%3d) > >> > >> =============================================================== > >> > >> Submitting Session Agendas > >> > >> > >> Please submit the agendas for your Working Group sessions as early as >> possible using the "IETF Meeting Materials Management Tool," a Web-based >> tool for making your meeting agenda, minutes, and presentation slides >> available to the community before, during, and after an IETF meeting. If >> you are a BOF chair, then you may use the tool to submit a revised agenda as >> well as other materials for your BOF once the BOF has been approved. > >> > >> The URL for the tool is: > >> >> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fdatatracker.ietf.org%2fsecr%2fproceedings%2f&data=01%7c01%7clufang%40microsoft.com%7c6e1d1c8df494458b5f0408d3161ae157%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=FlyIB3rZ9Ot%2bEp4DO1CVeM8aNNBPYMtzGieTl4kynFk%3d > >> > >> Additional information about this tool is available at: > >> >> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.ietf.org%2fwg%2fmeeting-materials.html&data=01%7c01%7clufang%40microsoft.com%7c6e1d1c8df494458b5f0408d3161ae157%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=pGP%2bv73X%2bAhnuGXvHl58VkpN%2benfWPrYCiKqVewEMLw%3d > >> > >> Agendas submitted via the tool will be available to the public on the >> "IETF Meeting Materials" webpage as soon as they are submitted. > >> > >> The URL for the "IETF 95 Meeting Materials" Web page is: > >> >> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fdatatracker.ietf.org%2fmeeting%2f95%2fmaterials.html&data=01%7c01%7clufang%40microsoft.com%7c6e1d1c8df494458b5f0408d3161ae157%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=UQoWYJQe2SIC511bRbidC%2bI6ghuobgaZECawIT0llC0%3d > >> > >> If you are a Working Group chair, then you already have accounts on the >> "IETF Meeting Session Request Tool" and the "IETF Meeting Materials >> Management Tool." The same User ID and password will work for both tools. >> If you are a BOF chair who is not also a Working Group chair, then you will >> be given an account on the "IETF Meeting Materials Management Tool" when >> your BOF has been approved. If you require assistance in using either tool, >> or wish to report a bug, then please send a message to: >> ietf-action@ietf.org. > >> > >> =============================================================== > >> For your convenience please find a list of the IETF Area Directors with >> their e-mail addresses below: > >> > >> IETF Chair > >> Jari Arkko <jari.arkko@piuha.net> > >> > >> Applications and Real-Time Area (art) > >> Ben Campbell <ben@nostrum.com> > >> Alissa Cooper <alissa@cooperw.in> > >> Barry Leiba <barryleiba@computer.org> > >> > >> Internet Area (int) > >> Brian Haberman <brian@innovationslab.net> Terry Manderson >> <terry.manderson@icann.org> > >> > >> Operations & Management Area (ops) > >> Benoit Claise <bclaise@cisco.com> > >> Joel Jaeggli <joelja@bogus.com> > >> > >> Routing Area (rtg) > >> Alia Atlas <akatlas+iesg@gmail.com> > >> Deborah Brungard <dbrungard@att.com> > >> Alvaro Retana <aretana@cisco.com> > >> > >> Security Area (sec) > >> Stephen Farrell <stephen.farrell@cs.tcd.ie> Kathleen Moriarty >> <Kathleen.Moriarty.ietf@gmail.com> > >> > >> Transport Area (tsv) > >> Spencer Dawkins <spencerdawkins.ietf@gmail.com> Martin Stiemerling >> <martin.stiemerling@neclab.eu> > >> > >> =========================================================== > >> IETF 94 Meeting Attendance Numbers > >> > >> 6lo – 82 > >> 6man - 102 > >> 6tisch – 42 > >> ace - 77 > >> acme - 67 > >> anima – 91 > >> anima (2nd session) - 53 > >> avtcore - 24 > >> avtext – 32 > >> bess – 68 > >> bfd - 58 > >> bier - 57 > >> bmwg – 31 > >> ccamp - 52 > >> cdni – 32 > >> cfrg - 96 > >> clue – 22 > >> core - 75 > >> core (2nd session) – 60 > >> cose - 50 > >> dbound – 42 > >> detnet (BoF) - 81 > >> dhc – 48 > >> dime - 19 > >> dispatch - 70 > >> dmm – 32 > >> dnsop - 109 > >> dnssd – 95 > >> dots - 116 > >> dprive – 138 > >> dtn – 41 > >> ecrit - 26 > >> eppext – 39 > >> grow - 43 > >> homenet – 117 > >> hopsrg (PRG) – 167 > >> hrpc - 97 > >> httpbis – 114 > >> i2nsf - 84 > >> i2rs – 69 > >> ice - 55 > >> icnrg (RG) - 69 > >> idr – 83 > >> intarea (AG) - 91 > >> ippm – 62 > >> irtfopen - 174 > >> isis – 33 > >> iss (BoF) - 95 > >> l3sm – 53 > >> lager - 36 > >> lime - 47 > >> lisp - 36 > >> lmap – 45 > >> mboned - 19 > >> mif - 55 > >> mile - 43 > >> mmusic - 46 > >> modern - 24 > >> mpls - 56 > >> mpls (2nd session) – 64 > >> mptcp - 67 > >> netconf - 69 > >> netmod – 78 > >> netmod (2nd session) – 84 > >> netvc – 63 > >> netvc (2nd session) - 49 > >> nfvrg – 118 > >> nmlrg - 112 > >> nmrg - 59 > >> ntp (combined with tictoc) - 28 > >> nvo3 – 111 > >> oauth – 69 > >> openpgp – 27 > >> opsawg/opsarea – 48 > >> ospf – 47 > >> pals – 33 > >> payload - 42 > >> pce – 71 > >> perc - 35 > >> pim - 28 > >> radext - 14 > >> rmcat – 55 > >> rmcat (2nd session) - 33 > >> roll - 32 > >> rtcweb - 75 > >> rtcweb (2nd session) - 80 > >> rtgarea - 95 > >> rtgwg – 99 > >> rtgwg (2nd session) - 73 > >> saag - 188 > >> sacm - 48 > >> sacm (2nd session) - 37 > >> sdnrg (RG) – 145 > >> sfc - 123 > >> sidr – 61 > >> sidr (2nd session) - 47 > >> softwire – 32 > >> spring – 94 > >> stir – 36 > >> supa (BoF) – 77 > >> t2trg (PRG) – did not return > >> taps - 54 > >> tcpinc - 111 > >> tcpm – 80 > >> teas - 76 > >> tictoc (combined with ntp) - 28 > >> tls – 100 > >> tls (2nd session) - 108 > >> tokbind - 48 > >> tram – 38 > >> trans - 43 > >> trill – 26 > >> trill (2nd session) - 9 > >> tsvwg - 99 > >> tsvwg (2nd session) - 93 > >> v6ops - 82 > >> v6ops – 75 > >> webpush – 75 > >> xrblock - 10 > >> > >> _______________________________________________ > >> I2nsf mailing list > >> I2nsf@ietf.org > >> >> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.ietf.org%2fmailman%2flistinfo%2fi2nsf%0a&data=01%7c01%7clufang%40microsoft.com%7c6e1d1c8df494458b5f0408d3161ae157%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=56gq9Z5mLw6jBPgrec%2bNfgsERzpGIha0eRL7%2bo2GGU8%3d > >> _______________________________________________ > >> I2nsf mailing list > >> I2nsf@ietf.org > >> https://www.ietf.org/mailman/listinfo/i2nsf > > > > _______________________________________________ > > I2nsf mailing list > > I2nsf@ietf.org > > https://www.ietf.org/mailman/listinfo/i2nsf > > > _______________________________________________ > I2nsf mailing list > I2nsf@ietf.org > https://www.ietf.org/mailman/listinfo/i2nsf > -- -- Takeshi Takahashi, Ph.D. +81 80 3490 2971 http://www.taketaka.com/
- [I2nsf] Conflict sessions to avoid for I2NSF in B… Linda Dunbar
- Re: [I2nsf] Conflict sessions to avoid for I2NSF … Luyuan Fang
- Re: [I2nsf] Conflict sessions to avoid for I2NSF … Kathleen Moriarty
- Re: [I2nsf] Conflict sessions to avoid for I2NSF … Luyuan Fang
- Re: [I2nsf] Conflict sessions to avoid for I2NSF … Susan Hares
- Re: [I2nsf] Conflict sessions to avoid for I2NSF … Linda Dunbar
- Re: [I2nsf] Conflict sessions to avoid for I2NSF … Takeshi Takahashi
- Re: [I2nsf] Conflict sessions to avoid for I2NSF … Robert Moskowitz