
From marshall.eubanks@gmail.com  Mon Oct 31 15:13:15 2011
Return-Path: <marshall.eubanks@gmail.com>
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 BBE9B1F0C8B; Mon, 31 Oct 2011 15:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.826
X-Spam-Level: 
X-Spam-Status: No, score=-102.826 tagged_above=-999 required=5 tests=[AWL=-0.428, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 qdpplNdcsfut; Mon, 31 Oct 2011 15:13:14 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5D62A1F0C6D; Mon, 31 Oct 2011 15:13:14 -0700 (PDT)
Received: by qadc10 with SMTP id c10so6876353qad.31 for <multiple recipients>; Mon, 31 Oct 2011 15:13:14 -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=HK0X+h9zLvmYQwVKNWby92T+FNgddnancaqgVtA1KF0=; b=UuZYYTx9QB/6bfsZNG/SpQ3xdn73cBrvi4ClSBBxbltGx8IFKyUSPFbNrkPXk7uCu1 Gk3lDixe2DJcGO0OS9m/6ArAJrS6pslOdVTBSDTYl9qKCQy9gIpbLPdD2G6PMYzhaZCJ Rz6EpAGc0PiyaiOrwYp5lU0B+2BLxkOpdd01s=
MIME-Version: 1.0
Received: by 10.182.17.3 with SMTP id k3mr3264255obd.59.1320099193723; Mon, 31 Oct 2011 15:13:13 -0700 (PDT)
Received: by 10.182.14.65 with HTTP; Mon, 31 Oct 2011 15:13:13 -0700 (PDT)
In-Reply-To: <097EB222-ABD7-4F94-95EC-ABA8DA9AF02F@cisco.com>
References: <EDC652A26FB23C4EB6384A4584434A0403BE8EBF@307622ANEX5.global.avaya.com> <CAJNg7VL72GUbCJaQkPh433U+crgBFwNBsb-dOkaUygwbG3FbVg@mail.gmail.com> <097EB222-ABD7-4F94-95EC-ABA8DA9AF02F@cisco.com>
Date: Mon, 31 Oct 2011 18:13:13 -0400
Message-ID: <CAJNg7V+XW=DJH_BBKfhYraB3w_mkzrRHhbAnr=r_h_jGXNbnUw@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Fred Baker <fred@cisco.com>
Content-Type: multipart/alternative; boundary=f46d04447247829d0a04b09f8b59
X-Mailman-Approved-At: Tue, 01 Nov 2011 07:47:52 -0700
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 <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Oct 2011 22:13:15 -0000

--f46d04447247829d0a04b09f8b59
Content-Type: text/plain; charset=ISO-8859-1

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
>
>

--f46d04447247829d0a04b09f8b59
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote">On Mon, Oct 31, 2011 at 5:33 PM, Fred Baker =
<span dir=3D"ltr">&lt;<a href=3D"mailto:fred@cisco.com">fred@cisco.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
what is the <a href=3D"mailto:vpn4dc@ietf.org">vpn4dc@ietf.org</a> list bei=
ng used for?<br>
<div><div></div><div class=3D"h5"><br></div></div></blockquote><div><br></d=
iv><div>Not much at present. The VPN4DC BOF was turned into a special sessi=
on of L3VPN, so I asked people not to use<br></div><div>the BOF VPN4DC mail=
ing list.=A0</div>
<div><br></div><div>I would assume that the disposition of the ML would be =
gated by the disposition of the work, which we</div><div>don&#39;t know yet=
. There is some probability that this would become a standalone BOF / WG, s=
o in that case it would find some use.</div>
<div><br></div><div>Regards</div><div>Marshall</div><div><br></div><div>=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex;"><div><div class=3D"h5">
On Oct 5, 2011, at 11:04 PM, Marshall Eubanks wrote:<br>
<br>
&gt; Similarly, VPN4DC should be of interest to the OPS area. =A0This was n=
ot<br>
&gt; approved as<br>
&gt; a BOF, but will be discussed in the L3VPN mailing list (now) and (if<b=
r>
&gt; there is sufficient interest)<br>
&gt; in a L3VPN meeting in Taipei.<br>
&gt;<br>
&gt; You can find a brief description in <a href=3D"http://trac.tools.ietf.=
org/bof/trac/wiki" target=3D"_blank">http://trac.tools.ietf.org/bof/trac/wi=
ki</a><br>
&gt;<br>
&gt; Please direct discussion of VPN4DC to L3VPN.<br>
&gt;<br>
&gt; Regards<br>
&gt; Marshall Eubanks<br>
&gt;<br>
&gt; On Wed, Oct 5, 2011 at 10:33 AM, Romascanu, Dan (Dan)<br>
&gt; &lt;<a href=3D"mailto:dromasca@avaya.com">dromasca@avaya.com</a>&gt; w=
rote:<br>
&gt;&gt; Please see the message from Adrian about the Software Driven Netwo=
rks<br>
&gt;&gt; (SDN) BOF approved for Taipei. As Adrian puts it &#39; The BoF is =
nominally<br>
&gt;&gt; in the Routing Area, but I expect considerable involvement from th=
e OPS<br>
&gt;&gt; Area.&#39; Scheduling will avoid conflict with the area meetings a=
nd to the<br>
&gt;&gt; possible extent to the other WGs in OPS whose participants could<b=
r>
&gt;&gt; contribute to this work (OPSAWG, NETCONF, NETMOD, V6OPS). The mail=
 list<br>
&gt;&gt; is at <a href=3D"http://www.lucidvision.com/mailman/listinfo/sdnp"=
 target=3D"_blank">http://www.lucidvision.com/mailman/listinfo/sdnp</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: Adrian Farrel [mailto:<a href=3D"mailto:adrian@olddog.co.uk"=
>adrian@olddog.co.uk</a>]<br>
&gt;&gt; Sent: Tuesday, October 04, 2011 10:00 PM<br>
&gt;&gt; To: <a href=3D"mailto:sdnp@lucidvision.com">sdnp@lucidvision.com</=
a><br>
&gt;&gt; Cc: <a href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</a>; =
Romascanu, Dan (Dan); <a href=3D"mailto:rbonica@juniper.net">rbonica@junipe=
r.net</a><br>
&gt;&gt; Subject: BoF in Taipei<br>
&gt;&gt;<br>
&gt;&gt; Hi SDN list,<br>
&gt;&gt;<br>
&gt;&gt; I wanted you to know that the IAB and IESG met today to discuss Bo=
Fs for<br>
&gt;&gt; Taipei.<br>
&gt;&gt;<br>
&gt;&gt; They have agreed that we will hold a BoF for SDN with a goal of<br=
>
&gt;&gt; &quot;discussing the<br>
&gt;&gt; technology and identifying work items&quot;. The BoF is nominally =
in the<br>
&gt;&gt; Routing<br>
&gt;&gt; Area, but I expect considerable involvement from the OPS Area.<br>
&gt;&gt;<br>
&gt;&gt; That means that it will not be designated a &quot;working group fo=
rming BoF&quot;.<br>
&gt;&gt; In<br>
&gt;&gt; other words, the objective of the meeting will not be to discuss t=
he<br>
&gt;&gt; precise<br>
&gt;&gt; nature of what a new working group would do (charter, scope, miles=
tones,<br>
&gt;&gt; documents). Rather, it will try to reach agreement on what the top=
ic<br>
&gt;&gt; actually<br>
&gt;&gt; is, what work is out there, what belongs in the IETF, who wants to=
 do<br>
