
From lars.eggert@nokia.com  Tue May  3 05:27:54 2011
Return-Path: <lars.eggert@nokia.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01B38E080E for <irtf-discuss@ietfa.amsl.com>; Tue,  3 May 2011 05:27:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.499
X-Spam-Level: 
X-Spam-Status: No, score=-103.499 tagged_above=-999 required=5 tests=[AWL=0.989, BAYES_00=-2.599, GB_I_INVITATION=-2, SARE_NETPROD=0.111, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rx397o5uvRwS for <irtf-discuss@ietfa.amsl.com>; Tue,  3 May 2011 05:27:53 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id 12EC7E0808 for <irtf-discuss@irtf.org>; Tue,  3 May 2011 05:27:53 -0700 (PDT)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da02.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p43CRohX013531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <irtf-discuss@irtf.org>; Tue, 3 May 2011 15:27:52 +0300
From: Lars Eggert <lars.eggert@nokia.com>
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.97 at fit.nokia.com
Content-Type: multipart/signed; boundary=Apple-Mail-57--299045965; protocol="application/pkcs7-signature"; micalg=sha1
Date: Tue, 3 May 2011 15:27:48 +0300
Message-Id: <EB930286-8F76-4846-8860-32C695D76B1E@nokia.com>
To: irtf-discuss@irtf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.fit.nokia.com); Tue, 03 May 2011 15:27:48 +0300 (EEST)
X-Nokia-AV: Clean
Subject: [irtf-discuss] FIVE DAYS REMAINING: Call for Nominations: Applied Networking Research Prize (ANRP)
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: anrp@isoc.org
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2011 12:27:54 -0000

--Apple-Mail-57--299045965
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


                   CALL FOR NOMINATIONS:

          APPLIED NETWORKING RESEARCH PRIZE (ANRP)


*** Apply until May 8, 2011 for the ANR Prize for IETF-81,
*** July 24-29, 2011 in Quebec City, Canada!

The Applied Networking Research Prize (ANRP) is awarded for
recent results in applied networking research that are relevant
for transitioning into shipping Internet products and related
standardization efforts. Researchers with relevant, recently
published results are encouraged to apply for this prize, which
will offer them the opportunity to present and discuss their work
with the engineers, network operators, policy makers and
scientists that participate in the Internet Engineering Task
Force (IETF) and its research arm, the Internet Research Task
Force (IRTF). Third-party nominations for this prize are also
encouraged. The goal of the Applied Networking Research Prize
(ANRP) is to recognize the best new ideas in networking, and
bring them to the IETF and IRTF especially in cases where they
would not otherwise see much exposure or discussion.

The Applied Networking Research Prize (ANRP) consists of:

  * cash prize of $500 (USD)

  * invited talk at the IRTF Open Meeting

  * travel grant to attend the week-long IETF meeting
    (airfare, hotel, registration, stipend)

  * recognition at the IETF plenary

  * invitation to related social activities

  * potential for additional travel grants to future IETF
    meetings, based on community feedback

The Applied Networking Research Prize (ANRP) will be awarded
three times per year, in conjunction with the three annual IETF
meetings.


HOW TO APPLY

Applicants must nominate a peer-reviewed, recently-published,
original journal, conference or workshop paper. Both self
nominations (nominating one's own paper) and third-party
nominations (nominating someone else's paper) are encouraged. The
nominee must be one of the main authors of the nominated paper.

The nominated paper should provide a scientific foundation for
possible future IETF engineering work or IRTF experimentation,
analyze the behavior of Internet protocols in operational
deployments or realistic testbeds, make an important contribution
to the understanding of Internet scalability, performance,
reliability, security or capability, or otherwise be of relevance
to ongoing or future IETF or IRTF activities.

Applicants must briefly describe how the nominated paper relates
to these goals, and are encouraged to describe how presentation
of these research results will foster their transition into new
IETF engineering or IRTF experimentation, or otherwise seed new
activities that will have an impact on the real-world Internet.

The goal of the Applied Networking Research Prize (ANRP) is to
foster the transitioning of research results into real-world
benefits for the Internet. Therefore, applicants must indicate
that they (or the nominee, in case of third-party applications)
are available to attend the respective IETF meeting in person and
in its entirety.

Applications must include:

  * the name and email address of the nominee

  * a reference to the published nominated paper

  * a PDF copy of the nominated paper

  * a statement that describes how the nominated paper
    fulfills the goals of the award

  * a statement that the nominee is available to attend the
    respective IETF meeting in person and in its entirety

  * a brief biography or CV of the nominee

  * optionally, any other supporting information (link to
    nominee's web site, etc.)

*** Applications are submitted by email to anrp@isoc.org. ***


SELECTION PROCESS

A small selection committee comprised of individuals
knowledgeable about the IRTF, IETF and the broader networking
research community will evaluate the submissions against these
selection criteria. The goal is to select 1-2 submissions for the
Applied Networking Research Prize (ANRP) during each application
period. All applicants will be notified by email.


IMPORTANT DATES

Applications open:      April 11, 2011
Applications close:     May 8, 2011
Notifications:          May 31, 2011
IETF-81 Meeting:        July 24-29, 2011


SPONSORS

The Applied Networking Research Prize (ANRP) is supported by the
Internet Society (ISOC), as part of its Internet Research Award
Programme, in coordination with the Internet Research Task Force
(IRTF).


--Apple-Mail-57--299045965
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMRjCCBVAw
ggQ4oAMCAQICEGxdPUZzCwUJ8KBiJwH+bYgwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMDEwMTUwMDAwMDBaFw0x
MTEwMTUyMzU5NTlaMIIBEzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9r
aWEuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwolKEyOz/NQZJJlw0x9XBS9W
wCmabdY1fXpbWSdcaJiEWhQpRzSIC/pgIwCgaUW9g3JsWioXCawyjUVeg8xR42sR690f4z+OPAUm
3jokZxsuRaGX6fuPkPQomYAGz7htUHws/8FZIU+4dciETQf4vF5ptitJ+QZCVRCTLqisj6mG/kG4
65Op3G5/YZF9F/a390LdhuRP6vdY2Y+dqm8LDa0zmENPpoE98u1pIZGqCcnskN/nNBtEPd+a4lNh
ZSGnPuL4XCUSJYR9NB7FAYBvi5N7LSWHR3fspwa5EgpXynJcsLzaLA0iGfjFOBYFxul/07edmyw4
FIXuCIkaMDUfEwIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcX
ATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIF
oDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDov
L2luZGMxZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3Js
MA0GCSqGSIb3DQEBBQUAA4IBAQAlSTzUKqa3ZouKWFQfIJ+4l/KsztPnY4Onwzt8lqAmeiFPqOmf
kLTXbXDKtC6caFadNtyHpnsmQFFKXwhe5Z9/AaVSwryu6F9992DzYLp3j8PE0DSU0wmpUXUtp+rz
TFqJRkzB8RCBoq/TPBmkMPr68qB0TkU3dbYiVIvscOt1MRkdHiwG4wKQLyCf8XRRWqmMY6lbun7g
kiEWiris5StGKRvE5+e1SrcdnoZxIKQFF7Etr+4ftClrsDQWX9nRCEjYcmz4y/deq+HU8ylBaKZE
0ZJmcnYlAaD50OYWi0ckGDnKYyeMUEtCZJSV0otm2LqyIUAu9WPv/GNHt2ntjnUaMIIG7jCCBdag
AwIBAgIQcRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAV
BgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTow
OAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5
MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g
QXV0aG9yaXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBO
ZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t
L3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJp
U2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6Zvg
SU6Lb9UB0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHs
EnMhjfXcMM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO
4YM/d/mZ//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSy
riMGZSalJ1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCC
ArUwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20w
EgYDVR0TAQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUH
AgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWdu
LmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgw
VhYJaW1hZ2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDov
L2xvZ28udmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQ
cml2YXRlTGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYD
VR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4x
HzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlT
aWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENs
YXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaE
VIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlM
JBq6WaSHO3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKv
YLMVirOVnDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDR
yxTWcVibvtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy
+kgOZY5JyNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/
wYIxggSLMIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMu
MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2Ug
YXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2Ny
aWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJ
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDUwMzEyMjc0OFowIwYJKoZIhvcNAQkE
MRYEFNir9cPhDjERQq9d3j0MB3caWECcMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AJygeQg4ursmIpHydCDnbI/8myKU/SnAAJMmPqKMZZ82AAble5z4m3IGfg2xht7BFNSkqLpZpQ9e
acmPycsV891bUdNmbpcPujpzmZnQ1FJ/e1Yi/6KaH3EV9PpUywxYJAM3PZYydHR/IRMr/nhvh2NZ
D+b3Y0z/rHVUfM/mebdFo+/U1a+ZI8wtZl+af2cpCXNVsoivPyJEu7WlLvqTHKlecM4SJZRlrzvg
qZCs+mfbBT/OCklo/KsZiKjCMEE4KQEZFDDpXgcjJQMQgF1QkAw3KmOnPQ6qGEv2lRzCeX7gidLY
rj1ZaY1s/X4V98SWfyGMjxJed8NaghUVKGHcyjMAAAAAAAA=

--Apple-Mail-57--299045965--

From leeyoung@huawei.com  Mon May  9 10:10:01 2011
Return-Path: <leeyoung@huawei.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71CD6E07D8 for <irtf-discuss@ietfa.amsl.com>; Mon,  9 May 2011 10:10:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.598
X-Spam-Level: 
X-Spam-Status: No, score=-7.598 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hyrLGo6qPt9T for <irtf-discuss@ietfa.amsl.com>; Mon,  9 May 2011 10:09:54 -0700 (PDT)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by ietfa.amsl.com (Postfix) with ESMTP id 5B06BE06C3 for <irtf-discuss@irtf.org>; Mon,  9 May 2011 10:09:42 -0700 (PDT)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKX0061SUC4IA@usaga04-in.huawei.com> for irtf-discuss@irtf.org; Mon, 09 May 2011 12:09:41 -0500 (CDT)
Received: from dfweml201-edg.china.huawei.com ([172.18.9.107]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPS id <0LKX008MYUC4ES@usaga04-in.huawei.com> for irtf-discuss@irtf.org; Mon, 09 May 2011 12:09:40 -0500 (CDT)
Received: from DFWEML401-HUB.china.huawei.com (10.193.5.101) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 09 May 2011 10:09:38 -0700
Received: from DFWEML501-MBX.china.huawei.com ([fe80::c52a:9e19:87eb:4531]) by DFWEML401-HUB.china.huawei.com ([fe80::f07f:889f:78ef:8df3%13]) with mapi id 14.01.0270.001; Mon, 09 May 2011 10:09:39 -0700
Date: Mon, 09 May 2011 17:09:38 +0000
From: Leeyoung <leeyoung@huawei.com>
X-Originating-IP: [10.192.11.164]
To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Message-id: <7AEB3D6833318045B4AE71C2C87E8E170C6152A7@DFWEML501-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_d3AeIsB4yebslbglNffG1w)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: CSO workshop
Thread-index: AcwOaGYqt5fnaqY2SWuMCCqODXu65AAAuPOA
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Mailman-Approved-At: Mon, 09 May 2011 11:28:27 -0700
Subject: [irtf-discuss] CSO workshop
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2011 17:10:01 -0000

--Boundary_(ID_d3AeIsB4yebslbglNffG1w)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hello IRTF community,

As part of a follow-up activity since the last IRTF meeting in Prague on Cross Stratum Optimization work, there will be a workshop on Cloud Computing and Cross Stratum Optimization held on June 7-8, 2011.

The workshop will be held in ETRI's facility in Daejeon, Korea.  Please see the details of this workshop below. We will look forward to your participation and contribution for this workshop.
Please contact us should you have any question on the workshop: Taesang Choi<mailto:tschoi@etri.or.kr> or Young Lee<mailto:leeyoung@huawei.com>.
Best Regards,
Taesang & Young


Call for Participation

Cloud Computing and Cross Stratum Optimization Workshop

ETRI, Daejeon, Korea,
June 7-8, 2011

Background

Cloud computing provides a variety of services allowing end-users, from individual to enterprises, to access to large pools of storage resources, computational resources and various application services.  There are many ways in which these services are provided to end-users, ranging from individual software applications (Google docs, Salesforce.com) to the allocation and use of thousands of raw computing resources geographically distributed around the world.  Data centers provide the physical and virtual infrastructure in which cloud computing applications and services are provided.

Since cloud computing and the data centers used to provide application services are distributed geographically around a network, many decisions made in the control and management of application services, such as where to instantiate another service instance or to which data center out of several a new client is assigned, can have a significant impact on the state of the network. Conversely the capabilities and state of the network can have a major impact on application performance.

Currently application decisions are made with very little or no information concerning the underlying network used to deliver those services. Hence such decisions may be sub-optimal from both application and network resource utilization, and from the achievement of quality of service objectives.  Among the top ten obstacles to the adoption of cloud computing identified according to Ambrust[1] et. al., over half have significant involvement of the network: 1. availability/business continuity; 3. data confidentiality and auditability; 4. data transfer bottlenecks; 5. performance unpredictability; 8. scaling quickly; 9. reputation fate sharing.

As more application and services are envisaged to be offered via cloud computing and data centers, it is critical to have an overall architectural model   from both the application stratum and the network stratum points of view; define key interfaces among the entities involved in cloud computing, data centers and the networks supporting them; and provide a next generation  architecture that integrate select aspects of  cloud computing, data centers, and networks to improve service continuity, performance predictability/guarantees, scalability and manageability.

Cross-stratum optimization is referred to combined optimization in the application and network stratum that aims to provide joint application/network resource optimization, responsiveness to quickly changing demands from/to application to/from network, enhanced service resilience (via cooperative recovery techniques between application and network) and quality of application experience (QoE) enhancement (via better use of existing network and application resources).

This workshop aims to explore the challenges and issues faced by cloud computing and data center integration with networks. Among the key areas of investigation to be discussed in the workshop are as follows:

*         Cloud/network integration architectures and subsystems
*         Use cases, business models and requirements for cloud/network integration
*         Control/management issues for cloud/network integration
*         Network virtualization and its impact for cloud/network integration
*         Application-aware transport network
*         Network-aware application/cloud computing
*         Joint application/network reliability and security
*         Experimental/trial experience
*         Scalability
*         Joint/shared performance and fault monitoring
*         Multi-domain issues

The goal of this workshop is to promote the research interest in cloud/network integration and to start a new research activity in the IRTF community. The workshop organizers are interested in receiving contributions that supports this goal.
Workshop Style
The workshop's main focus will be on the discussions of technical topics. Each presentation will be given about 40 minutes and 15 minutes of discussion.  Interactive discussion will be encouraged.
In order to keep the group at a manageable size, participants are required to submit a position paper as an expression of interest. The authors of accepted papers will be invited to submit power point presentations and attend the workshop although under special circumstances remote access capability via video conferencing will be provided.
Important Dates
The position papers (an abstract with no more than two pages) must be submitted by May 20th, 2011.
Position papers will be reviewed by the program organizers and an invitation to the workshop will be sent to one of the paper authors. At the latest, invitations will be distributed by May 25th, 2011.
Invited contributions (power point slides) must be submitted at latest by June 3rd, 2011.
All contributions can be submitted to: cso-workshop-prep@cccso.net<mailto:cso-workshop-prep@cccso.net>.
Workshop Technical Committee
Members of the workshop technical committee are as follows:

  *   Tae Sang Choi (ETRI)
  *   Young Lee (Huawei)
  *   Volker Hilt (Bell Labs)
  *   Kohei Shiomoto (NTT)
  *   Francisco Javier Jimenez Chico (Telefonica)
  *   Oscar de Dios Gonzalez (Telefonica)
  *   Greg Bernstein (Grotto Networking)
  *   Ning So (Verizon)
  *   Andrea Fumagalli (University of Texas, Dallas)
  *   Tae Yeon Kim (ETRI)
  *   Dan Li (Huawei)
  *   Dong Sik Yun (KT)

Workshop Logistics
This one and a half day workshop will take place on June 7-8, 2011 in ETRI facility, Daejeon, Korea:
161 Gajong-Dong, Yusong-Gu, Daejeon 305-350 Republic of Korea

l    How to get to ETRI facility from Incheon International Airport
The best way to get to ETRI from Incheon airport is by airport limousine bus.  It will take you to Daeduk Doryong bus stop which is 5 minutes away by Taxi from ETRI.  The journey will take about 3 hours from airport to bus stop.
An alternative way is to take KTX express train from Seoul train station to Daejeon train station and take taxi from it to ETRI.
l    Lodging/hotel information
Two local hotels are recommended.
Spapia Hotel: http://www.hotelspapia.com/english/index.php
Yusong Hotel: http://www.yousunghotel.com (Korean web page only)
Reservations with corporate discount rate are available.  You can contact Taesang Choi<mailto:tschoi@etri.or.kr> (email: choits@etri.re.kr<mailto:choits@etri.re.kr>; tel: +82 42 860 5628) for the reservations.
Please contact us should you have any question on the workshop: Taesang Choi<mailto:tschoi@etri.or.kr> or Young Lee<mailto:leeyoung@huawei.com>.





________________________________

[1] M. Armbrust et al., "A view of cloud computing," Communications of the ACM, vol. 53, p. 50-58, Apr. 2010.

--Boundary_(ID_d3AeIsB4yebslbglNffG1w)
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:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.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 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:offic=
e:smarttags" name=3D"country-region" /><o:SmartTagType namespaceuri=3D"urn:=
schemas-microsoft-com:office:smarttags" name=3D"City" /><o:SmartTagType nam=
espaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"place" /><=
o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PlaceName" /><o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-=
com:office:smarttags" name=3D"PlaceType" /><o:SmartTagType namespaceuri=3D"=
urn:schemas-microsoft-com:office:smarttags" name=3D"PersonName" /><!--[if !=
mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]--><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\B9D1\C740 \ACE0\B515";}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@\B9D1\C740 \ACE0\B515";}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
h1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	page-break-after:avoid;
	mso-list:l3 level1 lfo3;
	font-size:16.0pt;
	font-family:Arial;}
