From adrian@olddog.co.uk Fri Oct 4 16:12:50 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 901EA21F9BF2 for ; Fri, 4 Oct 2013 16:12:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.524 X-Spam-Level: X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yyktS0D-iW8O for ; Fri, 4 Oct 2013 16:12:45 -0700 (PDT) Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 9974321F9BD8 for ; Fri, 4 Oct 2013 16:12:42 -0700 (PDT) Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r94NCfFQ013213 for ; Sat, 5 Oct 2013 00:12:41 +0100 Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r94NCekt013207 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Sat, 5 Oct 2013 00:12:40 +0100 From: "Adrian Farrel" To: References: <20131004173149.22991.14931.idtracker@ietfa.amsl.com> In-Reply-To: <20131004173149.22991.14931.idtracker@ietfa.amsl.com> Subject: FW: NOMCOM 2013 - Second Call for Nominations - two weeks left Date: Sat, 5 Oct 2013 00:12:36 +0100 Message-ID: <068a01cec157$3734dd50$a59e97f0$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQLL++SFmyRuLtaSjD2BlMq0RAvP75fqtnVQ Content-Language: en-gb X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Oct 2013 23:12:50 -0000 Please nominate qualified candidates for all open positions. Self-nomination is very acceptable. Adrian > -----Original Message----- > From: ietf-announce-bounces@ietf.org [mailto:ietf-announce- > bounces@ietf.org] On Behalf Of NomCom Chair 2013 > Sent: 04 October 2013 18:32 > To: IETF Announcement List > Cc: IETF Discuss List > Subject: NOMCOM 2013 - Second Call for Nominations - two weeks left >=20 > Nominations for the IESG, IAB, and IAOC are due to the Nomcom by = Friday, 18 > October, 2013. >=20 > Is there someone you work with at IETF who has leadership potential = and a > growing track record? Please read the Nomcom call for nominations and = consider > nominating her or him. Or several folks! Deadline for nominations is = October 18. > Nominate soon to give your nominee(s) plenty time to fill in the = questionnaire. > Information about the desired expertise for positions is here: > https://datatracker.ietf.org/nomcom/2013/expertise >=20 > Lots more, including which positions are open, how to make a = nomination, and > how to > send us your feedback on the desired expertise, follows. >=20 > IETFers, let's hear from you! Make nominations, accept nominations! >=20 > If you have any questions about the process, feel free to get in touch = with me. >=20 > Best regards, >=20 > Allison for the Nomcom >=20 > Allison Mankin > Nomcom Chair 2013-14 >=20 > ----- The Info You Need for Nominating ----- >=20 > The 2013-14 Nominating Committee (Nomcom) is seeking nominations > from now until October 18, 2013. The open positions being considered > by this year's Nomcom can be found later in this section, and also on > this year's Nomcom website: >=20 > https://datatracker.ietf.org/nomcom/2013/ >=20 > Nominations may be made by selecting the Nominate link at the top of > the Nomcom 2013 home page, or by visiting the following URL: >=20 > https://datatracker.ietf.org/nomcom/2013/nominate/ >=20 > Note that nominations made using the web tool require an ietf.org > datatracker account. You can create a datatracker ietf.org account > if you don't have one already by visiting the following URL: >=20 > https://datatracker.ietf.org/accounts/create/ >=20 > Nominations may also be made by email to nomcom13 at ietf.org. > If you nominate by email, please include the word "Nominate" in the = Subject > and indicate in the email who is being nominated, their email address = (to > confirm acceptance of the nomination), and the position for which you > are making the nomination. If you use email, please use a separate = email for > each person you nominate, and for each position (if you are nominating = one > person for multiple positions). >=20 > Self-nomination is welcome! No need to be shy. >=20 > Nomcom 2013-14 will follow the policy for "Open Disclosure of Willing > Nominees" described in RFC 5680. As stated in RFC 5680: "The list of > nominees willing to be considered for positions under review in the > current Nomcom cycle is not confidential". Willing nominees for each > position will be listed in a publicly accessible way - anyone with a > datatracker account may access the lists. In all other ways, the > confidentiality requirements of RFC 3777/BCP10 remain in effect. All > feedback and all Nomcom deliberations will remain confidential and = will > not be disclosed. >=20 > In order to ensure time to collect sufficient community feedback about > each of the willing nominees, nominations must be received by the > Nomcom on or before October 18, 2013. Please submit your nominations > as early as possible for the sake of your nominees, as we've set the > questionnaire submission deadline for October 25, 2013. >=20 > The list of people and posts whose terms end with the March 2014 IETF = meeting, > and thus the positions for which we are accepting nominations: >=20 > IAOC > Chris Griffiths >=20 > IAB > Bernard Aboba > Marc Blanchet > Ross Callon > Eliot Lear > Hannes Tschofenig >=20 > IESG > Barry Leiba (Applications) > Brian Haberman (Internet) > Benoit Claise (Operations and Management) > Gonzalo Camarillo (RAI) > Stewart Bryant (Routing) > Sean Turner (Security) > Martin Stiemerling (Transport) >=20 > Please be resourceful in identifying possible candidates for these > positions, as developing our talent is a very crucial requirement for > the IETF. Also, please give serious consideration to accepting = nominations > you receive. >=20 > The summaries of the desired expertise for the positions, developed by = the > respective bodies, are found at: >=20 > https://datatracker.ietf.org/nomcom/2013/expertise/ >=20 > In addition to nominations, the Nomcom seeks community input on > the positions themselves. We need and welcome the community's > views and input on the jobs within each organization. If you > have ideas on the positions' responsibilities (more, less, > different), please let us know. You can send us email about this to > nomcom13 at ietf.org, and we will use this feedback actively. >=20 > Thank you for your help in nominating a great pool of strong and = interesting > nominees! >=20 From adrian@olddog.co.uk Mon Oct 7 10:38:50 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3929311E810A; Mon, 7 Oct 2013 10:38:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.535 X-Spam-Level: X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xfAqrZSg-vL3; Mon, 7 Oct 2013 10:38:44 -0700 (PDT) Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 1B35021F9FAE; Mon, 7 Oct 2013 10:38:43 -0700 (PDT) Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r97HceWj030078; Mon, 7 Oct 2013 18:38:40 +0100 Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r97HcdK5030069 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Oct 2013 18:38:39 +0100 From: "Adrian Farrel" To: , , Subject: Routing ADs Open Office : Vancouver Date: Mon, 7 Oct 2013 18:38:39 +0100 Message-ID: <02f501cec384$0f818950$2e849bf0$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac7DhAuSLs1v28q5R/GMhN3NuGdUfQ== Content-Language: en-gb Cc: stbryant@cisco.com X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 17:38:50 -0000 Hi, In a break with tradition, we will hold office hours at lunch on Thursday. Venue will be the IESG break-out room (to be announced). Sorry in advance that you may have to watch the ADs eat! Adrian and Stewart. From jdrake@juniper.net Tue Oct 8 14:58:44 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06E8821F9E73; Tue, 8 Oct 2013 14:58:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.099 X-Spam-Level: X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=1.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R2jqqZ-OsoDG; Tue, 8 Oct 2013 14:58:37 -0700 (PDT) Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe005.messaging.microsoft.com [207.46.163.28]) by ietfa.amsl.com (Postfix) with ESMTP id 9B58B21F9FC7; Tue, 8 Oct 2013 14:58:26 -0700 (PDT) Received: from mail111-co9-R.bigfish.com (10.236.132.252) by CO9EHSOBE036.bigfish.com (10.236.130.99) with Microsoft SMTP Server id 14.1.225.22; Tue, 8 Oct 2013 21:58:24 +0000 Received: from mail111-co9 (localhost [127.0.0.1]) by mail111-co9-R.bigfish.com (Postfix) with ESMTP id 8F32EA400EE; Tue, 8 Oct 2013 21:58:24 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -22 X-BigFish: VPS-22(zz9371I542I1432Ief7Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL1de097h8275bh8275dhz2fh2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h9a9j1155h) Received-SPF: pass (mail111-co9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=jdrake@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(13464003)(377454003)(51704005)(189002)(199002)(38314003)(31966008)(69226001)(51856001)(50986001)(47736001)(80022001)(47976001)(81686001)(83072001)(59766001)(19580395003)(19580405001)(65816001)(49866001)(83322001)(81816001)(74502001)(79102001)(80976001)(77982001)(74662001)(63696002)(46102001)(47446002)(54316002)(66066001)(81542001)(74316001)(33646001)(81342001)(76482001)(53806001)(74876001)(54356001)(56776001)(76576001)(74706001)(4396001)(74366001)(85306002)(76796001)(77096001)(56816003)(76786001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR05MB141; H:BY2PR05MB142.namprd05.prod.outlook.com; CLIP:66.129.224.36; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; Received: from mail111-co9 (localhost.localdomain [127.0.0.1]) by mail111-co9 (MessageSwitch) id 1381269502349779_32379; Tue, 8 Oct 2013 21:58:22 +0000 (UTC) Received: from CO9EHSMHS017.bigfish.com (unknown [10.236.132.247]) by mail111-co9.bigfish.com (Postfix) with ESMTP id 4E79F10004B; Tue, 8 Oct 2013 21:58:22 +0000 (UTC) Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by CO9EHSMHS017.bigfish.com (10.236.130.27) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 8 Oct 2013 21:58:22 +0000 Received: from BY2PR05MB141.namprd05.prod.outlook.com (10.242.39.148) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.371.2; Tue, 8 Oct 2013 21:58:20 +0000 Received: from BY2PR05MB142.namprd05.prod.outlook.com (10.242.39.144) by BY2PR05MB141.namprd05.prod.outlook.com (10.242.39.148) with Microsoft SMTP Server (TLS) id 15.0.775.9; Tue, 8 Oct 2013 21:58:17 +0000 Received: from BY2PR05MB142.namprd05.prod.outlook.com ([169.254.12.177]) by BY2PR05MB142.namprd05.prod.outlook.com ([169.254.12.115]) with mapi id 15.00.0775.005; Tue, 8 Oct 2013 21:58:17 +0000 From: John E Drake To: "adrian@olddog.co.uk" , "routing-discussion@ietf.org" , "rtgarea-chairs@tools.ietf.org" , "rtg-dir@ietf.org" Subject: RE: [RTG-DIR] Routing ADs Open Office : Vancouver Thread-Topic: [RTG-DIR] Routing ADs Open Office : Vancouver Thread-Index: Ac7DhAuSLs1v28q5R/GMhN3NuGdUfQA7V77g Date: Tue, 8 Oct 2013 21:58:16 +0000 Message-ID: <380fad1f1e6e473baf3964f741ce5c0c@BY2PR05MB142.namprd05.prod.outlook.com> References: <02f501cec384$0f818950$2e849bf0$@olddog.co.uk> In-Reply-To: <02f501cec384$0f818950$2e849bf0$@olddog.co.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.224.36] x-forefront-prvs: 0993689CD1 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% X-Mailman-Approved-At: Wed, 09 Oct 2013 04:06:20 -0700 Cc: "stbryant@cisco.com" X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 21:58:44 -0000 Adrian, Will you be providing lunch and/or beer? Yours Irrespectively, John > -----Original Message----- > From: rtg-dir-bounces@ietf.org [mailto:rtg-dir-bounces@ietf.org] On Behal= f > Of Adrian Farrel > Sent: Monday, October 07, 2013 10:39 AM > To: routing-discussion@ietf.org; rtgarea-chairs@tools.ietf.org; rtg- > dir@ietf.org > Cc: stbryant@cisco.com > Subject: [RTG-DIR] Routing ADs Open Office : Vancouver >=20 > Hi, >=20 > In a break with tradition, we will hold office hours at lunch on Thursday= . >=20 > Venue will be the IESG break-out room (to be announced). >=20 > Sorry in advance that you may have to watch the ADs eat! >=20 > Adrian and Stewart. >=20 >=20 From loa@pi.nu Tue Oct 8 18:37:34 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B412821F9FF6; Tue, 8 Oct 2013 18:37:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PANnnKvOdVoG; Tue, 8 Oct 2013 18:37:28 -0700 (PDT) Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id E130D11E8104; Tue, 8 Oct 2013 18:37:27 -0700 (PDT) Received: from [192.168.1.6] (unknown [112.208.84.108]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 8584618014F6; Wed, 9 Oct 2013 03:37:24 +0200 (CEST) Message-ID: <5254B351.1010204@pi.nu> Date: Wed, 09 Oct 2013 09:37:21 +0800 From: Loa Andersson User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: John E Drake Subject: Re: [RTG-DIR] Routing ADs Open Office : Vancouver References: <02f501cec384$0f818950$2e849bf0$@olddog.co.uk> <380fad1f1e6e473baf3964f741ce5c0c@BY2PR05MB142.namprd05.prod.outlook.com> In-Reply-To: <380fad1f1e6e473baf3964f741ce5c0c@BY2PR05MB142.namprd05.prod.outlook.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 09 Oct 2013 04:06:20 -0700 Cc: "adrian@olddog.co.uk" , "stbryant@cisco.com" , "rtg-dir@ietf.org" , "routing-discussion@ietf.org" , "rtgarea-chairs@tools.ietf.org" X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 01:37:35 -0000 if Adrian pay, I can get a good selection of pale ale and/or IPA. Vancover is a fairly OK beer city :) /Lo9a On 2013-10-09 05:58, John E Drake wrote: > Adrian, > > Will you be providing lunch and/or beer? > > Yours Irrespectively, > > John > >> -----Original Message----- >> From: rtg-dir-bounces@ietf.org [mailto:rtg-dir-bounces@ietf.org] On Behalf >> Of Adrian Farrel >> Sent: Monday, October 07, 2013 10:39 AM >> To: routing-discussion@ietf.org; rtgarea-chairs@tools.ietf.org; rtg- >> dir@ietf.org >> Cc: stbryant@cisco.com >> Subject: [RTG-DIR] Routing ADs Open Office : Vancouver >> >> Hi, >> >> In a break with tradition, we will hold office hours at lunch on Thursday. >> >> Venue will be the IESG break-out room (to be announced). >> >> Sorry in advance that you may have to watch the ADs eat! >> >> Adrian and Stewart. >> >> > > -- Loa Andersson email: loa@mail01.huawei.com Senior MPLS Expert loa@pi.nu Huawei Technologies (consultant) phone: +46 739 81 21 64 From adrian@olddog.co.uk Fri Oct 25 06:18:39 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6B1F11E83FD; Fri, 25 Oct 2013 06:18:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.833 X-Spam-Level: X-Spam-Status: No, score=-1.833 tagged_above=-999 required=5 tests=[AWL=-0.723, BAYES_05=-1.11] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B0UAh0xxZx7p; Fri, 25 Oct 2013 06:18:33 -0700 (PDT) Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 4CBDE11E8402; Fri, 25 Oct 2013 06:18:26 -0700 (PDT) Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9PDIMIR012599; Fri, 25 Oct 2013 14:18:22 +0100 Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9PDIJtc012527 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 25 Oct 2013 14:18:19 +0100 From: "Adrian Farrel" To: , , Subject: Reminder : Routing ADs Open Office : Vancouver Date: Fri, 25 Oct 2013 14:18:15 +0100 Message-ID: <156e01ced184$ab51dc00$01f59400$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac7RhKJzdtqNMoEyR3G9ujyo+LidTw== Content-Language: en-gb Cc: stbryant@cisco.com X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Oct 2013 13:18:39 -0000 Hi, The room will be called Lord Byron. > From: rtg-dir-bounces@ietf.org [mailto:rtg-dir-bounces@ietf.org] On Behalf Of > Adrian Farrel > Sent: 07 October 2013 18:39 > To: routing-discussion@ietf.org; rtgarea-chairs@tools.ietf.org; rtg-dir@ietf.org > Cc: stbryant@cisco.com > Subject: [RTG-DIR] Routing ADs Open Office : Vancouver > > Hi, > > In a break with tradition, we will hold office hours at lunch on Thursday. > > Venue will be the IESG break-out room (to be announced). > > Sorry in advance that you may have to watch the ADs eat! > > Adrian and Stewart. From adrian@olddog.co.uk Fri Oct 25 06:25:32 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52E1011E8192; Fri, 25 Oct 2013 06:25:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.573 X-Spam-Level: X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CRjpGECUje43; Fri, 25 Oct 2013 06:25:21 -0700 (PDT) Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 27F1C11E83F3; Fri, 25 Oct 2013 06:25:17 -0700 (PDT) Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9PDPGtT030907; Fri, 25 Oct 2013 14:25:16 +0100 Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9PDPFrg030899 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 25 Oct 2013 14:25:16 +0100 From: "Adrian Farrel" To: , , Subject: Topics for Routing Area meeting Date: Fri, 25 Oct 2013 14:25:11 +0100 Message-ID: <157601ced185$a27400d0$e75c0270$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac7RhUuL8WHLv4HBRj+zcJHzodCY3Q== Content-Language: en-gb X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Oct 2013 13:25:32 -0000 Hi, Does anyone have a topic they want to cover in this meeting? Let us know. Adrian and Stewart. From abdussalambaryun@gmail.com Sat Oct 26 01:40:24 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04B8C11E80F9; Sat, 26 Oct 2013 01:40:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.534 X-Spam-Level: X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mWvPln4UTytx; Sat, 26 Oct 2013 01:40:23 -0700 (PDT) Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id EAD1E21E8064; Sat, 26 Oct 2013 01:40:21 -0700 (PDT) Received: by mail-pb0-f44.google.com with SMTP id xa7so5461024pbc.17 for ; Sat, 26 Oct 2013 01:40:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zcMJe+tXmxZt5fU95PZNFA4rsA3WEN/r62QsByXS1go=; b=X9fslwgI7BrdVwuOqd7j+VIPAu5+2rSJBEKxjLYCQQ1rsuRwjF5SQ4Y4tyiaK5oX/K je20rZRdNBQj1G0Yps58lnNxZ9Or1yETs26jfEInc85zYq9RerZFrc5B5wkEWOgNnm6D l3NW1co8NeUOsZNdqgw/jaF5IvSbtWpGb6KhOeTmeDu2NtTg6tgDcuCzdAe+6VJ8QNKh 59jm9+3NQDqPCHYbWsQ8tm+ae4mGCzN13N2R7SUxfwrscwKiuSd1OkvJVfy5ku9xdFed SawT1+fk2ZymdLVro9UgSEd267iqpPWpmf5du4Z4N2nwLJJBK35aofGdZagN1zMngeMO EhnA== MIME-Version: 1.0 X-Received: by 10.66.227.39 with SMTP id rx7mr15195970pac.44.1382776821579; Sat, 26 Oct 2013 01:40:21 -0700 (PDT) Received: by 10.69.8.5 with HTTP; Sat, 26 Oct 2013 01:40:21 -0700 (PDT) In-Reply-To: <157601ced185$a27400d0$e75c0270$@olddog.co.uk> References: <157601ced185$a27400d0$e75c0270$@olddog.co.uk> Date: Sat, 26 Oct 2013 09:40:21 +0100 Message-ID: Subject: Re: Topics for Routing Area meeting From: Abdussalam Baryun To: "adrian@olddog.co.uk" Content-Type: multipart/alternative; boundary=047d7b111f3f4106b604e9a0d146 Cc: "rtg-dir@ietf.org" , "routing-discussion@ietf.org" , "rtg-chairs@ietf.org" X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Oct 2013 08:40:24 -0000 --047d7b111f3f4106b604e9a0d146 Content-Type: text/plain; charset=ISO-8859-1 If you mean anyone including remote participants, I have an issue not sure about within routing area, which is the cross WG issues do we leave it to ADs to advise or do WGs Chairs should take over this task and discuss cross issues, or participants/editor should consider this while developing I-Ds and presentations. Some people in IETF are concerned to compare our standards with other SDOs while developing I-Ds within IETF, I think we need more cross-WG considerations within developing standards and WG-charters. AB On Friday, October 25, 2013, Adrian Farrel wrote: > Hi, > > Does anyone have a topic they want to cover in this meeting? > > Let us know. > > Adrian and Stewart. > > _______________________________________________ > routing-discussion mailing list > routing-discussion@ietf.org > https://www.ietf.org/mailman/listinfo/routing-discussion > --047d7b111f3f4106b604e9a0d146 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If you mean anyone including remote participants, I have an issue not sure = about within routing area,=A0which is the cross WG issues do we leave it to= ADs to advise=A0or do WGs Chairs should take over this task and discuss cr= oss issues, or participants/editor should consider this while developing I-= Ds and presentations.