&gt;&gt; what, and<br>
&gt;&gt; how it breaks into manageable units, etc..<br>
&gt;&gt;<br>
&gt;&gt; We may find that the outcome is a clear new WG. We might find piec=
es of<br>
&gt;&gt; work<br>
&gt;&gt; that belong in different existing WGs. We might find that all the =
work<br>
&gt;&gt; actually<br>
&gt;&gt; belongs in another body. And we might find that there is no work t=
o be<br>
&gt;&gt; done.<br>
&gt;&gt;<br>
&gt;&gt; Over the next couple of days I will work with Tom on an initial dr=
aft<br>
&gt;&gt; agenda for<br>
&gt;&gt; the meeting which we will put to you for more debate and bashing. =
We<br>
&gt;&gt; have a 2<br>
&gt;&gt; hour slot, so we should be able to cover quite a lot.<br>
&gt;&gt;<br>
&gt;&gt; I will also appoint chairs for the BoF relatively soon so that the=
y can<br>
&gt;&gt; take on<br>
&gt;&gt; a guiding role leading up to the meeting.<br>
&gt;&gt;<br>
&gt;&gt; OK?<br>
&gt;&gt;<br>
&gt;&gt; Adrian<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; OPS-DIR mailing list<br>
&gt;&gt; <a href=3D"mailto:OPS-DIR@ietf.org">OPS-DIR@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ops-dir" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/ops-dir</a><br>
&gt;&gt;<br>
&gt; _______________________________________________<br>
&gt; OPS-DIR mailing list<br>
&gt; <a href=3D"mailto:OPS-DIR@ietf.org">OPS-DIR@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ops-dir" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/ops-dir</a><br>
<br>
</div></div></blockquote></div><br>

