
From keiichi.shima.1016@gmail.com  Mon Sep  2 21:54:13 2013
Return-Path: <keiichi.shima.1016@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 520DF21E8089 for <opsawg@ietfa.amsl.com>; Mon,  2 Sep 2013 21:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 CID84Cnuk2Mh for <opsawg@ietfa.amsl.com>; Mon,  2 Sep 2013 21:54:09 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id BBDFD11E8121 for <opsawg@ietf.org>; Mon,  2 Sep 2013 21:54:07 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx10so5928811pab.41 for <opsawg@ietf.org>; Mon, 02 Sep 2013 21:54:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=M67FCBPVsrrADwOyxk5hFoWQx8mNs4OXMR8N8PqTdwc=; b=H8HNhWbykwdKjmUeVodmcnijtU6ll7lI8PC25io94DyfyiBZPCaydZ0KSHc1OxpOix F9pF7leZg212nBTONkalspUGcTCLJM9fQmptgs3eB2FgaAwWmDUb5DZRPAYHbMQ2YRG5 TJpBbkBFUu7pK6SuT6t/fjoZXodp/6P8446k6ErGLiU1EiZGBecuwATnPLHCsUaquzLS jr3SwOdXhtz3J9zTnTKC4xIe+J96AnoBif5tmpi0Ih0PDbAbU0Ik0TR+xh/hal75+71f 7NuKrkksWoFEBts9nhVkxtJ2TBKkPkdc/D0SU1v/URoDnxidY2IujGsejR24AtxzeaBk CPzQ==
X-Received: by 10.68.176.132 with SMTP id ci4mr29255013pbc.7.1378184047516; Mon, 02 Sep 2013 21:54:07 -0700 (PDT)
Received: from [10.0.6.145] ([203.178.156.134]) by mx.google.com with ESMTPSA id ht5sm19690823pbb.29.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Sep 2013 21:54:06 -0700 (PDT)
Sender: Keiichi SHIMA <keiichi.shima.1016@gmail.com>
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: SHIMA Keiichi <shima@wide.ad.jp>
In-Reply-To: <521F635C.8080502@cisco.com>
Date: Tue, 3 Sep 2013 13:54:03 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DADDE23-5EC1-4964-BB0F-6F0260BB3C85@wide.ad.jp>
References: <DD8CEE16-D3CC-4D29-ACDC-839FD63D1113@wide.ad.jp> <20130826105955.GA17723@elstar.local> <521F635C.8080502@cisco.com>
To: Joe Marcus Clarke <jclarke@cisco.com>
X-Mailer: Apple Mail (2.1508)
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] VMM-MIB: question about vmAdminState values
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2013 04:54:13 -0000

On 2013/08/30, at 0:06, Joe Marcus Clarke <jclarke@cisco.com> wrote:

> This reminds me of another problem I had initially noticed, but forgot
> to raise.  That is, the use of the state name to define the state.  I
> think what you have written here is good, but is there another way to
> say "blocked" that would define it more clearly?
>=20
> I have the same comment for just about all states.  Their definition
> contains the state name.  If those descriptions were more descriptive,
> it might short-circuit emails like this in the future.

I agree that we need more explanation on the text describing the states.

By the way, VirtualMachineAdminState has more detailed explanation, =
which is nice :)  Maybe we should do the similar work for =
VirtualMachineOperState too?

---
Keiichi SHIMA (=E5=B3=B6 =E6=85=B6=E4=B8=80)
WIDE project <shima@wide.ad.jp>
Research Laboratory, IIJ Innovation Institute, Inc <keiichi@iijlab.net>



On 2013/08/30, at 0:06, Joe Marcus Clarke <jclarke@cisco.com> wrote:

> On 8/26/13 6:59 AM, Juergen Schoenwaelder wrote:
>> Would this clarification help:
>>=20
>>             blocked(5)     The virtual machine is currently blocked
>> 	     		    waiting for example for some action of=20
>>                            the hypervisor to finish.
>=20
> This reminds me of another problem I had initially noticed, but forgot
> to raise.  That is, the use of the state name to define the state.  I
> think what you have written here is good, but is there another way to
> say "blocked" that would define it more clearly?
>=20
> I have the same comment for just about all states.  Their definition
> contains the state name.  If those descriptions were more descriptive,
> it might short-circuit emails like this in the future.
>=20
> Joe
>=20
> --=20
> Joe Marcus Clarke, CCIE #5384,         |          |
> SCJP, SCSA, SCNA, SCSECA, VCP        |||||      |||||
> Distinguished Services Engineer ..:|||||||||::|||||||||:..
> Phone: +1 (919) 392-2867         c i s c o  S y s t e m s
> Email: jclarke@cisco.com
>=20
> =
--------------------------------------------------------------------------=
--
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg


From jclarke@cisco.com  Tue Sep  3 08:01:39 2013
Return-Path: <jclarke@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 018EA21F9A90 for <opsawg@ietfa.amsl.com>; Tue,  3 Sep 2013 08:01:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 tF8962rfQvI6 for <opsawg@ietfa.amsl.com>; Tue,  3 Sep 2013 08:01:14 -0700 (PDT)
Received: from av-tac-jap.cisco.com (skinny-sumo.cisco.com [64.104.15.102]) by ietfa.amsl.com (Postfix) with ESMTP id C79B011E80DE for <opsawg@ietf.org>; Tue,  3 Sep 2013 08:01:01 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-jap.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r83F0xuL000147; Wed, 4 Sep 2013 00:01:00 +0900 (JST)
Received: from dhcp-10-150-54-77.cisco.com (dhcp-10-150-54-77.cisco.com [10.150.54.77]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r83F0rSp004876;  Tue, 3 Sep 2013 11:00:53 -0400 (EDT)
Message-ID: <5225F9A5.8010000@cisco.com>
Date: Tue, 03 Sep 2013 11:00:53 -0400
From: Joe Marcus Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: SHIMA Keiichi <shima@wide.ad.jp>
References: <DD8CEE16-D3CC-4D29-ACDC-839FD63D1113@wide.ad.jp> <20130826105955.GA17723@elstar.local> <521F635C.8080502@cisco.com> <5DADDE23-5EC1-4964-BB0F-6F0260BB3C85@wide.ad.jp>
In-Reply-To: <5DADDE23-5EC1-4964-BB0F-6F0260BB3C85@wide.ad.jp>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] VMM-MIB: question about vmAdminState values
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2013 15:01:41 -0000

On 9/3/13 12:54 AM, SHIMA Keiichi wrote:
> On 2013/08/30, at 0:06, Joe Marcus Clarke <jclarke@cisco.com> wrote:
> 
>> This reminds me of another problem I had initially noticed, but forgot
>> to raise.  That is, the use of the state name to define the state.  I
>> think what you have written here is good, but is there another way to
>> say "blocked" that would define it more clearly?
>>
>> I have the same comment for just about all states.  Their definition
>> contains the state name.  If those descriptions were more descriptive,
>> it might short-circuit emails like this in the future.
> 
> I agree that we need more explanation on the text describing the states.
> 
> By the way, VirtualMachineAdminState has more detailed explanation, which is nice :)  Maybe we should do the similar work for VirtualMachineOperState too?

Yes, AdminState is much better, but still has one issue.  The
shutdown(4) state is described as "...should be taken shuttingdown."  I
don't think think this is right :-).

Joe

> 
> ---
> Keiichi SHIMA (島 慶一)
> WIDE project <shima@wide.ad.jp>
> Research Laboratory, IIJ Innovation Institute, Inc <keiichi@iijlab.net>
> 
> 
> 
> On 2013/08/30, at 0:06, Joe Marcus Clarke <jclarke@cisco.com> wrote:
> 
>> On 8/26/13 6:59 AM, Juergen Schoenwaelder wrote:
>>> Would this clarification help:
>>>
>>>             blocked(5)     The virtual machine is currently blocked
>>> 	     		    waiting for example for some action of 
>>>                            the hypervisor to finish.
>>
>> This reminds me of another problem I had initially noticed, but forgot
>> to raise.  That is, the use of the state name to define the state.  I
>> think what you have written here is good, but is there another way to
>> say "blocked" that would define it more clearly?
>>
>> I have the same comment for just about all states.  Their definition
>> contains the state name.  If those descriptions were more descriptive,
>> it might short-circuit emails like this in the future.
>>
>> Joe
>>
>> -- 
>> Joe Marcus Clarke, CCIE #5384,         |          |
>> SCJP, SCSA, SCNA, SCSECA, VCP        |||||      |||||
>> Distinguished Services Engineer ..:|||||||||::|||||||||:..
>> Phone: +1 (919) 392-2867         c i s c o  S y s t e m s
>> Email: jclarke@cisco.com
>>
>> ----------------------------------------------------------------------------
>> _______________________________________________
>> OPSAWG mailing list
>> OPSAWG@ietf.org
>> https://www.ietf.org/mailman/listinfo/opsawg
> 
> 


-- 
Joe Marcus Clarke, CCIE #5384,         |          |
SCJP, SCSA, SCNA, SCSECA, VCP        |||||      |||||
Distinguished Services Engineer ..:|||||||||::|||||||||:..
Phone: +1 (919) 392-2867         c i s c o  S y s t e m s
Email: jclarke@cisco.com

----------------------------------------------------------------------------

From agmalis@gmail.com  Tue Sep  3 10:28:34 2013
Return-Path: <agmalis@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39EA621E815A for <opsawg@ietfa.amsl.com>; Tue,  3 Sep 2013 10:28:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bNmx6evCIws0 for <opsawg@ietfa.amsl.com>; Tue,  3 Sep 2013 10:28:33 -0700 (PDT)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 2EA5621E8126 for <opsawg@ietf.org>; Tue,  3 Sep 2013 10:28:32 -0700 (PDT)
Received: by mail-we0-f177.google.com with SMTP id q55so5033072wes.22 for <opsawg@ietf.org>; Tue, 03 Sep 2013 10:28:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=KzGRP5tYQmko+UUTAre5v334K9wAdwToTXh+boHEoNg=; b=RHeLzAPMrTheUI1cvdKRK9PuWdvt2SP9nQbOwBsVNdjDc6YNehqGyHozPkvi53nwoC /2zp/fAFkKZKhHWvtPLSoyd5OLpC5gOItM/ifSiaEFk2uZ93LeZ0hzSK5vjPc2R5ENbN K17EqtloZ/OquOgm4XgI4oy6BNvyf99rXarGuoaYnnATeHpPLjNRY0pLd1mmrMSNYAeG /pGaVpWm9Zv5hZc04vSmSldgWCegF5QNiUkPFCg1YCgwU59K4PkrO5U+1zv/avLCqn2c 22DTMolQqaEXSCikv4IZxdRxlK1+Gy9HhQhyF/09Sg29vX9O89/zASuDmW4sGOJBJkhs T4eA==
X-Received: by 10.180.89.101 with SMTP id bn5mr19229992wib.39.1378229312193; Tue, 03 Sep 2013 10:28:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.255.20 with HTTP; Tue, 3 Sep 2013 10:28:12 -0700 (PDT)
In-Reply-To: <52191268.5070500@gmail.com>
References: <52191268.5070500@gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 3 Sep 2013 13:28:12 -0400
Message-ID: <CAA=duU1PEOe+9+NJU-UisiTDUsZQiWAWzEPTALHtP3tcNYhXEw@mail.gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=f46d0444eba392896b04e57e047e
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, "opsawg-chairs@tools.ietf.org" <opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2013 17:28:34 -0000

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

I have provided comments on previous revisions of this draft and believe
that it is now ready for publication.

Thanks,
Andy


On Sat, Aug 24, 2013 at 4:07 PM, Melinda Shore <melinda.shore@gmail.com>wrote:

> This is to announce the start of working group last call on:
>
>     Mechanisms for Optimal LAG/ECMP Component Link Utilization in
>         Networks
>
>
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-balancing/
>
> It is intended for publication as an informational RFC.
>
> Please give it a careful read and provide any feedback to this
> mailing list by September 9, 2013
>
> Thanks,
>
> opsawg chairs
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>

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

<div dir=3D"ltr"><div>I have provided comments on previous revisions of thi=
s draft and believe that it is now ready for publication.<br><br></div>Than=
ks,<br>Andy<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">

On Sat, Aug 24, 2013 at 4:07 PM, Melinda Shore <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:melinda.shore@gmail.com" target=3D"_blank">melinda.shore@gmail.=
com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

This is to announce the start of working group last call on:<br>
<br>
=A0 =A0 Mechanisms for Optimal LAG/ECMP Component Link Utilization in<br>
=A0 =A0 =A0 =A0 Networks<br>
<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-loa=
d-balancing/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-=
opsawg-large-flow-load-balancing/</a><br>
<br>
It is intended for publication as an informational RFC.<br>
<br>
Please give it a careful read and provide any feedback to this<br>
mailing list by September 9, 2013<br>
<br>
Thanks,<br>
<br>
opsawg chairs<br>
_______________________________________________<br>
OPSAWG mailing list<br>
<a href=3D"mailto:OPSAWG@ietf.org">OPSAWG@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/opsawg" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/opsawg</a><br>
</blockquote></div><br></div>

--f46d0444eba392896b04e57e047e--

From pjmoyer@gmail.com  Tue Sep  3 10:34:38 2013
Return-Path: <pjmoyer@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E5F421E8162 for <opsawg@ietfa.amsl.com>; Tue,  3 Sep 2013 10:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uWwqZOg8PEZz for <opsawg@ietfa.amsl.com>; Tue,  3 Sep 2013 10:34:38 -0700 (PDT)
Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id D8C7621E815A for <opsawg@ietf.org>; Tue,  3 Sep 2013 10:34:37 -0700 (PDT)
Received: by mail-qc0-f181.google.com with SMTP id q4so1004125qcx.12 for <opsawg@ietf.org>; Tue, 03 Sep 2013 10:34:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ww/EGjrJVyqGtN8DMTV6SJ5VvnUO63msst5cyvBb0Rw=; b=jxHWNVjoktFcorKIfVwV1gyfgWRHoDAAYzJV4sIE9OPLIlyoAWhvw4nmheVkDBGf1F OsvS/FNDNLLq+Fkvu4Fw720Bv0CdqCsorP7pzLpDkNbbGM39565B+14j3utjozSPoUfE nife+y7fvA15ZlIcHl948hG8y9ki4R7KD3ARARd6d0gfRYv0m5ggBQ0qLHYVyhQkMffy D8IV+4iTrgOS6Ja8XmIADAHAdED4bZIqim5p+rTgqwHQMsYlq3U1WLAf73rJL/aJr4uB ZF9DUPzYoFnyUp+n0xwJAIfSK8wwWR1IUngqQ16lM+j0oybqRdSdPCHbdCv192kZpedk KRxA==
MIME-Version: 1.0
X-Received: by 10.224.28.202 with SMTP id n10mr2227683qac.20.1378229677335; Tue, 03 Sep 2013 10:34:37 -0700 (PDT)
Received: by 10.49.0.241 with HTTP; Tue, 3 Sep 2013 10:34:37 -0700 (PDT)
In-Reply-To: <52191268.5070500@gmail.com>
References: <52191268.5070500@gmail.com>
Date: Tue, 3 Sep 2013 10:34:37 -0700
Message-ID: <CAD=hUP8TZtCdernrNVY1J60ZKt0tPN5pdSC3hbG2XPZEY0rdCQ@mail.gmail.com>
From: pete <pjmoyer@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c34c2a562dd704e57e1a9e
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, "opsawg-chairs@tools.ietf.org" <opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2013 17:34:38 -0000

--001a11c34c2a562dd704e57e1a9e
Content-Type: text/plain; charset=UTF-8

I support this document, as these mechanisms are needed in SP and Research
and Education Networks (RENs).

I have a few minor comments:

1-

4.2. Overview of the mechanism

...

   Step 2) The egress component links are periodically scanned for
link utilization. If the egress component link utilization exceeds a
pre-programmed threshold, an operator alert is generated. The large
flows mapped to the congested egress component link are exported to a
central management entity



I believe you mean to say that the information about the large flows
is exported, rather than the large flows themselves being exported.


2 -


Providing large flow information to a central management entity
provides the capability to further optimize flow distribution at with
multi-node visibility.


The last part of that sentence needs clarification.


Thanks.

pete



On Sat, Aug 24, 2013 at 1:07 PM, Melinda Shore <melinda.shore@gmail.com>wrote:

> This is to announce the start of working group last call on:
>
>     Mechanisms for Optimal LAG/ECMP Component Link Utilization in
>         Networks
>
>
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-balancing/
>
> It is intended for publication as an informational RFC.
>
> Please give it a careful read and provide any feedback to this
> mailing list by September 9, 2013
>
> Thanks,
>
> opsawg chairs
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>

--001a11c34c2a562dd704e57e1a9e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"font-family:arial,sans-serif;font-size:12.4=
99999046325684px">I support this document, as these mechanisms are needed i=
n SP and Research and Education Networks (RENs).</span><div style=3D"font-f=
amily:arial,sans-serif;font-size:12.499999046325684px">
<br></div><div style=3D"font-family:arial,sans-serif;font-size:12.499999046=
325684px">I have a few minor comments:</div><div style=3D"font-family:arial=
,sans-serif;font-size:12.499999046325684px"><br></div><div style=3D"font-fa=
mily:arial,sans-serif;font-size:12.499999046325684px">
1-=C2=A0</div><div style=3D"font-family:arial,sans-serif;font-size:12.49999=
9046325684px"><br></div><div style=3D"font-family:arial,sans-serif;font-siz=
e:12.499999046325684px"><pre style=3D"white-space:pre-wrap;line-height:1.2e=
m;font-size:13px;margin-bottom:0px;margin-top:0px">
<span style=3D"font-family:arial;font-weight:bold">4.2. Overview of the mec=
hanism</span>

...</pre><pre style=3D"white-space:pre-wrap;line-height:1.2em;font-size:13p=
x;margin-bottom:0px;margin-top:0px">   Step 2) The egress component links a=
re periodically scanned for link utilization. If the egress component link =
utilization exceeds a pre-programmed threshold, an operator alert is genera=
ted. The large flows mapped to the congested egress component link are expo=
rted to a central management entity</pre>
<pre style=3D"white-space:pre-wrap;line-height:1.2em;font-size:13px;margin-=
bottom:0px;margin-top:0px"><br></pre><pre style=3D"white-space:pre-wrap;lin=
e-height:1.2em;font-size:13px;margin-bottom:0px;margin-top:0px"><span style=
=3D"font-family:arial;font-size:small;line-height:normal;white-space:normal=
"><br>
</span></pre><pre style=3D"white-space:pre-wrap;line-height:1.2em;font-size=
:13px;margin-bottom:0px;margin-top:0px"><span style=3D"font-family:arial;fo=
nt-size:small;line-height:normal;white-space:normal">I believe you mean to =
say that the information about the large flows is exported, rather than the=
 large flows themselves being exported.</span><br>

</pre><pre style=3D"white-space:pre-wrap;line-height:1.2em;font-size:13px;m=
argin-bottom:0px;margin-top:0px"><span style=3D"font-family:arial;font-size=
:small;line-height:normal;white-space:normal"><br></span></pre><pre style=
=3D"white-space:pre-wrap;line-height:1.2em;font-size:13px;margin-bottom:0px=
;margin-top:0px">
<span style=3D"font-family:arial;font-size:small;line-height:normal;white-s=
pace:normal">2 -=C2=A0</span></pre><pre style=3D"white-space:pre-wrap;line-=
height:1.2em;font-size:13px;margin-bottom:0px;margin-top:0px"><span style=
=3D"font-family:arial;font-size:small;line-height:normal;white-space:normal=
"><br>
</span></pre><pre style=3D"white-space:pre-wrap;line-height:1.2em;font-size=
:13px;margin-bottom:0px;margin-top:0px"><pre style=3D"white-space:pre-wrap;=
line-height:1.2em;margin-top:0px;margin-bottom:0px;font-size:13px">Providin=
g large flow information to a central management entity provides the capabi=
lity to further optimize flow distribution at with multi-node visibility.</=
pre>
<pre style=3D"white-space:pre-wrap;line-height:1.2em;margin-top:0px;margin-=
bottom:0px;font-size:13px"><br></pre><pre style=3D"white-space:pre-wrap;lin=
e-height:1.2em;margin-top:0px;margin-bottom:0px;font-size:13px"><pre style=
=3D"white-space:pre-wrap;font-size:13px;line-height:1.2em;margin-top:0px;ma=
rgin-bottom:0px">
<span style=3D"font-family:arial;font-size:small;line-height:normal;white-s=
pace:normal">The last part of that sentence needs clarification.</span></pr=
e>
<pre style=3D"white-space:pre-wrap;font-size:13px;line-height:1.2em;margin-=
top:0px;margin-bottom:0px"><span style=3D"font-family:arial;font-size:small=
;line-height:normal;white-space:normal"><br></span></pre><pre style=3D"whit=
e-space:pre-wrap;font-size:13px;line-height:1.2em;margin-top:0px;margin-bot=
tom:0px">
<span style=3D"font-family:arial;font-size:small;line-height:normal;white-s=
pace:normal">Thanks.</span></pre><span class=3D""><font color=3D"#888888"><=
pre style=3D"white-space:pre-wrap;font-size:13px;line-height:1.2em;margin-t=
op:0px;margin-bottom:0px">
<span style=3D"color:rgb(34,34,34);font-family:arial;font-size:small;line-h=
eight:normal;white-space:normal">pete</span></pre></font></span></pre></pre=
></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">=
On Sat, Aug 24, 2013 at 1:07 PM, Melinda Shore <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:melinda.shore@gmail.com" target=3D"_blank">melinda.shore@gmail.=
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">This is to announce the start of working gro=
up last call on:<br>
<br>
=C2=A0 =C2=A0 Mechanisms for Optimal LAG/ECMP Component Link Utilization in=
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Networks<br>
<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-loa=
d-balancing/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-=
opsawg-large-flow-load-balancing/</a><br>
<br>
It is intended for publication as an informational RFC.<br>
<br>
Please give it a careful read and provide any feedback to this<br>
mailing list by September 9, 2013<br>
<br>
Thanks,<br>
<br>
opsawg chairs<br>
_______________________________________________<br>
OPSAWG mailing list<br>
<a href=3D"mailto:OPSAWG@ietf.org">OPSAWG@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/opsawg" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/opsawg</a><br>
</blockquote></div><br></div>

--001a11c34c2a562dd704e57e1a9e--

From ramk@Brocade.com  Tue Sep  3 10:49:41 2013
Return-Path: <ramk@Brocade.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 726E711E812B for <opsawg@ietfa.amsl.com>; Tue,  3 Sep 2013 10:49:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.264
X-Spam-Level: 
X-Spam-Status: No, score=-3.264 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1]
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 iAoJ2+V5e9Mm for <opsawg@ietfa.amsl.com>; Tue,  3 Sep 2013 10:49:36 -0700 (PDT)
Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) by ietfa.amsl.com (Postfix) with ESMTP id 2E9A611E810B for <opsawg@ietf.org>; Tue,  3 Sep 2013 10:49:36 -0700 (PDT)
Received: from pps.filterd (m0000700 [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.14.5/8.14.5) with SMTP id r83H6mS1008964; Tue, 3 Sep 2013 10:49:34 -0700
Received: from hq1wp-exchub02.corp.brocade.com ([144.49.131.13]) by mx0b-000f0801.pphosted.com with ESMTP id 1en9nh8xkc-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 03 Sep 2013 10:49:34 -0700
Received: from HQ1WP-EXHUB02.corp.brocade.com (10.70.38.14) by hq1wp-exchub02.corp.brocade.com (10.70.38.99) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 3 Sep 2013 10:49:33 -0700
Received: from HQ1-EXCH01.corp.brocade.com ([fe80::ed42:173e:fe7d:d0a6]) by HQ1WP-EXHUB02.corp.brocade.com ([fe80::e1f4:a4c8:696b:3780%10]) with mapi; Tue, 3 Sep 2013 10:49:33 -0700
From: ramki Krishnan <ramk@Brocade.com>
To: pete <pjmoyer@gmail.com>, Melinda Shore <melinda.shore@gmail.com>
Date: Tue, 3 Sep 2013 10:49:21 -0700
Thread-Topic: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
Thread-Index: Ac6oy98SRIHh+gkYTzqPDL+9YO9DqAAAbR3A
Message-ID: <C7634EB63EFD984A978DFB46EA5174F2BFFE853970@HQ1-EXCH01.corp.brocade.com>
References: <52191268.5070500@gmail.com> <CAD=hUP8TZtCdernrNVY1J60ZKt0tPN5pdSC3hbG2XPZEY0rdCQ@mail.gmail.com>
In-Reply-To: <CAD=hUP8TZtCdernrNVY1J60ZKt0tPN5pdSC3hbG2XPZEY0rdCQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C7634EB63EFD984A978DFB46EA5174F2BFFE853970HQ1EXCH01corp_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-09-03_06:2013-09-03, 2013-09-03, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1309030050
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, "opsawg-chairs@tools.ietf.org" <opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2013 17:49:41 -0000

--_000_C7634EB63EFD984A978DFB46EA5174F2BFFE853970HQ1EXCH01corp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgUGV0ZSwNCg0KVGhhbmtzIGEgbG90IGZvciB5b3VyIGNvbW1lbnRzLiBXZSB3aWxsIGFkZHJl
c3MgdGhlc2UuDQoNClRoYW5rcywNClJhbWtpDQoNCkZyb206IG9wc2F3Zy1ib3VuY2VzQGlldGYu
b3JnIFttYWlsdG86b3BzYXdnLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBwZXRlDQpT
ZW50OiBUdWVzZGF5LCBTZXB0ZW1iZXIgMDMsIDIwMTMgMTA6MzUgQU0NClRvOiBNZWxpbmRhIFNo
b3JlDQpDYzogb3BzYXdnQGlldGYub3JnOyBvcHNhd2ctY2hhaXJzQHRvb2xzLmlldGYub3JnDQpT
dWJqZWN0OiBSZTogW09QU0FXR10gV0cgbGFzdCBjYWxsIGZvciAiTWVjaGFuaXNtcyBmb3IgT3B0
aW1hbCBMQUcvRUNNUCBDb21wb25lbnQgTGluayBVdGlsaXphdGlvbiBpbiBOZXR3b3JrcyINCg0K
SSBzdXBwb3J0IHRoaXMgZG9jdW1lbnQsIGFzIHRoZXNlIG1lY2hhbmlzbXMgYXJlIG5lZWRlZCBp
biBTUCBhbmQgUmVzZWFyY2ggYW5kIEVkdWNhdGlvbiBOZXR3b3JrcyAoUkVOcykuDQoNCkkgaGF2
ZSBhIGZldyBtaW5vciBjb21tZW50czoNCg0KMS0NCg0KDQoNCg0KNC4yLiBPdmVydmlldyBvZiB0
aGUgbWVjaGFuaXNtDQoNCg0KDQouLi4NCg0KICAgU3RlcCAyKSBUaGUgZWdyZXNzIGNvbXBvbmVu
dCBsaW5rcyBhcmUgcGVyaW9kaWNhbGx5IHNjYW5uZWQgZm9yIGxpbmsgdXRpbGl6YXRpb24uIElm
IHRoZSBlZ3Jlc3MgY29tcG9uZW50IGxpbmsgdXRpbGl6YXRpb24gZXhjZWVkcyBhIHByZS1wcm9n
cmFtbWVkIHRocmVzaG9sZCwgYW4gb3BlcmF0b3IgYWxlcnQgaXMgZ2VuZXJhdGVkLiBUaGUgbGFy
Z2UgZmxvd3MgbWFwcGVkIHRvIHRoZSBjb25nZXN0ZWQgZWdyZXNzIGNvbXBvbmVudCBsaW5rIGFy
ZSBleHBvcnRlZCB0byBhIGNlbnRyYWwgbWFuYWdlbWVudCBlbnRpdHkNCg0KDQoNCg0KDQpJIGJl
bGlldmUgeW91IG1lYW4gdG8gc2F5IHRoYXQgdGhlIGluZm9ybWF0aW9uIGFib3V0IHRoZSBsYXJn
ZSBmbG93cyBpcyBleHBvcnRlZCwgcmF0aGVyIHRoYW4gdGhlIGxhcmdlIGZsb3dzIHRoZW1zZWx2
ZXMgYmVpbmcgZXhwb3J0ZWQuDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KMiAtDQoNCg0KDQpQcm92
aWRpbmcgbGFyZ2UgZmxvdyBpbmZvcm1hdGlvbiB0byBhIGNlbnRyYWwgbWFuYWdlbWVudCBlbnRp
dHkgcHJvdmlkZXMgdGhlIGNhcGFiaWxpdHkgdG8gZnVydGhlciBvcHRpbWl6ZSBmbG93IGRpc3Ry
aWJ1dGlvbiBhdCB3aXRoIG11bHRpLW5vZGUgdmlzaWJpbGl0eS4NCg0KDQoNCg0KDQoNCg0KVGhl
IGxhc3QgcGFydCBvZiB0aGF0IHNlbnRlbmNlIG5lZWRzIGNsYXJpZmljYXRpb24uDQoNCg0KDQoN
Cg0KDQoNClRoYW5rcy4NCg0KDQoNCnBldGUNCg0KT24gU2F0LCBBdWcgMjQsIDIwMTMgYXQgMTow
NyBQTSwgTWVsaW5kYSBTaG9yZSA8bWVsaW5kYS5zaG9yZUBnbWFpbC5jb208bWFpbHRvOm1lbGlu
ZGEuc2hvcmVAZ21haWwuY29tPj4gd3JvdGU6DQpUaGlzIGlzIHRvIGFubm91bmNlIHRoZSBzdGFy
dCBvZiB3b3JraW5nIGdyb3VwIGxhc3QgY2FsbCBvbjoNCg0KICAgIE1lY2hhbmlzbXMgZm9yIE9w
dGltYWwgTEFHL0VDTVAgQ29tcG9uZW50IExpbmsgVXRpbGl6YXRpb24gaW4NCiAgICAgICAgTmV0
d29ya3MNCg0KaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW9wc2F3
Zy1sYXJnZS1mbG93LWxvYWQtYmFsYW5jaW5nLw0KDQpJdCBpcyBpbnRlbmRlZCBmb3IgcHVibGlj
YXRpb24gYXMgYW4gaW5mb3JtYXRpb25hbCBSRkMuDQoNClBsZWFzZSBnaXZlIGl0IGEgY2FyZWZ1
bCByZWFkIGFuZCBwcm92aWRlIGFueSBmZWVkYmFjayB0byB0aGlzDQptYWlsaW5nIGxpc3QgYnkg
U2VwdGVtYmVyIDksIDIwMTMNCg0KVGhhbmtzLA0KDQpvcHNhd2cgY2hhaXJzDQpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KT1BTQVdHIG1haWxpbmcgbGlz
dA0KT1BTQVdHQGlldGYub3JnPG1haWx0bzpPUFNBV0dAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL29wc2F3Zw0KDQo=

--_000_C7634EB63EFD984A978DFB46EA5174F2BFFE853970HQ1EXCH01corp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQoNCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9R2VuZXJhdG9y
IGNvbnRlbnQ9Ik1pY3Jvc29mdCBXb3JkIDEyIChmaWx0ZXJlZCBtZWRpdW0pIj4NCjxzdHlsZT4N
CjwhLS0NCiAvKiBGb250IERlZmluaXRpb25zICovDQogQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6VGFob21hOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q29uc29sYXM7DQoJcGFub3NlLTE6MiAxMSA2IDkg
MiAyIDQgMyAyIDQ7fQ0KIC8qIFN0eWxlIERlZmluaXRpb25zICovDQogcC5Nc29Ob3JtYWwsIGxp
Lk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206
LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9t
YW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJp
b3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6
dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcHJlDQoJ
e21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0
ZWQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1z
aXplOjEwLjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCnNwYW4uSFRNTFByZWZv
cm1hdHRlZENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0K
CW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0
ZWQiOw0KCWZvbnQtZmFtaWx5OkNvbnNvbGFzO30NCnNwYW4uRW1haWxTdHlsZTE5DQoJe21zby1z
dHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1z
ZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlw
ZTpleHBvcnQtb25seTt9DQpAcGFnZSBTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCglt
YXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LlNlY3Rpb24xDQoJe3BhZ2U6U2Vj
dGlvbjE7fQ0KLS0+DQo8L3N0eWxlPg0KPCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQogPG86c2hh
cGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlm
XS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KIDxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0
Ij4NCiAgPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQogPC9vOnNoYXBlbGF5b3V0
PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KDQo8Ym9keSBsYW5nPUVOLVVTIGxpbms9Ymx1
ZSB2bGluaz1wdXJwbGU+DQoNCjxkaXYgY2xhc3M9U2VjdGlvbjE+DQoNCjxwIGNsYXNzPU1zb05v
cm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIs
InNhbnMtc2VyaWYiOw0KY29sb3I6IzFGNDk3RCc+SGkgUGV0ZSw8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KY29sb3I6IzFGNDk3RCc+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9
J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCmNv
bG9yOiMxRjQ5N0QnPlRoYW5rcyBhIGxvdCBmb3IgeW91ciBjb21tZW50cy4gV2Ugd2lsbCBhZGRy
ZXNzIHRoZXNlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxz
cGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1z
ZXJpZiI7DQpjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxw
IGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KY29sb3I6IzFGNDk3RCc+VGhhbmtzLDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQpjb2xvcjojMUY0
OTdEJz5SYW1raTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxz
cGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1z
ZXJpZiI7DQpjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxk
aXYgc3R5bGU9J2JvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRk
aW5nOjMuMHB0IDBpbiAwaW4gMGluJz4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxiPjxzcGFuIHN0
eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIic+
RnJvbTo8L3NwYW4+PC9iPjxzcGFuDQpzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eToiVGFob21hIiwic2Fucy1zZXJpZiInPg0Kb3BzYXdnLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0
bzpvcHNhd2ctYm91bmNlc0BpZXRmLm9yZ10gPGI+T24gQmVoYWxmIE9mIDwvYj5wZXRlPGJyPg0K
PGI+U2VudDo8L2I+IFR1ZXNkYXksIFNlcHRlbWJlciAwMywgMjAxMyAxMDozNSBBTTxicj4NCjxi
PlRvOjwvYj4gTWVsaW5kYSBTaG9yZTxicj4NCjxiPkNjOjwvYj4gb3BzYXdnQGlldGYub3JnOyBv
cHNhd2ctY2hhaXJzQHRvb2xzLmlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbT1BT
QVdHXSBXRyBsYXN0IGNhbGwgZm9yICZxdW90O01lY2hhbmlzbXMgZm9yIE9wdGltYWwNCkxBRy9F
Q01QIENvbXBvbmVudCBMaW5rIFV0aWxpemF0aW9uIGluIE5ldHdvcmtzJnF1b3Q7PG86cD48L286
cD48L3NwYW4+PC9wPg0KDQo8L2Rpdj4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KDQo8ZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2Zv
bnQtc2l6ZTo5LjVwdDtmb250LWZhbWlseToiQXJpYWwiLCJzYW5zLXNlcmlmIic+SQ0Kc3VwcG9y
dCB0aGlzIGRvY3VtZW50LCBhcyB0aGVzZSBtZWNoYW5pc21zIGFyZSBuZWVkZWQgaW4gU1AgYW5k
IFJlc2VhcmNoIGFuZA0KRWR1Y2F0aW9uIE5ldHdvcmtzIChSRU5zKS48L3NwYW4+PG86cD48L286
cD48L3A+DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1z
aXplOjkuNXB0O2ZvbnQtZmFtaWx5OiJBcmlhbCIsInNhbnMtc2VyaWYiJz48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQoNCjwvZGl2Pg0KDQo8ZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+
PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZTo5LjVwdDtmb250LWZhbWlseToiQXJpYWwiLCJzYW5zLXNl
cmlmIic+SQ0KaGF2ZSBhIGZldyBtaW5vciBjb21tZW50czo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQoNCjwvZGl2Pg0KDQo8ZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2Zv
bnQtc2l6ZTo5LjVwdDtmb250LWZhbWlseToiQXJpYWwiLCJzYW5zLXNlcmlmIic+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KDQo8L2Rpdj4NCg0KPGRpdj4NCg0KPHAgY2xhc3M9TXNvTm9y
bWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6OS41cHQ7Zm9udC1mYW1pbHk6IkFyaWFsIiwic2Fu
cy1zZXJpZiInPjEtJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KDQo8L2Rpdj4NCg0KPGRp
dj4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6OS41cHQ7Zm9u
dC1mYW1pbHk6IkFyaWFsIiwic2Fucy1zZXJpZiInPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCg0KPC9kaXY+DQoNCjxkaXY+PHByZSBzdHlsZT0nbGluZS1oZWlnaHQ6MTQuNHB0O3doaXRl
LXNwYWNlOnByZS13cmFwJz48bzpwPiZuYnNwOzwvbzpwPjwvcHJlPjxwcmUNCnN0eWxlPSdsaW5l
LWhlaWdodDoxNC40cHQnPjxiPjxzcGFuIHN0eWxlPSdmb250LWZhbWlseToiQXJpYWwiLCJzYW5z
LXNlcmlmIic+NC4yLiBPdmVydmlldyBvZiB0aGUgbWVjaGFuaXNtPC9zcGFuPjwvYj48bzpwPjwv
bzpwPjwvcHJlPjxwcmUNCnN0eWxlPSdsaW5lLWhlaWdodDoxNC40cHQnPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wcmU+PHByZSBzdHlsZT0nbGluZS1oZWlnaHQ6MTQuNHB0Jz4uLi48bzpwPjwvbzpwPjwv
cHJlPjxwcmUNCnN0eWxlPSdsaW5lLWhlaWdodDoxNC40cHQ7d2hpdGUtc3BhY2U6cHJlLXdyYXAn
PsKgwqAgU3RlcCAyKSBUaGUgZWdyZXNzIGNvbXBvbmVudCBsaW5rcyBhcmUgcGVyaW9kaWNhbGx5
IHNjYW5uZWQgZm9yIGxpbmsgdXRpbGl6YXRpb24uIElmIHRoZSBlZ3Jlc3MgY29tcG9uZW50IGxp
bmsgdXRpbGl6YXRpb24gZXhjZWVkcyBhIHByZS1wcm9ncmFtbWVkIHRocmVzaG9sZCwgYW4gb3Bl
cmF0b3IgYWxlcnQgaXMgZ2VuZXJhdGVkLiBUaGUgbGFyZ2UgZmxvd3MgbWFwcGVkIHRvIHRoZSBj
b25nZXN0ZWQgZWdyZXNzIGNvbXBvbmVudCBsaW5rIGFyZSBleHBvcnRlZCB0byBhIGNlbnRyYWwg
bWFuYWdlbWVudCBlbnRpdHk8bzpwPjwvbzpwPjwvcHJlPjxwcmUNCnN0eWxlPSdsaW5lLWhlaWdo
dDoxNC40cHQ7d2hpdGUtc3BhY2U6cHJlLXdyYXAnPjxvOnA+Jm5ic3A7PC9vOnA+PC9wcmU+PHBy
ZQ0Kc3R5bGU9J2xpbmUtaGVpZ2h0OjE0LjRwdDt3aGl0ZS1zcGFjZTpwcmUtd3JhcCc+PG86cD4m
bmJzcDs8L286cD48L3ByZT48cHJlDQpzdHlsZT0nbGluZS1oZWlnaHQ6MTQuNHB0O3doaXRlLXNw
YWNlOnByZS13cmFwJz48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEyLjBwdDsNCmZvbnQtZmFtaWx5
OiJBcmlhbCIsInNhbnMtc2VyaWYiJz5JIGJlbGlldmUgeW91IG1lYW4gdG8gc2F5IHRoYXQgdGhl
IGluZm9ybWF0aW9uIGFib3V0IHRoZSBsYXJnZSBmbG93cyBpcyBleHBvcnRlZCwgcmF0aGVyIHRo
YW4gdGhlIGxhcmdlIGZsb3dzIHRoZW1zZWx2ZXMgYmVpbmcgZXhwb3J0ZWQuPC9zcGFuPjxicj4N
Cjxicj4NCjxvOnA+PC9vOnA+PC9wcmU+PHByZSBzdHlsZT0nbGluZS1oZWlnaHQ6MTQuNHB0Jz48
bzpwPiZuYnNwOzwvbzpwPjwvcHJlPjxwcmUNCnN0eWxlPSdsaW5lLWhlaWdodDoxNC40cHQ7d2hp
dGUtc3BhY2U6cHJlLXdyYXAnPjxvOnA+Jm5ic3A7PC9vOnA+PC9wcmU+PHByZQ0Kc3R5bGU9J2xp
bmUtaGVpZ2h0OjE0LjRwdDt3aGl0ZS1zcGFjZTpwcmUtd3JhcCc+PG86cD4mbmJzcDs8L286cD48
L3ByZT48cHJlDQpzdHlsZT0nbGluZS1oZWlnaHQ6MTQuNHB0Jz48c3BhbiBzdHlsZT0nZm9udC1z
aXplOjEyLjBwdDtmb250LWZhbWlseToiQXJpYWwiLCJzYW5zLXNlcmlmIic+MiAtJm5ic3A7PC9z
cGFuPjxvOnA+PC9vOnA+PC9wcmU+PHByZQ0Kc3R5bGU9J2xpbmUtaGVpZ2h0OjE0LjRwdDt3aGl0
ZS1zcGFjZTpwcmUtd3JhcCc+PG86cD4mbmJzcDs8L286cD48L3ByZT48cHJlDQpzdHlsZT0nbGlu
ZS1oZWlnaHQ6MTQuNHB0O3doaXRlLXNwYWNlOnByZS13cmFwJz5Qcm92aWRpbmcgbGFyZ2UgZmxv
dyBpbmZvcm1hdGlvbiB0byBhIGNlbnRyYWwgbWFuYWdlbWVudCBlbnRpdHkgcHJvdmlkZXMgdGhl
IGNhcGFiaWxpdHkgdG8gZnVydGhlciBvcHRpbWl6ZSBmbG93IGRpc3RyaWJ1dGlvbiBhdCB3aXRo
IG11bHRpLW5vZGUgdmlzaWJpbGl0eS48bzpwPjwvbzpwPjwvcHJlPjxwcmUNCnN0eWxlPSdsaW5l
LWhlaWdodDoxNC40cHQnPjxvOnA+Jm5ic3A7PC9vOnA+PC9wcmU+PHByZSBzdHlsZT0nbGluZS1o
ZWlnaHQ6MTQuNHB0Ow0Kd2hpdGUtc3BhY2U6cHJlLXdyYXAnPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
cmU+PHByZSBzdHlsZT0nbGluZS1oZWlnaHQ6MTQuNHB0Ow0Kd2hpdGUtc3BhY2U6cHJlLXdyYXAn
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wcmU+PHByZSBzdHlsZT0nbGluZS1oZWlnaHQ6MTQuNHB0Jz48
c3Bhbg0Kc3R5bGU9J2ZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6IkFyaWFsIiwic2Fucy1z
ZXJpZiInPlRoZSBsYXN0IHBhcnQgb2YgdGhhdCBzZW50ZW5jZSBuZWVkcyBjbGFyaWZpY2F0aW9u
Ljwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPjxwcmUNCnN0eWxlPSdsaW5lLWhlaWdodDoxNC40cHQn
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wcmU+PHByZSBzdHlsZT0nbGluZS1oZWlnaHQ6MTQuNHB0Ow0K
d2hpdGUtc3BhY2U6cHJlLXdyYXAnPjxvOnA+Jm5ic3A7PC9vOnA+PC9wcmU+PHByZSBzdHlsZT0n
bGluZS1oZWlnaHQ6MTQuNHB0Ow0Kd2hpdGUtc3BhY2U6cHJlLXdyYXAnPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wcmU+PHByZSBzdHlsZT0nbGluZS1oZWlnaHQ6MTQuNHB0Jz48c3Bhbg0Kc3R5bGU9J2Zv
bnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6IkFyaWFsIiwic2Fucy1zZXJpZiInPlRoYW5rcy48
L3NwYW4+PG86cD48L286cD48L3ByZT48cHJlDQpzdHlsZT0nbGluZS1oZWlnaHQ6MTQuNHB0O3do
aXRlLXNwYWNlOnByZS13cmFwJz48c3BhbiBzdHlsZT0nY29sb3I6Izg4ODg4OCc+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wcmU+PHByZQ0Kc3R5bGU9J2xpbmUtaGVpZ2h0OjE0LjRwdCc+PHNw
YW4gc3R5bGU9J2ZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6IkFyaWFsIiwic2Fucy1zZXJp
ZiI7DQpjb2xvcjojMjIyMjIyJz5wZXRlPC9zcGFuPjxzcGFuIHN0eWxlPSdjb2xvcjojODg4ODg4
Jz48bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT48L2Rpdj4NCg0KPC9kaXY+DQoNCjxkaXY+DQoNCjxw
IGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRvbToxMi4wcHQnPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KDQo8ZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+T24gU2F0LCBBdWcgMjQs
IDIwMTMgYXQgMTowNyBQTSwgTWVsaW5kYSBTaG9yZSAmbHQ7PGENCmhyZWY9Im1haWx0bzptZWxp
bmRhLnNob3JlQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm1lbGluZGEuc2hvcmVAZ21haWwu
Y29tPC9hPiZndDsNCndyb3RlOjxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+
VGhpcyBpcyB0byBhbm5vdW5jZSB0aGUgc3RhcnQgb2Ygd29ya2luZyBncm91cCBsYXN0IGNhbGwg
b246PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyBNZWNoYW5pc21zIGZvciBPcHRpbWFsIExBRy9F
Q01QIENvbXBvbmVudCBMaW5rIFV0aWxpemF0aW9uIGluPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7IE5ldHdvcmtzPGJyPg0KPGJyPg0KPGENCmhyZWY9Imh0dHA6Ly9kYXRhdHJhY2tl
ci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1vcHNhd2ctbGFyZ2UtZmxvdy1sb2FkLWJhbGFuY2lu
Zy8iDQp0YXJnZXQ9Il9ibGFuayI+aHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFm
dC1pZXRmLW9wc2F3Zy1sYXJnZS1mbG93LWxvYWQtYmFsYW5jaW5nLzwvYT48YnI+DQo8YnI+DQpJ
dCBpcyBpbnRlbmRlZCBmb3IgcHVibGljYXRpb24gYXMgYW4gaW5mb3JtYXRpb25hbCBSRkMuPGJy
Pg0KPGJyPg0KUGxlYXNlIGdpdmUgaXQgYSBjYXJlZnVsIHJlYWQgYW5kIHByb3ZpZGUgYW55IGZl
ZWRiYWNrIHRvIHRoaXM8YnI+DQptYWlsaW5nIGxpc3QgYnkgU2VwdGVtYmVyIDksIDIwMTM8YnI+
DQo8YnI+DQpUaGFua3MsPGJyPg0KPGJyPg0Kb3BzYXdnIGNoYWlyczxicj4NCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KT1BTQVdHIG1haWxpbmcg
bGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzpPUFNBV0dAaWV0Zi5vcmciPk9QU0FXR0BpZXRmLm9y
ZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L29wc2F3ZyIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vb3BzYXdnPC9hPjxvOnA+PC9vOnA+PC9wPg0KDQo8L2Rpdj4NCg0KPHAgY2xhc3M9TXNv
Tm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KDQo8L2Rpdj4NCg0KPC9kaXY+DQoNCjwvYm9k
eT4NCg0KPC9odG1sPg0K

--_000_C7634EB63EFD984A978DFB46EA5174F2BFFE853970HQ1EXCH01corp_--

From vumip1@gmail.com  Sun Sep  8 10:34:46 2013
Return-Path: <vumip1@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EC1D21F938E for <opsawg@ietfa.amsl.com>; Sun,  8 Sep 2013 10:34:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ciAslZTsNgFM for <opsawg@ietfa.amsl.com>; Sun,  8 Sep 2013 10:34:46 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id E8F7A21F90CF for <opsawg@ietf.org>; Sun,  8 Sep 2013 10:34:45 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id y10so4621719wgg.24 for <opsawg@ietf.org>; Sun, 08 Sep 2013 10:34:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=B08rE7EAL3kq4+3O3Pjjtsz5aT4TNwNVfZPZv84kzJg=; b=KbBmyFm8/3imaqB/osFl23zKgt5RbQSV+zKp1Yh5XdYjIOk4f4GUqsjcXuFD6J3wEW WGc+ikjbuJHKRIrze3PsoNZh7lEk/FtK5B7VTNrlR+A9ZQQ6rkI6WE67XiheHx/cOcu1 ValFC2r87dsKEkiBN0PYbJoOTt/dPywUyKk61EorLT71fvHb29inq7I8FJum29aRSpIh MAxYGg1WIG+7cd+MRJknHZR8vCuqgwep5ucC7aWf4208qhLj4MvbWfpbe9nm+RtMRiYv cB/Dve6Yz9n+pg8oQIh1+9dz5o9acrxNnEoSp/+BaU0oh+kMdVDvJsDn5/P0rvT6ZhDv rHQA==
MIME-Version: 1.0
X-Received: by 10.180.76.171 with SMTP id l11mr93134wiw.39.1378661685058; Sun, 08 Sep 2013 10:34:45 -0700 (PDT)
Received: by 10.216.28.135 with HTTP; Sun, 8 Sep 2013 10:34:45 -0700 (PDT)
Date: Sun, 8 Sep 2013 13:34:45 -0400
Message-ID: <CANtnpwi7_UQchpNbP6om7EKzbNif1B4sdHZT2zgHOVHs3AUfyw@mail.gmail.com>
From: "B.Khasnabish@ieee.org" <vumip1@gmail.com>
To: "opsawg at ietf.org" <opsawg@ietf.org>
Content-Type: multipart/alternative; boundary=f46d043749bd00e5fd04e5e2b05a
Subject: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Sep 2013 17:34:46 -0000

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

Yes, support the publication as an informational RFC
(i am a co-author). Thanks.
Best.
Bhumip


On Sat, Aug 24, 2013 at 1:07 PM, Melinda Shore <melinda.shore@gmail.com>wrote:

> This is to announce the start of working group last call on:
>
> Mechanisms for Optimal LAG/ECMP Component Link Utilization in
> Networks
>
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-
> flow-load-balancing/
>
> It is intended for publication as an informational RFC.
>
> Please give it a careful read and provide any feedback to this
> mailing list by September 9, 2013
>
> Thanks,
>
> opsawg chairs
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg

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

<div dir=3D"ltr"><div>Yes, support the publication as an informational RFC<=
/div><div>(i am a co-author). Thanks.</div><div>Best.</div><div>Bhumip</div=
><div><br clear=3D"all"><br>On Sat, Aug 24, 2013 at 1:07 PM, <span>Melinda<=
/span> Shore <span dir=3D"ltr">&lt;<a href=3D"mailto:melinda.shore@gmail.co=
m" target=3D"_blank"><font color=3D"#0066cc"><span>melinda</span>.shore@gma=
il.com</font></a>&gt;</span> wrote:<br>
</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border=
-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"=
 class=3D"gmail_quote">This is to announce the start of working group last =
call on:<br>
<br>    Mechanisms for Optimal LAG/ECMP Component Link Utilization in<br>  =
      Networks<br><br><a href=3D"http://datatracker.ietf.org/doc/draft-ietf=
-opsawg-large-flow-load-balancing/" target=3D"_blank"><font color=3D"#0066c=
c">http://datatracker.ietf.org/</font><font color=3D"#0066cc">doc/draft-iet=
f-opsawg-large-</font><font color=3D"#0066cc">flow-load-balancing/</font></=
a><br>
<br>It is intended for publication as an informational RFC.<br><br>Please g=
ive it a careful read and provide any feedback to this<br>mailing list by <=
span tabindex=3D"0"><span>September 9, 2013</span></span><br><br>Thanks,<br=
>
<br>opsawg chairs<br>_______________________________________________<br>OPS=
AWG mailing list<br><a href=3D"mailto:OPSAWG@ietf.org" target=3D"_blank"><f=
ont color=3D"#0066cc">OPSAWG@ietf.org</font></a><br><a href=3D"https://www.=
ietf.org/mailman/listinfo/opsawg" target=3D"_blank"><font color=3D"#0066cc"=
>https://www.ietf.org/mailman/</font><font color=3D"#0066cc">listinfo/opsaw=
g</font></a></blockquote>

</div>

--f46d043749bd00e5fd04e5e2b05a--

From haibin.song@huawei.com  Sun Sep  8 21:00:00 2013
Return-Path: <haibin.song@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77FB621E8138 for <opsawg@ietfa.amsl.com>; Sun,  8 Sep 2013 21:00:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FDBjFO1QxiAG for <opsawg@ietfa.amsl.com>; Sun,  8 Sep 2013 20:59:56 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8937421E8087 for <opsawg@ietf.org>; Sun,  8 Sep 2013 20:59:52 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AVF06538; Mon, 09 Sep 2013 03:59:48 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 9 Sep 2013 04:59:43 +0100
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 9 Sep 2013 04:59:46 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.141]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0146.000; Mon, 9 Sep 2013 11:59:33 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: New Version Notification for draft-song-opsawg-virtual-network-function-config-00.txt
Thread-Index: AQHOqqB+ynd9mojl70SmXWV2W8Dot5m8zHcg
Date: Mon, 9 Sep 2013 03:59:32 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F247A21EA@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.66]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [OPSAWG] FW: New Version Notification for	draft-song-opsawg-virtual-network-function-config-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2013 04:00:00 -0000

SGkgZ3V5cywNCg0KSGVyZSBpcyBhIG5ldyBkcmFmdCBvbiB2aXJ0dWFsIG5ldHdvcmsgZnVuY3Rp
b24gY29uZmlndXJhdGlvbi4gQW55IGNvbW1lbnRzIGFyZSB3ZWxjb21lIQ0KDQpCUiwNCi1IYWli
aW4NCkh1YXdlaSBUZWNobm9sb2dpZXMgQ28uLCBMdGQuDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCkZyb206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0
LWRyYWZ0c0BpZXRmLm9yZ10gDQpTZW50OiBGcmlkYXksIFNlcHRlbWJlciAwNiwgMjAxMyA5OjI5
IEFNDQpUbzogU29uZ2hhaWJpbiAoQSkNClN1YmplY3Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlv
biBmb3IgZHJhZnQtc29uZy1vcHNhd2ctdmlydHVhbC1uZXR3b3JrLWZ1bmN0aW9uLWNvbmZpZy0w
MC50eHQNCg0KDQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtc29uZy1vcHNhd2ctdmlydHVh
bC1uZXR3b3JrLWZ1bmN0aW9uLWNvbmZpZy0wMC50eHQNCmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBz
dWJtaXR0ZWQgYnkgSGFpYmluIFNvbmcgYW5kIHBvc3RlZCB0byB0aGUNCklFVEYgcmVwb3NpdG9y
eS4NCg0KRmlsZW5hbWU6CSBkcmFmdC1zb25nLW9wc2F3Zy12aXJ0dWFsLW5ldHdvcmstZnVuY3Rp
b24tY29uZmlnDQpSZXZpc2lvbjoJIDAwDQpUaXRsZToJCSBUaGUgUHJvYmxlbXMgb2YgVmlydHVh
bCBOZXR3b3JrIEZ1bmN0aW9uIENvbmZpZ3VyYXRpb24NCkNyZWF0aW9uIGRhdGU6CSAyMDEzLTA5
LTA2DQpHcm91cDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCk51bWJlciBvZiBwYWdlczogNw0K
VVJMOiAgICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFm
dC1zb25nLW9wc2F3Zy12aXJ0dWFsLW5ldHdvcmstZnVuY3Rpb24tY29uZmlnLTAwLnR4dA0KU3Rh
dHVzOiAgICAgICAgICBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXNvbmct
b3BzYXdnLXZpcnR1YWwtbmV0d29yay1mdW5jdGlvbi1jb25maWcNCkh0bWxpemVkOiAgICAgICAg
aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtc29uZy1vcHNhd2ctdmlydHVhbC1uZXR3
b3JrLWZ1bmN0aW9uLWNvbmZpZy0wMA0KDQoNCkFic3RyYWN0Og0KICAgVGhpcyBkb2N1bWVudCBk
ZXNjcmliZXMgdGhlIHByb2JsZW0gc3BhY2Ugb2YgcmVtb3RlIHNlcnZpY2UNCiAgIGluc3RhbGxh
dGlvbiBhbmQgY29uZmlndXJhdGlvbiBpbiB0aGUgcHJvdmlkZXIncyBuZXR3b3JrIHRocm91Z2gg
YQ0KICAgY2VudHJhbGl6ZWQgbWFuYWdlbWVudCBzeXN0ZW0uICBUaGlzIGlzIGEgdHlwaWNhbCBz
Y2VuYXJpbyBmb3INCiAgIHZpcnR1YWwgZnVuY3Rpb24gaW5zdGFsbGF0aW9uIGFuZCBkeW5hbWlj
IGNvbmZpZ3VyYXRpb24gaW4gbmV0d29yaw0KICAgZnVuY3Rpb24gdmlydHVhbGl6YXRpb24gKE5G
VikgY29udGV4dC4gIEl0IGlzIGFsc28gYSB0eXBpY2FsIHNjZW5hcmlvDQogICBpbiBjbG91ZCBj
b21wdXRpbmcgZW52aXJvbm1lbnQgd2hlcmUgZW5kIHVzZXJzIGRvIG5vdCBoYXZlIHRvIGluc3Rh
bGwNCiAgIGFwcGxpY2F0aW9ucyBpbiB0aGVpciBlbmQgaG9zdHMsIGJ1dCBjYW4gaW5zdGFsbCB0
aGVpciBvd24gZmVhdHVyZWQNCiAgIHBvd2VyZnVsIHNvZnR3YXJlIGFwcGxpY2F0aW9uIGluIHRo
ZSBjbG91ZC4gIFRoaXMgc3BlY2lmaWNhdGlvbiBhbHNvDQogICBpZGVudGlmaWVzIHRoZSBzY29w
ZSB0aGF0IG5lZWRzIHN0YW5kYXJkaXphdGlvbiBiYXNlZCBvbiB0aGUNCiAgIHByb2JsZW1zLg0K
DQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgDQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkg
dGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbg0KdW50
aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5p
ZXRmLm9yZy4NCg0KVGhlIElFVEYgU2VjcmV0YXJpYXQNCg0K

From ietf@cdl.asgaard.org  Mon Sep  9 02:09:17 2013
Return-Path: <ietf@cdl.asgaard.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FD2211E81AD for <opsawg@ietfa.amsl.com>; Mon,  9 Sep 2013 02:09:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 QTMp9zvT7M3m for <opsawg@ietfa.amsl.com>; Mon,  9 Sep 2013 02:09:04 -0700 (PDT)
Received: from smtp4.emailarray.com (smtp4.emailarray.com [65.39.216.22]) by ietfa.amsl.com (Postfix) with ESMTP id 5F98811E81A9 for <opsawg@ietf.org>; Mon,  9 Sep 2013 02:09:02 -0700 (PDT)
Received: (qmail 20270 invoked by uid 89); 9 Sep 2013 09:09:01 -0000
Received: from unknown (HELO ?192.168.1.149?) (Y2RsQGFzZ2FhcmQub3JnQDYzLjE5OC4yNDIuMTEy) (POLARISLOCAL)  by smtp4.emailarray.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 9 Sep 2013 09:09:01 -0000
From: "Christopher LILJENSTOLPE" <ietf@cdl.asgaard.org>
To: "opsawg@ietf.org" <opsawg@ietf.org>, opsawg-chairs <opsawg-chairs@tools.ietf.org>
Date: Mon, 09 Sep 2013 02:08:58 -0700
Message-ID: <F570812A-23B7-4A8E-ACC1-0C286C48B62A@cdl.asgaard.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_F0E254F0-59B7-4041-9C8E-0CD3BC935709_="; micalg=pgp-sha1; protocol="application/pgp-signature"
X-Mailer: MailMate (1.6r3658)
X-PolarisMail-Flags: 
Subject: [OPSAWG] Stepping down
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2013 09:09:17 -0000

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_F0E254F0-59B7-4041-9C8E-0CD3BC935709_=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Greetings all,

	As you may have noticed, I've been a bit absent as of late, mainly due t=
o work changes.  At this point, I don't see the situation calming for the=
 next 6 months to a year, so I think it only fair that I step down.  =


	The AD's have found a very capable replacement in Warren Kumari, who, al=
ong with my long-suffering co-chairs will continue to herd the cats, I me=
an working group :) =


	Thank you for being a great working group.  I have enjoyed the time you =
have allowed me to chair the working group, and hope to see you all in Va=
ncouver.

	Christopher


--
=E6=9D=8E=E6=9F=AF=E7=9D=BF
Check my PGP key here: http://www.asgaard.org/cdl/cdl.asc
Current vCard here: http://www.asgaard.org/cdl/cdl.vcf
--=_MailMate_F0E254F0-59B7-4041-9C8E-0CD3BC935709_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJSLZAqAAoJEGmx2Mt/+Iw/zzwIAJSNDw9P5dGqSoKW8H8EAYxT
HmCGZ77kO8qGqc2qDoOyRu4VxUUKLOlT+gVagvGsX0/OSrXMfWszUjYkUMaY4UQq
SlEEN5Vz3d5A3MrW2mNunk0bonJfsjjuy2iwMwoxpWp91uQBPvsw/lCzC9O6Llgo
AnjAYp+QA8E+VI4F7ULNAg529Q0yn5Zjg1HpH+yc41MhRbwv99EA2SDm5Xrz5wKa
hD7JWEWAWBg8O93CvFH4FYSTQijwYifdptgstdwqimxip3Ugj3EinrIFe/ZzHrzZ
C/Q11Sb7mxr24pcsfroJNUp3ff70fAFL6NmM6SNV5LM0AiXSv1npdL7Qb60QZ4E=
=dn34
-----END PGP SIGNATURE-----

--=_MailMate_F0E254F0-59B7-4041-9C8E-0CD3BC935709_=--

From bclaise@cisco.com  Mon Sep  9 02:29:39 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4CDB21F9B4D for <opsawg@ietfa.amsl.com>; Mon,  9 Sep 2013 02:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 sFhm2czekf1J for <opsawg@ietfa.amsl.com>; Mon,  9 Sep 2013 02:29:28 -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 55F1121E80B6 for <opsawg@ietf.org>; Mon,  9 Sep 2013 02:29:28 -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 r899T8St004676; Mon, 9 Sep 2013 11:29:09 +0200 (CEST)
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r899Rvev028783; Mon, 9 Sep 2013 11:28:17 +0200 (CEST)
Message-ID: <522D949D.7010106@cisco.com>
Date: Mon, 09 Sep 2013 11:27:57 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Christopher LILJENSTOLPE <ietf@cdl.asgaard.org>
References: <F570812A-23B7-4A8E-ACC1-0C286C48B62A@cdl.asgaard.org>
In-Reply-To: <F570812A-23B7-4A8E-ACC1-0C286C48B62A@cdl.asgaard.org>
Content-Type: multipart/alternative; boundary="------------050601010305010002030408"
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, opsawg-chairs <opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] Stepping down
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2013 09:29:39 -0000

This is a multi-part message in MIME format.
--------------050601010305010002030408
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Thanks Chris for your years of service.

And let's welcome Warren who accepted to co-chair this WG.

Regards, Benoit
> Greetings all,
>
> 	As you may have noticed, I've been a bit absent as of late, mainly due to work changes.  At this point, I don't see the situation calming for the next 6 months to a year, so I think it only fair that I step down.
>
> 	The AD's have found a very capable replacement in Warren Kumari, who, along with my long-suffering co-chairs will continue to herd the cats, I mean working group :)
>
> 	Thank you for being a great working group.  I have enjoyed the time you have allowed me to chair the working group, and hope to see you all in Vancouver.
>
> 	Christopher
>
>
> --
> ???
> Check my PGP key here: http://www.asgaard.org/cdl/cdl.asc
> Current vCard here: http://www.asgaard.org/cdl/cdl.vcf
>
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg


--------------050601010305010002030408
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Thanks Chris for your years of service.<br>
      <br>
      And let's welcome Warren who accepted to co-chair this WG.&nbsp; <br>
      <br>
      Regards, Benoit<br>
    </div>
    <blockquote
      cite="mid:F570812A-23B7-4A8E-ACC1-0C286C48B62A@cdl.asgaard.org"
      type="cite">
      <pre wrap="">Greetings all,

	As you may have noticed, I've been a bit absent as of late, mainly due to work changes.  At this point, I don't see the situation calming for the next 6 months to a year, so I think it only fair that I step down.  

	The AD's have found a very capable replacement in Warren Kumari, who, along with my long-suffering co-chairs will continue to herd the cats, I mean working group :) 

	Thank you for being a great working group.  I have enjoyed the time you have allowed me to chair the working group, and hope to see you all in Vancouver.

	Christopher


--
&#26446;&#26607;&#30591;
Check my PGP key here: <a class="moz-txt-link-freetext" href="http://www.asgaard.org/cdl/cdl.asc">http://www.asgaard.org/cdl/cdl.asc</a>
Current vCard here: <a class="moz-txt-link-freetext" href="http://www.asgaard.org/cdl/cdl.vcf">http://www.asgaard.org/cdl/cdl.vcf</a></pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OPSAWG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OPSAWG@ietf.org">OPSAWG@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/opsawg">https://www.ietf.org/mailman/listinfo/opsawg</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------050601010305010002030408--

From melinda.shore@gmail.com  Mon Sep  9 14:50:54 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D0E021E80BD for <opsawg@ietfa.amsl.com>; Mon,  9 Sep 2013 14:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 w2ifl1qmm-ie for <opsawg@ietfa.amsl.com>; Mon,  9 Sep 2013 14:50:53 -0700 (PDT)
Received: from mail-yh0-x22f.google.com (mail-yh0-x22f.google.com [IPv6:2607:f8b0:4002:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id CC6A511E8122 for <opsawg@ietf.org>; Mon,  9 Sep 2013 14:50:53 -0700 (PDT)
Received: by mail-yh0-f47.google.com with SMTP id l109so1145364yhq.34 for <opsawg@ietf.org>; Mon, 09 Sep 2013 14:50:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=55stwCqUwxXUl+3ALr6cUArfE7Z+JS5cOzcGl6vwjnc=; b=PXNhOo4mJHsCvKsHXjhq+qY5FSnG0bbk6ptdHVoaM54T6RCh6nUxQ/1Vgu4JwfGbja ZPzUQpq0Ik0CObo2jrbQ6H8dmfCnHtn2YdhPX8uo9SllBhmSXquZNoVI4vqG8od/Nup6 evULgfAmJPGH+gIQFSocwVRCZr/ZGLFY9HdOlV9mgR+U5R9uXaif8WAW+Lb7fH8/4PVY A3rz5Y7lK6CcE5DrfmOaVgl7VWbpSbzNpCS786nNeDurZGuK7KIiKlH99nIh0E+U7UhV 32plI7T4RKTEpHW7b6lgZmxsuejBPAf9dZrt95JMqs232TLVPxphHlrMEzgCwevDJDc9 2n3g==
X-Received: by 10.236.153.169 with SMTP id f29mr70949yhk.82.1378763453148; Mon, 09 Sep 2013 14:50:53 -0700 (PDT)
Received: from [50.94.107.75] ([50.94.107.75]) by mx.google.com with ESMTPSA id u66sm20188482yhd.24.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Sep 2013 14:50:52 -0700 (PDT)
Message-ID: <522E42BB.40605@gmail.com>
Date: Mon, 09 Sep 2013 13:50:51 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: opsawg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [OPSAWG] "Support" in working group last calls
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2013 21:50:54 -0000

Over the past year or so there's been an increase in
the number of people responding to working group last
calls with "I support as a co-author."  This is a
request to stop.

By the time a document enters working group last call,
presumably the authors are familiar with its contents
and don't have serious disagreements with them.  Because
"I support as a co-author" introduces little-to-no
new information it's difficult to conclude that the
reason that it's being posted has something to do with
voting.  We don't vote.  (One hopes the reason isn't
that the co-author has just read the document for the
first time and finds it agreeable).

The IETF makes decisions through a process of rough
consensus, and this doesn't mean counting a show of
hands, counting "yes" postings, or counting "I support
this as a co-author" posts.  Decisions are made on
the basis of technical discussion and agreement with
the technical contents of a document.  This decision-
making process can be confusing to people who haven't
worked in consensus-oriented environments before, and
if you haven't already read Pete Resnick's internet draft
on consensus processes in the IETF, you may want to take
a look at it.  It's well-written and does a good job
of capturing what it is that we're doing when we have
last call on a document or ask other questions of
working group participants.  That document is here:
http://datatracker.ietf.org/doc/draft-resnick-on-consensus/

In the meantime, when we have last call on a document,
the co-authors should avoid posting their opinion on
whether or not they support publication unless they take
the probably surprising position of not supporting
publishing the document.  In that case they should definitely
speak up.

Many thanks,

Melinda

From randy@psg.com  Mon Sep  9 17:55:40 2013
Return-Path: <randy@psg.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FD5F11E80E8 for <opsawg@ietfa.amsl.com>; Mon,  9 Sep 2013 17:55:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 u2ZIXs5eLAHO for <opsawg@ietfa.amsl.com>; Mon,  9 Sep 2013 17:55:37 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 756E621F9C6A for <opsawg@ietf.org>; Mon,  9 Sep 2013 17:55:36 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VJCEw-0001Z6-Us; Tue, 10 Sep 2013 00:55:35 +0000
Date: Tue, 10 Sep 2013 09:55:33 +0900
Message-ID: <m27geppkai.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Melinda Shore <melinda.shore@gmail.com>
In-Reply-To: <522E42BB.40605@gmail.com>
References: <522E42BB.40605@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] "Support" in working group last calls
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 00:55:40 -0000

> Over the past year or so there's been an increase in
> the number of people responding to working group last
> calls with "I support as a co-author."  This is a
> request to stop.

thank you

From ietfdbh@comcast.net  Mon Sep  9 21:36:44 2013
Return-Path: <ietfdbh@comcast.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86C0621E80FC for <opsawg@ietfa.amsl.com>; Mon,  9 Sep 2013 21:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.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 QpCIrLeGPzYs for <opsawg@ietfa.amsl.com>; Mon,  9 Sep 2013 21:36:30 -0700 (PDT)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40]) by ietfa.amsl.com (Postfix) with ESMTP id 3630A21E8084 for <opsawg@ietf.org>; Mon,  9 Sep 2013 21:36:30 -0700 (PDT)
Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by qmta04.westchester.pa.mail.comcast.net with comcast id PGcQ1m0021ZXKqc54GcVqZ; Tue, 10 Sep 2013 04:36:29 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta21.westchester.pa.mail.comcast.net with comcast id PGcU1m00Z2yZEBF3hGcVN6; Tue, 10 Sep 2013 04:36:29 +0000
From: "ietfdbh" <ietfdbh@comcast.net>
To: "'Melinda Shore'" <melinda.shore@gmail.com>, <opsawg@ietf.org>
References: <522E42BB.40605@gmail.com>
In-Reply-To: <522E42BB.40605@gmail.com>
Date: Tue, 10 Sep 2013 00:36:23 -0400
Message-ID: <023d01ceaddf$4df9eca0$e9edc5e0$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJqf0tmZrgCNkf9vIdp9NmtygxmmZiGvlSA
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1378787789; bh=ZRbxH+ov7HV3963zS0y/smIgceZt/qxrPSHcLnQVGAc=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=jumPF+LPYFDHNvIx1sQw6aJNkEBdg2xAV0HvKMqGAVa/KMRx8/0eDD5Y+lkytxVoq w85dOaO5tMTbSkepaXMr7qNqzcsknUjqk/91X+reLwHePePcq7FC+zUWhUaqHsBcH9 wg2bJSSokxMzuHEjqZAi+4hqcKefI2md2eCkCDtE19jtg2oelDygEj29qVqaLfLfEp YkF3yAWbDkrRmcGch89fHAWRX+JsGDOygt79eiZeSxM+PcV0OMj6s2I85gTPapsA5Q x8K9tV8kIVzN3GIUuZpjqb1P5FYMEz/Y69Th0lNMVwoBF0yDKg5PR8M+HUff//KIxK qFdM4cStRsSiA==
Subject: Re: [OPSAWG] "Support" in working group last calls
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 04:36:44 -0000

Hi Melinda,

You are the chair for this WG, and to a degree you can set the rules for how
WGLC works in your WG.
I respectfully disagree with your position.

Having been an editor for documents where my opinion about technical choices
was in the rough, I still stated support for publication of the document
because I felt it represented WG consensus, and wasn't "broken".
Having been a co-author for documents where I did not do the final editing
passes on the document, I read the updated document and supported the
document as ready for publication.
Having been a co-author where I did do the final editing passes because the
other editors were called away for day-job responsibilities, I appreciated
that they read the document and expressed support for the latest version as
named co-authors (even if they might have felt they were in the rough).
Having been a chair, one of the biggest problems can sometimes be getting
any responses at all to WGLC. I appreciated getting responses, even if they
were from co-authors of the documents.

I think it *does* have meaningful content to say that one supports the
document as a co-author/editor.

I agree that such statements would be MUCH more useful if they stated "I
read the document and believe it represents WG consensus" or "I read the
document and believe it is ready for publication".
I think we should educate people that that type of statement of support is
far more valuable than one that just says "I support the document".
I think we should NOT educate people that "if you are a co-author, then a
statement of your opinion is worthless".

Chairs are in the unenviable position of determining whether a co-author's
statement of support is based on actual support for the reviewed document or
some type of (inappropriate) political statement of support, and chairs have
ti decide whether to consider such statement as part of determining
consensus.
I do not think chairs should abdicate those responsibilities by simply
deciding all co-authors' statements of support should be ignored - ask for a
more detailed statement if "I support the document" does not seem
informative enough.

But, as I said, you are chairing this WG, and if that's your preference
about how this WG should operate, then so be it.

David Harrington
ietfdbh@comcast.net
+1-603-828-1401

> -----Original Message-----
> From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On
> Behalf Of Melinda Shore
> Sent: Monday, September 09, 2013 5:51 PM
> To: opsawg@ietf.org
> Subject: [OPSAWG] "Support" in working group last calls
> 
> Over the past year or so there's been an increase in
> the number of people responding to working group last
> calls with "I support as a co-author."  This is a
> request to stop.
> 
> By the time a document enters working group last call,
> presumably the authors are familiar with its contents
> and don't have serious disagreements with them.  Because
> "I support as a co-author" introduces little-to-no
> new information it's difficult to conclude that the
> reason that it's being posted has something to do with
> voting.  We don't vote.  (One hopes the reason isn't
> that the co-author has just read the document for the
> first time and finds it agreeable).
> 
> The IETF makes decisions through a process of rough
> consensus, and this doesn't mean counting a show of
> hands, counting "yes" postings, or counting "I support
> this as a co-author" posts.  Decisions are made on
> the basis of technical discussion and agreement with
> the technical contents of a document.  This decision-
> making process can be confusing to people who haven't
> worked in consensus-oriented environments before, and
> if you haven't already read Pete Resnick's internet draft
> on consensus processes in the IETF, you may want to take
> a look at it.  It's well-written and does a good job
> of capturing what it is that we're doing when we have
> last call on a document or ask other questions of
> working group participants.  That document is here:
> http://datatracker.ietf.org/doc/draft-resnick-on-consensus/
> 
> In the meantime, when we have last call on a document,
> the co-authors should avoid posting their opinion on
> whether or not they support publication unless they take
> the probably surprising position of not supporting
> publishing the document.  In that case they should definitely
> speak up.
> 
> Many thanks,
> 
> Melinda
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg


From mshaikh@Brocade.com  Mon Sep  9 22:54:17 2013
Return-Path: <mshaikh@Brocade.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C881A21E8127 for <opsawg@ietfa.amsl.com>; Mon,  9 Sep 2013 22:54:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.264
X-Spam-Level: 
X-Spam-Status: No, score=-3.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1]
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 SrXpRV2onvhn for <opsawg@ietfa.amsl.com>; Mon,  9 Sep 2013 22:54:13 -0700 (PDT)
Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) by ietfa.amsl.com (Postfix) with ESMTP id D313921E8114 for <opsawg@ietf.org>; Mon,  9 Sep 2013 22:54:12 -0700 (PDT)
Received: from pps.filterd (m0000700 [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.14.5/8.14.5) with SMTP id r8A5f7cS015306; Mon, 9 Sep 2013 22:54:12 -0700
Received: from hq1wp-exchub02.corp.brocade.com ([144.49.131.13]) by mx0b-000f0801.pphosted.com with ESMTP id 1eskvygq4b-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 09 Sep 2013 22:54:12 -0700
Received: from HQ1WP-EXHUB02.corp.brocade.com (10.70.38.14) by hq1wp-exchub02.corp.brocade.com (10.70.38.99) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 9 Sep 2013 22:54:11 -0700
Received: from HQ1-EXCH02.corp.brocade.com ([fe80::8c73:93bf:41b4:1443]) by HQ1WP-EXHUB02.corp.brocade.com ([fe80::e1f4:a4c8:696b:3780%10]) with mapi; Mon, 9 Sep 2013 22:54:03 -0700
From: Mukhtiar Shaikh <mshaikh@Brocade.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Date: Mon, 9 Sep 2013 22:54:00 -0700
Thread-Topic: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
Thread-Index: Ac6t6iZA3HQM33w5SJSBZQoc7+Wt7g==
Message-ID: <CE53DD78.410C9%mshaikh@brocade.com>
In-Reply-To: <C7634EB63EFD984A978DFB46EA5174F2BFFE854111@HQ1-EXCH01.corp.brocade.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.6.130613
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CE53DD78410C9mshaikhbrocadecom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-09-10_02:2013-09-10, 2013-09-10, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1309090205
Cc: "opsawg-chairs@tools.ietf.org" <opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 05:54:18 -0000

--_000_CE53DD78410C9mshaikhbrocadecom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I support the publication of this document as informational RFC. Have a cou=
ple of additional comments.

I think section 4.3.4. Automatic Hardware Recognition is a little vague. It=
 is not clear how and what is expected from the hardware to detect the larg=
e flows. Is it sampling of packet forwarding counters in hardware or someth=
ing else? Any clarity on this will be good.

Also, from operational considerations point of view, as indicated in sectio=
n 6, frequent rebalancing of flows could be counter productive leading to o=
ut of order packets and /or system instability. Similar challenges could ar=
ise from immediate rebalancing of flows on one or more component links in t=
he LAG experiencing frequent failures. System may implement a throttling me=
chanism to regulate when and what types of flows are re-distributed to pote=
ntially flaky links to avoid instability.

Thanks,
-Mukhtiar




-----Original Message-----
From: opsawg-bounces@ietf.org<mailto:opsawg-bounces@ietf.org> [mailto:opsaw=
g-bounces@ietf.org] On Behalf Of Melinda Shore
Sent: Saturday, August 24, 2013 1:07 PM
To: opsawg@ietf.org<mailto:opsawg@ietf.org>
Cc: opsawg-chairs@tools.ietf.org<mailto:opsawg-chairs@tools.ietf.org>
Subject: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Compone=
nt Link Utilization in Networks"



This is to announce the start of working group last call on:



    Mechanisms for Optimal LAG/ECMP Component Link Utilization in

        Networks



http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-balancing=
/



It is intended for publication as an informational RFC.



Please give it a careful read and provide any feedback to this mailing list=
 by September 9, 2013



Thanks,



opsawg chairs

_______________________________________________

OPSAWG mailing list

OPSAWG@ietf.org<mailto:OPSAWG@ietf.org>

https://www.ietf.org/mailman/listinfo/opsawg

--_000_CE53DD78410C9mshaikhbrocadecom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-si=
ze: 14px; font-family: Calibri, sans-serif; "><div><p class=3D"MsoNormal" s=
tyle=3D"font-size: 12pt; font-family: Cambria; "><font face=3D"Calibri" siz=
e=3D"3">I support the publication of this document as informational RFC. Ha=
ve a couple of additional comments.<o:p></o:p></font></p><p class=3D"MsoNor=
mal" style=3D"font-size: 12pt; font-family: Cambria; "><font face=3D"Calibr=
i" size=3D"3">&nbsp;</font></p><p class=3D"MsoNormal" style=3D"font-size: 1=
2pt; font-family: Cambria; "><font face=3D"Calibri" size=3D"3">I think sect=
ion 4.3.4. Automatic Hardware Recognition is a little vague. It is not clea=
r how and what is expected from the hardware to detect the large flows. Is =
it sampling of packet forwarding counters in hardware or&nbsp;something&nbs=
p;else? Any clarity on this will be good.<o:p></o:p></font></p><p class=3D"=
MsoNormal" style=3D"font-size: 12pt; font-family: Cambria; "><font face=3D"=
Calibri" size=3D"3">&nbsp;</font></p><p class=3D"MsoNormal" style=3D"font-s=
ize: 12pt; font-family: Cambria; "><font face=3D"Calibri" size=3D"3">Also, =
from operational considerations point of view, as indicated in section 6, f=
requent rebalancing of flows could be counter productive leading to out of =
order packets and /or system instability. Similar challenges could arise fr=
om immediate rebalancing of flows on one or more component links in the LAG=
 experiencing frequent failures. System may implement a throttling mechanis=
m to regulate when and what types of flows are re-distributed to potentiall=
y flaky links to avoid instability.<o:p></o:p></font></p><p class=3D"MsoNor=
mal" style=3D"font-size: 12pt; font-family: Cambria; "><font face=3D"Calibr=
i" size=3D"3">&nbsp;</font></p><p class=3D"MsoNormal" style=3D"font-size: 1=
2pt; font-family: Cambria; "><font face=3D"Calibri" size=3D"3">Thanks,<o:p>=
</o:p></font></p><p class=3D"MsoNormal" style=3D"font-size: 12pt; font-fami=
ly: Cambria; "><font face=3D"Calibri" size=3D"3">-Mukhtiar<o:p></o:p></font=
></p></div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><div xmlns:v=3D=
"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office=
:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" xmlns:x=3D"urn:s=
chemas-microsoft-com:office:excel" xmlns:m=3D"http://schemas.microsoft.com/=
office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><div lang=3D=
"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"Section1"><p class=3D"=
MsoPlainText"><o:p>&nbsp;</o:p></p><p class=3D"MsoPlainText">-----Original =
Message-----<br>
From: <a href=3D"mailto:opsawg-bounces@ietf.org">opsawg-bounces@ietf.org</a=
> [<a href=3D"mailto:opsawg-bounces@ietf.org">mailto:opsawg-bounces@ietf.or=
g</a>] On Behalf Of Melinda Shore<br>
Sent: Saturday, August 24, 2013 1:07 PM<br>
To: <a href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</a><br>
Cc: <a href=3D"mailto:opsawg-chairs@tools.ietf.org">opsawg-chairs@tools.iet=
f.org</a><br>
Subject: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Compone=
nt Link Utilization in Networks"<o:p></o:p></p><p class=3D"MsoPlainText"><o=
:p>&nbsp;</o:p></p><p class=3D"MsoPlainText">This is to announce the start =
of working group last call on:<o:p></o:p></p><p class=3D"MsoPlainText"><o:p=
>&nbsp;</o:p></p><p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp; Mechanisms fo=
r Optimal LAG/ECMP Component Link Utilization in<o:p></o:p></p><p class=3D"=
MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Networks<o:p></o:p=
></p><p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p><p class=3D"MsoPlainTex=
t"><a href=3D"http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-=
load-balancing/"><span style=3D"color:windowtext;text-decoration:none">http=
://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-balancing/</s=
pan></a><o:p></o:p></p><p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p><p cl=
ass=3D"MsoPlainText">It is intended for publication as an informational RFC=
.<o:p></o:p></p><p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p><p class=3D"=
MsoPlainText">Please give it a careful read and provide any feedback to thi=
s mailing list by September 9, 2013<o:p></o:p></p><p class=3D"MsoPlainText"=
><o:p>&nbsp;</o:p></p><p class=3D"MsoPlainText">Thanks,<o:p></o:p></p><p cl=
ass=3D"MsoPlainText"><o:p>&nbsp;</o:p></p><p class=3D"MsoPlainText">opsawg =
chairs<o:p></o:p></p><p class=3D"MsoPlainText">____________________________=
___________________<o:p></o:p></p><p class=3D"MsoPlainText">OPSAWG mailing =
list<o:p></o:p></p><p class=3D"MsoPlainText"><a href=3D"mailto:OPSAWG@ietf.=
org"><span style=3D"color:windowtext;
text-decoration:none">OPSAWG@ietf.org</span></a><o:p></o:p></p><p class=3D"=
MsoPlainText"><a href=3D"https://www.ietf.org/mailman/listinfo/opsawg"><spa=
n style=3D"color:windowtext;text-decoration:none">https://www.ietf.org/mail=
man/listinfo/opsawg</span></a><o:p></o:p></p></div></div></div></span><styl=
e>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1339698399;
	mso-list-type:hybrid;
	mso-list-template-ids:-955771746 -1763809818 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:5;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style></body></html>

--_000_CE53DD78410C9mshaikhbrocadecom_--

From dromasca@avaya.com  Tue Sep 10 03:13:28 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6997821E80C5 for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 03:13:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 OUgXiVo93kKd for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 03:13:23 -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 8A8A021E80B6 for <opsawg@ietf.org>; Tue, 10 Sep 2013 03:13:23 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AscKAJzvLlLGmAcV/2dsb2JhbABbgmYhOFGteQeUMYEoFnSCJQEBAQECAQEBAQ8LHTQLBQcEAgEIDQQEAQELFAUEBycLFAkIAgQBDQUIGodaBgELoxOcPhePKjEHBoMXgQADmSWFJ4sVgWOBPYIq
X-IronPort-AV: E=Sophos;i="4.90,877,1371096000"; d="scan'208";a="27565913"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 10 Sep 2013 06:13:22 -0400
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 10 Sep 2013 06:11:09 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0146.000; Tue, 10 Sep 2013 06:13:20 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Melinda Shore <melinda.shore@gmail.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
Thread-Index: AQHOoQbakNn37BHdZkSN0GBt4gbUPJm+1yNQ
Date: Tue, 10 Sep 2013 10:13:20 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA128CE68A@AZ-FFEXMB04.global.avaya.com>
References: <52191268.5070500@gmail.com>
In-Reply-To: <52191268.5070500@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "opsawg-chairs@tools.ietf.org" <opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 10:13:28 -0000

Hi,

I apologize for the one day delay in sending this review. Vacation interfer=
ed.=20

I read the document and I have a basic unclarity. Hopefully it is just me, =
and maybe some clarification text and references to be added.=20

What does this document exactly refer to when saying 'LAG/ECMP techniques'?=
 Is this either LAG (layer 2) or ECMP, or a combination of the two, or all =
of these? There is no reference at all in the document for LAG, no solid re=
ference for ECMP (2992 only refers to 'an ECMP algorithm').=20

I also had a hard time finding the sFlow references. In desperation I went =
to wiki http://en.wikipedia.org/wiki/SFlow which kindly informed me that=20

> sFlow is a technology for monitoring network,[1] wireless[2] and host[3] =
devices. The sFlow.org consortium[4] is the authoritative source for the sF=
low protocol specifications.[5] sFlow version 5 is the current version of s=
Flow. Previous versions of sFlow, including RFC 3176, have been deprecated.=
[6]

This seems problematic. RFC 3176 has no mark of being 'deprecated' in IETF =
terms anyway.=20

Regards,

Dan
=20


> -----Original Message-----
> From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf
> Of Melinda Shore
> Sent: Saturday, August 24, 2013 11:07 PM
> To: opsawg@ietf.org
> Cc: opsawg-chairs@tools.ietf.org
> Subject: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP
> Component Link Utilization in Networks"
>=20
> This is to announce the start of working group last call on:
>=20
>     Mechanisms for Optimal LAG/ECMP Component Link Utilization in
>         Networks
>=20
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-
> balancing/
>=20
> It is intended for publication as an informational RFC.
>=20
> Please give it a careful read and provide any feedback to this mailing
> list by September 9, 2013
>=20
> Thanks,
>=20
> opsawg chairs
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg

From melinda.shore@gmail.com  Tue Sep 10 04:15:12 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B87521F9A7D for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 04:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 cnYBot+sl3KG for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 04:15:11 -0700 (PDT)
Received: from mail-ye0-x232.google.com (mail-ye0-x232.google.com [IPv6:2607:f8b0:4002:c04::232]) by ietfa.amsl.com (Postfix) with ESMTP id 6DC5921F9A6C for <opsawg@ietf.org>; Tue, 10 Sep 2013 04:15:11 -0700 (PDT)
Received: by mail-ye0-f178.google.com with SMTP id m5so2437759yen.9 for <opsawg@ietf.org>; Tue, 10 Sep 2013 04:15:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=rbYVZ8GmjZEaN7OfO7GrnQrls05LtrggR4Vvbk1KxNo=; b=py3BBTyU8S2DE31gHdNRHtYXgzQ+uIoAQ1dV7nGU4tw/Vv54+12cMfjtkXKVKZvUia dL2X9AgorH6x2Le1YlroCb2X0EcbrNIn4hLquSidG85EwitChhbS/zZM+u7prKNxUdUC tARTmPh+PPUdrkrQt32oqof2AptUtm27uOHyMxbhHHu7PosIJ0ed0G3bz7qUlXxM6opl 5xQXg2LMG5i0QTmiCpl4NZBXrCjeBXanhEo0C3gTm2zKDg8HgB5bQCHS9UZoist9YrV9 Tal+oC4Aavo4/9QG6nfxYYSHYuRr3HU9OKf5Gf4Rs3hsbRvlkE1A7koGm+FAKReZ6BFa caZQ==
X-Received: by 10.236.32.3 with SMTP id n3mr21197375yha.25.1378811710946; Tue, 10 Sep 2013 04:15:10 -0700 (PDT)
Received: from [50.94.107.75] ([50.94.107.75]) by mx.google.com with ESMTPSA id w42sm24047778yhb.8.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Sep 2013 04:15:10 -0700 (PDT)
Message-ID: <522EFF3D.9040104@gmail.com>
Date: Tue, 10 Sep 2013 03:15:09 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietfdbh <ietfdbh@comcast.net>
References: <522E42BB.40605@gmail.com> <023d01ceaddf$4df9eca0$e9edc5e0$@comcast.net>
In-Reply-To: <023d01ceaddf$4df9eca0$e9edc5e0$@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] "Support" in working group last calls
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 11:15:12 -0000

On 9/9/2013 8:36 PM, ietfdbh wrote:
> I think it *does* have meaningful content to say that one supports the
> document as a co-author/editor.

I really don't think so.  It's meaningful to say that one
is a co-author and doesn't support the draft moving forward.

We don't vote, and I tend to think these "I support as co-
author" posts do take the form of voting.

Melinda




From loa@pi.nu  Tue Sep 10 04:30:11 2013
Return-Path: <loa@pi.nu>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF94821F9B4B for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 04:30:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 c88UVURsVjRu for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 04:30:05 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 46EFC21E8135 for <opsawg@ietf.org>; Tue, 10 Sep 2013 04:29:51 -0700 (PDT)
Received: from [192.168.1.133] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id C954718033E4; Tue, 10 Sep 2013 13:29:48 +0200 (CEST)
Message-ID: <522F02AD.7070004@pi.nu>
Date: Tue, 10 Sep 2013 13:29:49 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
References: <522E42BB.40605@gmail.com> <023d01ceaddf$4df9eca0$e9edc5e0$@comcast.net> <522EFF3D.9040104@gmail.com>
In-Reply-To: <522EFF3D.9040104@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] "Support" in working group last calls
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 11:30:11 -0000

Melinda,

in general I agree with you - but I would say that the "support
as co-author" is in a group of mails that could be called
"unnecessary but not forbidden".

Actually from the mpls wg there are a few expereiences.

Since starting to add "the co-authors of draft-xxx-
has told the wg chairs that the document is ready for working
group last call" to mails that tells what the wg chairs do
with the documents - the "support as co-author" has dropped.

Telling the wg during the wg status report at meeting that if
you are a co-author you don't need to speak up during wglc
in support of a document.

Also telling people that do that anyway offline also has effect.

/Loa

On 2013-09-10 13:15, Melinda Shore wrote:
> On 9/9/2013 8:36 PM, ietfdbh wrote:
>> I think it *does* have meaningful content to say that one supports the
>> document as a co-author/editor.
>
> I really don't think so.  It's meaningful to say that one
> is a co-author and doesn't support the draft moving forward.
>
> We don't vote, and I tend to think these "I support as co-
> author" posts do take the form of voting.
>
> Melinda
>
>
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From melinda.shore@gmail.com  Tue Sep 10 04:40:25 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B29E21F9F0E for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 04:40:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 f+IXeZcgH6eY for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 04:40:22 -0700 (PDT)
Received: from mail-ve0-x229.google.com (mail-ve0-x229.google.com [IPv6:2607:f8b0:400c:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id C483A21E8126 for <opsawg@ietf.org>; Tue, 10 Sep 2013 04:39:46 -0700 (PDT)
Received: by mail-ve0-f169.google.com with SMTP id db12so4455926veb.14 for <opsawg@ietf.org>; Tue, 10 Sep 2013 04:39:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=3gVEQ6H6eaAscvmZD2B/IFc+b+8W42UqYkrQyvpcUiA=; b=pY4iz6Cuz0n3OGobDp4TclfRkgOPbIwodY8YkUVxZ/gW80hDxaH2dbjf432H7SqD+b JFTfWx2w/7Bqzjw3uJBlLyY8oIQkEi67HjL2HT0V0eKnzK+A8GmbTn//6W/TJjUA318p eC485RbVXvjhsEkYUmD7Ow5KAfOxxlR2JdtTg0/7NG2O/U6avcHvM5djlnqjG6m8tJg1 IYOCJecs7Cnex3+lCU4vtppQQgoEfVM/YFnyYBhimIEQkeeZriE8dHfazcyktE9C0EkE ujxFFEI86a+W1sjwG7tpx58qPKW0Ei2M1Zx/TuPdpR6e/oMRtqL9HNAlrKUR7g9J0PEr pSGA==
X-Received: by 10.52.227.6 with SMTP id rw6mr18941199vdc.19.1378813184407; Tue, 10 Sep 2013 04:39:44 -0700 (PDT)
Received: from [50.94.107.75] ([50.94.107.75]) by mx.google.com with ESMTPSA id jw6sm4836156veb.3.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Sep 2013 04:39:44 -0700 (PDT)
Message-ID: <522F04FF.9090506@gmail.com>
Date: Tue, 10 Sep 2013 03:39:43 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Loa Andersson <loa@pi.nu>
References: <522E42BB.40605@gmail.com> <023d01ceaddf$4df9eca0$e9edc5e0$@comcast.net> <522EFF3D.9040104@gmail.com> <522F02AD.7070004@pi.nu>
In-Reply-To: <522F02AD.7070004@pi.nu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] "Support" in working group last calls
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 11:40:25 -0000

On 9/10/2013 3:29 AM, Loa Andersson wrote:
> Melinda,
> 
> in general I agree with you - but I would say that the "support
> as co-author" is in a group of mails that could be called
> "unnecessary but not forbidden".

Right, that's my feeling as well.  But I do think that
consensus processes are not well-understood, to the
detriment of the IETF, and that misunderstanding can be
expressed in a variety of ways, including responding
to working group last calls with a vote.  As the
organization has grown and changed over the years this
has become more of an issue.  It's a very good thing
that the IETF has grown and changed, and having a broader
set of participants both improves our documents and improves
the uptake of our documents, but it does mean
that from time to time we need to remind ourselves that
we do business a little (or a lot) differently from
other standards bodies.

One response I've never seen but that would indicate that
the person "gets it" would be a response along the lines
of "I don't agree with the contents of this document but
I made my case during its development, and while I'd
like my disagreement noted I will not object to it moving
forward."

Melinda


From loa@pi.nu  Tue Sep 10 06:26:59 2013
Return-Path: <loa@pi.nu>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 804B711E81A9 for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 06:26:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 X9PWO5ObGqeC for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 06:26:53 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id B262221E80F7 for <opsawg@ietf.org>; Tue, 10 Sep 2013 06:26:36 -0700 (PDT)
Received: from [192.168.5.61] (81-229-83-119-no65.business.telia.com [81.229.83.119]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id AAC2118033E4; Tue, 10 Sep 2013 15:26:35 +0200 (CEST)
Message-ID: <522F1E0C.7010200@pi.nu>
Date: Tue, 10 Sep 2013 15:26:36 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
References: <522E42BB.40605@gmail.com> <023d01ceaddf$4df9eca0$e9edc5e0$@comcast.net> <522EFF3D.9040104@gmail.com> <522F02AD.7070004@pi.nu> <522F04FF.9090506@gmail.com>
In-Reply-To: <522F04FF.9090506@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] "Support" in working group last calls
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 13:26:59 -0000

Melinda,

again I agree that this is an issue, but I'm not sure about the
magnitude. The "support as co-author" often happens when a new
author has her/his first draft progressed through a wglc.

This is a good opportunity to reply with an off-line mail as
say "yes we understand that you supports the document - after
all you are  co-author; but please note that the IETF consensus
process does not work by voting". And maybe a pointer to the
Tao of IETF.

/Loa

On 2013-09-10 13:39, Melinda Shore wrote:
> On 9/10/2013 3:29 AM, Loa Andersson wrote:
>> Melinda,
>>
>> in general I agree with you - but I would say that the "support
>> as co-author" is in a group of mails that could be called
>> "unnecessary but not forbidden".
>
> Right, that's my feeling as well.  But I do think that
> consensus processes are not well-understood, to the
> detriment of the IETF, and that misunderstanding can be
> expressed in a variety of ways, including responding
> to working group last calls with a vote.  As the
> organization has grown and changed over the years this
> has become more of an issue.  It's a very good thing
> that the IETF has grown and changed, and having a broader
> set of participants both improves our documents and improves
> the uptake of our documents, but it does mean
> that from time to time we need to remind ourselves that
> we do business a little (or a lot) differently from
> other standards bodies.
>
> One response I've never seen but that would indicate that
> the person "gets it" would be a response along the lines
> of "I don't agree with the contents of this document but
> I made my case during its development, and while I'd
> like my disagreement noted I will not object to it moving
> forward."
>
> Melinda
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From zehn.cao@gmail.com  Tue Sep 10 07:46:25 2013
Return-Path: <zehn.cao@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83EDC11E81B5 for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 07:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WeMKwDLeznRb for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 07:46:25 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id A44F511E8181 for <opsawg@ietf.org>; Tue, 10 Sep 2013 07:46:24 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id c10so810470wiw.5 for <opsawg@ietf.org>; Tue, 10 Sep 2013 07:46:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=t3d8LCLjAnCqOWj7uF4ubHnOtr8wTxsRUVoidKuBhRs=; b=VreUjELgOfQ1dJEfqaPsLluewjEDdyhiDyv8cLvkRnNvZwvjbI7yJPNachYjga7WD1 pMcgimCUO9d453PO6sCjbSJpuP/xJulcu/U3sFDN7TpHzMbsxjuSJuh2Mq3XomJsvdsC l7hK2+fHOijAeAAnPpkWcGAlgrjCBR3XkzKdm58ZcL5tWWqDjHCi60x+RX+HeqWiB8gB ZTYFef7u+NdKvs0suqz5dozLuTH+1fT45rfKFBeSm5BTadWApA/W1s1zTD5UG9Y3aCs4 zKMHwRAgDusbzO6CkHv6/47OuPpZJgjwwtEqaHFQQdU92fn0h1SWVCVZQ66avaaRSX3B iA2g==
MIME-Version: 1.0
X-Received: by 10.194.87.36 with SMTP id u4mr894973wjz.64.1378824383617; Tue, 10 Sep 2013 07:46:23 -0700 (PDT)
Received: by 10.216.214.131 with HTTP; Tue, 10 Sep 2013 07:46:23 -0700 (PDT)
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F247A21EA@nkgeml501-mbs.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F247A21EA@nkgeml501-mbs.china.huawei.com>
Date: Tue, 10 Sep 2013 10:46:23 -0400
Message-ID: <CAProHATCVwfhjP6qXqCh+B65p_Eht=FexRtKeCKWXUL1hxvobQ@mail.gmail.com>
From: "Cao,Zhen" <zehn.cao@gmail.com>
To: "Songhaibin (A)" <haibin.song@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] FW: New Version Notification for draft-song-opsawg-virtual-network-function-config-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 14:46:25 -0000

Thanks for the draft. I have some comments as below:

Comments for section 3 about service configuration problems.

some more problems from my understanding
1. service chain requirement could be submitted by the user to the
controller
2. service elasticity requirements should be specified by the user
3. in addition to software versions, the user also want to specify the
operating system versions.

   There are also resource requirements for the remote software
   installation, which are complement to the software components
   selection.  There is lack of a standard for a user to tell the
   controller how much bandwidth, storage, CPU, memory are allocated to
   a specific software in the provider's network (perhaps there is
   existing standard for the virtual machine or host level resources),

[cz] but the Openstack-Neutron have such APIs to specify the user's
request , better to notice the difference here.


==quote
4.  Scope for Standardization

   (1) A protocol between the user and controller for software
   installation components choices, dynamic service configuration
   through the controller, and the resource requirements for the
   installation.

   (2) A protocol between software vendor and the controller for the
   detailed description of the software components and the recommended
   resource requirements for service instance.

[cz] Envision a picture here. and what's the operator's role in the picture,
i believe the operator-controller interface should also be specified ,
maybe add a (3).


On Sun, Sep 8, 2013 at 11:59 PM, Songhaibin (A) <haibin.song@huawei.com> wrote:
> Hi guys,
>
> Here is a new draft on virtual network function configuration. Any comments are welcome!
>
> BR,
> -Haibin
> Huawei Technologies Co., Ltd.
>
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Friday, September 06, 2013 9:29 AM
> To: Songhaibin (A)
> Subject: New Version Notification for draft-song-opsawg-virtual-network-function-config-00.txt
>
>
> A new version of I-D, draft-song-opsawg-virtual-network-function-config-00.txt
> has been successfully submitted by Haibin Song and posted to the
> IETF repository.
>
> Filename:        draft-song-opsawg-virtual-network-function-config
> Revision:        00
> Title:           The Problems of Virtual Network Function Configuration
> Creation date:   2013-09-06
> Group:           Individual Submission
> Number of pages: 7
> URL:             http://www.ietf.org/internet-drafts/draft-song-opsawg-virtual-network-function-config-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-song-opsawg-virtual-network-function-config
> Htmlized:        http://tools.ietf.org/html/draft-song-opsawg-virtual-network-function-config-00
>
>
> Abstract:
>    This document describes the problem space of remote service
>    installation and configuration in the provider's network through a
>    centralized management system.  This is a typical scenario for
>    virtual function installation and dynamic configuration in network
>    function virtualization (NFV) context.  It is also a typical scenario
>    in cloud computing environment where end users do not have to install
>    applications in their end hosts, but can install their own featured
>    powerful software application in the cloud.  This specification also
>    identifies the scope that needs standardization based on the
>    problems.
>
>
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg

From ghanwani@gmail.com  Tue Sep 10 08:30:43 2013
Return-Path: <ghanwani@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C388321F9A1C for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 08:30:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TiRt08xb7gU2 for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 08:30:42 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 45EBF21F9A16 for <opsawg@ietf.org>; Tue, 10 Sep 2013 08:30:42 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w62so5826414wes.1 for <opsawg@ietf.org>; Tue, 10 Sep 2013 08:30:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=5c5Iail7moxirxdpYUw42KwemskEBw+vzYoSZIFEBsA=; b=wkIuzzr2EWdLe48w3KJVxyu62HBZvN9L9+fyouVHvUeB1gC2LBYpSPyvxrnShUWNr/ LZTv/0NNMhal+Nius5gxpFVt5CMpbwUKmXqCW9rAr5Cp4A5SnrjHI/8r9K5c1sORofRt nRdNb/34G2FnV2TYI3UteYuwBv+pSevQnmGurVDnqciBYo5BOB6zAfKOuPXnMiSC6Xbk 2FUyxzIZeB4TqyE4CXCk93TsVQgMaUwW2ByvTE/BGddJ7X9MFq9JcMmVBzz64bfJz6hY Hq+tWzgrXgne6OEajDB/SfaZ9fsTHTAkSfg8bypFdROije0pp2xn+a2cq94vkll1o1tX PyHg==
MIME-Version: 1.0
X-Received: by 10.194.123.227 with SMTP id md3mr17814597wjb.17.1378827041363;  Tue, 10 Sep 2013 08:30:41 -0700 (PDT)
Sender: ghanwani@gmail.com
Received: by 10.217.54.6 with HTTP; Tue, 10 Sep 2013 08:30:41 -0700 (PDT)
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA128CE68A@AZ-FFEXMB04.global.avaya.com>
References: <52191268.5070500@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CE68A@AZ-FFEXMB04.global.avaya.com>
Date: Tue, 10 Sep 2013 08:30:41 -0700
X-Google-Sender-Auth: q1HsvwdB3x8XckF-xDhSHXkKNJM
Message-ID: <CA+-tSzxzrGgbEH1cULg+CBVEhR1mQw90u7PSe9meDNAwdWrN1Q@mail.gmail.com>
From: Anoop Ghanwani <anoop@alumni.duke.edu>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: multipart/alternative; boundary=089e01229a5801df5704e609303d
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, "opsawg-chairs@tools.ietf.org" <opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 15:30:43 -0000

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

Hi Dan,

Thanks for the careful review.  Please see inline.

On Tue, Sep 10, 2013 at 3:13 AM, Romascanu, Dan (Dan) <dromasca@avaya.com>wrote:

> Hi,
>
> I apologize for the one day delay in sending this review. Vacation
> interfered.
>
> I read the document and I have a basic unclarity. Hopefully it is just me,
> and maybe some clarification text and references to be added.
>
> What does this document exactly refer to when saying 'LAG/ECMP
> techniques'? Is this either LAG (layer 2) or ECMP, or a combination of the
> two, or all of these? There is no reference at all in the document for LAG,
> no solid reference for ECMP (2992 only refers to 'an ECMP algorithm').
>

It refers to all of them, i.e. LAG, ECMP, and even the (hierarchical)
combination.  We can try and provide some clarification around that.  We
will add 802.1AX as a reference for LAG.  What would be a reasonable
reference for ECMP?  Would RFC 2991 suffice?


>
> I also had a hard time finding the sFlow references. In desperation I went
> to wiki http://en.wikipedia.org/wiki/SFlow which kindly informed me that
>
> > sFlow is a technology for monitoring network,[1] wireless[2] and host[3]
> devices. The sFlow.org consortium[4] is the authoritative source for the
> sFlow protocol specifications.[5] sFlow version 5 is the current version of
> sFlow. Previous versions of sFlow, including RFC 3176, have been
> deprecated.[6]
>
> This seems problematic. RFC 3176 has no mark of being 'deprecated' in IETF
> terms anyway.
>

The reference that we have for sflow in the references section is the
"sflow Version 5" specification which is located at
http://sflow.org/sflow_version_5.txt.  We can update the reference to
include the URL.

Anoop


>
> > -----Original Message-----
> > From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf
> > Of Melinda Shore
> > Sent: Saturday, August 24, 2013 11:07 PM
> > To: opsawg@ietf.org
> > Cc: opsawg-chairs@tools.ietf.org
> > Subject: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP
> > Component Link Utilization in Networks"
> >
> > This is to announce the start of working group last call on:
> >
> >     Mechanisms for Optimal LAG/ECMP Component Link Utilization in
> >         Networks
> >
> > http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-
> > balancing/
> >
> > It is intended for publication as an informational RFC.
> >
> > Please give it a careful read and provide any feedback to this mailing
> > list by September 9, 2013
> >
> > Thanks,
> >
> > opsawg chairs
> > _______________________________________________
> > OPSAWG mailing list
> > OPSAWG@ietf.org
> > https://www.ietf.org/mailman/listinfo/opsawg
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>

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

<div dir=3D"ltr">Hi Dan,<div><br></div><div>Thanks for the careful review. =
=A0Please see inline.</div><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Tue, Sep 10, 2013 at 3:13 AM, Romascanu, Dan (Dan) <span dir=
=3D"ltr">&lt;<a href=3D"mailto:dromasca@avaya.com" target=3D"_blank">dromas=
ca@avaya.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">Hi,<br>
<br>
I apologize for the one day delay in sending this review. Vacation interfer=
ed.<br>
<br>
I read the document and I have a basic unclarity. Hopefully it is just me, =
and maybe some clarification text and references to be added.<br>
<br>
What does this document exactly refer to when saying &#39;LAG/ECMP techniqu=
es&#39;? Is this either LAG (layer 2) or ECMP, or a combination of the two,=
 or all of these? There is no reference at all in the document for LAG, no =
solid reference for ECMP (2992 only refers to &#39;an ECMP algorithm&#39;).=
<br>
</blockquote><div><br></div><div>It refers to all of them, i.e. LAG, ECMP, =
and even the (hierarchical) combination. =A0We can try and provide some cla=
rification around that. =A0We will add 802.1AX as a reference for LAG. =A0W=
hat would be a reasonable reference for ECMP? =A0Would RFC 2991 suffice?</d=
iv>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">
<br>
I also had a hard time finding the sFlow references. In desperation I went =
to wiki <a href=3D"http://en.wikipedia.org/wiki/SFlow" target=3D"_blank">ht=
tp://en.wikipedia.org/wiki/SFlow</a> which kindly informed me that<br>
<br>
&gt; sFlow is a technology for monitoring network,[1] wireless[2] and host[=
3] devices. The sFlow.org consortium[4] is the authoritative source for the=
 sFlow protocol specifications.[5] sFlow version 5 is the current version o=
f sFlow. Previous versions of sFlow, including RFC 3176, have been deprecat=
ed.[6]<br>

<br>
This seems problematic. RFC 3176 has no mark of being &#39;deprecated&#39; =
in IETF terms anyway.<br></blockquote><div><br></div><div>The reference tha=
t we have for sflow in the references section is the &quot;sflow Version 5&=
quot; specification which is located at <a href=3D"http://sflow.org/sflow_v=
ersion_5.txt">http://sflow.org/sflow_version_5.txt</a>. =A0We can update th=
e reference to include the URL.</div>
<div><br></div><div>Anoop</div><div><br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-co=
lor:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=
=3D"im">
<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:opsawg-bounces@ietf.org">opsawg-bounces@ietf.o=
rg</a> [mailto:<a href=3D"mailto:opsawg-bounces@ietf.org">opsawg-bounces@ie=
tf.org</a>] On Behalf<br>
</div><div class=3D"im">&gt; Of Melinda Shore<br>
&gt; Sent: Saturday, August 24, 2013 11:07 PM<br>
&gt; To: <a href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</a><br>
&gt; Cc: <a href=3D"mailto:opsawg-chairs@tools.ietf.org">opsawg-chairs@tool=
s.ietf.org</a><br>
&gt; Subject: [OPSAWG] WG last call for &quot;Mechanisms for Optimal LAG/EC=
MP<br>
&gt; Component Link Utilization in Networks&quot;<br>
&gt;<br>
</div><div class=3D""><div class=3D"h5">&gt; This is to announce the start =
of working group last call on:<br>
&gt;<br>
&gt; =A0 =A0 Mechanisms for Optimal LAG/ECMP Component Link Utilization in<=
br>
&gt; =A0 =A0 =A0 =A0 Networks<br>
&gt;<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flo=
w-load-" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-opsaw=
g-large-flow-load-</a><br>
&gt; balancing/<br>
&gt;<br>
&gt; It is intended for publication as an informational RFC.<br>
&gt;<br>
&gt; Please give it a careful read and provide any feedback to this mailing=
<br>
&gt; list by September 9, 2013<br>
&gt;<br>
&gt; Thanks,<br>
&gt;<br>
&gt; opsawg chairs<br>
&gt; _______________________________________________<br>
&gt; OPSAWG mailing list<br>
&gt; <a href=3D"mailto:OPSAWG@ietf.org">OPSAWG@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/opsawg" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/opsawg</a><br>
_______________________________________________<br>
OPSAWG mailing list<br>
<a href=3D"mailto:OPSAWG@ietf.org">OPSAWG@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/opsawg" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/opsawg</a><br>
</div></div></blockquote></div><br></div></div>

--089e01229a5801df5704e609303d--

From dromasca@avaya.com  Tue Sep 10 08:39:42 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E90411E81DB for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 08:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.224
X-Spam-Level: 
X-Spam-Status: No, score=-103.224 tagged_above=-999 required=5 tests=[AWL=0.374, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 Eug2L+0KjRrH for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 08:39:36 -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 39B3F11E81C6 for <opsawg@ietf.org>; Tue, 10 Sep 2013 08:39:28 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnYPALg8L1LGmAcV/2dsb2JhbABbDoI1IyE4Ua1+B4IdiVeIR4EkFnSCJQEBAQECAQEBAQ8LEEELBQcEAgEIDQQEAQELGQQHIQYLFAkIAgQOBQgah04DCQYBC6NUkw0NiFsXjHCCOi0EBgEGA4MUgQADlgwBgxiFJ4VlhTCBY34/gio
X-IronPort-AV: E=Sophos;i="4.90,879,1371096000"; d="scan'208,217";a="27007931"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by co300216-co-outbound.net.avaya.com with ESMTP; 10 Sep 2013 11:39:28 -0400
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 10 Sep 2013 11:37:14 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0146.000; Tue, 10 Sep 2013 17:39:26 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Anoop Ghanwani <anoop@alumni.duke.edu>
Thread-Topic: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
Thread-Index: AQHOoQbakNn37BHdZkSN0GBt4gbUPJm+1yNQgACfR4D//72kYA==
Date: Tue, 10 Sep 2013 15:39:26 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA128CF4C1@AZ-FFEXMB04.global.avaya.com>
References: <52191268.5070500@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CE68A@AZ-FFEXMB04.global.avaya.com> <CA+-tSzxzrGgbEH1cULg+CBVEhR1mQw90u7PSe9meDNAwdWrN1Q@mail.gmail.com>
In-Reply-To: <CA+-tSzxzrGgbEH1cULg+CBVEhR1mQw90u7PSe9meDNAwdWrN1Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA128CF4C1AZFFEXMB04globa_"
MIME-Version: 1.0
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, "opsawg-chairs@tools.ietf.org" <opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 15:39:42 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA128CF4C1AZFFEXMB04globa_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Anoop,

Thanks for the quick response and for the clarification. Clarification text=
 and better references as you suggest would be welcome.

I am not sure RFC 2991 is a solid reference for ECMP. Maybe you should ask =
Dave Thaler.

There is another problem that this document prompts to. If the protocol des=
cribed by RFC 3176 is indeed 'deprecated' the RFC should be made Historical=
. That's an issue for the IESG to consider.

Regards,

Dan



From: ghanwani@gmail.com [mailto:ghanwani@gmail.com] On Behalf Of Anoop Gha=
nwani
Sent: Tuesday, September 10, 2013 6:31 PM
To: Romascanu, Dan (Dan)
Cc: Melinda Shore; opsawg@ietf.org; opsawg-chairs@tools.ietf.org
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Com=
ponent Link Utilization in Networks"

Hi Dan,

Thanks for the careful review.  Please see inline.

On Tue, Sep 10, 2013 at 3:13 AM, Romascanu, Dan (Dan) <dromasca@avaya.com<m=
ailto:dromasca@avaya.com>> wrote:
Hi,

I apologize for the one day delay in sending this review. Vacation interfer=
ed.

I read the document and I have a basic unclarity. Hopefully it is just me, =
and maybe some clarification text and references to be added.

What does this document exactly refer to when saying 'LAG/ECMP techniques'?=
 Is this either LAG (layer 2) or ECMP, or a combination of the two, or all =
of these? There is no reference at all in the document for LAG, no solid re=
ference for ECMP (2992 only refers to 'an ECMP algorithm').

It refers to all of them, i.e. LAG, ECMP, and even the (hierarchical) combi=
nation.  We can try and provide some clarification around that.  We will ad=
d 802.1AX as a reference for LAG.  What would be a reasonable reference for=
 ECMP?  Would RFC 2991 suffice?


I also had a hard time finding the sFlow references. In desperation I went =
to wiki http://en.wikipedia.org/wiki/SFlow which kindly informed me that

> sFlow is a technology for monitoring network,[1] wireless[2] and host[3] =
devices. The sFlow.org consortium[4] is the authoritative source for the sF=
low protocol specifications.[5] sFlow version 5 is the current version of s=
Flow. Previous versions of sFlow, including RFC 3176, have been deprecated.=
[6]

This seems problematic. RFC 3176 has no mark of being 'deprecated' in IETF =
terms anyway.

The reference that we have for sflow in the references section is the "sflo=
w Version 5" specification which is located at http://sflow.org/sflow_versi=
on_5.txt.  We can update the reference to include the URL.

Anoop



> -----Original Message-----
> From: opsawg-bounces@ietf.org<mailto:opsawg-bounces@ietf.org> [mailto:ops=
awg-bounces@ietf.org<mailto:opsawg-bounces@ietf.org>] On Behalf
> Of Melinda Shore
> Sent: Saturday, August 24, 2013 11:07 PM
> To: opsawg@ietf.org<mailto:opsawg@ietf.org>
> Cc: opsawg-chairs@tools.ietf.org<mailto:opsawg-chairs@tools.ietf.org>
> Subject: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP
> Component Link Utilization in Networks"
>
> This is to announce the start of working group last call on:
>
>     Mechanisms for Optimal LAG/ECMP Component Link Utilization in
>         Networks
>
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-
> balancing/
>
> It is intended for publication as an informational RFC.
>
> Please give it a careful read and provide any feedback to this mailing
> list by September 9, 2013
>
> Thanks,
>
> opsawg chairs
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org<mailto:OPSAWG@ietf.org>
> https://www.ietf.org/mailman/listinfo/opsawg
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org<mailto:OPSAWG@ietf.org>
https://www.ietf.org/mailman/listinfo/opsawg


--_000_9904FB1B0159DA42B0B887B7FA8119CA128CF4C1AZFFEXMB04globa_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Anoop,
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks for the quick resp=
onse and for the clarification. Clarification text and better references as=
 you suggest would be welcome.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I am not sure RFC 2991 is=
 a solid reference for ECMP. Maybe you should ask Dave Thaler.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">There is another problem =
that this document prompts to. If the protocol described by RFC 3176 is ind=
eed &#8216;deprecated&#8217; the RFC should be made Historical. That&#8217;=
s
 an issue for the IESG to consider. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regards,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Dan<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> ghanwani=
@gmail.com [mailto:ghanwani@gmail.com]
<b>On Behalf Of </b>Anoop Ghanwani<br>
<b>Sent:</b> Tuesday, September 10, 2013 6:31 PM<br>
<b>To:</b> Romascanu, Dan (Dan)<br>
<b>Cc:</b> Melinda Shore; opsawg@ietf.org; opsawg-chairs@tools.ietf.org<br>
<b>Subject:</b> Re: [OPSAWG] WG last call for &quot;Mechanisms for Optimal =
LAG/ECMP Component Link Utilization in Networks&quot;<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Hi Dan,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks for the careful review. &nbsp;Please see inli=
ne.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Tue, Sep 10, 2013 at 3:13 AM, Romascanu, Dan (Dan=
) &lt;<a href=3D"mailto:dromasca@avaya.com" target=3D"_blank">dromasca@avay=
a.com</a>&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">Hi,<br>
<br>
I apologize for the one day delay in sending this review. Vacation interfer=
ed.<br>
<br>
I read the document and I have a basic unclarity. Hopefully it is just me, =
and maybe some clarification text and references to be added.<br>
<br>
What does this document exactly refer to when saying 'LAG/ECMP techniques'?=
 Is this either LAG (layer 2) or ECMP, or a combination of the two, or all =
of these? There is no reference at all in the document for LAG, no solid re=
ference for ECMP (2992 only refers
 to 'an ECMP algorithm').<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">It refers to all of them, i.e. LAG, ECMP, and even t=
he (hierarchical) combination. &nbsp;We can try and provide some clarificat=
ion around that. &nbsp;We will add 802.1AX as a reference for LAG. &nbsp;Wh=
at would be a reasonable reference for ECMP? &nbsp;Would
 RFC 2991 suffice?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal"><br>
I also had a hard time finding the sFlow references. In desperation I went =
to wiki
<a href=3D"http://en.wikipedia.org/wiki/SFlow" target=3D"_blank">http://en.=
wikipedia.org/wiki/SFlow</a> which kindly informed me that<br>
<br>
&gt; sFlow is a technology for monitoring network,[1] wireless[2] and host[=
3] devices. The sFlow.org consortium[4] is the authoritative source for the=
 sFlow protocol specifications.[5] sFlow version 5 is the current version o=
f sFlow. Previous versions of sFlow,
 including RFC 3176, have been deprecated.[6]<br>
<br>
This seems problematic. RFC 3176 has no mark of being 'deprecated' in IETF =
terms anyway.<o:p></o:p></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The reference that we have for sflow in the referenc=
es section is the &quot;sflow Version 5&quot; specification which is locate=
d at
<a href=3D"http://sflow.org/sflow_version_5.txt">http://sflow.org/sflow_ver=
sion_5.txt</a>. &nbsp;We can update the reference to include the URL.<o:p><=
/o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Anoop<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class=3D"MsoNormal"><br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:opsawg-bounces@ietf.org">opsawg-bounces@ietf.o=
rg</a> [mailto:<a href=3D"mailto:opsawg-bounces@ietf.org">opsawg-bounces@ie=
tf.org</a>] On Behalf<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&gt; Of Melinda Shore<br>
&gt; Sent: Saturday, August 24, 2013 11:07 PM<br>
&gt; To: <a href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</a><br>
&gt; Cc: <a href=3D"mailto:opsawg-chairs@tools.ietf.org">opsawg-chairs@tool=
s.ietf.org</a><br>
&gt; Subject: [OPSAWG] WG last call for &quot;Mechanisms for Optimal LAG/EC=
MP<br>
&gt; Component Link Utilization in Networks&quot;<br>
&gt;<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">&gt; This is to announce the start of working group =
last call on:<br>
&gt;<br>
&gt; &nbsp; &nbsp; Mechanisms for Optimal LAG/ECMP Component Link Utilizati=
on in<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; Networks<br>
&gt;<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flo=
w-load-" target=3D"_blank">
http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-</a><br>
&gt; balancing/<br>
&gt;<br>
&gt; It is intended for publication as an informational RFC.<br>
&gt;<br>
&gt; Please give it a careful read and provide any feedback to this mailing=
<br>
&gt; list by September 9, 2013<br>
&gt;<br>
&gt; Thanks,<br>
&gt;<br>
&gt; opsawg chairs<br>
&gt; _______________________________________________<br>
&gt; OPSAWG mailing list<br>
&gt; <a href=3D"mailto:OPSAWG@ietf.org">OPSAWG@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/opsawg" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/opsawg</a><br>
_______________________________________________<br>
OPSAWG mailing list<br>
<a href=3D"mailto:OPSAWG@ietf.org">OPSAWG@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/opsawg" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/opsawg</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA128CF4C1AZFFEXMB04globa_--

From melinda.shore@gmail.com  Tue Sep 10 10:46:21 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59A6B21F9F23 for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 10:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 i7RWZlFy5Evm for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 10:46:21 -0700 (PDT)
Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id E00D821F9DF0 for <opsawg@ietf.org>; Tue, 10 Sep 2013 10:46:20 -0700 (PDT)
Received: by mail-ie0-f182.google.com with SMTP id aq17so16999654iec.13 for <opsawg@ietf.org>; Tue, 10 Sep 2013 10:46:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=GDXnNzce7RGCBATCycKWMy633kvvRfyTZZlIHwCr3ik=; b=NyRnX5i4bYp9Ua78FIembkuFbY7GzPCvahoCJoFOhlENFb0j1a1SNYpsTYElLCFetf ExjvvK/Mwuq3YW47rQ5YgyEzWw2jhyZP6LoHHis8WIcKkZIVzHk2qF1Rz3DtSndZ9dSf 9DUR4ISa4Q5EdITOxxYkUN9V13sABQLa9v8uHv4rjgNdQJTxwjxIb/Oo93UEowzB6fzs L0Uvzl6pIBunChjZy0cRu0erxLSqdOQ69H8HCYlkiZmyhbq4G/HY6y3opnK915nSWyWu Y0Ld0M/LoQN1pfzqTdtq09slRbktfmuvk3y4M/0fP9jCHzqmEd/2gcsGjDewpvG0nW8E 4HuQ==
X-Received: by 10.50.29.39 with SMTP id g7mr11176531igh.16.1378835179392; Tue, 10 Sep 2013 10:46:19 -0700 (PDT)
Received: from [10.88.68.7] (nat1.corp-fo.iad1.verisign.com. [216.168.230.7]) by mx.google.com with ESMTPSA id p10sm1550385igx.4.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Sep 2013 10:46:18 -0700 (PDT)
Message-ID: <522F5AE8.1090706@gmail.com>
Date: Tue, 10 Sep 2013 09:46:16 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "opsawg@ietf.org" <opsawg@ietf.org>
References: <52191268.5070500@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CE68A@AZ-FFEXMB04.global.avaya.com> <CA+-tSzxzrGgbEH1cULg+CBVEhR1mQw90u7PSe9meDNAwdWrN1Q@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CF4C1@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA128CF4C1@AZ-FFEXMB04.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org" <draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 17:46:21 -0000

One issue that's been raised off-list is that there may not be
sufficient visibility into the per-circuit queues for this to
be implementable.  Does one of the authors have any feedback
on this?

Melinda

From ghanwani@gmail.com  Tue Sep 10 10:56:13 2013
Return-Path: <ghanwani@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1334C21E8127 for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 10:56:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5AY5ujvlUCze for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 10:56:12 -0700 (PDT)
Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 40B1E21F99ED for <opsawg@ietf.org>; Tue, 10 Sep 2013 10:56:11 -0700 (PDT)
Received: by mail-we0-f176.google.com with SMTP id u56so6948182wes.35 for <opsawg@ietf.org>; Tue, 10 Sep 2013 10:56:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=y/8fv2OIi7y3pq2zi4j5j8iZhjNhHsnKzyVrsnmoKas=; b=zRGHmvzNczGK/cQuRnEdOB7goPiMUJg9M+AkUYmXB/JtZ88zUrqb0+/p1WecRqTe3J K02VS/tqGhcaupYh6We1IWQRjDMmQSixF+edCQFufTflEKktE7/yP1pxnNsWFpEKhiKT VTtAyhgtk1cCkbutn2Fqjqkz2d7DcceEcGuxzztP/d7Sb2cr5hClOYc2s26NYu4HZED1 tTSnYGvQMDGG0xbqIhiDhn8cPjsf4TK7BeBmz0JnCTdR+CwrqX1QaRw8fsDBFIGb4DQn Psg3K/59nBOcLUZ9vQmDGViu7ug60aVtwKc5rmWotcwx6qmMn8IuAG2GoUs07xLutsqx 9SPg==
MIME-Version: 1.0
X-Received: by 10.180.231.6 with SMTP id tc6mr13654235wic.59.1378835771180; Tue, 10 Sep 2013 10:56:11 -0700 (PDT)
Sender: ghanwani@gmail.com
Received: by 10.217.54.6 with HTTP; Tue, 10 Sep 2013 10:56:11 -0700 (PDT)
In-Reply-To: <522F5AE8.1090706@gmail.com>
References: <52191268.5070500@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CE68A@AZ-FFEXMB04.global.avaya.com> <CA+-tSzxzrGgbEH1cULg+CBVEhR1mQw90u7PSe9meDNAwdWrN1Q@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CF4C1@AZ-FFEXMB04.global.avaya.com> <522F5AE8.1090706@gmail.com>
Date: Tue, 10 Sep 2013 10:56:11 -0700
X-Google-Sender-Auth: DP45q2TGh5JmMpPsZKMDe8DvAhc
Message-ID: <CA+-tSzyiz6CeWecs64y6feWbZ1vFkkwfmbXssP3qGViaAk=OYA@mail.gmail.com>
From: Anoop Ghanwani <anoop@alumni.duke.edu>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=001a1134d1ba584c4504e60b382d
Cc: "draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org" <draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 17:56:13 -0000

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

Melinda,

I would need a bit more clarity on what is "per circuit".  The mechanism
works by looking at the utilization on individual component links within a
LAG/ECMP.  The port-level queues and packet/byte counters are always
visible to an implementation.

It is possible that some implementations may not be able to control the
flow of traffic in the way that is proposed in the draft (i.e. mapping
specific large flows to an individual component link), but I'm not aware of
any in recent memory (5+ years).

Anoop


On Tue, Sep 10, 2013 at 10:46 AM, Melinda Shore <melinda.shore@gmail.com>wrote:

> One issue that's been raised off-list is that there may not be
> sufficient visibility into the per-circuit queues for this to
> be implementable.  Does one of the authors have any feedback
> on this?
>
> Melinda
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>

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

<div dir=3D"ltr">Melinda,<div><br></div><div>I would need a bit more clarit=
y on what is &quot;per circuit&quot;. =A0The mechanism works by looking at =
the utilization on individual component links within a LAG/ECMP. =A0The por=
t-level queues and packet/byte counters are always visible to an implementa=
tion. =A0</div>
<div><br></div><div>It is possible that some implementations may not be abl=
e to control the flow of traffic in the way that is proposed in the draft (=
i.e. mapping specific large flows to an individual component link), but I&#=
39;m not aware of any in recent memory (5+ years).</div>
<div><div><br></div><div>Anoop</div><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On Tue, Sep 10, 2013 at 10:46 AM, Melinda Shore <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:melinda.shore@gmail.com" target=3D"_bla=
nk">melinda.shore@gmail.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">One issue that&#39;s been raised off-list is=
 that there may not be<br>
sufficient visibility into the per-circuit queues for this to<br>
be implementable. =A0Does one of the authors have any feedback<br>
on this?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Melinda<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5">_____________________=
__________________________<br>
OPSAWG mailing list<br>
<a href=3D"mailto:OPSAWG@ietf.org">OPSAWG@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/opsawg" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/opsawg</a><br>
</div></div></blockquote></div><br></div></div></div>

--001a1134d1ba584c4504e60b382d--

From ramk@Brocade.com  Tue Sep 10 14:04:52 2013
Return-Path: <ramk@Brocade.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6038721F9BF7 for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 14:04:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.264
X-Spam-Level: 
X-Spam-Status: No, score=-3.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1]
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 G-WlpFVRnXJo for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 14:04:34 -0700 (PDT)
Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7C611E811B for <opsawg@ietf.org>; Tue, 10 Sep 2013 14:04:33 -0700 (PDT)
Received: from pps.filterd (m0000700 [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.14.5/8.14.5) with SMTP id r8AKfvDw003994; Tue, 10 Sep 2013 14:04:32 -0700
Received: from hq1wp-exchub02.corp.brocade.com ([144.49.131.13]) by mx0b-000f0801.pphosted.com with ESMTP id 1et6jfr9hg-9 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 10 Sep 2013 14:04:32 -0700
Received: from HQ1WP-EXHUB01.corp.brocade.com (10.70.36.14) by hq1wp-exchub02.corp.brocade.com (10.70.38.99) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 10 Sep 2013 14:04:31 -0700
Received: from HQ1-EXCH01.corp.brocade.com ([fe80::ed42:173e:fe7d:d0a6]) by HQ1WP-EXHUB01.corp.brocade.com ([::1]) with mapi; Tue, 10 Sep 2013 14:04:22 -0700
From: ramki Krishnan <ramk@Brocade.com>
To: Mukhtiar Shaikh <mshaikh@Brocade.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Date: Tue, 10 Sep 2013 14:04:02 -0700
Thread-Topic: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
Thread-Index: Ac6t6iZA3HQM33w5SJSBZQoc7+Wt7gAVPISQ
Message-ID: <C7634EB63EFD984A978DFB46EA5174F2BFFE958FE2@HQ1-EXCH01.corp.brocade.com>
References: <C7634EB63EFD984A978DFB46EA5174F2BFFE854111@HQ1-EXCH01.corp.brocade.com> <CE53DD78.410C9%mshaikh@brocade.com>
In-Reply-To: <CE53DD78.410C9%mshaikh@brocade.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C7634EB63EFD984A978DFB46EA5174F2BFFE958FE2HQ1EXCH01corp_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-09-10_08:2013-09-10, 2013-09-10, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1309100128
Cc: "opsawg-chairs@tools.ietf.org" <opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 21:04:52 -0000

--_000_C7634EB63EFD984A978DFB46EA5174F2BFFE958FE2HQ1EXCH01corp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Mukhtiar,

Thanks for your comments. Please find answers inline.
>>I think section 4.3.4. Automatic Hardware Recognition is a little vague. =
It is not clear how and what is expected from the hardware to detect the la=
rge flows. Is it sampling of packet forwarding counters in hardware or some=
thing else? Any clarity on this will be good.
Since the details are implementation specific, we are not planning on expan=
ding this section - IETF does not recommend specific implementations.
>> Also, from operational considerations point of view, as indicated in sec=
tion 6, frequent rebalancing of flows could be counter productive leading t=
o out of order packets and /or system instability. Similar challenges could=
 arise from immediate rebalancing of flows on one or more component links i=
n the LAG experiencing frequent failures. System may implement a throttling=
 mechanism to regulate when and what types of flows are re-distributed to p=
otentially flaky links to avoid instability.
Flaky links should be detected by the system and removed from the LAG right=
 ? I am not sure if there is anything specific we need to for large flow LA=
G load balancing.
Thanks,
Ramki

From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of=
 Mukhtiar Shaikh
Sent: Monday, September 09, 2013 10:54 PM
To: opsawg@ietf.org
Cc: opsawg-chairs@tools.ietf.org
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Com=
ponent Link Utilization in Networks"

I support the publication of this document as informational RFC. Have a cou=
ple of additional comments.

I think section 4.3.4. Automatic Hardware Recognition is a little vague. It=
 is not clear how and what is expected from the hardware to detect the larg=
e flows. Is it sampling of packet forwarding counters in hardware or someth=
ing else? Any clarity on this will be good.

Also, from operational considerations point of view, as indicated in sectio=
n 6, frequent rebalancing of flows could be counter productive leading to o=
ut of order packets and /or system instability. Similar challenges could ar=
ise from immediate rebalancing of flows on one or more component links in t=
he LAG experiencing frequent failures. System may implement a throttling me=
chanism to regulate when and what types of flows are re-distributed to pote=
ntially flaky links to avoid instability.

Thanks,
-Mukhtiar




-----Original Message-----
From: opsawg-bounces@ietf.org<mailto:opsawg-bounces@ietf.org> [mailto:opsaw=
g-bounces@ietf.org] On Behalf Of Melinda Shore
Sent: Saturday, August 24, 2013 1:07 PM
To: opsawg@ietf.org<mailto:opsawg@ietf.org>
Cc: opsawg-chairs@tools.ietf.org<mailto:opsawg-chairs@tools.ietf.org>
Subject: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Compone=
nt Link Utilization in Networks"



This is to announce the start of working group last call on:



    Mechanisms for Optimal LAG/ECMP Component Link Utilization in

        Networks



http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-balancing=
/



It is intended for publication as an informational RFC.



Please give it a careful read and provide any feedback to this mailing list=
 by September 9, 2013



Thanks,



opsawg chairs

_______________________________________________

OPSAWG mailing list

OPSAWG@ietf.org<mailto:OPSAWG@ietf.org>

https://www.ietf.org/mailman/listinfo/opsawg

--_000_C7634EB63EFD984A978DFB46EA5174F2BFFE958FE2HQ1EXCH01corp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>Hi Mukhtiar,<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Thanks for your comments. Please find answers inline.<=
o:p></o:p></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'>&gt;&gt;I
think section 4.3.4. Automatic Hardware Recognition is a little vague. It i=
s
not clear how and what is expected from the hardware to detect the large fl=
ows.
Is it sampling of packet forwarding counters in hardware
or&nbsp;something&nbsp;else? Any clarity on this will be good.<o:p></o:p></=
p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'>Since
the details are implementation specific, we are not planning on expanding t=
his
section &#8211; IETF does not recommend specific implementations.<o:p></o:p=
></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'>&gt;&gt;
Also, from operational considerations point of view, as indicated in sectio=
n 6,
frequent rebalancing of flows could be counter productive leading to out of
order packets and /or system instability. Similar challenges could arise fr=
om
immediate rebalancing of flows on one or more component links in the LAG
experiencing frequent failures. System may implement a throttling mechanism=
 to
regulate when and what types of flows are re-distributed to potentially fla=
ky
links to avoid instability.<span style=3D'font-family:"Cambria","serif"'><o=
:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'>Flaky
links should be detected by the system and removed from the LAG right ? I a=
m not
sure if there is anything specific we need to for large flow LAG load balan=
cing.<o:p></o:p></p>

<p class=3DMsoNormal>Thanks,<o:p></o:p></p>

<p class=3DMsoNormal>Ramki<o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] <b>On Behalf Of </=
b>Mukhtiar
Shaikh<br>
<b>Sent:</b> Monday, September 09, 2013 10:54 PM<br>
<b>To:</b> opsawg@ietf.org<br>
<b>Cc:</b> opsawg-chairs@tools.ietf.org<br>
<b>Subject:</b> Re: [OPSAWG] WG last call for &quot;Mechanisms for Optimal
LAG/ECMP Component Link Utilization in Networks&quot;<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>I support the publication of this document as informa=
tional
RFC. Have a couple of additional comments.</span><span style=3D'font-family=
:"Cambria","serif";
color:black'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>&nbsp;</span><span style=3D'font-family:"Cambria","se=
rif";
color:black'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>I think section 4.3.4. Automatic Hardware Recognition=
 is a
little vague. It is not clear how and what is expected from the hardware to
detect the large flows. Is it sampling of packet forwarding counters in
hardware or&nbsp;something&nbsp;else? Any clarity on this will be good.</sp=
an><span
style=3D'font-family:"Cambria","serif";color:black'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>&nbsp;</span><span style=3D'font-family:"Cambria","se=
rif";
color:black'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>Also, from operational considerations point of view, =
as
indicated in section 6, frequent rebalancing of flows could be counter
productive leading to out of order packets and /or system instability. Simi=
lar
challenges could arise from immediate rebalancing of flows on one or more
component links in the LAG experiencing frequent failures. System may imple=
ment
a throttling mechanism to regulate when and what types of flows are
re-distributed to potentially flaky links to avoid instability.</span><span
style=3D'font-family:"Cambria","serif";color:black'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>&nbsp;</span><span style=3D'font-family:"Cambria","se=
rif";
color:black'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>Thanks,</span><span style=3D'font-family:"Cambria","s=
erif";
color:black'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>-Mukhtiar</span><span style=3D'font-family:"Cambria",=
"serif";
color:black'><o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'><o:p>&nbs=
p;</o:p></span></p>

</div>

<div>

<div>

<div>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>-----O=
riginal
Message-----<br>
From: <a href=3D"mailto:opsawg-bounces@ietf.org">opsawg-bounces@ietf.org</a=
> [<a
href=3D"mailto:opsawg-bounces@ietf.org">mailto:opsawg-bounces@ietf.org</a>]=
 On
Behalf Of Melinda Shore<br>
Sent: Saturday, August 24, 2013 1:07 PM<br>
To: <a href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</a><br>
Cc: <a href=3D"mailto:opsawg-chairs@tools.ietf.org">opsawg-chairs@tools.iet=
f.org</a><br>
Subject: [OPSAWG] WG last call for &quot;Mechanisms for Optimal LAG/ECMP
Component Link Utilization in Networks&quot;<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>This i=
s to
announce the start of working group last call on:<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
&nbsp;&nbsp;
Mechanisms for Optimal LAG/ECMP Component Link Utilization in<o:p></o:p></s=
pan></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Networks<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'><a
href=3D"http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-b=
alancing/"><span
style=3D'color:windowtext;text-decoration:none'>http://datatracker.ietf.org=
/doc/draft-ietf-opsawg-large-flow-load-balancing/</span></a><o:p></o:p></sp=
an></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>It is =
intended
for publication as an informational RFC.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>Please=
 give it
a careful read and provide any feedback to this mailing list by September 9=
,
2013<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>Thanks=
,<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>opsawg=
 chairs<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>______=
_________________________________________<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>OPSAWG=
 mailing
list<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'><a
href=3D"mailto:OPSAWG@ietf.org"><span style=3D'color:windowtext;text-decora=
tion:
none'>OPSAWG@ietf.org</span></a><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'><a
href=3D"https://www.ietf.org/mailman/listinfo/opsawg"><span style=3D'color:=
windowtext;
text-decoration:none'>https://www.ietf.org/mailman/listinfo/opsawg</span></=
a><o:p></o:p></span></p>

</div>

</div>

</div>

</div>

</body>

</html>

--_000_C7634EB63EFD984A978DFB46EA5174F2BFFE958FE2HQ1EXCH01corp_--

From randy@psg.com  Tue Sep 10 16:59:00 2013
Return-Path: <randy@psg.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6689E11E80DF for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 16:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 hm7Ya2afFGeH for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 16:59:00 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id DA26911E80D5 for <opsawg@ietf.org>; Tue, 10 Sep 2013 16:58:59 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VJXpf-00042p-BS; Tue, 10 Sep 2013 23:58:55 +0000
Date: Tue, 10 Sep 2013 13:58:53 -1000
Message-ID: <m238pckz42.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Anoop Ghanwani <anoop@alumni.duke.edu>
In-Reply-To: <CA+-tSzyiz6CeWecs64y6feWbZ1vFkkwfmbXssP3qGViaAk=OYA@mail.gmail.com>
References: <52191268.5070500@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CE68A@AZ-FFEXMB04.global.avaya.com> <CA+-tSzxzrGgbEH1cULg+CBVEhR1mQw90u7PSe9meDNAwdWrN1Q@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CF4C1@AZ-FFEXMB04.global.avaya.com> <522F5AE8.1090706@gmail.com> <CA+-tSzyiz6CeWecs64y6feWbZ1vFkkwfmbXssP3qGViaAk=OYA@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: "draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org" <draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 23:59:00 -0000

> I would need a bit more clarity on what is "per circuit".  The
> mechanism works by looking at the utilization on individual component
> links within a LAG/ECMP.  The port-level queues and packet/byte
> counters are always visible to an implementation.

for some definitions of 'always'.  a few of us would greatly appreciate
if you could tell us the commands on junos and cisco XR to look at a
lag's per-physical-circuit queues.

randy

From ghanwani@gmail.com  Tue Sep 10 17:08:28 2013
Return-Path: <ghanwani@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4C0521E804D for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 17:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ABzw+bI2SZTx for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 17:08:27 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 43E7911E80DF for <opsawg@ietf.org>; Tue, 10 Sep 2013 17:08:25 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id n12so4773960wgh.3 for <opsawg@ietf.org>; Tue, 10 Sep 2013 17:08:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=+Mer6kqRLMrQnpVTw5VcJY+4BaEBrkvAvIuNg0oI7O4=; b=GfUhf7rm9NifppYRbb3TNMBPJmGNGIPIcagAfYY1/kMMky2y8BKWraEBblbMFNGteL RteOdMTdafZil9EMf6V4Ao4xgUD9s84lt3naehIodZktIiLBNbiHwfEXWY+jZSsb7SHn qaScB7bqaWc+ROABwLRT/e2q04vVcqg8Z+fg/76w9ny1h7mVthkx34MV3/rCBH7JFKE+ ZVUrYctHkrmxIcJT6bNiYKJRYkzf62ODUCotIeXPQY90mRwC32WQwvX0nNTDVWd5CAYm BoMuMsyWmMNoQT760BmG98I3G40atulFSLqzljwUEGLQO2jYKyFxzOFzPEJfUdGmjbqy gPqQ==
MIME-Version: 1.0
X-Received: by 10.180.74.164 with SMTP id u4mr15023369wiv.17.1378858105160; Tue, 10 Sep 2013 17:08:25 -0700 (PDT)
Sender: ghanwani@gmail.com
Received: by 10.217.54.6 with HTTP; Tue, 10 Sep 2013 17:08:25 -0700 (PDT)
In-Reply-To: <m238pckz42.wl%randy@psg.com>
References: <52191268.5070500@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CE68A@AZ-FFEXMB04.global.avaya.com> <CA+-tSzxzrGgbEH1cULg+CBVEhR1mQw90u7PSe9meDNAwdWrN1Q@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CF4C1@AZ-FFEXMB04.global.avaya.com> <522F5AE8.1090706@gmail.com> <CA+-tSzyiz6CeWecs64y6feWbZ1vFkkwfmbXssP3qGViaAk=OYA@mail.gmail.com> <m238pckz42.wl%randy@psg.com>
Date: Tue, 10 Sep 2013 17:08:25 -0700
X-Google-Sender-Auth: a_qOzHXr1Mg8gONedgL9r6kCJbE
Message-ID: <CA+-tSzz4=GqfOUhNag-GOf+yF5WgQC3tyeVQWeuyHbgqS8n-Sw@mail.gmail.com>
From: Anoop Ghanwani <anoop@alumni.duke.edu>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=f46d043c7f568dced104e6106b49
Cc: "draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org" <draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2013 00:08:29 -0000

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

Randy,

Please clarify what you mean by per-physical circuit queues.  There is no
mention of that term in this draft.

We deal with per physical port counters.  Finding those should be pretty
straightforward on any router.  Please see section 5.6.1:
http://tools.ietf.org/html/draft-ietf-opsawg-large-flow-load-balancing-05#section-5.6.1
for what the draft needs.  There are standard MIB objects for things like
these.

Anoop


On Tue, Sep 10, 2013 at 4:58 PM, Randy Bush <randy@psg.com> wrote:

> > I would need a bit more clarity on what is "per circuit".  The
> > mechanism works by looking at the utilization on individual component
> > links within a LAG/ECMP.  The port-level queues and packet/byte
> > counters are always visible to an implementation.
>
> for some definitions of 'always'.  a few of us would greatly appreciate
> if you could tell us the commands on junos and cisco XR to look at a
> lag's per-physical-circuit queues.
>
> randy
>

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

<div dir=3D"ltr">Randy,<div><br></div><div>Please clarify what you mean by =
per-physical circuit queues. =A0There is no mention of that term in this dr=
aft. =A0</div><div><br></div><div>We deal with per physical port counters. =
=A0Finding those should be pretty straightforward on any router. =A0Please =
see section 5.6.1:</div>
<div><a href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-large-flow-loa=
d-balancing-05#section-5.6.1">http://tools.ietf.org/html/draft-ietf-opsawg-=
large-flow-load-balancing-05#section-5.6.1</a><br></div><div>for what the d=
raft needs. =A0There are standard MIB objects for things like these.</div>
<div><br></div><div>Anoop</div></div><div class=3D"gmail_extra"><br><br><di=
v class=3D"gmail_quote">On Tue, Sep 10, 2013 at 4:58 PM, Randy Bush <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:randy@psg.com" target=3D"_blank">randy@psg=
.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"><div class=3D"im">&gt; I would need a bit mo=
re clarity on what is &quot;per circuit&quot;. =A0The<br>
&gt; mechanism works by looking at the utilization on individual component<=
br>
&gt; links within a LAG/ECMP. =A0The port-level queues and packet/byte<br>
&gt; counters are always visible to an implementation.<br>
<br>
</div>for some definitions of &#39;always&#39;. =A0a few of us would greatl=
y appreciate<br>
if you could tell us the commands on junos and cisco XR to look at a<br>
lag&#39;s per-physical-circuit queues.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
randy<br>
</font></span></blockquote></div><br></div>

--f46d043c7f568dced104e6106b49--

From haibin.song@huawei.com  Tue Sep 10 19:20:04 2013
Return-Path: <haibin.song@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12CE221E80D5 for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 19:20:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gY9kHezGdKWd for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 19:19:58 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id DFB7221E80DA for <opsawg@ietf.org>; Tue, 10 Sep 2013 19:19:57 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AVG95908; Wed, 11 Sep 2013 02:19:52 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 11 Sep 2013 03:19:40 +0100
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 11 Sep 2013 03:19:49 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.141]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0146.000; Wed, 11 Sep 2013 10:19:44 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: "Cao,Zhen" <zehn.cao@gmail.com>
Thread-Topic: [OPSAWG] FW: New Version Notification for draft-song-opsawg-virtual-network-function-config-00.txt
Thread-Index: AQHOrjSIYcKUT/d37E2SucSXokpvXpm/wwYw
Date: Wed, 11 Sep 2013 02:19:43 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F247B2421@nkgeml501-mbs.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F247A21EA@nkgeml501-mbs.china.huawei.com> <CAProHATCVwfhjP6qXqCh+B65p_Eht=FexRtKeCKWXUL1hxvobQ@mail.gmail.com>
In-Reply-To: <CAProHATCVwfhjP6qXqCh+B65p_Eht=FexRtKeCKWXUL1hxvobQ@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.66]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] FW: New Version Notification for draft-song-opsawg-virtual-network-function-config-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2013 02:20:04 -0000

Hi Cao Zhen

Thank you for your excellent comments! Please see my reply inline.


-----Original Message-----
From: Cao,Zhen [mailto:zehn.cao@gmail.com]=20
Sent: Tuesday, September 10, 2013 10:46 PM
To: Songhaibin (A)
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] FW: New Version Notification for draft-song-opsawg-vi=
rtual-network-function-config-00.txt

Thanks for the draft. I have some comments as below:

Comments for section 3 about service configuration problems.

some more problems from my understanding
1. service chain requirement could be submitted by the user to the
Controller

[Haibin] I agree! A user can directly establish a service chain or service =
chains. For the service graph, there can be two layers IMO, one is the stab=
le virtual link layer, and the other is conditional/stable service forwardi=
ng layer. I also noticed that there was a network service chain BOF at last=
 IETF meeting. But they are focusing on how to identify a service chain and=
 how to do the forwarding in the service chain. But for the requirement her=
e, we only want the user the send the description to the controller.

2. service elasticity requirements should be specified by the user
[Haibin] I have some description of this use case in the last paragraph of =
Section 1. Just like that the user tells the controller, "allocate resource=
s on-demand for me". Do you have some good idea in-mind on what are the ela=
sticity requirements?


3. in addition to software versions, the user also want to specify the
operating system versions.

[Haibin] I agree. That's part of the installation environment requirement.

   There are also resource requirements for the remote software
   installation, which are complement to the software components
   selection.  There is lack of a standard for a user to tell the
   controller how much bandwidth, storage, CPU, memory are allocated to
   a specific software in the provider's network (perhaps there is
   existing standard for the virtual machine or host level resources),

[cz] but the Openstack-Neutron have such APIs to specify the user's
request , better to notice the difference here.

[Haibin] VNF level and VM level are different. Because one VM might be hold=
ing multiple VNFs. That interface you mentioned is combined with a VM IMO a=
nd are not easy to make a change. But here when the resource is combined wi=
th a VNF. It is much easier to change it. Any thoughts?

=3D=3Dquote
4.  Scope for Standardization

   (1) A protocol between the user and controller for software
   installation components choices, dynamic service configuration
   through the controller, and the resource requirements for the
   installation.

   (2) A protocol between software vendor and the controller for the
   detailed description of the software components and the recommended
   resource requirements for service instance.

[cz] Envision a picture here. and what's the operator's role in the picture=
,
i believe the operator-controller interface should also be specified ,
maybe add a (3).

[Haibin] IMO, operator owns the controller. OSS/BSS for the NFV service is =
part of the controller. But the network administrator from the operator can=
 also act as a user to install and configure VNFs in the provider's (operat=
or's) network for the customers or for himself. This is the picture in my m=
ind. Is it consistent with what you have in mind?

Very good feedback, thank you again!

Regards!
-Haibin



On Sun, Sep 8, 2013 at 11:59 PM, Songhaibin (A) <haibin.song@huawei.com> wr=
ote:
> Hi guys,
>
> Here is a new draft on virtual network function configuration. Any commen=
ts are welcome!
>
> BR,
> -Haibin
> Huawei Technologies Co., Ltd.
>
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Friday, September 06, 2013 9:29 AM
> To: Songhaibin (A)
> Subject: New Version Notification for draft-song-opsawg-virtual-network-f=
unction-config-00.txt
>
>
> A new version of I-D, draft-song-opsawg-virtual-network-function-config-0=
0.txt
> has been successfully submitted by Haibin Song and posted to the
> IETF repository.
>
> Filename:        draft-song-opsawg-virtual-network-function-config
> Revision:        00
> Title:           The Problems of Virtual Network Function Configuration
> Creation date:   2013-09-06
> Group:           Individual Submission
> Number of pages: 7
> URL:             http://www.ietf.org/internet-drafts/draft-song-opsawg-vi=
rtual-network-function-config-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-song-opsawg-virtua=
l-network-function-config
> Htmlized:        http://tools.ietf.org/html/draft-song-opsawg-virtual-net=
work-function-config-00
>
>
> Abstract:
>    This document describes the problem space of remote service
>    installation and configuration in the provider's network through a
>    centralized management system.  This is a typical scenario for
>    virtual function installation and dynamic configuration in network
>    function virtualization (NFV) context.  It is also a typical scenario
>    in cloud computing environment where end users do not have to install
>    applications in their end hosts, but can install their own featured
>    powerful software application in the cloud.  This specification also
>    identifies the scope that needs standardization based on the
>    problems.
>
>
>
>
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg

From joelja@bogus.com  Tue Sep 10 20:54:32 2013
Return-Path: <joelja@bogus.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27F3711E812B for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 20:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 R+YiNNVvuLA5 for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 20:54:31 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7A6E911E80EA for <opsawg@ietf.org>; Tue, 10 Sep 2013 20:54:31 -0700 (PDT)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r8B3sR2X070058 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 11 Sep 2013 03:54:27 GMT (envelope-from joelja@bogus.com)
Message-ID: <522FE96D.1050305@bogus.com>
Date: Tue, 10 Sep 2013 20:54:21 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>, Anoop Ghanwani <anoop@alumni.duke.edu>
References: <52191268.5070500@gmail.com>	<9904FB1B0159DA42B0B887B7FA8119CA128CE68A@AZ-FFEXMB04.global.avaya.com>	<CA+-tSzxzrGgbEH1cULg+CBVEhR1mQw90u7PSe9meDNAwdWrN1Q@mail.gmail.com>	<9904FB1B0159DA42B0B887B7FA8119CA128CF4C1@AZ-FFEXMB04.global.avaya.com>	<522F5AE8.1090706@gmail.com>	<CA+-tSzyiz6CeWecs64y6feWbZ1vFkkwfmbXssP3qGViaAk=OYA@mail.gmail.com> <m238pckz42.wl%randy@psg.com>
In-Reply-To: <m238pckz42.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 11 Sep 2013 03:54:28 +0000 (UTC)
Cc: "draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org" <draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2013 03:54:32 -0000

On 9/10/13 4:58 PM, Randy Bush wrote:
>> I would need a bit more clarity on what is "per circuit".  The
>> mechanism works by looking at the utilization on individual component
>> links within a LAG/ECMP.  The port-level queues and packet/byte
>> counters are always visible to an implementation.
> 
> for some definitions of 'always'.  a few of us would greatly appreciate
> if you could tell us the commands on junos and cisco XR to look at a
> lag's per-physical-circuit queues.

In a distributed forwarding architecture, individual linecards or indeed
routers in the case of various MCLAG implementations may have little
timely insight into the port level queues on all lag members.

> randy
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
> 


From ghanwani@gmail.com  Tue Sep 10 22:34:21 2013
Return-Path: <ghanwani@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B705211E815C for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 22:34:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p+KjCiLNI15O for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 22:34:21 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id C498A11E8118 for <opsawg@ietf.org>; Tue, 10 Sep 2013 22:34:20 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id f12so7322748wgh.2 for <opsawg@ietf.org>; Tue, 10 Sep 2013 22:34:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=KRypytTuFugeWnLByIu3RJef13GP+6C+y1rljxijFoo=; b=KtjOUwu0YFKx8xMj1bHdgQqWL0G5J/po9xm8RWwwW1BbzUnXGbWzdZhtr+cicOHdZp wH5HYVUIH8ulr4mibbNuYfzOeHMcPkjBkG1gJlo0NBUxDuAF3PWXveiGU9W8fJNdmz0X c3SXHFYxYnGX+O92tPFAxsNOgOU/HVp4ve4bSln8lQCFX5ByRzwHsETGPia97J+6JG2O NjeNYQ/3S8Ri88Wa3R+bytmETjmTsPGwTByAOA4zqXemMt1O94rjUhtnyRQPLXNXpyOG G2KRdATy3xBHfBA8us00QBxdVFVL5sK8VNyPKDlzhMviV7uo5VyVUuSx0WmpEQK6MQyh 5lWg==
MIME-Version: 1.0
X-Received: by 10.180.184.107 with SMTP id et11mr15904469wic.60.1378877659776;  Tue, 10 Sep 2013 22:34:19 -0700 (PDT)
Sender: ghanwani@gmail.com
Received: by 10.217.54.6 with HTTP; Tue, 10 Sep 2013 22:34:19 -0700 (PDT)
In-Reply-To: <522FE96D.1050305@bogus.com>
References: <52191268.5070500@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CE68A@AZ-FFEXMB04.global.avaya.com> <CA+-tSzxzrGgbEH1cULg+CBVEhR1mQw90u7PSe9meDNAwdWrN1Q@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CF4C1@AZ-FFEXMB04.global.avaya.com> <522F5AE8.1090706@gmail.com> <CA+-tSzyiz6CeWecs64y6feWbZ1vFkkwfmbXssP3qGViaAk=OYA@mail.gmail.com> <m238pckz42.wl%randy@psg.com> <522FE96D.1050305@bogus.com>
Date: Tue, 10 Sep 2013 22:34:19 -0700
X-Google-Sender-Auth: HOD7RSIxth7yyGN1s1RaOCPajiU
Message-ID: <CA+-tSzzQVuFj32vst-xRm4FSfis83Hazm=0vQevK=08Jv0uMWA@mail.gmail.com>
From: Anoop Ghanwani <anoop@alumni.duke.edu>
To: joel jaeggli <joelja@bogus.com>
Content-Type: multipart/alternative; boundary=001a11c227ee198cb704e614f99b
Cc: "draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org" <draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2013 05:34:21 -0000

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

On Tue, Sep 10, 2013 at 8:54 PM, joel jaeggli <joelja@bogus.com> wrote:

> On 9/10/13 4:58 PM, Randy Bush wrote:
> >> I would need a bit more clarity on what is "per circuit".  The
> >> mechanism works by looking at the utilization on individual component
> >> links within a LAG/ECMP.  The port-level queues and packet/byte
> >> counters are always visible to an implementation.
> >
> > for some definitions of 'always'.  a few of us would greatly appreciate
> > if you could tell us the commands on junos and cisco XR to look at a
> > lag's per-physical-circuit queues.
>
> In a distributed forwarding architecture, individual linecards or indeed
> routers in the case of various MCLAG implementations may have little
> timely insight into the port level queues on all lag members.
>
> Joel,

One of the tools we discuss in the draft is sflow.  sflow is capable of
providing network-wide statistics within the time intervals we are talking
about (on the order of seconds).  And this is sufficient for the problem we
are trying to solve.  In fact, trying to solve it on fine timescales may be
counterproductive.

But you do bring up a good issue with MCLAG.  We have not tried to address
that in this document.  Lets take a simple example.  If we have a 2-chassis
system and we have an MCLAG to these two routers, typically whichever
router receives the traffic that is destined for the MCLAG will place it on
its local link.  So really, this becomes a fairly complex global network
optimization issue where one would have to make sure that the equal amounts
of traffic hits each of the routers. It may be possible to solve it by
identifying large flows globally and using PBR entries to ensure they are
routed to the desired router so that it exits on the desired component
link.  If you think it is worth adding some text, we can do that.

Anoop

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Sep 10, 2013 at 8:54 PM, joel jaeggli <span dir=3D"ltr">&lt=
;<a href=3D"mailto:joelja@bogus.com" target=3D"_blank">joelja@bogus.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"><div class=3D"HOEnZb"><div class=3D"h5">On 9=
/10/13 4:58 PM, Randy Bush wrote:<br>
&gt;&gt; I would need a bit more clarity on what is &quot;per circuit&quot;=
. =A0The<br>
&gt;&gt; mechanism works by looking at the utilization on individual compon=
ent<br>
&gt;&gt; links within a LAG/ECMP. =A0The port-level queues and packet/byte<=
br>
&gt;&gt; counters are always visible to an implementation.<br>
&gt;<br>
&gt; for some definitions of &#39;always&#39;. =A0a few of us would greatly=
 appreciate<br>
&gt; if you could tell us the commands on junos and cisco XR to look at a<b=
r>
&gt; lag&#39;s per-physical-circuit queues.<br>
<br>
</div></div>In a distributed forwarding architecture, individual linecards =
or indeed<br>
routers in the case of various MCLAG implementations may have little<br>
timely insight into the port level queues on all lag members.<br><div class=
=3D"HOEnZb"><div class=3D"h5"><br></div></div></blockquote><div>Joel,</div>=
<div><br></div><div>One of the tools we discuss in the draft is sflow. =A0s=
flow is capable of providing network-wide statistics within the time interv=
als we are talking about (on the order of seconds). =A0And this is sufficie=
nt for the problem we are trying to solve. =A0In fact, trying to solve it o=
n fine timescales may be counterproductive.</div>
<div><br></div><div>But you do bring up a good issue with MCLAG. =A0We have=
 not tried to address that in this document. =A0Lets take a simple example.=
 =A0If we have a 2-chassis system and we have an MCLAG to these two routers=
, typically whichever router receives the traffic that is destined for the =
MCLAG will place it on its local link. =A0So really, this becomes a fairly =
complex global network optimization issue where one would have to make sure=
 that the equal amounts of traffic hits each of the routers. It may be poss=
ible to solve it by identifying large flows globally and using PBR entries =
to ensure they are routed to the desired router so that it exits on the des=
ired component link. =A0If you think it is worth adding some text, we can d=
o that.</div>
<div><br></div><div>Anoop</div></div><br></div></div>

--001a11c227ee198cb704e614f99b--

From mshaikh@Brocade.com  Tue Sep 10 23:46:00 2013
Return-Path: <mshaikh@Brocade.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF71621F99FB for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 23:46:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.264
X-Spam-Level: 
X-Spam-Status: No, score=-3.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1]
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 MDqyvPqbYI1r for <opsawg@ietfa.amsl.com>; Tue, 10 Sep 2013 23:45:56 -0700 (PDT)
Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) by ietfa.amsl.com (Postfix) with ESMTP id 9C2DE21F99F4 for <opsawg@ietf.org>; Tue, 10 Sep 2013 23:45:49 -0700 (PDT)
Received: from pps.filterd (m0000700 [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.14.5/8.14.5) with SMTP id r8B6MiUL020651; Tue, 10 Sep 2013 23:45:49 -0700
Received: from hq1wp-exchub02.corp.brocade.com ([144.49.131.13]) by mx0b-000f0801.pphosted.com with ESMTP id 1et6jfryh6-9 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 10 Sep 2013 23:45:49 -0700
Received: from HQ1WP-EXHUB02.corp.brocade.com (10.70.38.14) by hq1wp-exchub02.corp.brocade.com (10.70.38.99) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 10 Sep 2013 23:45:49 -0700
Received: from HQ1-EXCH02.corp.brocade.com ([fe80::8c73:93bf:41b4:1443]) by HQ1WP-EXHUB02.corp.brocade.com ([fe80::e1f4:a4c8:696b:3780%10]) with mapi; Tue, 10 Sep 2013 23:45:40 -0700
From: Mukhtiar Shaikh <mshaikh@Brocade.com>
To: ramki Krishnan <ramk@Brocade.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Date: Tue, 10 Sep 2013 23:45:42 -0700
Thread-Topic: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
Thread-Index: Ac6uuoZipySRTtqeTtu/pyb6CNuyfQ==
Message-ID: <CE5552F5.421B1%mshaikh@brocade.com>
In-Reply-To: <C7634EB63EFD984A978DFB46EA5174F2BFFE958FE2@HQ1-EXCH01.corp.brocade.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.6.130613
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CE5552F5421B1mshaikhbrocadecom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-09-11_01:2013-09-11, 2013-09-11, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1309100221
Cc: "opsawg-chairs@tools.ietf.org" <opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2013 06:46:01 -0000

--_000_CE5552F5421B1mshaikhbrocadecom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Thanks Ramki. Please see comments inline:

From: ramki Krishnan <ramk@Brocade.com<mailto:ramk@Brocade.com>>
Date: Tuesday, September 10, 2013 2:04 PM
To: Mukhtiar Shaikh <mshaikh@brocade.com<mailto:mshaikh@brocade.com>>, "ops=
awg@ietf.org<mailto:opsawg@ietf.org>" <opsawg@ietf.org<mailto:opsawg@ietf.o=
rg>>
Cc: "opsawg-chairs@tools.ietf.org<mailto:opsawg-chairs@tools.ietf.org>" <op=
sawg-chairs@tools.ietf.org<mailto:opsawg-chairs@tools.ietf.org>>
Subject: RE: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Com=
ponent Link Utilization in Networks"

Hi Mukhtiar,

Thanks for your comments. Please find answers inline.
>>I think section 4.3.4. Automatic Hardware Recognition is a little vague. =
It is not clear how and what is expected from the hardware to detect the la=
rge flows. Is it sampling of packet forwarding counters in hardware or some=
thing else? Any clarity on this will be good.
Since the details are implementation specific, we are not planning on expan=
ding this section =96 IETF does not recommend specific implementations.

<MK> I was not suggesting to expand using implementation specific details..=
I was thinking of including some general examples such faster sampling capa=
bility in hardware, hardware packet counters etc

>> Also, from operational considerations point of view, as indicated in sec=
tion 6, frequent rebalancing of flows could be counter productive leading t=
o out of order packets and /or system instability. Similar challenges could=
 arise from immediate rebalancing of flows on one or more component links i=
n the LAG experiencing frequent failures. System may implement a throttling=
 mechanism to regulate when and what types of flows are re-distributed to p=
otentially flaky links to avoid instability.
Flaky links should be detected by the system and removed from the LAG right=
 ? I am not sure if there is anything specific we need to for large flow LA=
G load balancing.

<MK>The problem is not necessarily when a link is removed from the LAG upon=
 failure..but when it comes back up. Again, the assumption here is that lin=
k has been experiencing repeated failures and every time it comes back up, =
flows need to be readjusted. Therefore, if there is a history of failures o=
n a given link in the LAG, rebalancing could be done in a more conservative=
 way to minimize instability.

Regards,
-Mukhtiar

Thanks,
Ramki

From: opsawg-bounces@ietf.org<mailto:opsawg-bounces@ietf.org> [mailto:opsaw=
g-bounces@ietf.org] On Behalf Of Mukhtiar Shaikh
Sent: Monday, September 09, 2013 10:54 PM
To: opsawg@ietf.org<mailto:opsawg@ietf.org>
Cc: opsawg-chairs@tools.ietf.org<mailto:opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Com=
ponent Link Utilization in Networks"

I support the publication of this document as informational RFC. Have a cou=
ple of additional comments.

I think section 4.3.4. Automatic Hardware Recognition is a little vague. It=
 is not clear how and what is expected from the hardware to detect the larg=
e flows. Is it sampling of packet forwarding counters in hardware or someth=
ing else? Any clarity on this will be good.

Also, from operational considerations point of view, as indicated in sectio=
n 6, frequent rebalancing of flows could be counter productive leading to o=
ut of order packets and /or system instability. Similar challenges could ar=
ise from immediate rebalancing of flows on one or more component links in t=
he LAG experiencing frequent failures. System may implement a throttling me=
chanism to regulate when and what types of flows are re-distributed to pote=
ntially flaky links to avoid instability.

Thanks,
-Mukhtiar




-----Original Message-----
From: opsawg-bounces@ietf.org<mailto:opsawg-bounces@ietf.org> [mailto:opsaw=
g-bounces@ietf.org] On Behalf Of Melinda Shore
Sent: Saturday, August 24, 2013 1:07 PM
To: opsawg@ietf.org<mailto:opsawg@ietf.org>
Cc: opsawg-chairs@tools.ietf.org<mailto:opsawg-chairs@tools.ietf.org>
Subject: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Compone=
nt Link Utilization in Networks"



This is to announce the start of working group last call on:



    Mechanisms for Optimal LAG/ECMP Component Link Utilization in

        Networks



http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-balancing=
/



It is intended for publication as an informational RFC.



Please give it a careful read and provide any feedback to this mailing list=
 by September 9, 2013



Thanks,



opsawg chairs

_______________________________________________

OPSAWG mailing list

OPSAWG@ietf.org<mailto:OPSAWG@ietf.org>

https://www.ietf.org/mailman/listinfo/opsawg

--_000_CE5552F5421B1mshaikhbrocadecom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252"></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space;=
 -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14p=
x; font-family: Calibri, sans-serif; "><div>Thanks Ramki. Please see commen=
ts inline:</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><div style=
=3D"font-family:Calibri; font-size:11pt; text-align:left; color:black; BORD=
ER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADD=
ING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RI=
GHT: medium none; PADDING-TOP: 3pt"><span style=3D"font-weight:bold">From: =
</span> ramki Krishnan &lt;<a href=3D"mailto:ramk@Brocade.com">ramk@Brocade=
.com</a>&gt;<br><span style=3D"font-weight:bold">Date: </span> Tuesday, Sep=
tember 10, 2013 2:04 PM<br><span style=3D"font-weight:bold">To: </span> Muk=
htiar Shaikh &lt;<a href=3D"mailto:mshaikh@brocade.com">mshaikh@brocade.com=
</a>&gt;, &quot;<a href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</a>&quot=
; &lt;<a href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</a>&gt;<br><span s=
tyle=3D"font-weight:bold">Cc: </span> &quot;<a href=3D"mailto:opsawg-chairs=
@tools.ietf.org">opsawg-chairs@tools.ietf.org</a>&quot; &lt;<a href=3D"mail=
to:opsawg-chairs@tools.ietf.org">opsawg-chairs@tools.ietf.org</a>&gt;<br><s=
pan style=3D"font-weight:bold">Subject: </span> RE: [OPSAWG] WG last call f=
or &quot;Mechanisms for Optimal LAG/ECMP Component Link Utilization in Netw=
orks&quot;<br></div><div><br></div><div xmlns:v=3D"urn:schemas-microsoft-co=
m:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:s=
chemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/o=
ffice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><meta name=3D=
"Generator" content=3D"Microsoft Word 12 (filtered medium)"><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--><div lang=3D"EN-US" link=3D"blue" vlink=
=3D"purple"><div class=3D"Section1"><p class=3D"MsoNormal">Hi Mukhtiar,<o:p=
></o:p></p><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p><p class=3D"MsoNorma=
l">Thanks for your comments. Please find answers inline.<o:p></o:p></p><p c=
lass=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:a=
uto">&gt;&gt;I think section 4.3.4. Automatic Hardware Recognition is a lit=
tle vague. It is not clear how and what is expected from the hardware to de=
tect the large flows. Is it sampling of
 packet forwarding counters in hardware or&nbsp;something&nbsp;else? Any cl=
arity on this will be good.<o:p></o:p></p><p class=3D"MsoNormal" style=3D"m=
so-margin-top-alt:auto;mso-margin-bottom-alt:auto">Since the details are im=
plementation specific, we are not planning on expanding this section =96 IE=
TF does not recommend specific implementations.</p></div></div></div></span=
><div><br></div><div>&lt;MK&gt; I was not suggesting to expand using implem=
entation specific details..I was thinking of including some general example=
s such faster sampling capability in hardware, hardware packet counters etc=
</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><div xmlns:v=3D"urn:=
schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:offi=
ce" xmlns:w=3D"urn:schemas-microsoft-com:office:word" xmlns:m=3D"http://sch=
emas.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-h=
tml40"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"Sec=
tion1"><p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-b=
ottom-alt:auto"><o:p></o:p></p><p class=3D"MsoNormal" style=3D"mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto">&gt;&gt; Also, from operational con=
siderations point of view, as indicated in section 6, frequent rebalancing =
of flows could be counter productive leading to out of order packets and
 /or system instability. Similar challenges could arise from immediate reba=
lancing of flows on one or more component links in the LAG experiencing fre=
quent failures. System may implement a throttling mechanism to regulate whe=
n and what types of flows are re-distributed
 to potentially flaky links to avoid instability.<span style=3D"font-family=
: Cambria, serif; "><o:p></o:p></span></p><p class=3D"MsoNormal" style=3D"m=
so-margin-top-alt:auto;mso-margin-bottom-alt:auto">Flaky links should be de=
tected by the system and removed from the LAG right ? I am not sure if ther=
e is anything specific we need to for large flow LAG load balancing.</p></d=
iv></div></div></span><div><br></div><div>&lt;MK&gt;The problem is not nece=
ssarily when a link is removed from the LAG upon failure..but when it comes=
 back up. Again, the assumption here is that link has been experiencing rep=
eated failures and every time it comes back up, flows need to be readjusted=
. Therefore, if there is a history of failures on a given link in the LAG, =
rebalancing could be done in a more conservative way to minimize instabilit=
y.</div><div><br></div><div>Regards,</div><div>-Mukhtiar</div><div><br></di=
v><span id=3D"OLK_SRC_BODY_SECTION"><div xmlns:v=3D"urn:schemas-microsoft-c=
om:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:=
schemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/=
office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><div lang=3D=
"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"Section1"><p class=3D"=
MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><o:=
p></o:p></p><p class=3D"MsoNormal">Thanks,<o:p></o:p></p><p class=3D"MsoNor=
mal">Ramki<o:p></o:p></p><p class=3D"MsoNormal"><span style=3D"color:#1F497=
D"><o:p>&nbsp;</o:p></span></p><div><div style=3D"border:none;border-top:so=
lid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class=3D"MsoNormal"><b><spa=
n style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span>=
</b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; "> <a =
href=3D"mailto:opsawg-bounces@ietf.org">opsawg-bounces@ietf.org</a> [<a hre=
f=3D"mailto:opsawg-bounces@ietf.org">mailto:opsawg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Mukhtiar Shaikh<br><b>Sent:</b> Monday, September 09, 2=
013 10:54 PM<br><b>To:</b> <a href=3D"mailto:opsawg@ietf.org">opsawg@ietf.o=
rg</a><br><b>Cc:</b> <a href=3D"mailto:opsawg-chairs@tools.ietf.org">opsawg=
-chairs@tools.ietf.org</a><br><b>Subject:</b> Re: [OPSAWG] WG last call for=
 &quot;Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networ=
ks&quot;<o:p></o:p></span></p></div></div><p class=3D"MsoNormal"><o:p>&nbsp=
;</o:p></p><div><p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso=
-margin-bottom-alt:auto"><span style=3D"color:black">I support the publicat=
ion of this document as informational RFC. Have a couple of additional comm=
ents.</span><span style=3D"font-family: Cambria, serif; color: black; "><o:=
p></o:p></span></p><p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;=
mso-margin-bottom-alt:auto"><span style=3D"color:black">&nbsp;</span><span =
style=3D"font-family: Cambria, serif; color: black; "><o:p></o:p></span></p=
><p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto"><span style=3D"color:black">I think section 4.3.4. Automatic Hard=
ware Recognition is a little vague. It is not clear how and what is expecte=
d from the hardware to detect the large
 flows. Is it sampling of packet forwarding counters in hardware or&nbsp;so=
mething&nbsp;else? Any clarity on this will be good.</span><span style=3D"f=
ont-family: Cambria, serif; color: black; "><o:p></o:p></span></p><p class=
=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"=
><span style=3D"color:black">&nbsp;</span><span style=3D"font-family: Cambr=
ia, serif; color: black; "><o:p></o:p></span></p><p class=3D"MsoNormal" sty=
le=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style=3D"co=
lor:black">Also, from operational considerations point of view, as indicate=
d in section 6, frequent rebalancing of flows could be counter productive l=
eading to out
 of order packets and /or system instability. Similar challenges could aris=
e from immediate rebalancing of flows on one or more component links in the=
 LAG experiencing frequent failures. System may implement a throttling mech=
anism to regulate when and what
 types of flows are re-distributed to potentially flaky links to avoid inst=
ability.</span><span style=3D"font-family: Cambria, serif; color: black; ">=
<o:p></o:p></span></p><p class=3D"MsoNormal" style=3D"mso-margin-top-alt:au=
to;mso-margin-bottom-alt:auto"><span style=3D"color:black">&nbsp;</span><sp=
an style=3D"font-family: Cambria, serif; color: black; "><o:p></o:p></span>=
</p><p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto"><span style=3D"color:black">Thanks,</span><span style=3D"font-=
family: Cambria, serif; color: black; "><o:p></o:p></span></p><p class=3D"M=
soNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><spa=
n style=3D"color:black">-Mukhtiar</span><span style=3D"font-family: Cambria=
, serif; color: black; "><o:p></o:p></span></p></div><div><p class=3D"MsoNo=
rmal"><span style=3D"font-size:10.5pt;color:black"><o:p>&nbsp;</o:p></span>=
</p></div><div><div><div><p class=3D"MsoPlainText"><span style=3D"font-size=
:10.5pt;color:black">&nbsp;<o:p></o:p></span></p><p class=3D"MsoPlainText">=
<span style=3D"font-size:10.5pt;color:black">-----Original Message-----<br>
From: <a href=3D"mailto:opsawg-bounces@ietf.org">opsawg-bounces@ietf.org</a=
> [<a href=3D"mailto:opsawg-bounces@ietf.org">mailto:opsawg-bounces@ietf.or=
g</a>] On Behalf Of Melinda Shore<br>
Sent: Saturday, August 24, 2013 1:07 PM<br>
To: <a href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</a><br>
Cc: <a href=3D"mailto:opsawg-chairs@tools.ietf.org">opsawg-chairs@tools.iet=
f.org</a><br>
Subject: [OPSAWG] WG last call for &quot;Mechanisms for Optimal LAG/ECMP Co=
mponent Link Utilization in Networks&quot;<o:p></o:p></span></p><p class=3D=
"MsoPlainText"><span style=3D"font-size:10.5pt;color:black">&nbsp;<o:p></o:=
p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size:10.5pt;colo=
r:black">This is to announce the start of working group last call on:<o:p><=
/o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size:10.5pt;c=
olor:black">&nbsp;<o:p></o:p></span></p><p class=3D"MsoPlainText"><span sty=
le=3D"font-size:10.5pt;color:black">&nbsp;&nbsp;&nbsp; Mechanisms for Optim=
al LAG/ECMP Component Link Utilization in<o:p></o:p></span></p><p class=3D"=
MsoPlainText"><span style=3D"font-size:10.5pt;color:black">&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; Networks<o:p></o:p></span></p><p class=3D"MsoPla=
inText"><span style=3D"font-size:10.5pt;color:black">&nbsp;<o:p></o:p></spa=
n></p><p class=3D"MsoPlainText"><span style=3D"font-size:10.5pt;color:black=
"><a href=3D"http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-l=
oad-balancing/"><span style=3D"color:windowtext;text-decoration:none">http:=
//datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-balancing/</sp=
an></a><o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-=
size:10.5pt;color:black">&nbsp;<o:p></o:p></span></p><p class=3D"MsoPlainTe=
xt"><span style=3D"font-size:10.5pt;color:black">It is intended for publica=
tion as an informational RFC.<o:p></o:p></span></p><p class=3D"MsoPlainText=
"><span style=3D"font-size:10.5pt;color:black">&nbsp;<o:p></o:p></span></p>=
<p class=3D"MsoPlainText"><span style=3D"font-size:10.5pt;color:black">Plea=
se give it a careful read and provide any feedback to this mailing list by =
September 9, 2013<o:p></o:p></span></p><p class=3D"MsoPlainText"><span styl=
e=3D"font-size:10.5pt;color:black">&nbsp;<o:p></o:p></span></p><p class=3D"=
MsoPlainText"><span style=3D"font-size:10.5pt;color:black">Thanks,<o:p></o:=
p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size:10.5pt;colo=
r:black">&nbsp;<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=
=3D"font-size:10.5pt;color:black">opsawg chairs<o:p></o:p></span></p><p cla=
ss=3D"MsoPlainText"><span style=3D"font-size:10.5pt;color:black">__________=
_____________________________________<o:p></o:p></span></p><p class=3D"MsoP=
lainText"><span style=3D"font-size:10.5pt;color:black">OPSAWG mailing list<=
o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size:10.=
5pt;color:black"><a href=3D"mailto:OPSAWG@ietf.org"><span style=3D"color:wi=
ndowtext;text-decoration:
none">OPSAWG@ietf.org</span></a><o:p></o:p></span></p><p class=3D"MsoPlainT=
ext"><span style=3D"font-size:10.5pt;color:black"><a href=3D"https://www.ie=
tf.org/mailman/listinfo/opsawg"><span style=3D"color:windowtext;
text-decoration:none">https://www.ietf.org/mailman/listinfo/opsawg</span></=
a><o:p></o:p></span></p></div></div></div></div></div></div></span></body><=
/html>

--_000_CE5552F5421B1mshaikhbrocadecom_--

From warren@kumari.net  Wed Sep 11 07:04:13 2013
Return-Path: <warren@kumari.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DCC421F92E0 for <opsawg@ietfa.amsl.com>; Wed, 11 Sep 2013 07:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 Ctz5jRVoUBI3 for <opsawg@ietfa.amsl.com>; Wed, 11 Sep 2013 07:04:08 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9765C11E816D for <opsawg@ietf.org>; Wed, 11 Sep 2013 07:04:08 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.103]) by vimes.kumari.net (Postfix) with ESMTPSA id 81E431B40122; Wed, 11 Sep 2013 10:04:07 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <m238pckz42.wl%randy@psg.com>
Date: Wed, 11 Sep 2013 10:04:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8665CBFB-3A3F-4834-AB5E-8E319910BA64@kumari.net>
References: <52191268.5070500@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CE68A@AZ-FFEXMB04.global.avaya.com> <CA+-tSzxzrGgbEH1cULg+CBVEhR1mQw90u7PSe9meDNAwdWrN1Q@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CF4C1@AZ-FFEXMB04.global.avaya.com> <522F5AE8.1090706@gmail.com> <CA+-tSzyiz6CeWecs64y6feWbZ1vFkkwfmbXssP3qGViaAk=OYA@mail.gmail.com> <m238pckz42.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1508)
Cc: "draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org" <draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2013 14:04:13 -0000

On Sep 10, 2013, at 7:58 PM, Randy Bush <randy@psg.com> wrote:

>> I would need a bit more clarity on what is "per circuit".  The
>> mechanism works by looking at the utilization on individual component
>> links within a LAG/ECMP.  The port-level queues and packet/byte
>> counters are always visible to an implementation.
>=20
> for some definitions of 'always'.  a few of us would greatly =
appreciate
> if you could tell us the commands on junos and cisco XR to look at a
> lag's per-physical-circuit queues.


Yes, yes we would.
A  large number of implementations provide almost no visibility into the =
interface queues (even if you throw your toys out the cot, threaten to =
change vendors, etc), regardless of if the interface is part of LAG or =
not=85

However, I don't think that the draft needs queue level information -- =
interface counters is sufficient. Or am I missing something?

W

>=20
> randy
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>=20

--
"When it comes to glittering objects, wizards have all the taste and =
self-control of a deranged magpie."
-- Terry Pratchett





From ramk@Brocade.com  Wed Sep 11 07:54:18 2013
Return-Path: <ramk@Brocade.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BE4511E819C for <opsawg@ietfa.amsl.com>; Wed, 11 Sep 2013 07:54:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.264
X-Spam-Level: 
X-Spam-Status: No, score=-3.264 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1]
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 3zjho2GvP6x1 for <opsawg@ietfa.amsl.com>; Wed, 11 Sep 2013 07:54:09 -0700 (PDT)
Received: from mx0a-000f0801.pphosted.com (mx0a-000f0801.pphosted.com [67.231.144.122]) by ietfa.amsl.com (Postfix) with ESMTP id 9500E11E816F for <opsawg@ietf.org>; Wed, 11 Sep 2013 07:54:09 -0700 (PDT)
Received: from pps.filterd (m0000542 [127.0.0.1]) by mx0a-000f0801.pphosted.com (8.14.5/8.14.5) with SMTP id r8BEVeHG012007; Wed, 11 Sep 2013 07:54:08 -0700
Received: from hq1wp-exchub01.corp.brocade.com ([144.49.131.13]) by mx0a-000f0801.pphosted.com with ESMTP id 1etk0h8n5u-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 11 Sep 2013 07:54:08 -0700
Received: from HQ1WP-EXHUB02.corp.brocade.com (10.70.38.14) by HQ1WP-EXCHUB01.corp.brocade.com (10.70.36.99) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 11 Sep 2013 07:54:07 -0700
Received: from HQ1-EXCH01.corp.brocade.com ([fe80::ed42:173e:fe7d:d0a6]) by HQ1WP-EXHUB02.corp.brocade.com ([fe80::e1f4:a4c8:696b:3780%10]) with mapi; Wed, 11 Sep 2013 07:54:06 -0700
From: ramki Krishnan <ramk@Brocade.com>
To: Warren Kumari <warren@kumari.net>, Randy Bush <randy@psg.com>
Date: Wed, 11 Sep 2013 07:53:45 -0700
Thread-Topic: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
Thread-Index: Ac6u9+rQvDPFzZbgRqqCTaIQvC5oTAABpflQ
Message-ID: <C7634EB63EFD984A978DFB46EA5174F2BFFE9590DA@HQ1-EXCH01.corp.brocade.com>
References: <52191268.5070500@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CE68A@AZ-FFEXMB04.global.avaya.com> <CA+-tSzxzrGgbEH1cULg+CBVEhR1mQw90u7PSe9meDNAwdWrN1Q@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA128CF4C1@AZ-FFEXMB04.global.avaya.com> <522F5AE8.1090706@gmail.com> <CA+-tSzyiz6CeWecs64y6feWbZ1vFkkwfmbXssP3qGViaAk=OYA@mail.gmail.com> <m238pckz42.wl%randy@psg.com> <8665CBFB-3A3F-4834-AB5E-8E319910BA64@kumari.net>
In-Reply-To: <8665CBFB-3A3F-4834-AB5E-8E319910BA64@kumari.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-09-11_04:2013-09-11, 2013-09-11, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1309110074
Cc: "draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org" <draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP	Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2013 14:54:18 -0000

>> However, I don't think that the draft needs queue level information -- i=
nterface counters is sufficient. Or am I missing something?

Thanks Warren -- you said it right. For this draft, we need only interface =
counters.

Thanks,
Ramki

-----Original Message-----
From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of=
 Warren Kumari
Sent: Wednesday, September 11, 2013 7:04 AM
To: Randy Bush
Cc: draft-krishnan-opsawg-large-flow-load-balancing@tools.ietf.org; opsawg@=
ietf.org
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Com=
ponent Link Utilization in Networks"


On Sep 10, 2013, at 7:58 PM, Randy Bush <randy@psg.com> wrote:

>> I would need a bit more clarity on what is "per circuit".  The
>> mechanism works by looking at the utilization on individual component
>> links within a LAG/ECMP.  The port-level queues and packet/byte
>> counters are always visible to an implementation.
>=20
> for some definitions of 'always'.  a few of us would greatly appreciate
> if you could tell us the commands on junos and cisco XR to look at a
> lag's per-physical-circuit queues.


Yes, yes we would.
A  large number of implementations provide almost no visibility into the in=
terface queues (even if you throw your toys out the cot, threaten to change=
 vendors, etc), regardless of if the interface is part of LAG or not...

However, I don't think that the draft needs queue level information -- inte=
rface counters is sufficient. Or am I missing something?

W

>=20
> randy
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>=20

--
"When it comes to glittering objects, wizards have all the taste and self-c=
ontrol of a deranged magpie."
-- Terry Pratchett




_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

From ramk@Brocade.com  Wed Sep 11 12:19:35 2013
Return-Path: <ramk@Brocade.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7218C21E80CE for <opsawg@ietfa.amsl.com>; Wed, 11 Sep 2013 12:19:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.264
X-Spam-Level: 
X-Spam-Status: No, score=-3.264 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1]
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 xfUFPw3lK1m3 for <opsawg@ietfa.amsl.com>; Wed, 11 Sep 2013 12:19:30 -0700 (PDT)
Received: from mx0a-000f0801.pphosted.com (mx0a-000f0801.pphosted.com [67.231.144.122]) by ietfa.amsl.com (Postfix) with ESMTP id 9744321E80E7 for <opsawg@ietf.org>; Wed, 11 Sep 2013 12:19:30 -0700 (PDT)
Received: from pps.filterd (m0000542 [127.0.0.1]) by mx0a-000f0801.pphosted.com (8.14.5/8.14.5) with SMTP id r8BItvvk004157; Wed, 11 Sep 2013 12:19:29 -0700
Received: from hq1wp-exchub01.corp.brocade.com ([144.49.131.13]) by mx0a-000f0801.pphosted.com with ESMTP id 1etk0h8xa0-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 11 Sep 2013 12:19:29 -0700
Received: from HQ1WP-EXHUB01.corp.brocade.com (10.70.36.14) by HQ1WP-EXCHUB01.corp.brocade.com (10.70.36.99) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 11 Sep 2013 12:19:28 -0700
Received: from HQ1-EXCH01.corp.brocade.com ([fe80::ed42:173e:fe7d:d0a6]) by HQ1WP-EXHUB01.corp.brocade.com ([::1]) with mapi; Wed, 11 Sep 2013 12:19:04 -0700
From: ramki Krishnan <ramk@Brocade.com>
To: Mukhtiar Shaikh <mshaikh@Brocade.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Date: Wed, 11 Sep 2013 12:18:42 -0700
Thread-Topic: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
Thread-Index: Ac6uuoZipySRTtqeTtu/pyb6CNuyfQAaBclg
Message-ID: <C7634EB63EFD984A978DFB46EA5174F2BFFE959191@HQ1-EXCH01.corp.brocade.com>
References: <C7634EB63EFD984A978DFB46EA5174F2BFFE958FE2@HQ1-EXCH01.corp.brocade.com> <CE5552F5.421B1%mshaikh@brocade.com>
In-Reply-To: <CE5552F5.421B1%mshaikh@brocade.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C7634EB63EFD984A978DFB46EA5174F2BFFE959191HQ1EXCH01corp_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-09-11_06:2013-09-11, 2013-09-11, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1309110103
Cc: "opsawg-chairs@tools.ietf.org" <opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2013 19:19:35 -0000

--_000_C7634EB63EFD984A978DFB46EA5174F2BFFE959191HQ1EXCH01corp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks Mukhtiar, more inline.

<MK>The problem is not necessarily when a link is removed from the LAG upon=
 failure..but when it comes back up. Again, the assumption here is that lin=
k has been experiencing repeated failures and every time it comes back up, =
flows need to be readjusted. Therefore, if there is a history of failures o=
n a given link in the LAG, rebalancing could be done in a more conservative=
 way to minimize instability.

Good point. What you are bringing up would be applicable for normal LAG als=
o - we could potentially reduce the weight of the LAG member ports connecte=
d to flaky links.

Thanks,
Ramki

From: Mukhtiar Shaikh
Sent: Tuesday, September 10, 2013 11:46 PM
To: ramki Krishnan; opsawg@ietf.org
Cc: opsawg-chairs@tools.ietf.org
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Com=
ponent Link Utilization in Networks"

Thanks Ramki. Please see comments inline:

From: ramki Krishnan <ramk@Brocade.com<mailto:ramk@Brocade.com>>
Date: Tuesday, September 10, 2013 2:04 PM
To: Mukhtiar Shaikh <mshaikh@brocade.com<mailto:mshaikh@brocade.com>>, "ops=
awg@ietf.org<mailto:opsawg@ietf.org>" <opsawg@ietf.org<mailto:opsawg@ietf.o=
rg>>
Cc: "opsawg-chairs@tools.ietf.org<mailto:opsawg-chairs@tools.ietf.org>" <op=
sawg-chairs@tools.ietf.org<mailto:opsawg-chairs@tools.ietf.org>>
Subject: RE: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Com=
ponent Link Utilization in Networks"

Hi Mukhtiar,

Thanks for your comments. Please find answers inline.
>>I think section 4.3.4. Automatic Hardware Recognition is a little vague. =
It is not clear how and what is expected from the hardware to detect the la=
rge flows. Is it sampling of packet forwarding counters in hardware or some=
thing else? Any clarity on this will be good.
Since the details are implementation specific, we are not planning on expan=
ding this section - IETF does not recommend specific implementations.

<MK> I was not suggesting to expand using implementation specific details..=
I was thinking of including some general examples such faster sampling capa=
bility in hardware, hardware packet counters etc

>> Also, from operational considerations point of view, as indicated in sec=
tion 6, frequent rebalancing of flows could be counter productive leading t=
o out of order packets and /or system instability. Similar challenges could=
 arise from immediate rebalancing of flows on one or more component links i=
n the LAG experiencing frequent failures. System may implement a throttling=
 mechanism to regulate when and what types of flows are re-distributed to p=
otentially flaky links to avoid instability.
Flaky links should be detected by the system and removed from the LAG right=
 ? I am not sure if there is anything specific we need to for large flow LA=
G load balancing.

<MK>The problem is not necessarily when a link is removed from the LAG upon=
 failure..but when it comes back up. Again, the assumption here is that lin=
k has been experiencing repeated failures and every time it comes back up, =
flows need to be readjusted. Therefore, if there is a history of failures o=
n a given link in the LAG, rebalancing could be done in a more conservative=
 way to minimize instability.

Regards,
-Mukhtiar

Thanks,
Ramki

From: opsawg-bounces@ietf.org<mailto:opsawg-bounces@ietf.org> [mailto:opsaw=
g-bounces@ietf.org] On Behalf Of Mukhtiar Shaikh
Sent: Monday, September 09, 2013 10:54 PM
To: opsawg@ietf.org<mailto:opsawg@ietf.org>
Cc: opsawg-chairs@tools.ietf.org<mailto:opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Com=
ponent Link Utilization in Networks"

I support the publication of this document as informational RFC. Have a cou=
ple of additional comments.

I think section 4.3.4. Automatic Hardware Recognition is a little vague. It=
 is not clear how and what is expected from the hardware to detect the larg=
e flows. Is it sampling of packet forwarding counters in hardware or someth=
ing else? Any clarity on this will be good.

Also, from operational considerations point of view, as indicated in sectio=
n 6, frequent rebalancing of flows could be counter productive leading to o=
ut of order packets and /or system instability. Similar challenges could ar=
ise from immediate rebalancing of flows on one or more component links in t=
he LAG experiencing frequent failures. System may implement a throttling me=
chanism to regulate when and what types of flows are re-distributed to pote=
ntially flaky links to avoid instability.

Thanks,
-Mukhtiar




-----Original Message-----
From: opsawg-bounces@ietf.org<mailto:opsawg-bounces@ietf.org> [mailto:opsaw=
g-bounces@ietf.org] On Behalf Of Melinda Shore
Sent: Saturday, August 24, 2013 1:07 PM
To: opsawg@ietf.org<mailto:opsawg@ietf.org>
Cc: opsawg-chairs@tools.ietf.org<mailto:opsawg-chairs@tools.ietf.org>
Subject: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Compone=
nt Link Utilization in Networks"



This is to announce the start of working group last call on:



    Mechanisms for Optimal LAG/ECMP Component Link Utilization in

        Networks



http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-balancing=
/



It is intended for publication as an informational RFC.



Please give it a careful read and provide any feedback to this mailing list=
 by September 9, 2013



Thanks,



opsawg chairs

_______________________________________________

OPSAWG mailing list

OPSAWG@ietf.org<mailto:OPSAWG@ietf.org>

https://www.ietf.org/mailman/listinfo/opsawg

--_000_C7634EB63EFD984A978DFB46EA5174F2BFFE959191HQ1EXCH01corp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple style=3D'word-wrap: break-wor=
d;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Thanks Mukhtiar, more in=
line.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'>&lt;MK&gt=
;The
problem is not necessarily when a link is removed from the LAG upon
failure..but when it comes back up. Again, the assumption here is that link=
 has
been experiencing repeated failures and every time it comes back up, flows =
need
to be readjusted. Therefore, if there is a history of failures on a given l=
ink
in the LAG, rebalancing could be done in a more conservative way to minimiz=
e instability.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Good point. What you are
bringing up would be applicable for normal LAG also &#8211; we could potent=
ially
reduce the weight of the LAG member ports connected to flaky links. <o:p></=
o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Thanks,<o:p></o:p></span=
></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Ramki<o:p></o:p></span><=
/p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Mukhtiar Shai=
kh <br>
<b>Sent:</b> Tuesday, September 10, 2013 11:46 PM<br>
<b>To:</b> ramki Krishnan; opsawg@ietf.org<br>
<b>Cc:</b> opsawg-chairs@tools.ietf.org<br>
<b>Subject:</b> Re: [OPSAWG] WG last call for &quot;Mechanisms for Optimal
LAG/ECMP Component Link Utilization in Networks&quot;<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'>Thanks Ra=
mki.
Please see comments inline:<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'><o:p>&nbs=
p;</o:p></span></p>

</div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'color:black'>From: </span></b><span
style=3D'color:black'>ramki Krishnan &lt;<a href=3D"mailto:ramk@Brocade.com=
">ramk@Brocade.com</a>&gt;<br>
<b>Date: </b>Tuesday, September 10, 2013 2:04 PM<br>
<b>To: </b>Mukhtiar Shaikh &lt;<a href=3D"mailto:mshaikh@brocade.com">mshai=
kh@brocade.com</a>&gt;,
&quot;<a href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</a>&quot; &lt;<a
href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</a>&gt;<br>
<b>Cc: </b>&quot;<a href=3D"mailto:opsawg-chairs@tools.ietf.org">opsawg-cha=
irs@tools.ietf.org</a>&quot;
&lt;<a href=3D"mailto:opsawg-chairs@tools.ietf.org">opsawg-chairs@tools.iet=
f.org</a>&gt;<br>
<b>Subject: </b>RE: [OPSAWG] WG last call for &quot;Mechanisms for Optimal
LAG/ECMP Component Link Utilization in Networks&quot;<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'><o:p>&nbs=
p;</o:p></span></p>

</div>

<div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>Hi Mukhtiar,<o:p></o:p></s=
pan></p>

<p class=3DMsoNormal><span style=3D'color:black'>&nbsp;<o:p></o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'color:black'>Thanks for your comments. =
Please
find answers inline.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>&gt;&gt;I think section 4.3.4. Automatic Hardware
Recognition is a little vague. It is not clear how and what is expected fro=
m
the hardware to detect the large flows. Is it sampling of packet forwarding
counters in hardware or&nbsp;something&nbsp;else? Any clarity on this will =
be
good.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>Since the details are implementation specific, we are=
 not
planning on expanding this section &#8211; IETF does not recommend specific
implementations.<o:p></o:p></span></p>

</div>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'><o:p>&nbs=
p;</o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'>&lt;MK&gt=
; I was
not suggesting to expand using implementation specific details..I was think=
ing
of including some general examples such faster sampling capability in hardw=
are,
hardware packet counters etc<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'><o:p>&nbs=
p;</o:p></span></p>

</div>

<div>

<div>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>&gt;&gt; Also, from operational considerations point =
of
view, as indicated in section 6, frequent rebalancing of flows could be cou=
nter
productive leading to out of order packets and /or system instability. Simi=
lar
challenges could arise from immediate rebalancing of flows on one or more c=
omponent
links in the LAG experiencing frequent failures. System may implement a
throttling mechanism to regulate when and what types of flows are
re-distributed to potentially flaky links to avoid instability.<o:p></o:p><=
/span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>Flaky links should be detected by the system and remo=
ved
from the LAG right ? I am not sure if there is anything specific we need to=
 for
large flow LAG load balancing.<o:p></o:p></span></p>

</div>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'><o:p>&nbs=
p;</o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'>&lt;MK&gt=
;The
problem is not necessarily when a link is removed from the LAG upon
failure..but when it comes back up. Again, the assumption here is that link=
 has
been experiencing repeated failures and every time it comes back up, flows =
need
to be readjusted. Therefore, if there is a history of failures on a given l=
ink
in the LAG, rebalancing could be done in a more conservative way to minimiz=
e instability.<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'><o:p>&nbs=
p;</o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'>Regards,<=
o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'>-Mukhtiar=
<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'><o:p>&nbs=
p;</o:p></span></p>

</div>

<div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>Thanks,<o:p></o:p></span><=
/p>

<p class=3DMsoNormal><span style=3D'color:black'>Ramki<o:p></o:p></span></p=
>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>&nbsp;</span><span
style=3D'color:black'><o:p></o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif";
color:black'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"T=
ahoma","sans-serif";
color:black'> <a href=3D"mailto:opsawg-bounces@ietf.org">opsawg-bounces@iet=
f.org</a>
[<a href=3D"mailto:opsawg-bounces@ietf.org">mailto:opsawg-bounces@ietf.org<=
/a>] <b>On
Behalf Of </b>Mukhtiar Shaikh<br>
<b>Sent:</b> Monday, September 09, 2013 10:54 PM<br>
<b>To:</b> <a href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:opsawg-chairs@tools.ietf.org">opsawg-chairs@to=
ols.ietf.org</a><br>
<b>Subject:</b> Re: [OPSAWG] WG last call for &quot;Mechanisms for Optimal
LAG/ECMP Component Link Utilization in Networks&quot;</span><span
style=3D'color:black'><o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><span style=3D'color:black'>&nbsp;<o:p></o:p></span></=
p>

<div>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>I support the publication of this document as informa=
tional
RFC. Have a couple of additional comments.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>I think section 4.3.4. Automatic Hardware Recognition=
 is a
little vague. It is not clear how and what is expected from the hardware to
detect the large flows. Is it sampling of packet forwarding counters in
hardware or&nbsp;something&nbsp;else? Any clarity on this will be good.<o:p=
></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>Also, from operational considerations point of view, =
as
indicated in section 6, frequent rebalancing of flows could be counter
productive leading to out of order packets and /or system instability. Simi=
lar
challenges could arise from immediate rebalancing of flows on one or more
component links in the LAG experiencing frequent failures. System may imple=
ment
a throttling mechanism to regulate when and what types of flows are
re-distributed to potentially flaky links to avoid instability.<o:p></o:p><=
/span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>Thanks,<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'color:black'>-Mukhtiar<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'>&nbsp;</s=
pan><span
style=3D'color:black'><o:p></o:p></span></p>

</div>

<div>

<div>

<div>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
</span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>-----O=
riginal
Message-----<br>
From: <a href=3D"mailto:opsawg-bounces@ietf.org">opsawg-bounces@ietf.org</a=
> [<a
href=3D"mailto:opsawg-bounces@ietf.org">mailto:opsawg-bounces@ietf.org</a>]=
 On
Behalf Of Melinda Shore<br>
Sent: Saturday, August 24, 2013 1:07 PM<br>
To: <a href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</a><br>
Cc: <a href=3D"mailto:opsawg-chairs@tools.ietf.org">opsawg-chairs@tools.iet=
f.org</a><br>
Subject: [OPSAWG] WG last call for &quot;Mechanisms for Optimal LAG/ECMP
Component Link Utilization in Networks&quot;</span><span style=3D'color:bla=
ck'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
</span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>This i=
s to
announce the start of working group last call on:</span><span style=3D'colo=
r:
black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
</span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
&nbsp;&nbsp;
Mechanisms for Optimal LAG/ECMP Component Link Utilization in</span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Networks</span><span style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
</span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'><a
href=3D"http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-b=
alancing/"><span
style=3D'color:windowtext;text-decoration:none'>http://datatracker.ietf.org=
/doc/draft-ietf-opsawg-large-flow-load-balancing/</span></a></span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
</span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>It is =
intended
for publication as an informational RFC.</span><span style=3D'color:black'>=
<o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
</span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>Please=
 give it
a careful read and provide any feedback to this mailing list by September 9=
,
2013</span><span style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
</span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>Thanks=
,</span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>&nbsp;=
</span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>opsawg=
 chairs</span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>______=
_________________________________________</span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'>OPSAWG=
 mailing
list</span><span style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'><a
href=3D"mailto:OPSAWG@ietf.org"><span style=3D'color:windowtext;text-decora=
tion:
none'>OPSAWG@ietf.org</span></a></span><span style=3D'color:black'><o:p></o=
:p></span></p>

<p class=3DMsoPlainText><span style=3D'font-size:10.5pt;color:black'><a
href=3D"https://www.ietf.org/mailman/listinfo/opsawg"><span style=3D'color:=
windowtext;
text-decoration:none'>https://www.ietf.org/mailman/listinfo/opsawg</span></=
a></span><span
style=3D'color:black'><o:p></o:p></span></p>

</div>

</div>

</div>

</div>

</div>

</div>

</body>

</html>

--_000_C7634EB63EFD984A978DFB46EA5174F2BFFE959191HQ1EXCH01corp_--

From tom.taylor.stds@gmail.com  Fri Sep 13 06:32:43 2013
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CA3D11E81A6 for <opsawg@ietfa.amsl.com>; Fri, 13 Sep 2013 06:32:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 0jWfUjJO8B0W for <opsawg@ietfa.amsl.com>; Fri, 13 Sep 2013 06:32:42 -0700 (PDT)
Received: from mail-vb0-x230.google.com (mail-vb0-x230.google.com [IPv6:2607:f8b0:400c:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 98B9111E818E for <opsawg@ietf.org>; Fri, 13 Sep 2013 06:32:42 -0700 (PDT)
Received: by mail-vb0-f48.google.com with SMTP id w16so901605vbf.21 for <opsawg@ietf.org>; Fri, 13 Sep 2013 06:32:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=NC+laMgfjPqRj/fiQ/vLmiThrfzVFvJp+W9CdjJdkOg=; b=vTVDrnbVIFOqnlqrqsdav4lwMsgc3hubYCb3kmE/M1aA+A2KX6YywU+zhhy93i4k2T vHCsxWOX0zIQv2ttAs70Xkk8osuK1MKLVyD9QqTF9YfQ8JWlFVZgemnhGhfbAd3pCjlB A8SEJm2zYwu+KCzwFVhrNXpN/mtUkmCIxmyj98TrLHMnHwiwdx2/fx5l70weXeuz0M/1 lVvbdVhB7+/IsKg88kcO0HLPJlhb2FgYx3qMc07svy3bpyv0z1PW2RupYMycpDTiNU3V hZzMdeMwLG7ps8QzanLYg1z4qeS0DWdD0Ec6qqDmhH9NteEDqK/fTNPazrrRI20Ovgle bIMQ==
X-Received: by 10.221.64.17 with SMTP id xg17mr12009901vcb.5.1379079159982; Fri, 13 Sep 2013 06:32:39 -0700 (PDT)
Received: from [192.168.1.73] (dsl-173-206-171-98.tor.primus.ca. [173.206.171.98]) by mx.google.com with ESMTPSA id m6sm8292997vdi.8.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Sep 2013 06:32:39 -0700 (PDT)
Message-ID: <523313F5.2070800@gmail.com>
Date: Fri, 13 Sep 2013 09:32:37 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "opsawg@ietf.org" <opsawg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [OPSAWG] Choice of reporting for NAT events
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Sep 2013 13:32:43 -0000

We are currently working on logging of NAT events, and making this 
consistent with the NAT MIB (which is also being revised). Currently the 
NAT MIB has several notifications, indicating, in effect, resource 
utilizations reaching a configured threshold. We will definitely be 
adding these events to the logs (IPFIX and SYSLOG based). Do operators 
need a choice between logs and SNMP notifications, or can we get rid of 
the latter?

Tom Taylor

From zehn.cao@gmail.com  Sun Sep 15 19:21:05 2013
Return-Path: <zehn.cao@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DEC811E8192 for <opsawg@ietfa.amsl.com>; Sun, 15 Sep 2013 19:21:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.671
X-Spam-Level: 
X-Spam-Status: No, score=-1.671 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_20=-0.74, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xo8aUV6Q4QUL for <opsawg@ietfa.amsl.com>; Sun, 15 Sep 2013 19:21:05 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id A748611E818D for <opsawg@ietf.org>; Sun, 15 Sep 2013 19:21:04 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id ex4so2828446wid.2 for <opsawg@ietf.org>; Sun, 15 Sep 2013 19:21:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=RLNXLZYo+UEFhFXae14vf2yU8b3KDojZag2sY1OWLDw=; b=bIS2DydvddMNRLIuCcPsIFKP1wMYRAbe16eznCCdsRC2zkr9w+AGibDldNyIc0cQSO uj4ssp8+41hteo6U3uoF0KV9NMymdAtCM1D40gSmSJsCv8edK+5Hy3qoOxtG6MQNkG2Q tELspI7+cDwznmXtrkxW9YK+lobhFBPagD5tLhYAaISQOyj3wgSFOjLy3VJWfsb2q9jF k4Sav5uk8WVogG8zAV3ZB3EQdQesOTShArGB2ZeaZbMhTCq1VnsOxB03MtGWJEZPSv+Z GS2cedgBIeo+5xiAko3cbFswcQNWB3U/7wN/vve1h6EznOZ6p3TF46U5nRmVI21Q5Y+D 1+lA==
MIME-Version: 1.0
X-Received: by 10.180.184.107 with SMTP id et11mr11435899wic.60.1379298063786;  Sun, 15 Sep 2013 19:21:03 -0700 (PDT)
Received: by 10.216.214.131 with HTTP; Sun, 15 Sep 2013 19:21:03 -0700 (PDT)
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F247B2421@nkgeml501-mbs.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F247A21EA@nkgeml501-mbs.china.huawei.com> <CAProHATCVwfhjP6qXqCh+B65p_Eht=FexRtKeCKWXUL1hxvobQ@mail.gmail.com> <E33E01DFD5BEA24B9F3F18671078951F247B2421@nkgeml501-mbs.china.huawei.com>
Date: Sun, 15 Sep 2013 22:21:03 -0400
Message-ID: <CAProHATRWGccbLxUXXH7T=PfvzGt3VOGPXOuYxPv-ZFjK+QfrQ@mail.gmail.com>
From: "Cao,Zhen" <zehn.cao@gmail.com>
To: "Songhaibin (A)" <haibin.song@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] FW: New Version Notification for draft-song-opsawg-virtual-network-function-config-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2013 02:21:05 -0000

More comments inline below.

> Comments for section 3 about service configuration problems.
>
> some more problems from my understanding
> 1. service chain requirement could be submitted by the user to the
> Controller
>
> [Haibin] I agree! A user can directly establish a service chain or servic=
e chains. For the service graph, there can be two layers IMO, one is the st=
able virtual link layer, and the other is conditional/stable service forwar=
ding layer. I also noticed that there was a network service chain BOF at la=
st IETF meeting. But they are focusing on how to identify a service chain a=
nd how to do the forwarding in the service chain. But for the requirement h=
ere, we only want the user the send the description to the controller.
>

[cz] NSC may have further impacts on the configuration, for example,
some functions may be implemented by chaining existing 'atom
functions'. What's I am not sure right now the granularity of the vNF
configuration, a) user specifies the detailed function, e.g., fw, lb,
etc.. b) user specifies the high layer vNF objectives that need
chaining of several vNFs...


> 2. service elasticity requirements should be specified by the user
> [Haibin] I have some description of this use case in the last paragraph o=
f Section 1. Just like that the user tells the controller, "allocate resour=
ces on-demand for me". Do you have some good idea in-mind on what are the e=
lasticity requirements?

[cz] there should be some metrics for the "on-demand", because the vNF
resource could never be enough based on the available infrastructure.
For example, the vFW could be handling 100K transactions at most, sth
like this.

>
>    There are also resource requirements for the remote software
>    installation, which are complement to the software components
>    selection.  There is lack of a standard for a user to tell the
>    controller how much bandwidth, storage, CPU, memory are allocated to
>    a specific software in the provider's network (perhaps there is
>    existing standard for the virtual machine or host level resources),
>
> [cz] but the Openstack-Neutron have such APIs to specify the user's
> request , better to notice the difference here.
>
> [Haibin] VNF level and VM level are different. Because one VM might be ho=
lding multiple VNFs. That interface you mentioned is combined with a VM IMO=
 and are not easy to make a change. But here when the resource is combined =
with a VNF. It is much easier to change it. Any thoughts?

[cz] that's clarifies the difference, i think we should make it
clearer how the the configuration differ from the cloud OS interface.
Such description above should be stressed.

>
> =3D=3Dquote
> 4.  Scope for Standardization
> [cz] Envision a picture here. and what's the operator's role in the pictu=
re,
> i believe the operator-controller interface should also be specified ,
> maybe add a (3).
>
> [Haibin] IMO, operator owns the controller. OSS/BSS for the NFV service i=
s part of the controller. But the network administrator from the operator c=
an also act as a user to install and configure VNFs in the provider's (oper=
ator's) network for the customers or for himself. This is the picture in my=
 mind. Is it consistent with what you have in mind?

[cz] I believe the controller could be third party SP selling software
components for NFV, in this case, there should be the interface for
the operator to configure the controller in this architecture.

From wesley.george@twcable.com  Mon Sep 16 06:29:06 2013
Return-Path: <wesley.george@twcable.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA18A11E823E for <opsawg@ietfa.amsl.com>; Mon, 16 Sep 2013 06:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.786
X-Spam-Level: 
X-Spam-Status: No, score=0.786 tagged_above=-999 required=5 tests=[AWL=-1.165,  BAYES_40=-0.185, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 M2mIIzUAHoOE for <opsawg@ietfa.amsl.com>; Mon, 16 Sep 2013 06:29:01 -0700 (PDT)
Received: from cdcipgw01.twcable.com (cdcipgw01.twcable.com [165.237.91.110]) by ietfa.amsl.com (Postfix) with ESMTP id AA8AF11E8120 for <opsawg@ietf.org>; Mon, 16 Sep 2013 06:29:01 -0700 (PDT)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.90,915,1371096000"; d="scan'208";a="45092061"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdcipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 16 Sep 2013 09:29:01 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Mon, 16 Sep 2013 09:29:00 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Date: Mon, 16 Sep 2013 09:28:59 -0400
Thread-Topic: [OPSAWG] Choice of reporting for NAT events
Thread-Index: Ac6whdmAMpLtW+IaSDmb5BYTmoyhJgCWpIdQ
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD5923043A72EC72@PRVPEXVS15.corp.twcable.com>
References: <523313F5.2070800@gmail.com>
In-Reply-To: <523313F5.2070800@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OPSAWG] Choice of reporting for NAT events
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2013 13:29:06 -0000

>
> We are currently working on logging of NAT events, and making this
> consistent with the NAT MIB (which is also being revised). Currently the
> NAT MIB has several notifications, indicating, in effect, resource
> utilizations reaching a configured threshold. We will definitely be
> adding these events to the logs (IPFIX and SYSLOG based). Do operators
> need a choice between logs and SNMP notifications, or can we get rid of
> the latter?
>
[WEG] Yes, I believe they need to stay in SNMP as well. While it is possibl=
e to trigger alarms in a monitoring system via watching logs for a certain =
condition/text string, it's vastly easier to make it something you can mana=
ge via either a trap or polling a value and evaluating the result.

Thanks
Wes George


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From simon.perreault@viagenie.ca  Mon Sep 16 06:33:41 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5C0F11E824B for <opsawg@ietfa.amsl.com>; Mon, 16 Sep 2013 06:33:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057,  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 o1JZptUIJOCv for <opsawg@ietfa.amsl.com>; Mon, 16 Sep 2013 06:33:40 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 243CF11E8248 for <opsawg@ietf.org>; Mon, 16 Sep 2013 06:33:40 -0700 (PDT)
Received: from [127.0.0.1] (h196.viagenie.ca [206.123.31.196]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 35D8B403C5; Mon, 16 Sep 2013 09:33:39 -0400 (EDT)
Message-ID: <523708B2.4080609@viagenie.ca>
Date: Mon, 16 Sep 2013 15:33:38 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "George, Wes" <wesley.george@twcable.com>
References: <523313F5.2070800@gmail.com> <2671C6CDFBB59E47B64C10B3E0BD5923043A72EC72@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923043A72EC72@PRVPEXVS15.corp.twcable.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] Choice of reporting for NAT events
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2013 13:33:42 -0000

Le 2013-09-16 15:28, George, Wes a écrit :
>>
>> We are currently working on logging of NAT events, and making this
>> consistent with the NAT MIB (which is also being revised). Currently the
>> NAT MIB has several notifications, indicating, in effect, resource
>> utilizations reaching a configured threshold. We will definitely be
>> adding these events to the logs (IPFIX and SYSLOG based). Do operators
>> need a choice between logs and SNMP notifications, or can we get rid of
>> the latter?
>>
> [WEG] Yes, I believe they need to stay in SNMP as well. While it is possible to trigger alarms in a monitoring system via watching logs for a certain condition/text string, it's vastly easier to make it something you can manage via either a trap or polling a value and evaluating the result.

If they stay in SNMP, do they also need to stay in IPFIX/SYSLOG?

Simon

From Jean-Francois.TremblayING@videotron.com  Mon Sep 16 06:38:30 2013
Return-Path: <Jean-Francois.TremblayING@videotron.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE2B911E824B for <opsawg@ietfa.amsl.com>; Mon, 16 Sep 2013 06:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 zyLnaXKRdkKY for <opsawg@ietfa.amsl.com>; Mon, 16 Sep 2013 06:38:22 -0700 (PDT)
Received: from mx01.videotron.com (mx01.videotron.com [24.201.243.152]) by ietfa.amsl.com (Postfix) with ESMTP id 4756111E823E for <opsawg@ietf.org>; Mon, 16 Sep 2013 06:38:22 -0700 (PDT)
In-Reply-To: <523708B2.4080609@viagenie.ca>
References: <523313F5.2070800@gmail.com>	<2671C6CDFBB59E47B64C10B3E0BD5923043A72EC72@PRVPEXVS15.corp.twcable.com> <523708B2.4080609@viagenie.ca>
To: "opsawg@ietf.org" <opsawg@ietf.org>
MIME-Version: 1.0
X-KeepSent: 47F72D4A:AB436F10-85257BE8:004A9B87; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.3FP1 March 08, 2012
Message-ID: <OF47F72D4A.AB436F10-ON85257BE8.004A9B87-85257BE8.004AEBBA@videotron.com>
From: Jean-Francois.TremblayING@videotron.com
Date: Mon, 16 Sep 2013 09:38:19 -0400
X-MIMETrack: Serialize by Router on DOMMSG01/SRV/GVL(Release 8.5.3FP3|November 15, 2012) at 09/16/2013 09:38:20, Serialize complete at 09/16/2013 09:38:20
Content-Type: text/plain; charset="US-ASCII"
Received-SPF: none
Subject: Re: [OPSAWG] Choice of reporting for NAT events
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2013 13:38:30 -0000

> >> We are currently working on logging of NAT events, and making this
> >> consistent with the NAT MIB (which is also being revised). Currently 
the
> >> NAT MIB has several notifications, indicating, in effect, resource
> >> utilizations reaching a configured threshold. We will definitely be
> >> adding these events to the logs (IPFIX and SYSLOG based). Do 
operators
> >> need a choice between logs and SNMP notifications, or can we get rid 
of
> >> the latter?
> >>
> > [WEG] Yes, I believe they need to stay in SNMP as well. While it 
> is possible to trigger alarms in a monitoring system via watching 
> logs for a certain condition/text string, it's vastly easier to make
> it something you can manage via either a trap or polling a value and
> evaluating the result.
> 
> If they stay in SNMP, do they also need to stay in IPFIX/SYSLOG?

IMO, both should be kept. 

1 - It provides implementation flexibility
2 - Both might actually be needed at the same time (for different 
operational groups with different needs, procedures and systems)

/JF


From wesley.george@twcable.com  Mon Sep 16 14:03:27 2013
Return-Path: <wesley.george@twcable.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B942311E821E for <opsawg@ietfa.amsl.com>; Mon, 16 Sep 2013 14:03:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.242
X-Spam-Level: 
X-Spam-Status: No, score=-0.242 tagged_above=-999 required=5 tests=[AWL=0.222,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 HlRJpnZgrpuu for <opsawg@ietfa.amsl.com>; Mon, 16 Sep 2013 14:03:19 -0700 (PDT)
Received: from cdcipgw02.twcable.com (cdcipgw02.twcable.com [165.237.91.111]) by ietfa.amsl.com (Postfix) with ESMTP id 5589A11E81BD for <opsawg@ietf.org>; Mon, 16 Sep 2013 14:02:00 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.90,918,1371096000"; d="scan'208";a="38426532"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdcipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 16 Sep 2013 17:01:56 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Mon, 16 Sep 2013 17:01:55 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: Melinda Shore <melinda.shore@gmail.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Date: Mon, 16 Sep 2013 17:01:54 -0400
Thread-Topic: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
Thread-Index: Ac6hBYkTvOHfyrGyQTOGjmvrFi+FzASGY3+g
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD5923043A84B63A@PRVPEXVS15.corp.twcable.com>
References: <52191268.5070500@gmail.com>
In-Reply-To: <52191268.5070500@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "opsawg-chairs@tools.ietf.org" <opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2013 21:03:27 -0000

My apologies for missing the deadline on this, but I got my wires crossed a=
nd reviewed this doc in response to something I saw on IETF LC (which was a=
ctually on a different draft), so I figured the least I can do is provide m=
y feedback on the *right* draft/thread/list, and then swear off email and g=
o home for the day before I can do any more damage... sigh.
--------
one substantive comment:

I think within the operational considerations (and possibly the info model)=
, you need some discussion of diagnostics and troubleshooting, both for on-=
box and off-box implementations. How do I see that it's working properly, a=
nd how do I diagnose problems when it's not?
One of the problems with the existing hashing algorithms is that they are o=
ften opaque, such that it's not clear what the device is doing, whether the=
 hashing is working properly and the flows are of the sort that create imba=
lanced distribution, or whether hashing has broken somehow -- occasionally =
you can get info, but it's usually hidden commands, with difficult-to-inter=
pret responses, and it's not like most vendors publish their "secret sauce"=
 optimizations of hashing so that it's easy to predict what will happen giv=
en a certain set of flows.
In order for this to be operationally manageable, especially in the case of=
 on-router processing of this rebalancing, there has to be an easy way for =
the operator to access the information about what's happening - what the re=
sult would be if the flows were balanced according to the hash vs what is h=
appening as a result of rebalancing, so that they can chase down things lik=
e rebalancing misses or situations where this local optimization is creatin=
g a problem elsewhere in the path because that device did something differe=
nt in its attempts to balance better, etc. It may also be that this info is=
 necessary to properly tune the frequency of sampling, the thresholds for t=
hings like long-lived vs short-lived flows, etc. to the specific network wh=
ere it is being used.
I realize that in the model you've proposed, we're somewhat limited because=
 this is using sampled flow data instead of the realtime packet hash. It ma=
y be that this drives a requirement for the granularity of data being broug=
ht into the system in the external mode, and some requirements about the le=
vel of information available via the UI (or SNMP or XML or whatever) in the=
 automatic hardware-based mode.

Thanks
Wes George


> -----Original Message-----
> From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf
> Of Melinda Shore
> Sent: Saturday, August 24, 2013 4:07 PM
> To: opsawg@ietf.org
> Cc: opsawg-chairs@tools.ietf.org
> Subject: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP
> Component Link Utilization in Networks"
>
> This is to announce the start of working group last call on:
>
>     Mechanisms for Optimal LAG/ECMP Component Link Utilization in
>         Networks
>
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-
> balancing/
>
> It is intended for publication as an informational RFC.
>
> Please give it a careful read and provide any feedback to this
> mailing list by September 9, 2013
>
> Thanks,
>
> opsawg chairs
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From ramk@Brocade.com  Tue Sep 17 18:47:39 2013
Return-Path: <ramk@Brocade.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FB3011E8497 for <opsawg@ietfa.amsl.com>; Tue, 17 Sep 2013 18:47:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.265
X-Spam-Level: 
X-Spam-Status: No, score=-3.265 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1]
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 mWir4CemBFWo for <opsawg@ietfa.amsl.com>; Tue, 17 Sep 2013 18:47:34 -0700 (PDT)
Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) by ietfa.amsl.com (Postfix) with ESMTP id EC63411E81D5 for <opsawg@ietf.org>; Tue, 17 Sep 2013 18:47:32 -0700 (PDT)
Received: from pps.filterd (m0000700 [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.14.5/8.14.5) with SMTP id r8I19KV4007909; Tue, 17 Sep 2013 18:47:31 -0700
Received: from hq1wp-exchub02.corp.brocade.com ([144.49.131.13]) by mx0b-000f0801.pphosted.com with ESMTP id 1ey06d03b8-3 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 17 Sep 2013 18:47:31 -0700
Received: from HQ1WP-EXHUB01.corp.brocade.com (10.70.36.14) by hq1wp-exchub02.corp.brocade.com (10.70.38.99) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 17 Sep 2013 18:47:31 -0700
Received: from HQ1-EXCH01.corp.brocade.com ([fe80::ed42:173e:fe7d:d0a6]) by HQ1WP-EXHUB01.corp.brocade.com ([::1]) with mapi; Tue, 17 Sep 2013 18:47:28 -0700
From: ramki Krishnan <ramk@Brocade.com>
To: "George, Wes" <wesley.george@twcable.com>, Melinda Shore <melinda.shore@gmail.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Date: Tue, 17 Sep 2013 18:47:24 -0700
Thread-Topic: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
Thread-Index: Ac6hBYkTvOHfyrGyQTOGjmvrFi+FzASGY3+gADxrTvA=
Message-ID: <C7634EB63EFD984A978DFB46EA5174F2BFFE959BB1@HQ1-EXCH01.corp.brocade.com>
References: <52191268.5070500@gmail.com> <2671C6CDFBB59E47B64C10B3E0BD5923043A84B63A@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923043A84B63A@PRVPEXVS15.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-09-17_08:2013-09-18, 2013-09-17, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1309170141
Cc: "opsawg-chairs@tools.ietf.org" <opsawg-chairs@tools.ietf.org>
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2013 01:47:39 -0000

Hi Wes,

Thanks for your comments. Please find responses below.

>> In order for this to be operationally manageable, especially in the case=
 of on-router processing of this rebalancing, there has to be an easy way f=
or the operator to access the information about what's happening - what the=
 result would be if the flows were balanced according to the hash vs what i=
s happening as a result of rebalancing, so that they can chase down things =
like rebalancing misses or situations where this local optimization is crea=
ting a problem elsewhere in the path because that device did something diff=
erent in its attempts to balance better, etc. It may also be that this info=
 is necessary to properly tune the frequency of sampling, the thresholds fo=
r things like long-lived vs short-lived flows, etc. to the specific network=
 where it is being used.=20
=20
For determining component link imbalance, we are using interface counters. =
 For tracking the effectiveness of the scheme, we also have other monitorin=
g information such as 1) Number of times rebalancing was done and 2) Time s=
ince the last rebalancing event. Is there something else that you think wou=
ld be helpful?
=20
>> I realize that in the model you've proposed, we're somewhat limited beca=
use this is using sampled flow data instead of the realtime packet hash. It=
 may be that this drives a requirement for the granularity of data being br=
ought into the system in the external mode, and some requirements about the=
 level of information available via the UI (or SNMP or XML or whatever) in =
the automatic hardware-based mode.
=20
For large flow detection, we propose two modes 1) Sampling Techniques 2) Au=
tomatic Hardware Recognition. The primary difference between the two modes =
in terms of performance is the time taken to recognize the long-lived large=
 flows; there is no loss of accuracy in either mode. In the automatic hardw=
are based mode for detecting the large flows, it is best that the load bala=
ncing happen in the router. Are you looking for anything else ?

Thanks,
Ramki

-----Original Message-----
From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of=
 George, Wes
Sent: Monday, September 16, 2013 2:02 PM
To: Melinda Shore; opsawg@ietf.org
Cc: opsawg-chairs@tools.ietf.org
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Com=
ponent Link Utilization in Networks"

My apologies for missing the deadline on this, but I got my wires crossed a=
nd reviewed this doc in response to something I saw on IETF LC (which was a=
ctually on a different draft), so I figured the least I can do is provide m=
y feedback on the *right* draft/thread/list, and then swear off email and g=
o home for the day before I can do any more damage... sigh.
--------
one substantive comment:

I think within the operational considerations (and possibly the info model)=
, you need some discussion of diagnostics and troubleshooting, both for on-=
box and off-box implementations. How do I see that it's working properly, a=
nd how do I diagnose problems when it's not?
One of the problems with the existing hashing algorithms is that they are o=
ften opaque, such that it's not clear what the device is doing, whether the=
 hashing is working properly and the flows are of the sort that create imba=
lanced distribution, or whether hashing has broken somehow -- occasionally =
you can get info, but it's usually hidden commands, with difficult-to-inter=
pret responses, and it's not like most vendors publish their "secret sauce"=
 optimizations of hashing so that it's easy to predict what will happen giv=
en a certain set of flows.
In order for this to be operationally manageable, especially in the case of=
 on-router processing of this rebalancing, there has to be an easy way for =
the operator to access the information about what's happening - what the re=
sult would be if the flows were balanced according to the hash vs what is h=
appening as a result of rebalancing, so that they can chase down things lik=
e rebalancing misses or situations where this local optimization is creatin=
g a problem elsewhere in the path because that device did something differe=
nt in its attempts to balance better, etc. It may also be that this info is=
 necessary to properly tune the frequency of sampling, the thresholds for t=
hings like long-lived vs short-lived flows, etc. to the specific network wh=
ere it is being used.
I realize that in the model you've proposed, we're somewhat limited because=
 this is using sampled flow data instead of the realtime packet hash. It ma=
y be that this drives a requirement for the granularity of data being broug=
ht into the system in the external mode, and some requirements about the le=
vel of information available via the UI (or SNMP or XML or whatever) in the=
 automatic hardware-based mode.

Thanks
Wes George


> -----Original Message-----
> From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf
> Of Melinda Shore
> Sent: Saturday, August 24, 2013 4:07 PM
> To: opsawg@ietf.org
> Cc: opsawg-chairs@tools.ietf.org
> Subject: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP
> Component Link Utilization in Networks"
>
> This is to announce the start of working group last call on:
>
>     Mechanisms for Optimal LAG/ECMP Component Link Utilization in
>         Networks
>
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-
> balancing/
>
> It is intended for publication as an informational RFC.
>
> Please give it a careful read and provide any feedback to this
> mailing list by September 9, 2013
>
> Thanks,
>
> opsawg chairs
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

From haibin.song@huawei.com  Wed Sep 18 00:15:26 2013
Return-Path: <haibin.song@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADB7311E81B0 for <opsawg@ietfa.amsl.com>; Wed, 18 Sep 2013 00:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXdstzO8LsmU for <opsawg@ietfa.amsl.com>; Wed, 18 Sep 2013 00:15:21 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C9FFF11E81AF for <opsawg@ietf.org>; Wed, 18 Sep 2013 00:15:20 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AXY72161; Wed, 18 Sep 2013 07:15:19 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 18 Sep 2013 08:14:51 +0100
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 18 Sep 2013 08:15:18 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.141]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0146.000; Wed, 18 Sep 2013 15:15:13 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: "Cao,Zhen" <zehn.cao@gmail.com>
Thread-Topic: [OPSAWG] FW: New Version Notification for draft-song-opsawg-virtual-network-function-config-00.txt
Thread-Index: AQHOrjSIYcKUT/d37E2SucSXokpvXpm/wwYwgAdhPICAA/dtsA==
Date: Wed, 18 Sep 2013 07:15:12 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F247B6AC6@nkgeml501-mbs.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F247A21EA@nkgeml501-mbs.china.huawei.com> <CAProHATCVwfhjP6qXqCh+B65p_Eht=FexRtKeCKWXUL1hxvobQ@mail.gmail.com> <E33E01DFD5BEA24B9F3F18671078951F247B2421@nkgeml501-mbs.china.huawei.com> <CAProHATRWGccbLxUXXH7T=PfvzGt3VOGPXOuYxPv-ZFjK+QfrQ@mail.gmail.com>
In-Reply-To: <CAProHATRWGccbLxUXXH7T=PfvzGt3VOGPXOuYxPv-ZFjK+QfrQ@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.66]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] FW: New Version Notification for draft-song-opsawg-virtual-network-function-config-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2013 07:15:27 -0000

Hi Cao Zhen,

See inline.

-----Original Message-----
From: Cao,Zhen [mailto:zehn.cao@gmail.com]=20
Sent: Monday, September 16, 2013 10:21 AM
To: Songhaibin (A)
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] FW: New Version Notification for draft-song-opsawg-vi=
rtual-network-function-config-00.txt

More comments inline below.

> Comments for section 3 about service configuration problems.
>
> some more problems from my understanding
> 1. service chain requirement could be submitted by the user to the
> Controller
>
> [Haibin] I agree! A user can directly establish a service chain or servic=
e chains. For the service graph, there can be two layers IMO, one is the st=
able virtual link layer, and the other is conditional/stable service forwar=
ding layer. I also noticed that there was a network service chain BOF at la=
st IETF meeting. But they are focusing on how to identify a service chain a=
nd how to do the forwarding in the service chain. But for the requirement h=
ere, we only want the user the send the description to the controller.
>
[cz] NSC may have further impacts on the configuration, for example,
some functions may be implemented by chaining existing 'atom
functions'. What's I am not sure right now the granularity of the vNF
configuration, a) user specifies the detailed function, e.g., fw, lb,
etc.. b) user specifies the high layer vNF objectives that need
chaining of several vNFs...

[Haibin] I think both a) and b) should be supported. Different users have d=
ifferent expertise level. And it is also service related. Different VNF pro=
viders may have their own policy about whether to allow the users to specif=
ies what you mentioned "atom functions" and to what level. But this is a go=
od point that should be reflected when the document is updated.


> 2. service elasticity requirements should be specified by the user
> [Haibin] I have some description of this use case in the last paragraph o=
f Section 1. Just like that the user tells the controller, "allocate resour=
ces on-demand for me". Do you have some good idea in-mind on what are the e=
lasticity requirements?

[cz] there should be some metrics for the "on-demand", because the vNF
resource could never be enough based on the available infrastructure.
For example, the vFW could be handling 100K transactions at most, sth
like this.



>
>    There are also resource requirements for the remote software
>    installation, which are complement to the software components
>    selection.  There is lack of a standard for a user to tell the
>    controller how much bandwidth, storage, CPU, memory are allocated to
>    a specific software in the provider's network (perhaps there is
>    existing standard for the virtual machine or host level resources),
>
> [cz] but the Openstack-Neutron have such APIs to specify the user's
> request , better to notice the difference here.
>
> [Haibin] VNF level and VM level are different. Because one VM might be ho=
lding multiple VNFs. That interface you mentioned is combined with a VM IMO=
 and are not easy to make a change. But here when the resource is combined =
with a VNF. It is much easier to change it. Any thoughts?

[cz] that's clarifies the difference, i think we should make it
clearer how the the configuration differ from the cloud OS interface.
Such description above should be stressed.

[Haibin] OK.


> =3D=3Dquote
> 4.  Scope for Standardization
> [cz] Envision a picture here. and what's the operator's role in the pictu=
re,
> i believe the operator-controller interface should also be specified ,
> maybe add a (3).
>
> [Haibin] IMO, operator owns the controller. OSS/BSS for the NFV service i=
s part of the controller. But the network administrator from the operator c=
an also act as a user to install and configure VNFs in the provider's (oper=
ator's) network for the customers or for himself. This is the picture in my=
 mind. Is it consistent with what you have in mind?

[cz] I believe the controller could be third party SP selling software
components for NFV, in this case, there should be the interface for
the operator to configure the controller in this architecture.

[Haibin] I agree with your point, but I would assume that the controller ha=
s already be configured for the problem statement in this draft.

Thanks again,

-Haibin



From wesley.george@twcable.com  Wed Sep 18 07:43:08 2013
Return-Path: <wesley.george@twcable.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 394E711E8101 for <opsawg@ietfa.amsl.com>; Wed, 18 Sep 2013 07:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level: 
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[AWL=0.765,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
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 EYILQTKvJKvB for <opsawg@ietfa.amsl.com>; Wed, 18 Sep 2013 07:43:03 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 163F411E80EF for <opsawg@ietf.org>; Wed, 18 Sep 2013 07:43:02 -0700 (PDT)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.90,929,1371096000"; d="scan'208";a="137527635"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 18 Sep 2013 10:42:52 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Wed, 18 Sep 2013 10:43:01 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: ramki Krishnan <ramk@Brocade.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Date: Wed, 18 Sep 2013 10:43:00 -0400
Thread-Topic: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
Thread-Index: Ac6hBYkTvOHfyrGyQTOGjmvrFi+FzASGY3+gADxrTvAAGpwIYA==
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD5923043A8F51DF@PRVPEXVS15.corp.twcable.com>
References: <52191268.5070500@gmail.com> <2671C6CDFBB59E47B64C10B3E0BD5923043A84B63A@PRVPEXVS15.corp.twcable.com> <C7634EB63EFD984A978DFB46EA5174F2BFFE959BB1@HQ1-EXCH01.corp.brocade.com>
In-Reply-To: <C7634EB63EFD984A978DFB46EA5174F2BFFE959BB1@HQ1-EXCH01.corp.brocade.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2013 14:43:08 -0000

> From: ramki Krishnan [mailto:ramk@Brocade.com]
>
>
> For determining component link imbalance, we are using interface
> counters.  For tracking the effectiveness of the scheme, we also have
> other monitoring information such as 1) Number of times rebalancing was
> done and 2) Time since the last rebalancing event. Is there something
> else that you think would be helpful?
[WEG] yes. You need info about the number of flows being tracked on each in=
terface and their size, possibly also the category (long-lived vs short, la=
rge vs small) as well as which flows have been moved and when. You're alrea=
dy building all of this state to provide input to your algorithm, I'm just =
saying that you need to make it clear in the draft that operators may want =
to be able to see that data. Like I said, in order to evaluate this as actu=
ally being better than the existing hash, to tune the parameters, and to tr=
oubleshoot balancing problems, I need to be able to see what it's actually =
doing, not just the interface counters.

>
> >> I realize that in the model you've proposed, we're somewhat limited
> because this is using sampled flow data instead of the realtime packet
> hash. It may be that this drives a requirement for the granularity of
> data being brought into the system in the external mode, and some
> requirements about the level of information available via the UI (or
> SNMP or XML or whatever) in the automatic hardware-based mode.
>
> For large flow detection, we propose two modes 1) Sampling Techniques 2)
> Automatic Hardware Recognition. The primary difference between the two
> modes in terms of performance is the time taken to recognize the long-
> lived large flows; there is no loss of accuracy in either mode. In the
> automatic hardware based mode for detecting the large flows, it is best
> that the load balancing happen in the router. Are you looking for
> anything else ?
[WEG] Yes, I think maybe I was unclear. I'm looking for diagnostic tools to=
 make this less opaque for an operator. I was noting that it may be difficu=
lt to give specific, granular information by flow about the size of each fl=
ow and when/if it was moved by the loadbalancing algorithm if you were reli=
ant on sampled flow data, because it wouldn't be complete/granular enough -=
- it would only show a subset of the flows, not all flows.

Thanks
Wes


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From tom.taylor.stds@gmail.com  Thu Sep 19 04:01:16 2013
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D1FA21F99A2 for <opsawg@ietfa.amsl.com>; Thu, 19 Sep 2013 04:01:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.155
X-Spam-Level: 
X-Spam-Status: No, score=-3.155 tagged_above=-999 required=5 tests=[AWL=0.444,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Dtb-zVsCSpi0 for <opsawg@ietfa.amsl.com>; Thu, 19 Sep 2013 04:01:10 -0700 (PDT)
Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com [209.85.223.173]) by ietfa.amsl.com (Postfix) with ESMTP id 75E6C21F9193 for <opsawg@ietf.org>; Thu, 19 Sep 2013 04:01:08 -0700 (PDT)
Received: by mail-ie0-f173.google.com with SMTP id ar20so14821087iec.18 for <opsawg@ietf.org>; Thu, 19 Sep 2013 04:00:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=MblOIv0IrHgvTz+eHcRP2NkZVtcENDExaoHsIRNI0hE=; b=GpawFNXjQqRNgR52fVkUfMiH32WjOXwWkMzM6Wa5UrETHSGdz7Zfvqn7/PI8be9mUS 8u2lKftZcsklmhhhUneMqcTsHXUcsRgOXxj/aPFRFXvyiLGvLI2fBJCJtYo7kcRkLNCp 3d473F+w7WOKz9OUne7/VV00nUe7EZzsDE8sWP0GqliF76RCR9YjknbnEAJ60v0vmIvL w6HwpeWTmWhxSScDR2qQUuWO6I9y6NaUrGGWOyvTjydLKg+jSs9/icSTPx6PM8kLXugA 3lF7CM6LUFMd/IoE/DA1ijIZ8VuZ0g/ZFSBLen919kOsDOoXmScdTporBM06EKWc6a6S IlWA==
X-Received: by 10.42.146.1 with SMTP id h1mr565277icv.38.1379588453061; Thu, 19 Sep 2013 04:00:53 -0700 (PDT)
Received: from [192.168.1.73] (dsl-173-206-79-23.tor.primus.ca. [173.206.79.23]) by mx.google.com with ESMTPSA id ka5sm3079790igb.2.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Sep 2013 04:00:52 -0700 (PDT)
Message-ID: <523AD964.8060602@gmail.com>
Date: Thu, 19 Sep 2013 07:00:52 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "opsawg@ietf.org" <opsawg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [OPSAWG] SYSLOG architectural issue
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2013 11:01:16 -0000

In Behave, we are dealing with a potential logging architecture where 
Device A generates the content but exports it in the form of IPFIX 
records. Device B reformats the content into SYSLOG event reports.

Up to now I interpreted the first sentence of Section 6.2.4 to mean that 
the HOSTNAME field in the SYSLOG header had to identify Device B.

"The HOSTNAME field identifies the machine that originally sent the
    syslog message."

This meant that I had to define another field to identify Device A.

However, the very next paragraph says:

   "The HOSTNAME field SHOULD contain the hostname and the domain name of
    the originator in the format specified in STD 13 [RFC1034]."

So there are grounds for identifying Device A in the HOSTNAME field.

Any opinions one way or another? I'll go with Device A in the HOSTNAME 
field unless there are objections.

Tom Taylor

From j.schoenwaelder@jacobs-university.de  Thu Sep 19 05:07:34 2013
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC7C721F94FA for <opsawg@ietfa.amsl.com>; Thu, 19 Sep 2013 05:07:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.146
X-Spam-Level: 
X-Spam-Status: No, score=-103.146 tagged_above=-999 required=5 tests=[AWL=0.103, 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 ESAuyTEWnH9f for <opsawg@ietfa.amsl.com>; Thu, 19 Sep 2013 05:07:27 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id C74AC21F967F for <opsawg@ietf.org>; Thu, 19 Sep 2013 05:07:26 -0700 (PDT)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id D416D20C06; Thu, 19 Sep 2013 14:07:25 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id BrCAT84a8GPx; Thu, 19 Sep 2013 14:07:25 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 45C2820BF0; Thu, 19 Sep 2013 14:07:25 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 3E0C22872221; Thu, 19 Sep 2013 14:07:20 +0200 (CEST)
Date: Thu, 19 Sep 2013 14:07:19 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Tom Taylor <tom.taylor.stds@gmail.com>
Message-ID: <20130919120719.GA554@elstar.local>
Mail-Followup-To: Tom Taylor <tom.taylor.stds@gmail.com>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <523AD964.8060602@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <523AD964.8060602@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] SYSLOG architectural issue
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2013 12:07:34 -0000

On Thu, Sep 19, 2013 at 07:00:52AM -0400, Tom Taylor wrote:
> In Behave, we are dealing with a potential logging architecture
> where Device A generates the content but exports it in the form of
> IPFIX records. Device B reformats the content into SYSLOG event
> reports.
> 
> Up to now I interpreted the first sentence of Section 6.2.4 to mean
> that the HOSTNAME field in the SYSLOG header had to identify Device
> B.
> 
> "The HOSTNAME field identifies the machine that originally sent the
>    syslog message."
> 
> This meant that I had to define another field to identify Device A.
> 
> However, the very next paragraph says:
> 
>   "The HOSTNAME field SHOULD contain the hostname and the domain name of
>    the originator in the format specified in STD 13 [RFC1034]."
> 
> So there are grounds for identifying Device A in the HOSTNAME field.
> 
> Any opinions one way or another? I'll go with Device A in the
> HOSTNAME field unless there are objections.

I can't tell what is right or wrong here but back in a day when we did
RFC 5675, we decided to have the real originator of the notification
encoded in the structured data element. Of course, since RFC 5675
talks about SNMP notifications, we identify the source using an SNMP
context and not by a hostname. RFC 5675 actually says:

   The VERSION, TIMESTAMP, HOSTNAME, APP-NAME, PROCID, and MSGID fields
   in the SYSLOG message header are filled with values that are specific
   to the system on which the SNMP-to-SYSLOG translator is running.  The
   character set used in the HEADER MUST be seven-bit ASCII in an eight-
   bit field, as described in [RFC5424].

I think this implies that the HOSTNAME contains the name of the host
on which the translator is running, not the HOSTNAME of the SNMP agent
emitting the notification (which BTW may not be known in this case
since there can be SNMP proxies).

I would have to dig deeper into IPFIX to understand whether you can
always find out the hostname of the originator (since there might be
mediators involved as well) or whether there is another reliable way
to identify an IPFIX exporter.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From addogra@cisco.com  Thu Sep 19 05:25:16 2013
Return-Path: <addogra@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EC7C21F96E4 for <opsawg@ietfa.amsl.com>; Thu, 19 Sep 2013 05:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 CyaJeyYTsqGw for <opsawg@ietfa.amsl.com>; Thu, 19 Sep 2013 05:25:11 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 5FCA021F942D for <opsawg@ietf.org>; Thu, 19 Sep 2013 05:25:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3426; q=dns/txt; s=iport; t=1379593511; x=1380803111; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=uktmt1/c5AwDkeTU/jdR7fZfGg0mPY+H0zHtSmJpkVQ=; b=dJQDPNQwts4OpoQvmGfeHsdz52ZL12NjypE+OTpo+3gRg/2vX+knKdT0 n3JYFIj8Teg+Wv/+ddxCgITGodF3BlN1SHCyF2DlSAnXG+kONSVc8VERz Al2gYbXfMvPQwYQj2OrXwQR28vZgWqw2uGs+FnsQ/81TEMA6i2exnS+l+ 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAAPsOlKtJV2Z/2dsb2JhbABRBwODBzhSwGJKgSAWdIIlAQEBBAEBATc0CwwCAgIBCA4CAQEDAQEBChQJBxsMCxQDBggCBAENBQiHewy5TgSOIIESIRAHBguDDYEAA6lxgySCKg
X-IronPort-AV: E=Sophos;i="4.90,936,1371081600"; d="scan'208";a="261823357"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 19 Sep 2013 12:25:10 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r8JCPA8i022301 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 19 Sep 2013 12:25:10 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.253]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.02.0318.004; Thu, 19 Sep 2013 07:25:10 -0500
From: "Aditya Dogra (addogra)" <addogra@cisco.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Tom Taylor <tom.taylor.stds@gmail.com>
Thread-Topic: [OPSAWG] SYSLOG architectural issue
Thread-Index: AQHOtSeWXYnCJx8NRkKO7uhkTPlMF5nNSxaA//+uqvA=
Date: Thu, 19 Sep 2013 12:25:09 +0000
Message-ID: <94383E83699D0F4D9040CEFAE204B40709EA691F@xmb-aln-x11.cisco.com>
References: <523AD964.8060602@gmail.com> <20130919120719.GA554@elstar.local>
In-Reply-To: <20130919120719.GA554@elstar.local>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.142.104.112]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] SYSLOG architectural issue
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2013 12:25:16 -0000

On the Network operating systems also , the HOSTNAME is the hostname and th=
e domain name of  the originator and when we have a hop for this message, i=
t gets appended with the new hostname .

For eg in case we have few network devices connected (device A, device B ..=
 device X) and device X is configured as syslog relay. All devices A-W send=
 the messages to  Device X and then device X is connected with the remote s=
erver or SNMP server. In that case the message at the SNMP server will have=
 two Hostnames : Hostname X + Hostname A : Message or so on.=20


Regards,
Aditya Dogra (addogra)=20

-----Original Message-----
From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of=
 Juergen Schoenwaelder
Sent: Thursday, September 19, 2013 5:37 PM
To: Tom Taylor
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] SYSLOG architectural issue

On Thu, Sep 19, 2013 at 07:00:52AM -0400, Tom Taylor wrote:
> In Behave, we are dealing with a potential logging architecture where=20
> Device A generates the content but exports it in the form of IPFIX=20
> records. Device B reformats the content into SYSLOG event reports.
>=20
> Up to now I interpreted the first sentence of Section 6.2.4 to mean=20
> that the HOSTNAME field in the SYSLOG header had to identify Device B.
>=20
> "The HOSTNAME field identifies the machine that originally sent the
>    syslog message."
>=20
> This meant that I had to define another field to identify Device A.
>=20
> However, the very next paragraph says:
>=20
>   "The HOSTNAME field SHOULD contain the hostname and the domain name of
>    the originator in the format specified in STD 13 [RFC1034]."
>=20
> So there are grounds for identifying Device A in the HOSTNAME field.
>=20
> Any opinions one way or another? I'll go with Device A in the HOSTNAME=20
> field unless there are objections.

I can't tell what is right or wrong here but back in a day when we did RFC =
5675, we decided to have the real originator of the notification encoded in=
 the structured data element. Of course, since RFC 5675 talks about SNMP no=
tifications, we identify the source using an SNMP context and not by a host=
name. RFC 5675 actually says:

   The VERSION, TIMESTAMP, HOSTNAME, APP-NAME, PROCID, and MSGID fields
   in the SYSLOG message header are filled with values that are specific
   to the system on which the SNMP-to-SYSLOG translator is running.  The
   character set used in the HEADER MUST be seven-bit ASCII in an eight-
   bit field, as described in [RFC5424].

I think this implies that the HOSTNAME contains the name of the host on whi=
ch the translator is running, not the HOSTNAME of the SNMP agent emitting t=
he notification (which BTW may not be known in this case since there can be=
 SNMP proxies).

I would have to dig deeper into IPFIX to understand whether you can always =
find out the hostname of the originator (since there might be mediators inv=
olved as well) or whether there is another reliable way to identify an IPFI=
X exporter.

/js

--=20
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

From tom.taylor.stds@gmail.com  Thu Sep 19 05:56:39 2013
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A61EE21F96B1 for <opsawg@ietfa.amsl.com>; Thu, 19 Sep 2013 05:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.735
X-Spam-Level: 
X-Spam-Status: No, score=-2.735 tagged_above=-999 required=5 tests=[AWL=-0.136, 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 rxygtGnuh6Z5 for <opsawg@ietfa.amsl.com>; Thu, 19 Sep 2013 05:56:39 -0700 (PDT)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id E70AF21F9697 for <opsawg@ietf.org>; Thu, 19 Sep 2013 05:56:38 -0700 (PDT)
Received: by mail-yh0-f53.google.com with SMTP id b20so4054148yha.26 for <opsawg@ietf.org>; Thu, 19 Sep 2013 05:56:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=3nqeh4V1FOBqnNOQuWM0/KGladkfgOOCwEkeyFcx448=; b=MQjvo7x27lvm/93iJDTd0gqs2hJP99KeKX+wj4yNKjJEK7QiQEXz4LRzLXi8nXMbdn O3ohMkdVoVOARyrRjqmFNyXBGsZLO/zOdf44ZImEWHfDdfgUl2mZky3d5DcFh154olLr BY8OsSOWWnN/N3HmyCh92Jj2HTISsGqgzSr+R7n+qSEZPvZKlhwknpsXMkIXKSHaItsE cluKoT9U2qxEVCTdi85BMafCxkpYFwyGPw4l5XDvwMyFLP34p9r4Im/b2JgKRFOPXcNT QdP4awr9yiRZPl5sNZzWfeY2hV9UOYq7PdmTTAYGWSyxvWPQx/hoP/8eThx5led37ejd 6Btw==
X-Received: by 10.236.129.20 with SMTP id g20mr1077015yhi.10.1379595398244; Thu, 19 Sep 2013 05:56:38 -0700 (PDT)
Received: from [192.168.1.73] (dsl-173-206-79-23.tor.primus.ca. [173.206.79.23]) by mx.google.com with ESMTPSA id d40sm10575003yhi.10.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Sep 2013 05:56:37 -0700 (PDT)
Message-ID: <523AF484.3070006@gmail.com>
Date: Thu, 19 Sep 2013 08:56:36 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "opsawg@ietf.org" <opsawg@ietf.org>
References: <523AD964.8060602@gmail.com> <20130919120719.GA554@elstar.local>
In-Reply-To: <20130919120719.GA554@elstar.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [OPSAWG] SYSLOG architectural issue
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2013 12:56:39 -0000

On 19/09/2013 8:07 AM, Juergen Schoenwaelder wrote:
> On Thu, Sep 19, 2013 at 07:00:52AM -0400, Tom Taylor wrote:
>> In Behave, we are dealing with a potential logging architecture
>> where Device A generates the content but exports it in the form of
>> IPFIX records. Device B reformats the content into SYSLOG event
>> reports.
>>
...
>
> I would have to dig deeper into IPFIX to understand whether you can
> always find out the hostname of the originator (since there might be
> mediators involved as well) or whether there is another reliable way
> to identify an IPFIX exporter.
>
> /js
>
[PTT] Good point about IPFIX. RFC 5102 defines exporter IP address 
fields, but not exporter name.

From andrewf@plixer.com  Thu Sep 19 06:37:24 2013
Return-Path: <andrewf@plixer.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 697B521F95DC for <opsawg@ietfa.amsl.com>; Thu, 19 Sep 2013 06:37:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 tlKoMGBEWw2G for <opsawg@ietfa.amsl.com>; Thu, 19 Sep 2013 06:37:19 -0700 (PDT)
Received: from mx1.plixer.com (mx1.plixer.com [64.140.243.154]) by ietfa.amsl.com (Postfix) with ESMTP id 2B37A21F95D0 for <opsawg@ietf.org>; Thu, 19 Sep 2013 06:37:18 -0700 (PDT)
Received: from [10.8.1.10] (64.140.243.154) by mx1.plixer.com (10.1.5.1) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 19 Sep 2013 09:37:17 -0400
Message-ID: <523AFE0D.1030806@plixer.com>
Date: Thu, 19 Sep 2013 09:37:17 -0400
From: Andrew Feren <andrewf@plixer.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: <opsawg@ietf.org>
References: <523AD964.8060602@gmail.com> <20130919120719.GA554@elstar.local> <523AF484.3070006@gmail.com>
In-Reply-To: <523AF484.3070006@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [OPSAWG] SYSLOG architectural issue
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2013 13:37:24 -0000

On 09/19/2013 08:56 AM, Tom Taylor wrote:
> On 19/09/2013 8:07 AM, Juergen Schoenwaelder wrote:
>> On Thu, Sep 19, 2013 at 07:00:52AM -0400, Tom Taylor wrote:
>>> In Behave, we are dealing with a potential logging architecture
>>> where Device A generates the content but exports it in the form of
>>> IPFIX records. Device B reformats the content into SYSLOG event
>>> reports.
>>>
> ...
>>
>> I would have to dig deeper into IPFIX to understand whether you can
>> always find out the hostname of the originator (since there might be
>> mediators involved as well) or whether there is another reliable way
>> to identify an IPFIX exporter.
>>
>> /js
>>
> [PTT] Good point about IPFIX. RFC 5102 defines exporter IP address
> fields, but not exporter name.
I think the not yet assigned "originalExporterIPv4Address" in
draft-ietf-ipfix-mediation-protocol may be closer to what you are
looking for.  Although that draft also has no originalExporterName
defined.  Perhaps some name equivalents should be requested.

FWIW very recently 7012 obsoleted 5102 and  "The IANA "IPFIX Information
Elements" registry [IANA-IPFIX] is the current complete reference for
IPFIX Information Elements."  Still no exporterName element though.  :-)

As to the original question I think it is much more useful if HOSTNAME
is Device A (the original source of the log)

-Andrew

From ietf@cdl.asgaard.org  Thu Sep 19 09:20:43 2013
Return-Path: <ietf@cdl.asgaard.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 565BE21F9385 for <opsawg@ietfa.amsl.com>; Thu, 19 Sep 2013 09:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 dl1fLKvubGNh for <opsawg@ietfa.amsl.com>; Thu, 19 Sep 2013 09:20:39 -0700 (PDT)
Received: from smtp1.emailarray.com (smtp1.emailarray.com [65.39.216.14]) by ietfa.amsl.com (Postfix) with ESMTP id D8EEC21F994A for <opsawg@ietf.org>; Thu, 19 Sep 2013 09:20:37 -0700 (PDT)
Received: (qmail 7733 invoked by uid 89); 19 Sep 2013 16:20:36 -0000
Received: from unknown (HELO ?204.29.150.162?) (Y2RsQGFzZ2FhcmQub3JnQDUwLjc2LjM0LjE4NQ==) (POLARISLOCAL)  by smtp1.emailarray.com with SMTP; 19 Sep 2013 16:20:36 -0000
From: "Christopher LILJENSTOLPE" <ietf@cdl.asgaard.org>
To: "Andrew Feren" <andrewf@plixer.com>
Date: Thu, 19 Sep 2013 09:20:34 -0700
Message-ID: <DBD58CC5-79AA-46E9-B766-65ACC0A0BC69@cdl.asgaard.org>
In-Reply-To: <523AFE0D.1030806@plixer.com>
References: <523AD964.8060602@gmail.com> <20130919120719.GA554@elstar.local> <523AF484.3070006@gmail.com> <523AFE0D.1030806@plixer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.6r3684)
X-PolarisMail-Flags: x
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] [eX-bulk] : Re:  SYSLOG architectural issue
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2013 16:20:43 -0000

On 19 Sep 2013, at 6:37, Andrew Feren wrote:

> On 09/19/2013 08:56 AM, Tom Taylor wrote:
>> On 19/09/2013 8:07 AM, Juergen Schoenwaelder wrote:
>>> On Thu, Sep 19, 2013 at 07:00:52AM -0400, Tom Taylor wrote:
>>>> In Behave, we are dealing with a potential logging architecture
>>>> where Device A generates the content but exports it in the form of
>>>> IPFIX records. Device B reformats the content into SYSLOG event
>>>> reports.
>>>>
>> ...
>>>
>>> I would have to dig deeper into IPFIX to understand whether you can
>>> always find out the hostname of the originator (since there might be
>>> mediators involved as well) or whether there is another reliable way
>>> to identify an IPFIX exporter.
>>>
>>> /js
>>>
>> [PTT] Good point about IPFIX. RFC 5102 defines exporter IP address
>> fields, but not exporter name.
> I think the not yet assigned "originalExporterIPv4Address" in
> draft-ietf-ipfix-mediation-protocol may be closer to what you are
> looking for.  Although that draft also has no originalExporterName
> defined.  Perhaps some name equivalents should be requested.
>
> FWIW very recently 7012 obsoleted 5102 and  "The IANA "IPFIX 
> Information
> Elements" registry [IANA-IPFIX] is the current complete reference for
> IPFIX Information Elements."  Still no exporterName element though.  
> :-)
>
> As to the original question I think it is much more useful if HOSTNAME
> is Device A (the original source of the log)

I would agree with Andrew in both points.  A field would be best, 
however, in the absence of such a field, the HOSTNAME should be from 
Device A, not Device B.
	
	Christopher

>
> -Andrew
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg


--
李柯睿
Check my PGP key here: http://www.asgaard.org/cdl/cdl.asc
Current vCard here: http://www.asgaard.org/cdl/cdl.vcf

From Jean-Francois.TremblayING@videotron.com  Fri Sep 20 06:04:08 2013
Return-Path: <Jean-Francois.TremblayING@videotron.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19F3421F9344 for <opsawg@ietfa.amsl.com>; Fri, 20 Sep 2013 06:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.391
X-Spam-Level: 
X-Spam-Status: No, score=-1.391 tagged_above=-999 required=5 tests=[AWL=-1.208, BAYES_40=-0.185, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iJ4tnu9qkYYn for <opsawg@ietfa.amsl.com>; Fri, 20 Sep 2013 06:04:03 -0700 (PDT)
Received: from mx02.videotron.com (mx02.videotron.com [24.201.243.151]) by ietfa.amsl.com (Postfix) with ESMTP id EF27921F92DA for <opsawg@ietf.org>; Fri, 20 Sep 2013 06:04:02 -0700 (PDT)
In-Reply-To: <DBD58CC5-79AA-46E9-B766-65ACC0A0BC69@cdl.asgaard.org>
References: <523AD964.8060602@gmail.com> <20130919120719.GA554@elstar.local>	<523AF484.3070006@gmail.com> <523AFE0D.1030806@plixer.com> <DBD58CC5-79AA-46E9-B766-65ACC0A0BC69@cdl.asgaard.org>
To: opsawg@ietf.org
MIME-Version: 1.0
X-KeepSent: B9A5F310:C0F58C21-85257BEC:00475443; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.3FP1 March 08, 2012
Message-ID: <OFB9A5F310.C0F58C21-ON85257BEC.00475443-85257BEC.0047C7A3@videotron.com>
From: Jean-Francois.TremblayING@videotron.com
Date: Fri, 20 Sep 2013 09:04:01 -0400
X-MIMETrack: Serialize by Router on DOMMSG01/SRV/GVL(Release 8.5.3FP3|November 15, 2012) at 09/20/2013 09:04:01, Serialize complete at 09/20/2013 09:04:01
Content-Type: multipart/alternative; boundary="=_alternative 0047C7A285257BEC_="
Received-SPF: none
Subject: Re: [OPSAWG] : Re:  SYSLOG architectural issue
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Sep 2013 13:04:08 -0000

Message en plusieurs parties au format MIME
--=_alternative 0047C7A285257BEC_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

opsawg-bounces@ietf.org a =E9crit sur 19/09/2013 12:20:34 PM :

> De : "Christopher LILJENSTOLPE" <ietf@cdl.asgaard.org>
> I would agree with Andrew in both points.  A field would be best,=20
> however, in the absence of such a field, the HOSTNAME should be from=20
> Device A, not Device B.
>=20
>    Christopher

<operator hat on>
Agreed. Device A should be in the field, having device B is not of much=20
use.=20

Aggregating both names in the same fields seems like a bad idea, it would=20
only confuse correlation at the receiving end (a Splunk for example).=20

/JF


--=_alternative 0047C7A285257BEC_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<tt><font size=3D2>opsawg-bounces@ietf.org a =E9crit sur 19/09/2013 12:20:34
PM :<br>
<br>
&gt; De : &quot;Christopher LILJENSTOLPE&quot; &lt;ietf@cdl.asgaard.org&gt;=
</font></tt>
<br><tt><font size=3D2>&gt; I would agree with Andrew in both points. &nbsp=
;A
field would be best, <br>
&gt; however, in the absence of such a field, the HOSTNAME should be from
<br>
&gt; Device A, not Device B.<br>
&gt; &nbsp; &nbsp;<br>
&gt; &nbsp; &nbsp;Christopher<br>
</font></tt>
<br><tt><font size=3D2>&lt;operator hat on&gt;</font></tt>
<br><tt><font size=3D2>Agreed. Device A should be in the field, having devi=
ce
B is not of much use. </font></tt>
<br>
<br><tt><font size=3D2>Aggregating both names in the same fields seems like
a bad idea, it would only confuse correlation at the receiving end (a Splunk
for example). </font></tt>
<br>
<br><tt><font size=3D2>/JF</font></tt>
<br>
<br>
--=_alternative 0047C7A285257BEC_=--

From ramk@Brocade.com  Fri Sep 20 15:51:42 2013
Return-Path: <ramk@Brocade.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E464721F99FB for <opsawg@ietfa.amsl.com>; Fri, 20 Sep 2013 15:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.265
X-Spam-Level: 
X-Spam-Status: No, score=-3.265 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1]
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 KIB9wWaeYLbG for <opsawg@ietfa.amsl.com>; Fri, 20 Sep 2013 15:51:34 -0700 (PDT)
Received: from mx0a-000f0801.pphosted.com (mx0a-000f0801.pphosted.com [67.231.144.122]) by ietfa.amsl.com (Postfix) with ESMTP id 9E58C21F994C for <opsawg@ietf.org>; Fri, 20 Sep 2013 15:51:34 -0700 (PDT)
Received: from pps.filterd (m0000542 [127.0.0.1]) by mx0a-000f0801.pphosted.com (8.14.5/8.14.5) with SMTP id r8KMDv5S021025; Fri, 20 Sep 2013 15:51:34 -0700
Received: from hq1wp-exchub01.corp.brocade.com ([144.49.131.13]) by mx0a-000f0801.pphosted.com with ESMTP id 1f0w1eg2k4-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 20 Sep 2013 15:51:34 -0700
Received: from HQ1WP-EXHUB01.corp.brocade.com (10.70.36.14) by HQ1WP-EXCHUB01.corp.brocade.com (10.70.36.99) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 20 Sep 2013 15:51:33 -0700
Received: from HQ1-EXCH01.corp.brocade.com ([fe80::ed42:173e:fe7d:d0a6]) by HQ1WP-EXHUB01.corp.brocade.com ([::1]) with mapi; Fri, 20 Sep 2013 15:51:33 -0700
From: ramki Krishnan <ramk@Brocade.com>
To: "George, Wes" <wesley.george@twcable.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Date: Fri, 20 Sep 2013 15:51:32 -0700
Thread-Topic: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
Thread-Index: Ac6hBYkTvOHfyrGyQTOGjmvrFi+FzASGY3+gADxrTvAAGpwIYAB2EOEw
Message-ID: <C7634EB63EFD984A978DFB46EA5174F2BFFEA3756A@HQ1-EXCH01.corp.brocade.com>
References: <52191268.5070500@gmail.com> <2671C6CDFBB59E47B64C10B3E0BD5923043A84B63A@PRVPEXVS15.corp.twcable.com> <C7634EB63EFD984A978DFB46EA5174F2BFFE959BB1@HQ1-EXCH01.corp.brocade.com> <2671C6CDFBB59E47B64C10B3E0BD5923043A8F51DF@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923043A8F51DF@PRVPEXVS15.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-09-20_11:2013-09-20, 2013-09-20, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1309200116
Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks"
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Sep 2013 22:51:42 -0000

Thanks Wes, please see inline.

Thanks,
Ramki
-----Original Message-----
From: George, Wes [mailto:wesley.george@twcable.com]=20
Sent: Wednesday, September 18, 2013 7:43 AM
To: ramki Krishnan; opsawg@ietf.org
Subject: RE: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Com=
ponent Link Utilization in Networks"

> From: ramki Krishnan [mailto:ramk@Brocade.com]
>
>
> For determining component link imbalance, we are using interface=20
> counters.  For tracking the effectiveness of the scheme, we also have=20
> other monitoring information such as 1) Number of times rebalancing=20
> was done and 2) Time since the last rebalancing event. Is there=20
> something else that you think would be helpful?
[WEG] yes. You need info about the number of flows being tracked on each in=
terface and their size, possibly also the category (long-lived vs short, la=
rge vs small) as well as which flows have been moved and when. You're alrea=
dy building all of this state to provide input to your algorithm, I'm just =
saying that you need to make it clear in the draft that operators may want =
to be able to see that data. Like I said, in order to evaluate this as actu=
ally being better than the existing hash, to tune the parameters, and to tr=
oubleshoot balancing problems, I need to be able to see what it's actually =
doing, not just the interface counters.
[ramki] will do.

>
> >> I realize that in the model you've proposed, we're somewhat limited
> because this is using sampled flow data instead of the realtime packet=20
> hash. It may be that this drives a requirement for the granularity of=20
> data being brought into the system in the external mode, and some=20
> requirements about the level of information available via the UI (or=20
> SNMP or XML or whatever) in the automatic hardware-based mode.
>
> For large flow detection, we propose two modes 1) Sampling Techniques=20
> 2) Automatic Hardware Recognition. The primary difference between the=20
> two modes in terms of performance is the time taken to recognize the=20
> long- lived large flows; there is no loss of accuracy in either mode.=20
> In the automatic hardware based mode for detecting the large flows, it=20
> is best that the load balancing happen in the router. Are you looking=20
> for anything else ?
[WEG] Yes, I think maybe I was unclear. I'm looking for diagnostic tools to=
 make this less opaque for an operator. I was noting that it may be difficu=
lt to give specific, granular information by flow about the size of each fl=
ow and when/if it was moved by the loadbalancing algorithm if you were reli=
ant on sampled flow data, because it wouldn't be complete/granular enough -=
- it would only show a subset of the flows, not all flows.
[ramki] In this case, large flows are a significant percentage of the link =
bandwidth. We don't see any issue in tracking such large flows through samp=
ling technologies like sFlow.

Thanks
Wes


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From zehn.cao@gmail.com  Sun Sep 22 18:29:34 2013
Return-Path: <zehn.cao@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 970F421F940D for <opsawg@ietfa.amsl.com>; Sun, 22 Sep 2013 18:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.391
X-Spam-Level: 
X-Spam-Status: No, score=-1.391 tagged_above=-999 required=5 tests=[AWL=-0.280, BAYES_05=-1.11, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iv172OXxOv2c for <opsawg@ietfa.amsl.com>; Sun, 22 Sep 2013 18:29:33 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 78D5D21F942D for <opsawg@ietf.org>; Sun, 22 Sep 2013 18:29:33 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id n12so2503370wgh.15 for <opsawg@ietf.org>; Sun, 22 Sep 2013 18:29:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=sIqiHjr10oh2dmNAfgqy319pYnmh3HZoOm8Emx/G5kc=; b=nk4xh5pnKTaHDCJmZeb4XqK2kR3E8FGj5lASEZVvodq/3enGt5AkJ/uIMWd0wqVaPB 8dvan/xk+dOKA0wgimvB8G4cQey7BobpVFTTRzDnJZxEDqK5zwWf8Iq7F/Q/adacWFPt B8i5TY5nmMREp/mO4mYOIz/pp7u0Yx+Yf6GmVmlktqEVyDjiNsEWgRuBcRH1jIPLRGaf nZeVLRcR+u1UVEr6EKG6SnPT+QbKPUfHlA64ykMewPYcnY9iZwuKX3SIBdMpfRRrJnwx B9sexQloENrMDwoYSpRtpcMLIpIYoS+jDKBvo7Oip6J3hToWPLlJSTMtuUWD/puS60GY Lmyg==
MIME-Version: 1.0
X-Received: by 10.180.205.236 with SMTP id lj12mr11477651wic.22.1379899772595;  Sun, 22 Sep 2013 18:29:32 -0700 (PDT)
Received: by 10.216.214.131 with HTTP; Sun, 22 Sep 2013 18:29:32 -0700 (PDT)
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F247B6AC6@nkgeml501-mbs.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F247A21EA@nkgeml501-mbs.china.huawei.com> <CAProHATCVwfhjP6qXqCh+B65p_Eht=FexRtKeCKWXUL1hxvobQ@mail.gmail.com> <E33E01DFD5BEA24B9F3F18671078951F247B2421@nkgeml501-mbs.china.huawei.com> <CAProHATRWGccbLxUXXH7T=PfvzGt3VOGPXOuYxPv-ZFjK+QfrQ@mail.gmail.com> <E33E01DFD5BEA24B9F3F18671078951F247B6AC6@nkgeml501-mbs.china.huawei.com>
Date: Mon, 23 Sep 2013 09:29:32 +0800
Message-ID: <CAProHARDUo+8mOfMJTT+aQtr1WLfDuDn2+=vMhhFh64TzU85cQ@mail.gmail.com>
From: "Cao,Zhen" <zehn.cao@gmail.com>
To: "Songhaibin (A)" <haibin.song@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] FW: New Version Notification for draft-song-opsawg-virtual-network-function-config-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Sep 2013 01:29:34 -0000

Hi Haibin,

Inline please.

On Wed, Sep 18, 2013 at 3:15 PM, Songhaibin (A) <haibin.song@huawei.com> wr=
ote:
>> [Haibin] I agree! A user can directly establish a service chain or servi=
ce chains. For the service graph, there can be two layers IMO, one is the s=
table virtual link layer, and the other is conditional/stable service forwa=
rding layer. I also noticed that there was a network service chain BOF at l=
ast IETF meeting. But they are focusing on how to identify a service chain =
and how to do the forwarding in the service chain. But for the requirement =
here, we only want the user the send the description to the controller.
>>
> [cz] NSC may have further impacts on the configuration, for example,
> some functions may be implemented by chaining existing 'atom
> functions'. What's I am not sure right now the granularity of the vNF
> configuration, a) user specifies the detailed function, e.g., fw, lb,
> etc.. b) user specifies the high layer vNF objectives that need
> chaining of several vNFs...
>
> [Haibin] I think both a) and b) should be supported. Different users have=
 different expertise level. And it is also service related. Different VNF p=
roviders may have their own policy about whether to allow the users to spec=
ifies what you mentioned "atom functions" and to what level. But this is a =
good point that should be reflected when the document is updated.
>

[cz] it will be a rather complicate architecture for vnf
configuration. For ietf, have you figured out what's the gap of
protocols that will be needed to support this architecture?

>
>> 2. service elasticity requirements should be specified by the user
>> [Haibin] I have some description of this use case in the last paragraph =
of Section 1. Just like that the user tells the controller, "allocate resou=
rces on-demand for me". Do you have some good idea in-mind on what are the =
elasticity requirements?
>
> [cz] there should be some metrics for the "on-demand", because the vNF
> resource could never be enough based on the available infrastructure.
> For example, the vFW could be handling 100K transactions at most, sth
> like this.
>
>>
>>    There are also resource requirements for the remote software
>>    installation, which are complement to the software components
>>    selection.  There is lack of a standard for a user to tell the
>>    controller how much bandwidth, storage, CPU, memory are allocated to
>>    a specific software in the provider's network (perhaps there is
>>    existing standard for the virtual machine or host level resources),
>>
>> [cz] but the Openstack-Neutron have such APIs to specify the user's
>> request , better to notice the difference here.
>>
>> [Haibin] VNF level and VM level are different. Because one VM might be h=
olding multiple VNFs. That interface you mentioned is combined with a VM IM=
O and are not easy to make a change. But here when the resource is combined=
 with a VNF. It is much easier to change it. Any thoughts?
>
> [cz] that's clarifies the difference, i think we should make it
> clearer how the the configuration differ from the cloud OS interface.
> Such description above should be stressed.
>
> [Haibin] OK.
>
>
>> =3D=3Dquote
>> 4.  Scope for Standardization
>> [cz] Envision a picture here. and what's the operator's role in the pict=
ure,
>> i believe the operator-controller interface should also be specified ,
>> maybe add a (3).
>>
>> [Haibin] IMO, operator owns the controller. OSS/BSS for the NFV service =
is part of the controller. But the network administrator from the operator =
can also act as a user to install and configure VNFs in the provider's (ope=
rator's) network for the customers or for himself. This is the picture in m=
y mind. Is it consistent with what you have in mind?
>
> [cz] I believe the controller could be third party SP selling software
> components for NFV, in this case, there should be the interface for
> the operator to configure the controller in this architecture.
>
> [Haibin] I agree with your point, but I would assume that the controller =
has already be configured for the problem statement in this draft.
>
[cz] ok

From cathy.zhou@huawei.com  Sun Sep 22 19:02:18 2013
Return-Path: <cathy.zhou@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2A6C11E8172 for <opsawg@ietfa.amsl.com>; Sun, 22 Sep 2013 19:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.402
X-Spam-Level: 
X-Spam-Status: No, score=-6.402 tagged_above=-999 required=5 tests=[AWL=-0.197, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_OTHER=0.135, SARE_SUB_OBFU_Z=0.259]
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 aVyIlChAgELp for <opsawg@ietfa.amsl.com>; Sun, 22 Sep 2013 19:02:14 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 297AA11E8167 for <opsawg@ietf.org>; Sun, 22 Sep 2013 19:02:14 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYD17723; Mon, 23 Sep 2013 02:02:12 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 23 Sep 2013 03:01:30 +0100
Received: from SZXEML404-HUB.china.huawei.com (10.82.67.59) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 23 Sep 2013 03:02:10 +0100
Received: from SZXEML513-MBS.china.huawei.com ([169.254.8.106]) by szxeml404-hub.china.huawei.com ([::1]) with mapi id 14.03.0146.000; Mon, 23 Sep 2013 10:02:04 +0800
From: "Zhouqian (Cathy)" <cathy.zhou@huawei.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: New Version Notification for draft-xjz-nfv-model-problem-statement-00.txt
Thread-Index: AQHOqc5wgDlsDqXeEkOjLJLc3GC9k5nSqrWQ
Date: Mon, 23 Sep 2013 02:02:05 +0000
Message-ID: <A6A061BEE5DDC94A9692D9D81AF776DF39AC6F3F@szxeml513-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.76.105]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [OPSAWG] FW: New Version Notification for	draft-xjz-nfv-model-problem-statement-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Sep 2013 02:02:18 -0000

RGVhciBhbGwsDQpXZSBoYXZlIHN1Ym1pdHRlZCBhIG5ldyBkcmFmdCBvbiB0aGUgcHJvYmxlbSBz
cGFjZSBvZiB0aGUgTmV0d29yayBGdW5jdGlvbnMgVmlydHVhbGl6YXRpb24gbW9kZWxpbmcuIA0K
VGhlIGdvYWwgb2YgdGhlIGRvY3VtZW50IGlzIHRvIHByb3ZpZGUgbWFuYWdlbWVudCBlbnRpdGll
cyB3aXRoIHN0YW5kYXJkaXplZCBpbmZvcm1hdGlvbiB0aGV5IGNhbiB1c2UgdG8gZGVwbG95LCBp
bnN0YW50aWF0ZSwgY29uZmlndXJlIGFuZCBtYW5hZ2UgbmV0d29yayBzZXJ2aWNlcyBiYXNlZCBv
biBORlYgaW5mcmFzdHJ1Y3R1cmUuIFRoZSBpbmZvcm1hdGlvbiBpcyBvcmdhbml6ZWQgd2l0aCBW
TkZELCB0aGUgVk5GIEZvcndhcmRpbmcgR3JhcGggYW5kIHRoZSBORlYgU2VydmljZS4gQSBuZXcg
c2V0IG9mIGRhdGEgbW9kZWxzIChlLmcuLCBZQU5HKSBtYXkgYmUgbmVlZGVkIGZvciB0aGVzZSBp
bmZvcm1hdGlvbi4NCllvdXIgY29tbWVudHMgYXJlIHdlbGNvbWUuDQoNCkJlc3QgUmVnYXJkcywN
CkNhdGh5DQoNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpbnRlcm5l
dC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmddDQo+IFNl
bnQ6IFRodXJzZGF5LCBTZXB0ZW1iZXIgMDUsIDIwMTMgODoyNiBBTQ0KPiBUbzogWHV3ZWlwaW5n
IChBKTsgWmhvdXFpYW4gKENhdGh5KTsgSmlhbmd5dWFubG9uZw0KPiBTdWJqZWN0OiBOZXcgVmVy
c2lvbiBOb3RpZmljYXRpb24gZm9yDQo+IGRyYWZ0LXhqei1uZnYtbW9kZWwtcHJvYmxlbS1zdGF0
ZW1lbnQtMDAudHh0DQo+IA0KPiANCj4gQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LXhqei1u
ZnYtbW9kZWwtcHJvYmxlbS1zdGF0ZW1lbnQtMDAudHh0DQo+IGhhcyBiZWVuIHN1Y2Nlc3NmdWxs
eSBzdWJtaXR0ZWQgYnkgV2VpcGluZyBYdSBhbmQgcG9zdGVkIHRvIHRoZQ0KPiBJRVRGIHJlcG9z
aXRvcnkuDQo+IA0KPiBGaWxlbmFtZToJIGRyYWZ0LXhqei1uZnYtbW9kZWwtcHJvYmxlbS1zdGF0
ZW1lbnQNCj4gUmV2aXNpb246CSAwMA0KPiBUaXRsZToJCSBQcm9ibGVtIFN0YXRlbWVudCBvZiBO
ZXR3b3JrIEZ1bmN0aW9ucyBWaXJ0dWFsaXphdGlvbg0KPiBNb2RlbA0KPiBDcmVhdGlvbiBkYXRl
OgkgMjAxMy0wOS0wMQ0KPiBHcm91cDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCj4gTnVtYmVy
IG9mIHBhZ2VzOiAxMA0KPiBVUkw6DQo+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJh
ZnRzL2RyYWZ0LXhqei1uZnYtbW9kZWwtcHJvYmxlbS1zdGF0ZW1lbnQNCj4gLTAwLnR4dA0KPiBT
dGF0dXM6DQo+IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQteGp6LW5mdi1t
b2RlbC1wcm9ibGVtLXN0YXRlbWVudA0KPiBIdG1saXplZDoNCj4gaHR0cDovL3Rvb2xzLmlldGYu
b3JnL2h0bWwvZHJhZnQteGp6LW5mdi1tb2RlbC1wcm9ibGVtLXN0YXRlbWVudC0wMA0KPiANCj4g
DQo+IEFic3RyYWN0Og0KPiAgICBUaGlzIGRvY3VtZW50IGRpc2N1c3NlcyB0aGUgcHJvYmxlbSBz
cGFjZSBvZiB0aGUgTmV0d29yayBGdW5jdGlvbnMNCj4gICAgVmlydHVhbGlzYXRpb24gKE5GVikg
bW9kZWxzIGluIHRoZSBORlYgZW52aXJvbm1lbnQuIFBvc3NpYmxlIHVzZQ0KPiAgICBjYXNlcyBh
bmQgdGhlIGxhbmd1YWdlIGZvciB0aGUgbW9kZWxzIHdpbGwgYWxzbyBiZSBpZGVudGlmaWVkLg0K
PiANCj4gDQo+IA0KPiANCj4gUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBv
ZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbg0KPiB1bnRpbCB0aGUgaHRtbGl6
ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KPiAN
Cj4gVGhlIElFVEYgU2VjcmV0YXJpYXQNCg0K

From haibin.song@huawei.com  Sun Sep 22 19:03:48 2013
Return-Path: <haibin.song@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F5B011E8178 for <opsawg@ietfa.amsl.com>; Sun, 22 Sep 2013 19:03:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m77ptvwWRDDm for <opsawg@ietfa.amsl.com>; Sun, 22 Sep 2013 19:03:43 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6FD1C11E8175 for <opsawg@ietf.org>; Sun, 22 Sep 2013 19:03:43 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYD17800; Mon, 23 Sep 2013 02:03:42 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 23 Sep 2013 03:02:57 +0100
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 23 Sep 2013 03:03:42 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.141]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0146.000; Mon, 23 Sep 2013 10:03:37 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: New Version Notification for draft-zhou-opsawg-vnf-config-arch-00.txt
Thread-Index: AQHOuADNBMO35b/PFk+XiKs9gJMc4JnSkeeQ
Date: Mon, 23 Sep 2013 02:03:36 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F247B7D7B@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [OPSAWG] FW: New Version Notification for draft-zhou-opsawg-vnf-config-arch-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Sep 2013 02:03:48 -0000

SGksDQoNCldlIGhhdmUganVzdCBzdWJtaXR0ZWQgYSBkcmFmdCBvbiBWaXJ0dWFsIE5ldHdvcmsg
RnVuY3Rpb24gQ29uZmlndXJhdGlvbiBBcmNoaXRlY3R1cmUuIEFueSBjb21tZW50cyBhcmUgd2Vs
Y29tZS4NCg0KDQpCUiwNCi1IYWliaW4NCkh1YXdlaSBUZWNobm9sb2dpZXMgQ28uLCBMdGQuDQoN
Ci0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5v
cmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmddIA0KU2VudDogTW9uZGF5LCBTZXB0
ZW1iZXIgMjMsIDIwMTMgMTA6MDEgQU0NClRvOiBTb25naGFpYmluIChBKTsgRnUgUWlhbzsgWmhv
dWhvbmcNClN1YmplY3Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtemhvdS1v
cHNhd2ctdm5mLWNvbmZpZy1hcmNoLTAwLnR4dA0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBk
cmFmdC16aG91LW9wc2F3Zy12bmYtY29uZmlnLWFyY2gtMDAudHh0DQpoYXMgYmVlbiBzdWNjZXNz
ZnVsbHkgc3VibWl0dGVkIGJ5IEhvbmcgWmhvdSBhbmQgcG9zdGVkIHRvIHRoZQ0KSUVURiByZXBv
c2l0b3J5Lg0KDQpGaWxlbmFtZToJIGRyYWZ0LXpob3Utb3BzYXdnLXZuZi1jb25maWctYXJjaA0K
UmV2aXNpb246CSAwMA0KVGl0bGU6CQkgVmlydHVhbCBOZXR3b3JrIEZ1bmN0aW9uIENvbmZpZ3Vy
YXRpb24gQXJjaGl0ZWN0dXJlDQpDcmVhdGlvbiBkYXRlOgkgMjAxMy0wOS0yMw0KR3JvdXA6CQkg
SW5kaXZpZHVhbCBTdWJtaXNzaW9uDQpOdW1iZXIgb2YgcGFnZXM6IDkNClVSTDogICAgICAgICAg
ICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtemhvdS1vcHNhd2ct
dm5mLWNvbmZpZy1hcmNoLTAwLnR4dA0KU3RhdHVzOiAgICAgICAgICBodHRwOi8vZGF0YXRyYWNr
ZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXpob3Utb3BzYXdnLXZuZi1jb25maWctYXJjaA0KSHRtbGl6
ZWQ6ICAgICAgICBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC16aG91LW9wc2F3Zy12
bmYtY29uZmlnLWFyY2gtMDANCg0KDQpBYnN0cmFjdDoNCiAgIFRoaXMgZG9jdW1lbnQgZGVzY3Jp
YmVzIHRoZSBhcmNoaXRlY3R1cmUgb2YgcmVtb3RlIHNlcnZpY2UNCiAgIGluc3RhbGxhdGlvbiBh
bmQgY29uZmlndXJhdGlvbiBpbiB0aGUgcHJvdmlkZXIncyBuZXR3b3JrIHRocm91Z2ggYQ0KICAg
Y2VudHJhbGl6ZWQgbWFuYWdlbWVudCBzeXN0ZW0uICBUaGlzIGlzIGEgdHlwaWNhbCBzY2VuYXJp
byBmb3INCiAgIHZpcnR1YWwgbmV0d29yayBmdW5jdGlvbiBpbnN0YWxsYXRpb24gYW5kIGR5bmFt
aWMgY29uZmlndXJhdGlvbiBpbg0KICAgbmV0d29yayBmdW5jdGlvbiB2aXJ0dWFsaXphdGlvbiAo
TkZWKSBjb250ZXh0LiAgSXQgaXMgYWxzbyBhIHR5cGljYWwNCiAgIHNjZW5hcmlvIGluIGNsb3Vk
IGNvbXB1dGluZyBlbnZpcm9ubWVudCB3aGVyZSBlbmQgdXNlcnMgZG8gbm90IGhhdmUNCiAgIHRv
IGluc3RhbGwgYXBwbGljYXRpb25zIG9uIHRoZWlyIGVuZCBob3N0cywgYnV0IGNhbiBpbnN0YWxs
IHRoZWlyIG93bg0KICAgZmVhdHVyZWQgcG93ZXJmdWwgc29mdHdhcmUgYXBwbGljYXRpb24gaW4g
dGhlIGNsb3VkLiAgVGhpcw0KICAgc3BlY2lmaWNhdGlvbiBkZXNjcmliZXMgYW4gYXJjaGl0ZWN0
dXJlIG9mIHZpcnR1YWwgbmV0d29yayBmdW5jdGlvbg0KICAgaW5zdGFsbGF0aW9uIGFuZCBjb25m
aWd1cmF0aW9uLiAgSXQgaXMgYWxzbyBhcHBsaWNhYmxlIHRvIG90aGVyIHVzZQ0KICAgY2FzZXMg
d2l0aCBzaW1pbGFyIHJlcXVpcmVtZW50cy4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0K
DQoNClBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9t
IHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24NCnVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBk
aWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQoNClRoZSBJRVRGIFNlY3JldGFy
aWF0DQoNCg==

From bclaise@cisco.com  Mon Sep 23 08:50:34 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C209821F9477 for <opsawg@ietfa.amsl.com>; Mon, 23 Sep 2013 08:50:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.801
X-Spam-Level: 
X-Spam-Status: No, score=-9.801 tagged_above=-999 required=5 tests=[AWL=-0.692, BAYES_05=-1.11, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 rCf3nc43nGr9 for <opsawg@ietfa.amsl.com>; Mon, 23 Sep 2013 08:50:12 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id BE3E221F86B2 for <opsawg@ietf.org>; Mon, 23 Sep 2013 08:50:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=68148; q=dns/txt; s=iport; t=1379951411; x=1381161011; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=kNMoskTNFWoE7uAF7fve8yc9hesaFyv0wg/5+d5l+qI=; b=ZvSTy6s9q9Y23qVrkXMt1npWrhganQ4XjKDnqRB7I+SwWTQHyN0u7SkT LaY9/sluJ8NbfAu3HeBG02FOJt8/0ex+NYQgYwOhVs8eozAjcBGYO/BSO PCeTa2H9zG54NSdSYmHoS/QiaOZoQaSmFDJemdIUZE3gFvHH3vxxcCsQW Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ar4FAENiQFKQ/khM/2dsb2JhbABZgkNEOIlYuCuBIhZtB4IlAQEBAwEYAgESRQcFCxwBAwEBAQkXAQYHDxIlAwYIBg0BBQIBAQURh1kDCQYMsToNiWqMd4E1gTQFBgGEHgOWE4FpgS+FA4YShTODJjqBNQ
X-IronPort-AV: E=Sophos;i="4.90,872,1371081600"; d="scan'208,217";a="17745370"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 23 Sep 2013 15:50:05 +0000
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r8NFo2C2005712; Mon, 23 Sep 2013 15:50:03 GMT
Message-ID: <5240632A.7@cisco.com>
Date: Mon, 23 Sep 2013 17:50:02 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "opsawg@ietf.org" <opsawg@ietf.org>
References: <523C7060.1040903@cisco.com>
In-Reply-To: <523C7060.1040903@cisco.com>
X-Forwarded-Message-Id: <523C7060.1040903@cisco.com>
Content-Type: multipart/alternative; boundary="------------060503090806020101050605"
Cc: "draft-ietf-opsawg-oam-overview@tools.ietf.org" <draft-ietf-opsawg-oam-overview@tools.ietf.org>
Subject: [OPSAWG] draft-ietf-opsawg-oam-overview sent back to the WG
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Sep 2013 15:50:35 -0000

This is a multi-part message in MIME format.
--------------060503090806020101050605
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

In agreement between OPS ADs and the WG chairs, I'm resending 
draft-ietf-opsawg-oam-overview to the WG, for further work.
This document was sent to the IESG in August 2011.

The authors received a lot of feedback (150 if I'm not mistaken), mainly 
from the directorates and the IESG.
Some of this feedback relates to basic comments, such as the 
definitions. This leads me to think that the WG has not spent enough 
time reviewing the document.
On top of that, see 
https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/
Based on this ballot half the positions are held by people who aren't on 
the IESG anymore.

This will probably arrive as a bad news, but my highest priority is 
document quality.

Here is also some background information, outcome of the IESG retreat
http://www.ietf.org/mail-archive/web/ietf/current/msg79194.html

    1. Send more documents back to the WG to complete the necessary changes. While the responsibility for changes has always been at the WG, the documents were still in the IESG process. The IESG felt that particularly in situations where changes are large or multiple, it would be useful to make the situation about WG ownership even clearer. We will do this by handing the document back to the WG and getting the IESG out of the loop, with the instruction that the chairs should manage the process and address the issues raised in the IETF last call and by the ADs.


Regards, Benoit (OPS AD)

> Hi Benoit, Joel,
>
> We have done quite a bit of work on this draft lately, and I believe 
> we are steadily moving towards convergence.
>
> Following Stewart's comments we have ~5 open issues, which I believe 
> can be resolved with a bit of work.
>
> Assuming we resolve Stewart's comments, how would you suggest to proceed?
>
> Thanks,
> Tal.
>
> *From:*Stewart Bryant [mailto:stbryant@cisco.com]
> *Sent:* Friday, September 20, 2013 3:24 PM
> *To:* Tal Mizrahi
> *Cc:* Benoit Claise
> *Subject:* Re: Mail regarding draft-ietf-opsawg-oam-overview
>
> Hi Tal,
>
> Next week is not the greatest week, as I am quite busy, but we should 
> be able to get some time morning or early afternoon 30th. Will this be 
> just with you, or are you also inviting your co-authors?
>
> However, so that we do not waste our time, can I suggest that you 
> first talk to your AD to see how they wishes to progress the draft.
>
> - Stewart
>
>
> On 20/09/2013 11:59, Tal Mizrahi wrote:
>
>     Hi Stewart,
>
>     Sorry for nagging, but it would be great if we could have a short
>     call early next week.
>
>     Thanks,
>     Tal.
>
>     *From:*Tal Mizrahi
>     *Sent:* Wednesday, September 18, 2013 12:06 AM
>     *To:* 'stbryant@cisco.com <mailto:stbryant@cisco.com>'
>     *Subject:* RE: Mail regarding draft-ietf-opsawg-oam-overview
>
>     Hi Stewart,
>
>     Thanks for your responses.
>
>     I am switching to unicast mode, as I think it will be more effective.
>
>     In the next few days I am going to do some further work following
>     your comments, and if it is okay with you I would like to do a
>     phone/Webex 1:1 meeting with you, to make sure we have addressed
>     your concerns. I think we can save a lot of back-and-forth emails
>     with a short conversation.
>
>     Wednesday-Friday are a holiday in Israel, but would you be
>     available on Monday morning for phone/Webex?
>
>     In the meantime, just a couple of clarification questions:
>
>     >>and a devolved application specific control plane function
>     >What is one of those?
>
>     Stewart, sorry but I could not understand the comment. Did you
>     mean that we should add an example of an application specific
>     control plane function?
>
>     >>>FRR is, at least within the ITU definition and OAM function. There
>     >>>is BTW no discussion of the network repair class of OAM function
>     >>>in this text. Now it is OK if you make it clear that you are only
>     >>>dealing with the network instrumentation OAM class, but you need
>     >>>to say so.
>
>     >>Network repair functions such as Fast Reroute (FRR) and
>     protection switching, which are often trigger by >>OAM protocols,
>     are also out of the scope of this document.
>
>     >That is a cop out. You need to deal this in terms of the various
>     definitions of OAM. Particularly as you >talk about the ITU
>     definitions of OAM.
>
>     I am not sure I understand "as you talk about the ITU definitions
>     of OAM". In an older version of this document there was an
>     overview of some of the ITU OAM mechanisms, but we were asked not
>     to survey non-IETF protocols in this document, so we just briefly
>     mention ITU related issues whenever it is necessary.
>     Do you mean section "2.2.7 Failures"?
>
>     Regards,
>
>     Tal.
>
>     *From:*Stewart Bryant [mailto:stbryant@cisco.com]
>     *Sent:* Tuesday, September 17, 2013 4:31 PM
>     *To:* Tal Mizrahi
>     *Cc:* nurit.sprecher@nsn.com <mailto:nurit.sprecher@nsn.com>;
>     wyaacov@gmail.com <mailto:wyaacov@gmail.com>;
>     ops-ads@tools.ietf.org <mailto:ops-ads@tools.ietf.org>; Adrian
>     Farrel; Benoit Claise; joel jaeggli;
>     draft-ietf-opsawg-oam-overview@tools.ietf.org
>     <mailto:draft-ietf-opsawg-oam-overview@tools.ietf.org>
>     *Subject:* Re: Mail regarding draft-ietf-opsawg-oam-overview
>
>     On 16/09/2013 23:07, Tal Mizrahi wrote:
>
>         Hi Stewart,
>
>         Thanks. We appreciate your comments, and hope to publish this
>         document soon.
>
>         Following your comments I am attaching an updated draft in
>         which we tried to resolve the comments you sent, with the
>         exception of the comments I am responding to below.
>
>         We intend to work hard to resolve all the pending comments and
>         hopefully publish this document soon.
>
>         If you have any comments about the updated draft, we will be
>         more than happy.
>
>         >Related to the above something that the RTG Reviewer brought up
>
>         >before was the issue of connection oriented vs connectionless
>
>         >paths. I think that you have responded by deleting all references
>
>         >to this, but in reading the draft I think that there really needs to
>
>         >be a discussion on CO vs CL and P2P vs P2MP vs MP2MP since
>
>         >these all have a major impact on what you need from an OAM
>
>         >and how you design the OAM. Indeed many of the differences
>
>         >in OAM design stem from these three network differences.
>
>         As you point out, there was some text about this in previous
>         versions of the document, but the RTG reviewer did not agree
>         with this text. We believed that it would be best to remove
>         this text, but now if we bring it back it may be controversial
>         again. Sorry, but I am running out of ideas here.
>
>         If you could help us out and provide some text here, that
>         would be great.
>
>
>     This was the comment:
>
>     3.   OAM in connectionless vs. connection-oriented networks:
>
>       
>
>     a. (2a) above suggests that OAM is applicable only
>
>     to connection-oriented networks (if you do not have
>
>     connections, connection problems do not exist by definition)
>
>       
>
>     b. At  the same time, the draft discusses ICMP Ping
>
>     (Section 4.1) operating in connectionless IP networks,
>
>     and Ethernet OAM (Sections  4.7 and 4.8) operating
>
>     in connectionless Ethernet networks.
>
>       
>
>       The authors should define the scope of OAM explicitly
>
>     and clearly - and then remove the sections dealing with
>
>     protocols and mechanisms that happen to be out of this
>
>     scope. In particular, explaining the relationship of
>
>     each specific defect to a specific networking plane.
>
>
>     I think that you need at  a section describing the
>     CL vs CO issues, noting that a Session is a type of
>     CO environment, noting  what is easy and what
>     is difficult in each case and noting the approaches used.
>
>
>     >I found your definition of "OAM Function" quite confusing - are
>
>     >you defining the function of OAM or the definition of an OAM function.
>
>     >I think that was looking for some text of the form "An OAM function
>     is...."
>
>     Indeed, a couple of lines later you will find the text "OAM
>     functions are the atomic building blocks of OAM, where each
>     function defines an OAM capability."
>
>     I gave this specific item in the document more thought than one
>     would expect, and here is what I came up with:
>
>     The term "OAM function" is pretty self-explanatory, and I cannot
>     think of a one-sentence definition that clarifies it more than the
>     two words "OAM function". Hence, we refer to it as an "atomic
>     building block", such that OAM **is defined** by the set of OAM
>     functions, and not vice versa. That is why I found it most
>     suitable to quote the OAM definition from the ATM Forum glossary
>     which says that "OAM is a group of functions that...".
>
>
>     That text does not work either.
>
>     Are you defining the function of OAM, or an OAM function?
>
>
>     >"The Data Plane is typically described as the hardware and software
>
>     >components responsible for receiving a packet..."
>
>     >There needs to be something about sending packets!
>
>     Indeed, the rest of the sentence continues with "...and forwarding
>     the packet out through the appropriate outgoing interface".
>
>     Again, I put quite a bit of effort into looking for the right
>     definitions of 'data plane' and 'control plane'. These terms are
>     so commonly used that nobody even thinks about defining them. I
>     finally found and quoted this definition from RFC 6192, which is
>     based on IETF consensus (I hate to use the IETF consensus card,
>     but it is what it is).
>
>     I really do not think that is a productive approach to the problem
>     at hand.
>
>     A document only has consensus in its own context.
>
>     I just grepped rfc6192 and it only has one instance of the term
>     "data" and that is the prefix of "datagram".
>
>     So that's not the right reference, and even if it were a suitable
>     reference, the title might explain why it does not talk about sending.
>
>     So you need to find a suitable definition for DP.
>
>
>     >"The Control Plane, as described in [Cont], is generally described as
>
>     >the hardware and software components for handling packets destined to
>
>     >the device itself as well as building and sending packets originated
>
>     >locally on the device."
>
>     >Do you mean the OAM control plane, or the network control plane.
>     This is
>
>     >certainly not the definition of the network control plane.
>
>     This definition refers to the network control plane, and once
>     again, is based on RFC 6192. I don't want to use the IETF
>     consensus card again, but I am certainly open to other suggestions
>     (hoping that this doesn't open a whole new thread/DISCUSS ...).
>
>     I think that you need to start by reading and answering my question.
>
>     Looking at the changes;
>
>     and a devolved application specific control plane function
>
>     What is one of those?
>
>
>     Network repair functions such as Fast Reroute (FRR) and protection
>     switching, which are often trigger by OAM protocols, are also out
>     of the scope of this document.
>
>     That is a cop out. You need to deal this in terms of the various
>     definitions of OAM. Particularly as you talk about the ITU
>     definitions of OAM.
>
>     Paris Traceroute is an extension to Traceroute that discovers all
>     the available paths from A to B by scanning different values of
>     header fields (such as UDP ports) in the probe packets.
>
>     Really? maybe you mean "attempts to discover"?
>
>     Conversely, MPLS-TP OAM does not use ECMP
>
>     It is MPLS-TP that does not support ECMP
>
>
>     Thanks,
>
>     Tal.
>
>     *From:*Stewart Bryant [mailto:stbryant@cisco.com]
>     *Sent:* Monday, September 16, 2013 6:13 PM
>     *To:* draft-ietf-opsawg-oam-overview@tools.ietf.org
>     <mailto:draft-ietf-opsawg-oam-overview@tools.ietf.org>
>     *Cc:* ops-ads@tools.ietf.org <mailto:ops-ads@tools.ietf.org>;
>     Adrian Farrel
>     *Subject:* Mail regarding draft-ietf-opsawg-oam-overview
>
>     As requested I have taken a look at this draft, and it is much
>     improved.
>
>     There are however a few things that still need be looked at. Please
>     see below.
>
>     A note to the responsible AD - what are your plans for this document
>     and what is it state? If I look at the draft, I see I hold a
>     discuss on it
>     but if I look at my discuss list it does not show.
>
>     =======
>
>     Something I did not see, but which I found very useful in
>     understanding
>     OAM is to consider it as providing two functions, and instrumentation
>     function, and a devolved application specific control plane function.
>     FRR is, at least within the ITU definition and OAM function. There
>     is BTW no discussion of the network repair class of OAM function
>     in this text. Now it is OK if you make it clear that you are only
>     dealing with the network instrumentation OAM class, but you need
>     to say so.
>
>     =======
>     It would really help the reader if you sorted the references, I spent
>     quite a while hunting through the paper copy I used to review the
>     text
>     to find a couple of references.
>
>     =======
>     " OAM typically has a multi-layer architecture; each transport
>     technology
>     has its own OAM mechanisms"
>
>     I think that networks have the multi-layer arch, not the OAM
>
>     =======
>     A major topic that you have not addressed is ECMP which although
>     addressed at some complexity in MPLS is not addressed in IP and
>     can lead to false negatives. This is important in a number
>     of dimensions, not the least of which is fate sharing.
>
>     Related to the above something that the RTG Reviewer brought up
>     before was the issue of connection oriented vs connectionless
>     paths. I think that you have responded by deleting all references
>     to this, but in reading the draft I think that there really needs to
>     be a discussion on CO vs CL and P2P vs P2MP vs MP2MP since
>     these all have a major impact on what you need from an OAM
>     and how you design the OAM. Indeed many of the differences
>     in OAM design stem from these three network differences.
>
>     It might also be worth some text somewhere on the hw
>     vs sw tradeoffs that impact OAM design which accounts for
>     some of the differences.
>
>     =========
>
>     I found your definition of "OAM Function" quite confusing - are
>     you defining the function of OAM or the definition of an OAM function.
>     I think that was looking for some text of the form "An OAM
>     function is...."
>
>     ========
>
>     "The Data Plane is typically described as the hardware and software
>
>     components responsible for receiving a packet..."
>
>       
>
>     There needs to be something about sending packets!
>
>       
>
>     ============
>
>       
>
>     "The Control Plane, as described in [Cont], is generally described as
>
>     the hardware and software components for handling packets destined to
>
>     the device itself as well as building and sending packets originated
>
>     locally on the device."
>
>       
>
>     Do you mean the OAM control plane, or the network control plane. This is
>
>     certainly not the definition of the network control plane.
>
>       
>
>     ============
>
>       
>
>     "and hence it is imperative to have fate-sharing between OAM
>
>         traffic and the data plane traffic it monitors."
>
>       
>
>     It is a lot more complicated than that. Some elements of the
>
>     OAM need to fate share, but by no means all. Specifically
>
>     it is only required that measurement packets of some types
>
>     fate share, but there is a lot more to OAM than that.
>
>       
>
>       
>
>     ============
>
>     "take after" is slang
>
>       
>
>     ============
>
>       
>
>     "'Ping' is an abbreviation for Packet internet groper"
>
>       
>
>     I am sure that was a contrived definition, and in any case given the
>
>     common meaning of the term groper, if this were my text, I would
>
>     finesse the name.
>
>       
>
>     =============
>
>       
>
>     In IP traceroute, you really need to talk about ECMP as well as
>
>     path asymmetry.
>
>       
>
>     =============
>
>       
>
>     In the section on LSP ping/traceroute, you really need text to help the reader
>
>     understand the ECMP issue and how it gets the packet back to the sender.
>
>       
>
>     You may wish to note how this contrasts with how MPLS-TP does it.
>
>     =============
>
>       
>
>     You have some discussion on one way packet delay measurement. That really
>
>     needs some supporting text on the issue of time synchronization. In the
>
>     two way, some warning about OW != TW/2 is called for due to path asymmetry.
>
>       
>
>     ============
>
>       
>
>     In your discussion on PW OAM a reference todraft-ietf-pwe3-vccv-impl-survey-results-02  <http://datatracker.ietf.org/doc/draft-ietf-pwe3-vccv-impl-survey-results/>
>
>     may be beneficial to the reader.
>
>       
>
>     ============
>
>       
>
>     You talk about ECMP in the context of TRILL as if it is novel to TRILL
>
>     this is not the case, and indeed is consider in the case of MPLS
>
>       
>
>     ============
>
>       
>
>     - Stewart
>
>       
>
>       
>
>       
>
>       
>
>       
>
>
>
>
>     -- 
>
>     For corporate legal information go to:
>
>       
>
>     http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>       
>
>
>
>
> -- 
> For corporate legal information go to:
>   
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>   




--------------060503090806020101050605
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Dear all, <br>
    <div class="moz-forward-container"><br>
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      In agreement between OPS ADs and the WG chairs, I'm resending
      draft-ietf-opsawg-oam-overview to the WG, for further work.<br>
      This document was sent to the IESG in August 2011.<br>
      <div class="moz-cite-prefix"> <br>
        The authors received a lot of feedback (150 if I'm not
        mistaken), mainly from the directorates and the IESG.<br>
        Some of this feedback relates to basic comments, such as the
        definitions. This leads me to think that the WG has not spent
        enough time reviewing the document. <br>
        On top of that, see <a moz-do-not-send="true"
          class="moz-txt-link-freetext"
href="https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/">https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/</a>
        <br>
        Based on this ballot half the positions are held by people who
        aren't on the IESG anymore. <br>
        <br>
        This will probably arrive as a bad news, but my highest priority
        is document quality.<br>
        <br>
        Here is also some background information, outcome of the IESG
        retreat<br>
        <a moz-do-not-send="true" class="moz-txt-link-freetext"
          href="http://www.ietf.org/mail-archive/web/ietf/current/msg79194.html">http://www.ietf.org/mail-archive/web/ietf/current/msg79194.html</a><br>
        <blockquote>
          <pre wrap="">1. Send more documents back to the WG to complete the necessary changes. While the responsibility for changes has always been at the WG, the documents were still in the IESG process. The IESG felt that particularly in situations where changes are large or multiple, it would be useful to make the situation about WG ownership even clearer. We will do this by handing the document back to the WG and getting the IESG out of the loop, with the instruction that the chairs should manage the process and address the issues raised in the IETF last call and by the ADs.
</pre>
        </blockquote>
        <br>
        Regards, Benoit (OPS AD)<br>
        <br>
      </div>
      <blockquote
cite="mid:74470498B659FA4687F0B0018C19A89C01B87D50D13F@IL-MB01.marvell.com"
        type="cite">
        <meta name="Generator" content="Microsoft Word 14 (filtered
          medium)">
        <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Times New Roman \, serif";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	font-size:12.0pt;
	font-family:"Courier New";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.3in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.msoins0
	{mso-style-name:msoins;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.msoIns
	{mso-style-type:export-only;
	mso-style-name:"";
	text-decoration:underline;
	color:teal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
        <div class="WordSection1">
          <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi

              Benoit, Joel,<o:p></o:p></span></p>
          <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">We

              have done quite a bit of work on this draft lately, and I
              believe we are steadily moving towards convergence.<o:p></o:p></span></p>
          <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Following

              Stewart&#8217;s comments we have ~5 open issues, which I believe
              can be resolved with a bit of work.<o:p></o:p></span></p>
          <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Assuming

              we resolve Stewart&#8217;s comments, how would you suggest to
              proceed?<o:p></o:p></span></p>
          <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <div>
            <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,<br>
              </span><span
style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D">Tal.<o:p></o:p></span></p>
          </div>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <div>
            <div style="border:none;border-top:solid #B5C4DF
              1.0pt;padding:3.0pt 0in 0in 0in">
              <p class="MsoNormal"
                style="margin:0in;margin-bottom:.0001pt;line-height:normal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">
                  Stewart Bryant [<a moz-do-not-send="true"
                    class="moz-txt-link-freetext"
                    href="mailto:stbryant@cisco.com">mailto:stbryant@cisco.com</a>]
                  <br>
                  <b>Sent:</b> Friday, September 20, 2013 3:24 PM<br>
                  <b>To:</b> Tal Mizrahi<br>
                  <b>Cc:</b> Benoit Claise<br>
                  <b>Subject:</b> Re: Mail regarding
                  draft-ietf-opsawg-oam-overview<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          <div>
            <p class="MsoNormal">Hi Tal,<br>
              <br>
              Next week is not the greatest week, as I am quite busy,
              but we should be able to get some time morning or early
              afternoon 30th. Will this be just with you, or are you
              also inviting your co-authors?<br>
              <br>
              However, so that we do not waste our time, can I suggest
              that you first talk to your AD to see how they wishes to
              progress the draft. <br>
              <br>
              - Stewart<br>
              <br>
              <br>
              On 20/09/2013 11:59, Tal Mizrahi wrote:<o:p></o:p></p>
          </div>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi

                Stewart,</span><o:p></o:p></p>
            <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Sorry

                for nagging, but it would be great if we could have a
                short call early next week.</span><o:p></o:p></p>
            <div>
              <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,<br>
                </span><span
style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D">Tal.</span><o:p></o:p></p>
            </div>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <div>
              <div style="border:none;border-top:solid #B5C4DF
                1.0pt;padding:3.0pt 0in 0in 0in">
                <p class="MsoNormal"
                  style="margin:0in;margin-bottom:.0001pt;line-height:normal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">
                    Tal Mizrahi <br>
                    <b>Sent:</b> Wednesday, September 18, 2013 12:06 AM<br>
                    <b>To:</b> '<a moz-do-not-send="true"
                      href="mailto:stbryant@cisco.com">stbryant@cisco.com</a>'<br>
                    <b>Subject:</b> RE: Mail regarding
                    draft-ietf-opsawg-oam-overview</span><o:p></o:p></p>
              </div>
            </div>
            <p class="MsoNormal">&nbsp;<o:p></o:p></p>
            <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi

                Stewart,</span><o:p></o:p></p>
            <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks

                for your responses. </span><o:p></o:p></p>
            <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I
                am switching to unicast mode, as I think it will be more
                effective.</span><o:p></o:p></p>
            <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">In

                the next few days I am going to do some further work
                following your comments, and if it is okay with you I
                would like to do a phone/Webex 1:1 meeting with you, to
                make sure we have addressed your concerns. I think we
                can save a lot of back-and-forth emails with a short
                conversation.</span><o:p></o:p></p>
            <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Wednesday-Friday

                are a holiday in Israel, but would you be available on
                Monday morning for phone/Webex?</span><o:p></o:p></p>
            <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">In

                the meantime, just a couple of clarification questions:</span><o:p></o:p></p>
            <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal" style="margin-left:0in"><span
                class="msoins0">&gt;&gt;and a devolved application
                specific control plane function</span> <br>
              <span style="font-family:&quot;Times New Roman ,
                serif&quot;,&quot;serif&quot;">&gt;What is one of those?</span><o:p></o:p></p>
            <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Stewart,

                sorry but I could not understand the comment. Did you
                mean that we should add an example of an application
                specific control plane function?</span><o:p></o:p></p>
            <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal">&gt;&gt;&gt;FRR is, at least within the
              ITU definition and OAM function. There<br>
              &gt;&gt;&gt;is BTW no discussion of the network repair
              class of OAM function<br>
              &gt;&gt;&gt;in this text. Now it is OK if you make it
              clear that you are only<br>
              &gt;&gt;&gt;dealing with the network instrumentation OAM
              class, but you need<br>
              &gt;&gt;&gt;to say so.<o:p></o:p></p>
            <p class="MsoNormal">&gt;&gt;Network repair functions such
              as Fast Reroute (FRR) and protection switching, which are
              often trigger by &gt;&gt;OAM protocols, are also out of
              the scope of this document.<o:p></o:p></p>
            <p class="MsoNormal">&gt;That is a cop out. You need to deal
              this in terms of the various definitions of OAM.
              Particularly as you &gt;talk about the ITU definitions of
              OAM.<o:p></o:p></p>
            <p class="MsoNormal" style="margin-left:0in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I
                am not sure I understand &#8220;as you talk about the ITU
                definitions of OAM&#8221;. In an older version of this
                document there was an overview of some of the ITU OAM
                mechanisms, but we were asked not to survey non-IETF
                protocols in this document, so we just briefly mention
                ITU related issues whenever it is necessary. <br>
                Do you mean section &#8220;2.2.7 Failures&#8221;?</span><o:p></o:p></p>
            <div>
              <p class="MsoNormal"
                style="margin:0in;margin-bottom:.0001pt;line-height:normal"><span
style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
              <p class="MsoNormal"
                style="margin:0in;margin-bottom:.0001pt;line-height:normal"><span
style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D">Regards,</span><o:p></o:p></p>
              <p class="MsoNormal"
                style="margin:0in;margin-bottom:.0001pt;line-height:normal"><span
style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D">Tal.</span><o:p></o:p></p>
            </div>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <div>
              <div style="border:none;border-top:solid #B5C4DF
                1.0pt;padding:3.0pt 0in 0in 0in">
                <p class="MsoNormal"
                  style="margin:0in;margin-bottom:.0001pt;line-height:normal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">
                    Stewart Bryant [<a moz-do-not-send="true"
                      href="mailto:stbryant@cisco.com">mailto:stbryant@cisco.com</a>]
                    <br>
                    <b>Sent:</b> Tuesday, September 17, 2013 4:31 PM<br>
                    <b>To:</b> Tal Mizrahi<br>
                    <b>Cc:</b> <a moz-do-not-send="true"
                      href="mailto:nurit.sprecher@nsn.com">nurit.sprecher@nsn.com</a>;
                    <a moz-do-not-send="true"
                      href="mailto:wyaacov@gmail.com">wyaacov@gmail.com</a>;
                    <a moz-do-not-send="true"
                      href="mailto:ops-ads@tools.ietf.org">ops-ads@tools.ietf.org</a>;
                    Adrian Farrel; Benoit Claise; joel jaeggli; <a
                      moz-do-not-send="true"
                      href="mailto:draft-ietf-opsawg-oam-overview@tools.ietf.org">draft-ietf-opsawg-oam-overview@tools.ietf.org</a><br>
                    <b>Subject:</b> Re: Mail regarding
                    draft-ietf-opsawg-oam-overview</span><o:p></o:p></p>
              </div>
            </div>
            <p class="MsoNormal">&nbsp;<o:p></o:p></p>
            <div>
              <p class="MsoNormal">On 16/09/2013 23:07, Tal Mizrahi
                wrote:<o:p></o:p></p>
            </div>
            <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi

                  Stewart,</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks.

                  We appreciate your comments, and hope to publish this
                  document soon.</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Following

                  your comments I am attaching an updated draft in which
                  we tried to resolve the comments you sent, with the
                  exception of the comments I am responding to below.</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">We

                  intend to work hard to resolve all the pending
                  comments and hopefully publish this document soon.</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">If

                  you have any comments about the updated draft, we will
                  be more than happy.</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;Related

                  to the above something that the RTG Reviewer brought
                  up </span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;before

                  was the issue of connection oriented vs connectionless</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;paths.

                  I think that you have responded by deleting all
                  references</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;to

                  this, but in reading the draft I think that there
                  really needs to</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;be

                  a discussion on CO vs CL and P2P vs P2MP vs MP2MP
                  since</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;these

                  all have a major impact on what you need from an OAM</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;and

                  how you design the OAM. Indeed many of the differences</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;in

                  OAM design stem from these three network differences.</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">As

                  you point out, there was some text about this in
                  previous versions of the document, but the RTG
                  reviewer did not agree with this text. We believed
                  that it would be best to remove this text, but now if
                  we bring it back it may be controversial again. Sorry,
                  but I am running out of ideas here.</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">If

                  you could help us out and provide some text here, that
                  would be great. </span><o:p></o:p></p>
            </blockquote>
            <p class="MsoNormal"><br>
              This was the comment:<o:p></o:p></p>
            <pre>3.&nbsp;&nbsp; OAM in connectionless vs. connection-oriented networks:<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>a. (2a) above suggests that OAM is applicable only<o:p></o:p></pre>
            <pre>to connection-oriented networks (if you do not have<o:p></o:p></pre>
            <pre>connections, connection problems do not exist by definition)<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>b. At&nbsp; the same time, the draft discusses ICMP Ping<o:p></o:p></pre>
            <pre>(Section 4.1) operating in connectionless IP networks,<o:p></o:p></pre>
            <pre>and Ethernet OAM (Sections&nbsp; 4.7 and 4.8) operating<o:p></o:p></pre>
            <pre>in connectionless Ethernet networks.<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre> The authors should define the scope of OAM explicitly<o:p></o:p></pre>
            <pre>and clearly - and then remove the sections dealing with<o:p></o:p></pre>
            <pre>protocols and mechanisms that happen to be out of this<o:p></o:p></pre>
            <pre>scope. In particular, explaining the relationship of<o:p></o:p></pre>
            <pre>each specific defect to a specific networking plane.<o:p></o:p></pre>
            <p class="MsoNormal"><br>
              I think that you need at&nbsp; a section describing the <br>
              CL vs CO issues, noting that a Session is a type of<br>
              CO environment, noting&nbsp; what is easy and what<br>
              is difficult in each case and noting the approaches used.<br>
              <br>
              <br>
              <o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;I

                found your definition of "OAM Function" quite confusing
                - are</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;you

                defining the function of OAM or the definition of an OAM
                function.</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;I

                think that was looking for some text of the form "An OAM
                function is...."</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Indeed,

                a couple of lines later you will find the text &#8220;OAM
                functions are the atomic building blocks of OAM, where
                each function defines an OAM capability.&#8221;</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I
                gave this specific item in the document more thought
                than one would expect, and here is what I came up with:</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The

                term &#8220;OAM function&#8221; is pretty self-explanatory, and I
                cannot think of a one-sentence definition that clarifies
                it more than the two words &#8220;OAM function&#8221;. Hence, we
                refer to it as an &#8220;atomic building block&#8221;, such that OAM
                *<b>is defined</b>* by the set of OAM functions, and not
                vice versa. That is why I found it most suitable to
                quote the OAM definition from the ATM Forum glossary
                which says that &#8220;OAM is a group of functions that&#8230;&#8221;.</span><o:p></o:p></p>
            <p class="MsoNormal"><br>
              That text does not work either.<br>
              <br>
              Are you defining the function of OAM, or an OAM function?<br>
              <br>
              <br>
              <o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;"The

                Data Plane is typically described as the hardware and
                software</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;components

                responsible for receiving a packet..."</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;There

                needs to be something about sending packets!</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Indeed,

                the rest of the sentence continues with &#8220;&#8230;and forwarding
                the packet out through the appropriate outgoing
                interface&#8221;.</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Again,

                I put quite a bit of effort into looking for the right
                definitions of &#8216;data plane&#8217; and &#8216;control plane&#8217;. These
                terms are so commonly used that nobody even thinks about
                defining them. I finally found and quoted this
                definition from RFC 6192, which is based on IETF
                consensus (I hate to use the IETF consensus card, but it
                is what it is).</span><o:p></o:p></p>
            <p class="MsoNormal">I really do not think that is a
              productive approach to the problem at hand.<br>
              <br>
              A document only has consensus in its own context.<br>
              <br>
              I just grepped rfc6192 and it only has one instance of the
              term "data" and that is the prefix of "datagram".<br>
              <br>
              So that's not the right reference, and even if it were a
              suitable reference, the title might explain why it does
              not talk about sending.<br>
              <br>
              So you need to find a suitable definition for DP.<br>
              <br>
              <br>
              <o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;"The

                Control Plane, as described in [Cont], is generally
                described as</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;the

                hardware and software components for handling packets
                destined to</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;the

                device itself as well as building and sending packets
                originated</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;locally

                on the device."</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;Do

                you mean the OAM control plane, or the network control
                plane. This is </span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;certainly

                not the definition of the network control plane.</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">This

                definition refers to the network control plane, and once
                again, is based on RFC 6192. I don&#8217;t want to use the
                IETF consensus card again, but I am certainly open to
                other suggestions (hoping that this doesn&#8217;t open a whole
                new thread/DISCUSS &#8230;).</span><o:p></o:p></p>
            <p class="MsoNormal"
              style="margin-left:0in;line-height:normal">I think that
              you need to start by reading and answering my question.<br>
              <br>
              Looking at the changes;<br>
              <br>
              <span class="msoins0"><span class="msoIns"><ins
                    cite="mailto:Tal%20Mizrahi"
                    datetime="2013-09-17T00:59">and a devolved
                    application specific control plane function</ins></span></span>
              <br>
              <span style="font-family:&quot;Times New Roman ,
                serif&quot;,&quot;serif&quot;"><br>
                What is one of those?<br>
                <br>
                <br>
              </span><o:p></o:p></p>
            <p class="MsoNormal"><span class="msoIns"><ins
                  cite="mailto:Tal%20Mizrahi"
                  datetime="2013-09-17T00:59">Network repair functions
                  such as Fast Reroute (FRR) and protection switching,
                  which are often trigger by OAM protocols, are also out
                  of the scope of this document.</ins></span><o:p></o:p></p>
            <p class="MsoNormal">That is a cop out. You need to deal
              this in terms of the various definitions of OAM.
              Particularly as you talk about the ITU definitions of OAM.<o:p></o:p></p>
            <p class="MsoNormal"><span class="msoIns"><ins
                  cite="mailto:Tal%20Mizrahi"
                  datetime="2013-09-17T00:59">Paris Traceroute is an
                  extension to Traceroute that discovers all the
                  available paths from A to B by scanning different
                  values of header fields (such as UDP ports) in the
                  probe packets.</ins></span><o:p></o:p></p>
            <p class="MsoNormal"
              style="margin-left:0in;line-height:normal"><span
                style="font-family:&quot;Times New Roman ,
                serif&quot;,&quot;serif&quot;">Really? maybe you mean
                "attempts to discover"? </span><o:p></o:p></p>
            <p class="MsoNormal"
              style="margin-left:0in;line-height:normal"><span
                class="msoIns"><ins cite="mailto:Tal%20Mizrahi"
                  datetime="2013-09-17T00:59">Conversely, MPLS-TP OAM
                  does not use ECMP</ins></span><span
                style="font-family:&quot;Times New Roman ,
                serif&quot;,&quot;serif&quot;"> <br>
                <br>
                It is MPLS-TP that does not support ECMP<br>
                <br>
                <br>
              </span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,

              </span><o:p></o:p></p>
            <div>
              <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D">Tal.</span><o:p></o:p></p>
            </div>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
            <div>
              <div style="border:none;border-top:solid #B5C4DF
                1.0pt;padding:3.0pt 0in 0in 0in">
                <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">
                    Stewart Bryant [<a moz-do-not-send="true"
                      href="mailto:stbryant@cisco.com">mailto:stbryant@cisco.com</a>]
                    <br>
                    <b>Sent:</b> Monday, September 16, 2013 6:13 PM<br>
                    <b>To:</b> <a moz-do-not-send="true"
                      href="mailto:draft-ietf-opsawg-oam-overview@tools.ietf.org">draft-ietf-opsawg-oam-overview@tools.ietf.org</a><br>
                    <b>Cc:</b> <a moz-do-not-send="true"
                      href="mailto:ops-ads@tools.ietf.org">ops-ads@tools.ietf.org</a>;
                    Adrian Farrel<br>
                    <b>Subject:</b> Mail regarding
                    draft-ietf-opsawg-oam-overview</span><o:p></o:p></p>
              </div>
            </div>
            <p class="MsoNormal">&nbsp;<o:p></o:p></p>
            <p class="MsoNormal">As requested I have taken a look at
              this draft, and it is much improved.<br>
              <br>
              There are however a few things that still need be looked
              at. Please<br>
              see below.<br>
              <br>
              A note to the responsible AD - what are your plans for
              this document<br>
              and what is it state? If I look at the draft, I see I hold
              a discuss on it<br>
              but if I look at my discuss list it does not show.<br>
              <br>
              =======<br>
              <br>
              Something I did not see, but which I found very useful in
              understanding<br>
              OAM is to consider it as providing two functions, and
              instrumentation<br>
              function, and a devolved application specific control
              plane function.<br>
              FRR is, at least within the ITU definition and OAM
              function. There<br>
              is BTW no discussion of the network repair class of OAM
              function<br>
              in this text. Now it is OK if you make it clear that you
              are only<br>
              dealing with the network instrumentation OAM class, but
              you need<br>
              to say so.<br>
              <br>
              =======<br>
              It would really help the reader if you sorted the
              references, I spent<br>
              quite a while hunting through the paper copy I used to
              review the text <br>
              to find a couple of references.<br>
              <br>
              =======<br>
              " OAM typically has a multi-layer architecture; each
              transport technology <br>
              has its own OAM mechanisms"<br>
              <br>
              I think that networks have the multi-layer arch, not the
              OAM<br>
              <br>
              =======<br>
              A major topic that you have not addressed is ECMP which
              although<br>
              addressed at some complexity in MPLS is not addressed in
              IP and<br>
              can lead to false negatives. This is important in a number<br>
              of dimensions, not the least of which is fate sharing.<br>
              <br>
              Related to the above something that the RTG Reviewer
              brought up <br>
              before was the issue of connection oriented vs
              connectionless<br>
              paths. I think that you have responded by deleting all
              references<br>
              to this, but in reading the draft I think that there
              really needs to<br>
              be a discussion on CO vs CL and P2P vs P2MP vs MP2MP since<br>
              these all have a major impact on what you need from an OAM<br>
              and how you design the OAM. Indeed many of the differences<br>
              in OAM design stem from these three network differences.<br>
              <br>
              It might also be worth some text somewhere on the hw<br>
              vs sw tradeoffs that impact OAM design which accounts for<br>
              some of the differences.<br>
              <br>
              =========<br>
              <br>
              I found your definition of "OAM Function" quite confusing
              - are<br>
              you defining the function of OAM or the definition of an
              OAM function.<br>
              I think that was looking for some text of the form "An OAM
              function is...."<br>
              <br>
              ========<o:p></o:p></p>
            <pre>"The Data Plane is typically described as the hardware and software<o:p></o:p></pre>
            <pre>components responsible for receiving a packet..."<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>There needs to be something about sending packets!<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>============<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>"The Control Plane, as described in [Cont], is generally described as<o:p></o:p></pre>
            <pre>the hardware and software components for handling packets destined to<o:p></o:p></pre>
            <pre>the device itself as well as building and sending packets originated<o:p></o:p></pre>
            <pre>locally on the device."<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>Do you mean the OAM control plane, or the network control plane. This is <o:p></o:p></pre>
            <pre>certainly not the definition of the network control plane.<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>============<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>"and hence it is imperative to have fate-sharing between OAM<o:p></o:p></pre>
            <pre>&nbsp;&nbsp; traffic and the data plane traffic it monitors."<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>It is a lot more complicated than that. Some elements of the <o:p></o:p></pre>
            <pre>OAM need to fate share, but by no means all. Specifically<o:p></o:p></pre>
            <pre>it is only required that measurement packets of some types<o:p></o:p></pre>
            <pre>fate share, but there is a lot more to OAM than that.<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>============<o:p></o:p></pre>
            <pre>"take after" is slang<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>============<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>"'Ping' is an abbreviation for Packet internet groper"<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>I am sure that was a contrived definition, and in any case given the <o:p></o:p></pre>
            <pre>common meaning of the term groper, if this were my text, I would <o:p></o:p></pre>
            <pre>finesse the name.<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>=============<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>In IP traceroute, you really need to talk about ECMP as well as <o:p></o:p></pre>
            <pre>path asymmetry.<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>=============<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>In the section on LSP ping/traceroute, you really need text to help the reader<o:p></o:p></pre>
            <pre>understand the ECMP issue and how it gets the packet back to the sender.<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>You may wish to note how this contrasts with how MPLS-TP does it.<o:p></o:p></pre>
            <pre>=============<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>You have some discussion on one way packet delay measurement. That really<o:p></o:p></pre>
            <pre>needs some supporting text on the issue of time synchronization. In the <o:p></o:p></pre>
            <pre>two way, some warning about OW != TW/2 is called for due to path asymmetry.<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>============<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>In your discussion on PW OAM a reference to <a moz-do-not-send="true" href="http://datatracker.ietf.org/doc/draft-ietf-pwe3-vccv-impl-survey-results/">draft-ietf-pwe3-vccv-impl-survey-results-02</a><o:p></o:p></pre>
            <pre>may be beneficial to the reader.<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>============<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>You talk about ECMP in the context of TRILL as if it is novel to TRILL<o:p></o:p></pre>
            <pre>this is not the case, and indeed is consider in the case of MPLS<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>============<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>- Stewart<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <p class="MsoNormal">&nbsp;<o:p></o:p></p>
            <p class="MsoNormal"
              style="margin-left:0in;line-height:normal"><span
                style="font-family:&quot;Times New Roman ,
                serif&quot;,&quot;serif&quot;"><br>
                <br>
                <br>
              </span><o:p></o:p></p>
            <pre>-- <o:p></o:p></pre>
            <pre>For corporate legal information go to:<o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
            <pre><a moz-do-not-send="true" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a><o:p></o:p></pre>
            <pre>&nbsp;<o:p></o:p></pre>
          </blockquote>
          <p class="MsoNormal"
            style="margin:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;"><br>
              <br>
              <br>
              <o:p></o:p></span></p>
          <pre>-- <o:p></o:p></pre>
          <pre>For corporate legal information go to:<o:p></o:p></pre>
          <pre><o:p>&nbsp;</o:p></pre>
          <pre><a moz-do-not-send="true" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a><o:p></o:p></pre>
          <pre><o:p>&nbsp;</o:p></pre>
        </div>
      </blockquote>
      <br>
      <br>
    </div>
    <br>
  </body>
</html>

--------------060503090806020101050605--

From bclaise@cisco.com  Mon Sep 23 09:14:03 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A7ED21F9FA7 for <opsawg@ietfa.amsl.com>; Mon, 23 Sep 2013 09:14:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.589
X-Spam-Level: 
X-Spam-Status: No, score=-6.589 tagged_above=-999 required=5 tests=[AWL=4.010,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 iOKoQKPPC2Cr for <opsawg@ietfa.amsl.com>; Mon, 23 Sep 2013 09:13:56 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id BCE2D21F9F5B for <opsawg@ietf.org>; Mon, 23 Sep 2013 09:13:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1725; q=dns/txt; s=iport; t=1379952836; x=1381162436; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=XRXupT+eXFMz/Qwc8Hde/u53m3igQHl4b8+jKfNOJdQ=; b=O6srzJyybc9LGpqpT+RMaSprF3pqDAWCLK0GScWhuWTPhfr0iQmGqAVU ulS5W1reK+v7a2QcIxy0sIfvZPbbpAAQxn3uQLiKWPOgnh7WWlX7ziOIv VB9QO0uQGB+VDXXVZMTqMQEt1RsaRc1TAeMGRUFXs+LQ3NUQZ0OBlYZb2 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAG5nQFKrRDoI/2dsb2JhbABPCoMHOME5SoEiFnSCJQEBAQQBAQE1NgoBEAsSBgkWDwkDAgECARUiDgYNAQUCAQGIAA27QY4igUMHhB4Dl3yBL4UDi0WDJjo
X-IronPort-AV: E=Sophos;i="4.90,963,1371081600"; d="scan'208";a="90220890"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 23 Sep 2013 16:13:51 +0000
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r8NGDnd5012482; Mon, 23 Sep 2013 16:13:50 GMT
Message-ID: <524068BD.2030500@cisco.com>
Date: Mon, 23 Sep 2013 18:13:49 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Andrew Feren <andrewf@plixer.com>
References: <523AD964.8060602@gmail.com> <20130919120719.GA554@elstar.local> <523AF484.3070006@gmail.com> <523AFE0D.1030806@plixer.com>
In-Reply-To: <523AFE0D.1030806@plixer.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] SYSLOG architectural issue
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Sep 2013 16:14:03 -0000

On 19/09/2013 15:37, Andrew Feren wrote:
> On 09/19/2013 08:56 AM, Tom Taylor wrote:
>> On 19/09/2013 8:07 AM, Juergen Schoenwaelder wrote:
>>> On Thu, Sep 19, 2013 at 07:00:52AM -0400, Tom Taylor wrote:
>>>> In Behave, we are dealing with a potential logging architecture
>>>> where Device A generates the content but exports it in the form of
>>>> IPFIX records. Device B reformats the content into SYSLOG event
>>>> reports.
>>>>
>> ...
>>> I would have to dig deeper into IPFIX to understand whether you can
>>> always find out the hostname of the originator (since there might be
>>> mediators involved as well) or whether there is another reliable way
>>> to identify an IPFIX exporter.
>>>
>>> /js
>>>
>> [PTT] Good point about IPFIX. RFC 5102 defines exporter IP address
>> fields, but not exporter name.
> I think the not yet assigned "originalExporterIPv4Address" in
> draft-ietf-ipfix-mediation-protocol may be closer to what you are
> looking for.
Yes, see 
http://tools.ietf.org/html/draft-ietf-ipfix-mediation-protocol-06#section-5

Regards, Benoit
> Although that draft also has no originalExporterName
> defined.  Perhaps some name equivalents should be requested.
>
> FWIW very recently 7012 obsoleted 5102 and  "The IANA "IPFIX Information
> Elements" registry [IANA-IPFIX] is the current complete reference for
> IPFIX Information Elements."  Still no exporterName element though.  :-)
>
> As to the original question I think it is much more useful if HOSTNAME
> is Device A (the original source of the log)
>
> -Andrew
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
> .
>


From dbharrington@comcast.net  Thu Sep 26 07:26:49 2013
Return-Path: <dbharrington@comcast.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37FC011E80D2 for <opsawg@ietfa.amsl.com>; Thu, 26 Sep 2013 07:26:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.093
X-Spam-Level: **
X-Spam-Status: No, score=2.093 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  J_CHICKENPOX_31=0.6, RDNS_NONE=0.1]
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 N-7FFJa4YEWL for <opsawg@ietfa.amsl.com>; Thu, 26 Sep 2013 07:26:44 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id 6278E21F963F for <opsawg@ietf.org>; Thu, 26 Sep 2013 07:26:44 -0700 (PDT)
Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by qmta12.westchester.pa.mail.comcast.net with comcast id Vnc91m0030QuhwU5CqSjNc; Thu, 26 Sep 2013 14:26:43 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta02.westchester.pa.mail.comcast.net with comcast id VqSj1m00d2yZEBF3NqSjeD; Thu, 26 Sep 2013 14:26:43 +0000
From: "David Harrington" <dbharrington@comcast.net>
To: <opsawg@ietf.org>
Date: Thu, 26 Sep 2013 10:26:41 -0400
Message-ID: <009001cebac4$6b8ef390$42acdab0$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac66tzPY3aNzZIATTfCsFa1wgLaJ9A==
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1380205603; bh=Gb7WhdGnvnTrMWZdrxvRekFC9M1Zn/B4Eim7X9SnECs=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=g6ijviydAz95HZTSeudDfN6Ih0sQtIII4XKI7o9vsz3Qb/GEzSMGlKjLr0q3qnr52 8PVL+LcC0/TAEWHw3ufdpUMqBJLFILActa7E24p9qtIkWRDoq+yzMfrugpsJ4rYl9T /3ZoovQgr8wH9vbIss9CJrY/iURPfVDZVFQSvRYFj2CzkAwZynABS6x3nQaUcJ05bl a3rqoRwsNqs3lkP5AC6zzn41mmfIqIuDXVZ80fF6i8yrKqmi3T2QzlySHQsYfRX4mD zdmrxtNRHKxCNqLqkyAXgdUZQcMZw1/qO7RcZTVOxEntxtl8NPhJsb95I+b5gDDhNX RhiW8YqfNi5KA==
Subject: [OPSAWG] quick review of draft-sdanda-localauth-mib-00
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2013 14:26:49 -0000

Hi,

I spotted this document announcement and thought I'd take a quick look. I
have some comments.

--- Technical comments ---

1) I have a concern about making authenticated usernames accessible via a
MIB. This would be very valuable information to an attacker.
Most login mechanisms requiring a username/password pair don't identify when
the username matches but the password doesn't, to avoid giving an attacker
an indication they found a valid username. 
The Security Considerations section has only boilerplate text, with no real
discussion of the security vulnerabilities from publishing such
authentication information in a MIB. 

The Security Considerations section doesn't follow the guidelines described
at https://svn.tools.ietf.org/area/ops/trac/wiki/mib-security.
The MIB module contains information that is potentially sensitive, and those
tables and objects should be listed with a description of why they are
sensitive.

The need for a standards-track module for locally authenticated users is
described in one or two sentences. I think the need should be justified with
discussion of applicable environments and use cases.

I think this is the single most important point in my comments. All the rest
of my comments are immaterial if the need of such a standards-track MIB
module cannot be justified.

2) Terminology (section 3) adopts the definitions from an Experimental
document [RFC2903] "Generic AAA Architecture" . This document was written by
an IRTF WG. I am not aware that this document and its definitions and
mechanisms have been adopted by the IETF. It is Experimental and not an IETF
standards-track document. 
draft-sdanda-localauth-mib has an Intended Status of standards track. This
normative dependence on an Experimental draft might be problematic. It would
be helpful to at least identify which terminology from RFC2903 is adopted by
this document. That way, eaders/reviewers might be able to recommend a
different document to use for terminology.

3) For compatibility with RFC4181 " Guidelines for Authors and Reviewers of
MIB Documents", Appendix C, I recommend naming the module "LOCAL-AUTH-MIB",
and using an object naming prefix of localAuth rather than lau. This would
also help object name expansions such as lauUserName =>
localAuthUserUserName.

4) Part of the description of this module states " it is useful collect
Authentication logs at the network element". Logging has some issues
associated with it, such as privacy and the relation to wiretapping
[RFC2804], and this document doesn't touch upon those issues. If the primary
use case is for logging, it would be good to include such a discussion, or
to mention the issues and point to other documents that include discussion
of the issues. Such discussions have been had in the syslog WG, and are
currently being discussed in the behave WG regarding CGN logging.

5) I think this document could use a good RFC4181 review by the authors. On
quick look, I see some usages I would question, such as 
5a) lauUserLoginSuccessCount OBJECT-TYPE
       SYNTAX          Unsigned32
       MAX-ACCESS      read-only
       STATUS          current
       DESCRIPTION
           "This object indicates the number of times, the user
           logged-in successfully."
       ::= { lauUserEntry 6 }

If this is counting, why not use a counter32?

5b) To make a standards-rack module useful across vendors/models, etc.,
descriptions should describe or recommend what information should be
included in a field.
lauUserDescription OBJECT-TYPE
       SYNTAX          OCTET STRING
       MAX-ACCESS      read-only
       STATUS          current
       DESCRIPTION
           "This object indicates the description of the local user."
       ::= { lauUserEntry 12 }

So is this where we should put descriptions of the user like ugly,
attractive, tall, short, fat, skinny. And so on? ;-)
What type of information should operators put into this field?
How should an NMS or operator expect to use the information found in this
field?
(and if it isn't useable by an NMS or operator, why are we publishing it in
a MIB?)

5c) lauUserPasswordLifetime OBJECT-TYPE
       SYNTAX          Unsigned32
       MAX-ACCESS      read-only
       STATUS          current
       DESCRIPTION
           "This object indicates the expiry duration of the
           password of the local user."
       ::= { lauUserEntry 13 }

Are implementers free to choose the UNITS? Or should this be standardized?

--- Editorial comments ---

1) This draft could use a good review for its English. Some of the sentences
are difficult to understand.

2) " Comments should be made directly to the WSPA mailing list at
opsawg@ietf.org." - what is the WSPA mailing list? I don't think
opsawg@ietf.org is the WSPA mailing list.

3) The description clause of the MODULE-IDENTITY includes a GLOSSARY; this
doesn't seem the right place for a glossary. The glossary here contains only
two terms, but the description also uses terms like SSH and dot1x. 


David Harrington
dbharrington@comcast.net
+1-603-828-1401



From melinda.shore@gmail.com  Thu Sep 26 19:31:58 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 917C521E80BD for <opsawg@ietfa.amsl.com>; Thu, 26 Sep 2013 19:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.528
X-Spam-Level: 
X-Spam-Status: No, score=-2.528 tagged_above=-999 required=5 tests=[AWL=0.071,  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 hN09lVxmzudQ for <opsawg@ietfa.amsl.com>; Thu, 26 Sep 2013 19:31:58 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 22AFE21F9CE3 for <opsawg@ietf.org>; Thu, 26 Sep 2013 19:31:58 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id kl14so2145211pab.11 for <opsawg@ietf.org>; Thu, 26 Sep 2013 19:31:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=DktVzNw6U7YeC+/VNX18lRLTFRsx6ahVr12PwsSlISM=; b=bvN1V5BpZxS0D8Es+c06t51kQqTu9MUbM0LIiQsj2qQq2TWD8isDZsvCTuTcg4Ksvo ozgNMlMNOVa39MePfOyAoRyC+j0hkGNHSOioUBAIl8F55tn8qMs6lOSLIIlS+/6GIZeK RMJZyMPlQiMWicJxyjtu58WXuR1+ci1CRsRsePL8SINHxytfWymA7Dz6DXGtl9vymfEJ UU+0obFWB3Fy45B/N5tEAiUOCL16ldr7RUks7vBoM7mR873xZh1y2t1Qswca12XUWIsU 9ldYD/vDfcQDi1IEKexPfPLjcQufE/jvKdirSJZRoqplA0UkNSKo1Z3oEW+0yOGIV5kL hQ8g==
X-Received: by 10.68.26.202 with SMTP id n10mr4508241pbg.97.1380249115737; Thu, 26 Sep 2013 19:31:55 -0700 (PDT)
Received: from spandex.local (63-140-95-123.dynamic.dsl.acsalaska.net. [63.140.95.123]) by mx.google.com with ESMTPSA id aq1sm5336832pbc.9.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 26 Sep 2013 19:31:54 -0700 (PDT)
Message-ID: <5244EE18.2090401@gmail.com>
Date: Thu, 26 Sep 2013 18:31:52 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: "opsawg@ietf.org" <opsawg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [OPSAWG] IETF 88 planning
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2013 02:31:58 -0000

With IETF 88 lurching into view many of you are starting to
think about how to get time on the agenda in Vancouver.
This is a reminder that the purpose of meetings is face-to-face
discussion of issues that haven't been able to make progress on the
mailing list, and to progress deliverables.  The IETF is somewhat
different from other standards bodies in that meeting time is generally
not used for presentation of new material, and that the work of the
organization is primarily done via working group mailing lists.  The
most reliable way to get time on a meeting agenda is to have a lively
discussion on the mailing list prior to the meeting.

So, if you've got a document that you're trying to progress,
now's a very good time to post to the mailing list with a
pointer to the document, a quick summary of what you're
trying to do, and what you think the open issues are or
areas that need discussion.

Thanks!

From tom.taylor.stds@gmail.com  Fri Sep 27 10:12:38 2013
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7FEE21E8100 for <opsawg@ietfa.amsl.com>; Fri, 27 Sep 2013 10:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.642
X-Spam-Level: 
X-Spam-Status: No, score=-2.642 tagged_above=-999 required=5 tests=[AWL=-0.043, 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 DaqTKyaZBuvN for <opsawg@ietfa.amsl.com>; Fri, 27 Sep 2013 10:12:38 -0700 (PDT)
Received: from mail-qa0-x233.google.com (mail-qa0-x233.google.com [IPv6:2607:f8b0:400d:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id 18CCF21E80FD for <opsawg@ietf.org>; Fri, 27 Sep 2013 10:12:37 -0700 (PDT)
Received: by mail-qa0-f51.google.com with SMTP id j15so659162qaq.3 for <opsawg@ietf.org>; Fri, 27 Sep 2013 10:12:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=OiPsmLNB8MzKy6m7YwA3GL5tbUC0ZLm+NdfnHvyQaXU=; b=Y/+kT8Zy/djsaBaPgYn72r05PRVOcG6rQk2aqXAYIYebdsxodjKbFEIFSxQmB5khHZ xYuvSS8QOybY5jeJ/LghAqgRMCHDEqI9ArmMwuTuXvI9lAGyXcfQqNGpTnQUI1W+1PI3 CRdIIntqdzmYUHRVLW+D88hpzt/Me3Xh7Lc0OjRWcSOi//HTBNEaU4f3KzL39Iyt3RFS ELP8oqd5tlst0TDQq3BgmZX4VErieBHHcLdW4mqujWksAXfkZXHdD+9WpaHMox+wDrn0 pMBaEx43Hvkr5u8WQREqwIoKPzrL1pF5EXI92AELHXEVeERyPzDTVISwTegc08VV4KJk 88tQ==
X-Received: by 10.49.3.101 with SMTP id b5mr10485278qeb.7.1380301957084; Fri, 27 Sep 2013 10:12:37 -0700 (PDT)
Received: from [192.168.1.65] (dsl-173-206-79-23.tor.primus.ca. [173.206.79.23]) by mx.google.com with ESMTPSA id w20sm20758272qax.11.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 27 Sep 2013 10:12:36 -0700 (PDT)
Message-ID: <5245BC81.3030809@gmail.com>
Date: Fri, 27 Sep 2013 13:12:33 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "opsawg@ietf.org" <opsawg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [OPSAWG] Plea for action: draft-schoenw-opsawg-nm-dhc-04
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2013 17:12:38 -0000

No I have no intention of seeking another meeting slot for this little 
document. But I do ask whether people can approve it in principle, so we 
can put through the necessary Standards Action to get the DHCP/DHCPv6 
options in place.

Again, this is about DHCP options to tell a router where to find two 
management entities, the SYSLOG Collector and the SNMP Notification 
Receiver, for use primarily in configuring mobile backhaul.

Tom Taylor

From jclarke@cisco.com  Fri Sep 27 10:23:15 2013
Return-Path: <jclarke@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FBD321F9E12 for <opsawg@ietfa.amsl.com>; Fri, 27 Sep 2013 10:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 j0GO7d9xrkJ6 for <opsawg@ietfa.amsl.com>; Fri, 27 Sep 2013 10:23:10 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id D012E21F9DA9 for <opsawg@ietf.org>; Fri, 27 Sep 2013 10:23:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1596; q=dns/txt; s=iport; t=1380302587; x=1381512187; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=N10mU3eQwrs/tc31KNWTfbE3MaDUS2AWJtYBvQFnpNM=; b=I3ilsPr1Pk2I/6MA23e6yC2fhaqBIqvV7fQgG+4Pj43ZLGGWSvkgFiEO Rt9j9AP5hm9qMIBi4KNJGUkxlupJGhKLXfXyccNvNq4s8BO13H9psrUiP exmR1E644UgXVVQXYOjw3LdEoHDxi0R4CgOvp+57io0CXMQLyayNqtZyy 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAGS+RVKtJV2d/2dsb2JhbABYA4MHwVaBHRZ0giUBAQEEOEAPAgsYCRYPCQMCAQIBCTwGAQwGAgEBiAK5awSOBIE5FxGEDwOXf5F4g0AggTU
X-IronPort-AV: E=Sophos;i="4.90,994,1371081600"; d="scan'208";a="265209319"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 27 Sep 2013 17:23:06 +0000
Received: from rtp-jclarke-8919.cisco.com (rtp-jclarke-8919.cisco.com [10.117.46.170]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r8RHN5n9024174;  Fri, 27 Sep 2013 17:23:06 GMT
Message-ID: <5245BEF9.6050907@cisco.com>
Date: Fri, 27 Sep 2013 13:23:05 -0400
From: Joe Marcus Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Tom Taylor <tom.taylor.stds@gmail.com>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <5245BC81.3030809@gmail.com>
In-Reply-To: <5245BC81.3030809@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [OPSAWG] Plea for action: draft-schoenw-opsawg-nm-dhc-04
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2013 17:23:15 -0000

On 9/27/13 1:12 PM, Tom Taylor wrote:
> No I have no intention of seeking another meeting slot for this little
> document. But I do ask whether people can approve it in principle, so we
> can put through the necessary Standards Action to get the DHCP/DHCPv6
> options in place.
>
> Again, this is about DHCP options to tell a router where to find two
> management entities, the SYSLOG Collector and the SNMP Notification
> Receiver, for use primarily in configuring mobile backhaul.

For the syslog, I have no objections.  However, I found the SNMP bit 
lacking.  Specifically, there are additional security considerations 
depending on SNMP version (plus the trap versus inform thing).  While 
this is explained in the Appendix, I started asking myself these 
questions when I read the SNMP and security consideration sections 
before getting to the appendix.

My point is that perhaps additional text is needed in the SNMP section 
that at the very least points to Appendix A for more specifics on SNMP 
version, notif type and security.  And in the security considerations, 
it would be good to speak to the fact that SNMP requires a level of 
security that must be specified externally to the DHCP offer from the 
server.

Joe

-- 
Joe Marcus Clarke, CCIE #5384,         |          |
SCJP, SCSA, SCNA, SCSECA, VCP        |||||      |||||
Distinguished Services Engineer ..:|||||||||::|||||||||:..
Phone: +1 (919) 392-2867         c i s c o  S y s t e m s
Email: jclarke@cisco.com

----------------------------------------------------------------------------

From tom.taylor.stds@gmail.com  Fri Sep 27 10:51:35 2013
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95EDD11E8110 for <opsawg@ietfa.amsl.com>; Fri, 27 Sep 2013 10:51:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.129
X-Spam-Level: 
X-Spam-Status: No, score=-3.129 tagged_above=-999 required=5 tests=[AWL=0.470,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 JDxG-eexnC99 for <opsawg@ietfa.amsl.com>; Fri, 27 Sep 2013 10:51:26 -0700 (PDT)
Received: from mail-gg0-f174.google.com (mail-gg0-f174.google.com [209.85.161.174]) by ietfa.amsl.com (Postfix) with ESMTP id 88D6011E815C for <opsawg@ietf.org>; Fri, 27 Sep 2013 10:51:21 -0700 (PDT)
Received: by mail-gg0-f174.google.com with SMTP id j5so156107ggn.19 for <opsawg@ietf.org>; Fri, 27 Sep 2013 10:51:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ft35SNWHM+hPuTlrEJL2dHM2tVdBa9UJt8OiQwlaGB0=; b=JNNL4fO/ZdFwnnKNOgJTorRHedWiMlN7fRCHWtLMWHfEQBzQ+YyxYa5fbOrbSDC+r4 obE76A5oZpHNP8TUVSR3tceNlV/5QVJ5FO7Y+eFpcuOrVx4iaaAzZcx6/7sE7dfrR/kv mPOuJ3Rgf0VChbrgEX2g+HdM2kN4+89qu9IL4TwHdbC1jN1mCWziYTbKWGbjx4KmqGHM Ikj+5wpYNLKV2xWsSlaXoyXX9sDFZgUnssFQP9O+gQ+18kEk7Eeby/Z40NZneQyecvGE FNg3fMR1I7jjsH5JuuK9B44QYjSrSX0KfYRIvzj56cI1NI34jt4Mx0I/pjalhcCamPJO L0Lg==
X-Received: by 10.236.150.193 with SMTP id z41mr2244860yhj.79.1380304265083; Fri, 27 Sep 2013 10:51:05 -0700 (PDT)
Received: from [192.168.1.65] (dsl-173-206-79-23.tor.primus.ca. [173.206.79.23]) by mx.google.com with ESMTPSA id s20sm12632197yhi.0.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 27 Sep 2013 10:51:04 -0700 (PDT)
Message-ID: <5245C586.2040300@gmail.com>
Date: Fri, 27 Sep 2013 13:51:02 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Joe Marcus Clarke <jclarke@cisco.com>
References: <5245BC81.3030809@gmail.com> <5245BEF9.6050907@cisco.com>
In-Reply-To: <5245BEF9.6050907@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] Plea for action: draft-schoenw-opsawg-nm-dhc-04
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2013 17:51:35 -0000

Thanks, will update pending other comments.

On 27/09/2013 1:23 PM, Joe Marcus Clarke wrote:
> On 9/27/13 1:12 PM, Tom Taylor wrote:
>> No I have no intention of seeking another meeting slot for this little
>> document. But I do ask whether people can approve it in principle, so we
>> can put through the necessary Standards Action to get the DHCP/DHCPv6
>> options in place.
>>
>> Again, this is about DHCP options to tell a router where to find two
>> management entities, the SYSLOG Collector and the SNMP Notification
>> Receiver, for use primarily in configuring mobile backhaul.
>
> For the syslog, I have no objections.  However, I found the SNMP bit
> lacking.  Specifically, there are additional security considerations
> depending on SNMP version (plus the trap versus inform thing).  While
> this is explained in the Appendix, I started asking myself these
> questions when I read the SNMP and security consideration sections
> before getting to the appendix.
>
> My point is that perhaps additional text is needed in the SNMP section
> that at the very least points to Appendix A for more specifics on SNMP
> version, notif type and security.  And in the security considerations,
> it would be good to speak to the fact that SNMP requires a level of
> security that must be specified externally to the DHCP offer from the
> server.
>
> Joe
>

From warren@kumari.net  Mon Sep 30 14:38:27 2013
Return-Path: <warren@kumari.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E889421F89A6 for <opsawg@ietfa.amsl.com>; Mon, 30 Sep 2013 14:38:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.457
X-Spam-Level: 
X-Spam-Status: No, score=-102.457 tagged_above=-999 required=5 tests=[AWL=0.142, 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 nlC5v0i15lht for <opsawg@ietfa.amsl.com>; Mon, 30 Sep 2013 14:38:22 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 869E121F87BB for <opsawg@ietf.org>; Mon, 30 Sep 2013 14:38:21 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.70]) by vimes.kumari.net (Postfix) with ESMTPSA id 77ECF1B401CE; Mon, 30 Sep 2013 17:38:20 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <5245BC81.3030809@gmail.com>
Date: Mon, 30 Sep 2013 17:38:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B23BF80-BB0C-4EB0-869C-FFB2605921BE@kumari.net>
References: <5245BC81.3030809@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] Plea for action: draft-schoenw-opsawg-nm-dhc-04
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Sep 2013 21:38:27 -0000

On Sep 27, 2013, at 1:12 PM, Tom Taylor <tom.taylor.stds@gmail.com> =
wrote:

> No I have no intention of seeking another meeting slot for this little =
document. But I do ask whether people can approve it in principle, so we =
can put through the necessary Standards Action to get the DHCP/DHCPv6 =
options in place.
>=20
> Again, this is about DHCP options to tell a router where to find two =
management entities, the SYSLOG Collector and the SNMP Notification =
Receiver, for use primarily in configuring mobile backhaul.

<no hats>

I must admit to being a little confused by this draft / the use case.

The draft says:
 "The Dynamic Host Configuration Protocol (DHCPv4 [RFC2131] and DHCPv6
   [RFC3315]) is a relevant tool for this purpose.  It provides a number
   of existing options to allow a node to acquire its configuration file
   and to locate key servers in the network. "

Presumably the node connects to $something and downloads a (node =
specific) config file -- why is the SYSLOG and SNMP devices not simply =
defined in the config file?=20

Or, is the intent that the nodes will all download the *same* config =
file, and then use DHCP options to provide the node specific bits?

If the latter, is [DNS, Hostname, SYSLOG, SNMP] the only things that =
differ between nodes? What about interface names / addresses / ssh keys =
/ etc?=20
I'm so not a mobile operator, so maybe I'm just not understanding what =
sorts of things these nodes do and so what sort of node specific config =
they need.

I'm not disagreeing with the concept, I'm more intrigued=85

</no hats>
W



>=20
> Tom Taylor
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>=20

--
Life is a concentration camp.  You're stuck here and there's no way out =
and you can only rage impotently against your persecutors.
                -- Woody Allen