Some people in IETF are concerned=A0to compare our standards= with other SDOs while developing I-Ds=A0within IETF, I think=A0we need mor= e cross-WG considerations within developing standards and WG-charters.
<= div>
AB

On Friday, October 25, 2013, Adrian Farrel wrote:=
Hi,

Does anyone have a topic they want to cover in this meeting?

Let us know.

Adrian and Stewart.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www.ietf.org/mailman/listinfo/routing-discussion
--047d7b111f3f4106b604e9a0d146-- From adrian@olddog.co.uk Sat Oct 26 09:31:53 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8ABD511E81A1; Sat, 26 Oct 2013 09:31:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.573 X-Spam-Level: X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n1Vcv6c-zCLQ; Sat, 26 Oct 2013 09:31:48 -0700 (PDT) Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 1C1E621F9F2D; Sat, 26 Oct 2013 09:31:47 -0700 (PDT) Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9QGVgJT004082; Sat, 26 Oct 2013 17:31:42 +0100 Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9QGVf80004067 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 26 Oct 2013 17:31:41 +0100 From: "Adrian Farrel" To: "'Abdussalam Baryun'" References: <157601ced185$a27400d0$e75c0270$@olddog.co.uk> In-Reply-To: Subject: RE: Topics for Routing Area meeting Date: Sat, 26 Oct 2013 17:31:37 +0100 Message-ID: <170e01ced268$d82d6b10$88884130$@olddog.co.uk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_170F_01CED271.39F44410" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKqBJqdcWpUwCTETd+Fr63vlHEN+wGBigLrmES6TMA= Content-Language: en-gb Cc: rtg-dir@ietf.org, routing-discussion@ietf.org, rtg-chairs@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Oct 2013 16:31:53 -0000 This is a multipart message in MIME format. ------=_NextPart_000_170F_01CED271.39F44410 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, It is good of you to be interested. In the Area meeting I think we are looking for topics of technical substance that span the Routing Area. For example, in London we are promised a talk from the Management AD on the importance of considering management concerns when documenting routing protocols. In a sense, that is exactly the sort of cross-area issue you are talking about. But I think the specific topic you are raising (i.e., what cross-area review and discussion is need and how should we cause it to happen) could be handled more profitably by an email discussion on the routing-discussion@ietf.org list if it is specific to either RTG review of documents produced in other areas, or other-area review of documents produced in RTG. Obviously, the widest version of this topic (any-to-any cross-area review) belongs on the main IETF list. Adrian From: Abdussalam Baryun [mailto:abdussalambaryun@gmail.com] Sent: 26 October 2013 09:40 To: adrian@olddog.co.uk Cc: routing-discussion@ietf.org; rtg-chairs@ietf.org; rtg-dir@ietf.org Subject: Re: Topics for Routing Area meeting If you mean anyone including remote participants, I have an issue not sure about within routing area, which is the cross WG issues do we leave it to ADs to advise or do WGs Chairs should take over this task and discuss cross issues, or participants/editor should consider this while developing I-Ds and presentations. Some people in IETF are concerned to compare our standards with other SDOs while developing I-Ds within IETF, I think we need more cross-WG considerations within developing standards and WG-charters. AB On Friday, October 25, 2013, Adrian Farrel wrote: Hi, Does anyone have a topic they want to cover in this meeting? Let us know. Adrian and Stewart. _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www.ietf.org/mailman/listinfo/routing-discussion ------=_NextPart_000_170F_01CED271.39F44410 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