--f46d04447247829d0a04b09f8b59--

From marshall.eubanks@gmail.com  Mon Oct 31 16:55:19 2011
Return-Path: <marshall.eubanks@gmail.com>
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 CE12D11E83BA; Mon, 31 Oct 2011 16:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.822
X-Spam-Level: 
X-Spam-Status: No, score=-102.822 tagged_above=-999 required=5 tests=[AWL=-0.424, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 kvJm5nr230bU; Mon, 31 Oct 2011 16:55:18 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 6246E11E840E; Mon, 31 Oct 2011 16:55:17 -0700 (PDT)
Received: by qyk31 with SMTP id 31so6539654qyk.10 for <multiple recipients>; Mon, 31 Oct 2011 16:55:17 -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=mUjfo6799o7UWmOMCoEif2hkkDp0nJLvApvewQ98U8g=; b=H2QnhknCiasy3lDtZUd8309bc/pOJGx/30R29lQHa3DvuApj7SSjZNjgBEsNkH+Sdr KO0M/snr8XX5FEiPhDxHOoDO7bxsRbWdSMPrVRRdKE1Xz590+oEvT3XzDymWGUxheGJU AbeRen/a7TP1zBtIuZdsXgNm+ClpY/Zg27eEY=
MIME-Version: 1.0
Received: by 10.182.111.33 with SMTP id if1mr3338687obb.29.1320105316709; Mon, 31 Oct 2011 16:55:16 -0700 (PDT)
Received: by 10.182.14.65 with HTTP; Mon, 31 Oct 2011 16:55:16 -0700 (PDT)
In-Reply-To: <C8D1B1DB-587F-4B5E-874B-90998EF2F38F@cisco.com>
References: <EDC652A26FB23C4EB6384A4584434A0403BE8EBF@307622ANEX5.global.avaya.com> <CAJNg7VL72GUbCJaQkPh433U+crgBFwNBsb-dOkaUygwbG3FbVg@mail.gmail.com> <097EB222-ABD7-4F94-95EC-ABA8DA9AF02F@cisco.com> <CAJNg7V+XW=DJH_BBKfhYraB3w_mkzrRHhbAnr=r_h_jGXNbnUw@mail.gmail.com> <C8D1B1DB-587F-4B5E-874B-90998EF2F38F@cisco.com>
Date: Mon, 31 Oct 2011 19:55:16 -0400
Message-ID: <CAJNg7VLWjshM0oza9pB_hGA+PKEF-nb46GbvmkiH_RHGq1VUeQ@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Fred Baker <fred@cisco.com>
Content-Type: multipart/alternative; boundary=14dae9399b9377f4f004b0a0f897
X-Mailman-Approved-At: Tue, 01 Nov 2011 07:47:52 -0700
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 <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Oct 2011 23:55:20 -0000

--14dae9399b9377f4f004b0a0f897
Content-Type: text/plain; charset=ISO-8859-1

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

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
>>
>>
>
>

--14dae9399b9377f4f004b0a0f897
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div><br><br><div class=3D"gmail_quote">On Mon, Oct 31, 2011 at 6:21 PM, Fr=
ed Baker <span dir=3D"ltr">&lt;<a href=3D"mailto:fred@cisco.com">fred@cisco=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style=3D"word-wrap:break-word">OK, do me a favor. I sent a note to vpn=
4dc@, and have since forwarded it to l3vpn@. I&#39;m not a member of the la=
tter. So let it through...<div><div></div><div class=3D"h5"><div><br></div>
</div></div></div></blockquote><div><br></div><div>Will do<div><br></div><d=
iv>Marshall</div></div><div>=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div s=
tyle=3D"word-wrap:break-word">
<div><div class=3D"h5"><div><div><div>On Nov 1, 2011, at 6:13 AM, Marshall =
Eubanks wrote:</div><br><blockquote type=3D"cite"><br><div class=3D"gmail_q=
uote">On Mon, Oct 31, 2011 at 5:33 PM, Fred Baker <span dir=3D"ltr">&lt;<a =
href=3D"mailto:fred@cisco.com" target=3D"_blank">fred@cisco.com</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
what is the <a href=3D"mailto:vpn4dc@ietf.org" target=3D"_blank">vpn4dc@iet=
f.org</a> list being used for?<br>
<div><div></div><div><br></div></div></blockquote><div><br></div><div>Not m=
uch at present. The VPN4DC BOF was turned into a special session of L3VPN, =
so I asked people not to use<br></div><div>the BOF VPN4DC mailing list.=A0<=
/div>

<div><br></div><div>I would assume that the disposition of the ML would be =
gated by the disposition of the work, which we</div><div>don&#39;t know yet=
. There is some probability that this would become a standalone BOF / WG, s=
o in that case it would find some use.</div>

<div><br></div><div>Regards</div><div>Marshall</div><div><br></div><div>=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div><div>
On Oct 5, 2011, at 11:04 PM, Marshall Eubanks wrote:<br>
<br>
&gt; Similarly, VPN4DC should be of interest to the OPS area. =A0This was n=
ot<br>
&gt; approved as<br>
&gt; a BOF, but will be discussed in the L3VPN mailing list (now) and (if<b=
r>
&gt; there is sufficient interest)<br>
&gt; in a L3VPN meeting in Taipei.<br>
&gt;<br>
&gt; You can find a brief description in <a href=3D"http://trac.tools.ietf.=
org/bof/trac/wiki" target=3D"_blank">http://trac.tools.ietf.org/bof/trac/wi=
ki</a><br>
&gt;<br>
&gt; Please direct discussion of VPN4DC to L3VPN.<br>
&gt;<br>
&gt; Regards<br>
&gt; Marshall Eubanks<br>
&gt;<br>
&gt; On Wed, Oct 5, 2011 at 10:33 AM, Romascanu, Dan (Dan)<br>
&gt; &lt;<a href=3D"mailto:dromasca@avaya.com" target=3D"_blank">dromasca@a=
vaya.com</a>&gt; wrote:<br>
&gt;&gt; Please see the message from Adrian about the Software Driven Netwo=
rks<br>
&gt;&gt; (SDN) BOF approved for Taipei. As Adrian puts it &#39; The BoF is =
nominally<br>
&gt;&gt; in the Routing Area, but I expect considerable involvement from th=
e OPS<br>
&gt;&gt; Area.&#39; Scheduling will avoid conflict with the area meetings a=
nd to the<br>
&gt;&gt; possible extent to the other WGs in OPS whose participants could<b=
r>
&gt;&gt; contribute to this work (OPSAWG, NETCONF, NETMOD, V6OPS). The mail=
 list<br>
&gt;&gt; is at <a href=3D"http://www.lucidvision.com/mailman/listinfo/sdnp"=
 target=3D"_blank">http://www.lucidvision.com/mailman/listinfo/sdnp</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: Adrian Farrel [mailto:<a href=3D"mailto:adrian@olddog.co.uk"=
 target=3D"_blank">adrian@olddog.co.uk</a>]<br>