p.MsoFootnoteText, li.MsoFootnoteText, div.MsoFootnoteText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Times New Roman";}
span.MsoFootnoteReference
	{vertical-align:super;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:Tahoma;}
p.Style1, li.Style1, div.Style1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	page-break-after:avoid;
	mso-list:l3 level1 lfo3;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.style10, li.style10, div.style10
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	page-break-after:avoid;
	mso-list:l3 level1 lfo3;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
span.CharChar
	{font-family:"MS Mincho";}
 /* Page Definitions */
 @page
	{mso-endnote-separator:url("cid:header.htm\@01CC0E41.F81C5050") es;
	mso-endnote-continuation-separator:url("cid:header.htm\@01CC0E41.F81C5050"=
) ecs;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:645549740;
	mso-list-type:hybrid;
	mso-list-template-ids:-1416842094 67698689 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1
	{mso-list-id:723870878;
	mso-list-type:hybrid;
	mso-list-template-ids:-2071415260 67698689 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F06C;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:40.0pt;
	text-indent:-20.0pt;
	font-family:Wingdings;}
@list l2
	{mso-list-id:1191452621;
	mso-list-type:hybrid;
	mso-list-template-ids:1238299894 67698689 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:42.0pt;
	mso-level-number-position:left;
	margin-left:42.0pt;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3
	{mso-list-id:1792360828;
	mso-list-template-ids:1288485006;}
@list l3:level1
	{mso-level-style-link:"Heading 1";
	mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;
	font-family:"Times New Roman";}
@list l3:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;
	font-family:"Times New Roman";}
@list l3:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;
	font-family:"Times New Roman";}
@list l3:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:.6in;
	mso-level-number-position:left;
	margin-left:.6in;
	text-indent:-.6in;}
@list l3:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:.7in;
	mso-level-number-position:left;
	margin-left:.7in;
	text-indent:-.7in;}
@list l3:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:.8in;
	mso-level-number-position:left;
	margin-left:.8in;
	text-indent:-.8in;}
@list l3:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:.9in;
	mso-level-number-position:left;
	margin-left:.9in;
	text-indent:-.9in;}
@list l3:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l3:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1028" />
</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"Section1">
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><!--[if gte vml 1]><v:shapetype id=3D"_x0000_t74" coordsize=3D"2160=
0,21600"=20
 o:spt=3D"74" path=3D"m10860,2187c10451,1746,9529,1018,9015,730,7865,152,66=
85,,5415,,4175,152,2995,575,1967,1305,1150,2187,575,3222,242,4220,,5410,242=
,6560,575,7597l10860,21600,20995,7597v485,-1037,605,-2187,485,-3377c21115,3=
222,20420,2187,19632,1305,18575,575,17425,152,16275,,15005,,13735,152,12705=
,730v-529,288,-1451,1016,-1845,1457xe">
 <v:stroke joinstyle=3D"miter" />
 <v:path gradientshapeok=3D"t" o:connecttype=3D"custom" o:connectlocs=3D"10=
860,2187;2928,10800;10860,21600;18672,10800"=20
  o:connectangles=3D"270,180,90,0" textboxrect=3D"5037,2277,16557,13677" />
</v:shapetype><v:shape id=3D"DtsShapeName" o:spid=3D"_x0000_s1026" type=3D"=
#_x0000_t74"=20
 alt=3D"47E529CG097D5920@5BB2C5D2BED5405097@8h8=3D@@dM62793!!!!!!BIHO@]M627=
93!!!11111111110BCGBD3519Onsl`m/enu!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!80L8Z8;D8_M62793!!!!!!BIHO@]m62793!!!11111111110BCGBD3519110B=
CGBD3519!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!86G;&lt;8=3D?8`=
M62793!!!!!!BIHO@]M62793!!!11111111110B322C71D4110B322C71D4!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8;?;A8;?@@M62793!!!!!!BIHO@]m62793!!!1@=
6B1B5B110B322C71D4110B322C71D4!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1!1"=20
 style=3D'position:absolute;margin-left:0;margin-top:0;width:.05pt;height:.=
05pt;
 z-index:1;visibility:hidden'>
 <w:anchorlock/>
</v:shape><![endif]--></span></font><font face=3D"Calibri"><span style=3D"f=
ont-family:
Calibri">Hello
 IRTF community, <o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri">As part of a follow-up activity since the last IRTF me=
eting in
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Prague</st1:City></st1:place> =
on Cross Stratum Optimization work, there will be a workshop on Cloud Compu=
ting and Cross Stratum Optimization held on June 7-8, 2011.
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri">The workshop will be held in ETRI&#8217;s facility in
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Daejeon</st1:City>, <st1:count=
ry-region w:st=3D"on">
Korea</st1:country-region></st1:place><font color=3D"navy"><span style=3D"c=
olor:navy">. &nbsp;Please see the details of this workshop below.
</span></font>We will look forward to your participation and contribution f=
or this workshop.
<font color=3D"navy"><span style=3D"color:navy"><o:p></o:p></span></font></=
span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">Please contact us should you have any question on the =
workshop:
<a href=3D"mailto:tschoi@etri.or.kr">Taesang Choi</a> or <a href=3D"mailto:=
leeyoung@huawei.com">
Young Lee</a>. <o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri">Best Regards,<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri">Taesang &amp; Young<o:p></o:p></span></font></p>
<div style=3D"mso-element:para-border-div;border:none;border-bottom:double =
windowtext 2.25pt;
padding:0in 0in 1.0pt 0in">
<p class=3D"MsoNormal" style=3D"border:none;padding:0in"><font size=3D"3" f=
ace=3D"Calibri"><span style=3D"font-size:12.0pt;font-family:Calibri"><o:p>&=
nbsp;</o:p></span></font></p>
</div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">Call for Participation<o:p></o:p></spa=
n></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><b><fon=
t size=3D"4" face=3D"Calibri"><span style=3D"font-size:14.0pt;font-family:C=
alibri;font-weight:
bold">Cloud Computing and Cross Stratum Optimization Workshop</span></font>=
</b><b><font size=3D"4" face=3D"Calibri"><span style=3D"font-size:14.0pt;fo=
nt-family:Calibri;
font-weight:bold"><o:p></o:p></span></font></b></p>
<p class=3D"MsoNormal"><b><font size=3D"3" face=3D"Calibri"><span style=3D"=
font-size:12.0pt;
font-family:Calibri;font-weight:bold"><o:p>&nbsp;</o:p></span></font></b></=
p>
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><b><fon=
t size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;font-family:C=
alibri;font-weight:
bold">ETRI,
</span></font></b><st1:place w:st=3D"on"><st1:City w:st=3D"on"><b><font fac=
e=3D"Calibri"><span style=3D"font-family:Calibri;font-weight:bold">Daejeon<=
/span></font></b></st1:City><b><font face=3D"Calibri"><span style=3D"font-f=
amily:Calibri;font-weight:bold">,
<st1:country-region w:st=3D"on">Korea</st1:country-region></span></font></b=
></st1:place><b><font face=3D"Calibri"><span style=3D"font-family:Calibri;f=
ont-weight:bold">,</span></font></b><b><font face=3D"Calibri"><span style=
=3D"font-family:Calibri;font-weight:bold"><o:p></o:p></span></font></b></p>
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><b><fon=
t size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;font-family:C=
alibri;font-weight:
bold">June 7-8, 2011<o:p></o:p></span></font></b></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><b><font size=3D"3" face=3D"Calibri"><span style=3D"=
font-size:12.0pt;
font-family:Calibri;font-weight:bold">Background<o:p></o:p></span></font></=
b></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri">Cloud computing provides a variety of services allowin=
g end-users, from individual to enterprises, to access to large pools of st=
orage resources, computational
 resources and various application services.&nbsp; There are many ways in w=
hich these services are provided to end-users, ranging from individual soft=
ware applications (Google docs, Salesforce.com) to the allocation and use o=
f thousands of raw computing resources
 geographically distributed around the world.&nbsp; Data centers provide th=
e physical and virtual infrastructure in which cloud computing applications=
 and services are provided.
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri">Since cloud computing and the data centers used to pro=
vide application services are distributed geographically around a network, =
many decisions made in the
 control and management of application services, such as where to instantia=
te another service instance or to which data center out of several a new cl=
ient is assigned, can have a significant impact on the state of the network=
. Conversely the capabilities and
 state of the network can have a major impact on application performance. <=
o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri">Currently application decisions are made with very lit=
tle or no information concerning the underlying network used to deliver tho=
se services. Hence such
 decisions may be sub-optimal from both application and network resource ut=
ilization, and from the achievement of quality of service objectives.&nbsp;=
 Among the top ten obstacles to the adoption of cloud computing identified =
according to Ambrust<a style=3D"mso-footnote-id:ftn1" href=3D"#_ftn1" name=
=3D"_ftnref1" title=3D""><span class=3D"MsoFootnoteReference"><sup><span cl=
ass=3D"MsoFootnoteReference"><sup><font size=3D"3" face=3D"Calibri"><span s=
tyle=3D"font-size:12.0pt;font-family:Calibri">[1]</span></font></sup></span=
></sup></span></a>
 et. al., over half have significant involvement of the network: 1. availab=
ility/business continuity; 3. data confidentiality and auditability; 4. dat=
a transfer bottlenecks; 5. performance unpredictability; 8. scaling quickly=
; 9. reputation fate sharing.
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri">As more application and services are envisaged to be o=
ffered via cloud computing and data centers, it is critical to have an over=
all architectural model
 &nbsp;&nbsp;from both the application stratum and the network stratum poin=
ts of view; define key interfaces among the entities involved in cloud comp=
uting, data centers and the networks supporting them; and provide a next ge=
neration&nbsp; architecture that integrate select
 aspects of &nbsp;cloud computing, data centers, and networks to improve se=
rvice continuity, performance predictability/guarantees, scalability and ma=
nageability.
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri">Cross-stratum optimization is referred to combined opt=
imization in the application and network stratum that aims to provide joint=
 application/network resource
 optimization, responsiveness to quickly changing demands from/to applicati=
on to/from network, enhanced service resilience (via cooperative recovery t=
echniques between application and network) and quality of application exper=
ience (QoE) enhancement (via better
 use of existing network and application resources). <o:p></o:p></span></fo=
nt></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri">This workshop aims to explore the challenges and issue=
s faced by cloud computing and data center integration with networks. Among=
 the key areas of investigation
 to be discussed in the workshop are as follows:<o:p></o:p></span></font></=
p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"margin-left:42.0pt;text-indent:-.25in;mso-l=
ist:l2 level1 lfo4">
<![if !supportLists]><font size=3D"3" face=3D"Symbol"><span style=3D"font-s=
ize:12.0pt;font-family:Symbol"><span style=3D"mso-list:Ignore">&middot;<fon=
t size=3D"1" face=3D"Times New Roman"><span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font face=3D"Calibri"><span s=
tyle=3D"font-family:Calibri">Cloud/network integration architectures and su=
bsystems<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"margin-left:42.0pt;text-indent:-.25in;mso-l=
ist:l2 level1 lfo4">
<![if !supportLists]><font size=3D"3" face=3D"Symbol"><span style=3D"font-s=
ize:12.0pt;font-family:Symbol"><span style=3D"mso-list:Ignore">&middot;<fon=
t size=3D"1" face=3D"Times New Roman"><span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font face=3D"Calibri"><span s=
tyle=3D"font-family:Calibri">U</span></font><font face=3D"Calibri"><span st=
yle=3D"font-family:Calibri">se cases</span></font><font face=3D"Calibri"><s=
pan style=3D"font-family:Calibri">, business
 models</span></font><font face=3D"Calibri"><span style=3D"font-family:Cali=
bri"> and requirements for cloud/network integration<o:p></o:p></span></fon=
t></p>
<p class=3D"MsoNormal" style=3D"margin-left:42.0pt;text-indent:-.25in;mso-l=
ist:l2 level1 lfo4">
<![if !supportLists]><font size=3D"3" face=3D"Symbol"><span style=3D"font-s=
ize:12.0pt;font-family:Symbol"><span style=3D"mso-list:Ignore">&middot;<fon=
t size=3D"1" face=3D"Times New Roman"><span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font face=3D"Calibri"><span s=
tyle=3D"font-family:Calibri">Control/management issues</span></font><font f=
ace=3D"Calibri"><span style=3D"font-family:Calibri"> for cloud/network inte=
gration</span></font><font face=3D"Calibri"><span style=3D"font-family:Cali=
bri"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"margin-left:42.0pt;text-indent:-.25in;mso-l=
ist:l2 level1 lfo4">
<![if !supportLists]><font size=3D"3" face=3D"Symbol"><span style=3D"font-s=
ize:12.0pt;font-family:Symbol"><span style=3D"mso-list:Ignore">&middot;<fon=
t size=3D"1" face=3D"Times New Roman"><span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font face=3D"Calibri"><span s=
tyle=3D"font-family:Calibri">Network virtualization
</span></font><font face=3D"Calibri"><span style=3D"font-family:Calibri">an=
d its impact for cloud/network integration</span></font><font face=3D"Calib=
ri"><span style=3D"font-family:Calibri"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"margin-left:42.0pt;text-indent:-.25in;mso-l=
ist:l2 level1 lfo4">
<![if !supportLists]><font size=3D"3" face=3D"Symbol"><span style=3D"font-s=
ize:12.0pt;font-family:Symbol"><span style=3D"mso-list:Ignore">&middot;<fon=
t size=3D"1" face=3D"Times New Roman"><span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font face=3D"Calibri"><span s=
tyle=3D"font-family:Calibri">Application-aware transport network
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"margin-left:42.0pt;text-indent:-.25in;mso-l=
ist:l2 level1 lfo4">
<![if !supportLists]><font size=3D"3" face=3D"Symbol"><span style=3D"font-s=
ize:12.0pt;font-family:Symbol"><span style=3D"mso-list:Ignore">&middot;<fon=
t size=3D"1" face=3D"Times New Roman"><span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font face=3D"Calibri"><span s=
tyle=3D"font-family:Calibri">Network-aware application/cloud computing<o:p>=
</o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"margin-left:42.0pt;text-indent:-.25in;mso-l=
ist:l2 level1 lfo4">
<![if !supportLists]><font size=3D"3" face=3D"Symbol"><span style=3D"font-s=
ize:12.0pt;font-family:Symbol"><span style=3D"mso-list:Ignore">&middot;<fon=
t size=3D"1" face=3D"Times New Roman"><span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font face=3D"Calibri"><span s=
tyle=3D"font-family:Calibri">Joint application/network reliability and secu=
rity
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"margin-left:42.0pt;text-indent:-.25in;mso-l=
ist:l2 level1 lfo4">
<![if !supportLists]><font size=3D"3" face=3D"Symbol"><span style=3D"font-s=
ize:12.0pt;font-family:Symbol"><span style=3D"mso-list:Ignore">&middot;<fon=
t size=3D"1" face=3D"Times New Roman"><span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font face=3D"Calibri"><span s=
tyle=3D"font-family:Calibri">Experimental/trial experience
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"margin-left:42.0pt;text-indent:-.25in;mso-l=
ist:l2 level1 lfo4">
<![if !supportLists]><font size=3D"3" face=3D"Symbol"><span style=3D"font-s=
ize:12.0pt;font-family:Symbol"><span style=3D"mso-list:Ignore">&middot;<fon=
t size=3D"1" face=3D"Times New Roman"><span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font face=3D"Calibri"><span s=
tyle=3D"font-family:Calibri">Scalability<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"margin-left:42.0pt;text-indent:-.25in;mso-l=
ist:l2 level1 lfo4">
<![if !supportLists]><font size=3D"3" face=3D"Symbol"><span style=3D"font-s=
ize:12.0pt;font-family:Symbol"><span style=3D"mso-list:Ignore">&middot;<fon=
t size=3D"1" face=3D"Times New Roman"><span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font face=3D"Calibri"><span s=
tyle=3D"font-family:Calibri">Joint/shared performance and fault monitoring
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"margin-left:42.0pt;text-indent:-.25in;mso-l=
ist:l2 level1 lfo4">
<![if !supportLists]><font size=3D"3" face=3D"Symbol"><span style=3D"font-s=
ize:12.0pt;font-family:Symbol"><span style=3D"mso-list:Ignore">&middot;<fon=
t size=3D"1" face=3D"Times New Roman"><span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font face=3D"Calibri"><span s=
tyle=3D"font-family:Calibri">Multi-domain issues
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"margin-left:24.0pt"><font size=3D"3" face=
=3D"Calibri"><span style=3D"font-size:12.0pt;font-family:Calibri"><o:p>&nbs=
p;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri">The goal of this workshop is to promote the research i=
nterest in cloud/network integration and to start a new research activity i=
n the IRTF community. The
 workshop organizers are interested in receiving contributions that support=