It is good of you to be = interested.

 

In the Area meeting I think we = are looking for topics of technical substance that span the Routing = Area. For example, in London we are promised a talk from the Management = AD on the importance of considering management concerns when documenting = routing protocols.

 

In a sense, that is exactly = the sort of cross-area issue you are talking about. But I think the = specific topic you are raising (i.e., what cross-area review and = discussion is need and how should we cause it to happen) could be = handled more profitably by an email discussion on the = routing-discussion@ietf.org list if it is specific to either RTG review = of documents produced in other areas, or other-area review of documents = produced in RTG. Obviously, the widest version of this topic (any-to-any = cross-area review) belongs on the main IETF = list.

 

Adrian

 

From: Abdussalam Baryun = [mailto:abdussalambaryun@gmail.com]
Sent: 26 October 2013 = 09:40
To: adrian@olddog.co.uk
Cc: = routing-discussion@ietf.org; rtg-chairs@ietf.org; = rtg-dir@ietf.org
Subject: Re: Topics for Routing Area = meeting

 

If you mean = anyone including remote participants, I have an issue not sure about = within routing area, which is the cross WG issues do we leave it to = ADs to advise or do WGs Chairs should take over this task and = discuss cross issues, or participants/editor should consider this while = developing I-Ds and presentations.

 