&gt;&gt; Sent: Tuesday, October 04, 2011 10:00 PM<br>
&gt;&gt; To: <a href=3D"mailto:sdnp@lucidvision.com" target=3D"_blank">sdnp=
@lucidvision.com</a><br>
&gt;&gt; Cc: <a href=3D"mailto:stbryant@cisco.com" target=3D"_blank">stbrya=
nt@cisco.com</a>; Romascanu, Dan (Dan); <a href=3D"mailto:rbonica@juniper.n=
et" target=3D"_blank">rbonica@juniper.net</a><br>
&gt;&gt; Subject: BoF in Taipei<br>
&gt;&gt;<br>
&gt;&gt; Hi SDN list,<br>
&gt;&gt;<br>
&gt;&gt; I wanted you to know that the IAB and IESG met today to discuss Bo=
Fs for<br>
&gt;&gt; Taipei.<br>
&gt;&gt;<br>
&gt;&gt; They have agreed that we will hold a BoF for SDN with a goal of<br=
>
&gt;&gt; &quot;discussing the<br>
&gt;&gt; technology and identifying work items&quot;. The BoF is nominally =
in the<br>
&gt;&gt; Routing<br>
&gt;&gt; Area, but I expect considerable involvement from the OPS Area.<br>
&gt;&gt;<br>
&gt;&gt; That means that it will not be designated a &quot;working group fo=
rming BoF&quot;.<br>
&gt;&gt; In<br>
&gt;&gt; other words, the objective of the meeting will not be to discuss t=
he<br>
&gt;&gt; precise<br>
&gt;&gt; nature of what a new working group would do (charter, scope, miles=
tones,<br>
&gt;&gt; documents). Rather, it will try to reach agreement on what the top=
ic<br>
&gt;&gt; actually<br>
&gt;&gt; is, what work is out there, what belongs in the IETF, who wants to=
 do<br>