s this goal. &nbsp;<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0=
pt;font-family:Calibri;
font-weight:bold">Workshop Style
<o:p></o:p></span></font></b></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">The workshop&#8217;s main focus will be on the discuss=
ions of technical topics. Each presentation will
 be given about 40 minutes and 15 minutes of discussion.&nbsp; Interactive =
discussion will be encouraged.
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">In order to keep the group at a manageable size, parti=
cipants are required to submit a
</span></font><font face=3D"Calibri"><span style=3D"font-family:Calibri">po=
sition paper</span></font><font face=3D"Calibri"><span style=3D"font-family=
:Calibri"> as an expression of interest. The authors of accepted
</span></font><font face=3D"Calibri"><span style=3D"font-family:Calibri">pa=
pers</span></font><font face=3D"Calibri"><span style=3D"font-family:Calibri=
"> will be invited to
</span></font><font face=3D"Calibri"><span style=3D"font-family:Calibri">su=
bmit power point presentations and
</span></font><font face=3D"Calibri"><span style=3D"font-family:Calibri">at=
tend the workshop although under special circumstances remote access capabi=
lity</span></font><font face=3D"Calibri"><span style=3D"font-family:Calibri=
"> via video conferencing</span></font><font face=3D"Calibri"><span style=
=3D"font-family:Calibri">
 will be provided. &nbsp;<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0=
pt;font-family:Calibri;
font-weight:bold">Important Dates<o:p></o:p></span></font></b></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">The position papers (an abstract with no more than two=
 pages) must be submitted by May 20<sup>th</sup>,
 2011.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">Position papers</span></font><font face=3D"Calibri"><s=
pan style=3D"font-family:Calibri"> will be reviewed
 by the program organizers and an invitation to the workshop will be sent t=
o one of the paper authors. At the latest, invitations will be distributed =
by May 25<sup>th</sup>, 2011.
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">Invited contributions (power point slides) must be sub=
mitted at latest by
</span></font><font face=3D"Calibri"><span style=3D"font-family:Calibri">Ju=
ne 3rd</span></font><font face=3D"Calibri"><span style=3D"font-family:Calib=
ri">, 2011.&nbsp;
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">All contributions can be submitted to:
<a href=3D"mailto:cso-workshop-prep@cccso.net">cso-workshop-prep@cccso.net<=
/a>. <o:p>
</o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0=
pt;font-family:Calibri;
font-weight:bold">Workshop Technical Committee<o:p></o:p></span></font></b>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">Members of the workshop technical committee are as fol=
lows:<o:p></o:p></span></font></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;
     mso-list:l0 level1 lfo6">
<font size=3D"3" face=3D"Calibri"><span style=3D"font-size:
     12.0pt;font-family:Calibri">Tae Sang Choi (ETRI)<o:p></o:p></span></fo=
nt>
</li><li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bo=
ttom-alt:auto;
     mso-list:l0 level1 lfo6">
<font size=3D"3" face=3D"Calibri"><span style=3D"font-size:
     12.0pt;font-family:Calibri">Young Lee (Huawei)<o:p></o:p></span></font=
>
</li><li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bo=
ttom-alt:auto;
     mso-list:l0 level1 lfo6">
<font size=3D"3" face=3D"Calibri"><span style=3D"font-size:
     12.0pt;font-family:Calibri">Volker Hilt (<st1:place w:st=3D"on"><st1:C=
ity w:st=3D"on">Bell</st1:City></st1:place> Labs)<o:p></o:p></span></font>
</li><li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bo=
ttom-alt:auto;
     mso-list:l0 level1 lfo6">
<font size=3D"3" face=3D"Calibri"><span style=3D"font-size:
     12.0pt;font-family:Calibri">Kohei Shiomoto (NTT)<o:p></o:p></span></fo=
nt>
</li><li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bo=
ttom-alt:auto;
     mso-list:l0 level1 lfo6">
<font size=3D"3" face=3D"Calibri"><span style=3D"font-size:
     12.0pt;font-family:Calibri">Francisco Javier Jimenez
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Chico</st1:City></st1:place> (=
Telefonica)<o:p></o:p></span></font>
</li><li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bo=
ttom-alt:auto;
     mso-list:l0 level1 lfo6">
<font size=3D"3" face=3D"Calibri"><span lang=3D"ES" style=3D"font-size:12.0=
pt;font-family:Calibri">Oscar de Dios Gonzalez (Telefonica)
<o:p></o:p></span></font></li><li class=3D"MsoNormal" style=3D"mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto;
     mso-list:l0 level1 lfo6">
<font size=3D"3" face=3D"Calibri"><span lang=3D"ES" style=3D"font-size:12.0=
pt;font-family:Calibri">Greg Bernstein (Grotto Networking)
<o:p></o:p></span></font></li><li class=3D"MsoNormal" style=3D"mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto;
     mso-list:l0 level1 lfo6">
<font size=3D"3" face=3D"Calibri"><span style=3D"font-size:
     12.0pt;font-family:Calibri">Ning So (Verizon)
<o:p></o:p></span></font></li><li class=3D"MsoNormal" style=3D"mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto;
     mso-list:l0 level1 lfo6">
<st1:PersonName w:st=3D"on"><font size=3D"3" face=3D"Calibri"><span style=
=3D"font-size:12.0pt;font-family:Calibri">Andrea Fumagalli</span></font></s=
t1:PersonName><font face=3D"Calibri"><span style=3D"font-family:Calibri"> (=
<st1:PlaceType w:st=3D"on">University</st1:PlaceType>
 of <st1:PlaceName w:st=3D"on">Texas</st1:PlaceName>, <st1:place w:st=3D"on=
"><st1:City w:st=3D"on">Dallas</st1:City></st1:place>)
<o:p></o:p></span></font></li><li class=3D"MsoNormal" style=3D"mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto;
     mso-list:l0 level1 lfo6">
<font size=3D"3" face=3D"Calibri"><span lang=3D"ES" style=3D"font-size:12.0=
pt;font-family:Calibri">Tae Yeon Kim (ETRI)
<o:p></o:p></span></font></li><li class=3D"MsoNormal" style=3D"mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto;
     mso-list:l0 level1 lfo6">
<font size=3D"3" face=3D"Calibri"><span lang=3D"ES" style=3D"font-size:12.0=
pt;font-family:Calibri">Dan Li (Huawei)<o:p></o:p></span></font>
</li><li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bo=
ttom-alt:auto;
     mso-list:l0 level1 lfo6">
<font size=3D"3" face=3D"Calibri"><span lang=3D"ES" style=3D"font-size:12.0=
pt;font-family:Calibri">Dong Sik Yun (KT)</span></font><i><font face=3D"Cal=
ibri"><span style=3D"font-family:Calibri;font-style:italic"><o:p></o:p></sp=
an></font></i>
</li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;
margin-left:.25in">
<i><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;
font-family:Calibri;font-style:italic"><o:p>&nbsp;</o:p></span></font></i><=
/p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0=
pt;font-family:Calibri;
font-weight:bold">Workshop Logistics&nbsp;<o:p></o:p></span></font></b></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">This one and a half day workshop will take place on Ju=
ne 7-8, 2011 in ETRI facility,
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Daejeon</st1:City>, <st1:count=
ry-region w:st=3D"on">
Korea</st1:country-region></st1:place>: </span></font><i><font face=3D"Cali=
bri"><span style=3D"font-family:Calibri;
font-style:italic"><o:p></o:p></span></font></i></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">161 Gajong-Dong, Yusong-Gu, Daejeon 305-350
<st1:place w:st=3D"on"><st1:PlaceType w:st=3D"on">Republic</st1:PlaceType> =
of <st1:PlaceName w:st=3D"on">
Korea</st1:PlaceName></st1:place><o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;
margin-left:14.2pt;text-indent:-14.2pt;mso-list:l1 level1 lfo7">
<![if !supportLists]><font size=3D"3" face=3D"Wingdings"><span style=3D"fon=
t-size:12.0pt;font-family:Wingdings"><span style=3D"mso-list:Ignore">l<font=
 size=3D"1" face=3D"Times New Roman"><span style=3D"font:7.0pt &quot;Times =
New Roman&quot;">&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font face=3D"Calibri"><span s=
tyle=3D"font-family:Calibri">How to get to ETRI facility from
<st1:place w:st=3D"on"><st1:PlaceName w:st=3D"on">Incheon</st1:PlaceName> <=
st1:PlaceName w:st=3D"on">
International</st1:PlaceName> <st1:PlaceType w:st=3D"on">Airport</st1:Place=
Type></st1:place>
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">The best way to get to ETRI from Incheon airport is by=
 airport limousine bus.&nbsp; It will take you
 to Daeduk Doryong bus stop which is 5 minutes away by Taxi from ETRI.&nbsp=
; The journey will take about 3 hours from airport to bus stop.<o:p></o:p><=
/span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">An alternative way is to take KTX express train from
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Seoul</st1:City></st1:place> t=
rain station to Daejeon train station and take taxi from it to ETRI.&nbsp;
</span></font><font face=3D"Calibri"><span style=3D"font-family:Calibri"><o=
:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;
margin-left:14.2pt;text-indent:-14.2pt;mso-list:l1 level1 lfo7">
<![if !supportLists]><font size=3D"3" face=3D"Wingdings"><span style=3D"fon=
t-size:12.0pt;font-family:Wingdings"><span style=3D"mso-list:Ignore">l<font=
 size=3D"1" face=3D"Times New Roman"><span style=3D"font:7.0pt &quot;Times =
New Roman&quot;">&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font face=3D"Calibri"><span s=
tyle=3D"font-family:Calibri">Lodging/hotel information<o:p></o:p></span></f=
ont></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">Two local hotels are recommended.<o:p></o:p></span></f=
ont></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">Spapia Hotel: http://www.hotelspapia.com/english/index=
.php<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">Yusong Hotel:
<a href=3D"http://www.yousunghotel.com">http://www.yousunghotel.com</a> (Ko=
rean web page only)<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">Reservations with corporate discount rate are availabl=
e.&nbsp; You can contact
</span></font><font face=3D"Calibri"><span style=3D"font-family:Calibri"><a=
 href=3D"mailto:tschoi@etri.or.kr">Taesang Choi</a></span></font><font face=
=3D"Calibri"><span style=3D"font-family:Calibri"> (email:
<a href=3D"mailto:choits@etri.re.kr"><span style=3D"text-decoration:none">c=
hoits@etri.re.kr</span></a>; tel: &#43;82 42 860 5628) for the reservations=
.</span></font><font face=3D"Calibri"><span style=3D"font-family:Calibri"><=
o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Calibri"><span style=3D"font-size:12.0pt;=
font-family:Calibri">Please contact us should you have any question on the =
workshop:
<a href=3D"mailto:tschoi@etri.or.kr">Taesang Choi</a> or <a href=3D"mailto:=
leeyoung@huawei.com">
Young Lee</a>. <o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Calibri"><span style=3D"fon=
t-size:12.0pt;
font-family:Calibri"><!--[if gte vml 1]><v:shape id=3D"_x0000_s1027" type=
=3D"#_x0000_t74"=20
 alt=3D"47E529CG097D5920@5BB2C5D2BED5405097@8h8=3D@@dM62793!!!!!!BIHO@]M627=
93!!!11111111110BCGBD3519Onsl`m/enu!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!80L8Z8;D8_M62793!!!!!!BIHO@]m62793!!!11111111110BCGBD3519110B=
CGBD3519!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!86G;&lt;8=3D?8`=
M62793!!!!!!BIHO@]M62793!!!11111111110B322C71D4110B322C71D4!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8;?;A8;?@@M62793!!!!!!BIHO@]m62793!!!1@=
6B1B5B110B322C71D4110B322C71D4!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1!1"=20
 style=3D'position:absolute;margin-left:0;margin-top:0;width:.05pt;height:.=
05pt;
 z-index:2;visibility:hidden'>
 <w:anchorlock/>
</v:shape><![endif]--></span></font><font face=3D"Calibri"><span style=3D"f=
ont-family:
Calibri"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div style=3D"mso-element:footnote-list"><br clear=3D"all">
<hr align=3D"left" size=3D"1" width=3D"33%">
<div style=3D"mso-element:footnote" id=3D"ftn1">
<p class=3D"MsoFootnoteText"><a style=3D"mso-footnote-id:ftn1" href=3D"#_ft=
nref1" name=3D"_ftn1" title=3D""><span class=3D"MsoFootnoteReference"><sup>=
<font size=3D"2" face=3D"Times New Roman"><span style=3D"font-size:10.0pt">=
<span class=3D"MsoFootnoteReference"><sup><font size=3D"2" face=3D"Times Ne=
w Roman"><span style=3D"font-size:10.0pt;font-family:&quot;Times New Roman&=
quot;">[1]</span></font></sup></span></span></font></sup></span></a>
<font face=3D"Calibri"><span style=3D"font-family:Calibri">M. Armbrust et a=
l., &#8220;A view of cloud computing,&#8221; Communications of the ACM, vol=
. 53, p. 50&#8211;58, Apr. 2010.<o:p></o:p></span></font></p>
</div>
</div>
</body>
</html>

--Boundary_(ID_d3AeIsB4yebslbglNffG1w)--

From borje.ohlman@ericsson.com  Mon May 23 04:27:34 2011
Return-Path: <borje.ohlman@ericsson.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22C19E0783 for <irtf-discuss@ietfa.amsl.com>; Mon, 23 May 2011 04:27:34 -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=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CXIdV3-DCcC4 for <irtf-discuss@ietfa.amsl.com>; Mon, 23 May 2011 04:27:33 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id B6AC8E077F for <irtf-discuss@irtf.org>; Mon, 23 May 2011 04:27:32 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-ec-4dda44a05da7
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 3C.92.20773.0A44ADD4; Mon, 23 May 2011 13:27:31 +0200 (CEST)
Received: from dhcp-147-214-75-143.ki.sw.ericsson.se (153.88.115.8) by smtps.internal.ericsson.com (153.88.115.96) with Microsoft SMTP Server id 8.3.137.0; Mon, 23 May 2011 13:27:25 +0200
From: =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>
Content-Type: multipart/mixed; boundary="Apple-Mail-35--722147607"
Date: Mon, 23 May 2011 13:27:30 +0200
Message-ID: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com>
To: <icn-interest@listserv.netlab.nec.de>, <irtf-discuss@irtf.org>
MIME-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-Brightmail-Tracker: AAAAAA==
Subject: [irtf-discuss] Draft ICN RG Charter
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2011 11:27:34 -0000