Some people in IETF are concerned to compare our = standards with other SDOs while developing I-Ds within IETF, I = think we need more cross-WG considerations within developing = standards and WG-charters.

 

AB

On Friday, October 25, 2013, Adrian Farrel = wrote:

Hi,

Does anyone have a = topic they want to cover in this meeting?

Let us = know.

Adrian and = Stewart.

_______________________________________________
routin= g-discussion mailing list
routing-discussion@ietf.org
https://www.ietf.org/mailman/listinfo/routing-discussio= n

------=_NextPart_000_170F_01CED271.39F44410-- From heinerhummel@aol.com Sun Oct 27 02:26:23 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8546411E8125 for ; Sun, 27 Oct 2013 02:26:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VI80AwQY6D3w for ; Sun, 27 Oct 2013 02:26:14 -0700 (PDT) Received: from omr-m04.mx.aol.com (omr-m04.mx.aol.com [64.12.143.78]) by ietfa.amsl.com (Postfix) with ESMTP id 2EAE511E8265 for ; Sun, 27 Oct 2013 02:26:09 -0700 (PDT) Received: from mtaomg-ma03.r1000.mx.aol.com (mtaomg-ma03.r1000.mx.aol.com [172.29.41.10]) by omr-m04.mx.aol.com (Outbound Mail Relay) with ESMTP id 9F10370000088; Sun, 27 Oct 2013 05:26:08 -0400 (EDT) Received: from core-dqa003a.r1000.mail.aol.com (core-dqa003.r1000.mail.aol.com [172.29.211.201]) by mtaomg-ma03.r1000.mx.aol.com (OMAG/Core Interface) with ESMTP id 623E0E000082; Sun, 27 Oct 2013 05:26:08 -0400 (EDT) References: <157601ced185$a27400d0$e75c0270$@olddog.co.uk> <170e01ced268$d82d6b10$88884130$@olddog.co.uk> To: adrian@olddog.co.uk, abdussalambaryun@gmail.com Subject: Re: Topics for Routing Area meeting In-Reply-To: <170e01ced268$d82d6b10$88884130$@olddog.co.uk> X-MB-Message-Source: WebUI Received: from 178.26.195.50 by webmail-vd008.sysops.aol.com (205.188.20.112) with HTTP (WebMailUI); Sun, 27 Oct 2013 05:26:08 -0400 MIME-Version: 1.0 From: heinerhummel@aol.com X-MB-Message-Type: User Content-Type: multipart/alternative; boundary="--------MB_8D0A10DB3AFAF74_1AA8_7F1D4_webmail-vd008.sysops.aol.com" X-Mailer: Webmail 38121-STANDARD Message-Id: <8D0A10DB39A4302-1AA8-232E7@webmail-vd008.sysops.aol.com> X-Originating-IP: [178.26.195.50] Date: Sun, 27 Oct 2013 05:26:08 -0400 (EDT) x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1382865968; bh=d3Af9gglZKuqd6wa8LPQ/ClPsYNcNDZRkVypxVoxpUI=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=y4Q1xjCjf92DHlH3fC3BDoHRIik3CFq/CPFzRn9i3UT0/8TPEcF1ho1IMcSeCAAsC iIVmfPHMYekCJNG4rbkuudUDhEmLfXso5iU3RlBEb573VFvDwig7XfOrCRI6OXIsr9 SkDu3r4QbETWhg7DuujjDvM/rjittsJ7gzcDoVt4= x-aol-sid: 3039ac1d290a526cdc3076e4 Cc: rtg-dir@ietf.org, routing-discussion@ietf.org, rtg-chairs@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Oct 2013 09:26:23 -0000 This is a multi-part message in MIME format. ----------MB_8D0A10DB3AFAF74_1AA8_7F1D4_webmail-vd008.sysops.aol.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Hi Adrian, If you mean anyone including remote participants, I have two topics to name= : 1) State-less multicast 2) A discussion what means anycast user services (given that IPv6 even prov= ides address space for this) from the application's point of view as well a= s from the IP-layer's point of view; or even to develop the necessary routi= ng technology. Heiner -----Urspr=C3=BCngliche Mitteilung-----=20 Von: Adrian Farrel An: 'Abdussalam Baryun' Cc: rtg-dir ; routing-discussion ; rtg-chairs Verschickt: Sa, 26 Okt 2013 6:32 pm Betreff: RE: Topics for Routing Area meeting Hi, =20 It is good of you to be interested. =20 In the Area meeting I think we are looking for topics of technical substanc= e that span the Routing Area. For example, in London we are promised a talk= from the Management AD on the importance of considering management concern= s when documenting routing protocols. =20 In a sense, that is exactly the sort of cross-area issue you are talking ab= out. But I think the specific topic you are raising (i.e., what cross-area = review and discussion is need and how should we cause it to happen) could b= e handled more profitably by an email discussion on the routing-discussion@= ietf.org list if it is specific to either RTG review of documents produced = in other areas, or other-area review of documents produced in RTG. Obviousl= y, the widest version of this topic (any-to-any cross-area review) belongs = on the main IETF list. =20 Adrian =20 From: Abdussalam Baryun [mailto:abdussalambaryun@gmail.com]=20 Sent: 26 October 2013 09:40 To: adrian@olddog.co.uk Cc: routing-discussion@ietf.org; rtg-chairs@ietf.org; rtg-dir@ietf.org Subject: Re: Topics for Routing Area meeting =20 If you mean anyone including remote participants, I have an issue not sure = about within routing area, which is the cross WG issues do we leave it to A= Ds to advise or do WGs Chairs should take over this task and discuss cross = issues, or participants/editor should consider this while developing I-Ds a= nd presentations. =20 Some people in IETF are concerned to compare our standards with other SDOs = while developing I-Ds within IETF, I think we need more cross-WG considerat= ions within developing standards and WG-charters. =20 AB On Friday, October 25, 2013, Adrian Farrel wrote: Hi, Does anyone have a topic they want to cover in this meeting? Let us know. Adrian and Stewart. _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www.ietf.org/mailman/listinfo/routing-discussion _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www.ietf.org/mailman/listinfo/routing-discussion =20 ----------MB_8D0A10DB3AFAF74_1AA8_7F1D4_webmail-vd008.sysops.aol.com Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8" Hi Adrian,
If you mea= n anyone including remote participants, I have two topics to name:
1= ) State-less multicast
2) A discussion what means anycast user servi= ces (given that IPv6 even provides address space for this) from the applica= tion's point of view as well as from the IP-layer's point of view; or even = to develop the necessary routing technology.