&gt;&gt; what, and<br>
&gt;&gt; how it breaks into manageable units, etc..<br>
&gt;&gt;<br>
&gt;&gt; We may find that the outcome is a clear new WG. We might find piec=
es of<br>
&gt;&gt; work<br>
&gt;&gt; that belong in different existing WGs. We might find that all the =
work<br>
&gt;&gt; actually<br>
&gt;&gt; belongs in another body. And we might find that there is no work t=
o be<br>
&gt;&gt; done.<br>
&gt;&gt;<br>
&gt;&gt; Over the next couple of days I will work with Tom on an initial dr=
aft<br>
&gt;&gt; agenda for<br>
&gt;&gt; the meeting which we will put to you for more debate and bashing. =
We<br>
&gt;&gt; have a 2<br>
&gt;&gt; hour slot, so we should be able to cover quite a lot.<br>
&gt;&gt;<br>
&gt;&gt; I will also appoint chairs for the BoF relatively soon so that the=
y can<br>
&gt;&gt; take on<br>
&gt;&gt; a guiding role leading up to the meeting.<br>
&gt;&gt;<br>
&gt;&gt; OK?<br>
&gt;&gt;<br>
&gt;&gt; Adrian<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; OPS-DIR mailing list<br>
&gt;&gt; <a href=3D"mailto:OPS-DIR@ietf.org" target=3D"_blank">OPS-DIR@ietf=
.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ops-dir" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/ops-dir</a><br>
&gt;&gt;<br>
&gt; _______________________________________________<br>
&gt; OPS-DIR mailing list<br>
&gt; <a href=3D"mailto:OPS-DIR@ietf.org" target=3D"_blank">OPS-DIR@ietf.org=
</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ops-dir" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/ops-dir</a><br>
<br>
</div></div></blockquote></div><br>
</blockquote></div><br></div></div></div></div></blockquote></div><br></div=
>

--14dae9399b9377f4f004b0a0f897--

From marshall.eubanks@gmail.com  Mon Oct 31 16:59:08 2011
Return-Path: <marshall.eubanks@gmail.com>
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 CA4BC11E8421; Mon, 31 Oct 2011 16:59:08 -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.415, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 jGLw+ZjyP36j; Mon, 31 Oct 2011 16:59:07 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 721C411E840D; Mon, 31 Oct 2011 16:59:07 -0700 (PDT)
Received: by qyk34 with SMTP id 34so4221278qyk.10 for <multiple recipients>; Mon, 31 Oct 2011 16:59:07 -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=cIZB6KaQx6vbnuv/dsO1/IG4YlS1qwnDZRBBn9MWaZs=; b=Co1g5nSl8ep1b9NQe/jgWAWamgpyKUl424AzLDCrK5ds19Ro1z1YgdR69QG7uq6gm1 BuiTI+cGJ88CHI7XrBjgXroUrgwVlEbDUCWe6iavxXubzVAaUUKLweAFKw+s6WrtXmkv ca09ZksZed53AMihNBAHWwP3rMvWjYDuQpFb0=
MIME-Version: 1.0
Received: by 10.182.17.3 with SMTP id k3mr3323402obd.59.1320105546755; Mon, 31 Oct 2011 16:59:06 -0700 (PDT)
Received: by 10.182.14.65 with HTTP; Mon, 31 Oct 2011 16:59:06 -0700 (PDT)
In-Reply-To: <CAJNg7VLWjshM0oza9pB_hGA+PKEF-nb46GbvmkiH_RHGq1VUeQ@mail.gmail.com>
References: <EDC652A26FB23C4EB6384A4584434A0403BE8EBF@307622ANEX5.global.avaya.com> <CAJNg7VL72GUbCJaQkPh433U+crgBFwNBsb-dOkaUygwbG3FbVg@mail.gmail.com> <097EB222-ABD7-4F94-95EC-ABA8DA9AF02F@cisco.com> <CAJNg7V+XW=DJH_BBKfhYraB3w_mkzrRHhbAnr=r_h_jGXNbnUw@mail.gmail.com> <C8D1B1DB-587F-4B5E-874B-90998EF2F38F@cisco.com> <CAJNg7VLWjshM0oza9pB_hGA+PKEF-nb46GbvmkiH_RHGq1VUeQ@mail.gmail.com>
Date: Mon, 31 Oct 2011 19:59:06 -0400
Message-ID: <CAJNg7V+Dr42QZk-odcc_chJKwmaLjMkSWD_wCr7NvVkWo73WWQ@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Fred Baker <fred@cisco.com>
Content-Type: multipart/alternative; boundary=f46d044472472e2cab04b0a10692
X-Mailman-Approved-At: Tue, 01 Nov 2011 07:47:52 -0700
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 <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Oct 2011 23:59:09 -0000