--Apple-Mail-35--722147607
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

Here is a proposal for a charter for an ICN RG. In producing this draft =
we have had great help from Volker Hilt, Lixia Zhang, Martin Vigoureux, =
Joerg Ott, Stephen Farrell and Bengt Ahlgren who has commented and made =
proposals for improvements. We also got some first positive feedback =
from the IRTF chair Lars Eggert.
But this does not mean that this charter is ready. There is still room =
for improvement, e.g. good research issues to be added. Please feel free =
to contribute to the discussion on this mailing list(s).
At the next IETF meeting we will present the proposal at the IRTF Open =
Meeting and an RG-to-be side meeting.=20
The side meeting could either be held in the week before the IETF =
meeting, with the problem that interested people might not yet be there, =
or during the IETF week, with the problem that interested people might =
have other conflicting meetings. Any feedback on this dilemma is very =
much appreciated.

	B=F6rje & Dirk


--Apple-Mail-35--722147607
Content-Disposition: attachment; filename="Draft-ICN-RG-Charter.txt"
Content-Type: text/plain; name="Draft-ICN-RG-Charter.txt"
Content-Transfer-Encoding: quoted-printable

Information-Centric Networking Research Group=0D
=0D
Charter=0D
=3D=3D=3D=3D=3D=3D=3D=0D
=0D
Background=0D
----------------=0D
Distributing named information is a major application in the Internet =
today. In addition to Web-based content distribution other distribution =
technologies have emerged such as P2P and CDN which are promoting a =
communication model of accessing data by name, regardless of origin =
server location. =0D
=0D
Information-centric networking (ICN) is an approach to evolve the =
Internet infrastructure to directly support this use by introducing =
uniquely named data as a core Internet principle.  Data becomes =
independent from location, application, storage, and means of =
transportation, enabling in-network caching and replication. The =
expected benefits are improved efficiency, better scalability with =
respect to information/bandwidth demand and better robustness in =
challenging communication scenarios. These concepts are known under =
different terms, including but not limited to: Network of Information =
(NetInf), Content-Centric Networking (CCN), Named Data Networking (NDN) =
and Publish/Subscribe Networking.=0D
=0D
ICN concepts can be applied to different layers of the protocol stack: =
named-based data access can be implemented on top of existing IP =
infrastructure, e.g., by providing resource naming, ubiquitous caching =
and corresponding transport services -- or it can actually be seen as a =
packet-level inter-networking technology that would incur fundamental =
changes to Internet routing and forwarding. In summary, ICN is expected =
to evolve the Internet architecture at different layers.=0D
=0D
Research Challenges=0D
-------------------=0D
Moving the focus from nodes to information objects brings scalability =
issues to a new level, currently the Internet is addressing in the order =
of 10^9 nodes, whereas the number of addressable ICN objects is expected =
to be several orders of magnitude higher. Name-based routing and name =
resolution have to be designed to scale accordingly, also considering =
mobility support and disruption tolerance. This is related to the =
question how objects are actually=0D
named, e.g., using flat labels with name/content integrity or more =
structured, possibly aggregatable names.=0D
=0D
Accessing copies of named content enables applying new data transport =
concepts, such as receiver-oriented (pull-based) transport protocols. =
Caches in the network may play an active role in transport sessions, =
enabling shorter feedback loops and specific transport protocol features =
in challenged networks, quite different from end-to-end transport as in =
TCP today. Leveraging the existence of multiple copies of each object =
enables new transport strategies such as parallel interaction with =
multiple caches.=0D
=0D
With ICN new security models are needed. Today's host centric trust =
model, retrieving data from a trusted server via a secure connection, no =
longer applies for ICN where ubiquitous replication and dynamic =
emergence of eligible object copies for access transactions are the =
norm. Instead, security/trust functions are rather expected to be bound =
to the information object themselves, employing signed objects and and =
ensuring name-data integrity. Moreover, not all objects will be =
universally accessible, requiring authorization and scoping mechanisms.=0D=

=0D
The ICN paradigm is also expected to require new interfaces for =
applications to interact with the network. For example, a new API should =
let the application developers take advantage of location-independent =
naming, caching, and multi access functionality in ICN.=0D
=0D
It is expected that ICN will require changes to the business, legal and =
regulatory landscape. Examples include changes to how peering agreements =
are made in a network that heavily relies on caching. Compensation =
schemes for user nodes contributing cache space, bandwidth and/or =
battery for participating in delivery of objects to third parties. The =
caching of objects also have implications on how the legal framework =
deals with caching objects, in transit, that would mean copyright and/or =
other legal violations if they were regarded as being in your =
possession.=0D
=0D
Finally to get to the deployment of new ICN technology will require a =
well defined migration path from today's networking technology without =
the need for any forklift upgrades or flag days. Migration and =
inter-working possibilities are also required to foster large-scale =
experiments and thorough evaluation of ICN concept and specific concrete =
approaches. The development of corresponding test-beds and =
experimentation facilities is considered a very important potential =
activity area of the ICN RG.=0D
=0D
ICNRG Objectives=0D
----------------=0D
The main objective of the ICNRG is to advance the state of ICN research =
in the mentioned areas, focusing on solutions that are relevant for =
evolving the Internet at large.=0D
=0D
The ICNRG will provide a forum for exchange and analysis of ICN research =
ideas and proposals, work that is based on implementation and simulation =
experiences will be given preference.=0D
=0D
The ICNRG will identify key ICN architecture invariants across different =
specific approaches which could form the basis of a future ICN =
architecture.=0D
=0D
The ICNRG will foster the development of ICN testbeds for performing =
experiments with running code.=0D
=0D
The intention is that one result from this work could be a common =
protocol framework that can be used to identify protocols for =
standardization. These protocols may or may not re-use existing IETF =
protocols.=0D
=0D
Milestones=0D
----------=0D
The ICNRG will not work along a complete list of milestones, but will be=0D=

set to meet the following starting point, intermediate and potential=0D
long-term goals:=0D
=0D
1. As a starting point the ICNRG will produce a document that describes =
the main concepts and research challenges in depth.=0D
2. An an intermediate milestone, the ICNRG will produce a document that =
provides a survey of different approaches and techniques.=0D
3. Eventual long-term goals would be documents describing an ICN =
architecture and possible specific (protocol) elements, as well as =
documents providing recommendations to the IETF regarding transferring =
ICNRG results to standardization work.=0D
=0D
Organization=0D
------------=0D
The ICNRG will use an open mailing list =
(icnrg@irtf.org<mailto:icnrg@irtf.org>) as the main communication =
vehicle for the group.=0D
=0D
Most of the communication inside the ICNRG will be done through use of =
mailing lists, however, the group will hold regular physical meetings at =
least once a year in conjunction with IETF meetings. Additional meetings =
may be held at IETF or other venues, such as in conjunction with related =
academic conferences.=0D
=0D
The ICNRG will produce Informational and Experimental RFCs in order to =
document the activity of the group and to formalize the outcome of the =
research topics carried by the group. In addition, such documentation =
could become input to IETF working groups.=

--Apple-Mail-35--722147607--

From martin.vigoureux@alcatel-lucent.com  Tue May 24 05:33:23 2011
Return-Path: <martin.vigoureux@alcatel-lucent.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04D94E068C for <irtf-discuss@ietfa.amsl.com>; Tue, 24 May 2011 05:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vxhKc9K0Vhf6 for <irtf-discuss@ietfa.amsl.com>; Tue, 24 May 2011 05:33:22 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 4039DE067C for <irtf-discuss@irtf.org>; Tue, 24 May 2011 05:33:21 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p4OCTxfZ010318 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 24 May 2011 14:33:17 +0200
Received: from [172.27.205.227] (135.120.57.7) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (135.120.45.63) with Microsoft SMTP Server (TLS) id 8.3.106.1; Tue, 24 May 2011 14:33:07 +0200
Message-ID: <4DDBA583.604@alcatel-lucent.com>
Date: Tue, 24 May 2011 14:33:07 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Paulo Mendes <paulo.mendes@ulusofona.pt>
References: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com> <62C44350-6EED-4A6F-9E02-6D3F89A3097D@ulusofona.pt>
In-Reply-To: <62C44350-6EED-4A6F-9E02-6D3F89A3097D@ulusofona.pt>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "icn-interest@listserv.netlab.nec.de" <icn-interest@listserv.netlab.nec.de>
Subject: Re: [irtf-discuss] [Icn-interest] Draft ICN RG Charter
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2011 12:33:23 -0000

Hello Paulo,

Le 24/05/2011 13:55, Paulo Mendes a écrit :
> Hi Borje and Dirk
>
> I would be careful with the word "architecture" since IETF/IRTF does not standardize architectures. Hence I would propose to use the following sentence...
>
> "The ICNRG will investigate components of a common protocol framework for information-centric networking, aiming to: i) identify protocols for standardization, which may or may not re; ii) support an ICN architecture with large applicability."
>
> ... to replace the following two sentences:
>
> "The ICNRG will identify key ICN architecture invariants across different specific approaches which could form the basis of a future ICN architecture."
>
> "The intention is that one result from this work could be a common protocol framework that can be used to identify protocols for standardization. These protocols may or may not re-use existing IETF protocols."

In turn, I would be careful with the statement "IETF/IRTF does not 
standardize architectures" :-)
It all depends on what one reads in "architecture".
Note also that the charter does not say that an architecture will be 
standardized.
I think the text is fine.

best regards,
martin

From paulo.mendes@ulusofona.pt  Tue May 24 04:55:41 2011
Return-Path: <paulo.mendes@ulusofona.pt>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50FA5E072C for <irtf-discuss@ietfa.amsl.com>; Tue, 24 May 2011 04:55:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T7OYVGUCAsZ5 for <irtf-discuss@ietfa.amsl.com>; Tue, 24 May 2011 04:55:40 -0700 (PDT)
Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by ietfa.amsl.com (Postfix) with ESMTP id C9D0EE068D for <irtf-discuss@irtf.org>; Tue, 24 May 2011 04:55:39 -0700 (PDT)
Received: by wyf23 with SMTP id 23so6686835wyf.13 for <irtf-discuss@irtf.org>; Tue, 24 May 2011 04:55:38 -0700 (PDT)
Received: by 10.216.121.200 with SMTP id r50mr3356533weh.7.1306238138441; Tue, 24 May 2011 04:55:38 -0700 (PDT)
Received: from [192.168.14.108] ([193.137.75.158]) by mx.google.com with ESMTPS id h39sm3781280wes.29.2011.05.24.04.55.37 (version=SSLv3 cipher=OTHER); Tue, 24 May 2011 04:55:37 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Paulo Mendes <paulo.mendes@ulusofona.pt>
In-Reply-To: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com>
Date: Tue, 24 May 2011 12:55:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <62C44350-6EED-4A6F-9E02-6D3F89A3097D@ulusofona.pt>
References: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com>
To: icn-interest@listserv.netlab.nec.de
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Tue, 24 May 2011 07:13:15 -0700
Cc: irtf-discuss@irtf.org
Subject: Re: [irtf-discuss] [Icn-interest] Draft ICN RG Charter
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2011 11:55:41 -0000

Hi Borje and Dirk

I would like to provide the following comments in what concerns the =
ICNRG objectives and milestones:

A) ICNRG objectives

Since the list of research areas is not fully analyzed (work proposed to =
be done as first milestone) I suggest to change the first objective to =
"The main objective of the ICNRG is to advance the state of ICN research =
in AT LEAST the mentioned areas, focusing on solutions that are relevant =
for evolving the Internet at large."

As for the expression "Internet at large" I would be a little more =
precise, including some examples in order to avoid misunderstandings.. I =
would suggest "... Internet at large, including the support for new =
services and operation into disruptive scenarios based for instance in =
the present of a considerable number of low-capacity (computational, =
storage) devices". The idea is to keep as an objective the analysis of =
the interaction of information-centric networking with =
Internet-of-services and Internet-of-connected-objects.

I would put more emphasis to work based on implementations than =
simulations.. Simulations should be pointed out as acceptable to prove =
the feasibility of proposed solutions in large-scale scenarios. Given =
more importance to implementations is inline with the other mentioned =
objective of ICNRG "The ICNRG will foster the development of ICN =
testbeds for performing experiments with running code."

I would be careful with the word "architecture" since IETF/IRTF does not =
standardize architectures. Hence I would propose to use the following =
sentence...

"The ICNRG will investigate components of a common protocol framework =
for information-centric networking, aiming to: i) identify protocols for =
standardization, which may or may not re; ii) support an ICN =
architecture with large applicability."=20

... to replace the following two sentences:

"The ICNRG will identify key ICN architecture invariants across =
different specific approaches which could form the basis of a future ICN =
architecture."

"The intention is that one result from this work could be a common =
protocol framework that can be used to identify protocols for =
standardization. These protocols may or may not re-use existing IETF =
protocols."


B) ICNRG Milestones

The charter has milestones to describe the main concepts and research =
challenges, to provide a survey of different approaches and to describe =
an ICN architecture.

What is missing here is the common protocol framework mentioned before. =
So I'll add the following milestone as third one: "Based on the =
identified main research challenges and the analysis of different =
approaches, ICNRG will devise a common protocol framework for ICN, =
aiming to have high applicability".

I would re-write the third ICNRG milestone, since saying that "... =
long-term goals would be documents describing an ICN architecture.. " =
since a little strange to see within IETF/IRTF work. Instead of saying =
that the goal will describe an architecture, I would suggest to say that =
the group will described guidelines to device an ICN architecture based =
on the common protocol framework to be devised within the ICNRG.

Somewhere in this process we should have a milestone to check the =
applicability of ICN, aiming to check our inline with potential =
standardization effort is the work to be devised in the ICNRG


Cheers
Paulo


On May 23, 2011, at 12:27 PM, B=F6rje Ohlman wrote:

> Here is a proposal for a charter for an ICN RG. In producing this =
draft we have had great help from Volker Hilt, Lixia Zhang, Martin =
Vigoureux, Joerg Ott, Stephen Farrell and Bengt Ahlgren who has =
commented and made proposals for improvements. We also got some first =
positive feedback from the IRTF chair Lars Eggert.
> But this does not mean that this charter is ready. There is still room =
for improvement, e.g. good research issues to be added. Please feel free =
to contribute to the discussion on this mailing list(s).
> At the next IETF meeting we will present the proposal at the IRTF Open =
Meeting and an RG-to-be side meeting.=20
> The side meeting could either be held in the week before the IETF =
meeting, with the problem that interested people might not yet be there, =
or during the IETF week, with the problem that interested people might =
have other conflicting meetings. Any feedback on this dilemma is very =
much appreciated.
>=20
> 	B=F6rje & Dirk
>=20
> =
<Draft-ICN-RG-Charter.txt>_______________________________________________
> Icn-interest mailing list
> Icn-interest@listserv.netlab.nec.de
> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest

-------------------------------------------------------------
Paulo Mendes, Ph.D
Scientific Director for Innovation of the Research Unit in Informatics =
Systems and Technologies (SITI)
Coordinator of the Internet Architecture and Networking Lab (IAN Lab)
University Lusofona, Portugal
paulo.mendes@ulusofona.pt
http://siti.ulusofona.pt
Tel.: 217 515 500 Fax: 21 757 7006











From Dirk.Kutscher@neclab.eu  Tue May 24 05:41:49 2011
Return-Path: <Dirk.Kutscher@neclab.eu>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D917CE06E9 for <irtf-discuss@ietfa.amsl.com>; Tue, 24 May 2011 05:41:49 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WP2FE35fFGp8 for <irtf-discuss@ietfa.amsl.com>; Tue, 24 May 2011 05:41:48 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by ietfa.amsl.com (Postfix) with ESMTP id 87D1CE068C for <irtf-discuss@irtf.org>; Tue, 24 May 2011 05:41:48 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id 7449E2C000088; Tue, 24 May 2011 14:41:47 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office.hd)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MEkOfYTLa44U; Tue, 24 May 2011 14:41:47 +0200 (CEST)
Received: by smtp0.neclab.eu (Postfix, from userid 1001) id 558372C00008A; Tue, 24 May 2011 14:41:47 +0200 (CEST)
Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by smtp0.neclab.eu (Postfix) with ESMTP id B059D2C000088; Tue, 24 May 2011 14:41:36 +0200 (CEST)
Received: from PALLENE.office.hd ([169.254.1.225]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0270.001; Tue, 24 May 2011 14:41:36 +0200
From: Dirk Kutscher <Dirk.Kutscher@neclab.eu>
To: "icn-interest@listserv.netlab.nec.de" <icn-interest@listserv.netlab.nec.de>
Thread-Topic: [Icn-interest] Draft ICN RG Charter
Thread-Index: AQHMGTxrvltMJilX+kKiz2CyondNKZSbvvuAgAAlhKA=
Date: Tue, 24 May 2011 12:41:35 +0000
Message-ID: <82AB329A76E2484D934BBCA77E9F524905B3FC78@PALLENE.office.hd>
References: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com> <62C44350-6EED-4A6F-9E02-6D3F89A3097D@ulusofona.pt>
In-Reply-To: <62C44350-6EED-4A6F-9E02-6D3F89A3097D@ulusofona.pt>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.2.105]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 24 May 2011 07:13:15 -0700
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Subject: Re: [irtf-discuss] [Icn-interest] Draft ICN RG Charter
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2011 12:41:50 -0000