Heiner



-----= Urspr=C3=BCngliche Mitteilung-----
Von: Adrian Farrel <adrian@olddog.co.uk>
An: 'Abdussalam Baryun' <abdussalambaryun@gmail.com>
Cc: rtg-dir <rtg-dir@ietf.org>; routing-discussion <routing-discus= sion@ietf.org>; rtg-chairs <rtg-chairs@ietf.org>
Verschickt: Sa, 26 Okt 2013 6:32 pm
Betreff: RE: Topics for Routing Area meeting

Hi,<= /span>
&nbs= p;
It i= s good of you to be interested.
&nbs= p;
In t= he Area meeting I think we are looking for topics of technical substance th= at span the Routing Area. For example, in London we are promised a talk fro= m the Management AD on the importance of considering management concerns wh= en documenting routing protocols.
&nbs= p;
In a= sense, that is exactly the sort of cross-area issue you are talking about.= But I think the specific topic you are raising (i.e., what cross-area revi= ew and discussion is need and how should we cause it to happen) could be ha= ndled more profitably by an email discussion on the routing-discussion@ietf.org list if it is speci= fic to either RTG review of documents produced in other areas, or other-are= a review of documents produced in RTG. Obviously, the widest version of thi= s topic (any-to-any cross-area review) belongs on the main IETF list.
&nbs= p;
Adri= an
&nbs= p;
From: Abdussalam Baryun [mailto:abdussalambaryun@gmail.com]
Sent: 26 October 2013 09:40
To: adrian@olddog.co.uk Cc: routing-discussio= n@ietf.org; rtg-chairs@ietf.org<= /a>; rtg-dir@ietf.org
Subject: Re: Topics for Routing Area meeting
 
If you mean anyone including remote participants, = I have an issue not sure about within routing area, which is the cross= WG issues do we leave it to ADs to advise or do WGs Chairs should tak= e over this task and discuss cross issues, or participants/editor should co= nsider this while developing I-Ds and presentations.
 
Some people in IETF are concerned to compare = our standards with other SDOs while developing I-Ds within IETF, I thi= nk we need more cross-WG considerations within developing standards an= d WG-charters.
 
AB

On Friday, October 25, 2013, Adrian Farrel wrote:
Hi,

Does anyone have a topic they want to cover in this meeting?

Let us know.

Adrian and Stewart.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www.ietf.org/mailman/listinfo/routing-discussion 
________________________________________=
_______
routing-discussion mailing list
routing-discussion@ietf.org<=
/a>
https://www.ietf.org/mailman/listinfo/routing-discussion
----------MB_8D0A10DB3AFAF74_1AA8_7F1D4_webmail-vd008.sysops.aol.com--