--f46d044472472e2cab04b0a10692
Content-Type: text/plain; charset=ISO-8859-1

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

http://www.ietf.org/mail-archive/web/l3vpn/current/msg03072.html

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
>>>
>>>
>>
>>
>

--f46d044472472e2cab04b0a10692
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Mon, Oct 31, 2011 at 7:55 PM, Marshal=
l Eubanks <span dir=3D"ltr">&lt;<a href=3D"mailto:marshall.eubanks@gmail.co=
m">marshall.eubanks@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex;">
<div><br><br><div class=3D"gmail_quote"><div class=3D"im">On Mon, Oct 31, 2=
011 at 6:21 PM, Fred Baker <span dir=3D"ltr">&lt;<a href=3D"mailto:fred@cis=
co.com" target=3D"_blank">fred@cisco.com</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">

<div style=3D"word-wrap:break-word">OK, do me a favor. I sent a note to vpn=
4dc@, and have since forwarded it to l3vpn@. I&#39;m not a member of the la=
tter. So let it through...<div><div></div><div><div><br></div>
</div></div></div></blockquote><div><br></div></div><div>Will do<div><br></=
div></div></div></div></blockquote><div><br></div><div>Done.=A0</div><div><=
br></div><div>You might want to follow this thread</div><div><br></div><div=
>
<a href=3D"http://www.ietf.org/mail-archive/web/l3vpn/current/msg03072.html=
">http://www.ietf.org/mail-archive/web/l3vpn/current/msg03072.html</a></div=
><div><br></div><div>Marshall</div><div><br></div><div>=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex;">
<div><div class=3D"gmail_quote"><div><div></div><font color=3D"#888888"><di=
v>Marshall</div></font></div><div><div></div><div class=3D"h5"><div>=A0</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word">
<div><div><div><div><div>On Nov 1, 2011, at 6:13 AM, Marshall Eubanks wrote=
:</div><br><blockquote type=3D"cite"><br><div class=3D"gmail_quote">On Mon,=
 Oct 31, 2011 at 5:33 PM, Fred Baker <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:fred@cisco.com" target=3D"_blank">fred@cisco.com</a>&gt;</span> wrote:<br=
>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
what is the <a href=3D"mailto:vpn4dc@ietf.org" target=3D"_blank">vpn4dc@iet=
f.org</a> list being used for?<br>
<div><div></div><div><br></div></div></blockquote><div><br></div><div>Not m=
uch at present. The VPN4DC BOF was turned into a special session of L3VPN, =
so I asked people not to use<br></div><div>the BOF VPN4DC mailing list.=A0<=
/div>


<div><br></div><div>I would assume that the disposition of the ML would be =
gated by the disposition of the work, which we</div><div>don&#39;t know yet=
. There is some probability that this would become a standalone BOF / WG, s=
o in that case it would find some use.</div>


<div><br></div><div>Regards</div><div>Marshall</div><div><br></div><div>=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div><div>
On Oct 5, 2011, at 11:04 PM, Marshall Eubanks wrote:<br>
<br>
&gt; Similarly, VPN4DC should be of interest to the OPS area. =A0This was n=
ot<br>
&gt; approved as<br>
&gt; a BOF, but will be discussed in the L3VPN mailing list (now) and (if<b=
r>
&gt; there is sufficient interest)<br>
&gt; in a L3VPN meeting in Taipei.<br>
&gt;<br>
&gt; You can find a brief description in <a href=3D"http://trac.tools.ietf.=
org/bof/trac/wiki" target=3D"_blank">http://trac.tools.ietf.org/bof/trac/wi=
ki</a><br>
&gt;<br>
&gt; Please direct discussion of VPN4DC to L3VPN.<br>
&gt;<br>
&gt; Regards<br>
&gt; Marshall Eubanks<br>
&gt;<br>
&gt; On Wed, Oct 5, 2011 at 10:33 AM, Romascanu, Dan (Dan)<br>
&gt; &lt;<a href=3D"mailto:dromasca@avaya.com" target=3D"_blank">dromasca@a=
vaya.com</a>&gt; wrote:<br>
&gt;&gt; Please see the message from Adrian about the Software Driven Netwo=
rks<br>
&gt;&gt; (SDN) BOF approved for Taipei. As Adrian puts it &#39; The BoF is =
nominally<br>
&gt;&gt; in the Routing Area, but I expect considerable involvement from th=
e OPS<br>
&gt;&gt; Area.&#39; Scheduling will avoid conflict with the area meetings a=
nd to the<br>
&gt;&gt; possible extent to the other WGs in OPS whose participants could<b=
r>
&gt;&gt; contribute to this work (OPSAWG, NETCONF, NETMOD, V6OPS). The mail=
 list<br>
