From dromasca@avaya.com Wed Oct 5 07:30:05 2011 Return-Path: X-Original-To: ops-area@ietfa.amsl.com Delivered-To: ops-area@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DD7E1F0C36; Wed, 5 Oct 2011 07:30:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.386 X-Spam-Level: X-Spam-Status: No, score=-103.386 tagged_above=-999 required=5 tests=[AWL=0.213, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 DEq+m9MJlbST; Wed, 5 Oct 2011 07:30:01 -0700 (PDT) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 12C691F0C35; Wed, 5 Oct 2011 07:30:00 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArwAAC9qjE7GmAcF/2dsb2JhbABCmH6PFIEFgVMBAQEBAwEBAQ8eCj8MBgEIDQQEAQELBgwLAQcmHwcBAQUEAQQBEggah2GbNpsjhkhhBJkzjAA X-IronPort-AV: E=Sophos;i="4.68,491,1312171200"; d="scan'208";a="307538162" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 05 Oct 2011 10:33:08 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 05 Oct 2011 10:32:12 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 5 Oct 2011 16:33:06 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: BoF in Taipei Thread-Index: AcyCz/tTDMY4EaJVQeyV7yJwvTcQRwAmnDng From: "Romascanu, Dan (Dan)" To: , , Subject: [OPS-AREA] FW: BoF in Taipei X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2011 14:30:05 -0000 Please see the message from Adrian about the Software Driven Networks (SDN) BOF approved for Taipei. As Adrian puts it ' The BoF is nominally in the Routing Area, but I expect considerable involvement from the OPS Area.' Scheduling will avoid conflict with the area meetings and to the possible extent to the other WGs in OPS whose participants could contribute to this work (OPSAWG, NETCONF, NETMOD, V6OPS). The mail list is at http://www.lucidvision.com/mailman/listinfo/sdnp -----Original Message----- From: Adrian Farrel [mailto:adrian@olddog.co.uk]=20 Sent: Tuesday, October 04, 2011 10:00 PM To: sdnp@lucidvision.com Cc: stbryant@cisco.com; Romascanu, Dan (Dan); rbonica@juniper.net Subject: BoF in Taipei Hi SDN list, I wanted you to know that the IAB and IESG met today to discuss BoFs for Taipei. They have agreed that we will hold a BoF for SDN with a goal of "discussing the technology and identifying work items". The BoF is nominally in the Routing Area, but I expect considerable involvement from the OPS Area. That means that it will not be designated a "working group forming BoF". In other words, the objective of the meeting will not be to discuss the precise nature of what a new working group would do (charter, scope, milestones, documents). Rather, it will try to reach agreement on what the topic actually is, what work is out there, what belongs in the IETF, who wants to do what, and how it breaks into manageable units, etc.. We may find that the outcome is a clear new WG. We might find pieces of work that belong in different existing WGs. We might find that all the work actually belongs in another body. And we might find that there is no work to be done. Over the next couple of days I will work with Tom on an initial draft agenda for the meeting which we will put to you for more debate and bashing. We have a 2 hour slot, so we should be able to cover quite a lot. I will also appoint chairs for the BoF relatively soon so that they can take on a guiding role leading up to the meeting. OK? Adrian From marshall.eubanks@gmail.com Wed Oct 5 08:01:03 2011 Return-Path: X-Original-To: ops-area@ietfa.amsl.com Delivered-To: ops-area@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D3FE21F8C94; Wed, 5 Oct 2011 08:01:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.662 X-Spam-Level: X-Spam-Status: No, score=-102.662 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_LOW=-1, 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 sxHyvtBZZ-ZU; Wed, 5 Oct 2011 08:00:59 -0700 (PDT) Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 52E6121F8C85; Wed, 5 Oct 2011 08:00:59 -0700 (PDT) Received: by gyd12 with SMTP id 12so2013239gyd.31 for ; Wed, 05 Oct 2011 08:04:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VHi9ehKFHHyVgZAl7zevfFd+OtilQL2lPfyhxiqOXww=; b=Y8DC5Hx2LSF8Z9u7n4P/amGsTUKiP86QIAXMJiNoWNSM0RlUlMeEfH95b+D90NPPkD 53sU+MDARo4Dihv3T/I31x+5BuV/j3YjYXMUPuEYAeqRXmxoNbEbOhlB18WOf4ljKqe3 N+X2dFiiEQhMXH/ay4jVHQKoW54JztjOPZ0yY= MIME-Version: 1.0 Received: by 10.150.53.12 with SMTP id b12mr2306505yba.140.1317827046027; Wed, 05 Oct 2011 08:04:06 -0700 (PDT) Received: by 10.151.98.20 with HTTP; Wed, 5 Oct 2011 08:04:05 -0700 (PDT) In-Reply-To: References: Date: Wed, 5 Oct 2011 11:04:05 -0400 Message-ID: From: Marshall Eubanks To: "Romascanu, Dan (Dan)" Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Wed, 05 Oct 2011 08:01:57 -0700 Cc: ops-dir@ietf.org, ops-chairs@ietf.org, ops-area@ietf.org Subject: Re: [OPS-AREA] [OPS-DIR] FW: BoF in Taipei X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2011 15:01:03 -0000 Similarly, VPN4DC should be of interest to the OPS area. This was not approved as a BOF, but will be discussed in the L3VPN mailing list (now) and (if there is sufficient interest) in a L3VPN meeting in Taipei. You can find a brief description in http://trac.tools.ietf.org/bof/trac/wiki Please direct discussion of VPN4DC to L3VPN. Regards Marshall Eubanks On Wed, Oct 5, 2011 at 10:33 AM, Romascanu, Dan (Dan) wrote: > Please see the message from Adrian about the Software Driven Networks > (SDN) BOF approved for Taipei. As Adrian puts it ' The BoF is nominally > in the Routing Area, but I expect considerable involvement from the OPS > Area.' Scheduling will avoid conflict with the area meetings and to the > possible extent to the other WGs in OPS whose participants could > contribute to this work (OPSAWG, NETCONF, NETMOD, V6OPS). The mail list > is at http://www.lucidvision.com/mailman/listinfo/sdnp > > > > -----Original Message----- > From: Adrian Farrel [mailto:adrian@olddog.co.uk] > Sent: Tuesday, October 04, 2011 10:00 PM > To: sdnp@lucidvision.com > Cc: stbryant@cisco.com; Romascanu, Dan (Dan); rbonica@juniper.net > Subject: BoF in Taipei > > Hi SDN list, > > I wanted you to know that the IAB and IESG met today to discuss BoFs for > Taipei. > > They have agreed that we will hold a BoF for SDN with a goal of > "discussing the > technology and identifying work items". The BoF is nominally in the > Routing > Area, but I expect considerable involvement from the OPS Area. > > That means that it will not be designated a "working group forming BoF". > In > other words, the objective of the meeting will not be to discuss the > precise > nature of what a new working group would do (charter, scope, milestones, > documents). Rather, it will try to reach agreement on what the topic > actually > is, what work is out there, what belongs in the IETF, who wants to do > what, and > how it breaks into manageable units, etc.. > > We may find that the outcome is a clear new WG. We might find pieces of > work > that belong in different existing WGs. We might find that all the work > actually > belongs in another body. And we might find that there is no work to be > done. > > Over the next couple of days I will work with Tom on an initial draft > agenda for > the meeting which we will put to you for more debate and bashing. We > have a 2 > hour slot, so we should be able to cover quite a lot. > > I will also appoint chairs for the BoF relatively soon so that they can > take on > a guiding role leading up to the meeting. > > OK? > > Adrian > > _______________________________________________ > OPS-DIR mailing list > OPS-DIR@ietf.org > https://www.ietf.org/mailman/listinfo/ops-dir > From dromasca@avaya.com Tue Oct 25 13:20:16 2011 Return-Path: X-Original-To: ops-area@ietfa.amsl.com Delivered-To: ops-area@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E60221F8569; Tue, 25 Oct 2011 13:20:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.813 X-Spam-Level: X-Spam-Status: No, score=-102.813 tagged_above=-999 required=5 tests=[AWL=-0.214, 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 ofAbjGr8l5I3; Tue, 25 Oct 2011 13:20:15 -0700 (PDT) Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 3600521F8531; Tue, 25 Oct 2011 13:20:15 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArkHAK0Zp06HCzI1/2dsb2JhbABDmh2PAIEFgXABAQMSHgo/EgEVFQYMDAdXAQQbARmHZphgm36HdWEEmVWMFQ X-IronPort-AV: E=Sophos;i="4.69,405,1315195200"; d="scan'208";a="214672066" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 25 Oct 2011 16:20:13 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 25 Oct 2011 16:09:36 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 25 Oct 2011 22:20:05 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: thread-topic: Preliminary Agenda for the Open OPS Area meeting at IETF82 thread-index: AcyTU3uVixd/UDXSS4GwSVm0krnKsg== From: "Romascanu, Dan (Dan)" To: Cc: opsarea-chairs@ietf.org Subject: [OPS-AREA] Preliminary Agenda for the Open OPS Area meeting at IETF82 X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 20:20:16 -0000 The OPS Area will hold (as at the last few IETF meetings) a 2.5 hours session shared with the OPSAWG.=20 The preliminary agenda (only for the OPSAREA part) is available at http://www.ietf.org/proceedings/82/agenda/opsarea.txt.=20 Please let us know if there are any other requests for agenda time for the area meeting.=20 Thanks and Regards, Dan From dromasca@avaya.com Wed Oct 26 04:05:17 2011 Return-Path: X-Original-To: ops-area@ietfa.amsl.com Delivered-To: ops-area@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58BE721F8B3F; Wed, 26 Oct 2011 04:05:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.302 X-Spam-Level: X-Spam-Status: No, score=-103.302 tagged_above=-999 required=5 tests=[AWL=0.297, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 WywgZrBJhSV4; Wed, 26 Oct 2011 04:05:16 -0700 (PDT) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 45B0621F8ACC; Wed, 26 Oct 2011 04:05:15 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvUAANLnp06HCzI1/2dsb2JhbAA/A5l3jH+CQ4EFgW4BAQEBAwEBAQ8eCjQXAgQBCA0DAQQBAQsGDAsBBxoMHwcBAQUEAQQBEggah2aYY5wAAoVTgjRhBJlWjBU X-IronPort-AV: E=Sophos;i="4.69,408,1315195200"; d="scan'208";a="274504207" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 26 Oct 2011 07:05:13 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 26 Oct 2011 06:54:34 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 26 Oct 2011 13:05:10 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: thread-topic: [Netconf] sdn bof in taipei thread-index: AcyTTKrf23roocIcT9KqMsJZvj7smAAglD3g From: "Romascanu, Dan (Dan)" To: , Subject: [OPS-AREA] FW: [Netconf] sdn bof in taipei X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 11:05:17 -0000 This information is probably relevant to a broader OPS constituency.=20 Regards, Dan -----Original Message----- From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder Sent: Tuesday, October 25, 2011 9:31 PM To: netconf@ietf.org Subject: [Netconf] sdn bof in taipei Hi, there is a BoF on Software Driven Networks (sdn) in Taipei (Thursday 17:40-19:40) which seems to be related to what has been discussed under the phrase "network-wide configuration" a while ago on this list and in the hallways. I am sending this simply to make everyone aware of this BoF happening at Taipei. For additional information, see . /js --=20 Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 _______________________________________________ Netconf mailing list Netconf@ietf.org https://www.ietf.org/mailman/listinfo/netconf From bclaise@cisco.com Fri Oct 28 06:49:54 2011 Return-Path: X-Original-To: ops-area@ietfa.amsl.com Delivered-To: ops-area@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3889B21F8677; Fri, 28 Oct 2011 06:49:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.498 X-Spam-Level: X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[AWL=0.101, 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 dgmpSwZgQQu2; Fri, 28 Oct 2011 06:49:53 -0700 (PDT) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 525F021F858C; Fri, 28 Oct 2011 06:49:53 -0700 (PDT) X-TACSUNS: Virus Scanned Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p9SDnmkc013123; Fri, 28 Oct 2011 15:49:48 +0200 (CEST) Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p9SDnmX4001540; Fri, 28 Oct 2011 15:49:48 +0200 (CEST) Message-ID: <4EAAB2FB.3090207@cisco.com> Date: Fri, 28 Oct 2011 15:49:48 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: eman mailing list Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ops-area@ietf.org Subject: [OPS-AREA] UUID required for all energy objects -> ENTITY-MIB v4? X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 13:49:54 -0000 Dear all, At the last IETF meeting, we concluded that we would need an UUID for every energy objects. See http://www.ietf.org/proceedings/81/minutes/eman.txt We also concluded there were two ways to add this UUID 1. within the ENERGY-AWARE MIB to be fast 2. within the ENTITY-MIB v4 (because the UUID is not energy specific) with a compliance statement in the ENERGY-AWARE-MIB to implement a couple of MIB objects from the ENTITY-MIB v4. One of them being the UUID. I haven't seen any work in the direction of option 2. So, right now, we're stuck with 1. Does anybody have been working on this? Does any of you have in interest in participating in such work? Regards, Benoit. From j.schoenwaelder@jacobs-university.de Fri Oct 28 07:05:27 2011 Return-Path: X-Original-To: ops-area@ietfa.amsl.com Delivered-To: ops-area@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AB1921F8B1E; Fri, 28 Oct 2011 07:05:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.122 X-Spam-Level: X-Spam-Status: No, score=-103.122 tagged_above=-999 required=5 tests=[AWL=0.127, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, 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 CRr9oiXjp39X; Fri, 28 Oct 2011 07:05:26 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 5ED3A21F8AD9; Fri, 28 Oct 2011 07:05:26 -0700 (PDT) Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 42EB120E76; Fri, 28 Oct 2011 16:05:25 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id amoDXdOPGuX0; Fri, 28 Oct 2011 16:05:24 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id F140220E7E; Fri, 28 Oct 2011 16:05:23 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id 013D81B3F633; Fri, 28 Oct 2011 16:05:07 +0200 (CEST) Date: Fri, 28 Oct 2011 16:05:07 +0200 From: Juergen Schoenwaelder To: Benoit Claise Message-ID: <20111028140507.GB43890@elstar.local> Mail-Followup-To: Benoit Claise , eman mailing list , Andy Bierman , ops-area@ietf.org References: <4EAAB2FB.3090207@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EAAB2FB.3090207@cisco.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: eman mailing list , ops-area@ietf.org Subject: Re: [OPS-AREA] [eman] UUID required for all energy objects -> ENTITY-MIB v4? X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 14:05:27 -0000 On Fri, Oct 28, 2011 at 03:49:48PM +0200, Benoit Claise wrote: > Dear all, > > At the last IETF meeting, we concluded that we would need an UUID > for every energy objects. > See http://www.ietf.org/proceedings/81/minutes/eman.txt > > We also concluded there were two ways to add this UUID > 1. within the ENERGY-AWARE MIB to be fast > 2. within the ENTITY-MIB v4 (because the UUID is not energy > specific) with a compliance statement in the ENERGY-AWARE-MIB to > implement a couple of MIB objects from the ENTITY-MIB v4. One of > them being the UUID. > > I haven't seen any work in the direction of option 2. So, right now, > we're stuck with 1. > Does anybody have been working on this? Does any of you have in > interest in participating in such work? The ENTITY-MIB version 3 has the entPhysicalUris object and it can hold an RFC 4122 UUID in URN format. There is no need for an ENTITY-MIB v4 to carry a UUID. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From bclaise@cisco.com Fri Oct 28 07:47:10 2011 Return-Path: X-Original-To: ops-area@ietfa.amsl.com Delivered-To: ops-area@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B1F821F8B30; Fri, 28 Oct 2011 07:47:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.502 X-Spam-Level: X-Spam-Status: No, score=-2.502 tagged_above=-999 required=5 tests=[AWL=0.097, 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 STh1odg5PATN; Fri, 28 Oct 2011 07:47:09 -0700 (PDT) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 3424421F8B3C; Fri, 28 Oct 2011 07:47:09 -0700 (PDT) X-TACSUNS: Virus Scanned Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p9SEl746019669; Fri, 28 Oct 2011 16:47:07 +0200 (CEST) Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p9SEl4BP014462; Fri, 28 Oct 2011 16:47:04 +0200 (CEST) Message-ID: <4EAAC068.2020008@cisco.com> Date: Fri, 28 Oct 2011 16:47:04 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: eman mailing list , Andy Bierman , ops-area@ietf.org References: <4EAAB2FB.3090207@cisco.com> <20111028140507.GB43890@elstar.local> In-Reply-To: <20111028140507.GB43890@elstar.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [OPS-AREA] [eman] UUID required for all energy objects -> ENTITY-MIB v4? X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 14:47:10 -0000 Thanks Juergen for the pointer. So it means that , whatever the entPhysicalUris MIB object contains, we could add a UUID (as specified to in RFC4122) to it, separated by a space, right? Regards, Benoit. > On Fri, Oct 28, 2011 at 03:49:48PM +0200, Benoit Claise wrote: >> Dear all, >> >> At the last IETF meeting, we concluded that we would need an UUID >> for every energy objects. >> See http://www.ietf.org/proceedings/81/minutes/eman.txt >> >> We also concluded there were two ways to add this UUID >> 1. within the ENERGY-AWARE MIB to be fast >> 2. within the ENTITY-MIB v4 (because the UUID is not energy >> specific) with a compliance statement in the ENERGY-AWARE-MIB to >> implement a couple of MIB objects from the ENTITY-MIB v4. One of >> them being the UUID. >> >> I haven't seen any work in the direction of option 2. So, right now, >> we're stuck with 1. >> Does anybody have been working on this? Does any of you have in >> interest in participating in such work? > The ENTITY-MIB version 3 has the entPhysicalUris object and it > can hold an RFC 4122 UUID in URN format. There is no need for an > ENTITY-MIB v4 to carry a UUID. > > /js > From j.schoenwaelder@jacobs-university.de Fri Oct 28 09:26:09 2011 Return-Path: X-Original-To: ops-area@ietfa.amsl.com Delivered-To: ops-area@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A960521F867F; Fri, 28 Oct 2011 09:26:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.126 X-Spam-Level: X-Spam-Status: No, score=-103.126 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, 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 bnIdWcwhdlIs; Fri, 28 Oct 2011 09:26:08 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id B410B21F85B5; Fri, 28 Oct 2011 09:26:08 -0700 (PDT) Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 14E6820DF9; Fri, 28 Oct 2011 18:26:08 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id delzBZ7dYNdf; Fri, 28 Oct 2011 18:26:07 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id CD2DF20DF5; Fri, 28 Oct 2011 18:26:06 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id 2B8231B3F951; Fri, 28 Oct 2011 18:25:49 +0200 (CEST) Date: Fri, 28 Oct 2011 18:25:49 +0200 From: Juergen Schoenwaelder To: Benoit Claise Message-ID: <20111028162549.GA44374@elstar.local> Mail-Followup-To: Benoit Claise , eman mailing list , Andy Bierman , ops-area@ietf.org References: <4EAAB2FB.3090207@cisco.com> <20111028140507.GB43890@elstar.local> <4EAAC068.2020008@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EAAC068.2020008@cisco.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: eman mailing list , ops-area@ietf.org Subject: Re: [OPS-AREA] [eman] UUID required for all energy objects -> ENTITY-MIB v4? X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 16:26:09 -0000 On Fri, Oct 28, 2011 at 04:47:04PM +0200, Benoit Claise wrote: > So it means that , whatever the entPhysicalUris MIB object contains, > we could add a UUID (as specified to in RFC4122) to it, separated by > a space, right? entPhysicalUris can contain a white space separated list of URIs: Multiple URIs may be present and are separated by white space characters. Leading and trailing white space characters are ignored. There was debate around CLEI codes (the pros and cons) and the final resolution was to support anything that can be represented as a URI. Today we seem to like UUIDs. This can all happily co-exist (note that entPhysicalUris does not even have the typical 255 octets size limit). /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From mrm@vmware.com Fri Oct 28 09:40:03 2011 Return-Path: X-Original-To: ops-area@ietfa.amsl.com Delivered-To: ops-area@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DCA221F86C3; Fri, 28 Oct 2011 09:40:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 8cdzj-tebFp0; Fri, 28 Oct 2011 09:40:03 -0700 (PDT) Received: from smtp-outbound-2.vmware.com (smtp-outbound-2.vmware.com [65.115.85.73]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD5321F86AA; Fri, 28 Oct 2011 09:40:03 -0700 (PDT) Received: from mailhost3.vmware.com (mailhost3.vmware.com [10.16.27.45]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id E038631015; Fri, 28 Oct 2011 09:40:02 -0700 (PDT) Received: from zimbra-prod-mta-2.vmware.com (zimbra-prod-mta-2.vmware.com [10.113.160.174]) by mailhost3.vmware.com (Postfix) with ESMTP id CDB5CCDA6E; Fri, 28 Oct 2011 09:40:02 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra-prod-mta-2.vmware.com (Postfix) with ESMTP id BE37326250; Fri, 28 Oct 2011 09:40:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at Received: from zimbra-prod-mta-2.vmware.com ([127.0.0.1]) by localhost (zimbra-prod-mta-2.vmware.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KtUUUKeJcfAE; Fri, 28 Oct 2011 09:40:02 -0700 (PDT) Received: from zimbra-prod-mbox-2.vmware.com (zimbra-prod-mbox-2.vmware.com [10.113.160.202]) by zimbra-prod-mta-2.vmware.com (Postfix) with ESMTP id 983A62624C; Fri, 28 Oct 2011 09:40:02 -0700 (PDT) Date: Fri, 28 Oct 2011 09:40:02 -0700 (PDT) From: Michael MacFaden To: Juergen Schoenwaelder Message-ID: <1176954381.380109.1319820002550.JavaMail.root@zimbra-prod-mbox-2.vmware.com> In-Reply-To: <20111028140507.GB43890@elstar.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.113.61.163] X-Mailer: Zimbra 7.1.1_GA_3225 (ZimbraWebClient - SAF3 (Mac)/7.1.1_GA_3225) Cc: eman mailing list , ops-area@ietf.org Subject: Re: [OPS-AREA] [eman] UUID required for all energy objects -> ENTITY-MIB v4? X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 16:40:03 -0000 > The ENTITY-MIB version 3 has the entPhysicalUris object and it > can hold an RFC 4122 UUID in URN format. There is no need for an > ENTITY-MIB v4 to carry a UUID. Hi Juergen, What would be the encoding? Text 38a52be4-9352-453e-af97-5c3b448652f0 Text with brackets {38a52be4-9352-453e-af97-5c3b448652f0}. URL: uuid://38a52be4-9352-453e-af97-5c3b448652f0 ?? Thanks, Mike MacFaden From j.schoenwaelder@jacobs-university.de Fri Oct 28 10:42:04 2011 Return-Path: X-Original-To: ops-area@ietfa.amsl.com Delivered-To: ops-area@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 340F621F85B1; Fri, 28 Oct 2011 10:42:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.129 X-Spam-Level: X-Spam-Status: No, score=-103.129 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, 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 BP3kCp-dqMXv; Fri, 28 Oct 2011 10:42:03 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 7E6D221F85A1; Fri, 28 Oct 2011 10:42:03 -0700 (PDT) Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id C618A20E62; Fri, 28 Oct 2011 19:42:02 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id gcsgpJwm2dsF; Fri, 28 Oct 2011 19:42:01 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6CCFC20E3C; Fri, 28 Oct 2011 19:42:01 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id 7516D1B3FAF1; Fri, 28 Oct 2011 19:41:45 +0200 (CEST) Date: Fri, 28 Oct 2011 19:41:45 +0200 From: Juergen Schoenwaelder To: Michael MacFaden Message-ID: <20111028174145.GA44687@elstar.local> Mail-Followup-To: Michael MacFaden , eman mailing list , ops-area@ietf.org, Benoit Claise References: <20111028140507.GB43890@elstar.local> <1176954381.380109.1319820002550.JavaMail.root@zimbra-prod-mbox-2.vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1176954381.380109.1319820002550.JavaMail.root@zimbra-prod-mbox-2.vmware.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: eman mailing list , ops-area@ietf.org Subject: Re: [OPS-AREA] [eman] UUID required for all energy objects -> ENTITY-MIB v4? X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 17:42:04 -0000 On Fri, Oct 28, 2011 at 09:40:02AM -0700, Michael MacFaden wrote: > > The ENTITY-MIB version 3 has the entPhysicalUris object and it > > can hold an RFC 4122 UUID in URN format. There is no need for an > > ENTITY-MIB v4 to carry a UUID. > > Hi Juergen, > > What would be the encoding? > Text > 38a52be4-9352-453e-af97-5c3b448652f0 > Text with brackets > {38a52be4-9352-453e-af97-5c3b448652f0}. > URL: > uuid://38a52be4-9352-453e-af97-5c3b448652f0 entPhysicalUris contains URIs, see the description clause. Copying an example from RFC 4122, it should be urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From fred@cisco.com Mon Oct 31 14:33:27 2011 Return-Path: X-Original-To: ops-area@ietfa.amsl.com Delivered-To: ops-area@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 571891F0C8D; Mon, 31 Oct 2011 14:33:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -108.739 X-Spam-Level: X-Spam-Status: No, score=-108.739 tagged_above=-999 required=5 tests=[AWL=0.660, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_HI=-8, 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 aTg-IawSRyNn; Mon, 31 Oct 2011 14:33:26 -0700 (PDT) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id B0CF01F0C8B; Mon, 31 Oct 2011 14:33:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=3249; q=dns/txt; s=iport; t=1320096806; x=1321306406; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=qoYILlRQMiTnqMhd5qiu78xMa1DYgyfDhqGVNhp7HhQ=; b=B6iDOVtRYRtR0INlXhujaSuB0LzepU7YysUoV1wcdm1v7aq77o7VWVN5 VRwNxySndNKPeo2TVqwFQVjRrx2X8etm/m7ki+UKHiVXOQcJGWIN5zEAo cO/SxjNfCOUPEkH9KEURG6M2OMcbdjV2QvvPCihs2BEK9nMS9CQbUVoOJ k=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuUAADQTr05Io8UQ/2dsb2JhbABDmWONBoJNgQWBcgEBAQECAQEBAQ8BJzQLBQcECxEEAQEBJwcnHwgBCAYTIodgCJVTAZ5AiCFhBIgEjAqFLYw/ X-IronPort-AV: E=Sophos;i="4.69,434,1315180800"; d="scan'208";a="120459675" Received: from bgl-core-1.cisco.com ([72.163.197.16]) by ams-iport-1.cisco.com with ESMTP; 31 Oct 2011 21:33:22 +0000 Received: from localhost (tky-vpn-client-231-167.cisco.com [10.70.231.167]) by bgl-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9VLVmQ2011969; Mon, 31 Oct 2011 21:33:19 GMT Received: from [127.0.0.1] by localhost (PGP Universal service); Tue, 01 Nov 2011 05:33:20 +0900 X-PGP-Universal: processed; by localhost on Tue, 01 Nov 2011 05:33:20 +0900 Mime-Version: 1.0 (Apple Message framework v1084) From: Fred Baker In-Reply-To: Date: Tue, 1 Nov 2011 05:33:18 +0800 Message-Id: <097EB222-ABD7-4F94-95EC-ABA8DA9AF02F@cisco.com> References: To: Marshall Eubanks X-Mailer: Apple Mail (2.1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: ops-dir@ietf.org, ops-area@ietf.org, ops-chairs@ietf.org Subject: Re: [OPS-AREA] [OPS-DIR] FW: BoF in Taipei X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2011 21:33:27 -0000 what is the vpn4dc@ietf.org list being used for? On Oct 5, 2011, at 11:04 PM, Marshall Eubanks wrote: > Similarly, VPN4DC should be of interest to the OPS area. This was not > approved as > a BOF, but will be discussed in the L3VPN mailing list (now) and (if > there is sufficient interest) > in a L3VPN meeting in Taipei. >=20 > You can find a brief description in = http://trac.tools.ietf.org/bof/trac/wiki >=20 > Please direct discussion of VPN4DC to L3VPN. >=20 > Regards > Marshall Eubanks >=20 > On Wed, Oct 5, 2011 at 10:33 AM, Romascanu, Dan (Dan) > wrote: >> Please see the message from Adrian about the Software Driven Networks >> (SDN) BOF approved for Taipei. As Adrian puts it ' The BoF is = nominally >> in the Routing Area, but I expect considerable involvement from the = OPS >> Area.' Scheduling will avoid conflict with the area meetings and to = the >> possible extent to the other WGs in OPS whose participants could >> contribute to this work (OPSAWG, NETCONF, NETMOD, V6OPS). The mail = list >> is at http://www.lucidvision.com/mailman/listinfo/sdnp >>=20 >>=20 >>=20 >> -----Original Message----- >> From: Adrian Farrel [mailto:adrian@olddog.co.uk] >> Sent: Tuesday, October 04, 2011 10:00 PM >> To: sdnp@lucidvision.com >> Cc: stbryant@cisco.com; Romascanu, Dan (Dan); rbonica@juniper.net >> Subject: BoF in Taipei >>=20 >> Hi SDN list, >>=20 >> I wanted you to know that the IAB and IESG met today to discuss BoFs = for >> Taipei. >>=20 >> They have agreed that we will hold a BoF for SDN with a goal of >> "discussing the >> technology and identifying work items". The BoF is nominally in the >> Routing >> Area, but I expect considerable involvement from the OPS Area. >>=20 >> That means that it will not be designated a "working group forming = BoF". >> In >> other words, the objective of the meeting will not be to discuss the >> precise >> nature of what a new working group would do (charter, scope, = milestones, >> documents). Rather, it will try to reach agreement on what the topic >> actually >> is, what work is out there, what belongs in the IETF, who wants to do >> what, and >> how it breaks into manageable units, etc.. >>=20 >> We may find that the outcome is a clear new WG. We might find pieces = of >> work >> that belong in different existing WGs. We might find that all the = work >> actually >> belongs in another body. And we might find that there is no work to = be >> done. >>=20 >> Over the next couple of days I will work with Tom on an initial draft >> agenda for >> the meeting which we will put to you for more debate and bashing. We >> have a 2 >> hour slot, so we should be able to cover quite a lot. >>=20 >> I will also appoint chairs for the BoF relatively soon so that they = can >> take on >> a guiding role leading up to the meeting. >>=20 >> OK? >>=20 >> Adrian >>=20 >> _______________________________________________ >> OPS-DIR mailing list >> OPS-DIR@ietf.org >> https://www.ietf.org/mailman/listinfo/ops-dir >>=20 > _______________________________________________ > OPS-DIR mailing list > OPS-DIR@ietf.org > https://www.ietf.org/mailman/listinfo/ops-dir From fred@cisco.com Mon Oct 31 15:21:44 2011 Return-Path: X-Original-To: ops-area@ietfa.amsl.com Delivered-To: ops-area@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E18A91F0D11; Mon, 31 Oct 2011 15:21:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -108.849 X-Spam-Level: X-Spam-Status: No, score=-108.849 tagged_above=-999 required=5 tests=[AWL=0.550, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_HI=-8, 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 asOFVFVy8x0F; Mon, 31 Oct 2011 15:21:43 -0700 (PDT) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 9AA401F0D05; Mon, 31 Oct 2011 15:21:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=10450; q=dns/txt; s=iport; t=1320099700; x=1321309300; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=KsKhODg88XQWpz1NSOAkQywpq//QP/5LYl3Tspc/QaE=; b=eg7wT5gNnVQDkFsSH0jCK79ThwNGo74qOFGseKrj9fI0jhFJItlkEe5U cleNYFwLMu76j8u6RxIwSjCe6qReyRZ1fxSjNxgsO2/9PIB5EPTO33ARa phaTq+kmodzPusuCT0ZD7f7Zhh7qDPwtZGEy73l8eHoCRzZ9XUnUJo6fw w=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvMAAOcer05Io8UQ/2dsb2JhbABDmWOHfoUIgk2BBYFyAQEBAQIBAQEBDwFbCwUHBAsRBAEBAScHJx8IAQgGEyKHYAiVYQGeP4ghYQSIBIwKhS2MPw X-IronPort-AV: E=Sophos;i="4.69,434,1315180800"; d="scan'208,217";a="120461439" Received: from bgl-core-1.cisco.com ([72.163.197.16]) by ams-iport-1.cisco.com with ESMTP; 31 Oct 2011 22:21:36 +0000 Received: from localhost (tky-vpn-client-231-167.cisco.com [10.70.231.167]) by bgl-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9VMLXGX018846; Mon, 31 Oct 2011 22:21:33 GMT Received: from [127.0.0.1] by localhost (PGP Universal service); Tue, 01 Nov 2011 06:21:35 +0900 X-PGP-Universal: processed; by localhost on Tue, 01 Nov 2011 06:21:35 +0900 Mime-Version: 1.0 (Apple Message framework v1084) From: Fred Baker In-Reply-To: Date: Tue, 1 Nov 2011 06:21:21 +0800 Message-Id: References: <097EB222-ABD7-4F94-95EC-ABA8DA9AF02F@cisco.com> To: Marshall Eubanks X-Mailer: Apple Mail (2.1084) Content-Type: multipart/alternative; boundary=Apple-Mail-15-342581939 Cc: ops-dir@ietf.org, ops-area@ietf.org, ops-chairs@ietf.org Subject: Re: [OPS-AREA] [OPS-DIR] FW: BoF in Taipei X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2011 22:21:45 -0000 --Apple-Mail-15-342581939 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii OK, do me a favor. I sent a note to vpn4dc@, and have since forwarded it = to l3vpn@. I'm not a member of the latter. So let it through... On Nov 1, 2011, at 6:13 AM, Marshall Eubanks wrote: >=20 > On Mon, Oct 31, 2011 at 5:33 PM, Fred Baker wrote: > what is the vpn4dc@ietf.org list being used for? >=20 >=20 > Not much at present. The VPN4DC BOF was turned into a special session = of L3VPN, so I asked people not to use > the BOF VPN4DC mailing list.=20 >=20 > I would assume that the disposition of the ML would be gated by the = disposition of the work, which we > don't know yet. There is some probability that this would become a = standalone BOF / WG, so in that case it would find some use. >=20 > Regards > Marshall >=20 > =20 > On Oct 5, 2011, at 11:04 PM, Marshall Eubanks wrote: >=20 > > Similarly, VPN4DC should be of interest to the OPS area. This was = not > > approved as > > a BOF, but will be discussed in the L3VPN mailing list (now) and (if > > there is sufficient interest) > > in a L3VPN meeting in Taipei. > > > > You can find a brief description in = http://trac.tools.ietf.org/bof/trac/wiki > > > > Please direct discussion of VPN4DC to L3VPN. > > > > Regards > > Marshall Eubanks > > > > On Wed, Oct 5, 2011 at 10:33 AM, Romascanu, Dan (Dan) > > wrote: > >> Please see the message from Adrian about the Software Driven = Networks > >> (SDN) BOF approved for Taipei. As Adrian puts it ' The BoF is = nominally > >> in the Routing Area, but I expect considerable involvement from the = OPS > >> Area.' Scheduling will avoid conflict with the area meetings and to = the > >> possible extent to the other WGs in OPS whose participants could > >> contribute to this work (OPSAWG, NETCONF, NETMOD, V6OPS). The mail = list > >> is at http://www.lucidvision.com/mailman/listinfo/sdnp > >> > >> > >> > >> -----Original Message----- > >> From: Adrian Farrel [mailto:adrian@olddog.co.uk] > >> Sent: Tuesday, October 04, 2011 10:00 PM > >> To: sdnp@lucidvision.com > >> Cc: stbryant@cisco.com; Romascanu, Dan (Dan); rbonica@juniper.net > >> Subject: BoF in Taipei > >> > >> Hi SDN list, > >> > >> I wanted you to know that the IAB and IESG met today to discuss = BoFs for > >> Taipei. > >> > >> They have agreed that we will hold a BoF for SDN with a goal of > >> "discussing the > >> technology and identifying work items". The BoF is nominally in the > >> Routing > >> Area, but I expect considerable involvement from the OPS Area. > >> > >> That means that it will not be designated a "working group forming = BoF". > >> In > >> other words, the objective of the meeting will not be to discuss = the > >> precise > >> nature of what a new working group would do (charter, scope, = milestones, > >> documents). Rather, it will try to reach agreement on what the = topic > >> actually > >> is, what work is out there, what belongs in the IETF, who wants to = do > >> what, and > >> how it breaks into manageable units, etc.. > >> > >> We may find that the outcome is a clear new WG. We might find = pieces of > >> work > >> that belong in different existing WGs. We might find that all the = work > >> actually > >> belongs in another body. And we might find that there is no work to = be > >> done. > >> > >> Over the next couple of days I will work with Tom on an initial = draft > >> agenda for > >> the meeting which we will put to you for more debate and bashing. = We > >> have a 2 > >> hour slot, so we should be able to cover quite a lot. > >> > >> I will also appoint chairs for the BoF relatively soon so that they = can > >> take on > >> a guiding role leading up to the meeting. > >> > >> OK? > >> > >> Adrian > >> > >> _______________________________________________ > >> OPS-DIR mailing list > >> OPS-DIR@ietf.org > >> https://www.ietf.org/mailman/listinfo/ops-dir > >> > > _______________________________________________ > > OPS-DIR mailing list > > OPS-DIR@ietf.org > > https://www.ietf.org/mailman/listinfo/ops-dir >=20 >=20 --Apple-Mail-15-342581939 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii OK, do me a favor. I sent a note to vpn4dc@, and have since forwarded it to l3vpn@. I'm not a member of the latter. So let it through...

On Nov 1, 2011, at 6:13 AM, Marshall Eubanks wrote:


On Mon, Oct 31, 2011 at 5:33 PM, Fred Baker <fred@cisco.com> wrote:
what is the vpn4dc@ietf.org list being used for?


Not much at present. The VPN4DC BOF was turned into a special session of L3VPN, so I asked people not to use
the BOF VPN4DC mailing list. 

I would assume that the disposition of the ML would be gated by the disposition of the work, which we
don't know yet. There is some probability that this would become a standalone BOF / WG, so in that case it would find some use.

Regards
Marshall

 
On Oct 5, 2011, at 11:04 PM, Marshall Eubanks wrote:

> Similarly, VPN4DC should be of interest to the OPS area.  This was not
> approved as
> a BOF, but will be discussed in the L3VPN mailing list (now) and (if
> there is sufficient interest)
> in a L3VPN meeting in Taipei.
>
> You can find a brief description in http://trac.tools.ietf.org/bof/trac/wiki
>
> Please direct discussion of VPN4DC to L3VPN.
>
> Regards
> Marshall Eubanks
>
> On Wed, Oct 5, 2011 at 10:33 AM, Romascanu, Dan (Dan)
> <dromasca@avaya.com> wrote:
>> Please see the message from Adrian about the Software Driven Networks
>> (SDN) BOF approved for Taipei. As Adrian puts it ' The BoF is nominally
>> in the Routing Area, but I expect considerable involvement from the OPS
>> Area.' Scheduling will avoid conflict with the area meetings and to the
>> possible extent to the other WGs in OPS whose participants could
>> contribute to this work (OPSAWG, NETCONF, NETMOD, V6OPS). The mail list
>> is at http://www.lucidvision.com/mailman/listinfo/sdnp
>>
>>
>>
>> -----Original Message-----
>> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
>> Sent: Tuesday, October 04, 2011 10:00 PM
>> To: sdnp@lucidvision.com
>> Cc: stbryant@cisco.com; Romascanu, Dan (Dan); rbonica@juniper.net
>> Subject: BoF in Taipei
>>
>> Hi SDN list,
>>
>> I wanted you to know that the IAB and IESG met today to discuss BoFs for
>> Taipei.
>>
>> They have agreed that we will hold a BoF for SDN with a goal of
>> "discussing the
>> technology and identifying work items". The BoF is nominally in the
>> Routing
>> Area, but I expect considerable involvement from the OPS Area.
>>
>> That means that it will not be designated a "working group forming BoF".
>> In
>> other words, the objective of the meeting will not be to discuss the
>> precise
>> nature of what a new working group would do (charter, scope, milestones,
>> documents). Rather, it will try to reach agreement on what the topic
>> actually
>> is, what work is out there, what belongs in the IETF, who wants to do
>> what, and
>> how it breaks into manageable units, etc..
>>
>> We may find that the outcome is a clear new WG. We might find pieces of
>> work
>> that belong in different existing WGs. We might find that all the work
>> actually
>> belongs in another body. And we might find that there is no work to be
>> done.
>>
>> Over the next couple of days I will work with Tom on an initial draft
>> agenda for
>> the meeting which we will put to you for more debate and bashing. We
>> have a 2
>> hour slot, so we should be able to cover quite a lot.
>>
>> I will also appoint chairs for the BoF relatively soon so that they can
>> take on
>> a guiding role leading up to the meeting.
>>
>> OK?
>>
>> Adrian
>>
>> _______________________________________________
>> OPS-DIR mailing list
>> OPS-DIR@ietf.org
>> https://www.ietf.org/mailman/listinfo/ops-dir
>>
> _______________________________________________
> OPS-DIR mailing list
> OPS-DIR@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-dir



--Apple-Mail-15-342581939-- From fred@cisco.com Mon Oct 31 17:14:51 2011 Return-Path: X-Original-To: ops-area@ietfa.amsl.com Delivered-To: ops-area@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 507E611E8089; Mon, 31 Oct 2011 17:14:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.968 X-Spam-Level: X-Spam-Status: No, score=-104.968 tagged_above=-999 required=5 tests=[AWL=0.430, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_MED=-4, 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 dmGozveQvABf; Mon, 31 Oct 2011 17:14:50 -0700 (PDT) Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 2DFE411E8083; Mon, 31 Oct 2011 17:14:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=12954; q=dns/txt; s=iport; t=1320106490; x=1321316090; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=Nji1wUQzAFKrVTkVp8NxG6HdPbqyxoxkw9MXecaAFoA=; b=OJe+HDLTMrGxPD2VDhK9KN7T0tD4Sio6d3+BdI6kLPLVuLcy10VYhvOO PAcAivtaF1EgAynlOdGivyVXgRNTszeAz1E9adES349NGNJaa9gft//3L TD36lak5syb1XibtEki6jNoalG/pNOKJ9T/Gjqpeti9LiX+ioS+R1nQjN M=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvMAAK84r06rRDoH/2dsb2JhbABDmWOHfoUIgk2BBYFyAQEBAQIBAQEBDwFbCwUHBAsRBAEBAScHIQYfCAEIBhMJGYdgCJV4AZ5AiCFhBIgEjAqFLYUJhzY X-IronPort-AV: E=Sophos;i="4.69,435,1315180800"; d="scan'208,217";a="10293802" Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 01 Nov 2011 00:14:49 +0000 Received: from localhost (tky-vpn-client-231-167.cisco.com [10.70.231.167]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pA10Ek1r028090; Tue, 1 Nov 2011 00:14:47 GMT Received: from [127.0.0.1] by localhost (PGP Universal service); Tue, 01 Nov 2011 08:14:48 +0900 X-PGP-Universal: processed; by localhost on Tue, 01 Nov 2011 08:14:48 +0900 Mime-Version: 1.0 (Apple Message framework v1084) From: Fred Baker In-Reply-To: Date: Tue, 1 Nov 2011 08:14:30 +0800 Message-Id: <6128F539-C359-4FB6-85EC-B9F752764D53@cisco.com> References: <097EB222-ABD7-4F94-95EC-ABA8DA9AF02F@cisco.com> To: Marshall Eubanks X-Mailer: Apple Mail (2.1084) Content-Type: multipart/alternative; boundary=Apple-Mail-24-349370928 Cc: ops-dir@ietf.org, ops-area@ietf.org, ops-chairs@ietf.org Subject: Re: [OPS-AREA] [OPS-DIR] FW: BoF in Taipei X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2011 00:14:51 -0000 --Apple-Mail-24-349370928 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii thanks.=20 On Nov 1, 2011, at 7:59 AM, Marshall Eubanks wrote: >=20 >=20 > On Mon, Oct 31, 2011 at 7:55 PM, Marshall Eubanks = wrote: >=20 >=20 > On Mon, Oct 31, 2011 at 6:21 PM, Fred Baker wrote: > OK, do me a favor. I sent a note to vpn4dc@, and have since forwarded = it to l3vpn@. I'm not a member of the latter. So let it through... >=20 >=20 > Will do >=20 >=20 > Done.=20 >=20 > You might want to follow this thread >=20 > http://www.ietf.org/mail-archive/web/l3vpn/current/msg03072.html >=20 > Marshall >=20 > =20 > Marshall > =20 > On Nov 1, 2011, at 6:13 AM, Marshall Eubanks wrote: >=20 >>=20 >> On Mon, Oct 31, 2011 at 5:33 PM, Fred Baker wrote: >> what is the vpn4dc@ietf.org list being used for? >>=20 >>=20 >> Not much at present. The VPN4DC BOF was turned into a special session = of L3VPN, so I asked people not to use >> the BOF VPN4DC mailing list.=20 >>=20 >> I would assume that the disposition of the ML would be gated by the = disposition of the work, which we >> don't know yet. There is some probability that this would become a = standalone BOF / WG, so in that case it would find some use. >>=20 >> Regards >> Marshall >>=20 >> =20 >> On Oct 5, 2011, at 11:04 PM, Marshall Eubanks wrote: >>=20 >> > Similarly, VPN4DC should be of interest to the OPS area. This was = not >> > approved as >> > a BOF, but will be discussed in the L3VPN mailing list (now) and = (if >> > there is sufficient interest) >> > in a L3VPN meeting in Taipei. >> > >> > You can find a brief description in = http://trac.tools.ietf.org/bof/trac/wiki >> > >> > Please direct discussion of VPN4DC to L3VPN. >> > >> > Regards >> > Marshall Eubanks >> > >> > On Wed, Oct 5, 2011 at 10:33 AM, Romascanu, Dan (Dan) >> > wrote: >> >> Please see the message from Adrian about the Software Driven = Networks >> >> (SDN) BOF approved for Taipei. As Adrian puts it ' The BoF is = nominally >> >> in the Routing Area, but I expect considerable involvement from = the OPS >> >> Area.' Scheduling will avoid conflict with the area meetings and = to the >> >> possible extent to the other WGs in OPS whose participants could >> >> contribute to this work (OPSAWG, NETCONF, NETMOD, V6OPS). The mail = list >> >> is at http://www.lucidvision.com/mailman/listinfo/sdnp >> >> >> >> >> >> >> >> -----Original Message----- >> >> From: Adrian Farrel [mailto:adrian@olddog.co.uk] >> >> Sent: Tuesday, October 04, 2011 10:00 PM >> >> To: sdnp@lucidvision.com >> >> Cc: stbryant@cisco.com; Romascanu, Dan (Dan); rbonica@juniper.net >> >> Subject: BoF in Taipei >> >> >> >> Hi SDN list, >> >> >> >> I wanted you to know that the IAB and IESG met today to discuss = BoFs for >> >> Taipei. >> >> >> >> They have agreed that we will hold a BoF for SDN with a goal of >> >> "discussing the >> >> technology and identifying work items". The BoF is nominally in = the >> >> Routing >> >> Area, but I expect considerable involvement from the OPS Area. >> >> >> >> That means that it will not be designated a "working group forming = BoF". >> >> In >> >> other words, the objective of the meeting will not be to discuss = the >> >> precise >> >> nature of what a new working group would do (charter, scope, = milestones, >> >> documents). Rather, it will try to reach agreement on what the = topic >> >> actually >> >> is, what work is out there, what belongs in the IETF, who wants to = do >> >> what, and >> >> how it breaks into manageable units, etc.. >> >> >> >> We may find that the outcome is a clear new WG. We might find = pieces of >> >> work >> >> that belong in different existing WGs. We might find that all the = work >> >> actually >> >> belongs in another body. And we might find that there is no work = to be >> >> done. >> >> >> >> Over the next couple of days I will work with Tom on an initial = draft >> >> agenda for >> >> the meeting which we will put to you for more debate and bashing. = We >> >> have a 2 >> >> hour slot, so we should be able to cover quite a lot. >> >> >> >> I will also appoint chairs for the BoF relatively soon so that = they can >> >> take on >> >> a guiding role leading up to the meeting. >> >> >> >> OK? >> >> >> >> Adrian >> >> >> >> _______________________________________________ >> >> OPS-DIR mailing list >> >> OPS-DIR@ietf.org >> >> https://www.ietf.org/mailman/listinfo/ops-dir >> >> >> > _______________________________________________ >> > OPS-DIR mailing list >> > OPS-DIR@ietf.org >> > https://www.ietf.org/mailman/listinfo/ops-dir >>=20 >>=20 >=20 >=20 >=20 --Apple-Mail-24-349370928 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii thanks. 

On Nov 1, 2011, at 7:59 AM, Marshall Eubanks wrote:



On Mon, Oct 31, 2011 at 7:55 PM, Marshall Eubanks <marshall.eubanks@gmail.com> wrote:


On Mon, Oct 31, 2011 at 6:21 PM, Fred Baker <fred@cisco.com> wrote:
OK, do me a favor. I sent a note to vpn4dc@, and have since forwarded it to l3vpn@. I'm not a member of the latter. So let it through...


Will do


Done. 

You might want to follow this thread


Marshall

 
Marshall
 
On Nov 1, 2011, at 6:13 AM, Marshall Eubanks wrote:


On Mon, Oct 31, 2011 at 5:33 PM, Fred Baker <fred@cisco.com> wrote:
what is the vpn4dc@ietf.org list being used for?


Not much at present. The VPN4DC BOF was turned into a special session of L3VPN, so I asked people not to use
the BOF VPN4DC mailing list. 

I would assume that the disposition of the ML would be gated by the disposition of the work, which we
don't know yet. There is some probability that this would become a standalone BOF / WG, so in that case it would find some use.

Regards
Marshall

 
On Oct 5, 2011, at 11:04 PM, Marshall Eubanks wrote:

> Similarly, VPN4DC should be of interest to the OPS area.  This was not
> approved as
> a BOF, but will be discussed in the L3VPN mailing list (now) and (if
> there is sufficient interest)
> in a L3VPN meeting in Taipei.
>
> You can find a brief description in http://trac.tools.ietf.org/bof/trac/wiki
>
> Please direct discussion of VPN4DC to L3VPN.
>
> Regards
> Marshall Eubanks
>
> On Wed, Oct 5, 2011 at 10:33 AM, Romascanu, Dan (Dan)
> <dromasca@avaya.com> wrote:
>> Please see the message from Adrian about the Software Driven Networks
>> (SDN) BOF approved for Taipei. As Adrian puts it ' The BoF is nominally
>> in the Routing Area, but I expect considerable involvement from the OPS
>> Area.' Scheduling will avoid conflict with the area meetings and to the
>> possible extent to the other WGs in OPS whose participants could
>> contribute to this work (OPSAWG, NETCONF, NETMOD, V6OPS). The mail list
>> is at http://www.lucidvision.com/mailman/listinfo/sdnp
>>
>>
>>
>> -----Original Message-----
>> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
>> Sent: Tuesday, October 04, 2011 10:00 PM
>> To: sdnp@lucidvision.com
>> Cc: stbryant@cisco.com; Romascanu, Dan (Dan); rbonica@juniper.net
>> Subject: BoF in Taipei
>>
>> Hi SDN list,
>>
>> I wanted you to know that the IAB and IESG met today to discuss BoFs for
>> Taipei.
>>
>> They have agreed that we will hold a BoF for SDN with a goal of
>> "discussing the
>> technology and identifying work items". The BoF is nominally in the
>> Routing
>> Area, but I expect considerable involvement from the OPS Area.
>>
>> That means that it will not be designated a "working group forming BoF".
>> In
>> other words, the objective of the meeting will not be to discuss the
>> precise
>> nature of what a new working group would do (charter, scope, milestones,
>> documents). Rather, it will try to reach agreement on what the topic
>> actually
>> is, what work is out there, what belongs in the IETF, who wants to do
>> what, and
>> how it breaks into manageable units, etc..
>>
>> We may find that the outcome is a clear new WG. We might find pieces of
>> work
>> that belong in different existing WGs. We might find that all the work
>> actually
>> belongs in another body. And we might find that there is no work to be
>> done.
>>
>> Over the next couple of days I will work with Tom on an initial draft
>> agenda for
>> the meeting which we will put to you for more debate and bashing. We
>> have a 2
>> hour slot, so we should be able to cover quite a lot.
>>
>> I will also appoint chairs for the BoF relatively soon so that they can
>> take on
>> a guiding role leading up to the meeting.
>>
>> OK?
>>
>> Adrian
>>
>> _______________________________________________
>> OPS-DIR mailing list
>> OPS-DIR@ietf.org
>> https://www.ietf.org/mailman/listinfo/ops-dir
>>
> _______________________________________________
> OPS-DIR mailing list
> OPS-DIR@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-dir






--Apple-Mail-24-349370928--