Re: [ncrg] Meeting Notes from Today's NCRG Call

Sheng Jiang <> Wed, 15 May 2013 09:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6F56E21F89A6 for <>; Wed, 15 May 2013 02:48:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id t+IQuFmUfiXn for <>; Wed, 15 May 2013 02:48:15 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 1971321F89A5 for <>; Wed, 15 May 2013 02:48:14 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.4-GA FastPath queued) with ESMTP id BCE19856; Wed, 15 May 2013 17:48:05 +0800 (CST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 15 May 2013 17:47:07 +0800
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 15 May 2013 17:47:08 +0800
Received: from ([]) by ([]) with mapi id 14.01.0323.007; Wed, 15 May 2013 17:47:06 +0800
From: Sheng Jiang <>
To: "Michael Behringer (mbehring)" <>, "" <>
Thread-Topic: Meeting Notes from Today's NCRG Call
Thread-Index: Ac5QtoQHlT7cKX86SVC6tqZM0LbSyQAljmFQ
Date: Wed, 15 May 2013 09:47:06 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [ncrg] Meeting Notes from Today's NCRG Call
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Network Complexity Research Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 15 May 2013 09:48:19 -0000

Hi, Michael and all,

My main concern for the current framework draft is how WG wants it end.

If the WG only wants to use the framework to be a working document, which records the WG's process, the current form seems fine. If the WG wants the document to be published as a RFC at the end, I think the current form has to be restructured. The current document looks more like a list of essay.

We need to find a way to organize these scattered idea into a single story. My suggestion is we should first try to reach consensus on a clear problem scope, or in other word, the purpose why we research network complexity. Then we can work out a story clue.

Best regards,


>-----Original Message-----
>From: [] On Behalf Of
>Michael Behringer (mbehring)
>Sent: Tuesday, May 14, 2013 11:30 PM
>Subject: [ncrg] Meeting Notes from Today's NCRG Call
>Attendees: Sheng Jiang, Xin Sun, Rana Sircar, Vladimir Marbukh, Michael
>Behringer (notes)
>Subject: Evolving the NCRG framework draft
>Brief notes:
>-	Suggestion to include metrics and tradeoffs in the framework draft; this
>was presented in Paris.
>-	draft-retana suggest more metrics, and trade-offs, these should also be
>in the framework draft.
>-	Sheng: Does cost (for example) represent a good metric?
>-	Cover the aspect of complexity: user facing? Internal, eg s/w
>-	Include text to describe the various forms (?) of complexity
>	+ Operational complexity
>	   deployment complexity; configuration complexity, trouble shooting
>	+ Network system complexity
>	  s/w complexity; h/w complexity; Protocol / algortihm complexity
>	+ Management system complexity
>	  OSS systems, etc.
>-	Intrinsic complexity of the system vs complexity from the user base?
>-	Rana: Should we limit to layer 3 and above? Or cover optical, wireless,
>etc? We may want to explain in the scope that the doc doesn't want to be
>specific to a particular solution/layer.
>-	Rana: Cost is a very good metric to measure complexity.
>-	Xin: Could improve 3.2: define different types of complexity. (operational
>complexity, s/w complexity,
>-	Vladimir: participated in a Santa Fe Complex Systems Institute workshop
>on network complexity; will point us to it. Also a recent Nature article. He
>could present to the group about these findings in Berlin.
>Next steps:
>-	propose on the list what you would like to contribute to the draft, or how
>it should be changed.
>-	set up bi-weekly calls to make progress on this.
>Thanks all for the discussion!
>ncrg mailing list