&gt;&gt; is at <a href=3D"http://www.lucidvision.com/mailman/listinfo/sdnp"=
 target=3D"_blank">http://www.lucidvision.com/mailman/listinfo/sdnp</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: Adrian Farrel [mailto:<a href=3D"mailto:adrian@olddog.co.uk"=
 target=3D"_blank">adrian@olddog.co.uk</a>]<br>
&gt;&gt; Sent: Tuesday, October 04, 2011 10:00 PM<br>
&gt;&gt; To: <a href=3D"mailto:sdnp@lucidvision.com" target=3D"_blank">sdnp=
@lucidvision.com</a><br>
&gt;&gt; Cc: <a href=3D"mailto:stbryant@cisco.com" target=3D"_blank">stbrya=
nt@cisco.com</a>; Romascanu, Dan (Dan); <a href=3D"mailto:rbonica@juniper.n=
et" target=3D"_blank">rbonica@juniper.net</a><br>
&gt;&gt; Subject: BoF in Taipei<br>
&gt;&gt;<br>
&gt;&gt; Hi SDN list,<br>
&gt;&gt;<br>
&gt;&gt; I wanted you to know that the IAB and IESG met today to discuss Bo=
Fs for<br>
&gt;&gt; Taipei.<br>
&gt;&gt;<br>
&gt;&gt; They have agreed that we will hold a BoF for SDN with a goal of<br=
>
&gt;&gt; &quot;discussing the<br>
&gt;&gt; technology and identifying work items&quot;. The BoF is nominally =
in the<br>
&gt;&gt; Routing<br>
&gt;&gt; Area, but I expect considerable involvement from the OPS Area.<br>
&gt;&gt;<br>
&gt;&gt; That means that it will not be designated a &quot;working group fo=
rming BoF&quot;.<br>
&gt;&gt; In<br>
&gt;&gt; other words, the objective of the meeting will not be to discuss t=
he<br>
&gt;&gt; precise<br>
&gt;&gt; nature of what a new working group would do (charter, scope, miles=
tones,<br>
&gt;&gt; documents). Rather, it will try to reach agreement on what the top=
ic<br>
&gt;&gt; actually<br>
&gt;&gt; is, what work is out there, what belongs in the IETF, who wants to=
 do<br>
&gt;&gt; what, and<br>
&gt;&gt; how it breaks into manageable units, etc..<br>
&gt;&gt;<br>
&gt;&gt; We may find that the outcome is a clear new WG. We might find piec=
es of<br>
&gt;&gt; work<br>
&gt;&gt; that belong in different existing WGs. We might find that all the =
work<br>
&gt;&gt; actually<br>
&gt;&gt; belongs in another body. And we might find that there is no work t=
o be<br>
&gt;&gt; done.<br>
&gt;&gt;<br>
&gt;&gt; Over the next couple of days I will work with Tom on an initial dr=
aft<br>
&gt;&gt; agenda for<br>
&gt;&gt; the meeting which we will put to you for more debate and bashing. =
We<br>
&gt;&gt; have a 2<br>
&gt;&gt; hour slot, so we should be able to cover quite a lot.<br>
&gt;&gt;<br>
&gt;&gt; I will also appoint chairs for the BoF relatively soon so that the=
y can<br>
&gt;&gt; take on<br>
&gt;&gt; a guiding role leading up to the meeting.<br>
&gt;&gt;<br>
&gt;&gt; OK?<br>
&gt;&gt;<br>
&gt;&gt; Adrian<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; OPS-DIR mailing list<br>
&gt;&gt; <a href=3D"mailto:OPS-DIR@ietf.org" target=3D"_blank">OPS-DIR@ietf=
.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ops-dir" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/ops-dir</a><br>
&gt;&gt;<br>
&gt; _______________________________________________<br>
&gt; OPS-DIR mailing list<br>
&gt; <a href=3D"mailto:OPS-DIR@ietf.org" target=3D"_blank">OPS-DIR@ietf.org=
</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ops-dir" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/ops-dir</a><br>
<br>
</div></div></blockquote></div><br>
</blockquote></div><br></div></div></div></div></blockquote></div></div></d=
iv><br></div>
</blockquote></div><br>

--f46d044472472e2cab04b0a10692--