Hi Paulo,

Thanks for the suggestions. Please my some comments inline.

> Since the list of research areas is not fully analyzed (work proposed
> to be done as first milestone) I suggest to change the first objective
> to "The main objective of the ICNRG is to advance the state of ICN
> research in AT LEAST the mentioned areas, focusing on solutions that
> are relevant for evolving the Internet at large."

OK, I agree.

> As for the expression "Internet at large" I would be a little more
> precise, including some examples in order to avoid misunderstandings..
> I would suggest "... Internet at large, including the support for new
> services and operation into disruptive scenarios based for instance in
> the present of a considerable number of low-capacity (computational,
> storage) devices". The idea is to keep as an objective the analysis of
> the interaction of information-centric networking with Internet-of-
> services and Internet-of-connected-objects.

Here, I really disagree. We did not want to create the notion of different =
"Internets", i.e., Information-Centric, Internet-of-Services, Internet-of-T=
hings etc. The message is that we want to assess ICN's applicability as a g=
eneral Internet technology ("Internet at large").
=20
> I would put more emphasis to work based on implementations than
> simulations.. Simulations should be pointed out as acceptable to prove
> the feasibility of proposed solutions in large-scale scenarios. Given
> more importance to implementations is inline with the other mentioned
> objective of ICNRG "The ICNRG will foster the development of ICN
> testbeds for performing experiments with running code."

Right, so IMO that aspect is already covered. We also said "work that is ba=
sed on implementation and simulation experiences will be given preference."=
.
=20
> I would be careful with the word "architecture" since IETF/IRTF does
> not standardize architectures. Hence I would propose to use the
> following sentence...
>=20
> "The ICNRG will investigate components of a common protocol framework
> for information-centric networking, aiming to: i) identify protocols
> for standardization, which may or may not re; ii) support an ICN
> architecture with large applicability."
>=20
> ... to replace the following two sentences:
>=20
> "The ICNRG will identify key ICN architecture invariants across
> different specific approaches which could form the basis of a future
> ICN architecture."
> "The intention is that one result from this work could be a common
> protocol framework that can be used to identify protocols for
> standardization. These protocols may or may not re-use existing IETF
> protocols."

OK, got your point. It's true that "form the basis of a future ICN architec=
ture" can be misinterpreted.

Here, we wanted to strike a balance: it's true that *system architecture* w=
ork is not the IETF's core business. However, for an IRTF research group, w=
e expect some architecture work to be required, e.g., to find out about com=
mon core elements that you need to agree on (for later protocol specificati=
ons etc.). For example, RFC 4838 is a good example of architecture work tha=
t describes fundamental architecture concepts for DTN, which has been a goo=
d basis for subsequent DTNRG work on the Bundle Protocol spec.

Will think of a better formulation.


>=20
>=20
> B) ICNRG Milestones
>=20
> The charter has milestones to describe the main concepts and research
> challenges, to provide a survey of different approaches and to describe
> an ICN architecture.
>=20
> What is missing here is the common protocol framework mentioned before.
> So I'll add the following milestone as third one: "Based on the
> identified main research challenges and the analysis of different
> approaches, ICNRG will devise a common protocol framework for ICN,
> aiming to have high applicability".
>=20
> I would re-write the third ICNRG milestone, since saying that "...
> long-term goals would be documents describing an ICN architecture.. "
> since a little strange to see within IETF/IRTF work. Instead of saying
> that the goal will describe an architecture, I would suggest to say
> that the group will described guidelines to device an ICN architecture
> based on the common protocol framework to be devised within the ICNRG.

OK, we have to remember that this is not an IETF WG charter. For a research=
 group, that is really highly contribution-driven, we should allow some fle=
xibility. From that perspective, I think it would be better not promise del=
ivering guidelines to devise an architecture. If course, that would not kee=
p the WG from doing that, if people are interested.

> Somewhere in this process we should have a milestone to check the
> applicability of ICN, aiming to check our inline with potential
> standardization effort is the work to be devised in the ICNRG

Again, normally "yes" for a tightly controlled activity, but for a research=
 group, I rather see our contribution in advancing ICN and offering the res=
ult to the community. I would not like to have a milestone on that.

Thanks again for the comments!

Best regards,

Dirk



=20
>=20
> Cheers
> Paulo
>=20
>=20
> On May 23, 2011, at 12:27 PM, B=F6rje Ohlman wrote:
>=20
> > Here is a proposal for a charter for an ICN RG. In producing this
> draft we have had great help from Volker Hilt, Lixia Zhang, Martin
> Vigoureux, Joerg Ott, Stephen Farrell and Bengt Ahlgren who has
> commented and made proposals for improvements. We also got some first
> positive feedback from the IRTF chair Lars Eggert.
> > But this does not mean that this charter is ready. There is still
> room for improvement, e.g. good research issues to be added. Please
> feel free to contribute to the discussion on this mailing list(s).
> > At the next IETF meeting we will present the proposal at the IRTF
> Open Meeting and an RG-to-be side meeting.
> > The side meeting could either be held in the week before the IETF
> meeting, with the problem that interested people might not yet be there,
> or during the IETF week, with the problem that interested people might
> have other conflicting meetings. Any feedback on this dilemma is very
> much appreciated.
> >
> > 	B=F6rje & Dirk
> >
> > <Draft-ICN-RG-
> Charter.txt>_______________________________________________
> > Icn-interest mailing list
> > Icn-interest@listserv.netlab.nec.de
> > https://listserv.netlab.nec.de/mailman/listinfo/icn-interest
>=20
> -------------------------------------------------------------
> Paulo Mendes, Ph.D
> Scientific Director for Innovation of the Research Unit in Informatics
> Systems and Technologies (SITI)
> Coordinator of the Internet Architecture and Networking Lab (IAN Lab)
> University Lusofona, Portugal
> paulo.mendes@ulusofona.pt
> http://siti.ulusofona.pt
> Tel.: 217 515 500 Fax: 21 757 7006
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Icn-interest mailing list
> Icn-interest@listserv.netlab.nec.de
> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest

From markus@mhof.com  Tue May 24 06:21:53 2011
Return-Path: <markus@mhof.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 344C2E0745 for <irtf-discuss@ietfa.amsl.com>; Tue, 24 May 2011 06:21:53 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wa8Y38Z-9AOm for <irtf-discuss@ietfa.amsl.com>; Tue, 24 May 2011 06:21:48 -0700 (PDT)
Received: from vms173005pub.verizon.net (vms173005pub.verizon.net [206.46.173.5]) by ietfa.amsl.com (Postfix) with ESMTP id D04C4E0743 for <irtf-discuss@irtf.org>; Tue, 24 May 2011 06:21:48 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Received: from [10.0.0.20] ([unknown] [71.187.39.97]) by vms173005.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LLP001NFBRRIQ40@vms173005.mailsrvcs.net> for irtf-discuss@irtf.org; Tue, 24 May 2011 08:21:31 -0500 (CDT)
Message-id: <4DDBB0D7.5080006@mhof.com>
Date: Tue, 24 May 2011 09:21:27 -0400
From: Markus Hofmann <markus@mhof.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
To: icn-interest@listserv.netlab.nec.de
References: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com>
In-reply-to: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com>
X-Mailman-Approved-At: Tue, 24 May 2011 07:13:15 -0700
Cc: irtf-discuss@irtf.org
Subject: Re: [irtf-discuss] [Icn-interest] Draft ICN RG Charter
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2011 13:21:53 -0000

On 5/23/2011 7:27 AM, Börje Ohlman wrote:
> Milestones
>
> ----------
>
> The ICNRG will not work along a complete list of milestones, but
> will be set to meet the following starting point, intermediate and
> potential long-term goals:
>
> 1. As a starting point the ICNRG will produce a document that
> describes the main concepts and research challenges in depth.

What about including a summary of the expected benefits of ICN, i.e. 
first describe the *problem* to be solved in *quantifiable* terms, then 
describe the main concepts and continue on to the research challenges.

Far too often do we in research work on solutions just to struggle later 
on with the justification of the problem they solve. Or is the problem 
ICN will solve not yet quantifiable?

If sufficient work on the problem statement has already been done, then 
a brief summary with references might suffice. But a clearly defined and 
convincing problem statement will go a long way, IMHO.

Cheers,
   Markus




From paulo.mendes@ulusofona.pt  Wed May 25 02:36:00 2011
Return-Path: <paulo.mendes@ulusofona.pt>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37EEDE06E7 for <irtf-discuss@ietfa.amsl.com>; Wed, 25 May 2011 02:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VlHdUK4rT-eK for <irtf-discuss@ietfa.amsl.com>; Wed, 25 May 2011 02:35:59 -0700 (PDT)
Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by ietfa.amsl.com (Postfix) with ESMTP id 16275E0679 for <irtf-discuss@irtf.org>; Wed, 25 May 2011 02:35:58 -0700 (PDT)
Received: by wwc33 with SMTP id 33so7489039wwc.19 for <irtf-discuss@irtf.org>; Wed, 25 May 2011 02:35:58 -0700 (PDT)
Received: by 10.216.191.208 with SMTP id g58mr4161813wen.85.1306316158052; Wed, 25 May 2011 02:35:58 -0700 (PDT)
Received: from [192.169.70.102] ([193.137.75.158]) by mx.google.com with ESMTPS id h65sm186096wes.37.2011.05.25.02.35.56 (version=SSLv3 cipher=OTHER); Wed, 25 May 2011 02:35:56 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Paulo Mendes <paulo.mendes@ulusofona.pt>
In-Reply-To: <4DDBA583.604@alcatel-lucent.com>
Date: Wed, 25 May 2011 10:35:54 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C517164-9DF8-44C7-A3F3-77FCB5333E1C@ulusofona.pt>
References: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com> <62C44350-6EED-4A6F-9E02-6D3F89A3097D@ulusofona.pt> <4DDBA583.604@alcatel-lucent.com>
To: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1084)
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "icn-interest@listserv.netlab.nec.de" <icn-interest@listserv.netlab.nec.de>
Subject: Re: [irtf-discuss] [Icn-interest] Draft ICN RG Charter
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2011 09:36:00 -0000

Hi Martin

Just to clarify. It is clear that the charter does not say that an =
architecture will be standardized. It couldn't in any case - IRTF does =
not aim to devise standards. I was commenting on the fact that one goal =
described in the charter seems to be to write "...documents describing =
an ICN architecture", and IETF/IRTF is focus on working on protocols and =
not architectures. 3GPP, ITU-T are more looking at architectures, most =
of the time making use of IETF protocols. So, we do not want to create =
misunderstandings :).

Paulo

On May 24, 2011, at 1:33 PM, Martin Vigoureux wrote:

> Hello Paulo,
>=20
> Le 24/05/2011 13:55, Paulo Mendes a =E9crit :
>> Hi Borje and Dirk
>>=20
>> I would be careful with the word "architecture" since IETF/IRTF does =
not standardize architectures. Hence I would propose to use the =
following sentence...
>>=20
>> "The ICNRG will investigate components of a common protocol framework =
for information-centric networking, aiming to: i) identify protocols for =
standardization, which may or may not re; ii) support an ICN =
architecture with large applicability."
>>=20
>> ... to replace the following two sentences:
>>=20
>> "The ICNRG will identify key ICN architecture invariants across =
different specific approaches which could form the basis of a future ICN =
architecture."
>>=20
>> "The intention is that one result from this work could be a common =
protocol framework that can be used to identify protocols for =
standardization. These protocols may or may not re-use existing IETF =
protocols."
>=20
> In turn, I would be careful with the statement "IETF/IRTF does not =
standardize architectures" :-)
> It all depends on what one reads in "architecture".
> Note also that the charter does not say that an architecture will be =
standardized.
> I think the text is fine.
>=20
> best regards,
> martin

-------------------------------------------------------------
Paulo Mendes, Ph.D
Scientific Director for Innovation of the Research Unit in Informatics =
Systems and Technologies (SITI)
Coordinator of the Internet Architecture and Networking Lab (IAN Lab)
University Lusofona, Portugal
paulo.mendes@ulusofona.pt
http://siti.ulusofona.pt
Tel.: 217 515 500 Fax: 21 757 7006











From paulo.mendes@ulusofona.pt  Wed May 25 03:42:26 2011
Return-Path: <paulo.mendes@ulusofona.pt>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75FD7130020 for <irtf-discuss@ietfa.amsl.com>; Wed, 25 May 2011 03:42:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iP55CrPMJ32x for <irtf-discuss@ietfa.amsl.com>; Wed, 25 May 2011 03:42:25 -0700 (PDT)
Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by ietfa.amsl.com (Postfix) with ESMTP id 49EB8130019 for <irtf-discuss@irtf.org>; Wed, 25 May 2011 03:42:22 -0700 (PDT)
Received: by wwc33 with SMTP id 33so7543779wwc.19 for <irtf-discuss@irtf.org>; Wed, 25 May 2011 03:42:21 -0700 (PDT)
Received: by 10.216.30.206 with SMTP id k56mr4495901wea.29.1306320141199; Wed, 25 May 2011 03:42:21 -0700 (PDT)
Received: from [192.169.70.102] ([193.137.75.158]) by mx.google.com with ESMTPS id z13sm216217weq.33.2011.05.25.03.42.19 (version=SSLv3 cipher=OTHER); Wed, 25 May 2011 03:42:20 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Paulo Mendes <paulo.mendes@ulusofona.pt>
In-Reply-To: <82AB329A76E2484D934BBCA77E9F524905B3FC78@PALLENE.office.hd>
Date: Wed, 25 May 2011 11:42:17 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC02A606-946C-4687-B943-3A443A2BC200@ulusofona.pt>
References: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com> <62C44350-6EED-4A6F-9E02-6D3F89A3097D@ulusofona.pt> <82AB329A76E2484D934BBCA77E9F524905B3FC78@PALLENE.office.hd>
To: icn-interest@listserv.netlab.nec.de
X-Mailer: Apple Mail (2.1084)
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Subject: Re: [irtf-discuss] [Icn-interest] Draft ICN RG Charter
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2011 10:42:26 -0000

Hi Dirk

see my comments inline...

On May 24, 2011, at 1:41 PM, Dirk Kutscher wrote:

> Hi Paulo,
>=20
> Thanks for the suggestions. Please my some comments inline.
>=20
>> Since the list of research areas is not fully analyzed (work proposed
>> to be done as first milestone) I suggest to change the first =
objective
>> to "The main objective of the ICNRG is to advance the state of ICN
>> research in AT LEAST the mentioned areas, focusing on solutions that
>> are relevant for evolving the Internet at large."
>=20
> OK, I agree.
>=20
>> As for the expression "Internet at large" I would be a little more
>> precise, including some examples in order to avoid =
misunderstandings..
>> I would suggest "... Internet at large, including the support for new
>> services and operation into disruptive scenarios based for instance =
in
>> the present of a considerable number of low-capacity (computational,
>> storage) devices". The idea is to keep as an objective the analysis =
of
>> the interaction of information-centric networking with Internet-of-
>> services and Internet-of-connected-objects.
>=20
> Here, I really disagree. We did not want to create the notion of =
different "Internets", i.e., Information-Centric, Internet-of-Services, =
Internet-of-Things etc. The message is that we want to assess ICN's =
applicability as a general Internet technology ("Internet at large").

I was not suggestion the creation of the notion of different =
"Internets", Just to say something in the charter about the =
applicability scenario at large... For instance, is ICNRG going to look =
at ICN solutions for the Internet as is it, or for the "expected" =
Internet which may be extended to different types of portable devices. =
But is all of us have this perspective in mind, than "Internet at large" =
is fine :)


>=20
>> I would put more emphasis to work based on implementations than
>> simulations.. Simulations should be pointed out as acceptable to =
prove
>> the feasibility of proposed solutions in large-scale scenarios. Given
>> more importance to implementations is inline with the other mentioned
>> objective of ICNRG "The ICNRG will foster the development of ICN
>> testbeds for performing experiments with running code."
>=20
> Right, so IMO that aspect is already covered. We also said "work that =
is based on implementation and simulation experiences will be given =
preference.".

RIght.. The question is that this sentence givens equal preference to =
simulations and testbed experiences. I was suggesting to give higher =
preference to testbed experiences.

>=20
>> I would be careful with the word "architecture" since IETF/IRTF does
>> not standardize architectures. Hence I would propose to use the
>> following sentence...
>>=20
>> "The ICNRG will investigate components of a common protocol framework
>> for information-centric networking, aiming to: i) identify protocols
>> for standardization, which may or may not re; ii) support an ICN
>> architecture with large applicability."
>>=20
>> ... to replace the following two sentences:
>>=20
>> "The ICNRG will identify key ICN architecture invariants across
>> different specific approaches which could form the basis of a future
>> ICN architecture."
>> "The intention is that one result from this work could be a common
>> protocol framework that can be used to identify protocols for
>> standardization. These protocols may or may not re-use existing IETF
>> protocols."
>=20
> OK, got your point. It's true that "form the basis of a future ICN =
architecture" can be misinterpreted.
>=20
> Here, we wanted to strike a balance: it's true that *system =
architecture* work is not the IETF's core business. However, for an IRTF =
research group, we expect some architecture work to be required, e.g., =
to find out about common core elements that you need to agree on (for =
later protocol specifications etc.). For example, RFC 4838 is a good =
example of architecture work that describes fundamental architecture =
concepts for DTN, which has been a good basis for subsequent DTNRG work =
on the Bundle Protocol spec.
>=20
> Will think of a better formulation.

Good.. If we are talking about RFC4838 type of work, and not a 3GPP type =
of description this is expectable.

>=20
>=20
>>=20
>>=20
>> B) ICNRG Milestones
>>=20
>> The charter has milestones to describe the main concepts and research
>> challenges, to provide a survey of different approaches and to =
describe
>> an ICN architecture.
>>=20
>> What is missing here is the common protocol framework mentioned =
before.
>> So I'll add the following milestone as third one: "Based on the
>> identified main research challenges and the analysis of different
>> approaches, ICNRG will devise a common protocol framework for ICN,
>> aiming to have high applicability".
>>=20
>> I would re-write the third ICNRG milestone, since saying that "...
>> long-term goals would be documents describing an ICN architecture.. "
>> since a little strange to see within IETF/IRTF work. Instead of =
saying
>> that the goal will describe an architecture, I would suggest to say
>> that the group will described guidelines to device an ICN =
architecture
>> based on the common protocol framework to be devised within the =
ICNRG.
>=20
> OK, we have to remember that this is not an IETF WG charter. For a =
research group, that is really highly contribution-driven, we should =
allow some flexibility. =46rom that perspective, I think it would be =
better not promise delivering guidelines to devise an architecture. If =
course, that would not keep the WG from doing that, if people are =
interested.

OK

>=20
>> Somewhere in this process we should have a milestone to check the
>> applicability of ICN, aiming to check our inline with potential
>> standardization effort is the work to be devised in the ICNRG
>=20
> Again, normally "yes" for a tightly controlled activity, but for a =
research group, I rather see our contribution in advancing ICN and =
offering the result to the community. I would not like to have a =
milestone on that.

I was not proposing a very tight activity, but just a reality-check =
milestone to analyze what is exactly the probability of having ICNRG =
research work being ported to IETF... I like to see this reality check =
in any research work, from PhD thesis to EU projects :-)

Cheers

Paulo


>=20
> Thanks again for the comments!
>=20
> Best regards,
>=20
> Dirk
>=20
>=20
>=20
>=20
>>=20
>> Cheers
>> Paulo
>>=20
>>=20
>> On May 23, 2011, at 12:27 PM, B=F6rje Ohlman wrote:
>>=20
>>> Here is a proposal for a charter for an ICN RG. In producing this
>> draft we have had great help from Volker Hilt, Lixia Zhang, Martin
>> Vigoureux, Joerg Ott, Stephen Farrell and Bengt Ahlgren who has
>> commented and made proposals for improvements. We also got some first
>> positive feedback from the IRTF chair Lars Eggert.
>>> But this does not mean that this charter is ready. There is still
>> room for improvement, e.g. good research issues to be added. Please
>> feel free to contribute to the discussion on this mailing list(s).
>>> At the next IETF meeting we will present the proposal at the IRTF
>> Open Meeting and an RG-to-be side meeting.
>>> The side meeting could either be held in the week before the IETF
>> meeting, with the problem that interested people might not yet be =
there,
>> or during the IETF week, with the problem that interested people =
might
>> have other conflicting meetings. Any feedback on this dilemma is very
>> much appreciated.
>>>=20
>>> 	B=F6rje & Dirk
>>>=20
>>> <Draft-ICN-RG-
>> Charter.txt>_______________________________________________
>>> Icn-interest mailing list
>>> Icn-interest@listserv.netlab.nec.de
>>> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest
>>=20
>> -------------------------------------------------------------
>> Paulo Mendes, Ph.D
>> Scientific Director for Innovation of the Research Unit in =
Informatics
>> Systems and Technologies (SITI)
>> Coordinator of the Internet Architecture and Networking Lab (IAN Lab)
>> University Lusofona, Portugal
>> paulo.mendes@ulusofona.pt
>> http://siti.ulusofona.pt
>> Tel.: 217 515 500 Fax: 21 757 7006
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> Icn-interest mailing list
>> Icn-interest@listserv.netlab.nec.de
>> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest
> _______________________________________________
> Icn-interest mailing list
> Icn-interest@listserv.netlab.nec.de
> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest

-------------------------------------------------------------
Paulo Mendes, Ph.D
Scientific Director for Innovation of the Research Unit in Informatics =
Systems and Technologies (SITI)
Coordinator of the Internet Architecture and Networking Lab (IAN Lab)
University Lusofona, Portugal
paulo.mendes@ulusofona.pt
http://siti.ulusofona.pt
Tel.: 217 515 500 Fax: 21 757 7006











From morabito.giacomo@gmail.com  Wed May 25 14:37:37 2011
Return-Path: <morabito.giacomo@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B21E0E0800 for <irtf-discuss@ietfa.amsl.com>; Wed, 25 May 2011 14:37:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZfgvEoyN1TX3 for <irtf-discuss@ietfa.amsl.com>; Wed, 25 May 2011 14:37:35 -0700 (PDT)
Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by ietfa.amsl.com (Postfix) with ESMTP id 51E69E075B for <irtf-discuss@irtf.org>; Wed, 25 May 2011 14:37:34 -0700 (PDT)
Received: by wwc33 with SMTP id 33so75098wwc.19 for <irtf-discuss@irtf.org>; Wed, 25 May 2011 14:37:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; bh=H/qFG6LoctlAQb9mzUCcwvPEh+Px8hqlyOeEu5CG4eI=; b=WAm2ixfF5nd0a+7nhSa2U4z9zxJeOjBZZi4LuEeRI0vlsb3wCJPaeZdXlFGEvj+Gg5 h4R7uRIoXhgImQGfeiaClt2r/QUN0u4bbg7bguU4T/ZQ6i3dwhpyT1fAQBArRpKXpBdD ZF5Awfm3JMy1t4j49Ku0ox38iyC/usCHsl1aw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=oYdNbaYJ31T9jJ7AgmVIozdLUfc/z6rvjZnP6ylVMD7Eh/WIbe5F4NAOAzs5yoFTqp NePEmv0QCBd+kXyk8v516T3TPpwIFBpJgajSwT4gqFwC3qX3Pfhj2kwnWEtMwEHYiwFm /ngrpbMQyVlPzE92Ic+fg7pz0xBYjFf5u1v7U=
Received: by 10.227.58.16 with SMTP id e16mr83018wbh.13.1306359453005; Wed, 25 May 2011 14:37:33 -0700 (PDT)
Received: from [192.168.1.100] (dynamic-adsl-94-37-33-79.clienti.tiscali.it [94.37.33.79]) by mx.google.com with ESMTPS id c17sm29961wbh.46.2011.05.25.14.37.31 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 May 2011 14:37:32 -0700 (PDT)
Message-Id: <4969949F-5E5A-4D2F-A3B2-AD1ADF446AA1@gmail.com>
From: Giacomo Morabito <morabito.giacomo@gmail.com>
To: icn-interest@listserv.netlab.nec.de
In-Reply-To: <DC02A606-946C-4687-B943-3A443A2BC200@ulusofona.pt>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 25 May 2011 23:37:29 +0200
References: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com> <62C44350-6EED-4A6F-9E02-6D3F89A3097D@ulusofona.pt> <82AB329A76E2484D934BBCA77E9F524905B3FC78@PALLENE.office.hd> <DC02A606-946C-4687-B943-3A443A2BC200@ulusofona.pt>
X-Mailer: Apple Mail (2.936)
X-Mailman-Approved-At: Wed, 25 May 2011 22:47:12 -0700
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Subject: Re: [irtf-discuss] [Icn-interest] Draft ICN RG Charter
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2011 21:39:48 -0000

Dear B=F6rje and Dirk, dear all

it looks like there is not a consensus on the weight to assign to =20
different experimental methodologies (implementation in physical =20
testbeds vs. simulations).
As you know methodologies exist that can combine the two approaches so =20=

you can run simulations where some of the nodes are "physical" nodes, =20=

or create testbeds where part of the network is "simulated/emulated".
In any case I believe that this discussion confirms what I already =20
heard from B=F6rje some time ago: the community needs to reach an =20
agreement on the experimental approach so that different solutions can =20=

be compared in a consistent way.

Accordingly, I would suggest to add another milestone about this issue.
It could be something like:

"The ICNRG will produce a document that provides guidelines for =20
experimental activities in the area of ICN so that different, =20
alternative solutions can be compared consistently."

Best regards
Giacomo



Il giorno 25/mag/11, alle ore 12:42, Paulo Mendes ha scritto:

> Hi Dirk
>
> see my comments inline...
>
> On May 24, 2011, at 1:41 PM, Dirk Kutscher wrote:
>
>> Hi Paulo,
>>
>> Thanks for the suggestions. Please my some comments inline.
>>
>>> Since the list of research areas is not fully analyzed (work =20
>>> proposed
>>> to be done as first milestone) I suggest to change the first =20
>>> objective
>>> to "The main objective of the ICNRG is to advance the state of ICN
>>> research in AT LEAST the mentioned areas, focusing on solutions that
>>> are relevant for evolving the Internet at large."
>>
>> OK, I agree.
>>
>>> As for the expression "Internet at large" I would be a little more
>>> precise, including some examples in order to avoid =20
>>> misunderstandings..
>>> I would suggest "... Internet at large, including the support for =20=

>>> new
>>> services and operation into disruptive scenarios based for =20
>>> instance in
>>> the present of a considerable number of low-capacity (computational,
>>> storage) devices". The idea is to keep as an objective the =20
>>> analysis of
>>> the interaction of information-centric networking with Internet-of-
>>> services and Internet-of-connected-objects.
>>
>> Here, I really disagree. We did not want to create the notion of =20
>> different "Internets", i.e., Information-Centric, Internet-of-=20
>> Services, Internet-of-Things etc. The message is that we want to =20
>> assess ICN's applicability as a general Internet technology =20
>> ("Internet at large").
>
> I was not suggestion the creation of the notion of different =20
> "Internets", Just to say something in the charter about the =20
> applicability scenario at large... For instance, is ICNRG going to =20
> look at ICN solutions for the Internet as is it, or for the =20
> "expected" Internet which may be extended to different types of =20
> portable devices. But is all of us have this perspective in mind, =20
> than "Internet at large" is fine :)
>
>
>>
>>> I would put more emphasis to work based on implementations than
>>> simulations.. Simulations should be pointed out as acceptable to =20
>>> prove
>>> the feasibility of proposed solutions in large-scale scenarios. =20
>>> Given
>>> more importance to implementations is inline with the other =20
>>> mentioned
>>> objective of ICNRG "The ICNRG will foster the development of ICN
>>> testbeds for performing experiments with running code."
>>
>> Right, so IMO that aspect is already covered. We also said "work =20
>> that is based on implementation and simulation experiences will be =20=

>> given preference.".
>
> RIght.. The question is that this sentence givens equal preference =20
> to simulations and testbed experiences. I was suggesting to give =20
> higher preference to testbed experiences.
>
>>
>>> I would be careful with the word "architecture" since IETF/IRTF does
>>> not standardize architectures. Hence I would propose to use the
>>> following sentence...
>>>
>>> "The ICNRG will investigate components of a common protocol =20
>>> framework
>>> for information-centric networking, aiming to: i) identify protocols
>>> for standardization, which may or may not re; ii) support an ICN
>>> architecture with large applicability."
>>>
>>> ... to replace the following two sentences:
>>>
>>> "The ICNRG will identify key ICN architecture invariants across
>>> different specific approaches which could form the basis of a future
>>> ICN architecture."
>>> "The intention is that one result from this work could be a common
>>> protocol framework that can be used to identify protocols for
>>> standardization. These protocols may or may not re-use existing IETF
>>> protocols."
>>
>> OK, got your point. It's true that "form the basis of a future ICN =20=

>> architecture" can be misinterpreted.
>>
>> Here, we wanted to strike a balance: it's true that *system =20
>> architecture* work is not the IETF's core business. However, for an =20=

>> IRTF research group, we expect some architecture work to be =20
>> required, e.g., to find out about common core elements that you =20
>> need to agree on (for later protocol specifications etc.). For =20
>> example, RFC 4838 is a good example of architecture work that =20
>> describes fundamental architecture concepts for DTN, which has been =20=

>> a good basis for subsequent DTNRG work on the Bundle Protocol spec.
>>
>> Will think of a better formulation.
>
> Good.. If we are talking about RFC4838 type of work, and not a 3GPP =20=

> type of description this is expectable.
>
>>
>>
>>>
>>>
>>> B) ICNRG Milestones
>>>
>>> The charter has milestones to describe the main concepts and =20
>>> research
>>> challenges, to provide a survey of different approaches and to =20
>>> describe
>>> an ICN architecture.
>>>
>>> What is missing here is the common protocol framework mentioned =20
>>> before.
>>> So I'll add the following milestone as third one: "Based on the
>>> identified main research challenges and the analysis of different
>>> approaches, ICNRG will devise a common protocol framework for ICN,
>>> aiming to have high applicability".
>>>
>>> I would re-write the third ICNRG milestone, since saying that "...
>>> long-term goals would be documents describing an ICN =20
>>> architecture.. "
>>> since a little strange to see within IETF/IRTF work. Instead of =20
>>> saying
>>> that the goal will describe an architecture, I would suggest to say
>>> that the group will described guidelines to device an ICN =20
>>> architecture
>>> based on the common protocol framework to be devised within the =20
>>> ICNRG.
>>
>> OK, we have to remember that this is not an IETF WG charter. For a =20=

>> research group, that is really highly contribution-driven, we =20
>> should allow some flexibility. =46rom that perspective, I think it =20=

>> would be better not promise delivering guidelines to devise an =20
>> architecture. If course, that would not keep the WG from doing =20
>> that, if people are interested.
>
> OK
>
>>
>>> Somewhere in this process we should have a milestone to check the
>>> applicability of ICN, aiming to check our inline with potential
>>> standardization effort is the work to be devised in the ICNRG
>>
>> Again, normally "yes" for a tightly controlled activity, but for a =20=

>> research group, I rather see our contribution in advancing ICN and =20=

>> offering the result to the community. I would not like to have a =20
>> milestone on that.
>
> I was not proposing a very tight activity, but just a reality-check =20=

> milestone to analyze what is exactly the probability of having ICNRG =20=