From dromasca@avaya.com  Thu Nov  3 06:07:29 2011
Return-Path: <dromasca@avaya.com>
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 77ED811E810B for <ops-area@ietfa.amsl.com>; Thu,  3 Nov 2011 06:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.33
X-Spam-Level: 
X-Spam-Status: No, score=-103.33 tagged_above=-999 required=5 tests=[AWL=0.269, 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 AMNtbO-+3Lvs for <ops-area@ietfa.amsl.com>; Thu,  3 Nov 2011 06:07:28 -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 97B5F11E80AC for <ops-area@ietf.org>; Thu,  3 Nov 2011 06:07:28 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AswJAFqRsk7GmAcF/2dsb2JhbABEmj+EAAOKFYEfgQWBdAEBAxIeClEBFRUGDAwHVwEEGwEZh2iUbYQSnBGIPWIEmWiMFg
X-IronPort-AV: E=Sophos;i="4.69,449,1315195200"; d="scan'208";a="312621546"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 03 Nov 2011 09:07:27 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 03 Nov 2011 09:04:53 -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: Thu, 3 Nov 2011 14:07:25 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A04048EDBE8@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: agenda for the OPSAREA meeting in Taipei
thread-index: AcyaKYgWD1pw2/vjS86oyPwtcexvMg==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Subject: [OPS-AREA] agenda for the OPSAREA meeting in Taipei
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 13:07:29 -0000

An update of the agenda of the OPSAREA open meeting is available at
http://www.ietf.org/proceedings/82/agenda/opsarea.txt

Comments and other proposals for agenda items are welcome.=20

Thanks and Regards,

Dan
=20




From dromasca@avaya.com  Sat Nov 12 17:43:46 2011
Return-Path: <dromasca@avaya.com>
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 74AF511E8082 for <ops-area@ietfa.amsl.com>; Sat, 12 Nov 2011 17:43:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.368
X-Spam-Level: 
X-Spam-Status: No, score=-103.368 tagged_above=-999 required=5 tests=[AWL=0.231, 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 fUuZopyBGsYL for <ops-area@ietfa.amsl.com>; Sat, 12 Nov 2011 17:43:46 -0800 (PST)
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 C82AB11E808B for <ops-area@ietf.org>; Sat, 12 Nov 2011 17:43:45 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ak4JAFogv06HCzI1/2dsb2JhbABCqSCBD4EFgXQBAQMSHgpRARUVBgwMB1cBBBsanmeEFZo8hmqCMmMEmgiMIA
X-IronPort-AV: E=Sophos;i="4.69,501,1315195200"; d="scan'208";a="277266470"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 12 Nov 2011 20:43:43 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 12 Nov 2011 20:32:33 -0500
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: Sun, 13 Nov 2011 02:43:40 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0404E03398@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: OPS-AREA open office hours
thread-index: Acyhpas6chVbt2TjSDGuaW8ooOb5zQ==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Subject: [OPS-AREA] OPS-AREA open office hours
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Nov 2011 01:43:46 -0000

The OPS Area open office hours will take place on Monday 13:00 to 15:00
in room 3F South Lounge. Please come to talk to us on any WG or area
items, or about new proposals, or about any other IETF-related business.


Ron and Dan





From dromasca@avaya.com  Thu Nov 17 18:04:14 2011
Return-Path: <dromasca@avaya.com>
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 1338811E808A; Thu, 17 Nov 2011 18:04:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.381
X-Spam-Level: 
X-Spam-Status: No, score=-103.381 tagged_above=-999 required=5 tests=[AWL=0.218, 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 4P-7ZCs2gZ-W; Thu, 17 Nov 2011 18:04:13 -0800 (PST)
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 2A95511E80C0; Thu, 17 Nov 2011 18:04:13 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ak4JAMq8xU7GmAcF/2dsb2JhbABCqS6BFYEFgXQBAQMSHgo/EgEVFQYMAQsHVwEEGxqiZ5tAhwKCMmMEmg+MIw
X-IronPort-AV: E=Sophos;i="4.69,530,1315195200"; d="scan'208";a="278069853"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 17 Nov 2011 21:03:54 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 17 Nov 2011 21:02:36 -0500
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: Fri, 18 Nov 2011 03:03:50 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0405298240@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: CAPWAP WG mail list closed
thread-index: AcylllCm38vafjXVTAmMrbbdise7ng==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Cc: ops-dir@ietf.org
Subject: [OPS-AREA] CAPWAP WG mail list closed
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2011 02:04:14 -0000

One and a half year after the conclusion of the CAPWAP WG I have decided
together with the chairs and the list host to shut down the mail list
which practically had zero useful traffic. Questions and discussions on
CAPWAP are invited on the ops-area list.=20

Regards,

Dan