> research work being ported to IETF... I like to see this reality =20
> check in any research work, from PhD thesis to EU projects :-)
>
> Cheers
>
> Paulo
>
>
>>
>> Thanks again for the comments!
>>
>> Best regards,
>>
>> Dirk
>>
>>
>>
>>
>>>
>>> Cheers
>>> Paulo
>>>
>>>
>>> On May 23, 2011, at 12:27 PM, B=F6rje Ohlman wrote:
>>>
>>>> Here is a proposal for a charter for an ICN RG. In producing this
>>> draft we have had great help from Volker Hilt, Lixia Zhang, Martin
>>> Vigoureux, Joerg Ott, Stephen Farrell and Bengt Ahlgren who has
>>> commented and made proposals for improvements. We also got some =20
>>> first
>>> positive feedback from the IRTF chair Lars Eggert.
>>>> But this does not mean that this charter is ready. There is still
>>> room for improvement, e.g. good research issues to be added. Please
>>> feel free to contribute to the discussion on this mailing list(s).
>>>> At the next IETF meeting we will present the proposal at the IRTF
>>> Open Meeting and an RG-to-be side meeting.
>>>> The side meeting could either be held in the week before the IETF
>>> meeting, with the problem that interested people might not yet be =20=

>>> there,
>>> or during the IETF week, with the problem that interested people =20
>>> might
>>> have other conflicting meetings. Any feedback on this dilemma is =20
>>> very
>>> much appreciated.
>>>>
>>>> 	B=F6rje & Dirk
>>>>
>>>> <Draft-ICN-RG-
>>> Charter.txt>_______________________________________________
>>>> Icn-interest mailing list
>>>> Icn-interest@listserv.netlab.nec.de
>>>> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest
>>>
>>> -------------------------------------------------------------
>>> Paulo Mendes, Ph.D
>>> Scientific Director for Innovation of the Research Unit in =20
>>> Informatics
>>> Systems and Technologies (SITI)
>>> Coordinator of the Internet Architecture and Networking Lab (IAN =20
>>> Lab)
>>> University Lusofona, Portugal
>>> paulo.mendes@ulusofona.pt
>>> http://siti.ulusofona.pt
>>> Tel.: 217 515 500 Fax: 21 757 7006
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Icn-interest mailing list
>>> Icn-interest@listserv.netlab.nec.de
>>> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest
>> _______________________________________________
>> Icn-interest mailing list
>> Icn-interest@listserv.netlab.nec.de
>> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest
>
> -------------------------------------------------------------
> Paulo Mendes, Ph.D
> Scientific Director for Innovation of the Research Unit in =20
> Informatics Systems and Technologies (SITI)
> Coordinator of the Internet Architecture and Networking Lab (IAN Lab)
> University Lusofona, Portugal
> paulo.mendes@ulusofona.pt
> http://siti.ulusofona.pt
> Tel.: 217 515 500 Fax: 21 757 7006
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Icn-interest mailing list
> Icn-interest@listserv.netlab.nec.de
> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest


From morabito.giacomo@gmail.com  Wed May 25 14:46:28 2011
Return-Path: <morabito.giacomo@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A794CE0802 for <irtf-discuss@ietfa.amsl.com>; Wed, 25 May 2011 14:46:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6rdFUQLImLL9 for <irtf-discuss@ietfa.amsl.com>; Wed, 25 May 2011 14:46:28 -0700 (PDT)
Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by ietfa.amsl.com (Postfix) with ESMTP id 1229BE069D for <irtf-discuss@irtf.org>; Wed, 25 May 2011 14:46:27 -0700 (PDT)
Received: by wyf23 with SMTP id 23so89623wyf.13 for <irtf-discuss@irtf.org>; Wed, 25 May 2011 14:46:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; bh=H/qFG6LoctlAQb9mzUCcwvPEh+Px8hqlyOeEu5CG4eI=; b=mOYmI/CGYu7HgzCeMu5hS21GtRYnijZML+cStZYVBJ6aAz6T2RhU3uTNw85UUUN7Qf SWCDO4qWTr1PwGtiYBMFG1ylWBYIEJQYsFC2HtGhqw/wMAHdlvacFPq5uDHU6dEsOaTz UP+QN1QgGpumAASUvDMqPSqaRw8FVtZZdlyFk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=sU2lGxyH/wjuUHhaYpKIzcs9LhKlTdK6ZdEMycTghYOKg875SS9CC1au9EMu2fOwK7 ho4VZDxl8zNiGYz1SUahdBLHPvwwImrEhRmGXpe2QM9kHzTGTQIFn+xEXKYEEdXQKWn7 yTK8Nky/1rNkFB8gnPOQcGPAP5CSWeiykG4/Q=
Received: by 10.227.37.220 with SMTP id y28mr54766wbd.82.1306359987092; Wed, 25 May 2011 14:46:27 -0700 (PDT)
Received: from [192.168.1.100] (dynamic-adsl-94-37-33-79.clienti.tiscali.it [94.37.33.79]) by mx.google.com with ESMTPS id fw15sm47360wbb.10.2011.05.25.14.46.25 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 May 2011 14:46:26 -0700 (PDT)
Message-Id: <A6AE1F30-B1A9-4235-A1A7-5BC3C615B3B0@gmail.com>
From: Giacomo Morabito <morabito.giacomo@gmail.com>
To: icn-interest@listserv.netlab.nec.de
In-Reply-To: <DC02A606-946C-4687-B943-3A443A2BC200@ulusofona.pt>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 25 May 2011 23:46:23 +0200
References: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com> <62C44350-6EED-4A6F-9E02-6D3F89A3097D@ulusofona.pt> <82AB329A76E2484D934BBCA77E9F524905B3FC78@PALLENE.office.hd> <DC02A606-946C-4687-B943-3A443A2BC200@ulusofona.pt>
X-Mailer: Apple Mail (2.936)
X-Mailman-Approved-At: Wed, 25 May 2011 22:47:12 -0700
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Subject: Re: [irtf-discuss] [Icn-interest] Draft ICN RG Charter
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2011 21:46:28 -0000

Dear B=F6rje and Dirk, dear all

it looks like there is not a consensus on the weight to assign to =20
different experimental methodologies (implementation in physical =20
testbeds vs. simulations).
As you know methodologies exist that can combine the two approaches so =20=

you can run simulations where some of the nodes are "physical" nodes, =20=

or create testbeds where part of the network is "simulated/emulated".
In any case I believe that this discussion confirms what I already =20
heard from B=F6rje some time ago: the community needs to reach an =20
agreement on the experimental approach so that different solutions can =20=

be compared in a consistent way.

Accordingly, I would suggest to add another milestone about this issue.
It could be something like:

"The ICNRG will produce a document that provides guidelines for =20
experimental activities in the area of ICN so that different, =20
alternative solutions can be compared consistently."

Best regards
Giacomo



Il giorno 25/mag/11, alle ore 12:42, Paulo Mendes ha scritto:

> Hi Dirk
>
> see my comments inline...
>
> On May 24, 2011, at 1:41 PM, Dirk Kutscher wrote:
>
>> Hi Paulo,
>>
>> Thanks for the suggestions. Please my some comments inline.
>>
>>> Since the list of research areas is not fully analyzed (work =20
>>> proposed
>>> to be done as first milestone) I suggest to change the first =20
>>> objective
>>> to "The main objective of the ICNRG is to advance the state of ICN
>>> research in AT LEAST the mentioned areas, focusing on solutions that
>>> are relevant for evolving the Internet at large."
>>
>> OK, I agree.
>>
>>> As for the expression "Internet at large" I would be a little more
>>> precise, including some examples in order to avoid =20
>>> misunderstandings..
>>> I would suggest "... Internet at large, including the support for =20=

>>> new
>>> services and operation into disruptive scenarios based for =20
>>> instance in
>>> the present of a considerable number of low-capacity (computational,
>>> storage) devices". The idea is to keep as an objective the =20
>>> analysis of
>>> the interaction of information-centric networking with Internet-of-
>>> services and Internet-of-connected-objects.
>>
>> Here, I really disagree. We did not want to create the notion of =20
>> different "Internets", i.e., Information-Centric, Internet-of-=20
>> Services, Internet-of-Things etc. The message is that we want to =20
>> assess ICN's applicability as a general Internet technology =20
>> ("Internet at large").
>
> I was not suggestion the creation of the notion of different =20
> "Internets", Just to say something in the charter about the =20
> applicability scenario at large... For instance, is ICNRG going to =20
> look at ICN solutions for the Internet as is it, or for the =20
> "expected" Internet which may be extended to different types of =20
> portable devices. But is all of us have this perspective in mind, =20
> than "Internet at large" is fine :)
>
>
>>
>>> I would put more emphasis to work based on implementations than
>>> simulations.. Simulations should be pointed out as acceptable to =20
>>> prove
>>> the feasibility of proposed solutions in large-scale scenarios. =20
>>> Given
>>> more importance to implementations is inline with the other =20
>>> mentioned
>>> objective of ICNRG "The ICNRG will foster the development of ICN
>>> testbeds for performing experiments with running code."
>>
>> Right, so IMO that aspect is already covered. We also said "work =20
>> that is based on implementation and simulation experiences will be =20=

>> given preference.".
>
> RIght.. The question is that this sentence givens equal preference =20
> to simulations and testbed experiences. I was suggesting to give =20
> higher preference to testbed experiences.
>
>>
>>> I would be careful with the word "architecture" since IETF/IRTF does
>>> not standardize architectures. Hence I would propose to use the
>>> following sentence...
>>>
>>> "The ICNRG will investigate components of a common protocol =20
>>> framework
>>> for information-centric networking, aiming to: i) identify protocols
>>> for standardization, which may or may not re; ii) support an ICN
>>> architecture with large applicability."
>>>
>>> ... to replace the following two sentences:
>>>
>>> "The ICNRG will identify key ICN architecture invariants across
>>> different specific approaches which could form the basis of a future
>>> ICN architecture."
>>> "The intention is that one result from this work could be a common
>>> protocol framework that can be used to identify protocols for
>>> standardization. These protocols may or may not re-use existing IETF
>>> protocols."
>>
>> OK, got your point. It's true that "form the basis of a future ICN =20=

>> architecture" can be misinterpreted.
>>
>> Here, we wanted to strike a balance: it's true that *system =20
>> architecture* work is not the IETF's core business. However, for an =20=

>> IRTF research group, we expect some architecture work to be =20
>> required, e.g., to find out about common core elements that you =20
>> need to agree on (for later protocol specifications etc.). For =20
>> example, RFC 4838 is a good example of architecture work that =20
>> describes fundamental architecture concepts for DTN, which has been =20=

>> a good basis for subsequent DTNRG work on the Bundle Protocol spec.
>>
>> Will think of a better formulation.
>
> Good.. If we are talking about RFC4838 type of work, and not a 3GPP =20=

> type of description this is expectable.
>
>>
>>
>>>
>>>
>>> B) ICNRG Milestones
>>>
>>> The charter has milestones to describe the main concepts and =20
>>> research
>>> challenges, to provide a survey of different approaches and to =20
>>> describe
>>> an ICN architecture.
>>>
>>> What is missing here is the common protocol framework mentioned =20
>>> before.
>>> So I'll add the following milestone as third one: "Based on the
>>> identified main research challenges and the analysis of different
>>> approaches, ICNRG will devise a common protocol framework for ICN,
>>> aiming to have high applicability".
>>>
>>> I would re-write the third ICNRG milestone, since saying that "...
>>> long-term goals would be documents describing an ICN =20
>>> architecture.. "
>>> since a little strange to see within IETF/IRTF work. Instead of =20
>>> saying
>>> that the goal will describe an architecture, I would suggest to say
>>> that the group will described guidelines to device an ICN =20
>>> architecture
>>> based on the common protocol framework to be devised within the =20
>>> ICNRG.
>>
>> OK, we have to remember that this is not an IETF WG charter. For a =20=

>> research group, that is really highly contribution-driven, we =20
>> should allow some flexibility. =46rom that perspective, I think it =20=

>> would be better not promise delivering guidelines to devise an =20
>> architecture. If course, that would not keep the WG from doing =20
>> that, if people are interested.
>
> OK
>
>>
>>> Somewhere in this process we should have a milestone to check the
>>> applicability of ICN, aiming to check our inline with potential
>>> standardization effort is the work to be devised in the ICNRG
>>
>> Again, normally "yes" for a tightly controlled activity, but for a =20=

>> research group, I rather see our contribution in advancing ICN and =20=

>> offering the result to the community. I would not like to have a =20
>> milestone on that.
>
> I was not proposing a very tight activity, but just a reality-check =20=

> milestone to analyze what is exactly the probability of having ICNRG =20=

> research work being ported to IETF... I like to see this reality =20
> check in any research work, from PhD thesis to EU projects :-)
>
> Cheers
>
> Paulo
>
>
>>
>> Thanks again for the comments!
>>
>> Best regards,
>>
>> Dirk
>>
>>
>>
>>
>>>
>>> Cheers
>>> Paulo
>>>
>>>
>>> On May 23, 2011, at 12:27 PM, B=F6rje Ohlman wrote:
>>>
>>>> Here is a proposal for a charter for an ICN RG. In producing this
>>> draft we have had great help from Volker Hilt, Lixia Zhang, Martin
>>> Vigoureux, Joerg Ott, Stephen Farrell and Bengt Ahlgren who has
>>> commented and made proposals for improvements. We also got some =20
>>> first
>>> positive feedback from the IRTF chair Lars Eggert.
>>>> But this does not mean that this charter is ready. There is still
>>> room for improvement, e.g. good research issues to be added. Please
>>> feel free to contribute to the discussion on this mailing list(s).
>>>> At the next IETF meeting we will present the proposal at the IRTF
>>> Open Meeting and an RG-to-be side meeting.
>>>> The side meeting could either be held in the week before the IETF
>>> meeting, with the problem that interested people might not yet be =20=

>>> there,
>>> or during the IETF week, with the problem that interested people =20
>>> might
>>> have other conflicting meetings. Any feedback on this dilemma is =20
>>> very
>>> much appreciated.
>>>>
>>>> 	B=F6rje & Dirk
>>>>
>>>> <Draft-ICN-RG-
>>> Charter.txt>_______________________________________________
>>>> Icn-interest mailing list
>>>> Icn-interest@listserv.netlab.nec.de
>>>> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest
>>>
>>> -------------------------------------------------------------
>>> Paulo Mendes, Ph.D
>>> Scientific Director for Innovation of the Research Unit in =20
>>> Informatics
>>> Systems and Technologies (SITI)
>>> Coordinator of the Internet Architecture and Networking Lab (IAN =20
>>> Lab)
>>> University Lusofona, Portugal
>>> paulo.mendes@ulusofona.pt
>>> http://siti.ulusofona.pt
>>> Tel.: 217 515 500 Fax: 21 757 7006
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Icn-interest mailing list
>>> Icn-interest@listserv.netlab.nec.de
>>> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest
>> _______________________________________________
>> Icn-interest mailing list
>> Icn-interest@listserv.netlab.nec.de
>> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest
>
> -------------------------------------------------------------
> Paulo Mendes, Ph.D
> Scientific Director for Innovation of the Research Unit in =20
> Informatics Systems and Technologies (SITI)
> Coordinator of the Internet Architecture and Networking Lab (IAN Lab)
> University Lusofona, Portugal
> paulo.mendes@ulusofona.pt
> http://siti.ulusofona.pt
> Tel.: 217 515 500 Fax: 21 757 7006
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Icn-interest mailing list
> Icn-interest@listserv.netlab.nec.de
> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest


From borje.ohlman@ericsson.com  Thu May 26 01:03:14 2011
Return-Path: <borje.ohlman@ericsson.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9576CE068F for <irtf-discuss@ietfa.amsl.com>; Thu, 26 May 2011 01:03:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.9
X-Spam-Level: 
X-Spam-Status: No, score=-5.9 tagged_above=-999 required=5 tests=[AWL=-0.400,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DWpWwUDESf-j for <irtf-discuss@ietfa.amsl.com>; Thu, 26 May 2011 01:03:13 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id AEF23E065B for <irtf-discuss@irtf.org>; Thu, 26 May 2011 01:03:12 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c17ae00000262e-28-4dde093f03ae
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id F6.FE.09774.F390EDD4; Thu, 26 May 2011 10:03:11 +0200 (CEST)
Received: from dhcp-147-214-75-143.ki.sw.ericsson.se (153.88.115.8) by smtps.internal.ericsson.com (153.88.115.90) with Microsoft SMTP Server id 8.3.137.0; Thu, 26 May 2011 10:03:10 +0200
MIME-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: =?iso-8859-1?Q?B=F6rje_Ohlman?= <Borje.Ohlman@ericsson.com>
In-Reply-To: <4969949F-5E5A-4D2F-A3B2-AD1ADF446AA1@gmail.com>
Date: Thu, 26 May 2011 10:03:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-ID: <B332C6E2-45B4-443D-824A-6C8B047F7D85@ericsson.com>
References: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com> <62C44350-6EED-4A6F-9E02-6D3F89A3097D@ulusofona.pt> <82AB329A76E2484D934BBCA77E9F524905B3FC78@PALLENE.office.hd> <DC02A606-946C-4687-B943-3A443A2BC200@ulusofona.pt> <4969949F-5E5A-4D2F-A3B2-AD1ADF446AA1@gmail.com>
To: Giacomo Morabito <morabito.giacomo@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Brightmail-Tracker: AAAAAA==
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "icn-interest@listserv.netlab.nec.de" <icn-interest@listserv.netlab.nec.de>
Subject: Re: [irtf-discuss] [Icn-interest] Draft ICN RG Charter
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2011 08:03:14 -0000

Hi Giacomo,

I think this is a good proposal which I do support. If people agree I =
will add this to the charter when I do the next update (probably this =
weekend).
I will also go through all the mails and do all uncontroversial updates, =
e.g. improved formulations, special thanks to Holger on that account.
BTW, from then on the charter for the proposed ICN RG will be available =
at the Wiki page
http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg

	B=F6rje

On 25 maj 2011, at 23.37, Giacomo Morabito wrote:

> Dear B=F6rje and Dirk, dear all
>=20
> it looks like there is not a consensus on the weight to assign to
> different experimental methodologies (implementation in physical
> testbeds vs. simulations).
> As you know methodologies exist that can combine the two approaches so
> you can run simulations where some of the nodes are "physical" nodes,
> or create testbeds where part of the network is "simulated/emulated".
> In any case I believe that this discussion confirms what I already
> heard from B=F6rje some time ago: the community needs to reach an
> agreement on the experimental approach so that different solutions can
> be compared in a consistent way.
>=20
> Accordingly, I would suggest to add another milestone about this =
issue.
> It could be something like:
>=20
> "The ICNRG will produce a document that provides guidelines for
> experimental activities in the area of ICN so that different,
> alternative solutions can be compared consistently."
>=20
> Best regards
> Giacomo
>=20
>=20
>=20
> Il giorno 25/mag/11, alle ore 12:42, Paulo Mendes ha scritto:
>=20
>> Hi Dirk
>>=20
>> see my comments inline...
>>=20
>> On May 24, 2011, at 1:41 PM, Dirk Kutscher wrote:
>>=20
>>> Hi Paulo,
>>>=20
>>> Thanks for the suggestions. Please my some comments inline.
>>>=20
>>>> Since the list of research areas is not fully analyzed (work
>>>> proposed
>>>> to be done as first milestone) I suggest to change the first
>>>> objective
>>>> to "The main objective of the ICNRG is to advance the state of ICN
>>>> research in AT LEAST the mentioned areas, focusing on solutions =
that
>>>> are relevant for evolving the Internet at large."
>>>=20
>>> OK, I agree.
>>>=20
>>>> As for the expression "Internet at large" I would be a little more
>>>> precise, including some examples in order to avoid
>>>> misunderstandings..
>>>> I would suggest "... Internet at large, including the support for
>>>> new
>>>> services and operation into disruptive scenarios based for
>>>> instance in
>>>> the present of a considerable number of low-capacity =
(computational,
>>>> storage) devices". The idea is to keep as an objective the
>>>> analysis of
>>>> the interaction of information-centric networking with Internet-of-
>>>> services and Internet-of-connected-objects.
>>>=20
>>> Here, I really disagree. We did not want to create the notion of
>>> different "Internets", i.e., Information-Centric, Internet-of-
>>> Services, Internet-of-Things etc. The message is that we want to
>>> assess ICN's applicability as a general Internet technology
>>> ("Internet at large").
>>=20
>> I was not suggestion the creation of the notion of different
>> "Internets", Just to say something in the charter about the
>> applicability scenario at large... For instance, is ICNRG going to
>> look at ICN solutions for the Internet as is it, or for the
>> "expected" Internet which may be extended to different types of
>> portable devices. But is all of us have this perspective in mind,
>> than "Internet at large" is fine :)
>>=20
>>=20
>>>=20
>>>> I would put more emphasis to work based on implementations than
>>>> simulations.. Simulations should be pointed out as acceptable to
>>>> prove
>>>> the feasibility of proposed solutions in large-scale scenarios.
>>>> Given
>>>> more importance to implementations is inline with the other
>>>> mentioned
>>>> objective of ICNRG "The ICNRG will foster the development of ICN
>>>> testbeds for performing experiments with running code."
>>>=20
>>> Right, so IMO that aspect is already covered. We also said "work
>>> that is based on implementation and simulation experiences will be
>>> given preference.".
>>=20
>> RIght.. The question is that this sentence givens equal preference
>> to simulations and testbed experiences. I was suggesting to give
>> higher preference to testbed experiences.
>>=20
>>>=20
>>>> I would be careful with the word "architecture" since IETF/IRTF =
does
>>>> not standardize architectures. Hence I would propose to use the
>>>> following sentence...
>>>>=20
>>>> "The ICNRG will investigate components of a common protocol
>>>> framework
>>>> for information-centric networking, aiming to: i) identify =
protocols
>>>> for standardization, which may or may not re; ii) support an ICN
>>>> architecture with large applicability."
>>>>=20
>>>> ... to replace the following two sentences:
>>>>=20
>>>> "The ICNRG will identify key ICN architecture invariants across
>>>> different specific approaches which could form the basis of a =
future
>>>> ICN architecture."
>>>> "The intention is that one result from this work could be a common
>>>> protocol framework that can be used to identify protocols for
>>>> standardization. These protocols may or may not re-use existing =
IETF
>>>> protocols."
>>>=20
>>> OK, got your point. It's true that "form the basis of a future ICN
>>> architecture" can be misinterpreted.
>>>=20
>>> Here, we wanted to strike a balance: it's true that *system
>>> architecture* work is not the IETF's core business. However, for an
>>> IRTF research group, we expect some architecture work to be
>>> required, e.g., to find out about common core elements that you
>>> need to agree on (for later protocol specifications etc.). For
>>> example, RFC 4838 is a good example of architecture work that
>>> describes fundamental architecture concepts for DTN, which has been
>>> a good basis for subsequent DTNRG work on the Bundle Protocol spec.
>>>=20
>>> Will think of a better formulation.
>>=20
>> Good.. If we are talking about RFC4838 type of work, and not a 3GPP
>> type of description this is expectable.
>>=20
>>>=20
>>>=20
>>>>=20
>>>>=20
>>>> B) ICNRG Milestones
>>>>=20
>>>> The charter has milestones to describe the main concepts and
>>>> research
>>>> challenges, to provide a survey of different approaches and to
>>>> describe
>>>> an ICN architecture.
>>>>=20
>>>> What is missing here is the common protocol framework mentioned
>>>> before.
>>>> So I'll add the following milestone as third one: "Based on the
>>>> identified main research challenges and the analysis of different
>>>> approaches, ICNRG will devise a common protocol framework for ICN,
>>>> aiming to have high applicability".
>>>>=20
>>>> I would re-write the third ICNRG milestone, since saying that "...
>>>> long-term goals would be documents describing an ICN
>>>> architecture.. "
>>>> since a little strange to see within IETF/IRTF work. Instead of
>>>> saying
>>>> that the goal will describe an architecture, I would suggest to say
>>>> that the group will described guidelines to device an ICN
>>>> architecture
>>>> based on the common protocol framework to be devised within the
>>>> ICNRG.
>>>=20
>>> OK, we have to remember that this is not an IETF WG charter. For a
>>> research group, that is really highly contribution-driven, we
>>> should allow some flexibility. =46rom that perspective, I think it
>>> would be better not promise delivering guidelines to devise an
>>> architecture. If course, that would not keep the WG from doing
>>> that, if people are interested.
>>=20
>> OK
>>=20
>>>=20
>>>> Somewhere in this process we should have a milestone to check the
>>>> applicability of ICN, aiming to check our inline with potential
>>>> standardization effort is the work to be devised in the ICNRG
>>>=20
>>> Again, normally "yes" for a tightly controlled activity, but for a
>>> research group, I rather see our contribution in advancing ICN and
>>> offering the result to the community. I would not like to have a
>>> milestone on that.
>>=20
>> I was not proposing a very tight activity, but just a reality-check
>> milestone to analyze what is exactly the probability of having ICNRG
>> research work being ported to IETF... I like to see this reality
>> check in any research work, from PhD thesis to EU projects :-)
>>=20
>> Cheers
>>=20
>> Paulo
>>=20
>>=20
>>>=20
>>> Thanks again for the comments!
>>>=20
>>> Best regards,
>>>=20
>>> Dirk
>>>=20
>>>=20
>>>=20
>>>=20
>>>>=20
>>>> Cheers
>>>> Paulo
>>>>=20
>>>>=20
>>>> On May 23, 2011, at 12:27 PM, B=F6rje Ohlman wrote:
>>>>=20
>>>>> Here is a proposal for a charter for an ICN RG. In producing this
>>>> draft we have had great help from Volker Hilt, Lixia Zhang, Martin
>>>> Vigoureux, Joerg Ott, Stephen Farrell and Bengt Ahlgren who has
>>>> commented and made proposals for improvements. We also got some
>>>> first
>>>> positive feedback from the IRTF chair Lars Eggert.
>>>>> But this does not mean that this charter is ready. There is still
>>>> room for improvement, e.g. good research issues to be added. Please
>>>> feel free to contribute to the discussion on this mailing list(s).
>>>>> At the next IETF meeting we will present the proposal at the IRTF
>>>> Open Meeting and an RG-to-be side meeting.
>>>>> The side meeting could either be held in the week before the IETF
>>>> meeting, with the problem that interested people might not yet be
>>>> there,
>>>> or during the IETF week, with the problem that interested people
>>>> might
>>>> have other conflicting meetings. Any feedback on this dilemma is
>>>> very
>>>> much appreciated.
>>>>>=20
>>>>>   B=F6rje & Dirk
>>>>>=20
>>>>> <Draft-ICN-RG-
>>>> Charter.txt>_______________________________________________
>>>>> Icn-interest mailing list
>>>>> Icn-interest@listserv.netlab.nec.de
>>>>> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest
>>>>=20
>>>> -------------------------------------------------------------
>>>> Paulo Mendes, Ph.D
>>>> Scientific Director for Innovation of the Research Unit in
>>>> Informatics
>>>> Systems and Technologies (SITI)
>>>> Coordinator of the Internet Architecture and Networking Lab (IAN
>>>> Lab)
>>>> University Lusofona, Portugal
>>>> paulo.mendes@ulusofona.pt
>>>> http://siti.ulusofona.pt
>>>> Tel.: 217 515 500 Fax: 21 757 7006
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> Icn-interest mailing list
>>>> Icn-interest@listserv.netlab.nec.de
>>>> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest
>>> _______________________________________________
>>> Icn-interest mailing list
>>> Icn-interest@listserv.netlab.nec.de
>>> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest
>>=20
>> -------------------------------------------------------------
>> Paulo Mendes, Ph.D
>> Scientific Director for Innovation of the Research Unit in
>> Informatics Systems and Technologies (SITI)
>> Coordinator of the Internet Architecture and Networking Lab (IAN Lab)
>> University Lusofona, Portugal
>> paulo.mendes@ulusofona.pt
>> http://siti.ulusofona.pt
>> Tel.: 217 515 500 Fax: 21 757 7006
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> Icn-interest mailing list
>> Icn-interest@listserv.netlab.nec.de
>> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest
>=20


From Dirk.Kutscher@neclab.eu  Thu May 26 01:17:06 2011
Return-Path: <Dirk.Kutscher@neclab.eu>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8E37E067B for <irtf-discuss@ietfa.amsl.com>; Thu, 26 May 2011 01:17:06 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aSqLTXbjFfY7 for <irtf-discuss@ietfa.amsl.com>; Thu, 26 May 2011 01:17:06 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by ietfa.amsl.com (Postfix) with ESMTP id 44667E0671 for <irtf-discuss@irtf.org>; Thu, 26 May 2011 01:17:06 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id 5E6A82C000148; Thu, 26 May 2011 10:17:05 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office.hd)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vOGHyf2tbDGG; Thu, 26 May 2011 10:17:05 +0200 (CEST)
Received: by smtp0.neclab.eu (Postfix, from userid 1001) id 3D3382C00008C; Thu, 26 May 2011 10:17:05 +0200 (CEST)
Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by smtp0.neclab.eu (Postfix) with ESMTP id E6E722C000148; Thu, 26 May 2011 10:16:49 +0200 (CEST)
Received: from PALLENE.office.hd ([169.254.1.225]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0270.001; Thu, 26 May 2011 10:16:50 +0200
From: Dirk Kutscher <Dirk.Kutscher@neclab.eu>
To: "icn-interest@listserv.netlab.nec.de" <icn-interest@listserv.netlab.nec.de>
Thread-Topic: [Icn-interest] Draft ICN RG Charter
Thread-Index: AQHMGTxrvltMJilX+kKiz2CyondNKZSb1viAgALu9eA=
Date: Thu, 26 May 2011 08:16:48 +0000
Message-ID: <82AB329A76E2484D934BBCA77E9F524905B43F87@PALLENE.office.hd>
References: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com> <4DDBB0D7.5080006@mhof.com>
In-Reply-To: <4DDBB0D7.5080006@mhof.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.2.105]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Subject: Re: [irtf-discuss] [Icn-interest] Draft ICN RG Charter
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2011 08:17:07 -0000

Markus,

> What about including a summary of the expected benefits of ICN, i.e.
> first describe the *problem* to be solved in *quantifiable* terms, then
> describe the main concepts and continue on to the research challenges.

Thanks, good point.

I'd preferably do that in more detail, in a problem statement draft, but I =
agree that the charter should ideally provide at least a summary for that.

Best regards,

Dirk

From markus@mhof.com  Thu May 26 03:59:18 2011
Return-Path: <markus@mhof.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDE3DE06BF for <irtf-discuss@ietfa.amsl.com>; Thu, 26 May 2011 03:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26TOIHaHq6oZ for <irtf-discuss@ietfa.amsl.com>; Thu, 26 May 2011 03:59:18 -0700 (PDT)
Received: from smtp116.iad.emailsrvr.com (smtp116.iad.emailsrvr.com [207.97.245.116]) by ietfa.amsl.com (Postfix) with ESMTP id 1C043E0664 for <irtf-discuss@irtf.org>; Thu, 26 May 2011 03:59:18 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp41.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id A821E2904B9; Thu, 26 May 2011 06:59:17 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp41.relay.iad1a.emailsrvr.com (Authenticated sender: markus-AT-mhof.com) with ESMTPSA id 772812900EB;  Thu, 26 May 2011 06:59:17 -0400 (EDT)
References: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com> <4DDBB0D7.5080006@mhof.com> <82AB329A76E2484D934BBCA77E9F524905B43F87@PALLENE.office.hd>
In-Reply-To: <82AB329A76E2484D934BBCA77E9F524905B43F87@PALLENE.office.hd>
Mime-Version: 1.0 (iPad Mail 8J3)
Content-Type: text/plain; charset=us-ascii
Message-Id: <23000241-B5B1-4B5C-8F77-A96A19A63C06@mhof.com>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (8J3)
From: Markus Hofmann <markus@mhof.com>
Date: Thu, 26 May 2011 06:59:52 -0400
To: "icn-interest@listserv.netlab.nec.de" <icn-interest@listserv.netlab.nec.de>
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "icn-interest@listserv.netlab.nec.de" <icn-interest@listserv.netlab.nec.de>
Subject: Re: [irtf-discuss] [Icn-interest] Draft ICN RG Charter
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2011 10:59:19 -0000

Dirk,

That's what I meant - include in the charter the preparation of a problem st=
atement draft as a deliverable. Not to include the summary itself in the cha=
rter.

Thanks,
  Markus

On May 26, 2011, at 4:16 AM, Dirk Kutscher <Dirk.Kutscher@neclab.eu> wrote:

> Markus,
>=20
>> What about including a summary of the expected benefits of ICN, i.e.
>> first describe the *problem* to be solved in *quantifiable* terms, then
>> describe the main concepts and continue on to the research challenges.
>=20
> Thanks, good point.
>=20
> I'd preferably do that in more detail, in a problem statement draft, but I=
 agree that the charter should ideally provide at least a summary for that.
>=20
> Best regards,
>=20
> Dirk
> _______________________________________________
> Icn-interest mailing list
> Icn-interest@listserv.netlab.nec.de
> https://listserv.netlab.nec.de/mailman/listinfo/icn-interest
