
From hassnaa.moustafa@intel.com  Mon Nov  4 05:02:55 2013
Return-Path: <hassnaa.moustafa@intel.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8295111E81B2 for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 05:02:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iv21BcawpZoA for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 05:02:51 -0800 (PST)
Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by ietfa.amsl.com (Postfix) with ESMTP id E492911E81A2 for <pcp@ietf.org>; Mon,  4 Nov 2013 05:02:48 -0800 (PST)
Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 04 Nov 2013 05:02:48 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.93,535,1378882800"; d="scan'208";a="384383674"
Received: from orsmsx103.amr.corp.intel.com ([10.22.225.130]) by azsmga001.ch.intel.com with ESMTP; 04 Nov 2013 05:02:47 -0800
Received: from orsmsx102.amr.corp.intel.com ([169.254.1.203]) by ORSMSX103.amr.corp.intel.com ([169.254.2.55]) with mapi id 14.03.0123.003; Mon, 4 Nov 2013 05:02:47 -0800
From: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: Ac7ZXRwLNJWMJz/iQNuoFr8x9AR4gw==
Date: Mon, 4 Nov 2013 13:02:46 +0000
Message-ID: <F893BEC192403B489DBA38999068CF190594847F@ORSMSX102.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.22.254.139]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2013 13:02:55 -0000

SGkgQWxsLA0KDQpEcmFmdCAoZHJhZnQtbW91LXBjcC1hcHBsaWNhdGlvbi1uZXR3b3JrLWZlZWRi
YWNrKSBpcyBhIG5ldyBkcmFmdCB0aGF0IGlzIHN1Ym1pdHRlZCB0b2RheSBvbiAoUENQIEV4dGVu
c2lvbiBmb3IgU2lnbmFsaW5nIEZlZWRiYWNrIEluZm9ybWF0aW9uIGZyb20gdGhlIEVuZC1Vc2Vy
IEFwcGxpY2F0aW9uIHRvIHRoZSBBcHBsaWNhdGlvbiBTZXZlciBhbmQgdG8gdGhlIE5ldHdvcmsp
LiANCg0KVGhlIGRyYWZ0IGlzIGF2YWlsYWJsZSBhdCA6ICAgICAgICAgICAgIGh0dHA6Ly93d3cu
aWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LW1vdS1wY3AtYXBwbGljYXRpb24tbmV0d29y
ay1mZWVkYmFjay0wMC50eHQNCg0KVGhpcyBkcmFmdCBhZGRyZXNzZXMgdGhlIG5lZWQgZm9yIG1v
cmUgaW50ZWxsaWdlbmNlIGluIHRoZSBuZXR3b3JrIGFuZCBzZXJ2aWNlIGluZnJhc3RydWN0dXJl
IGZvciBiZXR0ZXIgY29udGVudCBkZWxpdmVyeSB0byBvcHRpbWl6ZSB0aGUgbmV0d29yayBhbmQg
ZGV2aWNlcyByZXNvdXJjZXMuIEluIHRoaXMgdmlldywgdGhlIGRyYWZ0IHByb3Bvc2VzIHVzaW5n
IFBDUCB0byBzaWduYWwgaW5mb3JtYXRpb24gZm9yOiBpKSAgS25vd2xlZGdlIGluIHRoZSBuZXR3
b3JrIGFuZCBzZXJ2aWNlIHBsYXRmb3JtIGFib3V0IHRoZSBhdmFpbGFibGUgZGV2aWNlIGFuZCBu
ZXR3b3JrIGNvbmRpdGlvbnMgZm9yIHRoZSBlbmQtdXNlciBhbmQgaWkpIEtub3dsZWRnZSBpbiB0
aGUgbmV0d29yayBhYm91dCB0aGUgY29udGVudCByZXF1aXJlbWVudHMgaW4gdGVybXMgb2YgZGV2
aWNlcyBhbmQgIG5ldHdvcmsgcmVzb3VyY2VzIGZvciBjb250ZW50IHN0b3JlZCBlaXRoZXIgaW4g
dGhlIG5ldHdvcmsgb3IgaW4gdGhlIGFwcGxpY2F0aW9uIHNlcnZlci4NCg0KVGhlIGFic3RyYWN0
IG9mIHRoZSBkcmFmdCBpcyBhcyBmb2xsb3dzOg0KIiBBYnN0cmFjdDogICAgTm93YWRheXMgdXNl
cnMgY29uc3VtcHRpb24gc3R5bGUgZm9yIHZpZGVvIGFuZCBtdWx0aW1lZGlhICBhcHBsaWNhdGlv
bnMgaXMgc3Ryb25nbHkgY2hhbmdpbmcuICBVc2VycyBhcmUgaGVhdmlseSBjb3VudGluZyBvbiAg
d2lyZWxlc3MgYW5kIG1vYmlsZSBkZXZpY2VzIGZvciB2aWRlbyBzdHJlYW1pbmcgYW5kIGludGVy
YWN0aXZlIHZpZGVvDQogICBhbmQgbXVsdGltZWRpYSBhcHBsaWNhdGlvbnMuICBUaGlzIGNhbiBi
ZSBpbXBsZW1lbnRlZCBmb3IgaW5zdGFuY2UgYnkgaGF2aW5nIG1vcmUgaW50ZWxsaWdlbmNlIGlu
IHRoZSBzZXJ2aWNlIGFuZCB0aGUgbmV0d29yayBpbmZyYXN0cnVjdHVyZSB0byBiZXR0ZXIgc3Vp
dCBhIGRpZmZlcmVudGlhdGVkIHVzZXJzIGNvbnN1bXB0aW9uICBzdHlsZS4gIFRoaXMgY2FuIGJl
IGFjaGlldmVkIA0KICAgdGhyb3VnaCBoYXZpbmc6IChpKSBhIGtub3dsZWRnZSBpbiB0aGUgbmV0
d29yayBhbmQgc2VydmljZSBwbGF0Zm9ybSBhYm91dCB0aGUgYXZhaWxhYmxlIGRldmljZSBhbmQg
bmV0d29yayBjb25kaXRpb25zIGZvciB0aGUgZW5kLXVzZXIgYW5kIChpaSkgYSBrbm93bGVkZ2Ug
aW4gdGhlIG5ldHdvcmsgYWJvdXQgdGhlIGNvbnRlbnQgcmVxdWlyZW1lbnRzIGluIHRlcm1zIG9m
IGRldmljZXMNCiAgIGNhcGFiaWxpdGllcyBhbmQgbmV0d29yayByZXNvdXJjZXMgZm9yIGNvbnRl
bnQgc3RvcmVkIGVpdGhlciBpbiB0aGUgbmV0d29yayBvciBpbiB0aGUgYXBwbGljYXRpb24gc2Vy
dmVyLiAgVG8gb2J0YWluIHN1Y2gga25vd2xlZGdlIHdpdGggbm8gbmVlZCBmb3IgIGNoYW5naW5n
IHRoZSBjdXJyZW50IGluZnJhc3RydWN0dXJlIGFuZCBpbiBhIGdlbmVyYWxpemVkIHdheSB0byBh
bGwNCiAgIGFwcGxpY2F0aW9ucywgZmVlZGJhY2svbm90aWZpY2F0aW9uIG1lY2hhbmlzbXMgYmV0
d2VlbiB0aGUgZW5kLXVzZXIgYXBwbGljYXRpb24sIHRoZSBuZXR3b3JrIGFuZCB0aGUgc2Vydmlj
ZSBwbGF0Zm9ybSBpcyBuZWVkZWQgdG8gcHJvdmlkZSBpbmZvcm1hdGlvbiBoZWxwaW5nIHRoZSBj
b250ZW50IGRlbGl2ZXJ5IGFuZCBhZGFwdGF0aW9uIGRlY2lzaW9ucy4gIFRoaXMgZG9jdW1lbnQg
DQogICAgaXMgaW52ZXN0aWdhdGluZyBzdWNoIGFwcGxpY2F0aW9uLWFnbm9zdGljIHRyYWNrLg0K
DQogICBUaGlzIGRvY3VtZW50IGV4dGVuZHMgdGhlIFBvcnQgQ29udHJvbCBQcm90b2NvbCAoUENQ
KSBSRkMgNjg4NyAgW1JGQzY4ODddIHRvIGFsbG93OiAoaSkgdGhlIHVzZXJzIGFwcGxpY2F0aW9u
IHRvIG5vdGlmeSB0aGUgbmV0d29yayBhbmQgYXBwbGljYXRpb24gc2VydmVyIGFib3V0IGl0cyBh
dmFpbGFibGUgcmVzb3VyY2VzIGluIHRlcm1zIG9mDQogICBkZXZpY2VzIGNhcGFiaWxpdGllcyBh
bmQgbmV0d29yayBjb25kaXRpb25zIGFzIHdlbGwgYXMgaW5mb3JtYXRpb24gYWJvdXQgdGhlIHVz
ZXIgKGUuZy4sIGxvY2F0aW9uLCBtb2JpbGl0eSBzdGF0dXMpIGFuZCAoaWkpIHRoZSBhcHBsaWNh
dGlvbiBzZXJ2ZXIgdG8gbm90aWZ5IHRoZSBuZXR3b3JrIGFib3V0IHRoZSByZXF1aXJlbWVudHMg
b2YNCiAgIHRoZSBjb250ZW50IGl0IHN0b3JlcyBpbiB0ZXJtcyBvZiBkZXZpY2VzIGFuZCBuZXR3
b3JrIHJlc291cmNlcy4gIEEgbmV3IFBDUCBvcHRpb24sIGRlbm90ZWQgdGhlIEZFRURCQUNLLCBp
cyBzcGVjaWZpZWQgdG8gYWxsb3cgc3VjaCBmZWVkYmFjayBub3RpZmljYXRpb24gc2lnbmFsaW5n
LiAgVGhpcyBvcHRpb24gaXMgdXNlZCB3aXRoIGJvdGggUEVFUg0KICAgYW5kIE1BUCBPcGNvZGVz
LiINCg0KTG9va2luZyBmb3J3YXJkIHRvIGhhdmluZyB5b3VyIGZlZWRiYWNrIGFuZCBtb3JlIGRp
c2N1c3Npb24gb24gdGhpcyBkcmFmdC4NCg0KUmVnYXJkcywNCkhhc3NuYWENCg0KDQoNCi0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21h
aWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmddIA0KU2VudDogTW9uZGF5LCBOb3ZlbWJlciAw
NCwgMjAxMyA0OjA2IEFNDQpUbzogTW9oYW1lZCBCb3VjYWRhaXI7IE1vdXN0YWZhLCBIYXNzbmFh
OyBNb3NlcywgRGFubnkNClN1YmplY3Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJh
ZnQtbW91LXBjcC1hcHBsaWNhdGlvbi1uZXR3b3JrLWZlZWRiYWNrLTAwLnR4dA0KDQoNCkEgbmV3
IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1tb3UtcGNwLWFwcGxpY2F0aW9uLW5ldHdvcmstZmVlZGJh
Y2stMDAudHh0DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IEhhc3NuYWEgTW91
c3RhZmEgYW5kIHBvc3RlZCB0byB0aGUgSUVURiByZXBvc2l0b3J5Lg0KDQpGaWxlbmFtZToJIGRy
YWZ0LW1vdS1wY3AtYXBwbGljYXRpb24tbmV0d29yay1mZWVkYmFjaw0KUmV2aXNpb246CSAwMA0K
VGl0bGU6CQkgUENQIEV4dGVuc2lvbiBmb3IgU2lnbmFsaW5nIEZlZWRiYWNrIEluZm9ybWF0aW9u
IGZyb20gdGhlIEVuZC1Vc2VyIEFwcGxpY2F0aW9uIHRvIHRoZSBBcHBsaWNhdGlvbiBTZXZlciBh
bmQgdG8gdGhlIE5ldHdvcmsNCkNyZWF0aW9uIGRhdGU6CSAyMDEzLTExLTA0DQpHcm91cDoJCSBJ
bmRpdmlkdWFsIFN1Ym1pc3Npb24NCk51bWJlciBvZiBwYWdlczogMTQNClVSTDogICAgICAgICAg
ICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtbW91LXBjcC1hcHBs
aWNhdGlvbi1uZXR3b3JrLWZlZWRiYWNrLTAwLnR4dA0KU3RhdHVzOiAgICAgICAgICBodHRwOi8v
ZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LW1vdS1wY3AtYXBwbGljYXRpb24tbmV0d29y
ay1mZWVkYmFjaw0KSHRtbGl6ZWQ6ICAgICAgICBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9k
cmFmdC1tb3UtcGNwLWFwcGxpY2F0aW9uLW5ldHdvcmstZmVlZGJhY2stMDANCg0KDQpBYnN0cmFj
dDoNCiAgIE5vd2FkYXlzIHVzZXJzIGNvbnN1bXB0aW9uIHN0eWxlIGZvciB2aWRlbyBhbmQgbXVs
dGltZWRpYQ0KICAgYXBwbGljYXRpb25zIGlzIHN0cm9uZ2x5IGNoYW5naW5nLiAgVXNlcnMgYXJl
IGhlYXZpbHkgY291bnRpbmcgb24NCiAgIHdpcmVsZXNzIGFuZCBtb2JpbGUgZGV2aWNlcyBmb3Ig
dmlkZW8gc3RyZWFtaW5nIGFuZCBpbnRlcmFjdGl2ZSB2aWRlbw0KICAgYW5kIG11bHRpbWVkaWEg
YXBwbGljYXRpb25zLiAgVGhpcyBjYW4gYmUgaW1wbGVtZW50ZWQgZm9yIGluc3RhbmNlIGJ5DQog
ICBoYXZpbmcgbW9yZSBpbnRlbGxpZ2VuY2UgaW4gdGhlIHNlcnZpY2UgYW5kIHRoZSBuZXR3b3Jr
DQogICBpbmZyYXN0cnVjdHVyZSB0byBiZXR0ZXIgc3VpdCBhIGRpZmZlcmVudGlhdGVkIHVzZXJz
IGNvbnN1bXB0aW9uDQogICBzdHlsZS4gIFRoaXMgY2FuIGJlIGFjaGlldmVkIHRocm91Z2ggaGF2
aW5nOiAoaSkgYSBrbm93bGVkZ2UgaW4gdGhlDQogICBuZXR3b3JrIGFuZCBzZXJ2aWNlIHBsYXRm
b3JtIGFib3V0IHRoZSBhdmFpbGFibGUgZGV2aWNlIGFuZCBuZXR3b3JrDQogICBjb25kaXRpb25z
IGZvciB0aGUgZW5kLXVzZXIgYW5kIChpaSkgYSBrbm93bGVkZ2UgaW4gdGhlIG5ldHdvcmsgYWJv
dXQNCiAgIHRoZSBjb250ZW50IHJlcXVpcmVtZW50cyBpbiB0ZXJtcyBvZiBkZXZpY2VzIGNhcGFi
aWxpdGllcyBhbmQgbmV0d29yaw0KICAgcmVzb3VyY2VzIGZvciBjb250ZW50IHN0b3JlZCBlaXRo
ZXIgaW4gdGhlIG5ldHdvcmsgb3IgaW4gdGhlDQogICBhcHBsaWNhdGlvbiBzZXJ2ZXIuICBUbyBv
YnRhaW4gc3VjaCBrbm93bGVkZ2Ugd2l0aCBubyBuZWVkIGZvcg0KICAgY2hhbmdpbmcgdGhlIGN1
cnJlbnQgaW5mcmFzdHJ1Y3R1cmUgYW5kIGluIGEgZ2VuZXJhbGl6ZWQgd2F5IHRvIGFsbA0KICAg
YXBwbGljYXRpb25zLCBmZWVkYmFjay9ub3RpZmljYXRpb24gbWVjaGFuaXNtcyBiZXR3ZWVuIHRo
ZSBlbmQtdXNlcg0KICAgYXBwbGljYXRpb24sIHRoZSBuZXR3b3JrIGFuZCB0aGUgc2VydmljZSBw
bGF0Zm9ybSBpcyBuZWVkZWQgdG8NCiAgIHByb3ZpZGUgaW5mb3JtYXRpb24gaGVscGluZyB0aGUg
Y29udGVudCBkZWxpdmVyeSBhbmQgYWRhcHRhdGlvbg0KICAgZGVjaXNpb25zLiAgVGhpcyBkb2N1
bWVudCBpcyBpbnZlc3RpZ2F0aW5nIHN1Y2ggYXBwbGljYXRpb24tYWdub3N0aWMNCiAgIHRyYWNr
Lg0KDQogICBUaGlzIGRvY3VtZW50IGV4dGVuZHMgdGhlIFBvcnQgQ29udHJvbCBQcm90b2NvbCAo
UENQKSBSRkMgNjg4Nw0KICAgW1JGQzY4ODddIHRvIGFsbG93OiAoaSkgdGhlIHVzZXJzIGFwcGxp
Y2F0aW9uIHRvIG5vdGlmeSB0aGUgbmV0d29yaw0KICAgYW5kIGFwcGxpY2F0aW9uIHNlcnZlciBh
Ym91dCBpdHMgYXZhaWxhYmxlIHJlc291cmNlcyBpbiB0ZXJtcyBvZg0KICAgZGV2aWNlcyBjYXBh
YmlsaXRpZXMgYW5kIG5ldHdvcmsgY29uZGl0aW9ucyBhcyB3ZWxsIGFzIGluZm9ybWF0aW9uDQog
ICBhYm91dCB0aGUgdXNlciAoZS5nLiwgbG9jYXRpb24sIG1vYmlsaXR5IHN0YXR1cykgYW5kIChp
aSkgdGhlDQogICBhcHBsaWNhdGlvbiBzZXJ2ZXIgdG8gbm90aWZ5IHRoZSBuZXR3b3JrIGFib3V0
IHRoZSByZXF1aXJlbWVudHMgb2YNCiAgIHRoZSBjb250ZW50IGl0IHN0b3JlcyBpbiB0ZXJtcyBv
ZiBkZXZpY2VzIGFuZCBuZXR3b3JrIHJlc291cmNlcy4gIEENCiAgIG5ldyBQQ1Agb3B0aW9uLCBk
ZW5vdGVkIHRoZSBGRUVEQkFDSywgaXMgc3BlY2lmaWVkIHRvIGFsbG93IHN1Y2gNCiAgIGZlZWRi
YWNrIG5vdGlmaWNhdGlvbiBzaWduYWxpbmcuICBUaGlzIG9wdGlvbiBpcyB1c2VkIHdpdGggYm90
aCBQRUVSDQogICBhbmQgTUFQIE9wY29kZXMuDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAN
Cg0KDQpQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJv
bSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uIHVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBk
aWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQoNClRoZSBJRVRGIFNlY3JldGFy
aWF0DQoNCg==

From dthaler@microsoft.com  Mon Nov  4 18:40:01 2013
Return-Path: <dthaler@microsoft.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 755A521E80F1 for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 18:40:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.625
X-Spam-Level: 
X-Spam-Status: No, score=-103.625 tagged_above=-999 required=5 tests=[AWL=-0.026, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UVwprPnQiUTE for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 18:39:57 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0209.outbound.protection.outlook.com [207.46.163.209]) by ietfa.amsl.com (Postfix) with ESMTP id E09B121E8118 for <pcp@ietf.org>; Mon,  4 Nov 2013 18:39:56 -0800 (PST)
Received: from BN1PR03MB267.namprd03.prod.outlook.com (10.255.200.17) by BN1PR03MB265.namprd03.prod.outlook.com (10.255.200.12) with Microsoft SMTP Server (TLS) id 15.0.815.6; Tue, 5 Nov 2013 02:39:55 +0000
Received: from BN1PR03MB267.namprd03.prod.outlook.com ([169.254.15.28]) by BN1PR03MB267.namprd03.prod.outlook.com ([169.254.15.3]) with mapi id 15.00.0815.000; Tue, 5 Nov 2013 02:39:55 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
Thread-Index: Ac7OuJO2HaM+dCF0QiWR4TXiSiGTNQLF53Qw
Date: Tue, 5 Nov 2013 02:39:54 +0000
Message-ID: <0f2302afab944fbe8741cfe9212d145e@BN1PR03MB267.namprd03.prod.outlook.com>
References: <9b07e3810a7e4aed90b89b82b2eb7f5d@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <9b07e3810a7e4aed90b89b82b2eb7f5d@BY2PR03MB269.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:67c:370:160:7c5a:3b35:88f3:4c83]
x-forefront-prvs: 0021920B5A
x-forefront-antispam-report: SFV:NSPM; SFS:(377424004)(51704005)(377454003)(13464003)(189002)(199002)(50986001)(47446002)(63696002)(56816003)(47736001)(74502001)(46102001)(19580395003)(77096001)(83322001)(47976001)(77982001)(83072001)(54356001)(19580405001)(79102001)(59766001)(51856001)(74366001)(87266001)(81542001)(15202345003)(53806001)(76576001)(76786001)(76796001)(4396001)(81342001)(31966008)(49866001)(74662001)(80976001)(80022001)(65816001)(33646001)(15975445006)(74876001)(85306002)(56776001)(69226001)(54316002)(81686001)(76482001)(81816001)(2656002)(74706001)(74316001)(3826001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BN1PR03MB265; H:BN1PR03MB267.namprd03.prod.outlook.com; CLIP:2001:67c:370:160:7c5a:3b35:88f3:4c83; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Subject: Re: [pcp] WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 02:40:01 -0000

Reminder that the WGLC deadline is tomorrow.
I've only seen two responses so far.
We need more reviews, so consider this a prod.

-Dave

> -----Original Message-----
> From: Dave Thaler
> Sent: Monday, October 21, 2013 4:52 PM
> To: pcp@ietf.org
> Subject: WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
>=20
> This email initiates a two-week Working Group Last Call on
> draft-ietf-pcp-port-set-03 to conclude on Tuesday, November 5th.
>=20
> Please send comments to the list.
>=20
> -Dave
>=20
> > -----Original Message-----
> > From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> > Simon Perreault
> > Sent: Monday, October 21, 2013 5:33 AM
> > To: pcp@ietf.org
> > Subject: Re: [pcp] I-D Action: draft-ietf-pcp-port-set-03.txt
> >
> > WG,
> >
> > This revision addresses comments received at IETF 87 in Berlin, namely:
> >
> > - The "Port Set Offset" field has been replaced by a filed named
> > "First Internal Port".
> >
> > - A new section "Examples" shows various usage examples.
> >
> > To this editor's knowledge there are no open issues left.
> >
> > Simon
> >
> > Le 2013-10-21 12:56, internet-drafts@ietf.org a =E9crit :
> > >
> > > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > >  This draft is a work item of the Port Control Protocol Working
> > > Group of the
> > IETF.
> > >
> > > 	Title           : Port Control Protocol (PCP) Extension for Port Set
> > Allocation
> > > 	Author(s)       : Qiong Sun
> > >                           Mohamed Boucadair
> > >                           Senthil Sivakumar
> > >                           Cathy Zhou
> > >                           Tina Tsou
> > >                           Simon Perreault
> > > 	Filename        : draft-ietf-pcp-port-set-03.txt
> > > 	Pages           : 15
> > > 	Date            : 2013-10-21
> > >
> > > Abstract:
> > >    This document defines an extension to PCP allowing clients to
> > >    manipulate sets of ports as a whole.  This is accomplished by a ne=
w
> > >    MAP option: PORT_SET.
> > >
> > >
> > > The IETF datatracker status page for this draft is:
> > > https://datatracker.ietf.org/doc/draft-ietf-pcp-port-set
> > >
> > > There's also a htmlized version available at:
> > > http://tools.ietf.org/html/draft-ietf-pcp-port-set-03
> > >
> > > A diff from the previous version is available at:
> > > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcp-port-set-03
> > >
> > >
> > > Please note that it may take a couple of minutes from the time of
> > > submission until the htmlized version and diff are available at
> tools.ietf.org.
> > >
> > > Internet-Drafts are also available by anonymous FTP at:
> > > ftp://ftp.ietf.org/internet-drafts/
> > >
> > > _______________________________________________
> > > pcp mailing list
> > > pcp@ietf.org
> > > https://www.ietf.org/mailman/listinfo/pcp


From Ted.Lemon@nominum.com  Mon Nov  4 21:07:45 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16CE621E8100 for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 21:07:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.589
X-Spam-Level: 
X-Spam-Status: No, score=-106.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g-idky7Okli5 for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 21:07:30 -0800 (PST)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id A91B221E80E9 for <pcp@ietf.org>; Mon,  4 Nov 2013 21:07:26 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUnh9De5xvo2Y5EX0hqY84keytEbmMeo3@postini.com; Mon, 04 Nov 2013 21:07:26 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 034261B82A5 for <pcp@ietf.org>; Mon,  4 Nov 2013 21:07:25 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id F00A4190043; Mon,  4 Nov 2013 21:07:24 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.03.0158.001; Mon, 4 Nov 2013 21:07:19 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Dave Thaler <dthaler@microsoft.com>
Thread-Topic: [pcp] WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
Thread-Index: Ac7OuJO2HaM+dCF0QiWR4TXiSiGTNQLF53QwABXw4YA=
Date: Tue, 5 Nov 2013 05:07:17 +0000
Message-ID: <60642641-34D8-4114-A34B-E40D05E49B1A@nominum.com>
References: <9b07e3810a7e4aed90b89b82b2eb7f5d@BY2PR03MB269.namprd03.prod.outlook.com> <0f2302afab944fbe8741cfe9212d145e@BN1PR03MB267.namprd03.prod.outlook.com>
In-Reply-To: <0f2302afab944fbe8741cfe9212d145e@BN1PR03MB267.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <99DF69A9FBEED94D8243476A238D54D7@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 05:07:45 -0000

In figure 1, I think it's intended that the Reserved field be 7 bits, combi=
ning with P to fill a single octet.   However, the chart actually shows it =
as 8 bits, with the P bit out in the next octet.

Also in section 4:

      NOTE: In its current form, PORT_SET does not support allocating
      discontinuous port sets.  That feature could be added in the
      future depending on input from the working group.

The second sentence doesn't really make sense.  The working group can add f=
eatures, of course, but given that the document doesn't talk about how to d=
o this, why mention it?   It seems to me that it would be a new, relatively=
 distinct extension.

Aside from these observations, I don't see any obvious problems with the do=
cument, and it does solve at least one problem that I think is important to=
 solve.   I didn't notice anything that I think wouldn't work.   So (AD hat=
 off, of course) I do not object to publication.


From simon.perreault@viagenie.ca  Mon Nov  4 22:54:24 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E79C711E8176 for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 22:54:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dHI7ghNPKHP1 for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 22:54:24 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 686D911E81AF for <pcp@ietf.org>; Mon,  4 Nov 2013 22:54:23 -0800 (PST)
Received: from porto.nomis80.org (h194.viagenie.ca [206.123.31.194]) by jazz.viagenie.ca (Postfix) with ESMTPSA id B4D7D40213 for <pcp@ietf.org>; Tue,  5 Nov 2013 01:54:22 -0500 (EST)
Message-ID: <5278961E.9080909@viagenie.ca>
Date: Mon, 04 Nov 2013 22:54:22 -0800
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130805 Thunderbird/17.0.8
MIME-Version: 1.0
To: pcp@ietf.org
References: <9b07e3810a7e4aed90b89b82b2eb7f5d@BY2PR03MB269.namprd03.prod.outlook.com> <0f2302afab944fbe8741cfe9212d145e@BN1PR03MB267.namprd03.prod.outlook.com> <60642641-34D8-4114-A34B-E40D05E49B1A@nominum.com>
In-Reply-To: <60642641-34D8-4114-A34B-E40D05E49B1A@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [pcp] WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 06:54:25 -0000

Ted,

Thanks a lot for your review!

Le 2013-11-04 21:07, Ted Lemon a écrit :
> In figure 1, I think it's intended that the Reserved field be 7 bits, combining with P to fill a single octet.   However, the chart actually shows it as 8 bits, with the P bit out in the next octet.

Am I looking at the same figure as you are?

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | Option Code=? |   Reserved    |        Option Length=5        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |        Port Set Size          |      First Internal Port      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |  Reserved   |P|
    +-+-+-+-+-+-+-+-+

                          Figure 1: PORT_SET Option

It looks correct to me...

> Also in section 4:
>
>        NOTE: In its current form, PORT_SET does not support allocating
>        discontinuous port sets.  That feature could be added in the
>        future depending on input from the working group.
>
> The second sentence doesn't really make sense.  The working group can add features, of course, but given that the document doesn't talk about how to do this, why mention it?   It seems to me that it would be a new, relatively distinct extension.

Agreed. By "in the future" we meant "in future revisions of this draft". 
Now that we're in WGLC it doesn't make sense anymore. I'll just remove 
the note entirely.

> Aside from these observations, I don't see any obvious problems with the document, and it does solve at least one problem that I think is important to solve.   I didn't notice anything that I think wouldn't work.   So (AD hat off, of course) I do not object to publication.

Great!

Thanks,
Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From internet-drafts@ietf.org  Mon Nov  4 23:13:45 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FAD811E8171; Mon,  4 Nov 2013 23:13:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I4wDB9YkgAXa; Mon,  4 Nov 2013 23:13:44 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D091211E8178; Mon,  4 Nov 2013 23:13:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.82
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131105071342.29536.94063.idtracker@ietfa.amsl.com>
Date: Mon, 04 Nov 2013 23:13:42 -0800
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-dhcp-09.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 07:13:45 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Port Control Protocol Working Group of th=
e IETF.

	Title           : DHCP Options for the Port Control Protocol (PCP)
	Author(s)       : Mohamed Boucadair
                          Reinaldo Penno
                          Dan Wing
	Filename        : draft-ietf-pcp-dhcp-09.txt
	Pages           : 8
	Date            : 2013-11-04

Abstract:
   This document specifies DHCP (IPv4 and IPv6) options to configure
   hosts with Port Control Protocol (PCP) Server IP addresses.  The use
   of DHCPv4 or DHCPv6 depends on the PCP deployment scenario.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pcp-dhcp

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pcp-dhcp-09

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcp-dhcp-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From sunqi.thu@gmail.com  Mon Nov  4 23:16:00 2013
Return-Path: <sunqi.thu@gmail.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7196811E8171 for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 23:16:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2KvmKqjQlwF0 for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 23:15:58 -0800 (PST)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) by ietfa.amsl.com (Postfix) with ESMTP id 8C60B21E8087 for <pcp@ietf.org>; Mon,  4 Nov 2013 23:15:54 -0800 (PST)
Received: by mail-lb0-f179.google.com with SMTP id w6so6309931lbh.10 for <pcp@ietf.org>; Mon, 04 Nov 2013 23:15:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VoFHA1hc92ldI4GzRcG6CQoMuPmi31ZqsPnZZAkHHrA=; b=0wByq4CF43A9A7exDwaaEOY+YzpYCvVFeJmnQYCPRLm0rgwj0EmHAazw5Ekjvy2zdh dWk7XiGS+cuHIpvpljPCnvEEbhvGA7gynWioyAAzhIDL16gg9Of0H9d//+CwXRVuJCbL f0URfNPO7Yharz7DKybfP9FNnjGTjNrprO+Ls8dryB1M3i2uwKsbiOn7aTcaZ/HkyiBI AKXM3dkgYCEQLZZ+V95w4hGi1LBMVh4h4mICOmco1/GfWZX/8VtvtRHQlP1ZpV2GBJ9E 7UdRp4dzN/C1OKoujDwY7IyQxFPbReczmsakqkO33F1e0C/R/Xthsn7INxbpM+U8Ojx4 t1ag==
MIME-Version: 1.0
X-Received: by 10.112.171.228 with SMTP id ax4mr14252271lbc.6.1383635751527; Mon, 04 Nov 2013 23:15:51 -0800 (PST)
Received: by 10.112.198.225 with HTTP; Mon, 4 Nov 2013 23:15:51 -0800 (PST)
In-Reply-To: <9b07e3810a7e4aed90b89b82b2eb7f5d@BY2PR03MB269.namprd03.prod.outlook.com>
References: <9b07e3810a7e4aed90b89b82b2eb7f5d@BY2PR03MB269.namprd03.prod.outlook.com>
Date: Mon, 4 Nov 2013 23:15:51 -0800
Message-ID: <CA+-i+todQ7uWmGdDexmyOOrVT+0LAZi2Fut=7dNdRWcApb880Q@mail.gmail.com>
From: Qi Sun <sunqi.thu@gmail.com>
To: Dave Thaler <dthaler@microsoft.com>
Content-Type: multipart/alternative; boundary=001a11c3704477eb5e04ea68cd00
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 07:16:00 -0000

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

Dear all,

I support this document to move forward.

Best Regards,
Qi


On Mon, Oct 21, 2013 at 4:52 PM, Dave Thaler <dthaler@microsoft.com> wrote:

> This email initiates a two-week Working Group Last Call on
> draft-ietf-pcp-port-set-03 to conclude on Tuesday, November 5th.
>
> Please send comments to the list.
>
> -Dave
>
> > -----Original Message-----
> > From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> > Simon Perreault
> > Sent: Monday, October 21, 2013 5:33 AM
> > To: pcp@ietf.org
> > Subject: Re: [pcp] I-D Action: draft-ietf-pcp-port-set-03.txt
> >
> > WG,
> >
> > This revision addresses comments received at IETF 87 in Berlin, namely:
> >
> > - The "Port Set Offset" field has been replaced by a filed named "First
> Internal
> > Port".
> >
> > - A new section "Examples" shows various usage examples.
> >
> > To this editor's knowledge there are no open issues left.
> >
> > Simon
> >
> > Le 2013-10-21 12:56, internet-drafts@ietf.org a =E9crit :
> > >
> > > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > >  This draft is a work item of the Port Control Protocol Working Group
> of the
> > IETF.
> > >
> > >     Title           : Port Control Protocol (PCP) Extension for Port
> Set
> > Allocation
> > >     Author(s)       : Qiong Sun
> > >                           Mohamed Boucadair
> > >                           Senthil Sivakumar
> > >                           Cathy Zhou
> > >                           Tina Tsou
> > >                           Simon Perreault
> > >     Filename        : draft-ietf-pcp-port-set-03.txt
> > >     Pages           : 15
> > >     Date            : 2013-10-21
> > >
> > > Abstract:
> > >    This document defines an extension to PCP allowing clients to
> > >    manipulate sets of ports as a whole.  This is accomplished by a ne=
w
> > >    MAP option: PORT_SET.
> > >
> > >
> > > The IETF datatracker status page for this draft is:
> > > https://datatracker.ietf.org/doc/draft-ietf-pcp-port-set
> > >
> > > There's also a htmlized version available at:
> > > http://tools.ietf.org/html/draft-ietf-pcp-port-set-03
> > >
> > > A diff from the previous version is available at:
> > > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcp-port-set-03
> > >
> > >
> > > Please note that it may take a couple of minutes from the time of
> > > submission until the htmlized version and diff are available at
> tools.ietf.org.
> > >
> > > Internet-Drafts are also available by anonymous FTP at:
> > > ftp://ftp.ietf.org/internet-drafts/
> > >
> > > _______________________________________________
> > > pcp mailing list
> > > pcp@ietf.org
> > > https://www.ietf.org/mailman/listinfo/pcp
>
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp
>

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

<div dir=3D"ltr">Dear all,=A0<div><br></div><div>I support this document to=
 move forward.</div><div><br></div><div>Best Regards,</div><div>Qi</div></d=
iv><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, Oc=
t 21, 2013 at 4:52 PM, Dave Thaler <span dir=3D"ltr">&lt;<a href=3D"mailto:=
dthaler@microsoft.com" target=3D"_blank">dthaler@microsoft.com</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">This email initiates a two-week Working Grou=
p Last Call on<br>
draft-ietf-pcp-port-set-03 to conclude on Tuesday, November 5th.<br>
<br>
Please send comments to the list.<br>
<br>
-Dave<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:pcp-bounces@ietf.org">pcp-bounces@ietf.org</a>=
 [mailto:<a href=3D"mailto:pcp-bounces@ietf.org">pcp-bounces@ietf.org</a>] =
On Behalf Of<br>
&gt; Simon Perreault<br>
&gt; Sent: Monday, October 21, 2013 5:33 AM<br>
&gt; To: <a href=3D"mailto:pcp@ietf.org">pcp@ietf.org</a><br>
&gt; Subject: Re: [pcp] I-D Action: draft-ietf-pcp-port-set-03.txt<br>
&gt;<br>
&gt; WG,<br>
&gt;<br>
&gt; This revision addresses comments received at IETF 87 in Berlin, namely=
:<br>
&gt;<br>
&gt; - The &quot;Port Set Offset&quot; field has been replaced by a filed n=
amed &quot;First Internal<br>
&gt; Port&quot;.<br>
&gt;<br>
&gt; - A new section &quot;Examples&quot; shows various usage examples.<br>
&gt;<br>
&gt; To this editor&#39;s knowledge there are no open issues left.<br>
&gt;<br>
&gt; Simon<br>
&gt;<br>
&gt; Le 2013-10-21 12:56, <a href=3D"mailto:internet-drafts@ietf.org">inter=
net-drafts@ietf.org</a> a =E9crit :<br>
&gt; &gt;<br>
&gt; &gt; A New Internet-Draft is available from the on-line Internet-Draft=
s directories.<br>
&gt; &gt; =A0This draft is a work item of the Port Control Protocol Working=
 Group of the<br>
&gt; IETF.<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Port Control Protocol (PCP) E=
xtension for Port Set<br>
&gt; Allocation<br>
&gt; &gt; =A0 =A0 Author(s) =A0 =A0 =A0 : Qiong Sun<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Mohamed Bouca=
dair<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Senthil Sivak=
umar<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Cathy Zhou<br=
>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Tina Tsou<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Simon Perreau=
lt<br>
&gt; &gt; =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-pcp-port-set-03.txt<=
br>
&gt; &gt; =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 15<br>
&gt; &gt; =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2013-10-21<br>
&gt; &gt;<br>
&gt; &gt; Abstract:<br>
&gt; &gt; =A0 =A0This document defines an extension to PCP allowing clients=
 to<br>
&gt; &gt; =A0 =A0manipulate sets of ports as a whole. =A0This is accomplish=
ed by a new<br>
&gt; &gt; =A0 =A0MAP option: PORT_SET.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; The IETF datatracker status page for this draft is:<br>
&gt; &gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-pcp-port-s=
et" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-pcp-port-=
set</a><br>
&gt; &gt;<br>
&gt; &gt; There&#39;s also a htmlized version available at:<br>
&gt; &gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-pcp-port-set-03"=
 target=3D"_blank">http://tools.ietf.org/html/draft-ietf-pcp-port-set-03</a=
><br>
&gt; &gt;<br>
&gt; &gt; A diff from the previous version is available at:<br>
&gt; &gt; <a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcp-port=
-set-03" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pc=
p-port-set-03</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Please note that it may take a couple of minutes from the time of=
<br>
&gt; &gt; submission until the htmlized version and diff are available at <=
a href=3D"http://tools.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
&gt; &gt;<br>
&gt; &gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt; &gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank"=
>ftp://ftp.ietf.org/internet-drafts/</a><br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; pcp mailing list<br>
&gt; &gt; <a href=3D"mailto:pcp@ietf.org">pcp@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pcp" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/pcp</a><br>
<br>
_______________________________________________<br>
pcp mailing list<br>
<a href=3D"mailto:pcp@ietf.org">pcp@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pcp" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/pcp</a><br>
</blockquote></div><br></div>

--001a11c3704477eb5e04ea68cd00--

From eleven.fuyu@huawei.com  Mon Nov  4 23:22:42 2013
Return-Path: <eleven.fuyu@huawei.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E75F221E809C for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 23:22:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bRLiDFSmbdvp for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 23:22:38 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 179C211E810A for <pcp@ietf.org>; Mon,  4 Nov 2013 23:22:37 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AZW14967; Tue, 05 Nov 2013 07:22:35 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 5 Nov 2013 07:21:53 +0000
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 5 Nov 2013 07:22:32 +0000
Received: from NKGEML505-MBX.china.huawei.com ([169.254.1.31]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Tue, 5 Nov 2013 15:22:28 +0800
From: "Fuyu (Eleven)" <eleven.fuyu@huawei.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
Thread-Index: Ac7OuJO2HaM+dCF0QiWR4TXiSiGTNQLOAc6w
Date: Tue, 5 Nov 2013 07:22:28 +0000
Message-ID: <EF6A204047BD994A860EE26D5F23BF58415C426C@nkgeml505-mbx.china.huawei.com>
References: <9b07e3810a7e4aed90b89b82b2eb7f5d@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <9b07e3810a7e4aed90b89b82b2eb7f5d@BY2PR03MB269.namprd03.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.25]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [pcp] WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 07:22:43 -0000

Hi all,

I support to move forward this document. It is useful for managing a set of=
 ports.

Cheers
Yu

-----Original Message-----
From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of Dave =
Thaler
Sent: Tuesday, October 22, 2013 7:52 AM
To: pcp@ietf.org
Subject: [pcp] WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5

This email initiates a two-week Working Group Last Call on
draft-ietf-pcp-port-set-03 to conclude on Tuesday, November 5th.

Please send comments to the list.

-Dave

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Simon Perreault
> Sent: Monday, October 21, 2013 5:33 AM
> To: pcp@ietf.org
> Subject: Re: [pcp] I-D Action: draft-ietf-pcp-port-set-03.txt
>=20
> WG,
>=20
> This revision addresses comments received at IETF 87 in Berlin, namely:
>=20
> - The "Port Set Offset" field has been replaced by a filed named "First I=
nternal
> Port".
>=20
> - A new section "Examples" shows various usage examples.
>=20
> To this editor's knowledge there are no open issues left.
>=20
> Simon
>=20
> Le 2013-10-21 12:56, internet-drafts@ietf.org a =E9crit :
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts dire=
ctories.
> >  This draft is a work item of the Port Control Protocol Working Group o=
f the
> IETF.
> >
> > 	Title           : Port Control Protocol (PCP) Extension for Port Set
> Allocation
> > 	Author(s)       : Qiong Sun
> >                           Mohamed Boucadair
> >                           Senthil Sivakumar
> >                           Cathy Zhou
> >                           Tina Tsou
> >                           Simon Perreault
> > 	Filename        : draft-ietf-pcp-port-set-03.txt
> > 	Pages           : 15
> > 	Date            : 2013-10-21
> >
> > Abstract:
> >    This document defines an extension to PCP allowing clients to
> >    manipulate sets of ports as a whole.  This is accomplished by a new
> >    MAP option: PORT_SET.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-pcp-port-set
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-ietf-pcp-port-set-03
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcp-port-set-03
> >
> >
> > Please note that it may take a couple of minutes from the time of
> > submission until the htmlized version and diff are available at tools.i=
etf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > pcp mailing list
> > pcp@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcp

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

From gnocuil@gmail.com  Mon Nov  4 23:26:35 2013
Return-Path: <gnocuil@gmail.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E6E011E810A for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 23:26:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qcdm4lFtHLMO for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 23:26:34 -0800 (PST)
Received: from mail-qa0-x22b.google.com (mail-qa0-x22b.google.com [IPv6:2607:f8b0:400d:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 53BAF11E8238 for <pcp@ietf.org>; Mon,  4 Nov 2013 23:26:33 -0800 (PST)
Received: by mail-qa0-f43.google.com with SMTP id cm18so850817qab.2 for <pcp@ietf.org>; Mon, 04 Nov 2013 23:26:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=/VzXU+JY+Y6QJRe/dLHds25qyjpVhuqD3aDTvZzfpYo=; b=QBoziT0XonGXoAaWhqenp1ivPx+3iEH7Mt7eqjC9qx6aWtuvgzWL9dmH8myb6rPxXX cRiX7J0dvugYFncvwzlN6amF8gcUPV9CJBt1ogW17aS+SdE6hZ3vnFiNahXqf248bNOp pL1MoiGS/k6NLJNrbuci3V+QvI8em3mPumJ6DLsldtj2FXc4Zszhq1RDMGKdmtXeAqPC eFXgs+/mZDLb8RWDnyuWZEwpVS2jT7PHiat8kU6UaxX5NIBdRUOmi88ulZFayO7g1CCW vsCGvL34bcpcRayvxyFHgcKaQwMtAPRta2qMAJmaybxr4A/0wrVphjffHOV714EOumT1 6c+w==
X-Received: by 10.49.12.14 with SMTP id u14mr27657168qeb.74.1383636382163; Mon, 04 Nov 2013 23:26:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.96.185.33 with HTTP; Mon, 4 Nov 2013 23:26:02 -0800 (PST)
In-Reply-To: <5278961E.9080909@viagenie.ca>
References: <9b07e3810a7e4aed90b89b82b2eb7f5d@BY2PR03MB269.namprd03.prod.outlook.com> <0f2302afab944fbe8741cfe9212d145e@BN1PR03MB267.namprd03.prod.outlook.com> <60642641-34D8-4114-A34B-E40D05E49B1A@nominum.com> <5278961E.9080909@viagenie.ca>
From: Cong Liu <gnocuil@gmail.com>
Date: Mon, 4 Nov 2013 23:26:02 -0800
Message-ID: <CAF+sHxGmhJcEE4j=gD56s2EokaAHi+TNT3Bdm0m0pJkU2kRyOQ@mail.gmail.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Content-Type: multipart/alternative; boundary=047d7b6daa480ea7cf04ea68f382
Cc: pcp@ietf.org
Subject: Re: [pcp] WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 07:26:35 -0000

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

Dear all,

I've read this document and I think it's a very useful work. I support
advancing this document.

A small problem: in section 3, is "Length: 3 bytes" a mistake?

Best Regards,
Cong

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

<div dir=3D"ltr">Dear all,<div><br></div><div>I&#39;ve read this document a=
nd I think it&#39;s a very useful work.=A0I support advancing this document=
.=A0</div><div><br></div><div>A small problem: in section 3, is &quot;<span=
 style=3D"font-size:1em">Length:  3 bytes&quot; a mistake?</span></div>


<div><font color=3D"#000000"><br></font></div><div><font color=3D"#000000">=
Best Regards,</font></div><div><font color=3D"#000000">Cong<br></font><div>=
<div class=3D"gmail_extra"><br><br></div></div></div></div>

--047d7b6daa480ea7cf04ea68f382--

From chenycmx@gmail.com  Mon Nov  4 23:58:49 2013
Return-Path: <chenycmx@gmail.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2EE311E8238 for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 23:58:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 46ZHCSMCcuVB for <pcp@ietfa.amsl.com>; Mon,  4 Nov 2013 23:58:41 -0800 (PST)
Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id E491211E80DC for <pcp@ietf.org>; Mon,  4 Nov 2013 23:58:36 -0800 (PST)
Received: by mail-pd0-f179.google.com with SMTP id y10so7897049pdj.38 for <pcp@ietf.org>; Mon, 04 Nov 2013 23:58:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:reply-to:subject:references:mime-version:message-id :content-type; bh=fwiXmhP3Ponf1rWGob+DFC7VVgMR5TYEvSgB20xq/Wg=; b=wlL171lKi01r1zxgr9LX+xSozG9Ne2oU1fTUAyKq4AFVuLPv+KmiT+KssiwJPvyrDH QlBjKAzbBK9qYw/SfRqb57gWxqIPhPtQOMUPS9xIwbUw3ffjMcWZ6DEn2W3UQN4p6IS/ +NuC8FXQ+OD6N1mKzJ6ty9QlM6+3cyohJbduPxKcwkvgCkrl9SPNVdFoGbjCvelSENXc D0sgfb5JZb/ZSY6Y/FXe4+dKurz2YlvXP/LbbWa9iD54eSj+Xip04H5hbIXqF9B5IXTw zYpIZgW6sS68yoGkaSKmRFhI3Z+FIpZS2m0EXmp9ba2KIcNAymfQl2ZzHMbeXIyBf1Ez bzLw==
X-Received: by 10.67.4.136 with SMTP id ce8mr5724399pad.158.1383638316433; Mon, 04 Nov 2013 23:58:36 -0800 (PST)
Received: from netlab-PC ([166.111.68.231]) by mx.google.com with ESMTPSA id qn1sm32873966pbc.34.2013.11.04.23.58.30 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 04 Nov 2013 23:58:35 -0800 (PST)
Date: Tue, 5 Nov 2013 15:58:30 +0800
From: "Yuchi Chen" <chenycmx@gmail.com>
To: "Dave Thaler" <dthaler@microsoft.com>
References: <9b07e3810a7e4aed90b89b82b2eb7f5d@BY2PR03MB269.namprd03.prod.outlook.com>
X-Priority: 3
X-GUID: 3E91B288-767C-4407-BF93-54E9E6866951
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <2013110515582448890828@gmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart620184833601_=----"
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: chenycmx <chenycmx@gmail.com>
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 07:58:50 -0000

This is a multi-part message in MIME format.

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

SGkgYWxsLA0KDQpJIHN1cHBvcnQgbW92aW5nIGZvcndhcmQgdGhpcyBkb2N1bWVudC4gDQoNCkJl
c3QgcmVnYXJkcyENCg0KDQoNCll1Y2hpIENoZW4NCg0KRnJvbTogRGF2ZSBUaGFsZXINCkRhdGU6
IDIwMTMtMTAtMjIgMDc6NTINClRvOiBwY3BAaWV0Zi5vcmcNClN1YmplY3Q6IFtwY3BdIFdHTEM6
IGRyYWZ0LWlldGYtcGNwLXBvcnQtc2V0LTAzLnR4dCBjb21tZW50cyBkdWUgYnkgTk9WIDUNClRo
aXMgZW1haWwgaW5pdGlhdGVzIGEgdHdvLXdlZWsgV29ya2luZyBHcm91cCBMYXN0IENhbGwgb24N
CmRyYWZ0LWlldGYtcGNwLXBvcnQtc2V0LTAzIHRvIGNvbmNsdWRlIG9uIFR1ZXNkYXksIE5vdmVt
YmVyIDV0aC4NCg0KUGxlYXNlIHNlbmQgY29tbWVudHMgdG8gdGhlIGxpc3QuDQoNCi1EYXZlDQoN
Cj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogcGNwLWJvdW5jZXNAaWV0Zi5v
cmcgW21haWx0bzpwY3AtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mDQo+IFNpbW9uIFBl
cnJlYXVsdA0KPiBTZW50OiBNb25kYXksIE9jdG9iZXIgMjEsIDIwMTMgNTozMyBBTQ0KPiBUbzog
cGNwQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBbcGNwXSBJLUQgQWN0aW9uOiBkcmFmdC1pZXRm
LXBjcC1wb3J0LXNldC0wMy50eHQNCj4gDQo+IFdHLA0KPiANCj4gVGhpcyByZXZpc2lvbiBhZGRy
ZXNzZXMgY29tbWVudHMgcmVjZWl2ZWQgYXQgSUVURiA4NyBpbiBCZXJsaW4sIG5hbWVseToNCj4g
DQo+IC0gVGhlICJQb3J0IFNldCBPZmZzZXQiIGZpZWxkIGhhcyBiZWVuIHJlcGxhY2VkIGJ5IGEg
ZmlsZWQgbmFtZWQgIkZpcnN0IEludGVybmFsDQo+IFBvcnQiLg0KPiANCj4gLSBBIG5ldyBzZWN0
aW9uICJFeGFtcGxlcyIgc2hvd3MgdmFyaW91cyB1c2FnZSBleGFtcGxlcy4NCj4gDQo+IFRvIHRo
aXMgZWRpdG9yJ3Mga25vd2xlZGdlIHRoZXJlIGFyZSBubyBvcGVuIGlzc3VlcyBsZWZ0Lg0KPiAN
Cj4gU2ltb24NCj4gDQo+IExlIDIwMTMtMTAtMjEgMTI6NTYsIGludGVybmV0LWRyYWZ0c0BpZXRm
Lm9yZyBhIMOpY3JpdCA6DQo+ID4NCj4gPiBBIE5ldyBJbnRlcm5ldC1EcmFmdCBpcyBhdmFpbGFi
bGUgZnJvbSB0aGUgb24tbGluZSBJbnRlcm5ldC1EcmFmdHMgZGlyZWN0b3JpZXMuDQo+ID4gIFRo
aXMgZHJhZnQgaXMgYSB3b3JrIGl0ZW0gb2YgdGhlIFBvcnQgQ29udHJvbCBQcm90b2NvbCBXb3Jr
aW5nIEdyb3VwIG9mIHRoZQ0KPiBJRVRGLg0KPiA+DQo+ID4gIFRpdGxlICAgICAgICAgICA6IFBv
cnQgQ29udHJvbCBQcm90b2NvbCAoUENQKSBFeHRlbnNpb24gZm9yIFBvcnQgU2V0DQo+IEFsbG9j
YXRpb24NCj4gPiAgQXV0aG9yKHMpICAgICAgIDogUWlvbmcgU3VuDQo+ID4gICAgICAgICAgICAg
ICAgICAgICAgICAgICBNb2hhbWVkIEJvdWNhZGFpcg0KPiA+ICAgICAgICAgICAgICAgICAgICAg
ICAgICAgU2VudGhpbCBTaXZha3VtYXINCj4gPiAgICAgICAgICAgICAgICAgICAgICAgICAgIENh
dGh5IFpob3UNCj4gPiAgICAgICAgICAgICAgICAgICAgICAgICAgIFRpbmEgVHNvdQ0KPiA+ICAg
ICAgICAgICAgICAgICAgICAgICAgICAgU2ltb24gUGVycmVhdWx0DQo+ID4gIEZpbGVuYW1lICAg
ICAgICA6IGRyYWZ0LWlldGYtcGNwLXBvcnQtc2V0LTAzLnR4dA0KPiA+ICBQYWdlcyAgICAgICAg
ICAgOiAxNQ0KPiA+ICBEYXRlICAgICAgICAgICAgOiAyMDEzLTEwLTIxDQo+ID4NCj4gPiBBYnN0
cmFjdDoNCj4gPiAgICBUaGlzIGRvY3VtZW50IGRlZmluZXMgYW4gZXh0ZW5zaW9uIHRvIFBDUCBh
bGxvd2luZyBjbGllbnRzIHRvDQo+ID4gICAgbWFuaXB1bGF0ZSBzZXRzIG9mIHBvcnRzIGFzIGEg
d2hvbGUuICBUaGlzIGlzIGFjY29tcGxpc2hlZCBieSBhIG5ldw0KPiA+ICAgIE1BUCBvcHRpb246
IFBPUlRfU0VULg0KPiA+DQo+ID4NCj4gPiBUaGUgSUVURiBkYXRhdHJhY2tlciBzdGF0dXMgcGFn
ZSBmb3IgdGhpcyBkcmFmdCBpczoNCj4gPiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2Rv
Yy9kcmFmdC1pZXRmLXBjcC1wb3J0LXNldA0KPiA+DQo+ID4gVGhlcmUncyBhbHNvIGEgaHRtbGl6
ZWQgdmVyc2lvbiBhdmFpbGFibGUgYXQ6DQo+ID4gaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtaWV0Zi1wY3AtcG9ydC1zZXQtMDMNCj4gPg0KPiA+IEEgZGlmZiBmcm9tIHRoZSBwcmV2
aW91cyB2ZXJzaW9uIGlzIGF2YWlsYWJsZSBhdDoNCj4gPiBodHRwOi8vd3d3LmlldGYub3JnL3Jm
Y2RpZmY/dXJsMj1kcmFmdC1pZXRmLXBjcC1wb3J0LXNldC0wMw0KPiA+DQo+ID4NCj4gPiBQbGVh
c2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGlt
ZSBvZg0KPiA+IHN1Ym1pc3Npb24gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYg
YXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCj4gPg0KPiA+IEludGVybmV0LURyYWZ0
cyBhcmUgYWxzbyBhdmFpbGFibGUgYnkgYW5vbnltb3VzIEZUUCBhdDoNCj4gPiBmdHA6Ly9mdHAu
aWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KPiA+DQo+ID4gX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPiBwY3AgbWFpbGluZyBsaXN0DQo+ID4gcGNw
QGlldGYub3JnDQo+ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9wY3AN
Cg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnBjcCBt
YWlsaW5nIGxpc3QNCnBjcEBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9wY3A=

------=_001_NextPart620184833601_=----
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dutf-8" http-equiv=3DContent-Type>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91; COLO=
R: #000080; FONT-SIZE: 10.5pt
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 8.00.7601.17514"></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV>Hi&nbsp;all,</DIV>
<DIV>&nbsp;</DIV>
<DIV>I support moving forward this document.&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>Best regards!</DIV>
<HR style=3D"WIDTH: 210px; HEIGHT: 1px" align=3Dleft color=3D#b5c4df SIZE=
=3D1>

<DIV><SPAN><SPAN=20
style=3D"FONT-FAMILY: =E5=AE=8B=E4=BD=93; COLOR: #000000; FONT-SIZE: 10.5p=
t">Yuchi=20
Chen</SPAN></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:dthaler@microsoft.com">Dave=20
Thaler</A></DIV>
<DIV><B>Date:</B>&nbsp;2013-10-22&nbsp;07:52</DIV>
<DIV><B>To:</B>&nbsp;<A href=3D"mailto:pcp@ietf.org">pcp@ietf.org</A></DIV=
>
<DIV><B>Subject:</B>&nbsp;[pcp] WGLC: draft-ietf-pcp-port-set-03.txt comme=
nts=20
due by NOV 5</DIV></DIV></DIV>
<DIV>
<DIV>This&nbsp;email&nbsp;initiates&nbsp;a&nbsp;two-week&nbsp;Working&nbsp=
;Group&nbsp;Last&nbsp;Call&nbsp;on</DIV>
<DIV>draft-ietf-pcp-port-set-03&nbsp;to&nbsp;conclude&nbsp;on&nbsp;Tuesday=
,&nbsp;November&nbsp;5th.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Please&nbsp;send&nbsp;comments&nbsp;to&nbsp;the&nbsp;list.</DIV>
<DIV>&nbsp;</DIV>
<DIV>-Dave</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&nbsp;-----Original&nbsp;Message-----</DIV>
<DIV>&gt;&nbsp;From:&nbsp;pcp-bounces@ietf.org&nbsp;[mailto:pcp-bounces@ie=
tf.org]&nbsp;On&nbsp;Behalf&nbsp;Of</DIV>
<DIV>&gt;&nbsp;Simon&nbsp;Perreault</DIV>
<DIV>&gt;&nbsp;Sent:&nbsp;Monday,&nbsp;October&nbsp;21,&nbsp;2013&nbsp;5:3=
3&nbsp;AM</DIV>
<DIV>&gt;&nbsp;To:&nbsp;pcp@ietf.org</DIV>
<DIV>&gt;&nbsp;Subject:&nbsp;Re:&nbsp;[pcp]&nbsp;I-D&nbsp;Action:&nbsp;dra=
ft-ietf-pcp-port-set-03.txt</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;WG,</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;This&nbsp;revision&nbsp;addresses&nbsp;comments&nbsp;receiv=
ed&nbsp;at&nbsp;IETF&nbsp;87&nbsp;in&nbsp;Berlin,&nbsp;namely:</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;-&nbsp;The&nbsp;"Port&nbsp;Set&nbsp;Offset"&nbsp;field&nbsp=
;has&nbsp;been&nbsp;replaced&nbsp;by&nbsp;a&nbsp;filed&nbsp;named&nbsp;"Fi=
rst&nbsp;Internal</DIV>
<DIV>&gt;&nbsp;Port".</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;-&nbsp;A&nbsp;new&nbsp;section&nbsp;"Examples"&nbsp;shows&n=
bsp;various&nbsp;usage&nbsp;examples.</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;To&nbsp;this&nbsp;editor's&nbsp;knowledge&nbsp;there&nbsp;a=
re&nbsp;no&nbsp;open&nbsp;issues&nbsp;left.</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;Simon</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;Le&nbsp;2013-10-21&nbsp;12:56,&nbsp;internet-drafts@ietf.or=
g&nbsp;a&nbsp;=C3=A9crit&nbsp;:</DIV>
<DIV>&gt;&nbsp;&gt;</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;A&nbsp;New&nbsp;Internet-Draft&nbsp;is&nbsp;avail=
able&nbsp;from&nbsp;the&nbsp;on-line&nbsp;Internet-Drafts&nbsp;directories=
.</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;&nbsp;This&nbsp;draft&nbsp;is&nbsp;a&nbsp;work&nb=
sp;item&nbsp;of&nbsp;the&nbsp;Port&nbsp;Control&nbsp;Protocol&nbsp;Working=
&nbsp;Group&nbsp;of&nbsp;the</DIV>
<DIV>&gt;&nbsp;IETF.</DIV>
<DIV>&gt;&nbsp;&gt;</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;=20
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&n=
bsp;Port&nbsp;Control&nbsp;Protocol&nbsp;(PCP)&nbsp;Extension&nbsp;for&nbs=
p;Port&nbsp;Set</DIV>
<DIV>&gt;&nbsp;Allocation</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;=20
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&nbsp;Qiong&nbsp;Sun</=
DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Mohamed&nbsp;Boucadair</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Senthil&nbsp;Sivakumar</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Cathy&nbsp;Zhou</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tina&nbsp;Tsou</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Simon&nbsp;Perreault</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;=20
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&nbsp;draft-ietf-=
pcp-port-set-03.txt</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;=20
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&n=
bsp;15</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;=20
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;:&nbsp;2013-10-21</DIV>
<DIV>&gt;&nbsp;&gt;</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;Abstract:</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;&nbsp;&nbsp;&nbsp;This&nbsp;document&nbsp;defines=
&nbsp;an&nbsp;extension&nbsp;to&nbsp;PCP&nbsp;allowing&nbsp;clients&nbsp;t=
o</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;&nbsp;&nbsp;&nbsp;manipulate&nbsp;sets&nbsp;of&nb=
sp;ports&nbsp;as&nbsp;a&nbsp;whole.&nbsp;&nbsp;This&nbsp;is&nbsp;accomplis=
hed&nbsp;by&nbsp;a&nbsp;new</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;&nbsp;&nbsp;&nbsp;MAP&nbsp;option:&nbsp;PORT_SET.=
</DIV>
<DIV>&gt;&nbsp;&gt;</DIV>
<DIV>&gt;&nbsp;&gt;</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;The&nbsp;IETF&nbsp;datatracker&nbsp;status&nbsp;p=
age&nbsp;for&nbsp;this&nbsp;draft&nbsp;is:</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;https://datatracker.ietf.org/doc/draft-ietf-pcp-p=
ort-set</DIV>
<DIV>&gt;&nbsp;&gt;</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;There's&nbsp;also&nbsp;a&nbsp;htmlized&nbsp;versi=
on&nbsp;available&nbsp;at:</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;http://tools.ietf.org/html/draft-ietf-pcp-port-se=
t-03</DIV>
<DIV>&gt;&nbsp;&gt;</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;A&nbsp;diff&nbsp;from&nbsp;the&nbsp;previous&nbsp=
;version&nbsp;is&nbsp;available&nbsp;at:</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcp=
-port-set-03</DIV>
<DIV>&gt;&nbsp;&gt;</DIV>
<DIV>&gt;&nbsp;&gt;</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;Please&nbsp;note&nbsp;that&nbsp;it&nbsp;may&nbsp;=
take&nbsp;a&nbsp;couple&nbsp;of&nbsp;minutes&nbsp;from&nbsp;the&nbsp;time&=
nbsp;of</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;submission&nbsp;until&nbsp;the&nbsp;htmlized&nbsp=
;version&nbsp;and&nbsp;diff&nbsp;are&nbsp;available&nbsp;at&nbsp;tools.iet=
f.org.</DIV>
<DIV>&gt;&nbsp;&gt;</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;Internet-Drafts&nbsp;are&nbsp;also&nbsp;available=
&nbsp;by&nbsp;anonymous&nbsp;FTP&nbsp;at:</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;ftp://ftp.ietf.org/internet-drafts/</DIV>
<DIV>&gt;&nbsp;&gt;</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;_______________________________________________</=
DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;pcp&nbsp;mailing&nbsp;list</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;pcp@ietf.org</DIV>
<DIV>&gt;&nbsp;&gt;&nbsp;https://www.ietf.org/mailman/listinfo/pcp</DIV>
<DIV>&nbsp;</DIV>
<DIV>_______________________________________________</DIV>
<DIV>pcp&nbsp;mailing&nbsp;list</DIV>
<DIV>pcp@ietf.org</DIV>
<DIV>https://www.ietf.org/mailman/listinfo/pcp</DIV></DIV></BODY></HTML>

------=_001_NextPart620184833601_=------


From Ted.Lemon@nominum.com  Tue Nov  5 06:20:48 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BB8F21E8154 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 06:20:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.589
X-Spam-Level: 
X-Spam-Status: No, score=-106.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zUhYCi5Godhu for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 06:20:41 -0800 (PST)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id B1B6121E8259 for <pcp@ietf.org>; Tue,  5 Nov 2013 06:20:10 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKUnj+lbJWbn1VaN67xC84fBPCOi//Utr0@postini.com; Tue, 05 Nov 2013 06:20:11 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 97E441B82C5 for <pcp@ietf.org>; Tue,  5 Nov 2013 06:20:05 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 785CC190043; Tue,  5 Nov 2013 06:20:05 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.03.0158.001; Tue, 5 Nov 2013 06:20:05 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Thread-Topic: [pcp] WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
Thread-Index: Ac7OuJO2HaM+dCF0QiWR4TXiSiGTNQLF53QwABXw4YAAA70aAAAPkLiA
Date: Tue, 5 Nov 2013 14:20:03 +0000
Message-ID: <387239E2-7A13-43AE-B009-3ADFB7ADBE8E@nominum.com>
References: <9b07e3810a7e4aed90b89b82b2eb7f5d@BY2PR03MB269.namprd03.prod.outlook.com> <0f2302afab944fbe8741cfe9212d145e@BN1PR03MB267.namprd03.prod.outlook.com> <60642641-34D8-4114-A34B-E40D05E49B1A@nominum.com> <5278961E.9080909@viagenie.ca>
In-Reply-To: <5278961E.9080909@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <85CEF80A11B78540812751D8EFDFAD88@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: PCP Working Group <pcp@ietf.org>
Subject: Re: [pcp] WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 14:20:48 -0000

On Nov 4, 2013, at 10:54 PM, Simon Perreault <simon.perreault@viagenie.ca> =
wrote:
> Am I looking at the same figure as you are?

No.   I apparently reviewed the -01 version, which probably reflects poorly=
 on my ability to detect problems in the document.   The new version has se=
veral improvements that I like, including that the chart is fixed.   Sorry =
for the confusion.


From simon.perreault@viagenie.ca  Tue Nov  5 06:44:25 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19FBC21E82D8 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 06:44:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JyWs9O7JqX6x for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 06:44:24 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 85F1421E82D4 for <pcp@ietf.org>; Tue,  5 Nov 2013 06:44:24 -0800 (PST)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:2001::1000]) by jazz.viagenie.ca (Postfix) with ESMTPSA id D6C5240405; Tue,  5 Nov 2013 09:44:23 -0500 (EST)
Message-ID: <52790446.6060207@viagenie.ca>
Date: Tue, 05 Nov 2013 06:44:22 -0800
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130805 Thunderbird/17.0.8
MIME-Version: 1.0
To: Cong Liu <gnocuil@gmail.com>
References: <9b07e3810a7e4aed90b89b82b2eb7f5d@BY2PR03MB269.namprd03.prod.outlook.com> <0f2302afab944fbe8741cfe9212d145e@BN1PR03MB267.namprd03.prod.outlook.com> <60642641-34D8-4114-A34B-E40D05E49B1A@nominum.com> <5278961E.9080909@viagenie.ca> <CAF+sHxGmhJcEE4j=gD56s2EokaAHi+TNT3Bdm0m0pJkU2kRyOQ@mail.gmail.com>
In-Reply-To: <CAF+sHxGmhJcEE4j=gD56s2EokaAHi+TNT3Bdm0m0pJkU2kRyOQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: pcp@ietf.org
Subject: Re: [pcp] WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 14:44:25 -0000

Le 2013-11-04 23:26, Cong Liu a écrit :
> I've read this document and I think it's a very useful work. I support
> advancing this document.

Great!

> A small problem: in section 3, is "Length: 3 bytes" a mistake?

Yes! To be fixed in the next revision.

Thanks for the review!

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From dthaler@microsoft.com  Tue Nov  5 07:42:34 2013
Return-Path: <dthaler@microsoft.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BDA021E8137 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 07:42:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.624
X-Spam-Level: 
X-Spam-Status: No, score=-103.624 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8K+qM38sAuA2 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 07:42:30 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0241.outbound.protection.outlook.com [207.46.163.241]) by ietfa.amsl.com (Postfix) with ESMTP id 0C15721E8094 for <pcp@ietf.org>; Tue,  5 Nov 2013 07:42:29 -0800 (PST)
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) with Microsoft SMTP Server (TLS) id 15.0.815.6; Tue, 5 Nov 2013 15:42:28 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.185]) by BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.185]) with mapi id 15.00.0815.000; Tue, 5 Nov 2013 15:42:28 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Dave Thaler <dthaler@microsoft.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
Thread-Index: Ac7OuJO2HaM+dCF0QiWR4TXiSiGTNQLF53QwABtMpLA=
Date: Tue, 5 Nov 2013 15:42:27 +0000
Message-ID: <e0592ded49e3458eb21772421f34b584@BY2PR03MB269.namprd03.prod.outlook.com>
References: <9b07e3810a7e4aed90b89b82b2eb7f5d@BY2PR03MB269.namprd03.prod.outlook.com> <0f2302afab944fbe8741cfe9212d145e@BN1PR03MB267.namprd03.prod.outlook.com>
In-Reply-To: <0f2302afab944fbe8741cfe9212d145e@BN1PR03MB267.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:67c:370:144:e4b2:e26c:88c8:ce2a]
x-forefront-prvs: 0021920B5A
x-forefront-antispam-report: SFV:NSPM; SFS:(13464003)(189002)(199002)(51704005)(377424004)(377454003)(79102001)(1511001)(87266001)(4396001)(83072001)(53806001)(81686001)(2656002)(33646001)(65816001)(80022001)(46102001)(51856001)(63696002)(85306002)(81816001)(80976001)(83322001)(69226001)(19580405001)(19580395003)(76482001)(74366001)(50986001)(47976001)(76796001)(81342001)(76786001)(76576001)(81542001)(74876001)(77096001)(15202345003)(56816003)(74316001)(74706001)(31966008)(54316002)(56776001)(74502001)(59766001)(47446002)(77982001)(74662001)(54356001)(15975445006)(49866001)(47736001)(3826001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR03MB269; H:BY2PR03MB269.namprd03.prod.outlook.com; CLIP:2001:67c:370:144:e4b2:e26c:88c8:ce2a; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Subject: Re: [pcp] WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 15:42:34 -0000

When responding to WGLC, what we chairs are looking for is a statement=20
of document quality (not really about whether the mechanism should move
forward).  That is, state whether you think the document is ready as is,
or if not, what issues you see.

Thanks for those who have sent reviews, and I hope to see more today.

-Dave

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Dave Thaler
> Sent: Monday, November 4, 2013 6:40 PM
> To: pcp@ietf.org
> Subject: Re: [pcp] WGLC: draft-ietf-pcp-port-set-03.txt comments due by
> NOV 5
>=20
> Reminder that the WGLC deadline is tomorrow.
> I've only seen two responses so far.
> We need more reviews, so consider this a prod.
>=20
> -Dave
>=20
> > -----Original Message-----
> > From: Dave Thaler
> > Sent: Monday, October 21, 2013 4:52 PM
> > To: pcp@ietf.org
> > Subject: WGLC: draft-ietf-pcp-port-set-03.txt comments due by NOV 5
> >
> > This email initiates a two-week Working Group Last Call on
> > draft-ietf-pcp-port-set-03 to conclude on Tuesday, November 5th.
> >
> > Please send comments to the list.
> >
> > -Dave
> >
> > > -----Original Message-----
> > > From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf
> > > Of Simon Perreault
> > > Sent: Monday, October 21, 2013 5:33 AM
> > > To: pcp@ietf.org
> > > Subject: Re: [pcp] I-D Action: draft-ietf-pcp-port-set-03.txt
> > >
> > > WG,
> > >
> > > This revision addresses comments received at IETF 87 in Berlin, namel=
y:
> > >
> > > - The "Port Set Offset" field has been replaced by a filed named
> > > "First Internal Port".
> > >
> > > - A new section "Examples" shows various usage examples.
> > >
> > > To this editor's knowledge there are no open issues left.
> > >
> > > Simon
> > >
> > > Le 2013-10-21 12:56, internet-drafts@ietf.org a =E9crit :
> > > >
> > > > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > > >  This draft is a work item of the Port Control Protocol Working
> > > > Group of the
> > > IETF.
> > > >
> > > > 	Title           : Port Control Protocol (PCP) Extension for Port S=
et
> > > Allocation
> > > > 	Author(s)       : Qiong Sun
> > > >                           Mohamed Boucadair
> > > >                           Senthil Sivakumar
> > > >                           Cathy Zhou
> > > >                           Tina Tsou
> > > >                           Simon Perreault
> > > > 	Filename        : draft-ietf-pcp-port-set-03.txt
> > > > 	Pages           : 15
> > > > 	Date            : 2013-10-21
> > > >
> > > > Abstract:
> > > >    This document defines an extension to PCP allowing clients to
> > > >    manipulate sets of ports as a whole.  This is accomplished by a =
new
> > > >    MAP option: PORT_SET.
> > > >
> > > >
> > > > The IETF datatracker status page for this draft is:
> > > > https://datatracker.ietf.org/doc/draft-ietf-pcp-port-set
> > > >
> > > > There's also a htmlized version available at:
> > > > http://tools.ietf.org/html/draft-ietf-pcp-port-set-03
> > > >
> > > > A diff from the previous version is available at:
> > > > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcp-port-set-03
> > > >
> > > >
> > > > Please note that it may take a couple of minutes from the time of
> > > > submission until the htmlized version and diff are available at
> > tools.ietf.org.
> > > >
> > > > Internet-Drafts are also available by anonymous FTP at:
> > > > ftp://ftp.ietf.org/internet-drafts/
> > > >
> > > > _______________________________________________
> > > > pcp mailing list
> > > > pcp@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/pcp
>=20
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp

From sureshk@juniper.net  Tue Nov  5 11:03:48 2013
Return-Path: <sureshk@juniper.net>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0A8111E8242 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 11:03:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lZ9jMraO8Sm4 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 11:03:43 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe005.messaging.microsoft.com [65.55.88.15]) by ietfa.amsl.com (Postfix) with ESMTP id 92F3D21E80BE for <pcp@ietf.org>; Tue,  5 Nov 2013 11:03:43 -0800 (PST)
Received: from mail121-tx2-R.bigfish.com (10.9.14.244) by TX2EHSOBE013.bigfish.com (10.9.40.33) with Microsoft SMTP Server id 14.1.225.22; Tue, 5 Nov 2013 19:03:36 +0000
Received: from mail121-tx2 (localhost [127.0.0.1])	by mail121-tx2-R.bigfish.com (Postfix) with ESMTP id 87BBDA016E; Tue,  5 Nov 2013 19:03:36 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -26
X-BigFish: VPS-26(zzbb2dI98dI9371I936eI1432I14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL17326ah8275dh1de097h186068hz2fh109h2a8h839h944he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1fe8h1ff5h209eh2216h1155h)
Received-SPF: pass (mail121-tx2: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=sureshk@juniper.net; helo=BL2PRD0510HT002.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(53754006)(377424004)(377454003)(479174003)(51704005)(199002)(189002)(24454002)(47736001)(50986001)(53806001)(46102001)(87266001)(54356001)(76482001)(80976001)(81342001)(81686001)(74876001)(56776001)(85306002)(4396001)(74706001)(81542001)(47976001)(31966008)(83322001)(2656002)(81816001)(19580405001)(77982001)(19580395003)(59766001)(49866001)(69226001)(74502001)(51856001)(47446002)(74662001)(74366001)(79102001)(63696002)(76796001)(76786001)(56816003)(83072001)(54316002)(76176001)(15202345003)(66066001)(80022001)(83506001)(36756003)(15975445006)(65816001); DIR:OUT; SFP:; SCL:1; SRVR:DM2PR05MB287; H:DM2PR05MB288.namprd05.prod.outlook.com; CLIP:66.129.224.36; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail121-tx2 (localhost.localdomain [127.0.0.1]) by mail121-tx2 (MessageSwitch) id 1383678185688348_30971; Tue,  5 Nov 2013 19:03:05 +0000 (UTC)
Received: from TX2EHSMHS001.bigfish.com (unknown [10.9.14.234])	by mail121-tx2.bigfish.com (Postfix) with ESMTP id C10051E006A; Tue,  5 Nov 2013 19:02:45 +0000 (UTC)
Received: from BL2PRD0510HT002.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS001.bigfish.com (10.9.99.101) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 5 Nov 2013 19:02:45 +0000
Received: from DM2PR05MB287.namprd05.prod.outlook.com (10.141.101.27) by BL2PRD0510HT002.namprd05.prod.outlook.com (10.255.100.37) with Microsoft SMTP Server (TLS) id 14.16.371.2; Tue, 5 Nov 2013 19:02:45 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com (10.141.101.11) by DM2PR05MB287.namprd05.prod.outlook.com (10.141.101.27) with Microsoft SMTP Server (TLS) id 15.0.800.7; Tue, 5 Nov 2013 19:02:43 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) by DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) with mapi id 15.00.0800.005; Tue, 5 Nov 2013 19:02:43 +0000
From: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHO2lmbQ60NWXm7bU68b/cwqgHqfA==
Date: Tue, 5 Nov 2013 19:02:42 +0000
Message-ID: <CE9E7D38.26B47%sureshk@juniper.net>
In-Reply-To: <CE80F267.246A1%sureshk@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [66.129.224.36]
x-forefront-prvs: 0021920B5A
Content-Type: text/plain; charset="us-ascii"
Content-ID: <80AFEB598E754A4BB9A9DC63A30378D4@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 19:03:49 -0000

Hi All,=20

This draft talks about issues with checkpointing flows in current
deployment, and how they can be addressed and handled efficiently with PCP.
Please review and share your comments.

Thanks
Suresh

On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
<sureshk@juniper.net> wrote:

>Dear All,=20
>
>We submitted a new draft that sketches flow high availability through PCP.
>Please review.
>
>-Suresh
>
>On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
><internet-drafts@ietf.org> wrote:
>
>>
>>A new version of I-D, draft-vinapamula-flow-ha-00.txt
>>has been successfully submitted by Suresh Vinapamula and posted to the
>>IETF repository.
>>
>>Filename:	 draft-vinapamula-flow-ha
>>Revision:	 00
>>Title:		 Flow high availability through PCP
>>Creation date:	 2013-10-14
>>Group:		 Individual Submission
>>Number of pages: 5
>>URL:            =20
>>http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.txt
>>Status:          http://datatracker.ietf.org/doc/draft-vinapamula-flow-ha
>>Htmlized:        http://tools.ietf.org/html/draft-vinapamula-flow-ha-00
>>
>>
>>Abstract:
>>   This document describes a mechanism for a host signal Network Address
>>   Translator's (NAT) High Availability (HA) module to checkpoint
>>   interested connections.
>>
>>                =20
>>       =20
>>
>>
>>Please note that it may take a couple of minutes from the time of
>>submission
>>until the htmlized version and diff are available at tools.ietf.org.
>>
>>The IETF Secretariat
>>
>>
>>
>



From repenno@cisco.com  Tue Nov  5 12:01:30 2013
Return-Path: <repenno@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DAFC21E82A9 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 12:01:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.565
X-Spam-Level: 
X-Spam-Status: No, score=-10.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id okWIv8wjW+L1 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 12:01:25 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 294E321E8223 for <pcp@ietf.org>; Tue,  5 Nov 2013 12:01:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2598; q=dns/txt; s=iport; t=1383681677; x=1384891277; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=7gjbpo7Bbq64/v6R7vp8mQV2BDIJ1+Qy3SDtvNn8ZTk=; b=jyoJ1ihyKg4OcwM+6I5mQ8waUlOIpMpYXAle6TtfEYykWxVmNZHzxqwC rKOgLzSPMQ/eboi9AXKoCKtHoRzWV1q55SN4DxDnormECLLsu5b6AIVvq I7ZlrkwoiLoJq2QladwKJrE7ycn9z9BGdKh97UihLY6YlS8NHVciFA+eX k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhcFAFdNeVKtJXG+/2dsb2JhbABZgwc4U786gSwWdIIlAQEBBAEBATc0CRQBCBgeNwslAgQBEgmHeA2+eI9ghC8DmAqBL5BagyaCKg
X-IronPort-AV: E=Sophos;i="4.93,640,1378857600"; d="scan'208";a="281077308"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-5.cisco.com with ESMTP; 05 Nov 2013 20:01:16 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id rA5K1G6k008501 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Nov 2013 20:01:16 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.192]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 14:01:16 -0600
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHO2mHI2WmROkm+QUyYwyILSTeCrw==
Date: Tue, 5 Nov 2013 20:01:15 +0000
Message-ID: <CE9E8C97.56CA%repenno@cisco.com>
In-Reply-To: <CE9E7D38.26B47%sureshk@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.86.108]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6C707F4034767941AA09149BDD85A8D8@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 20:01:30 -0000

Interesting extension, a few comments:

- You mention *flow* checkpointing but a many flows can match a MAP
mapping. So, should a device checkpoint all flows matching a MAP mapping
or only the mapping itself?
- Do you need a new error code when checkpointing can not be honored or
can you refuse an existing one? I prefer the latter, but irrespective,
draft need those details.
  - This should be a long lifetime error since if, for example, PCP Server
does not support checkpointing, you do not want client to keep requesting
HA constantly.
- It would be good if this mechanism is totally decoupled from NAT so, for
example, it could be used for FLOWDATA extension. It seems that way, but
worth mentioning.

Thanks,

Reinaldo


On 11/5/13 11:02 AM, "Suresh Kumar Vinapamula Venkata"
<sureshk@juniper.net> wrote:

>Hi All,=20
>
>This draft talks about issues with checkpointing flows in current
>deployment, and how they can be addressed and handled efficiently with
>PCP.
>Please review and share your comments.
>
>Thanks
>Suresh
>
>On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
><sureshk@juniper.net> wrote:
>
>>Dear All,=20
>>
>>We submitted a new draft that sketches flow high availability through
>>PCP.
>>Please review.
>>
>>-Suresh
>>
>>On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
>><internet-drafts@ietf.org> wrote:
>>
>>>
>>>A new version of I-D, draft-vinapamula-flow-ha-00.txt
>>>has been successfully submitted by Suresh Vinapamula and posted to the
>>>IETF repository.
>>>
>>>Filename:	 draft-vinapamula-flow-ha
>>>Revision:	 00
>>>Title:		 Flow high availability through PCP
>>>Creation date:	 2013-10-14
>>>Group:		 Individual Submission
>>>Number of pages: 5
>>>URL:           =20
>>>http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.txt
>>>Status:        =20
>>>http://datatracker.ietf.org/doc/draft-vinapamula-flow-ha
>>>Htmlized:        http://tools.ietf.org/html/draft-vinapamula-flow-ha-00
>>>
>>>
>>>Abstract:
>>>   This document describes a mechanism for a host signal Network Address
>>>   Translator's (NAT) High Availability (HA) module to checkpoint
>>>   interested connections.
>>>
>>>               =20
>>>       =20
>>>
>>>
>>>Please note that it may take a couple of minutes from the time of
>>>submission
>>>until the htmlized version and diff are available at tools.ietf.org.
>>>
>>>The IETF Secretariat
>>>
>>>
>>>
>>
>
>
>_______________________________________________
>pcp mailing list
>pcp@ietf.org
>https://www.ietf.org/mailman/listinfo/pcp


From repenno@cisco.com  Tue Nov  5 12:59:15 2013
Return-Path: <repenno@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D61011E8175 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 12:59:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.568
X-Spam-Level: 
X-Spam-Status: No, score=-10.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ybv7uavsR0JI for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 12:59:09 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id A7A5121E8099 for <pcp@ietf.org>; Tue,  5 Nov 2013 12:59:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7064; q=dns/txt; s=iport; t=1383685147; x=1384894747; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=9LhX+cFPauSeiJW61znzOQOCz8mmt3Fq5LbUJ57eSN8=; b=FIl8+tzfGghWgzPt+jjhvBOKkjV2BHBmankJMKYuzziqFfGRFSslwd5x WNELTXWDwUCM78TjqYPTkjQCrTybrjcI8ZJidBZx+sm32LfWJmqFnZAEv z+l1Yb9a23fTLvnsfd4ub5zC7+nwPn/jdGrCWx1WpwWc29yBFgZLgO6as I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAKZbeVKtJV2d/2dsb2JhbABZgwc4U786gSwWdIIlAQEBBDo/DAYBCBEEAQEfCTkUCQgBAQQBDQUJh3gNvmyOCoFPBwaEKQOYCoEvkFqDJoIq
X-IronPort-AV: E=Sophos;i="4.93,641,1378857600"; d="scan'208";a="281129729"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP; 05 Nov 2013 20:59:07 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id rA5Kx6wg005699 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Nov 2013 20:59:06 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.192]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 14:59:06 -0600
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: Ac7ZXRwLNJWMJz/iQNuoFr8x9AR4gwA+/yMA
Date: Tue, 5 Nov 2013 20:59:05 +0000
Message-ID: <CE9E98E9.56F4%repenno@cisco.com>
In-Reply-To: <F893BEC192403B489DBA38999068CF190594847F@ORSMSX102.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.86.108]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5384064BF80EEA41ABAB77EA66214334@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 20:59:15 -0000

Comments:

Certain things on this draft do not make much sense to me, for example,
battery level, light environment. Are there video servers that plan on
adapting its streaming resolution due to these changing conditions? Why
would they make that decision on behalf of the user.

Some of these attributes can already be gathered today through smartphone
APIs and conveyed to streaming servers. For example, when I stream Netflix
on my smartphone it knows my screen resolution through smartphone SDKs and
pass that to the server. Why the method in this draft is better or worse?
=20

Geolocation. Same thing.

Having said that, I know of implementations where the device pass static
metadata such as device-type, manufacturer type to the network for
analytics or inventory purpose.

I believe we need further discussion, a presentation would be helpful.


On 11/4/13 5:02 AM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com> wrote:

>Hi All,
>
>Draft (draft-mou-pcp-application-network-feedback) is a new draft that is
>submitted today on (PCP Extension for Signaling Feedback Information from
>the End-User Application to the Application Sever and to the Network).
>
>The draft is available at :
>http://www.ietf.org/internet-drafts/draft-mou-pcp-application-network-feed
>back-00.txt
>
>This draft addresses the need for more intelligence in the network and
>service infrastructure for better content delivery to optimize the
>network and devices resources. In this view, the draft proposes using PCP
>to signal information for: i)  Knowledge in the network and service
>platform about the available device and network conditions for the
>end-user and ii) Knowledge in the network about the content requirements
>in terms of devices and  network resources for content stored either in
>the network or in the application server.
>
>The abstract of the draft is as follows:
>" Abstract:    Nowadays users consumption style for video and multimedia
>applications is strongly changing.  Users are heavily counting on
>wireless and mobile devices for video streaming and interactive video
>   and multimedia applications.  This can be implemented for instance by
>having more intelligence in the service and the network infrastructure to
>better suit a differentiated users consumption  style.  This can be
>achieved=20
>   through having: (i) a knowledge in the network and service platform
>about the available device and network conditions for the end-user and
>(ii) a knowledge in the network about the content requirements in terms
>of devices
>   capabilities and network resources for content stored either in the
>network or in the application server.  To obtain such knowledge with no
>need for  changing the current infrastructure and in a generalized way to
>all
>   applications, feedback/notification mechanisms between the end-user
>application, the network and the service platform is needed to provide
>information helping the content delivery and adaptation decisions.  This
>document=20
>    is investigating such application-agnostic track.
>
>   This document extends the Port Control Protocol (PCP) RFC 6887
>[RFC6887] to allow: (i) the users application to notify the network and
>application server about its available resources in terms of
>   devices capabilities and network conditions as well as information
>about the user (e.g., location, mobility status) and (ii) the application
>server to notify the network about the requirements of
>   the content it stores in terms of devices and network resources.  A
>new PCP option, denoted the FEEDBACK, is specified to allow such feedback
>notification signaling.  This option is used with both PEER
>   and MAP Opcodes."
>
>Looking forward to having your feedback and more discussion on this draft.
>
>Regards,
>Hassnaa
>
>
>
>-----Original Message-----
>From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>Sent: Monday, November 04, 2013 4:06 AM
>To: Mohamed Boucadair; Moustafa, Hassnaa; Moses, Danny
>Subject: New Version Notification for
>draft-mou-pcp-application-network-feedback-00.txt
>
>
>A new version of I-D, draft-mou-pcp-application-network-feedback-00.txt
>has been successfully submitted by Hassnaa Moustafa and posted to the
>IETF repository.
>
>Filename:	 draft-mou-pcp-application-network-feedback
>Revision:	 00
>Title:		 PCP Extension for Signaling Feedback Information from the
>End-User Application to the Application Sever and to the Network
>Creation date:	 2013-11-04
>Group:		 Individual Submission
>Number of pages: 14
>URL:            =20
>http://www.ietf.org/internet-drafts/draft-mou-pcp-application-network-feed
>back-00.txt
>Status:         =20
>http://datatracker.ietf.org/doc/draft-mou-pcp-application-network-feedback
>Htmlized:       =20
>http://tools.ietf.org/html/draft-mou-pcp-application-network-feedback-00
>
>
>Abstract:
>   Nowadays users consumption style for video and multimedia
>   applications is strongly changing.  Users are heavily counting on
>   wireless and mobile devices for video streaming and interactive video
>   and multimedia applications.  This can be implemented for instance by
>   having more intelligence in the service and the network
>   infrastructure to better suit a differentiated users consumption
>   style.  This can be achieved through having: (i) a knowledge in the
>   network and service platform about the available device and network
>   conditions for the end-user and (ii) a knowledge in the network about
>   the content requirements in terms of devices capabilities and network
>   resources for content stored either in the network or in the
>   application server.  To obtain such knowledge with no need for
>   changing the current infrastructure and in a generalized way to all
>   applications, feedback/notification mechanisms between the end-user
>   application, the network and the service platform is needed to
>   provide information helping the content delivery and adaptation
>   decisions.  This document is investigating such application-agnostic
>   track.
>
>   This document extends the Port Control Protocol (PCP) RFC 6887
>   [RFC6887] to allow: (i) the users application to notify the network
>   and application server about its available resources in terms of
>   devices capabilities and network conditions as well as information
>   about the user (e.g., location, mobility status) and (ii) the
>   application server to notify the network about the requirements of
>   the content it stores in terms of devices and network resources.  A
>   new PCP option, denoted the FEEDBACK, is specified to allow such
>   feedback notification signaling.  This option is used with both PEER
>   and MAP Opcodes.
>
>                 =20
>       =20
>
>
>Please note that it may take a couple of minutes from the time of
>submission until the htmlized version and diff are available at
>tools.ietf.org.
>
>The IETF Secretariat
>


From hassnaa.moustafa@intel.com  Tue Nov  5 13:15:07 2013
Return-Path: <hassnaa.moustafa@intel.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71B1A21F9F99 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 13:15:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hl-5ARPDxztp for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 13:15:03 -0800 (PST)
Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by ietfa.amsl.com (Postfix) with ESMTP id E236421E809A for <pcp@ietf.org>; Tue,  5 Nov 2013 13:15:02 -0800 (PST)
Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 05 Nov 2013 13:15:02 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.93,641,1378882800"; d="scan'208";a="428406979"
Received: from orsmsx110.amr.corp.intel.com ([10.22.240.8]) by fmsmga002.fm.intel.com with ESMTP; 05 Nov 2013 13:14:51 -0800
Received: from orsmsx116.amr.corp.intel.com (10.22.240.14) by ORSMSX110.amr.corp.intel.com (10.22.240.8) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 5 Nov 2013 13:14:51 -0800
Received: from orsmsx102.amr.corp.intel.com ([169.254.1.203]) by ORSMSX116.amr.corp.intel.com ([10.22.240.14]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 13:14:51 -0800
From: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: Ac7ZXRwLNJWMJz/iQNuoFr8x9AR4gwA+/yMAAARoMYA=
Date: Tue, 5 Nov 2013 21:14:50 +0000
Message-ID: <F893BEC192403B489DBA38999068CF19059492C5@ORSMSX102.amr.corp.intel.com>
References: <F893BEC192403B489DBA38999068CF190594847F@ORSMSX102.amr.corp.intel.com> <CE9E98E9.56F4%repenno@cisco.com>
In-Reply-To: <CE9E98E9.56F4%repenno@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.22.254.140]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 21:15:07 -0000

Thanks Reinaldo for your feedback.
Please find my replies to clarify more (In the presentation that we prepare=
d for the draft we illustrate the motivation for that and hope to find time=
 in the session for presenting it):
- About battery level: currently there are several work looking into power =
efficient video streaming for mobile devices and the need for considering t=
hat (The MPEG green standard mentions the as use-case the Dynamic Adaptive =
Streaming over HTTP (DASH) and the need to consider battery level during th=
e video adaptation for power efficient video) --> video adaptation in a pow=
er efficient way by the end-server of a middle box node saves also in the n=
etwork bandwidth by a significant percent.
- About the "light of the environment": According to different experiments =
that we did on smartphones and tablets for video streaming, it is shown tha=
t the screen consumes a very big percentage of the device battery and so if=
 the video is adapted in a way to reduce the brightness for example this ca=
n save power.
- About the attributes (e.g. screen size, location, ...) gathering by smart=
phones API: yes this surely happens now and our idea is to continue to use =
the same way of gathering them by smart phones API for example but to conve=
y them through PCP signaling to either the application server or an intelli=
gent network node (here is the challenge --> how to intercept this informat=
ion by a network node to do intelligent decision --> we need a signaling pr=
otocol like PCP for doing that).

Hope that things are clearer now and hope to have time for more exchange th=
rough a presentation.

Regards,
Hassnaa


-----Original Message-----
From: Reinaldo Penno (repenno) [mailto:repenno@cisco.com]=20
Sent: Tuesday, November 05, 2013 12:59 PM
To: Moustafa, Hassnaa; pcp@ietf.org
Cc: Dave Thaler; mohamed.boucadair@orange.com; Moses, Danny
Subject: Re: New Submission: draft-mou-pcp-application-network-feedback-00.=
txt

Comments:

Certain things on this draft do not make much sense to me, for example, bat=
tery level, light environment. Are there video servers that plan on adaptin=
g its streaming resolution due to these changing conditions? Why would they=
 make that decision on behalf of the user.

Some of these attributes can already be gathered today through smartphone A=
PIs and conveyed to streaming servers. For example, when I stream Netflix o=
n my smartphone it knows my screen resolution through smartphone SDKs and p=
ass that to the server. Why the method in this draft is better or worse?
=20

Geolocation. Same thing.

Having said that, I know of implementations where the device pass static me=
tadata such as device-type, manufacturer type to the network for analytics =
or inventory purpose.

I believe we need further discussion, a presentation would be helpful.


On 11/4/13 5:02 AM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com> wrote:

>Hi All,
>
>Draft (draft-mou-pcp-application-network-feedback) is a new draft that=20
>is submitted today on (PCP Extension for Signaling Feedback Information=20
>from the End-User Application to the Application Sever and to the Network)=
.
>
>The draft is available at :
>http://www.ietf.org/internet-drafts/draft-mou-pcp-application-network-f
>eed
>back-00.txt
>
>This draft addresses the need for more intelligence in the network and=20
>service infrastructure for better content delivery to optimize the=20
>network and devices resources. In this view, the draft proposes using=20
>PCP to signal information for: i)  Knowledge in the network and service=20
>platform about the available device and network conditions for the=20
>end-user and ii) Knowledge in the network about the content=20
>requirements in terms of devices and  network resources for content=20
>stored either in the network or in the application server.
>
>The abstract of the draft is as follows:
>" Abstract:    Nowadays users consumption style for video and multimedia
>applications is strongly changing.  Users are heavily counting on=20
>wireless and mobile devices for video streaming and interactive video
>   and multimedia applications.  This can be implemented for instance=20
>by having more intelligence in the service and the network=20
>infrastructure to better suit a differentiated users consumption =20
>style.  This can be achieved
>   through having: (i) a knowledge in the network and service platform=20
>about the available device and network conditions for the end-user and
>(ii) a knowledge in the network about the content requirements in terms=20
>of devices
>   capabilities and network resources for content stored either in the=20
>network or in the application server.  To obtain such knowledge with no=20
>need for  changing the current infrastructure and in a generalized way=20
>to all
>   applications, feedback/notification mechanisms between the end-user=20
>application, the network and the service platform is needed to provide=20
>information helping the content delivery and adaptation decisions. =20
>This document
>    is investigating such application-agnostic track.
>
>   This document extends the Port Control Protocol (PCP) RFC 6887=20
>[RFC6887] to allow: (i) the users application to notify the network and=20
>application server about its available resources in terms of
>   devices capabilities and network conditions as well as information=20
>about the user (e.g., location, mobility status) and (ii) the=20
>application server to notify the network about the requirements of
>   the content it stores in terms of devices and network resources.  A=20
>new PCP option, denoted the FEEDBACK, is specified to allow such=20
>feedback notification signaling.  This option is used with both PEER
>   and MAP Opcodes."
>
>Looking forward to having your feedback and more discussion on this draft.
>
>Regards,
>Hassnaa
>
>
>
>-----Original Message-----
>From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>Sent: Monday, November 04, 2013 4:06 AM
>To: Mohamed Boucadair; Moustafa, Hassnaa; Moses, Danny
>Subject: New Version Notification for
>draft-mou-pcp-application-network-feedback-00.txt
>
>
>A new version of I-D, draft-mou-pcp-application-network-feedback-00.txt
>has been successfully submitted by Hassnaa Moustafa and posted to the=20
>IETF repository.
>
>Filename:	 draft-mou-pcp-application-network-feedback
>Revision:	 00
>Title:		 PCP Extension for Signaling Feedback Information from the
>End-User Application to the Application Sever and to the Network
>Creation date:	 2013-11-04
>Group:		 Individual Submission
>Number of pages: 14
>URL:            =20
>http://www.ietf.org/internet-drafts/draft-mou-pcp-application-network-f
>eed
>back-00.txt
>Status:         =20
>http://datatracker.ietf.org/doc/draft-mou-pcp-application-network-feedback
>Htmlized:       =20
>http://tools.ietf.org/html/draft-mou-pcp-application-network-feedback-0
>0
>
>
>Abstract:
>   Nowadays users consumption style for video and multimedia
>   applications is strongly changing.  Users are heavily counting on
>   wireless and mobile devices for video streaming and interactive video
>   and multimedia applications.  This can be implemented for instance by
>   having more intelligence in the service and the network
>   infrastructure to better suit a differentiated users consumption
>   style.  This can be achieved through having: (i) a knowledge in the
>   network and service platform about the available device and network
>   conditions for the end-user and (ii) a knowledge in the network about
>   the content requirements in terms of devices capabilities and network
>   resources for content stored either in the network or in the
>   application server.  To obtain such knowledge with no need for
>   changing the current infrastructure and in a generalized way to all
>   applications, feedback/notification mechanisms between the end-user
>   application, the network and the service platform is needed to
>   provide information helping the content delivery and adaptation
>   decisions.  This document is investigating such application-agnostic
>   track.
>
>   This document extends the Port Control Protocol (PCP) RFC 6887
>   [RFC6887] to allow: (i) the users application to notify the network
>   and application server about its available resources in terms of
>   devices capabilities and network conditions as well as information
>   about the user (e.g., location, mobility status) and (ii) the
>   application server to notify the network about the requirements of
>   the content it stores in terms of devices and network resources.  A
>   new PCP option, denoted the FEEDBACK, is specified to allow such
>   feedback notification signaling.  This option is used with both PEER
>   and MAP Opcodes.
>
>                 =20
>       =20
>
>
>Please note that it may take a couple of minutes from the time of=20
>submission until the htmlized version and diff are available at=20
>tools.ietf.org.
>
>The IETF Secretariat
>


From repenno@cisco.com  Tue Nov  5 13:26:57 2013
Return-Path: <repenno@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C0EC21E80C4 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 13:26:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VU0TYdEQFkWN for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 13:26:51 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id A37B621E80BA for <pcp@ietf.org>; Tue,  5 Nov 2013 13:26:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9742; q=dns/txt; s=iport; t=1383686811; x=1384896411; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=WQxttGxurUNXjWQ+v3bz8sVn361Z+hLJ8nU6oRy5jBQ=; b=IdqOciumNj7X0hbH+lSpQ1teXIQlvvF1swjV6o2m+UMaqC01lbwRGEAT prGqcahALMYv/tG87dvsxE38IRkLftLbcybIpXRGsmcoliyfJXiN+l6p/ rS8byQ5mBuM+49LWUqNNbwjp60MU+6jmdTcRWTL0cs3HeKU8AYv6kb3E6 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAIpheVKtJXG9/2dsb2JhbABZgwc4U78+gSwWdIIlAQEBBCcTPwwGAQgRBAEBHwk5FAkIAQEEAQ0FCYd4Db50jgoXgTgHBoQpA5gKgS+QWoMmgio
X-IronPort-AV: E=Sophos;i="4.93,641,1378857600"; d="scan'208";a="280923174"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-1.cisco.com with ESMTP; 05 Nov 2013 21:26:50 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id rA5LQoAu010899 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Nov 2013 21:26:50 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.192]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 15:26:50 -0600
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: Ac7ZXRwLNJWMJz/iQNuoFr8x9AR4gwA+/yMAAARoMYD//+R8gA==
Date: Tue, 5 Nov 2013 21:26:49 +0000
Message-ID: <CE9EA1E0.5732%repenno@cisco.com>
In-Reply-To: <F893BEC192403B489DBA38999068CF19059492C5@ORSMSX102.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.86.108]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E7E8DAF65D1B4B4C99E09DCB1B039C71@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 21:26:57 -0000

On 11/5/13 1:14 PM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com> wrote:

>Thanks Reinaldo for your feedback.
>Please find my replies to clarify more (In the presentation that we
>prepared for the draft we illustrate the motivation for that and hope to
>find time in the session for presenting it):
>- About battery level: currently there are several work looking into
>power efficient video streaming for mobile devices and the need for
>considering that (The MPEG green standard mentions the as use-case the
>Dynamic Adaptive Streaming over HTTP (DASH) and the need to consider
>battery level during the video adaptation for power efficient video) -->
>video adaptation in a power efficient way by the end-server of a middle
>box node saves also in the network bandwidth by a significant percent.

[RP] Can you include this MPEG reference in the draft? I personally
believe more details are needed.

>- About the "light of the environment": According to different
>experiments that we did on smartphones and tablets for video streaming,
>it is shown that the screen consumes a very big percentage of the device
>battery and so if the video is adapted in a way to reduce the brightness
>for example this can save power.

[RP] Smartphones and tablets already have auto brightness. How much extra
savings you can get?

>- About the attributes (e.g. screen size, location, ...) gathering by
>smartphones API: yes this surely happens now and our idea is to continue
>to use the same way of gathering them by smart phones API for example but
>to convey them through PCP signaling to either the application server or
>an intelligent network node (here is the challenge --> how to intercept
>this information by a network node to do intelligent decision --> we need
>a signaling protocol like PCP for doing that).


[RP] If you have several applications on a smartphone, will each one
implement a PCP Client in oder to convey these metadata or there are plans
on some kernel implementation that expose some API?

>
>Hope that things are clearer now and hope to have time for more exchange
>through a presentation.
>
>Regards,
>Hassnaa
>
>
>-----Original Message-----
>From: Reinaldo Penno (repenno) [mailto:repenno@cisco.com]
>Sent: Tuesday, November 05, 2013 12:59 PM
>To: Moustafa, Hassnaa; pcp@ietf.org
>Cc: Dave Thaler; mohamed.boucadair@orange.com; Moses, Danny
>Subject: Re: New Submission:
>draft-mou-pcp-application-network-feedback-00.txt
>
>Comments:
>
>Certain things on this draft do not make much sense to me, for example,
>battery level, light environment. Are there video servers that plan on
>adapting its streaming resolution due to these changing conditions? Why
>would they make that decision on behalf of the user.
>
>Some of these attributes can already be gathered today through smartphone
>APIs and conveyed to streaming servers. For example, when I stream
>Netflix on my smartphone it knows my screen resolution through smartphone
>SDKs and pass that to the server. Why the method in this draft is better
>or worse?
>=20
>
>Geolocation. Same thing.
>
>Having said that, I know of implementations where the device pass static
>metadata such as device-type, manufacturer type to the network for
>analytics or inventory purpose.
>
>I believe we need further discussion, a presentation would be helpful.
>
>
>On 11/4/13 5:02 AM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>
>wrote:
>
>>Hi All,
>>
>>Draft (draft-mou-pcp-application-network-feedback) is a new draft that
>>is submitted today on (PCP Extension for Signaling Feedback Information
>>from the End-User Application to the Application Sever and to the
>>Network).
>>
>>The draft is available at :
>>http://www.ietf.org/internet-drafts/draft-mou-pcp-application-network-f
>>eed
>>back-00.txt
>>
>>This draft addresses the need for more intelligence in the network and
>>service infrastructure for better content delivery to optimize the
>>network and devices resources. In this view, the draft proposes using
>>PCP to signal information for: i)  Knowledge in the network and service
>>platform about the available device and network conditions for the
>>end-user and ii) Knowledge in the network about the content
>>requirements in terms of devices and  network resources for content
>>stored either in the network or in the application server.
>>
>>The abstract of the draft is as follows:
>>" Abstract:    Nowadays users consumption style for video and multimedia
>>applications is strongly changing.  Users are heavily counting on
>>wireless and mobile devices for video streaming and interactive video
>>   and multimedia applications.  This can be implemented for instance
>>by having more intelligence in the service and the network
>>infrastructure to better suit a differentiated users consumption
>>style.  This can be achieved
>>   through having: (i) a knowledge in the network and service platform
>>about the available device and network conditions for the end-user and
>>(ii) a knowledge in the network about the content requirements in terms
>>of devices
>>   capabilities and network resources for content stored either in the
>>network or in the application server.  To obtain such knowledge with no
>>need for  changing the current infrastructure and in a generalized way
>>to all
>>   applications, feedback/notification mechanisms between the end-user
>>application, the network and the service platform is needed to provide
>>information helping the content delivery and adaptation decisions.
>>This document
>>    is investigating such application-agnostic track.
>>
>>   This document extends the Port Control Protocol (PCP) RFC 6887
>>[RFC6887] to allow: (i) the users application to notify the network and
>>application server about its available resources in terms of
>>   devices capabilities and network conditions as well as information
>>about the user (e.g., location, mobility status) and (ii) the
>>application server to notify the network about the requirements of
>>   the content it stores in terms of devices and network resources.  A
>>new PCP option, denoted the FEEDBACK, is specified to allow such
>>feedback notification signaling.  This option is used with both PEER
>>   and MAP Opcodes."
>>
>>Looking forward to having your feedback and more discussion on this
>>draft.
>>
>>Regards,
>>Hassnaa
>>
>>
>>
>>-----Original Message-----
>>From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>Sent: Monday, November 04, 2013 4:06 AM
>>To: Mohamed Boucadair; Moustafa, Hassnaa; Moses, Danny
>>Subject: New Version Notification for
>>draft-mou-pcp-application-network-feedback-00.txt
>>
>>
>>A new version of I-D, draft-mou-pcp-application-network-feedback-00.txt
>>has been successfully submitted by Hassnaa Moustafa and posted to the
>>IETF repository.
>>
>>Filename:	 draft-mou-pcp-application-network-feedback
>>Revision:	 00
>>Title:		 PCP Extension for Signaling Feedback Information from the
>>End-User Application to the Application Sever and to the Network
>>Creation date:	 2013-11-04
>>Group:		 Individual Submission
>>Number of pages: 14
>>URL:            =20
>>http://www.ietf.org/internet-drafts/draft-mou-pcp-application-network-f
>>eed
>>back-00.txt
>>Status:         =20
>>http://datatracker.ietf.org/doc/draft-mou-pcp-application-network-feedbac
>>k
>>Htmlized:       =20
>>http://tools.ietf.org/html/draft-mou-pcp-application-network-feedback-0
>>0
>>
>>
>>Abstract:
>>   Nowadays users consumption style for video and multimedia
>>   applications is strongly changing.  Users are heavily counting on
>>   wireless and mobile devices for video streaming and interactive video
>>   and multimedia applications.  This can be implemented for instance by
>>   having more intelligence in the service and the network
>>   infrastructure to better suit a differentiated users consumption
>>   style.  This can be achieved through having: (i) a knowledge in the
>>   network and service platform about the available device and network
>>   conditions for the end-user and (ii) a knowledge in the network about
>>   the content requirements in terms of devices capabilities and network
>>   resources for content stored either in the network or in the
>>   application server.  To obtain such knowledge with no need for
>>   changing the current infrastructure and in a generalized way to all
>>   applications, feedback/notification mechanisms between the end-user
>>   application, the network and the service platform is needed to
>>   provide information helping the content delivery and adaptation
>>   decisions.  This document is investigating such application-agnostic
>>   track.
>>
>>   This document extends the Port Control Protocol (PCP) RFC 6887
>>   [RFC6887] to allow: (i) the users application to notify the network
>>   and application server about its available resources in terms of
>>   devices capabilities and network conditions as well as information
>>   about the user (e.g., location, mobility status) and (ii) the
>>   application server to notify the network about the requirements of
>>   the content it stores in terms of devices and network resources.  A
>>   new PCP option, denoted the FEEDBACK, is specified to allow such
>>   feedback notification signaling.  This option is used with both PEER
>>   and MAP Opcodes.
>>
>>                =20
>>       =20
>>
>>
>>Please note that it may take a couple of minutes from the time of
>>submission until the htmlized version and diff are available at
>>tools.ietf.org.
>>
>>The IETF Secretariat
>>
>


From ssenthil@cisco.com  Tue Nov  5 13:27:47 2013
Return-Path: <ssenthil@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E50E21E8064 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 13:27:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.998
X-Spam-Level: 
X-Spam-Status: No, score=-9.998 tagged_above=-999 required=5 tests=[AWL=0.601,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AnKM29zvNGGg for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 13:27:41 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 7415121E80C4 for <pcp@ietf.org>; Tue,  5 Nov 2013 13:27:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3159; q=dns/txt; s=iport; t=1383686852; x=1384896452; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=kWe6up4ORDWHPPWENDp2ARSZFd+J9UoGOB+fje9N7jw=; b=CG9xEUn+1WGBdebf1g7pAF4wr58PxGoyE7P5StQIoDu4htMrRlfrqZf+ tHe0+7KFW9q3OwXoxV6n+z3b79cvCmLBd++lLdwVQ5ds36c3q6CBOY3MC B80IyIMHlQY+u47rO62Ao8dVjjX3QBmw4Vr8ooKGCbw5LiLXu30IeOMfF E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhcFAEJheVKtJXG9/2dsb2JhbABZgwc4U78+gSwWdIIlAQEBBAEBATc0CRQBCBgeNwslAgQBEgmHeA2+dI9ghC8DmAqBL5BagyaCKg
X-IronPort-AV: E=Sophos;i="4.93,641,1378857600"; d="scan'208";a="281080463"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-2.cisco.com with ESMTP; 05 Nov 2013 21:27:26 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id rA5LRPli011785 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Nov 2013 21:27:25 GMT
Received: from xmb-rcd-x15.cisco.com ([169.254.5.54]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 15:27:24 -0600
From: "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>, "Suresh Kumar Vinapamula Venkata" <sureshk@juniper.net>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHOyLL/gCwN85yQD0CDyU03potPTJn0KroAgCNbqgCAABBcgP//s3uA
Date: Tue, 5 Nov 2013 21:27:24 +0000
Message-ID: <CE9ECA21.C9B8A%ssenthil@cisco.com>
In-Reply-To: <CE9E8C97.56CA%repenno@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.8.130913
x-originating-ip: [10.82.236.65]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E8C8045552CAD74A9FE44602F2314A8F@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 21:27:47 -0000

Thanks for the comments, please see inline.

On 11/5/13 3:01 PM, "Reinaldo Penno (repenno)" <repenno@cisco.com> wrote:

>Interesting extension, a few comments:
>
>- You mention *flow* checkpointing but a many flows can match a MAP
>mapping. So, should a device checkpoint all flows matching a MAP mapping
>or only the mapping itself?

All flows matching a MAP mapping need to be checkpointed.

>- Do you need a new error code when checkpointing can not be honored or
>can you refuse an existing one? I prefer the latter, but irrespective,
>draft need those details.

Ok, will do in the next rev.

>  - This should be a long lifetime error since if, for example, PCP Server
>does not support checkpointing, you do not want client to keep requesting
>HA constantly.

Agree.

>- It would be good if this mechanism is totally decoupled from NAT so, for
>example, it could be used for FLOWDATA extension. It seems that way, but
>worth mentioning.

Right, it is that way, except the abstract :-), we will wordsmith in the
next rev.

Thanks
Senthil
>
>Thanks,
>
>Reinaldo
>
>
>On 11/5/13 11:02 AM, "Suresh Kumar Vinapamula Venkata"
><sureshk@juniper.net> wrote:
>
>>Hi All,=20
>>
>>This draft talks about issues with checkpointing flows in current
>>deployment, and how they can be addressed and handled efficiently with
>>PCP.
>>Please review and share your comments.
>>
>>Thanks
>>Suresh
>>
>>On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
>><sureshk@juniper.net> wrote:
>>
>>>Dear All,=20
>>>
>>>We submitted a new draft that sketches flow high availability through
>>>PCP.
>>>Please review.
>>>
>>>-Suresh
>>>
>>>On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
>>><internet-drafts@ietf.org> wrote:
>>>
>>>>
>>>>A new version of I-D, draft-vinapamula-flow-ha-00.txt
>>>>has been successfully submitted by Suresh Vinapamula and posted to the
>>>>IETF repository.
>>>>
>>>>Filename:	 draft-vinapamula-flow-ha
>>>>Revision:	 00
>>>>Title:		 Flow high availability through PCP
>>>>Creation date:	 2013-10-14
>>>>Group:		 Individual Submission
>>>>Number of pages: 5
>>>>URL:          =20
>>>>http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.txt
>>>>Status:       =20
>>>>http://datatracker.ietf.org/doc/draft-vinapamula-flow-ha
>>>>Htmlized:        http://tools.ietf.org/html/draft-vinapamula-flow-ha-00
>>>>
>>>>
>>>>Abstract:
>>>>   This document describes a mechanism for a host signal Network
>>>>Address
>>>>   Translator's (NAT) High Availability (HA) module to checkpoint
>>>>   interested connections.
>>>>
>>>>              =20
>>>>       =20
>>>>
>>>>
>>>>Please note that it may take a couple of minutes from the time of
>>>>submission
>>>>until the htmlized version and diff are available at tools.ietf.org.
>>>>
>>>>The IETF Secretariat
>>>>
>>>>
>>>>
>>>
>>
>>
>>_______________________________________________
>>pcp mailing list
>>pcp@ietf.org
>>https://www.ietf.org/mailman/listinfo/pcp
>
>_______________________________________________
>pcp mailing list
>pcp@ietf.org
>https://www.ietf.org/mailman/listinfo/pcp


From hassnaa.moustafa@intel.com  Tue Nov  5 13:38:48 2013
Return-Path: <hassnaa.moustafa@intel.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1485111E81BC for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 13:38:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.449
X-Spam-Level: 
X-Spam-Status: No, score=-9.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_BACK=2.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bZ+xxstmTYER for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 13:38:29 -0800 (PST)
Received: from mga14.intel.com (mga14.intel.com [143.182.124.37]) by ietfa.amsl.com (Postfix) with ESMTP id CA4B421E8099 for <pcp@ietf.org>; Tue,  5 Nov 2013 13:38:13 -0800 (PST)
Received: from azsmga002.ch.intel.com ([10.2.17.35]) by azsmga102.ch.intel.com with ESMTP; 05 Nov 2013 13:38:12 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.93,535,1378882800"; d="scan'208";a="317400435"
Received: from orsmsx101.amr.corp.intel.com ([10.22.225.128]) by AZSMGA002.ch.intel.com with ESMTP; 05 Nov 2013 13:38:11 -0800
Received: from orsmsx156.amr.corp.intel.com (10.22.240.22) by ORSMSX101.amr.corp.intel.com (10.22.225.128) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 5 Nov 2013 13:38:10 -0800
Received: from orsmsx102.amr.corp.intel.com ([169.254.1.203]) by ORSMSX156.amr.corp.intel.com ([169.254.8.134]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 13:38:10 -0800
From: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: Ac7ZXRwLNJWMJz/iQNuoFr8x9AR4gwA+/yMAAARoMYD//+R8gP//3LdA
Date: Tue, 5 Nov 2013 21:38:09 +0000
Message-ID: <F893BEC192403B489DBA38999068CF1905949370@ORSMSX102.amr.corp.intel.com>
References: <F893BEC192403B489DBA38999068CF19059492C5@ORSMSX102.amr.corp.intel.com> <CE9EA1E0.5732%repenno@cisco.com>
In-Reply-To: <CE9EA1E0.5732%repenno@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.22.254.138]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 21:38:48 -0000

Please find the answer to your questions.

[RP] Can you include this MPEG reference in the draft? I personally believe=
 more details are needed.
	Hassnaa: Sure, we will include the MPEG version in the next version of the=
 draft. It is mentioned currently in our presentation slides.

[RP] Smartphones and tablets already have auto brightness. How much extra s=
avings you can get?
Hassnaa: Yes but when the device does the auto brightness this consumes a l=
ot of its device resources.

[RP] If you have several applications on a smartphone, will each one implem=
ent a PCP Client in oder to convey these metadata or there are plans on som=
e kernel implementation that expose some API?
Hassnaa: The current thought is to use one PCP client on each device for an=
y metadata transmission and not per application (we mention in the draft th=
at this proposed PCP extension through the Feedback option is meant to work=
 with the flowdata option)


Thanks.
Hassnaa
-----Original Message-----
From: Reinaldo Penno (repenno) [mailto:repenno@cisco.com]=20
Sent: Tuesday, November 05, 2013 1:27 PM
To: Moustafa, Hassnaa; pcp@ietf.org
Cc: Dave Thaler; mohamed.boucadair@orange.com; Moses, Danny
Subject: Re: New Submission: draft-mou-pcp-application-network-feedback-00.=
txt



On 11/5/13 1:14 PM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com> wrote:

>Thanks Reinaldo for your feedback.
>Please find my replies to clarify more (In the presentation that we=20
>prepared for the draft we illustrate the motivation for that and hope=20
>to find time in the session for presenting it):
>- About battery level: currently there are several work looking into=20
>power efficient video streaming for mobile devices and the need for=20
>considering that (The MPEG green standard mentions the as use-case the=20
>Dynamic Adaptive Streaming over HTTP (DASH) and the need to consider=20
>battery level during the video adaptation for power efficient video)=20
>--> video adaptation in a power efficient way by the end-server of a=20
>middle box node saves also in the network bandwidth by a significant perce=
nt.

[RP] Can you include this MPEG reference in the draft? I personally believe=
 more details are needed.

>- About the "light of the environment": According to different=20
>experiments that we did on smartphones and tablets for video streaming,=20
>it is shown that the screen consumes a very big percentage of the=20
>device battery and so if the video is adapted in a way to reduce the=20
>brightness for example this can save power.

[RP] Smartphones and tablets already have auto brightness. How much extra s=
avings you can get?

>- About the attributes (e.g. screen size, location, ...) gathering by=20
>smartphones API: yes this surely happens now and our idea is to=20
>continue to use the same way of gathering them by smart phones API for=20
>example but to convey them through PCP signaling to either the=20
>application server or an intelligent network node (here is the=20
>challenge --> how to intercept this information by a network node to do=20
>intelligent decision --> we need a signaling protocol like PCP for doing t=
hat).


[RP] If you have several applications on a smartphone, will each one implem=
ent a PCP Client in oder to convey these metadata or there are plans on som=
e kernel implementation that expose some API?

>
>Hope that things are clearer now and hope to have time for more=20
>exchange through a presentation.
>
>Regards,
>Hassnaa
>
>
>-----Original Message-----
>From: Reinaldo Penno (repenno) [mailto:repenno@cisco.com]
>Sent: Tuesday, November 05, 2013 12:59 PM
>To: Moustafa, Hassnaa; pcp@ietf.org
>Cc: Dave Thaler; mohamed.boucadair@orange.com; Moses, Danny
>Subject: Re: New Submission:
>draft-mou-pcp-application-network-feedback-00.txt
>
>Comments:
>
>Certain things on this draft do not make much sense to me, for example,=20
>battery level, light environment. Are there video servers that plan on=20
>adapting its streaming resolution due to these changing conditions? Why=20
>would they make that decision on behalf of the user.
>
>Some of these attributes can already be gathered today through=20
>smartphone APIs and conveyed to streaming servers. For example, when I=20
>stream Netflix on my smartphone it knows my screen resolution through=20
>smartphone SDKs and pass that to the server. Why the method in this=20
>draft is better or worse?
>=20
>
>Geolocation. Same thing.
>
>Having said that, I know of implementations where the device pass=20
>static metadata such as device-type, manufacturer type to the network=20
>for analytics or inventory purpose.
>
>I believe we need further discussion, a presentation would be helpful.
>
>
>On 11/4/13 5:02 AM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>
>wrote:
>
>>Hi All,
>>
>>Draft (draft-mou-pcp-application-network-feedback) is a new draft that=20
>>is submitted today on (PCP Extension for Signaling Feedback=20
>>Information from the End-User Application to the Application Sever and=20
>>to the Network).
>>
>>The draft is available at :
>>http://www.ietf.org/internet-drafts/draft-mou-pcp-application-network-
>>f
>>eed
>>back-00.txt
>>
>>This draft addresses the need for more intelligence in the network and=20
>>service infrastructure for better content delivery to optimize the=20
>>network and devices resources. In this view, the draft proposes using=20
>>PCP to signal information for: i)  Knowledge in the network and=20
>>service platform about the available device and network conditions for=20
>>the end-user and ii) Knowledge in the network about the content=20
>>requirements in terms of devices and  network resources for content=20
>>stored either in the network or in the application server.
>>
>>The abstract of the draft is as follows:
>>" Abstract:    Nowadays users consumption style for video and multimedia
>>applications is strongly changing.  Users are heavily counting on=20
>>wireless and mobile devices for video streaming and interactive video
>>   and multimedia applications.  This can be implemented for instance=20
>>by having more intelligence in the service and the network=20
>>infrastructure to better suit a differentiated users consumption=20
>>style.  This can be achieved
>>   through having: (i) a knowledge in the network and service platform=20
>>about the available device and network conditions for the end-user and
>>(ii) a knowledge in the network about the content requirements in=20
>>terms of devices
>>   capabilities and network resources for content stored either in the=20
>>network or in the application server.  To obtain such knowledge with=20
>>no need for  changing the current infrastructure and in a generalized=20
>>way to all
>>   applications, feedback/notification mechanisms between the end-user=20
>>application, the network and the service platform is needed to provide=20
>>information helping the content delivery and adaptation decisions.
>>This document
>>    is investigating such application-agnostic track.
>>
>>   This document extends the Port Control Protocol (PCP) RFC 6887=20
>>[RFC6887] to allow: (i) the users application to notify the network=20
>>and application server about its available resources in terms of
>>   devices capabilities and network conditions as well as information=20
>>about the user (e.g., location, mobility status) and (ii) the=20
>>application server to notify the network about the requirements of
>>   the content it stores in terms of devices and network resources.  A=20
>>new PCP option, denoted the FEEDBACK, is specified to allow such=20
>>feedback notification signaling.  This option is used with both PEER
>>   and MAP Opcodes."
>>
>>Looking forward to having your feedback and more discussion on this=20
>>draft.
>>
>>Regards,
>>Hassnaa
>>
>>
>>
>>-----Original Message-----
>>From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>Sent: Monday, November 04, 2013 4:06 AM
>>To: Mohamed Boucadair; Moustafa, Hassnaa; Moses, Danny
>>Subject: New Version Notification for
>>draft-mou-pcp-application-network-feedback-00.txt
>>
>>
>>A new version of I-D,=20
>>draft-mou-pcp-application-network-feedback-00.txt
>>has been successfully submitted by Hassnaa Moustafa and posted to the=20
>>IETF repository.
>>
>>Filename:	 draft-mou-pcp-application-network-feedback
>>Revision:	 00
>>Title:		 PCP Extension for Signaling Feedback Information from the
>>End-User Application to the Application Sever and to the Network
>>Creation date:	 2013-11-04
>>Group:		 Individual Submission
>>Number of pages: 14
>>URL:            =20
>>http://www.ietf.org/internet-drafts/draft-mou-pcp-application-network-
>>f
>>eed
>>back-00.txt
>>Status:         =20
>>http://datatracker.ietf.org/doc/draft-mou-pcp-application-network-feed
>>bac
>>k
>>Htmlized:       =20
>>http://tools.ietf.org/html/draft-mou-pcp-application-network-feedback-
>>0
>>0
>>
>>
>>Abstract:
>>   Nowadays users consumption style for video and multimedia
>>   applications is strongly changing.  Users are heavily counting on
>>   wireless and mobile devices for video streaming and interactive video
>>   and multimedia applications.  This can be implemented for instance by
>>   having more intelligence in the service and the network
>>   infrastructure to better suit a differentiated users consumption
>>   style.  This can be achieved through having: (i) a knowledge in the
>>   network and service platform about the available device and network
>>   conditions for the end-user and (ii) a knowledge in the network about
>>   the content requirements in terms of devices capabilities and network
>>   resources for content stored either in the network or in the
>>   application server.  To obtain such knowledge with no need for
>>   changing the current infrastructure and in a generalized way to all
>>   applications, feedback/notification mechanisms between the end-user
>>   application, the network and the service platform is needed to
>>   provide information helping the content delivery and adaptation
>>   decisions.  This document is investigating such application-agnostic
>>   track.
>>
>>   This document extends the Port Control Protocol (PCP) RFC 6887
>>   [RFC6887] to allow: (i) the users application to notify the network
>>   and application server about its available resources in terms of
>>   devices capabilities and network conditions as well as information
>>   about the user (e.g., location, mobility status) and (ii) the
>>   application server to notify the network about the requirements of
>>   the content it stores in terms of devices and network resources.  A
>>   new PCP option, denoted the FEEDBACK, is specified to allow such
>>   feedback notification signaling.  This option is used with both PEER
>>   and MAP Opcodes.
>>
>>                =20
>>       =20
>>
>>
>>Please note that it may take a couple of minutes from the time of=20
>>submission until the htmlized version and diff are available at=20
>>tools.ietf.org.
>>
>>The IETF Secretariat
>>
>


From repenno@cisco.com  Tue Nov  5 13:44:41 2013
Return-Path: <repenno@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D146621E8099 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 13:43:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sq4oANMzGxZw for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 13:43:46 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 3E53711E81DE for <pcp@ietf.org>; Tue,  5 Nov 2013 13:42:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=471; q=dns/txt; s=iport; t=1383687734; x=1384897334; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=jx4S5HTRM+gV69kWq/bemwfOkjZtRb+Hb/DKFnaDH7o=; b=m1hBrk6clB3DwDN7fw2+8n4ThE54rItXcTuJX3H3f9UeCNQbqEOTI+Io d28nIZTMcqRLIWspGim8v/i8TOC8X+tuqeLO491+IYljiXcL20XyLMIO+ FLZvz0c5JWlvouuPkbfwlc0pzEPfsSim9o8zI5wzLH0LjyMCIDDvdGWXU A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAAlleVKtJV2b/2dsb2JhbABZgweBC79GgSwWdIIsOj8SAQg2QiUBAQQBDQWIAb8Dj1kHhC8DmAqSCYMmgio
X-IronPort-AV: E=Sophos;i="4.93,641,1378857600"; d="scan'208";a="281146684"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-3.cisco.com with ESMTP; 05 Nov 2013 21:41:59 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rA5Lfx5A027199 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Nov 2013 21:41:59 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.192]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 15:41:58 -0600
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: Ac7ZXRwLNJWMJz/iQNuoFr8x9AR4gwA+/yMAAARoMYD//+R8gP//3LdAgAAnhwA=
Date: Tue, 5 Nov 2013 21:41:58 +0000
Message-ID: <CE9EA5C5.5752%repenno@cisco.com>
In-Reply-To: <F893BEC192403B489DBA38999068CF1905949370@ORSMSX102.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.86.108]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3E2022F69593794188DF6C6AE8FE88B5@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 21:44:55 -0000

Okay, let me see if I can get this:

If user moves from an environment from high to low lighting, do you
increase or decrease resolution? What if auto-brightness kicks in? Or not?

On 11/5/13 1:38 PM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com> wrote:

>[RP] Smartphones and tablets already have auto brightness. How much extra
>savings you can get?
>Hassnaa: Yes but when the device does the auto brightness this consumes a
>lot of its device resources.


From hassnaa.moustafa@intel.com  Tue Nov  5 14:59:33 2013
Return-Path: <hassnaa.moustafa@intel.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB90C21E80D1 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 14:59:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oGDLSfrJ+N7O for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 14:59:24 -0800 (PST)
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by ietfa.amsl.com (Postfix) with ESMTP id CB6BF21E80BD for <pcp@ietf.org>; Tue,  5 Nov 2013 14:59:23 -0800 (PST)
Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 05 Nov 2013 14:59:23 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.93,535,1378882800"; d="scan'208";a="404163949"
Received: from orsmsx107.amr.corp.intel.com ([10.22.240.5]) by orsmga001.jf.intel.com with ESMTP; 05 Nov 2013 14:59:21 -0800
Received: from orsmsx102.amr.corp.intel.com ([169.254.1.203]) by ORSMSX107.amr.corp.intel.com ([169.254.1.35]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 14:59:21 -0800
From: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: Ac7ZXRwLNJWMJz/iQNuoFr8x9AR4gwA+/yMAAARoMYD//+R8gP//3LdAgAAnhwD//8qOAA==
Date: Tue, 5 Nov 2013 22:59:20 +0000
Message-ID: <F893BEC192403B489DBA38999068CF1905949648@ORSMSX102.amr.corp.intel.com>
References: <F893BEC192403B489DBA38999068CF1905949370@ORSMSX102.amr.corp.intel.com> <CE9EA5C5.5752%repenno@cisco.com>
In-Reply-To: <CE9EA5C5.5752%repenno@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.22.254.138]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 22:59:33 -0000

The video encoding resolution here does not have a specific impact, since t=
he native screen resolution is what counts at the end. So the adaptation wo=
uld not be done regarding the resolution.
We mention specific examples (in the optimization examples in section 3.5 i=
n the draft that shows how the knowledge of the light level can help when i=
t is used by an external entity "end-server or other middle node" can be of=
 help than being done locally). Among the mentioned examples in Section 3.5=
, an example that can clarify the point in question is the following:=20
- If the user is in a bright/sunny environment and the battery level is not=
 high, content can be sent with higher brightness but with lower bitrate to=
 compensate the power consumed from content brightness. --> Here the bright=
ness settings can be done locally also however a bitrate adjustment can be =
done at the source as explained in the example to save battery.

And generally, modifying the pixel luminance of the video at the source bas=
ed on the lighting environment of the user is expected to improve the user =
quality and potentially reduce the network bandwidth.



-----Original Message-----
From: Reinaldo Penno (repenno) [mailto:repenno@cisco.com]=20
Sent: Tuesday, November 05, 2013 1:42 PM
To: Moustafa, Hassnaa; pcp@ietf.org
Cc: Dave Thaler; mohamed.boucadair@orange.com; Moses, Danny
Subject: Re: New Submission: draft-mou-pcp-application-network-feedback-00.=
txt

Okay, let me see if I can get this:

If user moves from an environment from high to low lighting, do you increas=
e or decrease resolution? What if auto-brightness kicks in? Or not?

On 11/5/13 1:38 PM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com> wrote:

>[RP] Smartphones and tablets already have auto brightness. How much=20
>extra savings you can get?
>Hassnaa: Yes but when the device does the auto brightness this consumes=20
>a lot of its device resources.


From versteb@cisco.com  Tue Nov  5 15:49:42 2013
Return-Path: <versteb@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3741721F8235 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 15:49:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v8ezs3T7D5Tt for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 15:49:37 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id A621A21E8131 for <pcp@ietf.org>; Tue,  5 Nov 2013 15:49:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=27730; q=dns/txt; s=iport; t=1383695373; x=1384904973; h=from:to:subject:date:message-id:mime-version; bh=w30mJwZBCfSW1agwILBM+NR3nqgtw8nUX80S09Ckmik=; b=DyR8Dmg9+z/Or7LZfKOkfV+b5yBBTEYOaIaqbVAQieMcv/WAuaCmM8lp JsR7Vnfe8tDsgl/gUBi3uOpllbZSHFKFd4pYoTF6IHfAD4Ia5jHa0eNa0 r6LBURxS/OnTyx6SFBCI3YZllKLNUbjGUNE1Inpa6yhEoI5rgrhfHrIjO Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As0JAHqDeVKtJV2b/2dsb2JhbABZgkNEOFOtHIloiEOBJhZtB4IlAQEBAwEtWAYBCBEEAQELFgc5FAkJAQQTCAGHcgYNnRmhSo8oPoMagQ8DmTmQWoMmgio
X-IronPort-AV: E=Sophos;i="4.93,642,1378857600";  d="scan'208,217";a="281125421"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-2.cisco.com with ESMTP; 05 Nov 2013 23:49:33 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rA5NnWFU017811 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <pcp@ietf.org>; Tue, 5 Nov 2013 23:49:32 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.196]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 17:49:32 -0600
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: RE: New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: Ac7agaDvGxDJgWj7TwOo0SUAuIXPuQ==
Date: Tue, 5 Nov 2013 23:49:32 +0000
Message-ID: <AE7F97DB5FEE054088D82E836BD15BE920134B70@xmb-aln-x05.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.97.111]
Content-Type: multipart/alternative; boundary="_000_AE7F97DB5FEE054088D82E836BD15BE920134B70xmbalnx05ciscoc_"
MIME-Version: 1.0
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 23:49:42 -0000

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

I have read this draft, and I have mixed emotions.



It is not clear (to me) if the intent is to use PCP to 1) actually invoke v=
ideo rate changes, or 2) use PCP signaling mechanisms to help the applicati=
on logic determine rate changes and to signal those rate changes to the net=
work.



IMHO- The former is not a good idea. The latter is an excellent idea, altho=
ugh I am not sure that all of the metadata described in this draft would be=
 useful.



I strongly encourage work in the area of exchanging metadata between the ho=
sts and the network edge. I am not sure that some of the video-specific met=
adata is useful (or appropriate) for consumption by the network. The bright=
ness, screen size, and the like is clearly useful to the client, and may ev=
en be useful for the server. However, I do not see how it is useful to the =
network.  Having said that,  I do like the idea of exchanging stuff like ne=
twork bandwidth/delay/loss/jitter/cost (aka network metadata) and applicati=
on flow priority/type/desired treatment (aka flow metadata).



I think that these points are worth spending some time on, and would like t=
o participate in that discussion.



Bill VerSteeg







>On 11/4/13 5:02 AM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com<mailto=
:hassnaa.moustafa@intel.com>>

>wrote:

>

>>Hi All,

>>

>>Draft (draft-mou-pcp-application-network-feedback) is a new draft that

>>is submitted today on (PCP Extension for Signaling Feedback

>>Information from the End-User Application to the Application Sever and to=
 the Network).

>>

>>The draft is available at :

>>http://www.ietf.org/internet-drafts/draft-mou-pcp-application-network-

>>fee

>>d

>>back-00.txt

>>

>>This draft addresses the need for more intelligence in the network and

>>service infrastructure for better content delivery to optimize the

>>network and devices resources. In this view, the draft proposes using

>>PCP to signal information for: i)  Knowledge in the network and

>>service platform about the available device and network conditions for

>>the end-user and ii) Knowledge in the network about the content

>>requirements in terms of devices and  network resources for content

>>stored either in the network or in the application server.

>>

>>The abstract of the draft is as follows:

>>" Abstract:    Nowadays users consumption style for video and multimedia

>>applications is strongly changing.  Users are heavily counting on

>>wireless and mobile devices for video streaming and interactive video

>>   and multimedia applications.  This can be implemented for instance

>>by having more intelligence in the service and the network

>>infrastructure to better suit a differentiated users consumption

>>style.  This can be achieved

>>   through having: (i) a knowledge in the network and service platform

>>about the available device and network conditions for the end-user and

>>(ii) a knowledge in the network about the content requirements in

>>terms of devices

>>   capabilities and network resources for content stored either in the

>>network or in the application server.  To obtain such knowledge with

>>no need for  changing the current infrastructure and in a generalized

>>way to all

>>   applications, feedback/notification mechanisms between the end-user

>>application, the network and the service platform is needed to provide

>>information helping the content delivery and adaptation decisions.

>>This document

>>    is investigating such application-agnostic track.

>>

>>   This document extends the Port Control Protocol (PCP) RFC 6887

>>[RFC6887] to allow: (i) the users application to notify the network

>>and application server about its available resources in terms of

>>   devices capabilities and network conditions as well as information

>>about the user (e.g., location, mobility status) and (ii) the

>>application server to notify the network about the requirements of

>>   the content it stores in terms of devices and network resources.  A

>>new PCP option, denoted the FEEDBACK, is specified to allow such

>>feedback notification signaling.  This option is used with both PEER

>>   and MAP Opcodes."

>>

>>Looking forward to having your feedback and more discussion on this

>>draft.

>>

>>Regards,

>>Hassnaa

>>

>>

>>

>>-----Original Message-----

>>From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:i=
nternet-drafts@ietf.org]

>>Sent: Monday, November 04, 2013 4:06 AM

>>To: Mohamed Boucadair; Moustafa, Hassnaa; Moses, Danny

>>Subject: New Version Notification for

>>draft-mou-pcp-application-network-feedback-00.txt

>>

>>

>>A new version of I-D,

>>draft-mou-pcp-application-network-feedback-00.txt

>>has been successfully submitted by Hassnaa Moustafa and posted to the

>>IETF repository.

>>

>>Filename:       draft-mou-pcp-application-network-feedback

>>Revision:        00

>>Title:                 PCP Extension for Signaling Feedback Information f=
rom the

>>End-User Application to the Application Sever and to the Network

>>Creation date:              2013-11-04

>>Group:                             Individual Submission

>>Number of pages: 14

>>URL:

>>http://www.ietf.org/internet-drafts/draft-mou-pcp-application-network-

>>fee

>>d

>>back-00.txt

>>Status:

>>http://datatracker.ietf.org/doc/draft-mou-pcp-application-network-feed

>>bac

>>k

>>Htmlized:

>>http://tools.ietf.org/html/draft-mou-pcp-application-network-feedback-

>>00

>>

>>

>>Abstract:

>>   Nowadays users consumption style for video and multimedia

>>   applications is strongly changing.  Users are heavily counting on

>>   wireless and mobile devices for video streaming and interactive video

>>   and multimedia applications.  This can be implemented for instance by

>>   having more intelligence in the service and the network

>>   infrastructure to better suit a differentiated users consumption

>>   style.  This can be achieved through having: (i) a knowledge in the

>>   network and service platform about the available device and network

>>   conditions for the end-user and (ii) a knowledge in the network about

>>   the content requirements in terms of devices capabilities and network

>>   resources for content stored either in the network or in the

>>   application server.  To obtain such knowledge with no need for

>>   changing the current infrastructure and in a generalized way to all

>>   applications, feedback/notification mechanisms between the end-user

>>   application, the network and the service platform is needed to

>>   provide information helping the content delivery and adaptation

>>   decisions.  This document is investigating such application-agnostic

>>   track.

>>

>>   This document extends the Port Control Protocol (PCP) RFC 6887

>>   [RFC6887] to allow: (i) the users application to notify the network

>>   and application server about its available resources in terms of

>>   devices capabilities and network conditions as well as information

>>   about the user (e.g., location, mobility status) and (ii) the

>>   application server to notify the network about the requirements of

>>   the content it stores in terms of devices and network resources.  A

>>   new PCP option, denoted the FEEDBACK, is specified to allow such

>>   feedback notification signaling.  This option is used with both PEER

>>   and MAP Opcodes.

>>

>>

>>

>>

>>

>>Please note that it may take a couple of minutes from the time of

>>submission until the htmlized version and diff are available at

>>tools.ietf.org.

>>

>>The IETF Secretariat

>>

>


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I have read this draft, and I have mixed emotions=
.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">It is not clear (to me) if the intent is to use P=
CP to 1) actually invoke video rate changes, or 2) use PCP signaling mechan=
isms to help the application logic determine rate changes and to signal tho=
se rate changes to the network.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">IMHO- The former is not a good idea. The latter i=
s an excellent idea, although I am not sure that all of the metadata descri=
bed in this draft would be useful.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I strongly encourage work in the area of exchangi=
ng metadata between the hosts and the network edge. I am not sure that some=
 of the video-specific metadata is useful (or appropriate) for consumption =
by the network. The brightness, screen
 size, and the like is clearly useful to the client, and may even be useful=
 for the server. However, I do not see how it is useful to the network.&nbs=
p; Having said that, &nbsp;I do like the idea of exchanging stuff like netw=
ork bandwidth/delay/loss/jitter/cost (aka
 network metadata) and application flow priority/type/desired treatment (ak=
a flow metadata).<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I think that these points are worth spending some=
 time on, and would like to participate in that discussion.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Bill VerSteeg<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;On 11/4/13 5:02 AM, &quot;Moustafa, Hassnaa&q=
uot; &lt;<a href=3D"mailto:hassnaa.moustafa@intel.com">hassnaa.moustafa@int=
el.com</a>&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;wrote:<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Hi All,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Draft (draft-mou-pcp-application-network-=
feedback) is a new draft that
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;is submitted today on (PCP Extension for =
Signaling Feedback
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Information from the End-User Application=
 to the Application Sever and to the Network).<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;The draft is available at :<o:p></o:p></p=
>
<p class=3D"MsoPlainText">&gt;&gt;<a href=3D"http://www.ietf.org/internet-d=
rafts/draft-mou-pcp-application-network-">http://www.ietf.org/internet-draf=
ts/draft-mou-pcp-application-network-</a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;fee<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;d<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;back-00.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;This draft addresses the need for more in=
telligence in the network and
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;service infrastructure for better content=
 delivery to optimize the
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;network and devices resources. In this vi=
ew, the draft proposes using
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;PCP to signal information for: i)&nbsp; K=
nowledge in the network and
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;service platform about the available devi=
ce and network conditions for
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;the end-user and ii) Knowledge in the net=
work about the content
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;requirements in terms of devices and&nbsp=
; network resources for content
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;stored either in the network or in the ap=
plication server.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;The abstract of the draft is as follows:<=
o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&quot; Abstract:&nbsp;&nbsp;&nbsp; Nowada=
ys users consumption style for video and multimedia<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;applications is strongly changing.&nbsp; =
Users are heavily counting on
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;wireless and mobile devices for video str=
eaming and interactive video<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and multimedia applications.=
&nbsp; This can be implemented for instance
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;by having more intelligence in the servic=
e and the network
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;infrastructure to better suit a different=
iated users consumption
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;style.&nbsp; This can be achieved<o:p></o=
:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; through having: (i) a knowle=
dge in the network and service platform
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;about the available device and network co=
nditions for the end-user and<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;(ii) a knowledge in the network about the=
 content requirements in
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;terms of devices<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; capabilities and network res=
ources for content stored either in the
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;network or in the application server.&nbs=
p; To obtain such knowledge with
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;no need for&nbsp; changing the current in=
frastructure and in a generalized
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;way to all<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; applications, feedback/notif=
ication mechanisms between the end-user
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;application, the network and the service =
platform is needed to provide
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;information helping the content delivery =
and adaptation decisions.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;This document<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp; is investigating such =
application-agnostic track.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; This document extends the Po=
rt Control Protocol (PCP) RFC 6887
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;[RFC6887] to allow: (i) the users applica=
tion to notify the network
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;and application server about its availabl=
e resources in terms of<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; devices capabilities and net=
work conditions as well as information
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;about the user (e.g., location, mobility =
status) and (ii) the
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;application server to notify the network =
about the requirements of<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; the content it stores in ter=
ms of devices and network resources.&nbsp; A
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;new PCP option, denoted the FEEDBACK, is =
specified to allow such
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;feedback notification signaling.&nbsp; Th=
is option is used with both PEER<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and MAP Opcodes.&quot;<o:p><=
/o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Looking forward to having your feedback a=
nd more discussion on this
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;draft.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Regards,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Hassnaa<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;-----Original Message-----<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;From: <a href=3D"mailto:internet-drafts@i=
etf.org">internet-drafts@ietf.org</a> [<a href=3D"mailto:internet-drafts@ie=
tf.org">mailto:internet-drafts@ietf.org</a>]<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Sent: Monday, November 04, 2013 4:06 AM<o=
:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;To: Mohamed Boucadair; Moustafa, Hassnaa;=
 Moses, Danny<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Subject: New Version Notification for<o:p=
></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;draft-mou-pcp-application-network-feedbac=
k-00.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;A new version of I-D,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;draft-mou-pcp-application-network-feedbac=
k-00.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;has been successfully submitted by Hassna=
a Moustafa and posted to the
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;IETF repository.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Filename:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; draft-mou-pcp-application-network-feedback<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Revision:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; 00<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Title:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PCP Extension=
 for Signaling Feedback Information from the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;End-User Application to the Application S=
ever and to the Network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Creation date:&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-11-04<o:p></o:p></=
p>
<p class=3D"MsoPlainText">&gt;&gt;Group:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Individual Submi=
ssion<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Number of pages: 14<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;URL:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<a href=3D"http://www.ietf.org/internet-d=
rafts/draft-mou-pcp-application-network-">http://www.ietf.org/internet-draf=
ts/draft-mou-pcp-application-network-</a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;fee<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;d<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;back-00.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Status:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<a href=3D"http://datatracker.ietf.org/do=
c/draft-mou-pcp-application-network-feed">http://datatracker.ietf.org/doc/d=
raft-mou-pcp-application-network-feed</a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;bac<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;k<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Htmlized:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<a href=3D"http://tools.ietf.org/html/dra=
ft-mou-pcp-application-network-feedback-">http://tools.ietf.org/html/draft-=
mou-pcp-application-network-feedback-</a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;00<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Abstract:<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; Nowadays users consumption s=
tyle for video and multimedia<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; applications is strongly cha=
nging.&nbsp; Users are heavily counting on<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; wireless and mobile devices =
for video streaming and interactive video<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and multimedia applications.=
&nbsp; This can be implemented for instance by<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; having more intelligence in =
the service and the network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; infrastructure to better sui=
t a differentiated users consumption<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; style.&nbsp; This can be ach=
ieved through having: (i) a knowledge in the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; network and service platform=
 about the available device and network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; conditions for the end-user =
and (ii) a knowledge in the network about<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; the content requirements in =
terms of devices capabilities and network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; resources for content stored=
 either in the network or in the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; application server.&nbsp; To=
 obtain such knowledge with no need for<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; changing the current infrast=
ructure and in a generalized way to all<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; applications, feedback/notif=
ication mechanisms between the end-user<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; application, the network and=
 the service platform is needed to<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; provide information helping =
the content delivery and adaptation<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; decisions.&nbsp; This docume=
nt is investigating such application-agnostic<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; track.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; This document extends the Po=
rt Control Protocol (PCP) RFC 6887<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; [RFC6887] to allow: (i) the =
users application to notify the network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and application server about=
 its available resources in terms of<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; devices capabilities and net=
work conditions as well as information<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; about the user (e.g., locati=
on, mobility status) and (ii) the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp; &nbsp;application server to notify=
 the network about the requirements of<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; the content it stores in ter=
ms of devices and network resources.&nbsp; A<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; new PCP option, denoted the =
FEEDBACK, is specified to allow such<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; feedback notification signal=
ing.&nbsp; This option is used with both PEER<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and MAP Opcodes.<o:p></o:p><=
/p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Please note that it may take a couple of =
minutes from the time of
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;submission until the htmlized version and=
 diff are available at
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;tools.ietf.org.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;The IETF Secretariat<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_AE7F97DB5FEE054088D82E836BD15BE920134B70xmbalnx05ciscoc_--

From repenno@cisco.com  Tue Nov  5 16:01:38 2013
Return-Path: <repenno@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5842B11E811A for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 16:01:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZNeshRkCURab for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 16:01:33 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 07F0D21F9477 for <pcp@ietf.org>; Tue,  5 Nov 2013 16:01:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=29919; q=dns/txt; s=iport; t=1383696093; x=1384905693; h=from:to:subject:date:message-id:in-reply-to:mime-version; bh=EEqzSi7cKdv3CRfHdRmP8yFyjs9GPFwfkEA6O5+jW7Q=; b=jX/P3a2QpnDzVD3kGKWmKCHtjt1cMkOAZ6Xv85BCKgD8O9ELa1v5HjZo BljL0kyBF6sjdxWUzzoflugkAYkitO/QWbqOtv4TOBefCw9DOuhTlHpcW K5yNjtid4V2+il/M4VFudxRHC2KU3mUjs0WbOMzMxkz5/R1QIoeCU4lEQ Y=;
X-Files: ATT00001.txt : 124
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As8JABaGeVKtJV2Y/2dsb2JhbABZgkNEOFOtHIloiEOBJhZtB4IlAQEBAwEBAQEqQRcGAQgRAwEBASEHCSULFAcBAQUDAQEEEwkFh20GDZ0boUWPSBgGhCkDkC6BMIYsgS+QWoMmgio
X-IronPort-AV: E=Sophos;i="4.93,642,1378857600";  d="txt'?scan'208,217";a="280971023"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP; 06 Nov 2013 00:01:32 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rA601WAu031530 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <pcp@ietf.org>; Wed, 6 Nov 2013 00:01:32 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.192]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 18:01:32 -0600
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: Ac7agaDvGxDJgWj7TwOo0SUAuIXPuf//4eaA
Date: Wed, 6 Nov 2013 00:01:30 +0000
Message-ID: <CE9EC6A3.578B%repenno@cisco.com>
In-Reply-To: <AE7F97DB5FEE054088D82E836BD15BE920134B70@xmb-aln-x05.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.86.108]
Content-Type: multipart/mixed; boundary="_004_CE9EC6A3578Brepennociscocom_"
MIME-Version: 1.0
Subject: [pcp] FW: New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2013 00:01:38 -0000

--_004_CE9EC6A3578Brepennociscocom_
Content-Type: multipart/alternative;
	boundary="_000_CE9EC6A3578Brepennociscocom_"

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

On behalf of Bill

From: "Bill Ver Steeg (versteb)" <versteb@cisco.com<mailto:versteb@cisco.co=
m>>
Date: Tuesday, November 5, 2013 3:49 PM
To: "pcp@ietf.org<mailto:pcp@ietf.org>" <pcp@ietf.org<mailto:pcp@ietf.org>>
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt


I have read this draft, and I have mixed emotions.



It is not clear (to me) if the intent is to use PCP to 1) actually invoke v=
ideo rate changes, or 2) use PCP signaling mechanisms to help the applicati=
on logic determine rate changes and to signal those rate changes to the net=
work.



IMHO- The former is not a good idea. The latter is an excellent idea, altho=
ugh I am not sure that all of the metadata described in this draft would be=
 useful.



I strongly encourage work in the area of exchanging metadata between the ho=
sts and the network edge. I am not sure that some of the video-specific met=
adata is useful (or appropriate) for consumption by the network. The bright=
ness, screen size, and the like is clearly useful to the client, and may ev=
en be useful for the server. However, I do not see how it is useful to the =
network.  Having said that,  I do like the idea of exchanging stuff like ne=
twork bandwidth/delay/loss/jitter/cost (aka network metadata) and applicati=
on flow priority/type/desired treatment (aka flow metadata).



I think that these points are worth spending some time on, and would like t=
o participate in that discussion.



Bill VerSteeg







>On 11/4/13 5:02 AM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com<mailto=
:hassnaa.moustafa@intel.com>>

>wrote:

>

>>Hi All,

>>

>>Draft (draft-mou-pcp-application-network-feedback) is a new draft that

>>is submitted today on (PCP Extension for Signaling Feedback

>>Information from the End-User Application to the Application Sever and to=
 the Network).

>>

>>The draft is available at :

>>http://www.ietf.org/internet-drafts/draft-mou-pcp-application-network-

>>fee

>>d

>>back-00.txt

>>

>>This draft addresses the need for more intelligence in the network and

>>service infrastructure for better content delivery to optimize the

>>network and devices resources. In this view, the draft proposes using

>>PCP to signal information for: i)  Knowledge in the network and

>>service platform about the available device and network conditions for

>>the end-user and ii) Knowledge in the network about the content

>>requirements in terms of devices and  network resources for content

>>stored either in the network or in the application server.

>>

>>The abstract of the draft is as follows:

>>" Abstract:    Nowadays users consumption style for video and multimedia

>>applications is strongly changing.  Users are heavily counting on

>>wireless and mobile devices for video streaming and interactive video

>>   and multimedia applications.  This can be implemented for instance

>>by having more intelligence in the service and the network

>>infrastructure to better suit a differentiated users consumption

>>style.  This can be achieved

>>   through having: (i) a knowledge in the network and service platform

>>about the available device and network conditions for the end-user and

>>(ii) a knowledge in the network about the content requirements in

>>terms of devices

>>   capabilities and network resources for content stored either in the

>>network or in the application server.  To obtain such knowledge with

>>no need for  changing the current infrastructure and in a generalized

>>way to all

>>   applications, feedback/notification mechanisms between the end-user

>>application, the network and the service platform is needed to provide

>>information helping the content delivery and adaptation decisions.

>>This document

>>    is investigating such application-agnostic track.

>>

>>   This document extends the Port Control Protocol (PCP) RFC 6887

>>[RFC6887] to allow: (i) the users application to notify the network

>>and application server about its available resources in terms of

>>   devices capabilities and network conditions as well as information

>>about the user (e.g., location, mobility status) and (ii) the

>>application server to notify the network about the requirements of

>>   the content it stores in terms of devices and network resources.  A

>>new PCP option, denoted the FEEDBACK, is specified to allow such

>>feedback notification signaling.  This option is used with both PEER

>>   and MAP Opcodes."

>>

>>Looking forward to having your feedback and more discussion on this

>>draft.

>>

>>Regards,

>>Hassnaa

>>

>>

>>

>>-----Original Message-----

>>From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:i=
nternet-drafts@ietf.org]

>>Sent: Monday, November 04, 2013 4:06 AM

>>To: Mohamed Boucadair; Moustafa, Hassnaa; Moses, Danny

>>Subject: New Version Notification for

>>draft-mou-pcp-application-network-feedback-00.txt

>>

>>

>>A new version of I-D,

>>draft-mou-pcp-application-network-feedback-00.txt

>>has been successfully submitted by Hassnaa Moustafa and posted to the

>>IETF repository.

>>

>>Filename:       draft-mou-pcp-application-network-feedback

>>Revision:        00

>>Title:                 PCP Extension for Signaling Feedback Information f=
rom the

>>End-User Application to the Application Sever and to the Network

>>Creation date:              2013-11-04

>>Group:                             Individual Submission

>>Number of pages: 14

>>URL:

>>http://www.ietf.org/internet-drafts/draft-mou-pcp-application-network-

>>fee

>>d

>>back-00.txt

>>Status:

>>http://datatracker.ietf.org/doc/draft-mou-pcp-application-network-feed

>>bac

>>k

>>Htmlized:

>>http://tools.ietf.org/html/draft-mou-pcp-application-network-feedback-

>>00

>>

>>

>>Abstract:

>>   Nowadays users consumption style for video and multimedia

>>   applications is strongly changing.  Users are heavily counting on

>>   wireless and mobile devices for video streaming and interactive video

>>   and multimedia applications.  This can be implemented for instance by

>>   having more intelligence in the service and the network

>>   infrastructure to better suit a differentiated users consumption

>>   style.  This can be achieved through having: (i) a knowledge in the

>>   network and service platform about the available device and network

>>   conditions for the end-user and (ii) a knowledge in the network about

>>   the content requirements in terms of devices capabilities and network

>>   resources for content stored either in the network or in the

>>   application server.  To obtain such knowledge with no need for

>>   changing the current infrastructure and in a generalized way to all

>>   applications, feedback/notification mechanisms between the end-user

>>   application, the network and the service platform is needed to

>>   provide information helping the content delivery and adaptation

>>   decisions.  This document is investigating such application-agnostic

>>   track.

>>

>>   This document extends the Port Control Protocol (PCP) RFC 6887

>>   [RFC6887] to allow: (i) the users application to notify the network

>>   and application server about its available resources in terms of

>>   devices capabilities and network conditions as well as information

>>   about the user (e.g., location, mobility status) and (ii) the

>>   application server to notify the network about the requirements of

>>   the content it stores in terms of devices and network resources.  A

>>   new PCP option, denoted the FEEDBACK, is specified to allow such

>>   feedback notification signaling.  This option is used with both PEER

>>   and MAP Opcodes.

>>

>>

>>

>>

>>

>>Please note that it may take a couple of minutes from the time of

>>submission until the htmlized version and diff are available at

>>tools.ietf.org.

>>

>>The IETF Secretariat

>>

>


--_000_CE9EC6A3578Brepennociscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <BEEEE75F82848644A167427C17241B6F@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>On behalf of Bill</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&quot;Bill Ver Steeg (versteb=
)&quot; &lt;<a href=3D"mailto:versteb@cisco.com">versteb@cisco.com</a>&gt;<=
br>
<span style=3D"font-weight:bold">Date: </span>Tuesday, November 5, 2013 3:4=
9 PM<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:pcp@iet=
f.org">pcp@ietf.org</a>&quot; &lt;<a href=3D"mailto:pcp@ietf.org">pcp@ietf.=
org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [pcp] New Submission: =
draft-mou-pcp-application-network-feedback-00.txt<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I have read this draft, and I have mixed emotions=
.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">It is not clear (to me) if the intent is to use P=
CP to 1) actually invoke video rate changes, or 2) use PCP signaling mechan=
isms to help the application logic determine rate changes and to signal tho=
se rate changes to the network.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">IMHO- The former is not a good idea. The latter i=
s an excellent idea, although I am not sure that all of the metadata descri=
bed in this draft would be useful.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I strongly encourage work in the area of exchangi=
ng metadata between the hosts and the network edge. I am not sure that some=
 of the video-specific metadata is useful (or appropriate) for consumption =
by the network. The brightness, screen
 size, and the like is clearly useful to the client, and may even be useful=
 for the server. However, I do not see how it is useful to the network.&nbs=
p; Having said that, &nbsp;I do like the idea of exchanging stuff like netw=
ork bandwidth/delay/loss/jitter/cost (aka
 network metadata) and application flow priority/type/desired treatment (ak=
a flow metadata).<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I think that these points are worth spending some=
 time on, and would like to participate in that discussion.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Bill VerSteeg<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;On 11/4/13 5:02 AM, &quot;Moustafa, Hassnaa&q=
uot; &lt;<a href=3D"mailto:hassnaa.moustafa@intel.com">hassnaa.moustafa@int=
el.com</a>&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;wrote:<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Hi All,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Draft (draft-mou-pcp-application-network-=
feedback) is a new draft that
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;is submitted today on (PCP Extension for =
Signaling Feedback
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Information from the End-User Application=
 to the Application Sever and to the Network).<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;The draft is available at :<o:p></o:p></p=
>
<p class=3D"MsoPlainText">&gt;&gt;<a href=3D"http://www.ietf.org/internet-d=
rafts/draft-mou-pcp-application-network-">http://www.ietf.org/internet-draf=
ts/draft-mou-pcp-application-network-</a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;fee<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;d<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;back-00.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;This draft addresses the need for more in=
telligence in the network and
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;service infrastructure for better content=
 delivery to optimize the
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;network and devices resources. In this vi=
ew, the draft proposes using
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;PCP to signal information for: i)&nbsp; K=
nowledge in the network and
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;service platform about the available devi=
ce and network conditions for
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;the end-user and ii) Knowledge in the net=
work about the content
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;requirements in terms of devices and&nbsp=
; network resources for content
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;stored either in the network or in the ap=
plication server.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;The abstract of the draft is as follows:<=
o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&quot; Abstract:&nbsp;&nbsp;&nbsp; Nowada=
ys users consumption style for video and multimedia<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;applications is strongly changing.&nbsp; =
Users are heavily counting on
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;wireless and mobile devices for video str=
eaming and interactive video<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and multimedia applications.=
&nbsp; This can be implemented for instance
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;by having more intelligence in the servic=
e and the network
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;infrastructure to better suit a different=
iated users consumption
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;style.&nbsp; This can be achieved<o:p></o=
:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; through having: (i) a knowle=
dge in the network and service platform
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;about the available device and network co=
nditions for the end-user and<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;(ii) a knowledge in the network about the=
 content requirements in
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;terms of devices<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; capabilities and network res=
ources for content stored either in the
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;network or in the application server.&nbs=
p; To obtain such knowledge with
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;no need for&nbsp; changing the current in=
frastructure and in a generalized
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;way to all<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; applications, feedback/notif=
ication mechanisms between the end-user
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;application, the network and the service =
platform is needed to provide
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;information helping the content delivery =
and adaptation decisions.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;This document<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp; is investigating such =
application-agnostic track.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; This document extends the Po=
rt Control Protocol (PCP) RFC 6887
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;[RFC6887] to allow: (i) the users applica=
tion to notify the network
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;and application server about its availabl=
e resources in terms of<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; devices capabilities and net=
work conditions as well as information
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;about the user (e.g., location, mobility =
status) and (ii) the
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;application server to notify the network =
about the requirements of<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; the content it stores in ter=
ms of devices and network resources.&nbsp; A
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;new PCP option, denoted the FEEDBACK, is =
specified to allow such
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;feedback notification signaling.&nbsp; Th=
is option is used with both PEER<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and MAP Opcodes.&quot;<o:p><=
/o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Looking forward to having your feedback a=
nd more discussion on this
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;draft.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Regards,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Hassnaa<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;-----Original Message-----<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;From: <a href=3D"mailto:internet-drafts@i=
etf.org">internet-drafts@ietf.org</a> [<a href=3D"mailto:internet-drafts@ie=
tf.org">mailto:internet-drafts@ietf.org</a>]<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Sent: Monday, November 04, 2013 4:06 AM<o=
:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;To: Mohamed Boucadair; Moustafa, Hassnaa;=
 Moses, Danny<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Subject: New Version Notification for<o:p=
></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;draft-mou-pcp-application-network-feedbac=
k-00.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;A new version of I-D,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;draft-mou-pcp-application-network-feedbac=
k-00.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;has been successfully submitted by Hassna=
a Moustafa and posted to the
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;IETF repository.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Filename:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; draft-mou-pcp-application-network-feedback<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Revision:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; 00<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Title:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PCP Extension=
 for Signaling Feedback Information from the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;End-User Application to the Application S=
ever and to the Network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Creation date:&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-11-04<o:p></o:p></=
p>
<p class=3D"MsoPlainText">&gt;&gt;Group:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Individual Submi=
ssion<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Number of pages: 14<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;URL:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<a href=3D"http://www.ietf.org/internet-d=
rafts/draft-mou-pcp-application-network-">http://www.ietf.org/internet-draf=
ts/draft-mou-pcp-application-network-</a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;fee<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;d<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;back-00.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Status:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<a href=3D"http://datatracker.ietf.org/do=
c/draft-mou-pcp-application-network-feed">http://datatracker.ietf.org/doc/d=
raft-mou-pcp-application-network-feed</a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;bac<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;k<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Htmlized:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<a href=3D"http://tools.ietf.org/html/dra=
ft-mou-pcp-application-network-feedback-">http://tools.ietf.org/html/draft-=
mou-pcp-application-network-feedback-</a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;00<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Abstract:<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; Nowadays users consumption s=
tyle for video and multimedia<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; applications is strongly cha=
nging.&nbsp; Users are heavily counting on<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; wireless and mobile devices =
for video streaming and interactive video<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and multimedia applications.=
&nbsp; This can be implemented for instance by<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; having more intelligence in =
the service and the network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; infrastructure to better sui=
t a differentiated users consumption<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; style.&nbsp; This can be ach=
ieved through having: (i) a knowledge in the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; network and service platform=
 about the available device and network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; conditions for the end-user =
and (ii) a knowledge in the network about<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; the content requirements in =
terms of devices capabilities and network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; resources for content stored=
 either in the network or in the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; application server.&nbsp; To=
 obtain such knowledge with no need for<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; changing the current infrast=
ructure and in a generalized way to all<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; applications, feedback/notif=
ication mechanisms between the end-user<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; application, the network and=
 the service platform is needed to<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; provide information helping =
the content delivery and adaptation<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; decisions.&nbsp; This docume=
nt is investigating such application-agnostic<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; track.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; This document extends the Po=
rt Control Protocol (PCP) RFC 6887<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; [RFC6887] to allow: (i) the =
users application to notify the network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and application server about=
 its available resources in terms of<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; devices capabilities and net=
work conditions as well as information<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; about the user (e.g., locati=
on, mobility status) and (ii) the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp; &nbsp;application server to notify=
 the network about the requirements of<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; the content it stores in ter=
ms of devices and network resources.&nbsp; A<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; new PCP option, denoted the =
FEEDBACK, is specified to allow such<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; feedback notification signal=
ing.&nbsp; This option is used with both PEER<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and MAP Opcodes.<o:p></o:p><=
/p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Please note that it may take a couple of =
minutes from the time of
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;submission until the htmlized version and=
 diff are available at
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;tools.ietf.org.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;The IETF Secretariat<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_CE9EC6A3578Brepennociscocom_--

--_004_CE9EC6A3578Brepennociscocom_
Content-Type: text/plain; name="ATT00001.txt"
Content-Description: ATT00001.txt
Content-Disposition: attachment; filename="ATT00001.txt"; size=124;
	creation-date="Wed, 06 Nov 2013 00:01:30 GMT";
	modification-date="Wed, 06 Nov 2013 00:01:30 GMT"
Content-ID: <CF3B5A0116A66C459C465F643DC80865@emea.cisco.com>
Content-Transfer-Encoding: base64

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnBjcCBtYWls
aW5nIGxpc3QNCnBjcEBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9wY3ANCg==

--_004_CE9EC6A3578Brepennociscocom_--

From sureshk@juniper.net  Tue Nov  5 16:57:30 2013
Return-Path: <sureshk@juniper.net>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B307F11E8199 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 16:57:30 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4dAHqK7iAU-1 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 16:57:25 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id 4477321F9E6D for <pcp@ietf.org>; Tue,  5 Nov 2013 16:57:25 -0800 (PST)
Received: from mail155-va3-R.bigfish.com (10.7.14.231) by VA3EHSOBE004.bigfish.com (10.7.40.24) with Microsoft SMTP Server id 14.1.225.22; Wed, 6 Nov 2013 00:57:23 +0000
Received: from mail155-va3 (localhost [127.0.0.1])	by mail155-va3-R.bigfish.com (Postfix) with ESMTP id 433F132026E; Wed,  6 Nov 2013 00:57:23 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -27
X-BigFish: VPS-27(z579ehzbb2dI98dI9371I936eI1432I4015I14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL17326ah8275bh8275dh1de097h186068hz2fh109h2a8h839h944hd25he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dfeh1dffh1fe8h1ff5h2052h20b3h2216h1155h)
Received-SPF: pass (mail155-va3: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=sureshk@juniper.net; helo=BL2PRD0510HT002.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(51704005)(24454002)(479174003)(377454003)(189002)(199002)(164054003)(53754006)(377424004)(19580395003)(49866001)(83322001)(19580405001)(47736001)(31966008)(74366001)(66066001)(80976001)(50986001)(47976001)(81342001)(74876001)(15202345003)(74706001)(36756003)(65816001)(63696002)(83716003)(80022001)(87266001)(33656001)(76796001)(74662001)(47446002)(81686001)(81542001)(81816001)(74502001)(56816003)(4396001)(69226001)(76786001)(51856001)(54316002)(54356001)(82746002)(85306002)(53806001)(59766001)(77982001)(46102001)(15975445006)(83072001)(79102001)(56776001)(76482001)(2656002); DIR:OUT; SFP:; SCL:1; SRVR:DM2PR05MB286; H:DM2PR05MB288.namprd05.prod.outlook.com; CLIP:50.136.207.230; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail155-va3 (localhost.localdomain [127.0.0.1]) by mail155-va3 (MessageSwitch) id 13836994422641_19832; Wed,  6 Nov 2013 00:57:22 +0000 (UTC)
Received: from VA3EHSMHS040.bigfish.com (unknown [10.7.14.246])	by mail155-va3.bigfish.com (Postfix) with ESMTP id F08A4440040; Wed,  6 Nov 2013 00:57:21 +0000 (UTC)
Received: from BL2PRD0510HT002.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS040.bigfish.com (10.7.99.50) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 6 Nov 2013 00:57:21 +0000
Received: from DM2PR05MB286.namprd05.prod.outlook.com (10.141.101.12) by BL2PRD0510HT002.namprd05.prod.outlook.com (10.255.100.37) with Microsoft SMTP Server (TLS) id 14.16.371.2; Wed, 6 Nov 2013 00:57:21 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com (10.141.101.11) by DM2PR05MB286.namprd05.prod.outlook.com (10.141.101.12) with Microsoft SMTP Server (TLS) id 15.0.800.7; Wed, 6 Nov 2013 00:57:19 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) by DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) with mapi id 15.00.0800.005; Wed, 6 Nov 2013 00:57:18 +0000
From: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>
Thread-Topic: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHO2lmbQ60NWXm7bU68b/cwqgHqfJoXDt2AgABSuFM=
Date: Wed, 6 Nov 2013 00:57:18 +0000
Message-ID: <EF4F90FF-9199-4527-AB7B-D3F9B81A52BE@juniper.net>
References: <CE9E7D38.26B47%sureshk@juniper.net>, <CE9E8C97.56CA%repenno@cisco.com>
In-Reply-To: <CE9E8C97.56CA%repenno@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.136.207.230]
x-forefront-prvs: 0022134A87
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2013 00:57:30 -0000

Reinaldo,

Thanks for your comments. Please see inline.=20

Suresh

> On Nov 5, 2013, at 12:01 PM, "Reinaldo Penno (repenno)" <repenno@cisco.co=
m> wrote:
>=20
> Interesting extension, a few comments:
>=20
> - You mention *flow* checkpointing but a many flows can match a MAP
> mapping. So, should a device checkpoint all flows matching a MAP mapping
> or only the mapping itself?
Good question. We can checkpoint all flows associated with that mapping. I =
am just thinking on applicability, where mapping is check pointed but all f=
lows need not be check pointed. For example, a free subscription (don't che=
ckpoint) but a paid subscription (checkpoint) of a service (exposed through=
 same mapping)?=20
We will get this addressed in the next version.=20

> - Do you need a new error code when checkpointing can not be honored or
> can you refuse an existing one? I prefer the latter, but irrespective,
> draft need those details.
Sure, will be addressed in next version.=20
> - This should be a long lifetime error since if, for example, PCP Server
> does not support checkpointing, you do not want client to keep requesting
> HA constantly.
Agreed
> - It would be good if this mechanism is totally decoupled from NAT so, fo=
r
> example, it could be used for FLOWDATA extension. It seems that way, but
> worth mentioning.
Yes it should work for other extensions, and even other applications, and t=
hat is the intention. Will be updated in the next revision.=20
>=20
> Thanks,
>=20
> Reinaldo
>=20
>=20
> On 11/5/13 11:02 AM, "Suresh Kumar Vinapamula Venkata"
> <sureshk@juniper.net> wrote:
>=20
>> Hi All,=20
>>=20
>> This draft talks about issues with checkpointing flows in current
>> deployment, and how they can be addressed and handled efficiently with
>> PCP.
>> Please review and share your comments.
>>=20
>> Thanks
>> Suresh
>>=20
>> On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
>> <sureshk@juniper.net> wrote:
>>=20
>>> Dear All,=20
>>>=20
>>> We submitted a new draft that sketches flow high availability through
>>> PCP.
>>> Please review.
>>>=20
>>> -Suresh
>>>=20
>>> On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
>>> <internet-drafts@ietf.org> wrote:
>>>=20
>>>>=20
>>>> A new version of I-D, draft-vinapamula-flow-ha-00.txt
>>>> has been successfully submitted by Suresh Vinapamula and posted to the
>>>> IETF repository.
>>>>=20
>>>> Filename:     draft-vinapamula-flow-ha
>>>> Revision:     00
>>>> Title:         Flow high availability through PCP
>>>> Creation date:     2013-10-14
>>>> Group:         Individual Submission
>>>> Number of pages: 5
>>>> URL:           =20
>>>> http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.txt
>>>> Status:        =20
>>>> http://datatracker.ietf.org/doc/draft-vinapamula-flow-ha
>>>> Htmlized:        http://tools.ietf.org/html/draft-vinapamula-flow-ha-0=
0
>>>>=20
>>>>=20
>>>> Abstract:
>>>> This document describes a mechanism for a host signal Network Address
>>>> Translator's (NAT) High Availability (HA) module to checkpoint
>>>> interested connections.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> Please note that it may take a couple of minutes from the time of
>>>> submission
>>>> until the htmlized version and diff are available at tools.ietf.org.
>>>>=20
>>>> The IETF Secretariat
>>=20
>>=20
>> _______________________________________________
>> pcp mailing list
>> pcp@ietf.org
>> https://www.ietf.org/mailman/listinfo/pcp
>=20
>=20
>=20


From tireddy@cisco.com  Tue Nov  5 19:58:24 2013
Return-Path: <tireddy@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C6CD11E81F7 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 19:58:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.524
X-Spam-Level: 
X-Spam-Status: No, score=-10.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pZy718H6taWq for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 19:58:19 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 2F7C311E81B0 for <pcp@ietf.org>; Tue,  5 Nov 2013 19:58:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9706; q=dns/txt; s=iport; t=1383710299; x=1384919899; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=3OpTVfG6MFEoy7Nxfw+UMeGq3wGhVIEWocpnJ/w1Oq8=; b=bayqY7oUPLCXZxVrxWbQ7groO+EdGupULxUUopaO3JKYSzAfk6BxbbDN 2RhV6Ty/dEr/S3iSqqI4qGr6aD8UQ7OeLKmgLdR8JTTkOt5nlSfOCZAa0 jZwNeR9yT42jjuZ80qCbctVo6XIbSMiwsoVKGlS5D31auqSEgGmkfCAdI o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmAFANW9eVKtJXG8/2dsb2JhbABZgwc4TQaDCLxEGIENFnSCJQEBAQQjEUUMBAIBCBEEAQEDAgYdAwICAjAUAQgIAgQBDQUIAYd4CAWsGZJDgSmMYYEeMQcGgmU1gQ8DmTmLJoU0gyaCKg
X-IronPort-AV: E=Sophos;i="4.93,643,1378857600"; d="scan'208";a="281181496"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-2.cisco.com with ESMTP; 06 Nov 2013 03:58:13 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id rA63wCkA011949 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 6 Nov 2013 03:58:12 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.47]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 21:58:12 -0600
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: AQHO2Zh1uTiiF1x+nUCuhfgqIOiaBpoXkJ+Q
Date: Wed, 6 Nov 2013 03:58:12 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A2425CF92@xmb-rcd-x10.cisco.com>
References: <F893BEC192403B489DBA38999068CF190594847F@ORSMSX102.amr.corp.intel.com>
In-Reply-To: <F893BEC192403B489DBA38999068CF190594847F@ORSMSX102.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.75.235.196]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission:	draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2013 03:58:24 -0000

SGksDQoNCk15IGluaXRpYWwgY29tbWVudHM6DQoNCjEpIElmIHRoZSBjbGllbnQgbGVhcm5zIHRo
YXQgdGhlIGJhdHRlcnkgY29uZGl0aW9ucywgbGlnaHQgbGV2ZWxzIGhhdmUgY2hhbmdlZCAtIA0K
YSkgd2h5IGNhbid0IHRoZSBjbGllbnQgcmVxdWVzdCBzdWJzZXF1ZW50IGNodW5rIHdpdGggZGlm
ZmVyZW50IGVuY29kaW5nIGZyb20gdGhlIFVSTCBpbiB0aGUgbWFuaWZlc3QgZmlsZSA/DQpiKSB3
aHkgY2FuJ3QgdGhlIGNsaWVudCBiZSBpbnRlbGxpZ2VudCBlbm91Z2ggdG8gcGljayB0aGUgc3Vi
c2VxdWVudCBjaHVuayB3aXRoIGFwcHJvcHJpYXRlIGJpdC1yYXRlIGJhc2VkIG9uIGVuZHBvaW50
IGRldmljZSBjb25kaXRpb25zID8NCg0KMikgdXNlIGNhc2UgaW4gc2VjdGlvbiAzLjIgb2YgdGhl
IGRyYWZ0OyB1Q0ROICh1cHN0cmVhbSBDRE4pIGJhc2VkIG9uIGxvY2F0aW9uIG9mIHRoZSBjbGll
bnQgYW5kIG90aGVyIHBhcmFtZXRlcnMgcXVlcmllcyBhdmFpbGFibGUgZENETiAoRG93bnN0cmVh
bSBDRE4pIHRvIHNlbGVjdHMgdGhlIGRDRE4gZm9yIHNlcnZpbmcgY29udGVudCB0byB0aGUgY2xp
ZW50LiANCg0KSG93IGlzIEZFRURCQUNLIG9wdGlvbiB1c2VmdWwgd2l0aCB1Q0ROL2RDRE4gPw0K
DQotVGlydS4NCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBNb3VzdGFm
YSwgSGFzc25hYSBbbWFpbHRvOmhhc3NuYWEubW91c3RhZmFAaW50ZWwuY29tXQ0KPiBTZW50OiBN
b25kYXksIE5vdmVtYmVyIDA0LCAyMDEzIDY6MzMgUE0NCj4gVG86IHBjcEBpZXRmLm9yZw0KPiBD
YzogTW9zZXMsIERhbm55DQo+IFN1YmplY3Q6IFtwY3BdIE5ldyBTdWJtaXNzaW9uOiBkcmFmdC1t
b3UtcGNwLWFwcGxpY2F0aW9uLW5ldHdvcmstZmVlZGJhY2stDQo+IDAwLnR4dA0KPiANCj4gSGkg
QWxsLA0KPiANCj4gRHJhZnQgKGRyYWZ0LW1vdS1wY3AtYXBwbGljYXRpb24tbmV0d29yay1mZWVk
YmFjaykgaXMgYSBuZXcgZHJhZnQgdGhhdCBpcw0KPiBzdWJtaXR0ZWQgdG9kYXkgb24gKFBDUCBF
eHRlbnNpb24gZm9yIFNpZ25hbGluZyBGZWVkYmFjayBJbmZvcm1hdGlvbiBmcm9tIHRoZQ0KPiBF
bmQtVXNlciBBcHBsaWNhdGlvbiB0byB0aGUgQXBwbGljYXRpb24gU2V2ZXIgYW5kIHRvIHRoZSBO
ZXR3b3JrKS4NCj4gDQo+IFRoZSBkcmFmdCBpcyBhdmFpbGFibGUgYXQgOiAgICAgICAgICAgICBo
dHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LQ0KPiBkcmFmdHMvZHJhZnQtbW91LXBjcC1hcHBs
aWNhdGlvbi1uZXR3b3JrLWZlZWRiYWNrLTAwLnR4dA0KPiANCj4gVGhpcyBkcmFmdCBhZGRyZXNz
ZXMgdGhlIG5lZWQgZm9yIG1vcmUgaW50ZWxsaWdlbmNlIGluIHRoZSBuZXR3b3JrIGFuZCBzZXJ2
aWNlDQo+IGluZnJhc3RydWN0dXJlIGZvciBiZXR0ZXIgY29udGVudCBkZWxpdmVyeSB0byBvcHRp
bWl6ZSB0aGUgbmV0d29yayBhbmQgZGV2aWNlcw0KPiByZXNvdXJjZXMuIEluIHRoaXMgdmlldywg
dGhlIGRyYWZ0IHByb3Bvc2VzIHVzaW5nIFBDUCB0byBzaWduYWwgaW5mb3JtYXRpb24NCj4gZm9y
OiBpKSAgS25vd2xlZGdlIGluIHRoZSBuZXR3b3JrIGFuZCBzZXJ2aWNlIHBsYXRmb3JtIGFib3V0
IHRoZSBhdmFpbGFibGUNCj4gZGV2aWNlIGFuZCBuZXR3b3JrIGNvbmRpdGlvbnMgZm9yIHRoZSBl
bmQtdXNlciBhbmQgaWkpIEtub3dsZWRnZSBpbiB0aGUNCj4gbmV0d29yayBhYm91dCB0aGUgY29u
dGVudCByZXF1aXJlbWVudHMgaW4gdGVybXMgb2YgZGV2aWNlcyBhbmQgIG5ldHdvcmsNCj4gcmVz
b3VyY2VzIGZvciBjb250ZW50IHN0b3JlZCBlaXRoZXIgaW4gdGhlIG5ldHdvcmsgb3IgaW4gdGhl
IGFwcGxpY2F0aW9uDQo+IHNlcnZlci4NCj4gDQo+IFRoZSBhYnN0cmFjdCBvZiB0aGUgZHJhZnQg
aXMgYXMgZm9sbG93czoNCj4gIiBBYnN0cmFjdDogICAgTm93YWRheXMgdXNlcnMgY29uc3VtcHRp
b24gc3R5bGUgZm9yIHZpZGVvIGFuZCBtdWx0aW1lZGlhDQo+IGFwcGxpY2F0aW9ucyBpcyBzdHJv
bmdseSBjaGFuZ2luZy4gIFVzZXJzIGFyZSBoZWF2aWx5IGNvdW50aW5nIG9uICB3aXJlbGVzcw0K
PiBhbmQgbW9iaWxlIGRldmljZXMgZm9yIHZpZGVvIHN0cmVhbWluZyBhbmQgaW50ZXJhY3RpdmUg
dmlkZW8NCj4gICAgYW5kIG11bHRpbWVkaWEgYXBwbGljYXRpb25zLiAgVGhpcyBjYW4gYmUgaW1w
bGVtZW50ZWQgZm9yIGluc3RhbmNlIGJ5DQo+IGhhdmluZyBtb3JlIGludGVsbGlnZW5jZSBpbiB0
aGUgc2VydmljZSBhbmQgdGhlIG5ldHdvcmsgaW5mcmFzdHJ1Y3R1cmUgdG8NCj4gYmV0dGVyIHN1
aXQgYSBkaWZmZXJlbnRpYXRlZCB1c2VycyBjb25zdW1wdGlvbiAgc3R5bGUuICBUaGlzIGNhbiBi
ZSBhY2hpZXZlZA0KPiAgICB0aHJvdWdoIGhhdmluZzogKGkpIGEga25vd2xlZGdlIGluIHRoZSBu
ZXR3b3JrIGFuZCBzZXJ2aWNlIHBsYXRmb3JtIGFib3V0DQo+IHRoZSBhdmFpbGFibGUgZGV2aWNl
IGFuZCBuZXR3b3JrIGNvbmRpdGlvbnMgZm9yIHRoZSBlbmQtdXNlciBhbmQgKGlpKSBhDQo+IGtu
b3dsZWRnZSBpbiB0aGUgbmV0d29yayBhYm91dCB0aGUgY29udGVudCByZXF1aXJlbWVudHMgaW4g
dGVybXMgb2YgZGV2aWNlcw0KPiAgICBjYXBhYmlsaXRpZXMgYW5kIG5ldHdvcmsgcmVzb3VyY2Vz
IGZvciBjb250ZW50IHN0b3JlZCBlaXRoZXIgaW4gdGhlIG5ldHdvcmsNCj4gb3IgaW4gdGhlIGFw
cGxpY2F0aW9uIHNlcnZlci4gIFRvIG9idGFpbiBzdWNoIGtub3dsZWRnZSB3aXRoIG5vIG5lZWQg
Zm9yDQo+IGNoYW5naW5nIHRoZSBjdXJyZW50IGluZnJhc3RydWN0dXJlIGFuZCBpbiBhIGdlbmVy
YWxpemVkIHdheSB0byBhbGwNCj4gICAgYXBwbGljYXRpb25zLCBmZWVkYmFjay9ub3RpZmljYXRp
b24gbWVjaGFuaXNtcyBiZXR3ZWVuIHRoZSBlbmQtdXNlcg0KPiBhcHBsaWNhdGlvbiwgdGhlIG5l
dHdvcmsgYW5kIHRoZSBzZXJ2aWNlIHBsYXRmb3JtIGlzIG5lZWRlZCB0byBwcm92aWRlDQo+IGlu
Zm9ybWF0aW9uIGhlbHBpbmcgdGhlIGNvbnRlbnQgZGVsaXZlcnkgYW5kIGFkYXB0YXRpb24gZGVj
aXNpb25zLiAgVGhpcw0KPiBkb2N1bWVudA0KPiAgICAgaXMgaW52ZXN0aWdhdGluZyBzdWNoIGFw
cGxpY2F0aW9uLWFnbm9zdGljIHRyYWNrLg0KPiANCj4gICAgVGhpcyBkb2N1bWVudCBleHRlbmRz
IHRoZSBQb3J0IENvbnRyb2wgUHJvdG9jb2wgKFBDUCkgUkZDIDY4ODcgIFtSRkM2ODg3XQ0KPiB0
byBhbGxvdzogKGkpIHRoZSB1c2VycyBhcHBsaWNhdGlvbiB0byBub3RpZnkgdGhlIG5ldHdvcmsg
YW5kIGFwcGxpY2F0aW9uDQo+IHNlcnZlciBhYm91dCBpdHMgYXZhaWxhYmxlIHJlc291cmNlcyBp
biB0ZXJtcyBvZg0KPiAgICBkZXZpY2VzIGNhcGFiaWxpdGllcyBhbmQgbmV0d29yayBjb25kaXRp
b25zIGFzIHdlbGwgYXMgaW5mb3JtYXRpb24gYWJvdXQNCj4gdGhlIHVzZXIgKGUuZy4sIGxvY2F0
aW9uLCBtb2JpbGl0eSBzdGF0dXMpIGFuZCAoaWkpIHRoZSBhcHBsaWNhdGlvbiBzZXJ2ZXIgdG8N
Cj4gbm90aWZ5IHRoZSBuZXR3b3JrIGFib3V0IHRoZSByZXF1aXJlbWVudHMgb2YNCj4gICAgdGhl
IGNvbnRlbnQgaXQgc3RvcmVzIGluIHRlcm1zIG9mIGRldmljZXMgYW5kIG5ldHdvcmsgcmVzb3Vy
Y2VzLiAgQSBuZXcgUENQDQo+IG9wdGlvbiwgZGVub3RlZCB0aGUgRkVFREJBQ0ssIGlzIHNwZWNp
ZmllZCB0byBhbGxvdyBzdWNoIGZlZWRiYWNrIG5vdGlmaWNhdGlvbg0KPiBzaWduYWxpbmcuICBU
aGlzIG9wdGlvbiBpcyB1c2VkIHdpdGggYm90aCBQRUVSDQo+ICAgIGFuZCBNQVAgT3Bjb2Rlcy4i
DQo+IA0KPiBMb29raW5nIGZvcndhcmQgdG8gaGF2aW5nIHlvdXIgZmVlZGJhY2sgYW5kIG1vcmUg
ZGlzY3Vzc2lvbiBvbiB0aGlzIGRyYWZ0Lg0KPiANCj4gUmVnYXJkcywNCj4gSGFzc25hYQ0KPiAN
Cj4gDQo+IA0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpbnRlcm5ldC1k
cmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmddDQo+IFNlbnQ6
IE1vbmRheSwgTm92ZW1iZXIgMDQsIDIwMTMgNDowNiBBTQ0KPiBUbzogTW9oYW1lZCBCb3VjYWRh
aXI7IE1vdXN0YWZhLCBIYXNzbmFhOyBNb3NlcywgRGFubnkNCj4gU3ViamVjdDogTmV3IFZlcnNp
b24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1tb3UtcGNwLWFwcGxpY2F0aW9uLW5ldHdvcmstDQo+
IGZlZWRiYWNrLTAwLnR4dA0KPiANCj4gDQo+IEEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1t
b3UtcGNwLWFwcGxpY2F0aW9uLW5ldHdvcmstZmVlZGJhY2stMDAudHh0DQo+IGhhcyBiZWVuIHN1
Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgSGFzc25hYSBNb3VzdGFmYSBhbmQgcG9zdGVkIHRvIHRo
ZSBJRVRGDQo+IHJlcG9zaXRvcnkuDQo+IA0KPiBGaWxlbmFtZToJIGRyYWZ0LW1vdS1wY3AtYXBw
bGljYXRpb24tbmV0d29yay1mZWVkYmFjaw0KPiBSZXZpc2lvbjoJIDAwDQo+IFRpdGxlOgkJIFBD
UCBFeHRlbnNpb24gZm9yIFNpZ25hbGluZyBGZWVkYmFjayBJbmZvcm1hdGlvbiBmcm9tIHRoZSBF
bmQtDQo+IFVzZXIgQXBwbGljYXRpb24gdG8gdGhlIEFwcGxpY2F0aW9uIFNldmVyIGFuZCB0byB0
aGUgTmV0d29yaw0KPiBDcmVhdGlvbiBkYXRlOgkgMjAxMy0xMS0wNA0KPiBHcm91cDoJCSBJbmRp
dmlkdWFsIFN1Ym1pc3Npb24NCj4gTnVtYmVyIG9mIHBhZ2VzOiAxNA0KPiBVUkw6ICAgICAgICAg
ICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LW1vdS1wY3AtDQo+
IGFwcGxpY2F0aW9uLW5ldHdvcmstZmVlZGJhY2stMDAudHh0DQo+IFN0YXR1czogICAgICAgICAg
aHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1tb3UtcGNwLWFwcGxpY2F0aW9u
LQ0KPiBuZXR3b3JrLWZlZWRiYWNrDQo+IEh0bWxpemVkOiAgICAgICAgaHR0cDovL3Rvb2xzLmll
dGYub3JnL2h0bWwvZHJhZnQtbW91LXBjcC1hcHBsaWNhdGlvbi1uZXR3b3JrLQ0KPiBmZWVkYmFj
ay0wMA0KPiANCj4gDQo+IEFic3RyYWN0Og0KPiAgICBOb3dhZGF5cyB1c2VycyBjb25zdW1wdGlv
biBzdHlsZSBmb3IgdmlkZW8gYW5kIG11bHRpbWVkaWENCj4gICAgYXBwbGljYXRpb25zIGlzIHN0
cm9uZ2x5IGNoYW5naW5nLiAgVXNlcnMgYXJlIGhlYXZpbHkgY291bnRpbmcgb24NCj4gICAgd2ly
ZWxlc3MgYW5kIG1vYmlsZSBkZXZpY2VzIGZvciB2aWRlbyBzdHJlYW1pbmcgYW5kIGludGVyYWN0
aXZlIHZpZGVvDQo+ICAgIGFuZCBtdWx0aW1lZGlhIGFwcGxpY2F0aW9ucy4gIFRoaXMgY2FuIGJl
IGltcGxlbWVudGVkIGZvciBpbnN0YW5jZSBieQ0KPiAgICBoYXZpbmcgbW9yZSBpbnRlbGxpZ2Vu
Y2UgaW4gdGhlIHNlcnZpY2UgYW5kIHRoZSBuZXR3b3JrDQo+ICAgIGluZnJhc3RydWN0dXJlIHRv
IGJldHRlciBzdWl0IGEgZGlmZmVyZW50aWF0ZWQgdXNlcnMgY29uc3VtcHRpb24NCj4gICAgc3R5
bGUuICBUaGlzIGNhbiBiZSBhY2hpZXZlZCB0aHJvdWdoIGhhdmluZzogKGkpIGEga25vd2xlZGdl
IGluIHRoZQ0KPiAgICBuZXR3b3JrIGFuZCBzZXJ2aWNlIHBsYXRmb3JtIGFib3V0IHRoZSBhdmFp
bGFibGUgZGV2aWNlIGFuZCBuZXR3b3JrDQo+ICAgIGNvbmRpdGlvbnMgZm9yIHRoZSBlbmQtdXNl
ciBhbmQgKGlpKSBhIGtub3dsZWRnZSBpbiB0aGUgbmV0d29yayBhYm91dA0KPiAgICB0aGUgY29u
dGVudCByZXF1aXJlbWVudHMgaW4gdGVybXMgb2YgZGV2aWNlcyBjYXBhYmlsaXRpZXMgYW5kIG5l
dHdvcmsNCj4gICAgcmVzb3VyY2VzIGZvciBjb250ZW50IHN0b3JlZCBlaXRoZXIgaW4gdGhlIG5l
dHdvcmsgb3IgaW4gdGhlDQo+ICAgIGFwcGxpY2F0aW9uIHNlcnZlci4gIFRvIG9idGFpbiBzdWNo
IGtub3dsZWRnZSB3aXRoIG5vIG5lZWQgZm9yDQo+ICAgIGNoYW5naW5nIHRoZSBjdXJyZW50IGlu
ZnJhc3RydWN0dXJlIGFuZCBpbiBhIGdlbmVyYWxpemVkIHdheSB0byBhbGwNCj4gICAgYXBwbGlj
YXRpb25zLCBmZWVkYmFjay9ub3RpZmljYXRpb24gbWVjaGFuaXNtcyBiZXR3ZWVuIHRoZSBlbmQt
dXNlcg0KPiAgICBhcHBsaWNhdGlvbiwgdGhlIG5ldHdvcmsgYW5kIHRoZSBzZXJ2aWNlIHBsYXRm
b3JtIGlzIG5lZWRlZCB0bw0KPiAgICBwcm92aWRlIGluZm9ybWF0aW9uIGhlbHBpbmcgdGhlIGNv
bnRlbnQgZGVsaXZlcnkgYW5kIGFkYXB0YXRpb24NCj4gICAgZGVjaXNpb25zLiAgVGhpcyBkb2N1
bWVudCBpcyBpbnZlc3RpZ2F0aW5nIHN1Y2ggYXBwbGljYXRpb24tYWdub3N0aWMNCj4gICAgdHJh
Y2suDQo+IA0KPiAgICBUaGlzIGRvY3VtZW50IGV4dGVuZHMgdGhlIFBvcnQgQ29udHJvbCBQcm90
b2NvbCAoUENQKSBSRkMgNjg4Nw0KPiAgICBbUkZDNjg4N10gdG8gYWxsb3c6IChpKSB0aGUgdXNl
cnMgYXBwbGljYXRpb24gdG8gbm90aWZ5IHRoZSBuZXR3b3JrDQo+ICAgIGFuZCBhcHBsaWNhdGlv
biBzZXJ2ZXIgYWJvdXQgaXRzIGF2YWlsYWJsZSByZXNvdXJjZXMgaW4gdGVybXMgb2YNCj4gICAg
ZGV2aWNlcyBjYXBhYmlsaXRpZXMgYW5kIG5ldHdvcmsgY29uZGl0aW9ucyBhcyB3ZWxsIGFzIGlu
Zm9ybWF0aW9uDQo+ICAgIGFib3V0IHRoZSB1c2VyIChlLmcuLCBsb2NhdGlvbiwgbW9iaWxpdHkg
c3RhdHVzKSBhbmQgKGlpKSB0aGUNCj4gICAgYXBwbGljYXRpb24gc2VydmVyIHRvIG5vdGlmeSB0
aGUgbmV0d29yayBhYm91dCB0aGUgcmVxdWlyZW1lbnRzIG9mDQo+ICAgIHRoZSBjb250ZW50IGl0
IHN0b3JlcyBpbiB0ZXJtcyBvZiBkZXZpY2VzIGFuZCBuZXR3b3JrIHJlc291cmNlcy4gIEENCj4g
ICAgbmV3IFBDUCBvcHRpb24sIGRlbm90ZWQgdGhlIEZFRURCQUNLLCBpcyBzcGVjaWZpZWQgdG8g
YWxsb3cgc3VjaA0KPiAgICBmZWVkYmFjayBub3RpZmljYXRpb24gc2lnbmFsaW5nLiAgVGhpcyBv
cHRpb24gaXMgdXNlZCB3aXRoIGJvdGggUEVFUg0KPiAgICBhbmQgTUFQIE9wY29kZXMuDQo+IA0K
PiANCj4gDQo+IA0KPiBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1p
bnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uDQo+IHVudGlsIHRoZSBodG1saXplZCB2
ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQo+IA0KPiBU
aGUgSUVURiBTZWNyZXRhcmlhdA0KDQo=

From hassnaa.moustafa@intel.com  Tue Nov  5 21:44:39 2013
Return-Path: <hassnaa.moustafa@intel.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D638621E80C2 for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 21:44:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id opesGNdkBfjk for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 21:44:35 -0800 (PST)
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by ietfa.amsl.com (Postfix) with ESMTP id DA85411E80F8 for <pcp@ietf.org>; Tue,  5 Nov 2013 21:44:34 -0800 (PST)
Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 05 Nov 2013 21:40:57 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.93,535,1378882800";  d="scan'208,217";a="404295864"
Received: from orsmsx107.amr.corp.intel.com ([10.22.240.5]) by orsmga001.jf.intel.com with ESMTP; 05 Nov 2013 21:44:24 -0800
Received: from orsmsx151.amr.corp.intel.com (10.22.226.38) by ORSMSX107.amr.corp.intel.com (10.22.240.5) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 5 Nov 2013 21:44:23 -0800
Received: from orsmsx102.amr.corp.intel.com ([169.254.1.203]) by ORSMSX151.amr.corp.intel.com ([10.22.226.38]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 21:44:23 -0800
From: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: Ac7agaDvGxDJgWj7TwOo0SUAuIXPuQAL9mSA
Date: Wed, 6 Nov 2013 05:44:22 +0000
Message-ID: <F893BEC192403B489DBA38999068CF19059498A9@ORSMSX102.amr.corp.intel.com>
References: <AE7F97DB5FEE054088D82E836BD15BE920134B70@xmb-aln-x05.cisco.com>
In-Reply-To: <AE7F97DB5FEE054088D82E836BD15BE920134B70@xmb-aln-x05.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.22.254.140]
Content-Type: multipart/alternative; boundary="_000_F893BEC192403B489DBA38999068CF19059498A9ORSMSX102amrcor_"
MIME-Version: 1.0
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2013 05:44:40 -0000

--_000_F893BEC192403B489DBA38999068CF19059498A9ORSMSX102amrcor_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks Bill for your comments.
To answer your questions:

-        The intent is to use PCP signaling mechanism to help the adaptatio=
n process (through using the information sent through PCP signals). How the=
 adaptation is done is out of the scope of the draft and is not a point tha=
t PCP or other WGs look at, for this the draft does not discuss that but gi=
ve optimization/adaptation examples in Section 3.5 (just as examples not mo=
re). So the draft approach aligns with what you see (point 2) and not (poin=
t 1)

-        For the metadata that needs to be exchange: there are some use-cas=
es defined in the draft showing how the knowledge of metadata helps in lett=
ing the network takes smart decisions in the adaptation process. Sure we ca=
n discuss more on that.

-        The video-specific metadata "mainly the draft considers the video =
content requirement for network bandwidth and devices resources", when know=
n by the network, allows the network to decide on the best adaptation to do=
 for the video through real-time transcoding for example, to save in bandwi=
dth and network resources.

-        For your last point (Having said that,  I do like the idea of exch=
anging stuff like network bandwidth/delay/loss/jitter/cost (aka network met=
adata) and application flow priority/type/desired treatment (aka flow metad=
ata)) --> I totally agree, for this the PCP feedback option proposed in the=
 draft is meant to work with the flowdata draft for this kind of metadata w=
hich we believe that flowdata considers.

Looking forward to more discussion during the PCP session.

Regards,
Hassnaa


From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of Bill =
Ver Steeg (versteb)
Sent: Tuesday, November 05, 2013 3:50 PM
To: pcp@ietf.org
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt


I have read this draft, and I have mixed emotions.



It is not clear (to me) if the intent is to use PCP to 1) actually invoke v=
ideo rate changes, or 2) use PCP signaling mechanisms to help the applicati=
on logic determine rate changes and to signal those rate changes to the net=
work.



IMHO- The former is not a good idea. The latter is an excellent idea, altho=
ugh I am not sure that all of the metadata described in this draft would be=
 useful.



I strongly encourage work in the area of exchanging metadata between the ho=
sts and the network edge. I am not sure that some of the video-specific met=
adata is useful (or appropriate) for consumption by the network. The bright=
ness, screen size, and the like is clearly useful to the client, and may ev=
en be useful for the server. However, I do not see how it is useful to the =
network.  Having said that,  I do like the idea of exchanging stuff like ne=
twork bandwidth/delay/loss/jitter/cost (aka network metadata) and applicati=
on flow priority/type/desired treatment (aka flow metadata).



I think that these points are worth spending some time on, and would like t=
o participate in that discussion.



Bill VerSteeg







>On 11/4/13 5:02 AM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com<mailto=
:hassnaa.moustafa@intel.com>>

>wrote:

>

>>Hi All,

>>

>>Draft (draft-mou-pcp-application-network-feedback) is a new draft that

>>is submitted today on (PCP Extension for Signaling Feedback

>>Information from the End-User Application to the Application Sever and to=
 the Network).

>>

>>The draft is available at :

>>http://www.ietf.org/internet-drafts/draft-mou-pcp-application-network-

>>fee

>>d

>>back-00.txt

>>

>>This draft addresses the need for more intelligence in the network and

>>service infrastructure for better content delivery to optimize the

>>network and devices resources. In this view, the draft proposes using

>>PCP to signal information for: i)  Knowledge in the network and

>>service platform about the available device and network conditions for

>>the end-user and ii) Knowledge in the network about the content

>>requirements in terms of devices and  network resources for content

>>stored either in the network or in the application server.

>>

>>The abstract of the draft is as follows:

>>" Abstract:    Nowadays users consumption style for video and multimedia

>>applications is strongly changing.  Users are heavily counting on

>>wireless and mobile devices for video streaming and interactive video

>>   and multimedia applications.  This can be implemented for instance

>>by having more intelligence in the service and the network

>>infrastructure to better suit a differentiated users consumption

>>style.  This can be achieved

>>   through having: (i) a knowledge in the network and service platform

>>about the available device and network conditions for the end-user and

>>(ii) a knowledge in the network about the content requirements in

>>terms of devices

>>   capabilities and network resources for content stored either in the

>>network or in the application server.  To obtain such knowledge with

>>no need for  changing the current infrastructure and in a generalized

>>way to all

>>   applications, feedback/notification mechanisms between the end-user

>>application, the network and the service platform is needed to provide

>>information helping the content delivery and adaptation decisions.

>>This document

>>    is investigating such application-agnostic track.

>>

>>   This document extends the Port Control Protocol (PCP) RFC 6887

>>[RFC6887] to allow: (i) the users application to notify the network

>>and application server about its available resources in terms of

>>   devices capabilities and network conditions as well as information

>>about the user (e.g., location, mobility status) and (ii) the

>>application server to notify the network about the requirements of

>>   the content it stores in terms of devices and network resources.  A

>>new PCP option, denoted the FEEDBACK, is specified to allow such

>>feedback notification signaling.  This option is used with both PEER

>>   and MAP Opcodes."

>>

>>Looking forward to having your feedback and more discussion on this

>>draft.

>>

>>Regards,

>>Hassnaa

>>

>>

>>

>>-----Original Message-----

>>From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:i=
nternet-drafts@ietf.org]

>>Sent: Monday, November 04, 2013 4:06 AM

>>To: Mohamed Boucadair; Moustafa, Hassnaa; Moses, Danny

>>Subject: New Version Notification for

>>draft-mou-pcp-application-network-feedback-00.txt

>>

>>

>>A new version of I-D,

>>draft-mou-pcp-application-network-feedback-00.txt

>>has been successfully submitted by Hassnaa Moustafa and posted to the

>>IETF repository.

>>

>>Filename:       draft-mou-pcp-application-network-feedback

>>Revision:        00

>>Title:                 PCP Extension for Signaling Feedback Information f=
rom the

>>End-User Application to the Application Sever and to the Network

>>Creation date:              2013-11-04

>>Group:                             Individual Submission

>>Number of pages: 14

>>URL:

>>http://www.ietf.org/internet-drafts/draft-mou-pcp-application-network-

>>fee

>>d

>>back-00.txt

>>Status:

>>http://datatracker.ietf.org/doc/draft-mou-pcp-application-network-feed

>>bac

>>k

>>Htmlized:

>>http://tools.ietf.org/html/draft-mou-pcp-application-network-feedback-

>>00

>>

>>

>>Abstract:

>>   Nowadays users consumption style for video and multimedia

>>   applications is strongly changing.  Users are heavily counting on

>>   wireless and mobile devices for video streaming and interactive video

>>   and multimedia applications.  This can be implemented for instance by

>>   having more intelligence in the service and the network

>>   infrastructure to better suit a differentiated users consumption

>>   style.  This can be achieved through having: (i) a knowledge in the

>>   network and service platform about the available device and network

>>   conditions for the end-user and (ii) a knowledge in the network about

>>   the content requirements in terms of devices capabilities and network

>>   resources for content stored either in the network or in the

>>   application server.  To obtain such knowledge with no need for

>>   changing the current infrastructure and in a generalized way to all

>>   applications, feedback/notification mechanisms between the end-user

>>   application, the network and the service platform is needed to

>>   provide information helping the content delivery and adaptation

>>   decisions.  This document is investigating such application-agnostic

>>   track.

>>

>>   This document extends the Port Control Protocol (PCP) RFC 6887

>>   [RFC6887] to allow: (i) the users application to notify the network

>>   and application server about its available resources in terms of

>>   devices capabilities and network conditions as well as information

>>   about the user (e.g., location, mobility status) and (ii) the

>>   application server to notify the network about the requirements of

>>   the content it stores in terms of devices and network resources.  A

>>   new PCP option, denoted the FEEDBACK, is specified to allow such

>>   feedback notification signaling.  This option is used with both PEER

>>   and MAP Opcodes.

>>

>>

>>

>>

>>

>>Please note that it may take a couple of minutes from the time of

>>submission until the htmlized version and diff are available at

>>tools.ietf.org.

>>

>>The IETF Secretariat

>>

>


--_000_F893BEC192403B489DBA38999068CF19059498A9ORSMSX102amrcor_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:767892208;
	mso-list-type:hybrid;
	mso-list-template-ids:-723116960 1719411782 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks Bill for your c=
omments.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">To answer your questio=
ns:<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">The intent is =
to use PCP signaling mechanism to help the adaptation process (through usin=
g the information sent through PCP signals). How the adaptation is done is =
out of the scope of the draft and
 is not a point that PCP or other WGs look at, for this the draft does not =
discuss that but give optimization/adaptation examples in Section 3.5 (just=
 as examples not more). So the draft approach aligns with what you see (poi=
nt 2) and not (point 1)<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">For the metada=
ta that needs to be exchange: there are some use-cases defined in the draft=
 showing how the knowledge of metadata helps in letting the network takes s=
mart decisions in the adaptation process.
 Sure we can discuss more on that.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">The video-spec=
ific metadata &#8220;mainly the draft considers the video content requireme=
nt for network bandwidth and devices resources&#8221;, when known by the ne=
twork, allows the network to decide on the best
 adaptation to do for the video through real-time transcoding for example, =
to save in bandwidth and network resources.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">For your last =
point (</span>Having said that, &nbsp;I do like the idea of exchanging stuf=
f like network bandwidth/delay/loss/jitter/cost (aka network metadata) and =
application flow priority/type/desired
 treatment (aka flow metadata)<span style=3D"color:#1F497D">) </span><span =
style=3D"font-family:Wingdings;color:#1F497D">=E0</span><span style=3D"colo=
r:#1F497D"> I totally agree, for this the PCP feedback option proposed in t=
he draft is meant to work with the flowdata
 draft for this kind of metadata which we believe that flowdata considers.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Looking forward to mor=
e discussion during the PCP session.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hassnaa<o:p></o:p></sp=
an></p>
<p class=3D"MsoListParagraph"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:=
p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> pcp-boun=
ces@ietf.org [mailto:pcp-bounces@ietf.org]
<b>On Behalf Of </b>Bill Ver Steeg (versteb)<br>
<b>Sent:</b> Tuesday, November 05, 2013 3:50 PM<br>
<b>To:</b> pcp@ietf.org<br>
<b>Subject:</b> Re: [pcp] New Submission: draft-mou-pcp-application-network=
-feedback-00.txt<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I have read this draft, and I have mixed emotions=
.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">It is not clear (to me) if the intent is to use P=
CP to 1) actually invoke video rate changes, or 2) use PCP signaling mechan=
isms to help the application logic determine rate changes and to signal tho=
se rate changes to the network.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">IMHO- The former is not a good idea. The latter i=
s an excellent idea, although I am not sure that all of the metadata descri=
bed in this draft would be useful.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I strongly encourage work in the area of exchangi=
ng metadata between the hosts and the network edge. I am not sure that some=
 of the video-specific metadata is useful (or appropriate) for consumption =
by the network. The brightness, screen
 size, and the like is clearly useful to the client, and may even be useful=
 for the server. However, I do not see how it is useful to the network.&nbs=
p; Having said that, &nbsp;I do like the idea of exchanging stuff like netw=
ork bandwidth/delay/loss/jitter/cost (aka
 network metadata) and application flow priority/type/desired treatment (ak=
a flow metadata).<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I think that these points are worth spending some=
 time on, and would like to participate in that discussion.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Bill VerSteeg<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;On 11/4/13 5:02 AM, &quot;Moustafa, Hassnaa&q=
uot; &lt;<a href=3D"mailto:hassnaa.moustafa@intel.com">hassnaa.moustafa@int=
el.com</a>&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;wrote:<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Hi All,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Draft (draft-mou-pcp-application-network-=
feedback) is a new draft that
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;is submitted today on (PCP Extension for =
Signaling Feedback
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Information from the End-User Application=
 to the Application Sever and to the Network).<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;The draft is available at :<o:p></o:p></p=
>
<p class=3D"MsoPlainText">&gt;&gt;<a href=3D"http://www.ietf.org/internet-d=
rafts/draft-mou-pcp-application-network-">http://www.ietf.org/internet-draf=
ts/draft-mou-pcp-application-network-</a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;fee<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;d<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;back-00.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;This draft addresses the need for more in=
telligence in the network and
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;service infrastructure for better content=
 delivery to optimize the
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;network and devices resources. In this vi=
ew, the draft proposes using
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;PCP to signal information for: i)&nbsp; K=
nowledge in the network and
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;service platform about the available devi=
ce and network conditions for
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;the end-user and ii) Knowledge in the net=
work about the content
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;requirements in terms of devices and&nbsp=
; network resources for content
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;stored either in the network or in the ap=
plication server.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;The abstract of the draft is as follows:<=
o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&quot; Abstract:&nbsp;&nbsp;&nbsp; Nowada=
ys users consumption style for video and multimedia<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;applications is strongly changing.&nbsp; =
Users are heavily counting on
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;wireless and mobile devices for video str=
eaming and interactive video<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and multimedia applications.=
&nbsp; This can be implemented for instance
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;by having more intelligence in the servic=
e and the network
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;infrastructure to better suit a different=
iated users consumption
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;style.&nbsp; This can be achieved<o:p></o=
:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; through having: (i) a knowle=
dge in the network and service platform
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;about the available device and network co=
nditions for the end-user and<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;(ii) a knowledge in the network about the=
 content requirements in
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;terms of devices<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; capabilities and network res=
ources for content stored either in the
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;network or in the application server.&nbs=
p; To obtain such knowledge with
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;no need for&nbsp; changing the current in=
frastructure and in a generalized
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;way to all<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; applications, feedback/notif=
ication mechanisms between the end-user
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;application, the network and the service =
platform is needed to provide
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;information helping the content delivery =
and adaptation decisions.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;This document<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp; is investigating such =
application-agnostic track.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; This document extends the Po=
rt Control Protocol (PCP) RFC 6887
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;[RFC6887] to allow: (i) the users applica=
tion to notify the network
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;and application server about its availabl=
e resources in terms of<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; devices capabilities and net=
work conditions as well as information
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;about the user (e.g., location, mobility =
status) and (ii) the
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;application server to notify the network =
about the requirements of<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; the content it stores in ter=
ms of devices and network resources.&nbsp; A
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;new PCP option, denoted the FEEDBACK, is =
specified to allow such
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;feedback notification signaling.&nbsp; Th=
is option is used with both PEER<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and MAP Opcodes.&quot;<o:p><=
/o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Looking forward to having your feedback a=
nd more discussion on this
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;draft.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Regards,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Hassnaa<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;-----Original Message-----<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;From: <a href=3D"mailto:internet-drafts@i=
etf.org">internet-drafts@ietf.org</a> [<a href=3D"mailto:internet-drafts@ie=
tf.org">mailto:internet-drafts@ietf.org</a>]<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Sent: Monday, November 04, 2013 4:06 AM<o=
:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;To: Mohamed Boucadair; Moustafa, Hassnaa;=
 Moses, Danny<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Subject: New Version Notification for<o:p=
></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;draft-mou-pcp-application-network-feedbac=
k-00.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;A new version of I-D,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;draft-mou-pcp-application-network-feedbac=
k-00.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;has been successfully submitted by Hassna=
a Moustafa and posted to the
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;IETF repository.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Filename:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; draft-mou-pcp-application-network-feedback<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Revision:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; 00<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Title:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PCP Extension=
 for Signaling Feedback Information from the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;End-User Application to the Application S=
ever and to the Network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Creation date:&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-11-04<o:p></o:p></=
p>
<p class=3D"MsoPlainText">&gt;&gt;Group:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Individual Submi=
ssion<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Number of pages: 14<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;URL:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<a href=3D"http://www.ietf.org/internet-d=
rafts/draft-mou-pcp-application-network-">http://www.ietf.org/internet-draf=
ts/draft-mou-pcp-application-network-</a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;fee<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;d<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;back-00.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Status:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<a href=3D"http://datatracker.ietf.org/do=
c/draft-mou-pcp-application-network-feed">http://datatracker.ietf.org/doc/d=
raft-mou-pcp-application-network-feed</a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;bac<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;k<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Htmlized:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<a href=3D"http://tools.ietf.org/html/dra=
ft-mou-pcp-application-network-feedback-">http://tools.ietf.org/html/draft-=
mou-pcp-application-network-feedback-</a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;00<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Abstract:<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; Nowadays users consumption s=
tyle for video and multimedia<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; applications is strongly cha=
nging.&nbsp; Users are heavily counting on<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; wireless and mobile devices =
for video streaming and interactive video<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and multimedia applications.=
&nbsp; This can be implemented for instance by<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; having more intelligence in =
the service and the network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; infrastructure to better sui=
t a differentiated users consumption<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; style.&nbsp; This can be ach=
ieved through having: (i) a knowledge in the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; network and service platform=
 about the available device and network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; conditions for the end-user =
and (ii) a knowledge in the network about<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; the content requirements in =
terms of devices capabilities and network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; resources for content stored=
 either in the network or in the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; application server.&nbsp; To=
 obtain such knowledge with no need for<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; changing the current infrast=
ructure and in a generalized way to all<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; applications, feedback/notif=
ication mechanisms between the end-user<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; application, the network and=
 the service platform is needed to<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; provide information helping =
the content delivery and adaptation<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; decisions.&nbsp; This docume=
nt is investigating such application-agnostic<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; track.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; This document extends the Po=
rt Control Protocol (PCP) RFC 6887<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; [RFC6887] to allow: (i) the =
users application to notify the network<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and application server about=
 its available resources in terms of<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; devices capabilities and net=
work conditions as well as information<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; about the user (e.g., locati=
on, mobility status) and (ii) the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp; &nbsp;application server to notify=
 the network about the requirements of<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; the content it stores in ter=
ms of devices and network resources.&nbsp; A<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; new PCP option, denoted the =
FEEDBACK, is specified to allow such<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; feedback notification signal=
ing.&nbsp; This option is used with both PEER<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp; and MAP Opcodes.<o:p></o:p><=
/p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;Please note that it may take a couple of =
minutes from the time of
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;submission until the htmlized version and=
 diff are available at
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;tools.ietf.org.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;The IETF Secretariat<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_F893BEC192403B489DBA38999068CF19059498A9ORSMSX102amrcor_--

From hassnaa.moustafa@intel.com  Tue Nov  5 21:55:45 2013
Return-Path: <hassnaa.moustafa@intel.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFB9211E818B for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 21:55:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cDeMtCoO63Ss for <pcp@ietfa.amsl.com>; Tue,  5 Nov 2013 21:55:41 -0800 (PST)
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by ietfa.amsl.com (Postfix) with ESMTP id B707A11E8131 for <pcp@ietf.org>; Tue,  5 Nov 2013 21:55:39 -0800 (PST)
Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 05 Nov 2013 21:52:10 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.93,535,1378882800"; d="scan'208";a="430507911"
Received: from orsmsx108.amr.corp.intel.com ([10.22.240.6]) by orsmga002.jf.intel.com with ESMTP; 05 Nov 2013 21:55:36 -0800
Received: from orsmsx157.amr.corp.intel.com (10.22.240.23) by ORSMSX108.amr.corp.intel.com (10.22.240.6) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 5 Nov 2013 21:55:36 -0800
Received: from orsmsx102.amr.corp.intel.com ([169.254.1.203]) by ORSMSX157.amr.corp.intel.com ([169.254.9.23]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 21:55:36 -0800
From: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: AQHO2Zh1uTiiF1x+nUCuhfgqIOiaBpoXkJ+QgAAizlA=
Date: Wed, 6 Nov 2013 05:55:35 +0000
Message-ID: <F893BEC192403B489DBA38999068CF19059498E0@ORSMSX102.amr.corp.intel.com>
References: <F893BEC192403B489DBA38999068CF190594847F@ORSMSX102.amr.corp.intel.com> <913383AAA69FF945B8F946018B75898A2425CF92@xmb-rcd-x10.cisco.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A2425CF92@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.22.254.140]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission:	draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2013 05:55:45 -0000

VGhhbmtzIFRpcnUgZm9yIHlvdXIgY29tbWVudHMuDQpQbGVhc2UgZmluZCBteSBhbnN3ZXJzOg0K
MSkgSWYgdGhlIGNsaWVudCBsZWFybnMgdGhhdCB0aGUgYmF0dGVyeSBjb25kaXRpb25zLCBsaWdo
dCBsZXZlbHMgaGF2ZSBjaGFuZ2VkIC0NCmEpIHdoeSBjYW4ndCB0aGUgY2xpZW50IHJlcXVlc3Qg
c3Vic2VxdWVudCBjaHVuayB3aXRoIGRpZmZlcmVudCBlbmNvZGluZyBmcm9tIHRoZSBVUkwgaW4g
dGhlIG1hbmlmZXN0IGZpbGUgPw0KYikgd2h5IGNhbid0IHRoZSBjbGllbnQgYmUgaW50ZWxsaWdl
bnQgZW5vdWdoIHRvIHBpY2sgdGhlIHN1YnNlcXVlbnQgY2h1bmsgd2l0aCBhcHByb3ByaWF0ZSBi
aXQtcmF0ZSBiYXNlZCBvbiBlbmRwb2ludCBkZXZpY2UgY29uZGl0aW9ucyA/DQoNCkhhc3NuYWE6
IHRoaXMgaXMgcG9zc2libGUgZm9yIEhUVFAgYWRhcHRpdmUgc3RyZWFtaW5nIHdoZXJlIHRoZSBj
bGllbnQgY29udHJvbHMgdGhlIHZpZGVvIHNlbGVjdGlvbiwgYnV0IGNvdWxkIG5vdCBiZSBkb25l
IGluIFJUUCB2aWRlbyBzdHJlYW1pbmcgYW5kIHZpZGVvIGNvbmZlcmVuY2luZyBhcHBsaWNhdGlv
bnMgaW4gd2hpY2ggdGhlIHNlcnZlciBzaG91bGQgdGFrZSB0aGUgYWRhcHRhdGlvbiBkZWNpc2lv
biBiYXNlZCBvbiBzb21lIGluZm9ybWF0aW9uIGtub3duIGZyb20gdGhlIGNsaWVudC4gQW5kIGV2
ZW4gZm9yIEhUVFAgYWRhcHRpdmUgc3RyZWFtaW5nLCB0aGUgY2xpZW50IGRvZXMgbm90IGhhdmUg
YSBmdWxsIHZpZXcgb2YgdGhlIG5ldHdvcmsgKGJ1dCBvbmx5IHRoZSB0aHJvdWdocHV0IGZvciBo
aXMgY29ubmVjdGl2aXR5KSBhbmQgaWYgdGhlIGFkYXB0YXRpb24gaXMgZG9uZSBieSB0aGUgbmV0
d29yayBpdHNlbGYgaXQgd2lsbCBjb25zaWRlciB0aGUgZ2xvYmFsIGJhbmR3aWR0aC4NCg0KMikg
dXNlIGNhc2UgaW4gc2VjdGlvbiAzLjIgb2YgdGhlIGRyYWZ0OyB1Q0ROICh1cHN0cmVhbSBDRE4p
IGJhc2VkIG9uIGxvY2F0aW9uIG9mIHRoZSBjbGllbnQgYW5kIG90aGVyIHBhcmFtZXRlcnMgcXVl
cmllcyBhdmFpbGFibGUgZENETiAoRG93bnN0cmVhbSBDRE4pIHRvIHNlbGVjdHMgdGhlIGRDRE4g
Zm9yIHNlcnZpbmcgY29udGVudCB0byB0aGUgY2xpZW50LiANCkhvdyBpcyBGRUVEQkFDSyBvcHRp
b24gdXNlZnVsIHdpdGggdUNETi9kQ0ROID8NCg0KSGFzc25hYTogVGhpcyB1c2UtY2FzZSBpbiB0
aGlzIGN1cnJlbnQgdmVyc2lvbiBvZiB0aGUgZHJhZnQgZG9lcyBub3QgY29uc2lkZXIgQ0ROLUkg
KENETiBJbnRlcmNvKSBidXQgaXQgaXMgYSB2ZXJ5IGdvb2QgcG9pbnQgdG8gY29uc2lkZXIgYSB1
c2UtY2FzZSBkb2UgQ0ROLUkgaW4gdGhlIG5leHQgdmVyc2lvbiBvZiB0aGUgZHJhZnQuIFdoYXQg
dGhlIGN1cnJlbnQgdXNlLWNhc2UgY29uc2lkZXJzIGlzIHNpbXBseSBhIGNvbnRyb2xsZXIgbm9k
ZSB0aGF0IGNvbnRyb2xzIHRoZSBtdWx0aXBsZSBBcHBsaWNhdGlvbiBzZXJ2ZXJzIGluIHRoZSBz
ZXJ2aWNlIHBsYXRmb3JtLiBBbmQgaGVyZSB0aGUgZmVlZGJhY2sgb3B0aW9uIGlzIHVzZWZ1bCBh
cyBpdCBhbGxvd3MgdGhlIGNvbnRyb2xsZXIgdG8gZG8gYSBzZWxlY3Rpb24gb2YgdGhlIGFwcGxp
Y2F0aW9uIHNlcnZlciBoYXZpbmcgY29udGVudCBtYXRjaGluZyB0aGUgInVzZXIgbG9jYXRpb24g
bG9va2luZyBmb3IgcHJveGltaXR5LCB1c2VyIGRldmljZXMgcmVzb3VyY2VzIHRoYXQgYXJlIGF2
YWlsYWJsZSwgLi4iDQoNCg0KSG9wZSB0aGF0IHRoaXMgY2xhcmlmaWVzIHlvdXIgcXVlc3Rpb25z
IGFuZCBsb29raW5nIGZvcndhcmQgdG8gbW9yZSBkaXNjdXNzaW9uLg0KDQpSZWdhcmRzLA0KSGFz
c25hYQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogVGlydW1hbGVzd2FyIFJl
ZGR5ICh0aXJlZGR5KSBbbWFpbHRvOnRpcmVkZHlAY2lzY28uY29tXSANClNlbnQ6IFR1ZXNkYXks
IE5vdmVtYmVyIDA1LCAyMDEzIDc6NTggUE0NClRvOiBNb3VzdGFmYSwgSGFzc25hYTsgcGNwQGll
dGYub3JnDQpDYzogTW9zZXMsIERhbm55DQpTdWJqZWN0OiBSRTogW3BjcF0gTmV3IFN1Ym1pc3Np
b246IGRyYWZ0LW1vdS1wY3AtYXBwbGljYXRpb24tbmV0d29yay1mZWVkYmFjay0wMC50eHQNCg0K
SGksDQoNCk15IGluaXRpYWwgY29tbWVudHM6DQoNCjEpIElmIHRoZSBjbGllbnQgbGVhcm5zIHRo
YXQgdGhlIGJhdHRlcnkgY29uZGl0aW9ucywgbGlnaHQgbGV2ZWxzIGhhdmUgY2hhbmdlZCAtDQph
KSB3aHkgY2FuJ3QgdGhlIGNsaWVudCByZXF1ZXN0IHN1YnNlcXVlbnQgY2h1bmsgd2l0aCBkaWZm
ZXJlbnQgZW5jb2RpbmcgZnJvbSB0aGUgVVJMIGluIHRoZSBtYW5pZmVzdCBmaWxlID8NCmIpIHdo
eSBjYW4ndCB0aGUgY2xpZW50IGJlIGludGVsbGlnZW50IGVub3VnaCB0byBwaWNrIHRoZSBzdWJz
ZXF1ZW50IGNodW5rIHdpdGggYXBwcm9wcmlhdGUgYml0LXJhdGUgYmFzZWQgb24gZW5kcG9pbnQg
ZGV2aWNlIGNvbmRpdGlvbnMgPw0KDQoyKSB1c2UgY2FzZSBpbiBzZWN0aW9uIDMuMiBvZiB0aGUg
ZHJhZnQ7IHVDRE4gKHVwc3RyZWFtIENETikgYmFzZWQgb24gbG9jYXRpb24gb2YgdGhlIGNsaWVu
dCBhbmQgb3RoZXIgcGFyYW1ldGVycyBxdWVyaWVzIGF2YWlsYWJsZSBkQ0ROIChEb3duc3RyZWFt
IENETikgdG8gc2VsZWN0cyB0aGUgZENETiBmb3Igc2VydmluZyBjb250ZW50IHRvIHRoZSBjbGll
bnQuIA0KDQpIb3cgaXMgRkVFREJBQ0sgb3B0aW9uIHVzZWZ1bCB3aXRoIHVDRE4vZENETiA/DQoN
Ci1UaXJ1Lg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IE1vdXN0YWZh
LCBIYXNzbmFhIFttYWlsdG86aGFzc25hYS5tb3VzdGFmYUBpbnRlbC5jb21dDQo+IFNlbnQ6IE1v
bmRheSwgTm92ZW1iZXIgMDQsIDIwMTMgNjozMyBQTQ0KPiBUbzogcGNwQGlldGYub3JnDQo+IENj
OiBNb3NlcywgRGFubnkNCj4gU3ViamVjdDogW3BjcF0gTmV3IFN1Ym1pc3Npb246IA0KPiBkcmFm
dC1tb3UtcGNwLWFwcGxpY2F0aW9uLW5ldHdvcmstZmVlZGJhY2stDQo+IDAwLnR4dA0KPiANCj4g
SGkgQWxsLA0KPiANCj4gRHJhZnQgKGRyYWZ0LW1vdS1wY3AtYXBwbGljYXRpb24tbmV0d29yay1m
ZWVkYmFjaykgaXMgYSBuZXcgZHJhZnQgdGhhdCANCj4gaXMgc3VibWl0dGVkIHRvZGF5IG9uIChQ
Q1AgRXh0ZW5zaW9uIGZvciBTaWduYWxpbmcgRmVlZGJhY2sgDQo+IEluZm9ybWF0aW9uIGZyb20g
dGhlIEVuZC1Vc2VyIEFwcGxpY2F0aW9uIHRvIHRoZSBBcHBsaWNhdGlvbiBTZXZlciBhbmQgdG8g
dGhlIE5ldHdvcmspLg0KPiANCj4gVGhlIGRyYWZ0IGlzIGF2YWlsYWJsZSBhdCA6ICAgICAgICAg
ICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtDQo+IGRyYWZ0cy9kcmFmdC1tb3UtcGNw
LWFwcGxpY2F0aW9uLW5ldHdvcmstZmVlZGJhY2stMDAudHh0DQo+IA0KPiBUaGlzIGRyYWZ0IGFk
ZHJlc3NlcyB0aGUgbmVlZCBmb3IgbW9yZSBpbnRlbGxpZ2VuY2UgaW4gdGhlIG5ldHdvcmsgYW5k
IA0KPiBzZXJ2aWNlIGluZnJhc3RydWN0dXJlIGZvciBiZXR0ZXIgY29udGVudCBkZWxpdmVyeSB0
byBvcHRpbWl6ZSB0aGUgDQo+IG5ldHdvcmsgYW5kIGRldmljZXMgcmVzb3VyY2VzLiBJbiB0aGlz
IHZpZXcsIHRoZSBkcmFmdCBwcm9wb3NlcyB1c2luZyANCj4gUENQIHRvIHNpZ25hbCBpbmZvcm1h
dGlvbg0KPiBmb3I6IGkpICBLbm93bGVkZ2UgaW4gdGhlIG5ldHdvcmsgYW5kIHNlcnZpY2UgcGxh
dGZvcm0gYWJvdXQgdGhlIA0KPiBhdmFpbGFibGUgZGV2aWNlIGFuZCBuZXR3b3JrIGNvbmRpdGlv
bnMgZm9yIHRoZSBlbmQtdXNlciBhbmQgaWkpIA0KPiBLbm93bGVkZ2UgaW4gdGhlIG5ldHdvcmsg
YWJvdXQgdGhlIGNvbnRlbnQgcmVxdWlyZW1lbnRzIGluIHRlcm1zIG9mIA0KPiBkZXZpY2VzIGFu
ZCAgbmV0d29yayByZXNvdXJjZXMgZm9yIGNvbnRlbnQgc3RvcmVkIGVpdGhlciBpbiB0aGUgDQo+
IG5ldHdvcmsgb3IgaW4gdGhlIGFwcGxpY2F0aW9uIHNlcnZlci4NCj4gDQo+IFRoZSBhYnN0cmFj
dCBvZiB0aGUgZHJhZnQgaXMgYXMgZm9sbG93czoNCj4gIiBBYnN0cmFjdDogICAgTm93YWRheXMg
dXNlcnMgY29uc3VtcHRpb24gc3R5bGUgZm9yIHZpZGVvIGFuZCBtdWx0aW1lZGlhDQo+IGFwcGxp
Y2F0aW9ucyBpcyBzdHJvbmdseSBjaGFuZ2luZy4gIFVzZXJzIGFyZSBoZWF2aWx5IGNvdW50aW5n
IG9uICANCj4gd2lyZWxlc3MgYW5kIG1vYmlsZSBkZXZpY2VzIGZvciB2aWRlbyBzdHJlYW1pbmcg
YW5kIGludGVyYWN0aXZlIHZpZGVvDQo+ICAgIGFuZCBtdWx0aW1lZGlhIGFwcGxpY2F0aW9ucy4g
IFRoaXMgY2FuIGJlIGltcGxlbWVudGVkIGZvciBpbnN0YW5jZSANCj4gYnkgaGF2aW5nIG1vcmUg
aW50ZWxsaWdlbmNlIGluIHRoZSBzZXJ2aWNlIGFuZCB0aGUgbmV0d29yayANCj4gaW5mcmFzdHJ1
Y3R1cmUgdG8gYmV0dGVyIHN1aXQgYSBkaWZmZXJlbnRpYXRlZCB1c2VycyBjb25zdW1wdGlvbiAg
c3R5bGUuICBUaGlzIGNhbiBiZSBhY2hpZXZlZA0KPiAgICB0aHJvdWdoIGhhdmluZzogKGkpIGEg
a25vd2xlZGdlIGluIHRoZSBuZXR3b3JrIGFuZCBzZXJ2aWNlIHBsYXRmb3JtIA0KPiBhYm91dCB0
aGUgYXZhaWxhYmxlIGRldmljZSBhbmQgbmV0d29yayBjb25kaXRpb25zIGZvciB0aGUgZW5kLXVz
ZXIgYW5kIA0KPiAoaWkpIGEga25vd2xlZGdlIGluIHRoZSBuZXR3b3JrIGFib3V0IHRoZSBjb250
ZW50IHJlcXVpcmVtZW50cyBpbiB0ZXJtcyBvZiBkZXZpY2VzDQo+ICAgIGNhcGFiaWxpdGllcyBh
bmQgbmV0d29yayByZXNvdXJjZXMgZm9yIGNvbnRlbnQgc3RvcmVkIGVpdGhlciBpbiB0aGUgDQo+
IG5ldHdvcmsgb3IgaW4gdGhlIGFwcGxpY2F0aW9uIHNlcnZlci4gIFRvIG9idGFpbiBzdWNoIGtu
b3dsZWRnZSB3aXRoIA0KPiBubyBuZWVkIGZvciBjaGFuZ2luZyB0aGUgY3VycmVudCBpbmZyYXN0
cnVjdHVyZSBhbmQgaW4gYSBnZW5lcmFsaXplZCB3YXkgdG8gYWxsDQo+ICAgIGFwcGxpY2F0aW9u
cywgZmVlZGJhY2svbm90aWZpY2F0aW9uIG1lY2hhbmlzbXMgYmV0d2VlbiB0aGUgZW5kLXVzZXIg
DQo+IGFwcGxpY2F0aW9uLCB0aGUgbmV0d29yayBhbmQgdGhlIHNlcnZpY2UgcGxhdGZvcm0gaXMg
bmVlZGVkIHRvIHByb3ZpZGUgDQo+IGluZm9ybWF0aW9uIGhlbHBpbmcgdGhlIGNvbnRlbnQgZGVs
aXZlcnkgYW5kIGFkYXB0YXRpb24gZGVjaXNpb25zLiAgDQo+IFRoaXMgZG9jdW1lbnQNCj4gICAg
IGlzIGludmVzdGlnYXRpbmcgc3VjaCBhcHBsaWNhdGlvbi1hZ25vc3RpYyB0cmFjay4NCj4gDQo+
ICAgIFRoaXMgZG9jdW1lbnQgZXh0ZW5kcyB0aGUgUG9ydCBDb250cm9sIFByb3RvY29sIChQQ1Ap
IFJGQyA2ODg3ICANCj4gW1JGQzY4ODddIHRvIGFsbG93OiAoaSkgdGhlIHVzZXJzIGFwcGxpY2F0
aW9uIHRvIG5vdGlmeSB0aGUgbmV0d29yayANCj4gYW5kIGFwcGxpY2F0aW9uIHNlcnZlciBhYm91
dCBpdHMgYXZhaWxhYmxlIHJlc291cmNlcyBpbiB0ZXJtcyBvZg0KPiAgICBkZXZpY2VzIGNhcGFi
aWxpdGllcyBhbmQgbmV0d29yayBjb25kaXRpb25zIGFzIHdlbGwgYXMgaW5mb3JtYXRpb24gDQo+
IGFib3V0IHRoZSB1c2VyIChlLmcuLCBsb2NhdGlvbiwgbW9iaWxpdHkgc3RhdHVzKSBhbmQgKGlp
KSB0aGUgDQo+IGFwcGxpY2F0aW9uIHNlcnZlciB0byBub3RpZnkgdGhlIG5ldHdvcmsgYWJvdXQg
dGhlIHJlcXVpcmVtZW50cyBvZg0KPiAgICB0aGUgY29udGVudCBpdCBzdG9yZXMgaW4gdGVybXMg
b2YgZGV2aWNlcyBhbmQgbmV0d29yayByZXNvdXJjZXMuICBBIA0KPiBuZXcgUENQIG9wdGlvbiwg
ZGVub3RlZCB0aGUgRkVFREJBQ0ssIGlzIHNwZWNpZmllZCB0byBhbGxvdyBzdWNoIA0KPiBmZWVk
YmFjayBub3RpZmljYXRpb24gc2lnbmFsaW5nLiAgVGhpcyBvcHRpb24gaXMgdXNlZCB3aXRoIGJv
dGggUEVFUg0KPiAgICBhbmQgTUFQIE9wY29kZXMuIg0KPiANCj4gTG9va2luZyBmb3J3YXJkIHRv
IGhhdmluZyB5b3VyIGZlZWRiYWNrIGFuZCBtb3JlIGRpc2N1c3Npb24gb24gdGhpcyBkcmFmdC4N
Cj4gDQo+IFJlZ2FyZHMsDQo+IEhhc3NuYWENCj4gDQo+IA0KPiANCj4gLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCj4gRnJvbTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50
ZXJuZXQtZHJhZnRzQGlldGYub3JnXQ0KPiBTZW50OiBNb25kYXksIE5vdmVtYmVyIDA0LCAyMDEz
IDQ6MDYgQU0NCj4gVG86IE1vaGFtZWQgQm91Y2FkYWlyOyBNb3VzdGFmYSwgSGFzc25hYTsgTW9z
ZXMsIERhbm55DQo+IFN1YmplY3Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgDQo+IGRy
YWZ0LW1vdS1wY3AtYXBwbGljYXRpb24tbmV0d29yay0NCj4gZmVlZGJhY2stMDAudHh0DQo+IA0K
PiANCj4gQSBuZXcgdmVyc2lvbiBvZiBJLUQsIA0KPiBkcmFmdC1tb3UtcGNwLWFwcGxpY2F0aW9u
LW5ldHdvcmstZmVlZGJhY2stMDAudHh0DQo+IGhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0
ZWQgYnkgSGFzc25hYSBNb3VzdGFmYSBhbmQgcG9zdGVkIHRvIHRoZSANCj4gSUVURiByZXBvc2l0
b3J5Lg0KPiANCj4gRmlsZW5hbWU6CSBkcmFmdC1tb3UtcGNwLWFwcGxpY2F0aW9uLW5ldHdvcmst
ZmVlZGJhY2sNCj4gUmV2aXNpb246CSAwMA0KPiBUaXRsZToJCSBQQ1AgRXh0ZW5zaW9uIGZvciBT
aWduYWxpbmcgRmVlZGJhY2sgSW5mb3JtYXRpb24gZnJvbSB0aGUgRW5kLQ0KPiBVc2VyIEFwcGxp
Y2F0aW9uIHRvIHRoZSBBcHBsaWNhdGlvbiBTZXZlciBhbmQgdG8gdGhlIE5ldHdvcmsNCj4gQ3Jl
YXRpb24gZGF0ZToJIDIwMTMtMTEtMDQNCj4gR3JvdXA6CQkgSW5kaXZpZHVhbCBTdWJtaXNzaW9u
DQo+IE51bWJlciBvZiBwYWdlczogMTQNCj4gVVJMOiAgICAgICAgICAgICBodHRwOi8vd3d3Lmll
dGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1tb3UtcGNwLQ0KPiBhcHBsaWNhdGlvbi1uZXR3
b3JrLWZlZWRiYWNrLTAwLnR4dA0KPiBTdGF0dXM6ICAgICAgICAgIGh0dHA6Ly9kYXRhdHJhY2tl
ci5pZXRmLm9yZy9kb2MvZHJhZnQtbW91LXBjcC1hcHBsaWNhdGlvbi0NCj4gbmV0d29yay1mZWVk
YmFjaw0KPiBIdG1saXplZDogICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0
LW1vdS1wY3AtYXBwbGljYXRpb24tbmV0d29yay0NCj4gZmVlZGJhY2stMDANCj4gDQo+IA0KPiBB
YnN0cmFjdDoNCj4gICAgTm93YWRheXMgdXNlcnMgY29uc3VtcHRpb24gc3R5bGUgZm9yIHZpZGVv
IGFuZCBtdWx0aW1lZGlhDQo+ICAgIGFwcGxpY2F0aW9ucyBpcyBzdHJvbmdseSBjaGFuZ2luZy4g
IFVzZXJzIGFyZSBoZWF2aWx5IGNvdW50aW5nIG9uDQo+ICAgIHdpcmVsZXNzIGFuZCBtb2JpbGUg
ZGV2aWNlcyBmb3IgdmlkZW8gc3RyZWFtaW5nIGFuZCBpbnRlcmFjdGl2ZSB2aWRlbw0KPiAgICBh
bmQgbXVsdGltZWRpYSBhcHBsaWNhdGlvbnMuICBUaGlzIGNhbiBiZSBpbXBsZW1lbnRlZCBmb3Ig
aW5zdGFuY2UgYnkNCj4gICAgaGF2aW5nIG1vcmUgaW50ZWxsaWdlbmNlIGluIHRoZSBzZXJ2aWNl
IGFuZCB0aGUgbmV0d29yaw0KPiAgICBpbmZyYXN0cnVjdHVyZSB0byBiZXR0ZXIgc3VpdCBhIGRp
ZmZlcmVudGlhdGVkIHVzZXJzIGNvbnN1bXB0aW9uDQo+ICAgIHN0eWxlLiAgVGhpcyBjYW4gYmUg
YWNoaWV2ZWQgdGhyb3VnaCBoYXZpbmc6IChpKSBhIGtub3dsZWRnZSBpbiB0aGUNCj4gICAgbmV0
d29yayBhbmQgc2VydmljZSBwbGF0Zm9ybSBhYm91dCB0aGUgYXZhaWxhYmxlIGRldmljZSBhbmQg
bmV0d29yaw0KPiAgICBjb25kaXRpb25zIGZvciB0aGUgZW5kLXVzZXIgYW5kIChpaSkgYSBrbm93
bGVkZ2UgaW4gdGhlIG5ldHdvcmsgYWJvdXQNCj4gICAgdGhlIGNvbnRlbnQgcmVxdWlyZW1lbnRz
IGluIHRlcm1zIG9mIGRldmljZXMgY2FwYWJpbGl0aWVzIGFuZCBuZXR3b3JrDQo+ICAgIHJlc291
cmNlcyBmb3IgY29udGVudCBzdG9yZWQgZWl0aGVyIGluIHRoZSBuZXR3b3JrIG9yIGluIHRoZQ0K
PiAgICBhcHBsaWNhdGlvbiBzZXJ2ZXIuICBUbyBvYnRhaW4gc3VjaCBrbm93bGVkZ2Ugd2l0aCBu
byBuZWVkIGZvcg0KPiAgICBjaGFuZ2luZyB0aGUgY3VycmVudCBpbmZyYXN0cnVjdHVyZSBhbmQg
aW4gYSBnZW5lcmFsaXplZCB3YXkgdG8gYWxsDQo+ICAgIGFwcGxpY2F0aW9ucywgZmVlZGJhY2sv
bm90aWZpY2F0aW9uIG1lY2hhbmlzbXMgYmV0d2VlbiB0aGUgZW5kLXVzZXINCj4gICAgYXBwbGlj
YXRpb24sIHRoZSBuZXR3b3JrIGFuZCB0aGUgc2VydmljZSBwbGF0Zm9ybSBpcyBuZWVkZWQgdG8N
Cj4gICAgcHJvdmlkZSBpbmZvcm1hdGlvbiBoZWxwaW5nIHRoZSBjb250ZW50IGRlbGl2ZXJ5IGFu
ZCBhZGFwdGF0aW9uDQo+ICAgIGRlY2lzaW9ucy4gIFRoaXMgZG9jdW1lbnQgaXMgaW52ZXN0aWdh
dGluZyBzdWNoIGFwcGxpY2F0aW9uLWFnbm9zdGljDQo+ICAgIHRyYWNrLg0KPiANCj4gICAgVGhp
cyBkb2N1bWVudCBleHRlbmRzIHRoZSBQb3J0IENvbnRyb2wgUHJvdG9jb2wgKFBDUCkgUkZDIDY4
ODcNCj4gICAgW1JGQzY4ODddIHRvIGFsbG93OiAoaSkgdGhlIHVzZXJzIGFwcGxpY2F0aW9uIHRv
IG5vdGlmeSB0aGUgbmV0d29yaw0KPiAgICBhbmQgYXBwbGljYXRpb24gc2VydmVyIGFib3V0IGl0
cyBhdmFpbGFibGUgcmVzb3VyY2VzIGluIHRlcm1zIG9mDQo+ICAgIGRldmljZXMgY2FwYWJpbGl0
aWVzIGFuZCBuZXR3b3JrIGNvbmRpdGlvbnMgYXMgd2VsbCBhcyBpbmZvcm1hdGlvbg0KPiAgICBh
Ym91dCB0aGUgdXNlciAoZS5nLiwgbG9jYXRpb24sIG1vYmlsaXR5IHN0YXR1cykgYW5kIChpaSkg
dGhlDQo+ICAgIGFwcGxpY2F0aW9uIHNlcnZlciB0byBub3RpZnkgdGhlIG5ldHdvcmsgYWJvdXQg
dGhlIHJlcXVpcmVtZW50cyBvZg0KPiAgICB0aGUgY29udGVudCBpdCBzdG9yZXMgaW4gdGVybXMg
b2YgZGV2aWNlcyBhbmQgbmV0d29yayByZXNvdXJjZXMuICBBDQo+ICAgIG5ldyBQQ1Agb3B0aW9u
LCBkZW5vdGVkIHRoZSBGRUVEQkFDSywgaXMgc3BlY2lmaWVkIHRvIGFsbG93IHN1Y2gNCj4gICAg
ZmVlZGJhY2sgbm90aWZpY2F0aW9uIHNpZ25hbGluZy4gIFRoaXMgb3B0aW9uIGlzIHVzZWQgd2l0
aCBib3RoIFBFRVINCj4gICAgYW5kIE1BUCBPcGNvZGVzLg0KPiANCj4gDQo+IA0KPiANCj4gUGxl
YXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20gdGhlIHRp
bWUgb2YgDQo+IHN1Ym1pc3Npb24gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYg
YXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCj4gDQo+IFRoZSBJRVRGIFNlY3JldGFy
aWF0DQoNCg==

From eckelcu@cisco.com  Wed Nov  6 14:40:30 2013
Return-Path: <eckelcu@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E54B21E81A8 for <pcp@ietfa.amsl.com>; Wed,  6 Nov 2013 14:40:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w-sOs8GxO-32 for <pcp@ietfa.amsl.com>; Wed,  6 Nov 2013 14:40:00 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id C785921E8155 for <pcp@ietf.org>; Wed,  6 Nov 2013 14:39:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9807; q=dns/txt; s=iport; t=1383777587; x=1384987187; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=1tqeFrGvzZtX/QZt5EqL4BG2V+4BgHj6skaO06xgJ1Y=; b=jVjdl2mMNJk19KhIeMXNEWWvux+hpBuuqknUOLUjiBxH5WBvdB090ddr zpVCOZ/JIPq8Xk55Gm3SAtiJHAM0hs9v1xP9EEXZLDeP5OH/rsS4Ph2yX S1IL54/P92aVfhQ5ju+b7nmaieFypO7agFohjTbcyHicYcZSx6Jsnvyyh 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0GAOnDelKtJXG//2dsb2JhbABbgwc4TQa/LYEmFnSCJQEBAQMBAQEBNzQLBQcGAQgRBAEBHwkuCxQJCAIEAQ0FCYdyBggFvwWOCoFPBwaEKgOYDIEviyaFNYMmgio
X-IronPort-AV: E=Sophos;i="4.93,647,1378857600"; d="scan'208";a="281464809"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-1.cisco.com with ESMTP; 06 Nov 2013 22:39:46 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id rA6MdjkA003103 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 6 Nov 2013 22:39:45 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.191]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0123.003; Wed, 6 Nov 2013 16:39:45 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: AQHO20EX7aeWR5gOw0WyYbyjnfhkfQ==
Date: Wed, 6 Nov 2013 22:39:45 +0000
Message-ID: <CEA003BD.144DB%eckelcu@cisco.com>
In-Reply-To: <F893BEC192403B489DBA38999068CF19059498E0@ORSMSX102.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.115.31]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F678A61D3FAD92499DBED6E9574DECC2@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2013 22:40:30 -0000

On 11/5/13 9:55 PM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com> wrote:

>Thanks Tiru for your comments.
>Please find my answers:
>1) If the client learns that the battery conditions, light levels have
>changed -
>a) why can't the client request subsequent chunk with different encoding
>from the URL in the manifest file ?
>b) why can't the client be intelligent enough to pick the subsequent
>chunk with appropriate bit-rate based on endpoint device conditions ?
>
>Hassnaa: this is possible for HTTP adaptive streaming where the client
>controls the video selection, but could not be done in RTP video
>streaming and video conferencing applications in which the server should
>take the adaptation decision based on some information known from the
>client.

For RTP traffic, using RTCP tmmbr seems an appropriate alternative.

Cheers,
Charles
=20
> And even for HTTP adaptive streaming, the client does not have a full
>view of the network (but only the throughput for his connectivity) and if
>the adaptation is done by the network itself it will consider the global
>bandwidth.
>
>2) use case in section 3.2 of the draft; uCDN (upstream CDN) based on
>location of the client and other parameters queries available dCDN
>(Downstream CDN) to selects the dCDN for serving content to the client.
>How is FEEDBACK option useful with uCDN/dCDN ?
>
>Hassnaa: This use-case in this current version of the draft does not
>consider CDN-I (CDN Interco) but it is a very good point to consider a
>use-case doe CDN-I in the next version of the draft. What the current
>use-case considers is simply a controller node that controls the multiple
>Application servers in the service platform. And here the feedback option
>is useful as it allows the controller to do a selection of the
>application server having content matching the "user location looking for
>proximity, user devices resources that are available, .."
>
>
>Hope that this clarifies your questions and looking forward to more
>discussion.
>
>Regards,
>Hassnaa
>
>-----Original Message-----
>From: Tirumaleswar Reddy (tireddy) [mailto:tireddy@cisco.com]
>Sent: Tuesday, November 05, 2013 7:58 PM
>To: Moustafa, Hassnaa; pcp@ietf.org
>Cc: Moses, Danny
>Subject: RE: [pcp] New Submission:
>draft-mou-pcp-application-network-feedback-00.txt
>
>Hi,
>
>My initial comments:
>
>1) If the client learns that the battery conditions, light levels have
>changed -
>a) why can't the client request subsequent chunk with different encoding
>from the URL in the manifest file ?
>b) why can't the client be intelligent enough to pick the subsequent
>chunk with appropriate bit-rate based on endpoint device conditions ?
>
>2) use case in section 3.2 of the draft; uCDN (upstream CDN) based on
>location of the client and other parameters queries available dCDN
>(Downstream CDN) to selects the dCDN for serving content to the client.
>
>How is FEEDBACK option useful with uCDN/dCDN ?
>
>-Tiru.
>
>> -----Original Message-----
>> From: Moustafa, Hassnaa [mailto:hassnaa.moustafa@intel.com]
>> Sent: Monday, November 04, 2013 6:33 PM
>> To: pcp@ietf.org
>> Cc: Moses, Danny
>> Subject: [pcp] New Submission:
>> draft-mou-pcp-application-network-feedback-
>> 00.txt
>>=20
>> Hi All,
>>=20
>> Draft (draft-mou-pcp-application-network-feedback) is a new draft that
>> is submitted today on (PCP Extension for Signaling Feedback
>> Information from the End-User Application to the Application Sever and
>>to the Network).
>>=20
>> The draft is available at :             http://www.ietf.org/internet-
>> drafts/draft-mou-pcp-application-network-feedback-00.txt
>>=20
>> This draft addresses the need for more intelligence in the network and
>> service infrastructure for better content delivery to optimize the
>> network and devices resources. In this view, the draft proposes using
>> PCP to signal information
>> for: i)  Knowledge in the network and service platform about the
>> available device and network conditions for the end-user and ii)
>> Knowledge in the network about the content requirements in terms of
>> devices and  network resources for content stored either in the
>> network or in the application server.
>>=20
>> The abstract of the draft is as follows:
>> " Abstract:    Nowadays users consumption style for video and multimedia
>> applications is strongly changing.  Users are heavily counting on
>> wireless and mobile devices for video streaming and interactive video
>>    and multimedia applications.  This can be implemented for instance
>> by having more intelligence in the service and the network
>> infrastructure to better suit a differentiated users consumption
>>style.  This can be achieved
>>    through having: (i) a knowledge in the network and service platform
>> about the available device and network conditions for the end-user and
>> (ii) a knowledge in the network about the content requirements in terms
>>of devices
>>    capabilities and network resources for content stored either in the
>> network or in the application server.  To obtain such knowledge with
>> no need for changing the current infrastructure and in a generalized
>>way to all
>>    applications, feedback/notification mechanisms between the end-user
>> application, the network and the service platform is needed to provide
>> information helping the content delivery and adaptation decisions.
>> This document
>>     is investigating such application-agnostic track.
>>=20
>>    This document extends the Port Control Protocol (PCP) RFC 6887
>> [RFC6887] to allow: (i) the users application to notify the network
>> and application server about its available resources in terms of
>>    devices capabilities and network conditions as well as information
>> about the user (e.g., location, mobility status) and (ii) the
>> application server to notify the network about the requirements of
>>    the content it stores in terms of devices and network resources.  A
>> new PCP option, denoted the FEEDBACK, is specified to allow such
>> feedback notification signaling.  This option is used with both PEER
>>    and MAP Opcodes."
>>=20
>> Looking forward to having your feedback and more discussion on this
>>draft.
>>=20
>> Regards,
>> Hassnaa
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Monday, November 04, 2013 4:06 AM
>> To: Mohamed Boucadair; Moustafa, Hassnaa; Moses, Danny
>> Subject: New Version Notification for
>> draft-mou-pcp-application-network-
>> feedback-00.txt
>>=20
>>=20
>> A new version of I-D,
>> draft-mou-pcp-application-network-feedback-00.txt
>> has been successfully submitted by Hassnaa Moustafa and posted to the
>> IETF repository.
>>=20
>> Filename:	 draft-mou-pcp-application-network-feedback
>> Revision:	 00
>> Title:		 PCP Extension for Signaling Feedback Information from the End-
>> User Application to the Application Sever and to the Network
>> Creation date:	 2013-11-04
>> Group:		 Individual Submission
>> Number of pages: 14
>> URL:             http://www.ietf.org/internet-drafts/draft-mou-pcp-
>> application-network-feedback-00.txt
>> Status:        =20
>>http://datatracker.ietf.org/doc/draft-mou-pcp-application-
>> network-feedback
>> Htmlized:      =20
>>http://tools.ietf.org/html/draft-mou-pcp-application-network-
>> feedback-00
>>=20
>>=20
>> Abstract:
>>    Nowadays users consumption style for video and multimedia
>>    applications is strongly changing.  Users are heavily counting on
>>    wireless and mobile devices for video streaming and interactive video
>>    and multimedia applications.  This can be implemented for instance by
>>    having more intelligence in the service and the network
>>    infrastructure to better suit a differentiated users consumption
>>    style.  This can be achieved through having: (i) a knowledge in the
>>    network and service platform about the available device and network
>>    conditions for the end-user and (ii) a knowledge in the network about
>>    the content requirements in terms of devices capabilities and network
>>    resources for content stored either in the network or in the
>>    application server.  To obtain such knowledge with no need for
>>    changing the current infrastructure and in a generalized way to all
>>    applications, feedback/notification mechanisms between the end-user
>>    application, the network and the service platform is needed to
>>    provide information helping the content delivery and adaptation
>>    decisions.  This document is investigating such application-agnostic
>>    track.
>>=20
>>    This document extends the Port Control Protocol (PCP) RFC 6887
>>    [RFC6887] to allow: (i) the users application to notify the network
>>    and application server about its available resources in terms of
>>    devices capabilities and network conditions as well as information
>>    about the user (e.g., location, mobility status) and (ii) the
>>    application server to notify the network about the requirements of
>>    the content it stores in terms of devices and network resources.  A
>>    new PCP option, denoted the FEEDBACK, is specified to allow such
>>    feedback notification signaling.  This option is used with both PEER
>>    and MAP Opcodes.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of
>> submission until the htmlized version and diff are available at
>>tools.ietf.org.
>>=20
>> The IETF Secretariat
>
>_______________________________________________
>pcp mailing list
>pcp@ietf.org
>https://www.ietf.org/mailman/listinfo/pcp


From hassnaa.moustafa@intel.com  Wed Nov  6 14:42:54 2013
Return-Path: <hassnaa.moustafa@intel.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 256E121E808A for <pcp@ietfa.amsl.com>; Wed,  6 Nov 2013 14:42:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.024
X-Spam-Level: 
X-Spam-Status: No, score=-10.024 tagged_above=-999 required=5 tests=[AWL=0.575, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3qOLHsrqYpB for <pcp@ietfa.amsl.com>; Wed,  6 Nov 2013 14:42:46 -0800 (PST)
Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by ietfa.amsl.com (Postfix) with ESMTP id 5F55721E80C7 for <pcp@ietf.org>; Wed,  6 Nov 2013 14:42:43 -0800 (PST)
Received: from azsmga002.ch.intel.com ([10.2.17.35]) by azsmga101.ch.intel.com with ESMTP; 06 Nov 2013 14:42:42 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.93,535,1378882800"; d="scan'208";a="317943966"
Received: from orsmsx106.amr.corp.intel.com ([10.22.225.133]) by AZSMGA002.ch.intel.com with ESMTP; 06 Nov 2013 14:42:41 -0800
Received: from orsmsx102.amr.corp.intel.com ([169.254.1.203]) by ORSMSX106.amr.corp.intel.com ([169.254.5.158]) with mapi id 14.03.0123.003; Wed, 6 Nov 2013 14:42:41 -0800
From: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: AQHO20EX7aeWR5gOw0WyYbyjnfhkfZoYy+UA
Date: Wed, 6 Nov 2013 22:42:40 +0000
Message-ID: <F893BEC192403B489DBA38999068CF1905949F31@ORSMSX102.amr.corp.intel.com>
References: <F893BEC192403B489DBA38999068CF19059498E0@ORSMSX102.amr.corp.intel.com> <CEA003BD.144DB%eckelcu@cisco.com>
In-Reply-To: <CEA003BD.144DB%eckelcu@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.22.254.140]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2013 22:42:56 -0000

Hi Charles,

But how to let RTP intercepted by middle nodes in the network? The main ide=
a behind this draft is looking for a signaling mechanism that can push feed=
back information into the network by the end-user application and by the se=
rvice platform.

Looking forward to more discussions.

Regards,
Hassnaa
-----Original Message-----
From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]=20
Sent: Wednesday, November 06, 2013 2:40 PM
To: Moustafa, Hassnaa; Tirumaleswar Reddy (tireddy); pcp@ietf.org
Cc: Moses, Danny
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

On 11/5/13 9:55 PM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com> wrote:

>Thanks Tiru for your comments.
>Please find my answers:
>1) If the client learns that the battery conditions, light levels have=20
>changed -
>a) why can't the client request subsequent chunk with different=20
>encoding from the URL in the manifest file ?
>b) why can't the client be intelligent enough to pick the subsequent=20
>chunk with appropriate bit-rate based on endpoint device conditions ?
>
>Hassnaa: this is possible for HTTP adaptive streaming where the client=20
>controls the video selection, but could not be done in RTP video=20
>streaming and video conferencing applications in which the server=20
>should take the adaptation decision based on some information known=20
>from the client.

For RTP traffic, using RTCP tmmbr seems an appropriate alternative.

Cheers,
Charles
=20
> And even for HTTP adaptive streaming, the client does not have a full=20
>view of the network (but only the throughput for his connectivity) and=20
>if the adaptation is done by the network itself it will consider the=20
>global bandwidth.
>
>2) use case in section 3.2 of the draft; uCDN (upstream CDN) based on=20
>location of the client and other parameters queries available dCDN=20
>(Downstream CDN) to selects the dCDN for serving content to the client.
>How is FEEDBACK option useful with uCDN/dCDN ?
>
>Hassnaa: This use-case in this current version of the draft does not=20
>consider CDN-I (CDN Interco) but it is a very good point to consider a=20
>use-case doe CDN-I in the next version of the draft. What the current=20
>use-case considers is simply a controller node that controls the=20
>multiple Application servers in the service platform. And here the=20
>feedback option is useful as it allows the controller to do a selection=20
>of the application server having content matching the "user location=20
>looking for proximity, user devices resources that are available, .."
>
>
>Hope that this clarifies your questions and looking forward to more=20
>discussion.
>
>Regards,
>Hassnaa
>
>-----Original Message-----
>From: Tirumaleswar Reddy (tireddy) [mailto:tireddy@cisco.com]
>Sent: Tuesday, November 05, 2013 7:58 PM
>To: Moustafa, Hassnaa; pcp@ietf.org
>Cc: Moses, Danny
>Subject: RE: [pcp] New Submission:
>draft-mou-pcp-application-network-feedback-00.txt
>
>Hi,
>
>My initial comments:
>
>1) If the client learns that the battery conditions, light levels have=20
>changed -
>a) why can't the client request subsequent chunk with different=20
>encoding from the URL in the manifest file ?
>b) why can't the client be intelligent enough to pick the subsequent=20
>chunk with appropriate bit-rate based on endpoint device conditions ?
>
>2) use case in section 3.2 of the draft; uCDN (upstream CDN) based on=20
>location of the client and other parameters queries available dCDN=20
>(Downstream CDN) to selects the dCDN for serving content to the client.
>
>How is FEEDBACK option useful with uCDN/dCDN ?
>
>-Tiru.
>
>> -----Original Message-----
>> From: Moustafa, Hassnaa [mailto:hassnaa.moustafa@intel.com]
>> Sent: Monday, November 04, 2013 6:33 PM
>> To: pcp@ietf.org
>> Cc: Moses, Danny
>> Subject: [pcp] New Submission:
>> draft-mou-pcp-application-network-feedback-
>> 00.txt
>>=20
>> Hi All,
>>=20
>> Draft (draft-mou-pcp-application-network-feedback) is a new draft=20
>>that  is submitted today on (PCP Extension for Signaling Feedback =20
>>Information from the End-User Application to the Application Sever and=20
>>to the Network).
>>=20
>> The draft is available at :             http://www.ietf.org/internet-
>> drafts/draft-mou-pcp-application-network-feedback-00.txt
>>=20
>> This draft addresses the need for more intelligence in the network=20
>> and service infrastructure for better content delivery to optimize=20
>> the network and devices resources. In this view, the draft proposes=20
>> using PCP to signal information
>> for: i)  Knowledge in the network and service platform about the=20
>> available device and network conditions for the end-user and ii)=20
>> Knowledge in the network about the content requirements in terms of=20
>> devices and  network resources for content stored either in the=20
>> network or in the application server.
>>=20
>> The abstract of the draft is as follows:
>> " Abstract:    Nowadays users consumption style for video and multimedia
>> applications is strongly changing.  Users are heavily counting on =20
>>wireless and mobile devices for video streaming and interactive video
>>    and multimedia applications.  This can be implemented for instance =20
>>by having more intelligence in the service and the network =20
>>infrastructure to better suit a differentiated users consumption=20
>>style.  This can be achieved
>>    through having: (i) a knowledge in the network and service=20
>>platform  about the available device and network conditions for the=20
>>end-user and
>> (ii) a knowledge in the network about the content requirements in=20
>>terms of devices
>>    capabilities and network resources for content stored either in=20
>>the  network or in the application server.  To obtain such knowledge=20
>>with  no need for changing the current infrastructure and in a=20
>>generalized way to all
>>    applications, feedback/notification mechanisms between the=20
>>end-user  application, the network and the service platform is needed=20
>>to provide  information helping the content delivery and adaptation decis=
ions.
>> This document
>>     is investigating such application-agnostic track.
>>=20
>>    This document extends the Port Control Protocol (PCP) RFC 6887=20
>> [RFC6887] to allow: (i) the users application to notify the network=20
>> and application server about its available resources in terms of
>>    devices capabilities and network conditions as well as information=20
>> about the user (e.g., location, mobility status) and (ii) the=20
>> application server to notify the network about the requirements of
>>    the content it stores in terms of devices and network resources. =20
>> A new PCP option, denoted the FEEDBACK, is specified to allow such=20
>> feedback notification signaling.  This option is used with both PEER
>>    and MAP Opcodes."
>>=20
>> Looking forward to having your feedback and more discussion on this=20
>>draft.
>>=20
>> Regards,
>> Hassnaa
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Monday, November 04, 2013 4:06 AM
>> To: Mohamed Boucadair; Moustafa, Hassnaa; Moses, Danny
>> Subject: New Version Notification for
>> draft-mou-pcp-application-network-
>> feedback-00.txt
>>=20
>>=20
>> A new version of I-D,
>> draft-mou-pcp-application-network-feedback-00.txt
>> has been successfully submitted by Hassnaa Moustafa and posted to the=20
>> IETF repository.
>>=20
>> Filename:	 draft-mou-pcp-application-network-feedback
>> Revision:	 00
>> Title:		 PCP Extension for Signaling Feedback Information from the End-
>> User Application to the Application Sever and to the Network
>> Creation date:	 2013-11-04
>> Group:		 Individual Submission
>> Number of pages: 14
>> URL:             http://www.ietf.org/internet-drafts/draft-mou-pcp-
>> application-network-feedback-00.txt
>> Status:        =20
>>http://datatracker.ietf.org/doc/draft-mou-pcp-application-
>> network-feedback
>> Htmlized:      =20
>>http://tools.ietf.org/html/draft-mou-pcp-application-network-
>> feedback-00
>>=20
>>=20
>> Abstract:
>>    Nowadays users consumption style for video and multimedia
>>    applications is strongly changing.  Users are heavily counting on
>>    wireless and mobile devices for video streaming and interactive video
>>    and multimedia applications.  This can be implemented for instance by
>>    having more intelligence in the service and the network
>>    infrastructure to better suit a differentiated users consumption
>>    style.  This can be achieved through having: (i) a knowledge in the
>>    network and service platform about the available device and network
>>    conditions for the end-user and (ii) a knowledge in the network about
>>    the content requirements in terms of devices capabilities and network
>>    resources for content stored either in the network or in the
>>    application server.  To obtain such knowledge with no need for
>>    changing the current infrastructure and in a generalized way to all
>>    applications, feedback/notification mechanisms between the end-user
>>    application, the network and the service platform is needed to
>>    provide information helping the content delivery and adaptation
>>    decisions.  This document is investigating such application-agnostic
>>    track.
>>=20
>>    This document extends the Port Control Protocol (PCP) RFC 6887
>>    [RFC6887] to allow: (i) the users application to notify the network
>>    and application server about its available resources in terms of
>>    devices capabilities and network conditions as well as information
>>    about the user (e.g., location, mobility status) and (ii) the
>>    application server to notify the network about the requirements of
>>    the content it stores in terms of devices and network resources.  A
>>    new PCP option, denoted the FEEDBACK, is specified to allow such
>>    feedback notification signaling.  This option is used with both PEER
>>    and MAP Opcodes.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of =20
>>submission until the htmlized version and diff are available at=20
>>tools.ietf.org.
>>=20
>> The IETF Secretariat
>
>_______________________________________________
>pcp mailing list
>pcp@ietf.org
>https://www.ietf.org/mailman/listinfo/pcp


From versteb@cisco.com  Wed Nov  6 14:53:26 2013
Return-Path: <versteb@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E29D021E8159 for <pcp@ietfa.amsl.com>; Wed,  6 Nov 2013 14:53:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.449
X-Spam-Level: 
X-Spam-Status: No, score=-9.449 tagged_above=-999 required=5 tests=[AWL=1.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Luf2Mv62hdL5 for <pcp@ietfa.amsl.com>; Wed,  6 Nov 2013 14:53:21 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id DF01A21E812A for <pcp@ietf.org>; Wed,  6 Nov 2013 14:53:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12353; q=dns/txt; s=iport; t=1383778401; x=1384988001; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=6ioPTgf7IfGNgHVAwUxdgEjXRftOeoFtlkgb8LfiWyk=; b=MSW8xWimQOLNTYt2YA51ntgYf9Wd9w+P8O6dzot+Py1YsdaAQOLo+Bzw eTRxm8+Hwpkp6Q8Q79ONGbP8u893OCO4bGB645JcF5Qu+EmfhDriYgaE+ McxKTu4Bpf6W1Unjkn9+nCcGB75pCrxtJVLLWfuWN13v2CPA7TguoYObz 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4GADHHelKtJV2d/2dsb2JhbABbgwc4TQa/LYEnFnSCJQEBAQMBAQEBNzQLBQcEAgEIEQQBAQsUCQcnCxQJCAIEAQ0FCAGHcgYIBb8LjgqBHjEHBoMagRADmTuLJoU1gyaCKg
X-IronPort-AV: E=Sophos;i="4.93,647,1378857600"; d="scan'208";a="281666102"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-5.cisco.com with ESMTP; 06 Nov 2013 22:53:20 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id rA6MrJnb005485 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 6 Nov 2013 22:53:19 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.196]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.03.0123.003; Wed, 6 Nov 2013 16:53:19 -0600
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: AQHO20FA3qQ5kE8Dck6wfwgBNXLH8ZoZMREA//+cYDA=
Date: Wed, 6 Nov 2013 22:53:18 +0000
Message-ID: <AE7F97DB5FEE054088D82E836BD15BE920137BF3@xmb-aln-x05.cisco.com>
References: <F893BEC192403B489DBA38999068CF19059498E0@ORSMSX102.amr.corp.intel.com> <CEA003BD.144DB%eckelcu@cisco.com> <F893BEC192403B489DBA38999068CF1905949F31@ORSMSX102.amr.corp.intel.com>
In-Reply-To: <F893BEC192403B489DBA38999068CF1905949F31@ORSMSX102.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.97.111]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2013 22:53:27 -0000

The network has use for flow metadata that is abstract enough to be useful =
to the network. Things like target bandwidth, requirements for delay/loss/j=
itter and the like seem to be interesting to the network.=20

The application-specific details like screen size, light level, weight of t=
he device do not have any apparent use. If the network is aware of the targ=
et bandwidth, desired delay/loss/jitter, what additional functionality is e=
nabled by having the network (as opposed to the hosts) knowing the light le=
vel ?

Once again, the client and the server have a different set of requirements =
in this area than the network. The bulk of the information should flow opaq=
uely between the client and the server. Only the information that is useful=
 to the network should be exposed to the network. There are complexity reas=
ons for this, security/privacy reasons for this, efficiency reasons, and ju=
st good layering techniques.

I am not arguing against flow and network metadata - just that we need to d=
efine a pretty concise set of metadata. The metadata definition methods nee=
d to be extensible to cover emerging requirements, but IMHO the initial def=
inition of the data conveyed should be quite constrained.

Bvs



-----Original Message-----
From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of Moust=
afa, Hassnaa
Sent: Wednesday, November 06, 2013 2:43 PM
To: Charles Eckel (eckelcu); Tirumaleswar Reddy (tireddy); pcp@ietf.org
Cc: Moses, Danny
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

Hi Charles,

But how to let RTP intercepted by middle nodes in the network? The main ide=
a behind this draft is looking for a signaling mechanism that can push feed=
back information into the network by the end-user application and by the se=
rvice platform.

Looking forward to more discussions.

Regards,
Hassnaa
-----Original Message-----
From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
Sent: Wednesday, November 06, 2013 2:40 PM
To: Moustafa, Hassnaa; Tirumaleswar Reddy (tireddy); pcp@ietf.org
Cc: Moses, Danny
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

On 11/5/13 9:55 PM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com> wrote:

>Thanks Tiru for your comments.
>Please find my answers:
>1) If the client learns that the battery conditions, light levels have=20
>changed -
>a) why can't the client request subsequent chunk with different=20
>encoding from the URL in the manifest file ?
>b) why can't the client be intelligent enough to pick the subsequent=20
>chunk with appropriate bit-rate based on endpoint device conditions ?
>
>Hassnaa: this is possible for HTTP adaptive streaming where the client=20
>controls the video selection, but could not be done in RTP video=20
>streaming and video conferencing applications in which the server=20
>should take the adaptation decision based on some information known=20
>from the client.

For RTP traffic, using RTCP tmmbr seems an appropriate alternative.

Cheers,
Charles
=20
> And even for HTTP adaptive streaming, the client does not have a full=20
>view of the network (but only the throughput for his connectivity) and=20
>if the adaptation is done by the network itself it will consider the=20
>global bandwidth.
>
>2) use case in section 3.2 of the draft; uCDN (upstream CDN) based on=20
>location of the client and other parameters queries available dCDN=20
>(Downstream CDN) to selects the dCDN for serving content to the client.
>How is FEEDBACK option useful with uCDN/dCDN ?
>
>Hassnaa: This use-case in this current version of the draft does not=20
>consider CDN-I (CDN Interco) but it is a very good point to consider a=20
>use-case doe CDN-I in the next version of the draft. What the current=20
>use-case considers is simply a controller node that controls the=20
>multiple Application servers in the service platform. And here the=20
>feedback option is useful as it allows the controller to do a selection=20
>of the application server having content matching the "user location=20
>looking for proximity, user devices resources that are available, .."
>
>
>Hope that this clarifies your questions and looking forward to more=20
>discussion.
>
>Regards,
>Hassnaa
>
>-----Original Message-----
>From: Tirumaleswar Reddy (tireddy) [mailto:tireddy@cisco.com]
>Sent: Tuesday, November 05, 2013 7:58 PM
>To: Moustafa, Hassnaa; pcp@ietf.org
>Cc: Moses, Danny
>Subject: RE: [pcp] New Submission:
>draft-mou-pcp-application-network-feedback-00.txt
>
>Hi,
>
>My initial comments:
>
>1) If the client learns that the battery conditions, light levels have=20
>changed -
>a) why can't the client request subsequent chunk with different=20
>encoding from the URL in the manifest file ?
>b) why can't the client be intelligent enough to pick the subsequent=20
>chunk with appropriate bit-rate based on endpoint device conditions ?
>
>2) use case in section 3.2 of the draft; uCDN (upstream CDN) based on=20
>location of the client and other parameters queries available dCDN=20
>(Downstream CDN) to selects the dCDN for serving content to the client.
>
>How is FEEDBACK option useful with uCDN/dCDN ?
>
>-Tiru.
>
>> -----Original Message-----
>> From: Moustafa, Hassnaa [mailto:hassnaa.moustafa@intel.com]
>> Sent: Monday, November 04, 2013 6:33 PM
>> To: pcp@ietf.org
>> Cc: Moses, Danny
>> Subject: [pcp] New Submission:
>> draft-mou-pcp-application-network-feedback-
>> 00.txt
>>=20
>> Hi All,
>>=20
>> Draft (draft-mou-pcp-application-network-feedback) is a new draft=20
>>that  is submitted today on (PCP Extension for Signaling Feedback=20
>>Information from the End-User Application to the Application Sever and=20
>>to the Network).
>>=20
>> The draft is available at :             http://www.ietf.org/internet-
>> drafts/draft-mou-pcp-application-network-feedback-00.txt
>>=20
>> This draft addresses the need for more intelligence in the network=20
>> and service infrastructure for better content delivery to optimize=20
>> the network and devices resources. In this view, the draft proposes=20
>> using PCP to signal information
>> for: i)  Knowledge in the network and service platform about the=20
>> available device and network conditions for the end-user and ii)=20
>> Knowledge in the network about the content requirements in terms of=20
>> devices and  network resources for content stored either in the=20
>> network or in the application server.
>>=20
>> The abstract of the draft is as follows:
>> " Abstract:    Nowadays users consumption style for video and multimedia
>> applications is strongly changing.  Users are heavily counting on=20
>>wireless and mobile devices for video streaming and interactive video
>>    and multimedia applications.  This can be implemented for instance=20
>>by having more intelligence in the service and the network=20
>>infrastructure to better suit a differentiated users consumption=20
>>style.  This can be achieved
>>    through having: (i) a knowledge in the network and service=20
>>platform  about the available device and network conditions for the=20
>>end-user and
>> (ii) a knowledge in the network about the content requirements in=20
>>terms of devices
>>    capabilities and network resources for content stored either in=20
>>the  network or in the application server.  To obtain such knowledge=20
>>with  no need for changing the current infrastructure and in a=20
>>generalized way to all
>>    applications, feedback/notification mechanisms between the=20
>>end-user  application, the network and the service platform is needed=20
>>to provide  information helping the content delivery and adaptation decis=
ions.
>> This document
>>     is investigating such application-agnostic track.
>>=20
>>    This document extends the Port Control Protocol (PCP) RFC 6887=20
>> [RFC6887] to allow: (i) the users application to notify the network=20
>> and application server about its available resources in terms of
>>    devices capabilities and network conditions as well as information=20
>> about the user (e.g., location, mobility status) and (ii) the=20
>> application server to notify the network about the requirements of
>>    the content it stores in terms of devices and network resources. =20
>> A new PCP option, denoted the FEEDBACK, is specified to allow such=20
>> feedback notification signaling.  This option is used with both PEER
>>    and MAP Opcodes."
>>=20
>> Looking forward to having your feedback and more discussion on this=20
>>draft.
>>=20
>> Regards,
>> Hassnaa
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Monday, November 04, 2013 4:06 AM
>> To: Mohamed Boucadair; Moustafa, Hassnaa; Moses, Danny
>> Subject: New Version Notification for
>> draft-mou-pcp-application-network-
>> feedback-00.txt
>>=20
>>=20
>> A new version of I-D,
>> draft-mou-pcp-application-network-feedback-00.txt
>> has been successfully submitted by Hassnaa Moustafa and posted to the=20
>> IETF repository.
>>=20
>> Filename:	 draft-mou-pcp-application-network-feedback
>> Revision:	 00
>> Title:		 PCP Extension for Signaling Feedback Information from the End-
>> User Application to the Application Sever and to the Network
>> Creation date:	 2013-11-04
>> Group:		 Individual Submission
>> Number of pages: 14
>> URL:             http://www.ietf.org/internet-drafts/draft-mou-pcp-
>> application-network-feedback-00.txt
>> Status:        =20
>>http://datatracker.ietf.org/doc/draft-mou-pcp-application-
>> network-feedback
>> Htmlized:      =20
>>http://tools.ietf.org/html/draft-mou-pcp-application-network-
>> feedback-00
>>=20
>>=20
>> Abstract:
>>    Nowadays users consumption style for video and multimedia
>>    applications is strongly changing.  Users are heavily counting on
>>    wireless and mobile devices for video streaming and interactive video
>>    and multimedia applications.  This can be implemented for instance by
>>    having more intelligence in the service and the network
>>    infrastructure to better suit a differentiated users consumption
>>    style.  This can be achieved through having: (i) a knowledge in the
>>    network and service platform about the available device and network
>>    conditions for the end-user and (ii) a knowledge in the network about
>>    the content requirements in terms of devices capabilities and network
>>    resources for content stored either in the network or in the
>>    application server.  To obtain such knowledge with no need for
>>    changing the current infrastructure and in a generalized way to all
>>    applications, feedback/notification mechanisms between the end-user
>>    application, the network and the service platform is needed to
>>    provide information helping the content delivery and adaptation
>>    decisions.  This document is investigating such application-agnostic
>>    track.
>>=20
>>    This document extends the Port Control Protocol (PCP) RFC 6887
>>    [RFC6887] to allow: (i) the users application to notify the network
>>    and application server about its available resources in terms of
>>    devices capabilities and network conditions as well as information
>>    about the user (e.g., location, mobility status) and (ii) the
>>    application server to notify the network about the requirements of
>>    the content it stores in terms of devices and network resources.  A
>>    new PCP option, denoted the FEEDBACK, is specified to allow such
>>    feedback notification signaling.  This option is used with both PEER
>>    and MAP Opcodes.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of=20
>>submission until the htmlized version and diff are available at=20
>>tools.ietf.org.
>>=20
>> The IETF Secretariat
>
>_______________________________________________
>pcp mailing list
>pcp@ietf.org
>https://www.ietf.org/mailman/listinfo/pcp

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

From hassnaa.moustafa@intel.com  Wed Nov  6 15:05:51 2013
Return-Path: <hassnaa.moustafa@intel.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B0C911E80FA for <pcp@ietfa.amsl.com>; Wed,  6 Nov 2013 15:05:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XThOdrIbwDDS for <pcp@ietfa.amsl.com>; Wed,  6 Nov 2013 15:05:41 -0800 (PST)
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by ietfa.amsl.com (Postfix) with ESMTP id 1FC1811E80E3 for <pcp@ietf.org>; Wed,  6 Nov 2013 15:05:41 -0800 (PST)
Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 06 Nov 2013 15:05:40 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.93,535,1378882800"; d="scan'208";a="430973970"
Received: from orsmsx108.amr.corp.intel.com ([10.22.240.6]) by orsmga002.jf.intel.com with ESMTP; 06 Nov 2013 15:05:39 -0800
Received: from orsmsx102.amr.corp.intel.com ([169.254.1.203]) by ORSMSX108.amr.corp.intel.com ([169.254.4.149]) with mapi id 14.03.0123.003; Wed, 6 Nov 2013 15:05:39 -0800
From: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: AQHO20FA3qQ5kE8Dck6wfwgBNXLH8ZoZMREA//+cYDCAAALlkA==
Date: Wed, 6 Nov 2013 23:05:39 +0000
Message-ID: <F893BEC192403B489DBA38999068CF1905949F7D@ORSMSX102.amr.corp.intel.com>
References: <F893BEC192403B489DBA38999068CF19059498E0@ORSMSX102.amr.corp.intel.com> <CEA003BD.144DB%eckelcu@cisco.com> <F893BEC192403B489DBA38999068CF1905949F31@ORSMSX102.amr.corp.intel.com> <AE7F97DB5FEE054088D82E836BD15BE920137BF3@xmb-aln-x05.cisco.com>
In-Reply-To: <AE7F97DB5FEE054088D82E836BD15BE920137BF3@xmb-aln-x05.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.22.254.140]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2013 23:05:53 -0000

Hi Bill,
Thanks for your detailed feedback.
Please see inline my replies.

Regards,
Hassnaa

-----Original Message-----
From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]=20
Sent: Wednesday, November 06, 2013 2:53 PM
To: Moustafa, Hassnaa; Charles Eckel (eckelcu); Tirumaleswar Reddy (tireddy=
); pcp@ietf.org
Cc: Moses, Danny
Subject: RE: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

The network has use for flow metadata that is abstract enough to be useful =
to the network. Things like target bandwidth, requirements for delay/loss/j=
itter and the like seem to be interesting to the network.=20

Hassnaa: Yes, I agree. But this is mainly for the QoS management. What we a=
re looking for is QoE which requires more metadata than the target BW, dela=
y/loss/jitter. QoE related metadata needs to work with the QoS related meta=
data an does not mean to replace it.

The application-specific details like screen size, light level, weight of t=
he device do not have any apparent use. If the network is aware of the targ=
et bandwidth, desired delay/loss/jitter, what additional functionality is e=
nabled by having the network (as opposed to the hosts) knowing the light le=
vel ?

Hassnaa: it do has for QoE, and if the session time permits for the present=
ation of this draft, I will show some experimental results on that. The add=
itional functionality that could be in the network is "real-time transcodin=
g as a service function in the network". Light information can help here in=
 adapting the pixels luminance, but "light" is not the only metadata that w=
e are building this draft on it.

Once again, the client and the server have a different set of requirements =
in this area than the network. The bulk of the information should flow opaq=
uely between the client and the server. Only the information that is useful=
 to the network should be exposed to the network. There are complexity reas=
ons for this, security/privacy reasons for this, efficiency reasons, and ju=
st good layering techniques.


Hassnaa: Involving the network in the knowledge of information between the =
client and the server is promising in optimizing the video delivery, moneti=
zing bandwidth, having the operator control on their networks, better manag=
ement for QoS, ...As for security, security considerations for PCP applies,=
 that what is mentioned in the draft. And also if we think of the network m=
iddle boxes as entities owned by the operator, then there is much more trus=
t here and the same security (authentication policy) between the operator a=
nd the client should apply.



I am not arguing against flow and network metadata - just that we need to d=
efine a pretty concise set of metadata. The metadata definition methods nee=
d to be extensible to cover emerging requirements, but IMHO the initial def=
inition of the data conveyed should be quite constrained.

Hassnaa: I agree that there is a need to define a concise set for metadata =
and I am looking forward to more discussion in that direction.

Bvs



-----Original Message-----
From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of Moust=
afa, Hassnaa
Sent: Wednesday, November 06, 2013 2:43 PM
To: Charles Eckel (eckelcu); Tirumaleswar Reddy (tireddy); pcp@ietf.org
Cc: Moses, Danny
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

Hi Charles,

But how to let RTP intercepted by middle nodes in the network? The main ide=
a behind this draft is looking for a signaling mechanism that can push feed=
back information into the network by the end-user application and by the se=
rvice platform.

Looking forward to more discussions.

Regards,
Hassnaa
-----Original Message-----
From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
Sent: Wednesday, November 06, 2013 2:40 PM
To: Moustafa, Hassnaa; Tirumaleswar Reddy (tireddy); pcp@ietf.org
Cc: Moses, Danny
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

On 11/5/13 9:55 PM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com> wrote:

>Thanks Tiru for your comments.
>Please find my answers:
>1) If the client learns that the battery conditions, light levels have=20
>changed -
>a) why can't the client request subsequent chunk with different=20
>encoding from the URL in the manifest file ?
>b) why can't the client be intelligent enough to pick the subsequent=20
>chunk with appropriate bit-rate based on endpoint device conditions ?
>
>Hassnaa: this is possible for HTTP adaptive streaming where the client=20
>controls the video selection, but could not be done in RTP video=20
>streaming and video conferencing applications in which the server=20
>should take the adaptation decision based on some information known=20
>from the client.

For RTP traffic, using RTCP tmmbr seems an appropriate alternative.

Cheers,
Charles
=20
> And even for HTTP adaptive streaming, the client does not have a full=20
>view of the network (but only the throughput for his connectivity) and=20
>if the adaptation is done by the network itself it will consider the=20
>global bandwidth.
>
>2) use case in section 3.2 of the draft; uCDN (upstream CDN) based on=20
>location of the client and other parameters queries available dCDN=20
>(Downstream CDN) to selects the dCDN for serving content to the client.
>How is FEEDBACK option useful with uCDN/dCDN ?
>
>Hassnaa: This use-case in this current version of the draft does not=20
>consider CDN-I (CDN Interco) but it is a very good point to consider a=20
>use-case doe CDN-I in the next version of the draft. What the current=20
>use-case considers is simply a controller node that controls the=20
>multiple Application servers in the service platform. And here the=20
>feedback option is useful as it allows the controller to do a selection=20
>of the application server having content matching the "user location=20
>looking for proximity, user devices resources that are available, .."
>
>
>Hope that this clarifies your questions and looking forward to more=20
>discussion.
>
>Regards,
>Hassnaa
>
>-----Original Message-----
>From: Tirumaleswar Reddy (tireddy) [mailto:tireddy@cisco.com]
>Sent: Tuesday, November 05, 2013 7:58 PM
>To: Moustafa, Hassnaa; pcp@ietf.org
>Cc: Moses, Danny
>Subject: RE: [pcp] New Submission:
>draft-mou-pcp-application-network-feedback-00.txt
>
>Hi,
>
>My initial comments:
>
>1) If the client learns that the battery conditions, light levels have=20
>changed -
>a) why can't the client request subsequent chunk with different=20
>encoding from the URL in the manifest file ?
>b) why can't the client be intelligent enough to pick the subsequent=20
>chunk with appropriate bit-rate based on endpoint device conditions ?
>
>2) use case in section 3.2 of the draft; uCDN (upstream CDN) based on=20
>location of the client and other parameters queries available dCDN=20
>(Downstream CDN) to selects the dCDN for serving content to the client.
>
>How is FEEDBACK option useful with uCDN/dCDN ?
>
>-Tiru.
>
>> -----Original Message-----
>> From: Moustafa, Hassnaa [mailto:hassnaa.moustafa@intel.com]
>> Sent: Monday, November 04, 2013 6:33 PM
>> To: pcp@ietf.org
>> Cc: Moses, Danny
>> Subject: [pcp] New Submission:
>> draft-mou-pcp-application-network-feedback-
>> 00.txt
>>=20
>> Hi All,
>>=20
>> Draft (draft-mou-pcp-application-network-feedback) is a new draft=20
>>that  is submitted today on (PCP Extension for Signaling Feedback=20
>>Information from the End-User Application to the Application Sever and=20
>>to the Network).
>>=20
>> The draft is available at :             http://www.ietf.org/internet-
>> drafts/draft-mou-pcp-application-network-feedback-00.txt
>>=20
>> This draft addresses the need for more intelligence in the network=20
>> and service infrastructure for better content delivery to optimize=20
>> the network and devices resources. In this view, the draft proposes=20
>> using PCP to signal information
>> for: i)  Knowledge in the network and service platform about the=20
>> available device and network conditions for the end-user and ii)=20
>> Knowledge in the network about the content requirements in terms of=20
>> devices and  network resources for content stored either in the=20
>> network or in the application server.
>>=20
>> The abstract of the draft is as follows:
>> " Abstract:    Nowadays users consumption style for video and multimedia
>> applications is strongly changing.  Users are heavily counting on=20
>>wireless and mobile devices for video streaming and interactive video
>>    and multimedia applications.  This can be implemented for instance=20
>>by having more intelligence in the service and the network=20
>>infrastructure to better suit a differentiated users consumption=20
>>style.  This can be achieved
>>    through having: (i) a knowledge in the network and service=20
>>platform  about the available device and network conditions for the=20
>>end-user and
>> (ii) a knowledge in the network about the content requirements in=20
>>terms of devices
>>    capabilities and network resources for content stored either in=20
>>the  network or in the application server.  To obtain such knowledge=20
>>with  no need for changing the current infrastructure and in a=20
>>generalized way to all
>>    applications, feedback/notification mechanisms between the=20
>>end-user  application, the network and the service platform is needed=20
>>to provide  information helping the content delivery and adaptation decis=
ions.
>> This document
>>     is investigating such application-agnostic track.
>>=20
>>    This document extends the Port Control Protocol (PCP) RFC 6887=20
>> [RFC6887] to allow: (i) the users application to notify the network=20
>> and application server about its available resources in terms of
>>    devices capabilities and network conditions as well as information=20
>> about the user (e.g., location, mobility status) and (ii) the=20
>> application server to notify the network about the requirements of
>>    the content it stores in terms of devices and network resources. =20
>> A new PCP option, denoted the FEEDBACK, is specified to allow such=20
>> feedback notification signaling.  This option is used with both PEER
>>    and MAP Opcodes."
>>=20
>> Looking forward to having your feedback and more discussion on this=20
>>draft.
>>=20
>> Regards,
>> Hassnaa
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Monday, November 04, 2013 4:06 AM
>> To: Mohamed Boucadair; Moustafa, Hassnaa; Moses, Danny
>> Subject: New Version Notification for
>> draft-mou-pcp-application-network-
>> feedback-00.txt
>>=20
>>=20
>> A new version of I-D,
>> draft-mou-pcp-application-network-feedback-00.txt
>> has been successfully submitted by Hassnaa Moustafa and posted to the=20
>> IETF repository.
>>=20
>> Filename:	 draft-mou-pcp-application-network-feedback
>> Revision:	 00
>> Title:		 PCP Extension for Signaling Feedback Information from the End-
>> User Application to the Application Sever and to the Network
>> Creation date:	 2013-11-04
>> Group:		 Individual Submission
>> Number of pages: 14
>> URL:             http://www.ietf.org/internet-drafts/draft-mou-pcp-
>> application-network-feedback-00.txt
>> Status:        =20
>>http://datatracker.ietf.org/doc/draft-mou-pcp-application-
>> network-feedback
>> Htmlized:      =20
>>http://tools.ietf.org/html/draft-mou-pcp-application-network-
>> feedback-00
>>=20
>>=20
>> Abstract:
>>    Nowadays users consumption style for video and multimedia
>>    applications is strongly changing.  Users are heavily counting on
>>    wireless and mobile devices for video streaming and interactive video
>>    and multimedia applications.  This can be implemented for instance by
>>    having more intelligence in the service and the network
>>    infrastructure to better suit a differentiated users consumption
>>    style.  This can be achieved through having: (i) a knowledge in the
>>    network and service platform about the available device and network
>>    conditions for the end-user and (ii) a knowledge in the network about
>>    the content requirements in terms of devices capabilities and network
>>    resources for content stored either in the network or in the
>>    application server.  To obtain such knowledge with no need for
>>    changing the current infrastructure and in a generalized way to all
>>    applications, feedback/notification mechanisms between the end-user
>>    application, the network and the service platform is needed to
>>    provide information helping the content delivery and adaptation
>>    decisions.  This document is investigating such application-agnostic
>>    track.
>>=20
>>    This document extends the Port Control Protocol (PCP) RFC 6887
>>    [RFC6887] to allow: (i) the users application to notify the network
>>    and application server about its available resources in terms of
>>    devices capabilities and network conditions as well as information
>>    about the user (e.g., location, mobility status) and (ii) the
>>    application server to notify the network about the requirements of
>>    the content it stores in terms of devices and network resources.  A
>>    new PCP option, denoted the FEEDBACK, is specified to allow such
>>    feedback notification signaling.  This option is used with both PEER
>>    and MAP Opcodes.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of=20
>>submission until the htmlized version and diff are available at=20
>>tools.ietf.org.
>>=20
>> The IETF Secretariat
>
>_______________________________________________
>pcp mailing list
>pcp@ietf.org
>https://www.ietf.org/mailman/listinfo/pcp

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

From versteb@cisco.com  Wed Nov  6 15:24:46 2013
Return-Path: <versteb@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE36B21E8064 for <pcp@ietfa.amsl.com>; Wed,  6 Nov 2013 15:24:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XOpgseF5YMo9 for <pcp@ietfa.amsl.com>; Wed,  6 Nov 2013 15:24:42 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id AB90911E814F for <pcp@ietf.org>; Wed,  6 Nov 2013 15:24:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15447; q=dns/txt; s=iport; t=1383780281; x=1384989881; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=6iE3+fB1mlDAP5NzPMJe8xHdV5LAxFd/qwQeeppw61Q=; b=L4G4Tp/7K59LOF9EGuNx2oAVbfugGZ5M6cB6DQXWZ2FAPA6emJGMftWM Emyq3mfqSJyLbtwx8xX6SDi3yyL6anyB+O8pzhYNeccQn8zmlvS/OU6lh 5jKj8C4xFIl3C9vDLomuR4nMNIdhGS1ioTsUWMY6T5AbkyiMUqAWlqvOA 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4GAF7PelKtJV2Y/2dsb2JhbABbgwc4TQa/LIEnFnSCJQEBAQMBAQEBNzQLBQcEAgEIEQQBAQsUCQcnCxQJCAIEAQ0FCAGHcgYIBb8EjgqBHjEHBoMagRADmTuLJoU1gyaCKg
X-IronPort-AV: E=Sophos;i="4.93,647,1378857600"; d="scan'208";a="281676048"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-5.cisco.com with ESMTP; 06 Nov 2013 23:24:38 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rA6NObpZ022541 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 6 Nov 2013 23:24:37 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.196]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0123.003; Wed, 6 Nov 2013 17:24:37 -0600
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: AQHO20FA3qQ5kE8Dck6wfwgBNXLH8ZoZMREA//+cYDCAAALlkIAAAubw
Date: Wed, 6 Nov 2013 23:24:36 +0000
Message-ID: <AE7F97DB5FEE054088D82E836BD15BE920137D2B@xmb-aln-x05.cisco.com>
References: <F893BEC192403B489DBA38999068CF19059498E0@ORSMSX102.amr.corp.intel.com> <CEA003BD.144DB%eckelcu@cisco.com> <F893BEC192403B489DBA38999068CF1905949F31@ORSMSX102.amr.corp.intel.com> <AE7F97DB5FEE054088D82E836BD15BE920137BF3@xmb-aln-x05.cisco.com> <F893BEC192403B489DBA38999068CF1905949F7D@ORSMSX102.amr.corp.intel.com>
In-Reply-To: <F893BEC192403B489DBA38999068CF1905949F7D@ORSMSX102.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.97.111]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2013 23:24:47 -0000

In line with BVS -----

Bvs


-----Original Message-----
From: Moustafa, Hassnaa [mailto:hassnaa.moustafa@intel.com]=20
Sent: Wednesday, November 06, 2013 3:06 PM
To: Bill Ver Steeg (versteb); Charles Eckel (eckelcu); Tirumaleswar Reddy (=
tireddy); pcp@ietf.org
Cc: Moses, Danny
Subject: RE: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

Hi Bill,
Thanks for your detailed feedback.
Please see inline my replies.

Regards,
Hassnaa

-----Original Message-----
From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
Sent: Wednesday, November 06, 2013 2:53 PM
To: Moustafa, Hassnaa; Charles Eckel (eckelcu); Tirumaleswar Reddy (tireddy=
); pcp@ietf.org
Cc: Moses, Danny
Subject: RE: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

The network has use for flow metadata that is abstract enough to be useful =
to the network. Things like target bandwidth, requirements for delay/loss/j=
itter and the like seem to be interesting to the network.=20

Hassnaa: Yes, I agree. But this is mainly for the QoS management. What we a=
re looking for is QoE which requires more metadata than the target BW, dela=
y/loss/jitter. QoE related metadata needs to work with the QoS related meta=
data an does not mean to replace it.

The application-specific details like screen size, light level, weight of t=
he device do not have any apparent use. If the network is aware of the targ=
et bandwidth, desired delay/loss/jitter, what additional functionality is e=
nabled by having the network (as opposed to the hosts) knowing the light le=
vel ?

Hassnaa: it do has for QoE, and if the session time permits for the present=
ation of this draft, I will show some experimental results on that. The add=
itional functionality that could be in the network is "real-time transcodin=
g as a service function in the network". Light information can help here in=
 adapting the pixels luminance, but "light" is not the only metadata that w=
e are building this draft on it.

Bvs ---- I would argue that if there is real-time transcoding in the networ=
k, that transcoding element would need to be considered more like a host th=
an a network element. The appropriate signaling between the host/decoder an=
d the server/encoder would be to use the (potentially encrypted) feedback m=
echanism such as RTCP. Once the endpoints decided on a new set of flow char=
acteristics, they could optionally signal the network with the new flow met=
adata using PCP-like methods.=20

Once again, the client and the server have a different set of requirements =
in this area than the network. The bulk of the information should flow opaq=
uely between the client and the server. Only the information that is useful=
 to the network should be exposed to the network. There are complexity reas=
ons for this, security/privacy reasons for this, efficiency reasons, and ju=
st good layering techniques.


Hassnaa: Involving the network in the knowledge of information between the =
client and the server is promising in optimizing the video delivery, moneti=
zing bandwidth, having the operator control on their networks, better manag=
ement for QoS, ...As for security, security considerations for PCP applies,=
 that what is mentioned in the draft. And also if we think of the network m=
iddle boxes as entities owned by the operator, then there is much more trus=
t here and the same security (authentication policy) between the operator a=
nd the client should apply.

Bvs - agreed, 100%.=20

I am not arguing against flow and network metadata - just that we need to d=
efine a pretty concise set of metadata. The metadata definition methods nee=
d to be extensible to cover emerging requirements, but IMHO the initial def=
inition of the data conveyed should be quite constrained.

Hassnaa: I agree that there is a need to define a concise set for metadata =
and I am looking forward to more discussion in that direction.
Bvs ---- Yup, this is a good discussion, and we should continue to fine-tun=
e the notion of flow metadata. Some of this discussion is PCP specific, but=
 most of it could be applied to signaling protocols like PCP/ICE/Netconf/wh=
atever. There is a BOF this evening, and perhaps we could have a talk there=
........


Bvs



-----Original Message-----
From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of Moust=
afa, Hassnaa
Sent: Wednesday, November 06, 2013 2:43 PM
To: Charles Eckel (eckelcu); Tirumaleswar Reddy (tireddy); pcp@ietf.org
Cc: Moses, Danny
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

Hi Charles,

But how to let RTP intercepted by middle nodes in the network? The main ide=
a behind this draft is looking for a signaling mechanism that can push feed=
back information into the network by the end-user application and by the se=
rvice platform.

Looking forward to more discussions.

Regards,
Hassnaa
-----Original Message-----
From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
Sent: Wednesday, November 06, 2013 2:40 PM
To: Moustafa, Hassnaa; Tirumaleswar Reddy (tireddy); pcp@ietf.org
Cc: Moses, Danny
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

On 11/5/13 9:55 PM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com> wrote:

>Thanks Tiru for your comments.
>Please find my answers:
>1) If the client learns that the battery conditions, light levels have=20
>changed -
>a) why can't the client request subsequent chunk with different=20
>encoding from the URL in the manifest file ?
>b) why can't the client be intelligent enough to pick the subsequent=20
>chunk with appropriate bit-rate based on endpoint device conditions ?
>
>Hassnaa: this is possible for HTTP adaptive streaming where the client=20
>controls the video selection, but could not be done in RTP video=20
>streaming and video conferencing applications in which the server=20
>should take the adaptation decision based on some information known=20
>from the client.

For RTP traffic, using RTCP tmmbr seems an appropriate alternative.

Cheers,
Charles
=20
> And even for HTTP adaptive streaming, the client does not have a full=20
>view of the network (but only the throughput for his connectivity) and=20
>if the adaptation is done by the network itself it will consider the=20
>global bandwidth.
>
>2) use case in section 3.2 of the draft; uCDN (upstream CDN) based on=20
>location of the client and other parameters queries available dCDN=20
>(Downstream CDN) to selects the dCDN for serving content to the client.
>How is FEEDBACK option useful with uCDN/dCDN ?
>
>Hassnaa: This use-case in this current version of the draft does not=20
>consider CDN-I (CDN Interco) but it is a very good point to consider a=20
>use-case doe CDN-I in the next version of the draft. What the current=20
>use-case considers is simply a controller node that controls the=20
>multiple Application servers in the service platform. And here the=20
>feedback option is useful as it allows the controller to do a selection=20
>of the application server having content matching the "user location=20
>looking for proximity, user devices resources that are available, .."
>
>
>Hope that this clarifies your questions and looking forward to more=20
>discussion.
>
>Regards,
>Hassnaa
>
>-----Original Message-----
>From: Tirumaleswar Reddy (tireddy) [mailto:tireddy@cisco.com]
>Sent: Tuesday, November 05, 2013 7:58 PM
>To: Moustafa, Hassnaa; pcp@ietf.org
>Cc: Moses, Danny
>Subject: RE: [pcp] New Submission:
>draft-mou-pcp-application-network-feedback-00.txt
>
>Hi,
>
>My initial comments:
>
>1) If the client learns that the battery conditions, light levels have=20
>changed -
>a) why can't the client request subsequent chunk with different=20
>encoding from the URL in the manifest file ?
>b) why can't the client be intelligent enough to pick the subsequent=20
>chunk with appropriate bit-rate based on endpoint device conditions ?
>
>2) use case in section 3.2 of the draft; uCDN (upstream CDN) based on=20
>location of the client and other parameters queries available dCDN=20
>(Downstream CDN) to selects the dCDN for serving content to the client.
>
>How is FEEDBACK option useful with uCDN/dCDN ?
>
>-Tiru.
>
>> -----Original Message-----
>> From: Moustafa, Hassnaa [mailto:hassnaa.moustafa@intel.com]
>> Sent: Monday, November 04, 2013 6:33 PM
>> To: pcp@ietf.org
>> Cc: Moses, Danny
>> Subject: [pcp] New Submission:
>> draft-mou-pcp-application-network-feedback-
>> 00.txt
>>=20
>> Hi All,
>>=20
>> Draft (draft-mou-pcp-application-network-feedback) is a new draft=20
>>that  is submitted today on (PCP Extension for Signaling Feedback=20
>>Information from the End-User Application to the Application Sever and=20
>>to the Network).
>>=20
>> The draft is available at :             http://www.ietf.org/internet-
>> drafts/draft-mou-pcp-application-network-feedback-00.txt
>>=20
>> This draft addresses the need for more intelligence in the network=20
>> and service infrastructure for better content delivery to optimize=20
>> the network and devices resources. In this view, the draft proposes=20
>> using PCP to signal information
>> for: i)  Knowledge in the network and service platform about the=20
>> available device and network conditions for the end-user and ii)=20
>> Knowledge in the network about the content requirements in terms of=20
>> devices and  network resources for content stored either in the=20
>> network or in the application server.
>>=20
>> The abstract of the draft is as follows:
>> " Abstract:    Nowadays users consumption style for video and multimedia
>> applications is strongly changing.  Users are heavily counting on=20
>>wireless and mobile devices for video streaming and interactive video
>>    and multimedia applications.  This can be implemented for instance=20
>>by having more intelligence in the service and the network=20
>>infrastructure to better suit a differentiated users consumption=20
>>style.  This can be achieved
>>    through having: (i) a knowledge in the network and service=20
>>platform  about the available device and network conditions for the=20
>>end-user and
>> (ii) a knowledge in the network about the content requirements in=20
>>terms of devices
>>    capabilities and network resources for content stored either in=20
>>the  network or in the application server.  To obtain such knowledge=20
>>with  no need for changing the current infrastructure and in a=20
>>generalized way to all
>>    applications, feedback/notification mechanisms between the=20
>>end-user  application, the network and the service platform is needed=20
>>to provide  information helping the content delivery and adaptation decis=
ions.
>> This document
>>     is investigating such application-agnostic track.
>>=20
>>    This document extends the Port Control Protocol (PCP) RFC 6887=20
>> [RFC6887] to allow: (i) the users application to notify the network=20
>> and application server about its available resources in terms of
>>    devices capabilities and network conditions as well as information=20
>> about the user (e.g., location, mobility status) and (ii) the=20
>> application server to notify the network about the requirements of
>>    the content it stores in terms of devices and network resources. =20
>> A new PCP option, denoted the FEEDBACK, is specified to allow such=20
>> feedback notification signaling.  This option is used with both PEER
>>    and MAP Opcodes."
>>=20
>> Looking forward to having your feedback and more discussion on this=20
>>draft.
>>=20
>> Regards,
>> Hassnaa
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Monday, November 04, 2013 4:06 AM
>> To: Mohamed Boucadair; Moustafa, Hassnaa; Moses, Danny
>> Subject: New Version Notification for
>> draft-mou-pcp-application-network-
>> feedback-00.txt
>>=20
>>=20
>> A new version of I-D,
>> draft-mou-pcp-application-network-feedback-00.txt
>> has been successfully submitted by Hassnaa Moustafa and posted to the=20
>> IETF repository.
>>=20
>> Filename:	 draft-mou-pcp-application-network-feedback
>> Revision:	 00
>> Title:		 PCP Extension for Signaling Feedback Information from the End-
>> User Application to the Application Sever and to the Network
>> Creation date:	 2013-11-04
>> Group:		 Individual Submission
>> Number of pages: 14
>> URL:             http://www.ietf.org/internet-drafts/draft-mou-pcp-
>> application-network-feedback-00.txt
>> Status:        =20
>>http://datatracker.ietf.org/doc/draft-mou-pcp-application-
>> network-feedback
>> Htmlized:      =20
>>http://tools.ietf.org/html/draft-mou-pcp-application-network-
>> feedback-00
>>=20
>>=20
>> Abstract:
>>    Nowadays users consumption style for video and multimedia
>>    applications is strongly changing.  Users are heavily counting on
>>    wireless and mobile devices for video streaming and interactive video
>>    and multimedia applications.  This can be implemented for instance by
>>    having more intelligence in the service and the network
>>    infrastructure to better suit a differentiated users consumption
>>    style.  This can be achieved through having: (i) a knowledge in the
>>    network and service platform about the available device and network
>>    conditions for the end-user and (ii) a knowledge in the network about
>>    the content requirements in terms of devices capabilities and network
>>    resources for content stored either in the network or in the
>>    application server.  To obtain such knowledge with no need for
>>    changing the current infrastructure and in a generalized way to all
>>    applications, feedback/notification mechanisms between the end-user
>>    application, the network and the service platform is needed to
>>    provide information helping the content delivery and adaptation
>>    decisions.  This document is investigating such application-agnostic
>>    track.
>>=20
>>    This document extends the Port Control Protocol (PCP) RFC 6887
>>    [RFC6887] to allow: (i) the users application to notify the network
>>    and application server about its available resources in terms of
>>    devices capabilities and network conditions as well as information
>>    about the user (e.g., location, mobility status) and (ii) the
>>    application server to notify the network about the requirements of
>>    the content it stores in terms of devices and network resources.  A
>>    new PCP option, denoted the FEEDBACK, is specified to allow such
>>    feedback notification signaling.  This option is used with both PEER
>>    and MAP Opcodes.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of=20
>>submission until the htmlized version and diff are available at=20
>>tools.ietf.org.
>>=20
>> The IETF Secretariat
>
>_______________________________________________
>pcp mailing list
>pcp@ietf.org
>https://www.ietf.org/mailman/listinfo/pcp

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

From hassnaa.moustafa@intel.com  Wed Nov  6 16:53:34 2013
Return-Path: <hassnaa.moustafa@intel.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 115C721F9EF0 for <pcp@ietfa.amsl.com>; Wed,  6 Nov 2013 16:53:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z6TDfr+6yTul for <pcp@ietfa.amsl.com>; Wed,  6 Nov 2013 16:53:26 -0800 (PST)
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by ietfa.amsl.com (Postfix) with ESMTP id 593F021F9E96 for <pcp@ietf.org>; Wed,  6 Nov 2013 16:53:26 -0800 (PST)
Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 06 Nov 2013 16:53:26 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.93,535,1378882800"; d="scan'208";a="431020285"
Received: from orsmsx107.amr.corp.intel.com ([10.22.240.5]) by orsmga002.jf.intel.com with ESMTP; 06 Nov 2013 16:53:25 -0800
Received: from orsmsx152.amr.corp.intel.com (10.22.226.39) by ORSMSX107.amr.corp.intel.com (10.22.240.5) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 6 Nov 2013 16:53:24 -0800
Received: from orsmsx102.amr.corp.intel.com ([169.254.1.203]) by ORSMSX152.amr.corp.intel.com ([10.22.226.39]) with mapi id 14.03.0123.003; Wed, 6 Nov 2013 16:53:24 -0800
From: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: AQHO20FA3qQ5kE8Dck6wfwgBNXLH8ZoZMREA//+cYDCAAALlkIAAAubwgAAc44A=
Date: Thu, 7 Nov 2013 00:53:24 +0000
Message-ID: <F893BEC192403B489DBA38999068CF190594A0D1@ORSMSX102.amr.corp.intel.com>
References: <F893BEC192403B489DBA38999068CF19059498E0@ORSMSX102.amr.corp.intel.com> <CEA003BD.144DB%eckelcu@cisco.com> <F893BEC192403B489DBA38999068CF1905949F31@ORSMSX102.amr.corp.intel.com> <AE7F97DB5FEE054088D82E836BD15BE920137BF3@xmb-aln-x05.cisco.com> <F893BEC192403B489DBA38999068CF1905949F7D@ORSMSX102.amr.corp.intel.com> <AE7F97DB5FEE054088D82E836BD15BE920137D2B@xmb-aln-x05.cisco.com>
In-Reply-To: <AE7F97DB5FEE054088D82E836BD15BE920137D2B@xmb-aln-x05.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.22.254.140]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2013 00:53:35 -0000

Hi Bill,

I think that we agree on most of the points.

Only, regarding this point:
" Bvs ---- I would argue that if there is real-time transcoding in the netw=
ork, that transcoding element would need to be considered more like a host =
than a network element. The appropriate signaling between the host/decoder =
and the server/encoder would be to use the (potentially encrypted) feedback=
 mechanism such as RTCP. Once the endpoints decided on a new set of flow ch=
aracteristics, they could optionally signal the network with the new flow m=
etadata using PCP-like methods. "

--> Hassnaa: I am not sure if we can consider the network element as a host=
/decoder. The network element sits as a middle between the client (host/dec=
oder) and the (application server).=20

Yes I am aware of the BoF on metadata and will be happy to discuss more.

Regards,
Hassnaa
-----Original Message-----
From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]=20
Sent: Wednesday, November 06, 2013 3:25 PM
To: Moustafa, Hassnaa; Charles Eckel (eckelcu); Tirumaleswar Reddy (tireddy=
); pcp@ietf.org
Cc: Moses, Danny
Subject: RE: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

In line with BVS -----

Bvs


-----Original Message-----
From: Moustafa, Hassnaa [mailto:hassnaa.moustafa@intel.com]
Sent: Wednesday, November 06, 2013 3:06 PM
To: Bill Ver Steeg (versteb); Charles Eckel (eckelcu); Tirumaleswar Reddy (=
tireddy); pcp@ietf.org
Cc: Moses, Danny
Subject: RE: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

Hi Bill,
Thanks for your detailed feedback.
Please see inline my replies.

Regards,
Hassnaa

-----Original Message-----
From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
Sent: Wednesday, November 06, 2013 2:53 PM
To: Moustafa, Hassnaa; Charles Eckel (eckelcu); Tirumaleswar Reddy (tireddy=
); pcp@ietf.org
Cc: Moses, Danny
Subject: RE: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

The network has use for flow metadata that is abstract enough to be useful =
to the network. Things like target bandwidth, requirements for delay/loss/j=
itter and the like seem to be interesting to the network.=20

Hassnaa: Yes, I agree. But this is mainly for the QoS management. What we a=
re looking for is QoE which requires more metadata than the target BW, dela=
y/loss/jitter. QoE related metadata needs to work with the QoS related meta=
data an does not mean to replace it.

The application-specific details like screen size, light level, weight of t=
he device do not have any apparent use. If the network is aware of the targ=
et bandwidth, desired delay/loss/jitter, what additional functionality is e=
nabled by having the network (as opposed to the hosts) knowing the light le=
vel ?

Hassnaa: it do has for QoE, and if the session time permits for the present=
ation of this draft, I will show some experimental results on that. The add=
itional functionality that could be in the network is "real-time transcodin=
g as a service function in the network". Light information can help here in=
 adapting the pixels luminance, but "light" is not the only metadata that w=
e are building this draft on it.

Bvs ---- I would argue that if there is real-time transcoding in the networ=
k, that transcoding element would need to be considered more like a host th=
an a network element. The appropriate signaling between the host/decoder an=
d the server/encoder would be to use the (potentially encrypted) feedback m=
echanism such as RTCP. Once the endpoints decided on a new set of flow char=
acteristics, they could optionally signal the network with the new flow met=
adata using PCP-like methods.=20

Once again, the client and the server have a different set of requirements =
in this area than the network. The bulk of the information should flow opaq=
uely between the client and the server. Only the information that is useful=
 to the network should be exposed to the network. There are complexity reas=
ons for this, security/privacy reasons for this, efficiency reasons, and ju=
st good layering techniques.


Hassnaa: Involving the network in the knowledge of information between the =
client and the server is promising in optimizing the video delivery, moneti=
zing bandwidth, having the operator control on their networks, better manag=
ement for QoS, ...As for security, security considerations for PCP applies,=
 that what is mentioned in the draft. And also if we think of the network m=
iddle boxes as entities owned by the operator, then there is much more trus=
t here and the same security (authentication policy) between the operator a=
nd the client should apply.

Bvs - agreed, 100%.=20

I am not arguing against flow and network metadata - just that we need to d=
efine a pretty concise set of metadata. The metadata definition methods nee=
d to be extensible to cover emerging requirements, but IMHO the initial def=
inition of the data conveyed should be quite constrained.

Hassnaa: I agree that there is a need to define a concise set for metadata =
and I am looking forward to more discussion in that direction.
Bvs ---- Yup, this is a good discussion, and we should continue to fine-tun=
e the notion of flow metadata. Some of this discussion is PCP specific, but=
 most of it could be applied to signaling protocols like PCP/ICE/Netconf/wh=
atever. There is a BOF this evening, and perhaps we could have a talk there=
........


Bvs



-----Original Message-----
From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of Moust=
afa, Hassnaa
Sent: Wednesday, November 06, 2013 2:43 PM
To: Charles Eckel (eckelcu); Tirumaleswar Reddy (tireddy); pcp@ietf.org
Cc: Moses, Danny
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

Hi Charles,

But how to let RTP intercepted by middle nodes in the network? The main ide=
a behind this draft is looking for a signaling mechanism that can push feed=
back information into the network by the end-user application and by the se=
rvice platform.

Looking forward to more discussions.

Regards,
Hassnaa
-----Original Message-----
From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
Sent: Wednesday, November 06, 2013 2:40 PM
To: Moustafa, Hassnaa; Tirumaleswar Reddy (tireddy); pcp@ietf.org
Cc: Moses, Danny
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedba=
ck-00.txt

On 11/5/13 9:55 PM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com> wrote:

>Thanks Tiru for your comments.
>Please find my answers:
>1) If the client learns that the battery conditions, light levels have=20
>changed -
>a) why can't the client request subsequent chunk with different=20
>encoding from the URL in the manifest file ?
>b) why can't the client be intelligent enough to pick the subsequent=20
>chunk with appropriate bit-rate based on endpoint device conditions ?
>
>Hassnaa: this is possible for HTTP adaptive streaming where the client=20
>controls the video selection, but could not be done in RTP video=20
>streaming and video conferencing applications in which the server=20
>should take the adaptation decision based on some information known=20
>from the client.

For RTP traffic, using RTCP tmmbr seems an appropriate alternative.

Cheers,
Charles
=20
> And even for HTTP adaptive streaming, the client does not have a full=20
>view of the network (but only the throughput for his connectivity) and=20
>if the adaptation is done by the network itself it will consider the=20
>global bandwidth.
>
>2) use case in section 3.2 of the draft; uCDN (upstream CDN) based on=20
>location of the client and other parameters queries available dCDN=20
>(Downstream CDN) to selects the dCDN for serving content to the client.
>How is FEEDBACK option useful with uCDN/dCDN ?
>
>Hassnaa: This use-case in this current version of the draft does not=20
>consider CDN-I (CDN Interco) but it is a very good point to consider a=20
>use-case doe CDN-I in the next version of the draft. What the current=20
>use-case considers is simply a controller node that controls the=20
>multiple Application servers in the service platform. And here the=20
>feedback option is useful as it allows the controller to do a selection=20
>of the application server having content matching the "user location=20
>looking for proximity, user devices resources that are available, .."
>
>
>Hope that this clarifies your questions and looking forward to more=20
>discussion.
>
>Regards,
>Hassnaa
>
>-----Original Message-----
>From: Tirumaleswar Reddy (tireddy) [mailto:tireddy@cisco.com]
>Sent: Tuesday, November 05, 2013 7:58 PM
>To: Moustafa, Hassnaa; pcp@ietf.org
>Cc: Moses, Danny
>Subject: RE: [pcp] New Submission:
>draft-mou-pcp-application-network-feedback-00.txt
>
>Hi,
>
>My initial comments:
>
>1) If the client learns that the battery conditions, light levels have=20
>changed -
>a) why can't the client request subsequent chunk with different=20
>encoding from the URL in the manifest file ?
>b) why can't the client be intelligent enough to pick the subsequent=20
>chunk with appropriate bit-rate based on endpoint device conditions ?
>
>2) use case in section 3.2 of the draft; uCDN (upstream CDN) based on=20
>location of the client and other parameters queries available dCDN=20
>(Downstream CDN) to selects the dCDN for serving content to the client.
>
>How is FEEDBACK option useful with uCDN/dCDN ?
>
>-Tiru.
>
>> -----Original Message-----
>> From: Moustafa, Hassnaa [mailto:hassnaa.moustafa@intel.com]
>> Sent: Monday, November 04, 2013 6:33 PM
>> To: pcp@ietf.org
>> Cc: Moses, Danny
>> Subject: [pcp] New Submission:
>> draft-mou-pcp-application-network-feedback-
>> 00.txt
>>=20
>> Hi All,
>>=20
>> Draft (draft-mou-pcp-application-network-feedback) is a new draft=20
>>that  is submitted today on (PCP Extension for Signaling Feedback=20
>>Information from the End-User Application to the Application Sever and=20
>>to the Network).
>>=20
>> The draft is available at :             http://www.ietf.org/internet-
>> drafts/draft-mou-pcp-application-network-feedback-00.txt
>>=20
>> This draft addresses the need for more intelligence in the network=20
>> and service infrastructure for better content delivery to optimize=20
>> the network and devices resources. In this view, the draft proposes=20
>> using PCP to signal information
>> for: i)  Knowledge in the network and service platform about the=20
>> available device and network conditions for the end-user and ii)=20
>> Knowledge in the network about the content requirements in terms of=20
>> devices and  network resources for content stored either in the=20
>> network or in the application server.
>>=20
>> The abstract of the draft is as follows:
>> " Abstract:    Nowadays users consumption style for video and multimedia
>> applications is strongly changing.  Users are heavily counting on=20
>>wireless and mobile devices for video streaming and interactive video
>>    and multimedia applications.  This can be implemented for instance=20
>>by having more intelligence in the service and the network=20
>>infrastructure to better suit a differentiated users consumption=20
>>style.  This can be achieved
>>    through having: (i) a knowledge in the network and service=20
>>platform  about the available device and network conditions for the=20
>>end-user and
>> (ii) a knowledge in the network about the content requirements in=20
>>terms of devices
>>    capabilities and network resources for content stored either in=20
>>the  network or in the application server.  To obtain such knowledge=20
>>with  no need for changing the current infrastructure and in a=20
>>generalized way to all
>>    applications, feedback/notification mechanisms between the=20
>>end-user  application, the network and the service platform is needed=20
>>to provide  information helping the content delivery and adaptation decis=
ions.
>> This document
>>     is investigating such application-agnostic track.
>>=20
>>    This document extends the Port Control Protocol (PCP) RFC 6887=20
>> [RFC6887] to allow: (i) the users application to notify the network=20
>> and application server about its available resources in terms of
>>    devices capabilities and network conditions as well as information=20
>> about the user (e.g., location, mobility status) and (ii) the=20
>> application server to notify the network about the requirements of
>>    the content it stores in terms of devices and network resources. =20
>> A new PCP option, denoted the FEEDBACK, is specified to allow such=20
>> feedback notification signaling.  This option is used with both PEER
>>    and MAP Opcodes."
>>=20
>> Looking forward to having your feedback and more discussion on this=20
>>draft.
>>=20
>> Regards,
>> Hassnaa
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Monday, November 04, 2013 4:06 AM
>> To: Mohamed Boucadair; Moustafa, Hassnaa; Moses, Danny
>> Subject: New Version Notification for
>> draft-mou-pcp-application-network-
>> feedback-00.txt
>>=20
>>=20
>> A new version of I-D,
>> draft-mou-pcp-application-network-feedback-00.txt
>> has been successfully submitted by Hassnaa Moustafa and posted to the=20
>> IETF repository.
>>=20
>> Filename:	 draft-mou-pcp-application-network-feedback
>> Revision:	 00
>> Title:		 PCP Extension for Signaling Feedback Information from the End-
>> User Application to the Application Sever and to the Network
>> Creation date:	 2013-11-04
>> Group:		 Individual Submission
>> Number of pages: 14
>> URL:             http://www.ietf.org/internet-drafts/draft-mou-pcp-
>> application-network-feedback-00.txt
>> Status:        =20
>>http://datatracker.ietf.org/doc/draft-mou-pcp-application-
>> network-feedback
>> Htmlized:      =20
>>http://tools.ietf.org/html/draft-mou-pcp-application-network-
>> feedback-00
>>=20
>>=20
>> Abstract:
>>    Nowadays users consumption style for video and multimedia
>>    applications is strongly changing.  Users are heavily counting on
>>    wireless and mobile devices for video streaming and interactive video
>>    and multimedia applications.  This can be implemented for instance by
>>    having more intelligence in the service and the network
>>    infrastructure to better suit a differentiated users consumption
>>    style.  This can be achieved through having: (i) a knowledge in the
>>    network and service platform about the available device and network
>>    conditions for the end-user and (ii) a knowledge in the network about
>>    the content requirements in terms of devices capabilities and network
>>    resources for content stored either in the network or in the
>>    application server.  To obtain such knowledge with no need for
>>    changing the current infrastructure and in a generalized way to all
>>    applications, feedback/notification mechanisms between the end-user
>>    application, the network and the service platform is needed to
>>    provide information helping the content delivery and adaptation
>>    decisions.  This document is investigating such application-agnostic
>>    track.
>>=20
>>    This document extends the Port Control Protocol (PCP) RFC 6887
>>    [RFC6887] to allow: (i) the users application to notify the network
>>    and application server about its available resources in terms of
>>    devices capabilities and network conditions as well as information
>>    about the user (e.g., location, mobility status) and (ii) the
>>    application server to notify the network about the requirements of
>>    the content it stores in terms of devices and network resources.  A
>>    new PCP option, denoted the FEEDBACK, is specified to allow such
>>    feedback notification signaling.  This option is used with both PEER
>>    and MAP Opcodes.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of=20
>>submission until the htmlized version and diff are available at=20
>>tools.ietf.org.
>>=20
>> The IETF Secretariat
>
>_______________________________________________
>pcp mailing list
>pcp@ietf.org
>https://www.ietf.org/mailman/listinfo/pcp

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

From eckelcu@cisco.com  Wed Nov  6 17:13:46 2013
Return-Path: <eckelcu@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70D5B11E81D2 for <pcp@ietfa.amsl.com>; Wed,  6 Nov 2013 17:13:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N+6j0taItSXj for <pcp@ietfa.amsl.com>; Wed,  6 Nov 2013 17:13:41 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id E03E311E81D4 for <pcp@ietf.org>; Wed,  6 Nov 2013 17:13:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11408; q=dns/txt; s=iport; t=1383786821; x=1384996421; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=vznjeLpiDswnczQ+vv1tfnm/rIpysBYKZLLKIV8tqd0=; b=ftT8k8SMT7n09bUcEIWYkd9HpE+YJHhFUhvX1JFrBNli65/m4e+xDx8c yxl138M9lzdUV+FojK3XV5rrzaB9czacf5SdABPq5YqdCmRPmT4eL3j7R td/y8/6QHVAmaks0TH0wirdtKCAdKqr30W7zmte8YIYOh+LRDgXThhbGU k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0GAMLoelKtJV2Y/2dsb2JhbABbgwc4TQa/LoEpFnSCJQEBAQQBAQE3NAsMBgEIEQQBAR8JLgsUCQgCBAENBQmHeAgFvn6OCoFPBwaEKgOYDIEviyaFNYMmgio
X-IronPort-AV: E=Sophos;i="4.93,647,1378857600"; d="scan'208";a="278708801"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-9.cisco.com with ESMTP; 07 Nov 2013 01:13:40 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rA71DduB029024 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 7 Nov 2013 01:13:39 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.191]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0123.003; Wed, 6 Nov 2013 19:13:39 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
Thread-Index: AQHO20EX7aeWR5gOw0WyYbyjnfhkfZoYy+UAgAAJHQA=
Date: Thu, 7 Nov 2013 01:13:38 +0000
Message-ID: <CEA02769.14664%eckelcu@cisco.com>
In-Reply-To: <F893BEC192403B489DBA38999068CF1905949F31@ORSMSX102.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.115.31]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D4FAC0FAB61DFA4F909A5227E9B202F6@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: Re: [pcp] New Submission: draft-mou-pcp-application-network-feedback-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2013 01:13:46 -0000

On 11/6/13 2:42 PM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com> wrote:

>Hi Charles,
>
>But how to let RTP intercepted by middle nodes in the network?

That is a different use case than the one I thought we were discussing.
I understood the use case to be that the client wanted to signal to an RTP
video streaming or conferencing server to reduce the amount of bandwidth
it receives. I am saying there are existing application level signaling
mechanisms to accomplish this. In the case of RTCP tmmbr, the RTCP message
would be from the client to the application server, and it is not intended
for the network to glean information from it.


>The main idea behind this draft is looking for a signaling mechanism that
>can push feedback information into the network by the end-user
>application and by the service platform.

Yes, and this idea seems reasonable to me in general, just not for the use
case above as I understood it.

Cheers,
Charles

>
>Looking forward to more discussions.
>
>Regards,
>Hassnaa
>-----Original Message-----
>From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
>Sent: Wednesday, November 06, 2013 2:40 PM
>To: Moustafa, Hassnaa; Tirumaleswar Reddy (tireddy); pcp@ietf.org
>Cc: Moses, Danny
>Subject: Re: [pcp] New Submission:
>draft-mou-pcp-application-network-feedback-00.txt
>
>On 11/5/13 9:55 PM, "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>
>wrote:
>
>>Thanks Tiru for your comments.
>>Please find my answers:
>>1) If the client learns that the battery conditions, light levels have
>>changed -
>>a) why can't the client request subsequent chunk with different
>>encoding from the URL in the manifest file ?
>>b) why can't the client be intelligent enough to pick the subsequent
>>chunk with appropriate bit-rate based on endpoint device conditions ?
>>
>>Hassnaa: this is possible for HTTP adaptive streaming where the client
>>controls the video selection, but could not be done in RTP video
>>streaming and video conferencing applications in which the server
>>should take the adaptation decision based on some information known
>>from the client.
>
>For RTP traffic, using RTCP tmmbr seems an appropriate alternative.
>
>Cheers,
>Charles
>=20
>> And even for HTTP adaptive streaming, the client does not have a full
>>view of the network (but only the throughput for his connectivity) and
>>if the adaptation is done by the network itself it will consider the
>>global bandwidth.
>>
>>2) use case in section 3.2 of the draft; uCDN (upstream CDN) based on
>>location of the client and other parameters queries available dCDN
>>(Downstream CDN) to selects the dCDN for serving content to the client.
>>How is FEEDBACK option useful with uCDN/dCDN ?
>>
>>Hassnaa: This use-case in this current version of the draft does not
>>consider CDN-I (CDN Interco) but it is a very good point to consider a
>>use-case doe CDN-I in the next version of the draft. What the current
>>use-case considers is simply a controller node that controls the
>>multiple Application servers in the service platform. And here the
>>feedback option is useful as it allows the controller to do a selection
>>of the application server having content matching the "user location
>>looking for proximity, user devices resources that are available, .."
>>
>>
>>Hope that this clarifies your questions and looking forward to more
>>discussion.
>>
>>Regards,
>>Hassnaa
>>
>>-----Original Message-----
>>From: Tirumaleswar Reddy (tireddy) [mailto:tireddy@cisco.com]
>>Sent: Tuesday, November 05, 2013 7:58 PM
>>To: Moustafa, Hassnaa; pcp@ietf.org
>>Cc: Moses, Danny
>>Subject: RE: [pcp] New Submission:
>>draft-mou-pcp-application-network-feedback-00.txt
>>
>>Hi,
>>
>>My initial comments:
>>
>>1) If the client learns that the battery conditions, light levels have
>>changed -
>>a) why can't the client request subsequent chunk with different
>>encoding from the URL in the manifest file ?
>>b) why can't the client be intelligent enough to pick the subsequent
>>chunk with appropriate bit-rate based on endpoint device conditions ?
>>
>>2) use case in section 3.2 of the draft; uCDN (upstream CDN) based on
>>location of the client and other parameters queries available dCDN
>>(Downstream CDN) to selects the dCDN for serving content to the client.
>>
>>How is FEEDBACK option useful with uCDN/dCDN ?
>>
>>-Tiru.
>>
>>> -----Original Message-----
>>> From: Moustafa, Hassnaa [mailto:hassnaa.moustafa@intel.com]
>>> Sent: Monday, November 04, 2013 6:33 PM
>>> To: pcp@ietf.org
>>> Cc: Moses, Danny
>>> Subject: [pcp] New Submission:
>>> draft-mou-pcp-application-network-feedback-
>>> 00.txt
>>>=20
>>> Hi All,
>>>=20
>>> Draft (draft-mou-pcp-application-network-feedback) is a new draft
>>>that  is submitted today on (PCP Extension for Signaling Feedback
>>>Information from the End-User Application to the Application Sever and
>>>to the Network).
>>>=20
>>> The draft is available at :             http://www.ietf.org/internet-
>>> drafts/draft-mou-pcp-application-network-feedback-00.txt
>>>=20
>>> This draft addresses the need for more intelligence in the network
>>> and service infrastructure for better content delivery to optimize
>>> the network and devices resources. In this view, the draft proposes
>>> using PCP to signal information
>>> for: i)  Knowledge in the network and service platform about the
>>> available device and network conditions for the end-user and ii)
>>> Knowledge in the network about the content requirements in terms of
>>> devices and  network resources for content stored either in the
>>> network or in the application server.
>>>=20
>>> The abstract of the draft is as follows:
>>> " Abstract:    Nowadays users consumption style for video and
>>>multimedia
>>> applications is strongly changing.  Users are heavily counting on
>>>wireless and mobile devices for video streaming and interactive video
>>>    and multimedia applications.  This can be implemented for instance
>>>by having more intelligence in the service and the network
>>>infrastructure to better suit a differentiated users consumption
>>>style.  This can be achieved
>>>    through having: (i) a knowledge in the network and service
>>>platform  about the available device and network conditions for the
>>>end-user and
>>> (ii) a knowledge in the network about the content requirements in
>>>terms of devices
>>>    capabilities and network resources for content stored either in
>>>the  network or in the application server.  To obtain such knowledge
>>>with  no need for changing the current infrastructure and in a
>>>generalized way to all
>>>    applications, feedback/notification mechanisms between the
>>>end-user  application, the network and the service platform is needed
>>>to provide  information helping the content delivery and adaptation
>>>decisions.
>>> This document
>>>     is investigating such application-agnostic track.
>>>=20
>>>    This document extends the Port Control Protocol (PCP) RFC 6887
>>> [RFC6887] to allow: (i) the users application to notify the network
>>> and application server about its available resources in terms of
>>>    devices capabilities and network conditions as well as information
>>> about the user (e.g., location, mobility status) and (ii) the
>>> application server to notify the network about the requirements of
>>>    the content it stores in terms of devices and network resources.
>>> A new PCP option, denoted the FEEDBACK, is specified to allow such
>>> feedback notification signaling.  This option is used with both PEER
>>>    and MAP Opcodes."
>>>=20
>>> Looking forward to having your feedback and more discussion on this
>>>draft.
>>>=20
>>> Regards,
>>> Hassnaa
>>>=20
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>> Sent: Monday, November 04, 2013 4:06 AM
>>> To: Mohamed Boucadair; Moustafa, Hassnaa; Moses, Danny
>>> Subject: New Version Notification for
>>> draft-mou-pcp-application-network-
>>> feedback-00.txt
>>>=20
>>>=20
>>> A new version of I-D,
>>> draft-mou-pcp-application-network-feedback-00.txt
>>> has been successfully submitted by Hassnaa Moustafa and posted to the
>>> IETF repository.
>>>=20
>>> Filename:	 draft-mou-pcp-application-network-feedback
>>> Revision:	 00
>>> Title:		 PCP Extension for Signaling Feedback Information from the End-
>>> User Application to the Application Sever and to the Network
>>> Creation date:	 2013-11-04
>>> Group:		 Individual Submission
>>> Number of pages: 14
>>> URL:             http://www.ietf.org/internet-drafts/draft-mou-pcp-
>>> application-network-feedback-00.txt
>>> Status:       =20
>>>http://datatracker.ietf.org/doc/draft-mou-pcp-application-
>>> network-feedback
>>> Htmlized:     =20
>>>http://tools.ietf.org/html/draft-mou-pcp-application-network-
>>> feedback-00
>>>=20
>>>=20
>>> Abstract:
>>>    Nowadays users consumption style for video and multimedia
>>>    applications is strongly changing.  Users are heavily counting on
>>>    wireless and mobile devices for video streaming and interactive
>>>video
>>>    and multimedia applications.  This can be implemented for instance
>>>by
>>>    having more intelligence in the service and the network
>>>    infrastructure to better suit a differentiated users consumption
>>>    style.  This can be achieved through having: (i) a knowledge in the
>>>    network and service platform about the available device and network
>>>    conditions for the end-user and (ii) a knowledge in the network
>>>about
>>>    the content requirements in terms of devices capabilities and
>>>network
>>>    resources for content stored either in the network or in the
>>>    application server.  To obtain such knowledge with no need for
>>>    changing the current infrastructure and in a generalized way to all
>>>    applications, feedback/notification mechanisms between the end-user
>>>    application, the network and the service platform is needed to
>>>    provide information helping the content delivery and adaptation
>>>    decisions.  This document is investigating such application-agnostic
>>>    track.
>>>=20
>>>    This document extends the Port Control Protocol (PCP) RFC 6887
>>>    [RFC6887] to allow: (i) the users application to notify the network
>>>    and application server about its available resources in terms of
>>>    devices capabilities and network conditions as well as information
>>>    about the user (e.g., location, mobility status) and (ii) the
>>>    application server to notify the network about the requirements of
>>>    the content it stores in terms of devices and network resources.  A
>>>    new PCP option, denoted the FEEDBACK, is specified to allow such
>>>    feedback notification signaling.  This option is used with both PEER
>>>    and MAP Opcodes.
>>>=20
>>>=20
>>>=20
>>>=20
>>> Please note that it may take a couple of minutes from the time of
>>>submission until the htmlized version and diff are available at
>>>tools.ietf.org.
>>>=20
>>> The IETF Secretariat
>>
>>_______________________________________________
>>pcp mailing list
>>pcp@ietf.org
>>https://www.ietf.org/mailman/listinfo/pcp
>


From peter@denic.de  Mon Nov 11 09:39:49 2013
Return-Path: <peter@denic.de>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF8B321E8204 for <pcp@ietfa.amsl.com>; Mon, 11 Nov 2013 09:39:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level: 
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wheDwQ7QGmLz for <pcp@ietfa.amsl.com>; Mon, 11 Nov 2013 09:39:49 -0800 (PST)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::3]) by ietfa.amsl.com (Postfix) with ESMTP id B420321E81FF for <pcp@ietf.org>; Mon, 11 Nov 2013 09:39:39 -0800 (PST)
Received: from x27.adm.denic.de (x28.fra2.if.denic.de [10.122.64.17]) by office.denic.de with esmtp   id 1VfvSc-00052n-Bx; Mon, 11 Nov 2013 18:39:38 +0100
Received: from localhost by x27.adm.denic.de with local  id 1VfvSc-0006F8-8V; Mon, 11 Nov 2013 18:39:38 +0100
Date: Mon, 11 Nov 2013 18:39:38 +0100
From: Peter Koch <pk@DENIC.DE>
To: pcp@ietf.org
Message-ID: <20131111173938.GQ24189@x28.adm.denic.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
Subject: [pcp] draft-ietf-pcp-port-set-03.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Nov 2013 17:39:50 -0000

This is a review of draft-ietf-pcp-port-set-03.txt, which I know
has passed WG last call.  Following the discussion in Vancouver I would
like to raise two issues that might benefit from being addressed:

1) The "NOTE TO IANA" in section 4 is inconsistent with the remark in
   the IANA considerations section:

      NOTE TO IANA (to be removed prior to publication as an RFC): The
      number is to be assigned by IANA in the range 128-191 (i.e.,
      optional to process and created via Standards Action).

   vs.

     IANA shall allocate a code in the range 1-63 for the new PCP option
     defined in Section 4.

   The note given in section 4 is what should go into the IANA considerations
   section, exactly identifying the IANA registry
   "PCP options" as per section 19.4 of RFC 6887.

   The draft does not explicitly state whether PORT_SET is optional
   or mandatory, although section 4.1 seems to suggest it's optional:

     If the PORT_SET option is not supported by the server, the PCP client
     will receive a response with no PORT_SET option, which is the
     operation of a PCP server that does not support PORT_SET.

   It would help the reader to understand what the choice is and the
   reasoning behind it.

2) The use cases in section 1 as well as the reasoning in section 3
   suggest that the PORT_SET is a method of convenience that, among other
   features, reduces latency compared to multiple subsequent
   single port requests.  The document does not mention whether a
   MAP/PORT_SET option is an atomic transaction, even though to the
   client it appears as such, since it will receive all-or-nothing.

   However, the fallback strategy outlined in section 3 ...

      Therefore, while it is functionally possible to obtain the same
      results using plain MAP, the extension proposed in this document

   and section 4.1

      If the PORT_SET option is not supported by the server, the PCP client
      will receive a response with no PORT_SET option, which is the
      operation of a PCP server that does not support PORT_SET.  That
      response will map one port.  To map its other desired ports, the PCP
      client will then have to issue individual MAP requests with no
      PORT_SET option to achieve similar functionality.

   made me think of potential resource contention issues (a.k.a.
   Dijkstra's 'dining philosophers'), expecially when asking for larger
   port ranges.  This would not follow from the new option, but originates
   from within the application. Still, I think the suggested fallback
   should be accompanied by an appropriate warning.

   The example given in 5.1 as well as the discussion in Vancouver
   mentioned mapping requests that would only be partly satisfied and
   often enough deemed "good enough".  Given that port diversity is
   sometimes used as a security measure (RFC 5452, RFC 6056), I'd
   like to suggest to add a remark to the security considerations
   section respectively.

As a minor one, I'd suggest to add an informational reference to RFC 4787
for a definition of 'port parity'.

-Peter

From simon.perreault@viagenie.ca  Mon Nov 11 11:17:45 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4220C11E8234 for <pcp@ietfa.amsl.com>; Mon, 11 Nov 2013 11:17:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zh-LD+7062-Y for <pcp@ietfa.amsl.com>; Mon, 11 Nov 2013 11:17:44 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 32D9E11E8231 for <pcp@ietf.org>; Mon, 11 Nov 2013 11:17:44 -0800 (PST)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:acf9:5812:a91c:5cc2]) by jazz.viagenie.ca (Postfix) with ESMTPSA id B0EDC403A7 for <pcp@ietf.org>; Mon, 11 Nov 2013 14:17:43 -0500 (EST)
Message-ID: <52812D57.9070400@viagenie.ca>
Date: Mon, 11 Nov 2013 14:17:43 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: pcp@ietf.org
References: <20131111173938.GQ24189@x28.adm.denic.de>
In-Reply-To: <20131111173938.GQ24189@x28.adm.denic.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [pcp] draft-ietf-pcp-port-set-03.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Nov 2013 19:17:46 -0000

Peter,

Thanks a lot for your review.

The next revision will be adjusted according to your comments.

Thanks,
Simon

Le 2013-11-11 12:39, Peter Koch a écrit :
> This is a review of draft-ietf-pcp-port-set-03.txt, which I know
> has passed WG last call.  Following the discussion in Vancouver I would
> like to raise two issues that might benefit from being addressed:
>
> 1) The "NOTE TO IANA" in section 4 is inconsistent with the remark in
>     the IANA considerations section:
>
>        NOTE TO IANA (to be removed prior to publication as an RFC): The
>        number is to be assigned by IANA in the range 128-191 (i.e.,
>        optional to process and created via Standards Action).
>
>     vs.
>
>       IANA shall allocate a code in the range 1-63 for the new PCP option
>       defined in Section 4.
>
>     The note given in section 4 is what should go into the IANA considerations
>     section, exactly identifying the IANA registry
>     "PCP options" as per section 19.4 of RFC 6887.
>
>     The draft does not explicitly state whether PORT_SET is optional
>     or mandatory, although section 4.1 seems to suggest it's optional:
>
>       If the PORT_SET option is not supported by the server, the PCP client
>       will receive a response with no PORT_SET option, which is the
>       operation of a PCP server that does not support PORT_SET.
>
>     It would help the reader to understand what the choice is and the
>     reasoning behind it.
>
> 2) The use cases in section 1 as well as the reasoning in section 3
>     suggest that the PORT_SET is a method of convenience that, among other
>     features, reduces latency compared to multiple subsequent
>     single port requests.  The document does not mention whether a
>     MAP/PORT_SET option is an atomic transaction, even though to the
>     client it appears as such, since it will receive all-or-nothing.
>
>     However, the fallback strategy outlined in section 3 ...
>
>        Therefore, while it is functionally possible to obtain the same
>        results using plain MAP, the extension proposed in this document
>
>     and section 4.1
>
>        If the PORT_SET option is not supported by the server, the PCP client
>        will receive a response with no PORT_SET option, which is the
>        operation of a PCP server that does not support PORT_SET.  That
>        response will map one port.  To map its other desired ports, the PCP
>        client will then have to issue individual MAP requests with no
>        PORT_SET option to achieve similar functionality.
>
>     made me think of potential resource contention issues (a.k.a.
>     Dijkstra's 'dining philosophers'), expecially when asking for larger
>     port ranges.  This would not follow from the new option, but originates
>     from within the application. Still, I think the suggested fallback
>     should be accompanied by an appropriate warning.
>
>     The example given in 5.1 as well as the discussion in Vancouver
>     mentioned mapping requests that would only be partly satisfied and
>     often enough deemed "good enough".  Given that port diversity is
>     sometimes used as a security measure (RFC 5452, RFC 6056), I'd
>     like to suggest to add a remark to the security considerations
>     section respectively.
>
> As a minor one, I'd suggest to add an informational reference to RFC 4787
> for a definition of 'port parity'.
>
> -Peter
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp
>


-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From tireddy@cisco.com  Thu Nov 14 07:21:10 2013
Return-Path: <tireddy@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9EAD11E8133 for <pcp@ietfa.amsl.com>; Thu, 14 Nov 2013 07:21:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.561
X-Spam-Level: 
X-Spam-Status: No, score=-10.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FIisYFtADltu for <pcp@ietfa.amsl.com>; Thu, 14 Nov 2013 07:21:06 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 07B9C21E80E7 for <pcp@ietf.org>; Thu, 14 Nov 2013 07:21:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3357; q=dns/txt; s=iport; t=1384442466; x=1385652066; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=OIibAX7+dK2maszKavTR4z7e0ORibOG346nVLVyO3m4=; b=lomQujVg0nJi5GtBB8PRwwKNtumu3z6/6f2/f8HPFwvwyrq5obkxQ3zw BghzUbkcDt5d5Qe+GbFKoUNRM9ZfSXV8nizpeILwadi1AqibLvBCDKg6L OkoCktuPvpm6G1URID9Q6h1T14wNXGzpzPqC89kMzlJcQ/vO4z7FQefs6 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAADphFKtJV2c/2dsb2JhbABagwc4U78hgR8WdIIlAQEBBDo9DgQCAQgRBAEBAQoUCQcyFAkIAgQBEggBh3gNwB6PLjgGgxqBEQOZP5BdgyiCKg
X-IronPort-AV: E=Sophos;i="4.93,700,1378857600"; d="scan'208";a="284595440"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-1.cisco.com with ESMTP; 14 Nov 2013 15:21:05 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id rAEFL4dW014127 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 14 Nov 2013 15:21:04 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.47]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0123.003; Thu, 14 Nov 2013 09:21:04 -0600
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHO2mGhjLsh300HAEimsEM4ztlxb5oksKaw
Date: Thu, 14 Nov 2013 15:21:03 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A24263C93@xmb-rcd-x10.cisco.com>
References: <CE80F267.246A1%sureshk@juniper.net> <CE9E7D38.26B47%sureshk@juniper.net>
In-Reply-To: <CE9E7D38.26B47%sureshk@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.79.196]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Nov 2013 15:21:11 -0000

Hi Suresh,

My initial comments

1)Why cannot the problem be solved for example by the PCP client sending PE=
ER with a long lifetime and if the lifetime is higher than a particular thr=
eshold only those connections are synced implicitly ?

2)HA is applicable for both NAT and Firewall devices. I would suggest not t=
o restrict the draft to only NAT scenarios.

3)In Active-Standby HA, switch-over is triggered not just because of Active=
 rebooting but also because of WAN-link failures. Are you assuming HA deplo=
yments with provider-independent or provider-dependent addresses ?

4)

a) PCP third-party authorization (draft-wing-pcp-third-party-authz) could a=
lso be one way of telling the network that it's for a business critical app=
lication and connection can be synced implicitly without explicit signaling=
.=20

b) Other possible ways could be checkpoint based on destination port/addres=
s (For example HTTPS flows are more critical than HTTP).

5)How does PCP ANNOUNCE work in this deployment ?
I mean some connections on the host need to know that PCP-aware NAT/Firewal=
l has rebooted but other connections may not because their states are check=
-pointed.

6) How does an application developer know if syncing the state is required =
or not ?
The problem could be that if every application says it's connections need t=
o be check-pointed then there is no benefit.

Cheers,
-Tiru.

> -----Original Message-----
> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
> Sent: Wednesday, November 06, 2013 12:33 AM
> To: pcp@ietf.org
> Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-
> 00.txt
>=20
> Hi All,
>=20
> This draft talks about issues with checkpointing flows in current
> deployment, and how they can be addressed and handled efficiently with PC=
P.
> Please review and share your comments.
>=20
> Thanks
> Suresh
>=20
> On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
> <sureshk@juniper.net> wrote:
>=20
> >Dear All,
> >
> >We submitted a new draft that sketches flow high availability through PC=
P.
> >Please review.
> >
> >-Suresh
> >
> >On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
> ><internet-drafts@ietf.org> wrote:
> >
> >>
> >>A new version of I-D, draft-vinapamula-flow-ha-00.txt
> >>has been successfully submitted by Suresh Vinapamula and posted to the
> >>IETF repository.
> >>
> >>Filename:	 draft-vinapamula-flow-ha
> >>Revision:	 00
> >>Title:		 Flow high availability through PCP
> >>Creation date:	 2013-10-14
> >>Group:		 Individual Submission
> >>Number of pages: 5
> >>URL:
> >>http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.txt
> >>Status:          http://datatracker.ietf.org/doc/draft-vinapamula-flow-=
ha
> >>Htmlized:        http://tools.ietf.org/html/draft-vinapamula-flow-ha-00
> >>
> >>
> >>Abstract:
> >>   This document describes a mechanism for a host signal Network Addres=
s
> >>   Translator's (NAT) High Availability (HA) module to checkpoint
> >>   interested connections.
> >>
> >>
> >>
> >>
> >>
> >>Please note that it may take a couple of minutes from the time of
> >>submission
> >>until the htmlized version and diff are available at tools.ietf.org.
> >>
> >>The IETF Secretariat
> >>
> >>
> >>
> >
>=20
>=20


From sureshk@juniper.net  Thu Nov 14 10:03:40 2013
Return-Path: <sureshk@juniper.net>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8CB821E8118 for <pcp@ietfa.amsl.com>; Thu, 14 Nov 2013 10:03:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cW3CPmWTN7pU for <pcp@ietfa.amsl.com>; Thu, 14 Nov 2013 10:03:35 -0800 (PST)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe004.messaging.microsoft.com [216.32.180.187]) by ietfa.amsl.com (Postfix) with ESMTP id DACFA21E8063 for <pcp@ietf.org>; Thu, 14 Nov 2013 10:03:27 -0800 (PST)
Received: from mail31-co1-R.bigfish.com (10.243.78.232) by CO1EHSOBE016.bigfish.com (10.243.66.79) with Microsoft SMTP Server id 14.1.225.22; Thu, 14 Nov 2013 18:03:27 +0000
Received: from mail31-co1 (localhost [127.0.0.1])	by mail31-co1-R.bigfish.com (Postfix) with ESMTP id 3DCFB340476; Thu, 14 Nov 2013 18:03:27 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -27
X-BigFish: VPS-27(z579ehzbb2dI98dI9371I936eI542I1432I14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL17326ah8275bh8275dh1de097h186068hz2fh109h2a8h839h944he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1fe8h1ff5h209eh2216h1155h)
Received-SPF: pass (mail31-co1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=sureshk@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(377424004)(53754006)(479174003)(189002)(199002)(13464003)(377454003)(24454002)(51704005)(50986001)(81342001)(80022001)(83072001)(47736001)(85306002)(74706001)(76482001)(69226001)(83322001)(19580405001)(66066001)(74366001)(74662001)(47976001)(79102001)(77982001)(87936001)(47446002)(87266001)(63696002)(2656002)(59766001)(74876001)(31966008)(76786001)(74502001)(76796001)(4396001)(81816001)(46102001)(81686001)(81542001)(83506001)(54356001)(36756003)(51856001)(53806001)(56816003)(65816001)(54316002)(19580395003)(56776001)(49866001)(76176001)(80976001); DIR:OUT; SFP:; SCL:1; SRVR:DM2PR05MB285; H:DM2PR05MB288.namprd05.prod.outlook.com; CLIP:66.129.239.14; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail31-co1 (localhost.localdomain [127.0.0.1]) by mail31-co1 (MessageSwitch) id 1384452205351157_28075; Thu, 14 Nov 2013 18:03:25 +0000 (UTC)
Received: from CO1EHSMHS032.bigfish.com (unknown [10.243.78.237])	by mail31-co1.bigfish.com (Postfix) with ESMTP id 51B27BE0074; Thu, 14 Nov 2013 18:03:25 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by CO1EHSMHS032.bigfish.com (10.243.66.42) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 14 Nov 2013 18:03:25 +0000
Received: from DM2PR05MB285.namprd05.prod.outlook.com (10.141.101.21) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.371.2; Thu, 14 Nov 2013 18:03:24 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com (10.141.101.11) by DM2PR05MB285.namprd05.prod.outlook.com (10.141.101.21) with Microsoft SMTP Server (TLS) id 15.0.800.7; Thu, 14 Nov 2013 18:03:21 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) by DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) with mapi id 15.00.0800.005; Thu, 14 Nov 2013 18:03:21 +0000
From: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHO2lmbQ60NWXm7bU68b/cwqgHqfJok5Y+A//+nOIA=
Date: Thu, 14 Nov 2013 18:03:20 +0000
Message-ID: <CEAA3D67.27D19%sureshk@juniper.net>
In-Reply-To: <913383AAA69FF945B8F946018B75898A24263C93@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [66.129.239.14]
x-forefront-prvs: 0030839EEE
Content-Type: text/plain; charset="us-ascii"
Content-ID: <725A048D8FC7AD4DB6EC5FC7B7F46EAA@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Nov 2013 18:03:40 -0000

Hi Tiru,=20

Thanks for your comments. Please see inline for responses.

On 11/14/13 7:21 AM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
wrote:

>Hi Suresh,
>
>My initial comments
>
>1)Why cannot the problem be solved for example by the PCP client sending
>PEER with a long lifetime and if the lifetime is higher than a particular
>threshold only those connections are synced implicitly ?
How would application know what is the threshold life time for it to
request life time greater than that? What if a connection is critical but
is short lived than the configured HA life time? Similarly, what if a
connection is not business critical, but its life time greater than
configured HA life time?
>
>2)HA is applicable for both NAT and Firewall devices. I would suggest not
>to restrict the draft to only NAT scenarios.
Yes, the intention is to not restrict to NAT only service.
>
>3)In Active-Standby HA, switch-over is triggered not just because of
>Active rebooting but also because of WAN-link failures. Are you assuming
>HA deployments with provider-independent or provider-dependent addresses ?
I am not sure what you meant by provider-independent or provider-dependent
addresses. Please clarify for my response.
>
>4)
>
>a) PCP third-party authorization (draft-wing-pcp-third-party-authz) could
>also be one way of telling the network that it's for a business critical
>application and connection can be synced implicitly without explicit
>signaling.
Even without authorization also, if flows are to be check pointed, they
will be check pointed with this option.
>=20
>
>b) Other possible ways could be checkpoint based on destination
>port/address (For example HTTPS flows are more critical than HTTP).
Admin can always configure that. This option gives more flexibility.
>
>5)How does PCP ANNOUNCE work in this deployment ?
>I mean some connections on the host need to know that PCP-aware
>NAT/Firewall has rebooted but other connections may not because their
>states are check-pointed.
I will get back to you on this.
>
>6) How does an application developer know if syncing the state is
>required or not ?
>The problem could be that if every application says it's connections need
>to be check-pointed then there is no benefit.
It is application and user dependent. Please refer section 7 in the draft.
>
>Cheers,
>-Tiru.
>
>> -----Original Message-----
>> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
>> Sent: Wednesday, November 06, 2013 12:33 AM
>> To: pcp@ietf.org
>> Subject: Re: [pcp] New Version Notification for
>>draft-vinapamula-flow-ha-
>> 00.txt
>>=20
>> Hi All,
>>=20
>> This draft talks about issues with checkpointing flows in current
>> deployment, and how they can be addressed and handled efficiently with
>>PCP.
>> Please review and share your comments.
>>=20
>> Thanks
>> Suresh
>>=20
>> On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
>> <sureshk@juniper.net> wrote:
>>=20
>> >Dear All,
>> >
>> >We submitted a new draft that sketches flow high availability through
>>PCP.
>> >Please review.
>> >
>> >-Suresh
>> >
>> >On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
>> ><internet-drafts@ietf.org> wrote:
>> >
>> >>
>> >>A new version of I-D, draft-vinapamula-flow-ha-00.txt
>> >>has been successfully submitted by Suresh Vinapamula and posted to the
>> >>IETF repository.
>> >>
>> >>Filename:	 draft-vinapamula-flow-ha
>> >>Revision:	 00
>> >>Title:		 Flow high availability through PCP
>> >>Creation date:	 2013-10-14
>> >>Group:		 Individual Submission
>> >>Number of pages: 5
>> >>URL:
>> >>http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.txt
>> >>Status:      =20
>>http://datatracker.ietf.org/doc/draft-vinapamula-flow-ha
>> >>Htmlized:    =20
>>http://tools.ietf.org/html/draft-vinapamula-flow-ha-00
>> >>
>> >>
>> >>Abstract:
>> >>   This document describes a mechanism for a host signal Network
>>Address
>> >>   Translator's (NAT) High Availability (HA) module to checkpoint
>> >>   interested connections.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>Please note that it may take a couple of minutes from the time of
>> >>submission
>> >>until the htmlized version and diff are available at tools.ietf.org.
>> >>
>> >>The IETF Secretariat
>> >>
>> >>
>> >>
>> >
>>=20
>>=20
>
>
>



From tireddy@cisco.com  Fri Nov 15 19:57:29 2013
Return-Path: <tireddy@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAD4311E820A for <pcp@ietfa.amsl.com>; Fri, 15 Nov 2013 19:57:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id krFLF+gYrHer for <pcp@ietfa.amsl.com>; Fri, 15 Nov 2013 19:57:22 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id B7AB811E8168 for <pcp@ietf.org>; Fri, 15 Nov 2013 19:57:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5736; q=dns/txt; s=iport; t=1384574240; x=1385783840; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=5L1tLv9dmhQQsvR37nYW0j48DdJsXLTPz6hls/IcDbs=; b=LfzZ10N3LvVXmNpBnaaPgQ1sG752eKXZC6m5IhBQzI97bA0phy+fDkAt QT7cSVzD04wngQE6e9yMtH/0wxvhXNkT2lDJ92cac33kp4VV4jtxpxwm5 wEhjIWmCHOI9MOom7z8e/xaNnWgITZpZiUdM/Y+F9SidvSue5pqzhHeir o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FAGPshlKtJXG//2dsb2JhbABZgwc4U78sgSsWdIIlAQEBAwE6PQcHBAIBCBEEAQEBChQJBzIUCQgCBAESCAEQh2IGDcEKjzg4BoMagREDmT+QXoMogio
X-IronPort-AV: E=Sophos;i="4.93,711,1378857600"; d="scan'208";a="94488207"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by mtv-iport-1.cisco.com with ESMTP; 16 Nov 2013 03:57:19 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id rAG3vJG8011327 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 16 Nov 2013 03:57:19 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.47]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0123.003; Fri, 15 Nov 2013 21:57:19 -0600
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHO2mGhjLsh300HAEimsEM4ztlxb5oksKawgADGxgCAAGVBwA==
Date: Sat, 16 Nov 2013 03:57:19 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A24264F74@xmb-rcd-x10.cisco.com>
References: <913383AAA69FF945B8F946018B75898A24263C93@xmb-rcd-x10.cisco.com> <CEAA3D67.27D19%sureshk@juniper.net>
In-Reply-To: <CEAA3D67.27D19%sureshk@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.58.211]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Nov 2013 03:57:31 -0000

Hi Suresh,

Please see inline

> -----Original Message-----
> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
> Sent: Thursday, November 14, 2013 11:33 PM
> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
> Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-
> 00.txt
>=20
> Hi Tiru,
>=20
> Thanks for your comments. Please see inline for responses.
>=20
> On 11/14/13 7:21 AM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
> wrote:
>=20
> >Hi Suresh,
> >
> >My initial comments
> >
> >1)Why cannot the problem be solved for example by the PCP client sending
> >PEER with a long lifetime and if the lifetime is higher than a particula=
r
> >threshold only those connections are synced implicitly ?
> How would application know what is the threshold life time for it to
> request life time greater than that? What if a connection is critical but
> is short lived than the configured HA life time?=20

Good point. we don't want short-lived business critical sessions to set lon=
g lifetime just for HA.

> Similarly, what if a
> connection is not business critical, but its life time greater than
> configured HA life time?

The problem is how does the network know that the mapping is for a business=
 critical application or not ?
Network needs a mechanism to distinguish b/w the applications.

> >
> >2)HA is applicable for both NAT and Firewall devices. I would suggest no=
t
> >to restrict the draft to only NAT scenarios.
> Yes, the intention is to not restrict to NAT only service.
> >
> >3)In Active-Standby HA, switch-over is triggered not just because of
> >Active rebooting but also because of WAN-link failures. Are you assuming
> >HA deployments with provider-independent or provider-dependent addresses=
 ?
> I am not sure what you meant by provider-independent or provider-dependen=
t
> addresses. Please clarify for my response.

Refer to http://tools.ietf.org/html/rfc4116 on PI and PA.

> >
> >4)
> >
> >a) PCP third-party authorization (draft-wing-pcp-third-party-authz) coul=
d
> >also be one way of telling the network that it's for a business critical
> >application and connection can be synced implicitly without explicit
> >signaling.

> Even without authorization also, if flows are to be check pointed, they
> will be check pointed with this option.

With third party authorization, PCP-aware server knows that the mapping is =
for business critical applications and hence can sync the state.

> >
> >
> >b) Other possible ways could be checkpoint based on destination
> >port/address (For example HTTPS flows are more critical than HTTP).
> Admin can always configure that. This option gives more flexibility.
> >
> >5)How does PCP ANNOUNCE work in this deployment ?
> >I mean some connections on the host need to know that PCP-aware
> >NAT/Firewall has rebooted but other connections may not because their
> >states are check-pointed.
> I will get back to you on this.

Ok.

> >
> >6) How does an application developer know if syncing the state is
> >required or not ?
> >The problem could be that if every application says it's connections nee=
d
> >to be check-pointed then there is no benefit.
> It is application and user dependent. Please refer section 7 in the draft=
.

The problem is every App developer would think that his application is impo=
rtant and asks for HA. A set of guidelines is probably needed in the draft =
for application developers to help decide when to ask for HA or not ?

-Tiru.

> >
> >Cheers,
> >-Tiru.
> >
> >> -----Original Message-----
> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
> >> Sent: Wednesday, November 06, 2013 12:33 AM
> >> To: pcp@ietf.org
> >> Subject: Re: [pcp] New Version Notification for
> >>draft-vinapamula-flow-ha-
> >> 00.txt
> >>
> >> Hi All,
> >>
> >> This draft talks about issues with checkpointing flows in current
> >> deployment, and how they can be addressed and handled efficiently with
> >>PCP.
> >> Please review and share your comments.
> >>
> >> Thanks
> >> Suresh
> >>
> >> On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
> >> <sureshk@juniper.net> wrote:
> >>
> >> >Dear All,
> >> >
> >> >We submitted a new draft that sketches flow high availability through
> >>PCP.
> >> >Please review.
> >> >
> >> >-Suresh
> >> >
> >> >On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
> >> ><internet-drafts@ietf.org> wrote:
> >> >
> >> >>
> >> >>A new version of I-D, draft-vinapamula-flow-ha-00.txt
> >> >>has been successfully submitted by Suresh Vinapamula and posted to t=
he
> >> >>IETF repository.
> >> >>
> >> >>Filename:	 draft-vinapamula-flow-ha
> >> >>Revision:	 00
> >> >>Title:		 Flow high availability through PCP
> >> >>Creation date:	 2013-10-14
> >> >>Group:		 Individual Submission
> >> >>Number of pages: 5
> >> >>URL:
> >> >>http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.txt
> >> >>Status:
> >>http://datatracker.ietf.org/doc/draft-vinapamula-flow-ha
> >> >>Htmlized:
> >>http://tools.ietf.org/html/draft-vinapamula-flow-ha-00
> >> >>
> >> >>
> >> >>Abstract:
> >> >>   This document describes a mechanism for a host signal Network
> >>Address
> >> >>   Translator's (NAT) High Availability (HA) module to checkpoint
> >> >>   interested connections.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>Please note that it may take a couple of minutes from the time of
> >> >>submission
> >> >>until the htmlized version and diff are available at tools.ietf.org.
> >> >>
> >> >>The IETF Secretariat
> >> >>
> >> >>
> >> >>
> >> >
> >>
> >>
> >
> >
> >
>=20


From tireddy@cisco.com  Sun Nov 17 05:37:05 2013
Return-Path: <tireddy@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2A7811E8D1F; Sun, 17 Nov 2013 05:37:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6NEhWjvpDG94; Sun, 17 Nov 2013 05:37:00 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id 82DD611E8CFC; Sun, 17 Nov 2013 05:36:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19617; q=dns/txt; s=iport; t=1384695417; x=1385905017; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=u3CA3DqnfYjEGmlhjM+o5qeuUq6S1IfkNDn2t1CiZ3c=; b=L2Aou3+7Gqd2ZP4RAU+Llr35WSvnMSrm0IoAEbh3B6A2WepNdFNQUu44 zONluOy+KJ10fLTngEh3yzhWgFMWven5eja533+L0AWq35t5R4gQ2t0BN xjT9+ghE8BMguBUeAoc4WggBGF/i8Yn/+nczjJfSVmPm2qroop1+oZ5xi U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjAHAFDGiFKtJXG+/2dsb2JhbABZgkNEOFOtBYlgiEWBEBZ0giUBAQEEAQEBJAZBCxACAQgOAwMBAQELAgkSByEGCxQJCAIEDgUIh2cDDw23QA2JOReMc4E0gREgDQQGAQkBgxaBEQOWJYMaiyaFOIMogWhC
X-IronPort-AV: E=Sophos;i="4.93,718,1378857600"; d="scan'208,217";a="145559"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by alln-iport-1.cisco.com with ESMTP; 17 Nov 2013 13:36:42 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id rAHDagKp007235 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 17 Nov 2013 13:36:42 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.47]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0123.003; Sun, 17 Nov 2013 07:36:42 -0600
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Oleg Moskalenko <mom040267@gmail.com>
Thread-Topic: [tram] First post
Thread-Index: AQHO4nrNOeLu8IlzsEisOVsWZS4tvJon2dyA//+cN3A=
Date: Sun, 17 Nov 2013 13:36:41 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A24265484@xmb-rcd-x10.cisco.com>
References: <CALDtMrK5X4euTOwwdGJNkOGEar1KdCXpZvOnR-MgJfnY1LzAKg@mail.gmail.com> <C17C5187-E20D-4AF5-97D2-B63ABCB2E298@cisco.com> <913383AAA69FF945B8F946018B75898A24264EF5@xmb-rcd-x10.cisco.com> <CALDtMrJW1-6vvkgREWdb-J3p3n2pM9UfULiaqGWMEQeq9Arikw@mail.gmail.com>
In-Reply-To: <CALDtMrJW1-6vvkgREWdb-J3p3n2pM9UfULiaqGWMEQeq9Arikw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.44.182]
Content-Type: multipart/alternative; boundary="_000_913383AAA69FF945B8F946018B75898A24265484xmbrcdx10ciscoc_"
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>, "tram@ietf.org" <tram@ietf.org>, Justin Uberti <juberti@google.com>
Subject: Re: [pcp] [tram] First post
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Nov 2013 13:37:05 -0000

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

Hi Oleg,

It has some similarities but is a lot different from PCP third party author=
ization. For example for TURN the Authorization Server will be providing se=
ssion key, MAC algorithm etc which is not required with the PCP third party=
 authorization.  There are various other differences like PCP server would =
need to communicate with the Authorization Server to determine the token bo=
und authorization data  (like the number of mappings permitted, flow charac=
teristics allowed etc) which may not be required with TURN authorization.  =
PCP-controlled Firewall will most likely be in the same administrative doma=
in as the endpoint but that may not be true with TURN.

we are working on the the details and will have something concrete in coupl=
e of weeks.

Cheers,
-Tiru.
From: tram-bounces@ietf.org [mailto:tram-bounces@ietf.org] On Behalf Of Ole=
g Moskalenko
Sent: Saturday, November 16, 2013 12:56 PM
To: Tirumaleswar Reddy (tireddy)
Cc: Simon Perreault; tram@ietf.org; Justin Uberti
Subject: Re: [tram] First post

Tiru, I suppose that will be similar to this draft:

http://tools.ietf.org/html/draft-wing-pcp-third-party-authz-01
That would be a significant addition to the TURN server.
Regards,
Oleg


On Fri, Nov 15, 2013 at 7:20 PM, Tirumaleswar Reddy (tireddy) <tireddy@cisc=
o.com<mailto:tireddy@cisco.com>> wrote:
Hi Oleg,

I am co-author of the MICE, draft-reddy-behave-turn-auth drafts and we are =
interested in TURN evolution. Justin and we are working on TURN Extension f=
or Third Party Authorization using OAuth which will address some of the pro=
blems discussed in above draft.

Cheers,
-Tiru.

From: Oleg Moskalenko <mom040267@gmail.com<mailto:mom040267@gmail.com>>
Subject: Re: [tram] First post
Date: November 15, 2013 11:01:24 AM PST
To: Simon Perreault <simon.perreault@viagenie.ca<mailto:simon.perreault@via=
genie.ca>>
Cc: <tram@ietf.org<mailto:tram@ietf.org>>

MMUSIC has an interesting draft on TURN mobility (MICE) that I am watching =
and I am going to implement. I wonder whether the authors of the draft may =
be interested in the TURN evolution.

On Fri, Nov 15, 2013 at 10:55 AM, Simon Perreault <simon.perreault@viagenie=
.ca<mailto:simon.perreault@viagenie.ca>> wrote:
All,

Any objection against sending the following to rtcweb, pntaw, and behave? A=
ny other lists that should be included?

Simon

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

All,

A few of us have been working on a proposal for a new working group that wo=
uld focus on enhancements to STUN and TURN. The proposed name is TRAM (Turn=
 Revised And Modernized) and discussion is happening in <tram@ietf.org<mail=
to:tram@ietf.org>>.
Subscribe link: <https://www.ietf.org/mailman/listinfo/tram>

Here is the charter we have been working on. If you would like to comment a=
nd/or get involved, please do so on the TRAM mailing list.

Simon (and many others!)
Turn Revised And Modernized (tram)
----------------------------------

Traversal Using Relays around NAT (TURN) was published as RFC 5766 in April
2010.  Until recently the protocol had only a rather limited deployment.  T=
his
is primarily because its primary use case is as one of the NAT traversal
methods of the Interactive Connectivity Establishment (ICE) framework (RFC
5245).  This inherent dependency on ICE combined with the fact that ICE its=
elf
was slow to achieve widespread adoption because other alternative mechanism=
s
were historically used by the VoIP industry were the causes of the initial
lack of interest.  This situation has changed drastically as ICE, and
consequently TURN, are mandatory to implement in WebRTC, which is a set of
technologies developed at the IETF and W3C aiming to enable Real Time
Communication on the Web.

Because of the ubiquity of the Web and of the new opportunities created by =
the
arrival of WebRTC, there is a renewed interest in TURN and ICE, as evidence=
d by
the recent work updating the ICE framework, as well as standardizing the UR=
Is
used to access a STUN [RFC7064] or TURN [RFC7065] server.

The goal of the TRAM Working Group is to consolidate the various initiative=
s
to update TURN and STUN, including the definition of new transport and
authentication mechanisms that make STUN and TURN more suitable for the Web=
RTC
environment.  The Working Group will closely coordinate with the appropriat=
e
Working Groups, including RTCWEB, MMUSIC, and HTTPBIS.

The current list of deliverable is:

- DTLS transport for TURN

  Candidate draft: draft-petithuguenin-tram-turn-dtls

  TURN defines three transports: UDP, TCP, and TLS. A straightforward exten=
sion
  of this set is DTLS, enabling secure datagram-oriented transport.

- New authentication mechanism for TURN

  Problem analysis: draft-reddy-behave-turn-auth
  Candidate draft: draft-uberti-behave-turn-rest, OAuth has also been sugge=
sted

  The current authentication mechanism for TURN, which is reused from STUN,=
 has
  been designed with a SIP account database in mind. The new RTCWEB usages,
  which are mostly based on web applications, do not fit that model. A new
  authentication mechanism optimized for such web applications will be crea=
ted.

- TURN server auto-discovery mechanism for enterprise and ISPs

  Candidate draft: TBD

  Current TURN server discovery is based on the presence of SRV and/or NAPT=
R DNS
  records. These records are usually under the administrative control of th=
e
  application or service provider, not the enterprise or the ISP on whose
  network the client is situated. Enterprises or ISPs wishing to provide th=
eir
  own TURN server, in an attempt to reduce so-called "triangle routing", ne=
ed a
  new auto-discovery mechanism.

- STUN-bis

  Candidate draft: TBD

  A new revision of RFC 5389 will contain:

  - Various bug fixes
  - STUN hash algorithm agility (currently only SHA-1 is allowed)

- TURN-bis

  Candidate draft: TBD

  A new revision of RFC 5766 will contain:

  - Various bug fixes
  - Support for multi-tenant servers
    (Servers always send the same REALM attribute. No realm negotiation pha=
se
     currently exists.)

Goals and Milestones:

[TBD]

--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca
_______________________________________________
tram mailing list
tram@ietf.org<mailto:tram@ietf.org>
https://www.ietf.org/mailman/listinfo/tram

_______________________________________________
tram mailing list
tram@ietf.org<mailto:tram@ietf.org>
https://www.ietf.org/mailman/listinfo/tram


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Hi Oleg,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">It has some similarities but is a lot different from PCP thi=
rd party authorization. For example for TURN the Authorization Server will =
be providing session
 key, MAC algorithm etc which is not required with the PCP third party auth=
orization.&nbsp; There are various other differences like PCP server would =
need to communicate with the Authorization Server to determine the token bo=
und authorization data &nbsp;(like the number
 of mappings permitted, flow characteristics allowed etc) which may not be =
required with TURN authorization.&nbsp; PCP-controlled Firewall will most l=
ikely be in the same administrative domain as the endpoint but that may not=
 be true with TURN.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">we are working on the the details and will have something co=
ncrete in couple of weeks.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">-Tiru.<o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tram-bou=
nces@ietf.org [mailto:tram-bounces@ietf.org]
<b>On Behalf Of </b>Oleg Moskalenko<br>
<b>Sent:</b> Saturday, November 16, 2013 12:56 PM<br>
<b>To:</b> Tirumaleswar Reddy (tireddy)<br>
<b>Cc:</b> Simon Perreault; tram@ietf.org; Justin Uberti<br>
<b>Subject:</b> Re: [tram] First post<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Tiru, I suppose that =
will be similar to this draft:<br>
<br>
<a href=3D"http://tools.ietf.org/html/draft-wing-pcp-third-party-authz-01">=
http://tools.ietf.org/html/draft-wing-pcp-third-party-authz-01</a><o:p></o:=
p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">That would be a signi=
ficant addition to the TURN server.<o:p></o:p></p>
</div>
<p class=3D"MsoNormal">Regards,<br>
Oleg<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Fri, Nov 15, 2013 at 7:20 PM, Tirumaleswar Reddy =
(tireddy) &lt;<a href=3D"mailto:tireddy@cisco.com" target=3D"_blank">tiredd=
y@cisco.com</a>&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">Hi Oleg,<br>
<br>
I am co-author of the MICE, draft-reddy-behave-turn-auth drafts and we are =
interested in TURN evolution. Justin and we are working on TURN Extension f=
or Third Party Authorization using OAuth which will address some of the pro=
blems discussed in above draft.<br>
<br>
Cheers,<br>
-Tiru.<br>
<br>
From: Oleg Moskalenko &lt;<a href=3D"mailto:mom040267@gmail.com">mom040267@=
gmail.com</a>&gt;<br>
Subject: Re: [tram] First post<br>
Date: November 15, 2013 11:01:24 AM PST<br>
To: Simon Perreault &lt;<a href=3D"mailto:simon.perreault@viagenie.ca">simo=
n.perreault@viagenie.ca</a>&gt;<br>
Cc: &lt;<a href=3D"mailto:tram@ietf.org">tram@ietf.org</a>&gt;<o:p></o:p></=
p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
MMUSIC has an interesting draft on TURN mobility (MICE) that I am watching =
and I am going to implement. I wonder whether the authors of the draft may =
be interested in the TURN evolution.<br>
<br>
On Fri, Nov 15, 2013 at 10:55 AM, Simon Perreault &lt;<a href=3D"mailto:sim=
on.perreault@viagenie.ca">simon.perreault@viagenie.ca</a>&gt; wrote:<br>
All,<br>
<br>
Any objection against sending the following to rtcweb, pntaw, and behave? A=
ny other lists that should be included?<br>
<br>
Simon<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
All,<br>
<br>
A few of us have been working on a proposal for a new working group that wo=
uld focus on enhancements to STUN and TURN. The proposed name is TRAM (Turn=
 Revised And Modernized) and discussion is happening in &lt;<a href=3D"mail=
to:tram@ietf.org">tram@ietf.org</a>&gt;.<br>
Subscribe link: &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/tram" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/tram</a>&gt;<br>
<br>
Here is the charter we have been working on. If you would like to comment a=
nd/or get involved, please do so on the TRAM mailing list.<br>
<br>
Simon (and many others!)<br>
Turn Revised And Modernized (tram)<br>
----------------------------------<br>
<br>
Traversal Using Relays around NAT (TURN) was published as RFC 5766 in April=
<br>
2010. &nbsp;Until recently the protocol had only a rather limited deploymen=
t. &nbsp;This<br>
is primarily because its primary use case is as one of the NAT traversal<br=
>
methods of the Interactive Connectivity Establishment (ICE) framework (RFC<=
br>
5245). &nbsp;This inherent dependency on ICE combined with the fact that IC=
E itself<br>
was slow to achieve widespread adoption because other alternative mechanism=
s<br>
were historically used by the VoIP industry were the causes of the initial<=
br>
lack of interest. &nbsp;This situation has changed drastically as ICE, and<=
br>
consequently TURN, are mandatory to implement in WebRTC, which is a set of<=
br>
technologies developed at the IETF and W3C aiming to enable Real Time<br>
Communication on the Web.<br>
<br>
Because of the ubiquity of the Web and of the new opportunities created by =
the<br>
arrival of WebRTC, there is a renewed interest in TURN and ICE, as evidence=
d by<br>
the recent work updating the ICE framework, as well as standardizing the UR=
Is<br>
used to access a STUN [RFC7064] or TURN [RFC7065] server.<br>
<br>
The goal of the TRAM Working Group is to consolidate the various initiative=
s<br>
to update TURN and STUN, including the definition of new transport and<br>
authentication mechanisms that make STUN and TURN more suitable for the Web=
RTC<br>
environment. &nbsp;The Working Group will closely coordinate with the appro=
priate<br>
Working Groups, including RTCWEB, MMUSIC, and HTTPBIS.<br>
<br>
The current list of deliverable is:<br>
<br>
- DTLS transport for TURN<br>
<br>
&nbsp; Candidate draft: draft-petithuguenin-tram-turn-dtls<br>
<br>
&nbsp; TURN defines three transports: UDP, TCP, and TLS. A straightforward =
extension<br>
&nbsp; of this set is DTLS, enabling secure datagram-oriented transport.<br=
>
<br>
- New authentication mechanism for TURN<br>
<br>
&nbsp; Problem analysis: draft-reddy-behave-turn-auth<br>
&nbsp; Candidate draft: draft-uberti-behave-turn-rest, OAuth has also been =
suggested<br>
<br>
&nbsp; The current authentication mechanism for TURN, which is reused from =
STUN, has<br>
&nbsp; been designed with a SIP account database in mind. The new RTCWEB us=
ages,<br>
&nbsp; which are mostly based on web applications, do not fit that model. A=
 new<br>
&nbsp; authentication mechanism optimized for such web applications will be=
 created.<br>
<br>
- TURN server auto-discovery mechanism for enterprise and ISPs<br>
<br>
&nbsp; Candidate draft: TBD<br>
<br>
&nbsp; Current TURN server discovery is based on the presence of SRV and/or=
 NAPTR DNS<br>
&nbsp; records. These records are usually under the administrative control =
of the<br>
&nbsp; application or service provider, not the enterprise or the ISP on wh=
ose<br>
&nbsp; network the client is situated. Enterprises or ISPs wishing to provi=
de their<br>
&nbsp; own TURN server, in an attempt to reduce so-called &quot;triangle ro=
uting&quot;, need a<br>
&nbsp; new auto-discovery mechanism.<br>
<br>
- STUN-bis<br>
<br>
&nbsp; Candidate draft: TBD<br>
<br>
&nbsp; A new revision of RFC 5389 will contain:<br>
<br>
&nbsp; - Various bug fixes<br>
&nbsp; - STUN hash algorithm agility (currently only SHA-1 is allowed)<br>
<br>
- TURN-bis<br>
<br>
&nbsp; Candidate draft: TBD<br>
<br>
&nbsp; A new revision of RFC 5766 will contain:<br>
<br>
&nbsp; - Various bug fixes<br>
&nbsp; - Support for multi-tenant servers<br>
&nbsp; &nbsp; (Servers always send the same REALM attribute. No realm negot=
iation phase<br>
&nbsp; &nbsp; &nbsp;currently exists.)<br>
<br>
Goals and Milestones:<br>
<br>
[TBD]<br>
<br>
--<br>
DTN made easy, lean, and smart --&gt; <a href=3D"http://postellation.viagen=
ie.ca" target=3D"_blank">
http://postellation.viagenie.ca</a><br>
NAT64/DNS64 open-source &nbsp; &nbsp; &nbsp; &nbsp;--&gt; <a href=3D"http:/=
/ecdysis.viagenie.ca" target=3D"_blank">
http://ecdysis.viagenie.ca</a><br>
STUN/TURN server &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; --&gt; <a=
 href=3D"http://numb.viagenie.ca" target=3D"_blank">
http://numb.viagenie.ca</a><br>
_______________________________________________<br>
tram mailing list<br>
<a href=3D"mailto:tram@ietf.org">tram@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tram" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/tram</a><br>
<br>
_______________________________________________<br>
tram mailing list<br>
<a href=3D"mailto:tram@ietf.org">tram@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tram" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/tram</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_913383AAA69FF945B8F946018B75898A24265484xmbrcdx10ciscoc_--

From sureshk@juniper.net  Sun Nov 17 14:48:36 2013
Return-Path: <sureshk@juniper.net>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E800511E82D9 for <pcp@ietfa.amsl.com>; Sun, 17 Nov 2013 14:48:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1PSy1CFV48Nl for <pcp@ietfa.amsl.com>; Sun, 17 Nov 2013 14:48:31 -0800 (PST)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0251.outbound.messaging.microsoft.com [213.199.154.251]) by ietfa.amsl.com (Postfix) with ESMTP id 340E011E8153 for <pcp@ietf.org>; Sun, 17 Nov 2013 14:48:31 -0800 (PST)
Received: from mail32-db9-R.bigfish.com (10.174.16.244) by DB9EHSOBE030.bigfish.com (10.174.14.93) with Microsoft SMTP Server id 14.1.225.22; Sun, 17 Nov 2013 22:48:28 +0000
Received: from mail32-db9 (localhost [127.0.0.1])	by mail32-db9-R.bigfish.com (Postfix) with ESMTP id 38AAE26021E; Sun, 17 Nov 2013 22:48:28 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -27
X-BigFish: VPS-27(z579ehzbb2dI98dI9371I936eI542I1432I14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL17326ah8275bh8275dh1de097h186068hz2fh109h2a8h839h944he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1fe8h1ff5h209eh2216h1155h)
Received-SPF: pass (mail32-db9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=sureshk@juniper.net; helo=BL2PRD0510HT002.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(377454003)(377424004)(53754006)(189002)(199002)(479174003)(13464003)(51704005)(24454002)(87266001)(87936001)(83072001)(81542001)(54356001)(63696002)(74502001)(77982001)(47446002)(76796001)(56816003)(76786001)(47736001)(19580395003)(53806001)(31966008)(69226001)(59766001)(81342001)(51856001)(83506001)(46102001)(15202345003)(2656002)(74662001)(79102001)(15975445006)(56776001)(81686001)(81816001)(36756003)(54316002)(83322001)(4396001)(49866001)(76482001)(76176001)(19580405001)(74876001)(66066001)(65816001)(85306002)(80022001)(80976001)(50986001)(47976001)(74706001)(74366001); DIR:OUT; SFP:; SCL:1; SRVR:DM2PR05MB285; H:DM2PR05MB288.namprd05.prod.outlook.com; CLIP:66.129.239.14; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail32-db9 (localhost.localdomain [127.0.0.1]) by mail32-db9 (MessageSwitch) id 1384728505716968_12917; Sun, 17 Nov 2013 22:48:25 +0000 (UTC)
Received: from DB9EHSMHS013.bigfish.com (unknown [10.174.16.247])	by mail32-db9.bigfish.com (Postfix) with ESMTP id A7CB9460070; Sun, 17 Nov 2013 22:48:25 +0000 (UTC)
Received: from BL2PRD0510HT002.namprd05.prod.outlook.com (157.56.240.101) by DB9EHSMHS013.bigfish.com (10.174.14.23) with Microsoft SMTP Server (TLS) id 14.16.227.3; Sun, 17 Nov 2013 22:48:25 +0000
Received: from DM2PR05MB285.namprd05.prod.outlook.com (10.141.101.21) by BL2PRD0510HT002.namprd05.prod.outlook.com (10.255.100.37) with Microsoft SMTP Server (TLS) id 14.16.383.1; Sun, 17 Nov 2013 22:48:23 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com (10.141.101.11) by DM2PR05MB285.namprd05.prod.outlook.com (10.141.101.21) with Microsoft SMTP Server (TLS) id 15.0.800.7; Sun, 17 Nov 2013 22:48:21 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) by DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) with mapi id 15.00.0800.005; Sun, 17 Nov 2013 22:48:21 +0000
From: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHO2lmbQ60NWXm7bU68b/cwqgHqfJok5Y+A//+nOICAAr5pgIACSDUA
Date: Sun, 17 Nov 2013 22:48:20 +0000
Message-ID: <CEAE5D46.2833B%sureshk@juniper.net>
In-Reply-To: <913383AAA69FF945B8F946018B75898A24264F74@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [66.129.239.14]
x-forefront-prvs: 0033AAD26D
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F29B941F97F02140BA0D9A9424F8FD36@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Nov 2013 22:48:37 -0000

Hi Tiru,=20

Thanks for your followup questions. Please see responses inline.

On 11/15/13 7:57 PM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
wrote:

>Hi Suresh,
>
>Please see inline
>
>> -----Original Message-----
>> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
>> Sent: Thursday, November 14, 2013 11:33 PM
>> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
>> Subject: Re: [pcp] New Version Notification for
>>draft-vinapamula-flow-ha-
>> 00.txt
>>=20
>> Hi Tiru,
>>=20
>> Thanks for your comments. Please see inline for responses.
>>=20
>> On 11/14/13 7:21 AM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
>> wrote:
>>=20
>> >Hi Suresh,
>> >
>> >My initial comments
>> >
>> >1)Why cannot the problem be solved for example by the PCP client
>>sending
>> >PEER with a long lifetime and if the lifetime is higher than a
>>particular
>> >threshold only those connections are synced implicitly ?
>> How would application know what is the threshold life time for it to
>> request life time greater than that? What if a connection is critical
>>but
>> is short lived than the configured HA life time?
>
>Good point. we don't want short-lived business critical sessions to set
>long lifetime just for HA.
>
>> Similarly, what if a
>> connection is not business critical, but its life time greater than
>> configured HA life time?
>
>The problem is how does the network know that the mapping is for a
>business critical application or not ?
>Network needs a mechanism to distinguish b/w the applications.
A bit in the PCP header indicates that it is critical right? An
application can use PCP medium to communicate to network about this.
>
>> >
>> >2)HA is applicable for both NAT and Firewall devices. I would suggest
>>not
>> >to restrict the draft to only NAT scenarios.
>> Yes, the intention is to not restrict to NAT only service.
>> >
>> >3)In Active-Standby HA, switch-over is triggered not just because of
>> >Active rebooting but also because of WAN-link failures. Are you
>>assuming
>> >HA deployments with provider-independent or provider-dependent
>>addresses ?
>> I am not sure what you meant by provider-independent or
>>provider-dependent
>> addresses. Please clarify for my response.
>
>Refer to http://tools.ietf.org/html/rfc4116 on PI and PA.
Oh, you meant provider aggregatable and provider independent. Are you
talking in the context of multihoming?
Isn't this taken care at link level or route level redundancy/update? If
not, sorry, I am trying to understand your question.
>
>> >
>> >4)
>> >
>> >a) PCP third-party authorization (draft-wing-pcp-third-party-authz)
>>could
>> >also be one way of telling the network that it's for a business
>>critical
>> >application and connection can be synced implicitly without explicit
>> >signaling.
>
>> Even without authorization also, if flows are to be check pointed, they
>> will be check pointed with this option.
>
>With third party authorization, PCP-aware server knows that the mapping
>is for business critical applications and hence can sync the state.
AFAIU, this draft doesn't talk that third party authorization is for
business critical applications only. Please let me know if I am missing
something?
>
>> >
>> >
>> >b) Other possible ways could be checkpoint based on destination
>> >port/address (For example HTTPS flows are more critical than HTTP).
>> Admin can always configure that. This option gives more flexibility.
>> >
>> >5)How does PCP ANNOUNCE work in this deployment ?
>> >I mean some connections on the host need to know that PCP-aware
>> >NAT/Firewall has rebooted but other connections may not because their
>> >states are check-pointed.
>> I will get back to you on this.
>
>Ok.
I feel all connections should refresh their mappings just as how they do
on seeing PCP ANNOUNCE.
For the mappings that are already check pointed, applications are
guaranteed to receive previous state of the mappings.
For the mappings that are not check pointed, depending on availability
they will be honored on first come first serve basis.
Is there an issue with this, so that I can update in the next version.
>
>> >
>> >6) How does an application developer know if syncing the state is
>> >required or not ?
>> >The problem could be that if every application says it's connections
>>need
>> >to be check-pointed then there is no benefit.
>> It is application and user dependent. Please refer section 7 in the
>>draft.
>
>The problem is every App developer would think that his application is
>important and asks for HA. A set of guidelines is probably needed in the
>draft for application developers to help decide when to ask for HA or not
>?
Ok, I will include the guide lines in the next draft. But, note for some
set of applications, an application that is critical to one user may not
be critical to another user. That is where both user/application have to
determine if it is critical. And as a security consideration, admin may
configure max checkpoints per user. Please comment, so I will update it in
the next version of draft.
>
>-Tiru.
>
>> >
>> >Cheers,
>> >-Tiru.
>> >
>> >> -----Original Message-----
>> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
>> >> Sent: Wednesday, November 06, 2013 12:33 AM
>> >> To: pcp@ietf.org
>> >> Subject: Re: [pcp] New Version Notification for
>> >>draft-vinapamula-flow-ha-
>> >> 00.txt
>> >>
>> >> Hi All,
>> >>
>> >> This draft talks about issues with checkpointing flows in current
>> >> deployment, and how they can be addressed and handled efficiently
>>with
>> >>PCP.
>> >> Please review and share your comments.
>> >>
>> >> Thanks
>> >> Suresh
>> >>
>> >> On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
>> >> <sureshk@juniper.net> wrote:
>> >>
>> >> >Dear All,
>> >> >
>> >> >We submitted a new draft that sketches flow high availability
>>through
>> >>PCP.
>> >> >Please review.
>> >> >
>> >> >-Suresh
>> >> >
>> >> >On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
>> >> ><internet-drafts@ietf.org> wrote:
>> >> >
>> >> >>
>> >> >>A new version of I-D, draft-vinapamula-flow-ha-00.txt
>> >> >>has been successfully submitted by Suresh Vinapamula and posted to
>>the
>> >> >>IETF repository.
>> >> >>
>> >> >>Filename:	 draft-vinapamula-flow-ha
>> >> >>Revision:	 00
>> >> >>Title:		 Flow high availability through PCP
>> >> >>Creation date:	 2013-10-14
>> >> >>Group:		 Individual Submission
>> >> >>Number of pages: 5
>> >> >>URL:
>> >> >>http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.txt
>> >> >>Status:
>> >>http://datatracker.ietf.org/doc/draft-vinapamula-flow-ha
>> >> >>Htmlized:
>> >>http://tools.ietf.org/html/draft-vinapamula-flow-ha-00
>> >> >>
>> >> >>
>> >> >>Abstract:
>> >> >>   This document describes a mechanism for a host signal Network
>> >>Address
>> >> >>   Translator's (NAT) High Availability (HA) module to checkpoint
>> >> >>   interested connections.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>Please note that it may take a couple of minutes from the time of
>> >> >>submission
>> >> >>until the htmlized version and diff are available at
>>tools.ietf.org.
>> >> >>
>> >> >>The IETF Secretariat
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >
>> >
>> >
>>=20
>
>
>



From tireddy@cisco.com  Mon Nov 18 17:53:15 2013
Return-Path: <tireddy@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B32F71AE98F for <pcp@ietfa.amsl.com>; Mon, 18 Nov 2013 17:53:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.026
X-Spam-Level: 
X-Spam-Status: No, score=-15.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pxfuN9m_ed2h for <pcp@ietfa.amsl.com>; Mon, 18 Nov 2013 17:53:12 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id A94591AE9B7 for <pcp@ietf.org>; Mon, 18 Nov 2013 17:53:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9566; q=dns/txt; s=iport; t=1384825986; x=1386035586; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=SHywHHqojWx0MpU9IvAKeZYH689x64B2d0S3lyEiJeI=; b=OPe2hVPascMsZ1mGXc6TZ87tZcP8eOC9nRMAmbSgdo5lJd+CgziAfQrJ Lmk/0gZZ3KziQHcZPzE939VF9IwJvbtEIljzoIKFwIMDO3vaLvBi1qozx xaL66QCi/T/3Lb269afsLO1yNh2BRd6VdWG/2wC0189KmtH3waHyYlEvX U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwFAFXDilKtJXG//2dsb2JhbABPCoMHOFO/N4EdFnSCJQEBAQMBOjYHBwcEAgEIEQQBAQEKFAkHMhQJCAIEARIIARCHYgYNwh0XjhQPgRUsDAaDGoERA5k/kF6DKIIq
X-IronPort-AV: E=Sophos;i="4.93,727,1378857600"; d="scan'208";a="286003115"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-3.cisco.com with ESMTP; 19 Nov 2013 01:53:05 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id rAJ1r5Ri024698 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Nov 2013 01:53:05 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.47]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0123.003; Mon, 18 Nov 2013 19:53:05 -0600
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHO2mGhjLsh300HAEimsEM4ztlxb5oksKawgADGxgCAAGVBwIAEoV4A///YwdA=
Date: Tue, 19 Nov 2013 01:53:04 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A24267498@xmb-rcd-x10.cisco.com>
References: <913383AAA69FF945B8F946018B75898A24264F74@xmb-rcd-x10.cisco.com> <CEAE5D46.2833B%sureshk@juniper.net>
In-Reply-To: <CEAE5D46.2833B%sureshk@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.67.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 01:53:15 -0000

Hi Suresh,

Please see inline

> -----Original Message-----
> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
> Sent: Monday, November 18, 2013 4:18 AM
> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
> Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-
> 00.txt
>=20
> Hi Tiru,
>=20
> Thanks for your followup questions. Please see responses inline.
>=20
> On 11/15/13 7:57 PM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
> wrote:
>=20
> >Hi Suresh,
> >
> >Please see inline
> >
> >> -----Original Message-----
> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
> >> Sent: Thursday, November 14, 2013 11:33 PM
> >> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
> >> Subject: Re: [pcp] New Version Notification for
> >>draft-vinapamula-flow-ha-
> >> 00.txt
> >>
> >> Hi Tiru,
> >>
> >> Thanks for your comments. Please see inline for responses.
> >>
> >> On 11/14/13 7:21 AM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com=
>
> >> wrote:
> >>
> >> >Hi Suresh,
> >> >
> >> >My initial comments
> >> >
> >> >1)Why cannot the problem be solved for example by the PCP client
> >>sending
> >> >PEER with a long lifetime and if the lifetime is higher than a
> >>particular
> >> >threshold only those connections are synced implicitly ?
> >> How would application know what is the threshold life time for it to
> >> request life time greater than that? What if a connection is critical
> >>but
> >> is short lived than the configured HA life time?
> >
> >Good point. we don't want short-lived business critical sessions to set
> >long lifetime just for HA.
> >
> >> Similarly, what if a
> >> connection is not business critical, but its life time greater than
> >> configured HA life time?
> >
> >The problem is how does the network know that the mapping is for a
> >business critical application or not ?
> >Network needs a mechanism to distinguish b/w the applications.
> A bit in the PCP header indicates that it is critical right ? An
> application can use PCP medium to communicate to network about this.

The problem is any application can set this bit. How does the network disti=
nguish b/w applications ?

> >
> >> >
> >> >2)HA is applicable for both NAT and Firewall devices. I would suggest
> >>not
> >> >to restrict the draft to only NAT scenarios.
> >> Yes, the intention is to not restrict to NAT only service.
> >> >
> >> >3)In Active-Standby HA, switch-over is triggered not just because of
> >> >Active rebooting but also because of WAN-link failures. Are you
> >>assuming
> >> >HA deployments with provider-independent or provider-dependent
> >>addresses ?
> >> I am not sure what you meant by provider-independent or
> >>provider-dependent
> >> addresses. Please clarify for my response.
> >
> >Refer to http://tools.ietf.org/html/rfc4116 on PI and PA.
> Oh, you meant provider aggregatable and provider independent. Are you
> talking in the context of multi-homing ?

Yes.

> Isn't this taken care at link level or route level redundancy/update? If
> not, sorry, I am trying to understand your question.

If you could add to the Appendix the deployment scenarios you had considere=
d that would help.
I was thinking of (Active-Standby) with multiple WAN links (Primary and Bac=
kup).

> >
> >> >
> >> >4)
> >> >
> >> >a) PCP third-party authorization (draft-wing-pcp-third-party-authz)
> >>could
> >> >also be one way of telling the network that it's for a business
> >>critical
> >> >application and connection can be synced implicitly without explicit
> >> >signaling.
> >
> >> Even without authorization also, if flows are to be check pointed, the=
y
> >> will be check pointed with this option.
> >
> >With third party authorization, PCP-aware server knows that the mapping
> >is for business critical applications and hence can sync the state.
> AFAIU, this draft doesn't talk that third party authorization is for
> business critical applications only. Please let me know if I am missing
> something ?

One application may be business critical in one domain and may not be anoth=
er domain. For example let's say WebRTC calls to Stark Industries may be bu=
siness critical in one Enterprise but there is no business tie-up for Stark=
 in another Enterprise and hence not business critical.

How does the PCP client set/reset this flag based on which network the BYOD=
 device is attached to ?

> >
> >> >
> >> >
> >> >b) Other possible ways could be checkpoint based on destination
> >> >port/address (For example HTTPS flows are more critical than HTTP).
> >> Admin can always configure that. This option gives more flexibility.
> >> >
> >> >5)How does PCP ANNOUNCE work in this deployment ?
> >> >I mean some connections on the host need to know that PCP-aware
> >> >NAT/Firewall has rebooted but other connections may not because their
> >> >states are check-pointed.
> >> I will get back to you on this.
> >
> >Ok.
> I feel all connections should refresh their mappings just as how they do
> on seeing PCP ANNOUNCE.
> For the mappings that are already check pointed, applications are
> guaranteed to receive previous state of the mappings.

So check-pointed application will ignore PCP ANNOUNCE ?

> For the mappings that are not check pointed, depending on availability
> they will be honored on first come first serve basis.
> Is there an issue with this, so that I can update in the next version.

This may work, you may want to explicitly mention the above information in =
the draft.

> >
> >> >
> >> >6) How does an application developer know if syncing the state is
> >> >required or not ?
> >> >The problem could be that if every application says it's connections
> >>need
> >> >to be check-pointed then there is no benefit.
> >> It is application and user dependent. Please refer section 7 in the
> >>draft.
> >
> >The problem is every App developer would think that his application is
> >important and asks for HA. A set of guidelines is probably needed in the
> >draft for application developers to help decide when to ask for HA or no=
t
> >?
> Ok, I will include the guide lines in the next draft. But, note for some
> set of applications, an application that is critical to one user may not
> be critical to another user. That is where both user/application have to
> determine if it is critical.

I think there is one more aspect to consider, if the application can surviv=
e PCP server crash. For example if application based on PCP ANNOUNCE can do=
 state resumption or application is using multiple paths (MPTCP) that thoug=
h it is a business critical application but does not need to ask for check-=
pointing the connection.

> And as a security consideration, admin may
> configure max checkpoints per user.=20

Does that mean PCP auth (draft-ietf-pcp-authentication) is mandatory for th=
e PCP server to identify a user ?

-Tiru.

> Please comment, so I will update it in
> the next version of draft.
> >
> >-Tiru.
> >
> >> >
> >> >Cheers,
> >> >-Tiru.
> >> >
> >> >> -----Original Message-----
> >> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
> >> >> Sent: Wednesday, November 06, 2013 12:33 AM
> >> >> To: pcp@ietf.org
> >> >> Subject: Re: [pcp] New Version Notification for
> >> >>draft-vinapamula-flow-ha-
> >> >> 00.txt
> >> >>
> >> >> Hi All,
> >> >>
> >> >> This draft talks about issues with checkpointing flows in current
> >> >> deployment, and how they can be addressed and handled efficiently
> >>with
> >> >>PCP.
> >> >> Please review and share your comments.
> >> >>
> >> >> Thanks
> >> >> Suresh
> >> >>
> >> >> On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
> >> >> <sureshk@juniper.net> wrote:
> >> >>
> >> >> >Dear All,
> >> >> >
> >> >> >We submitted a new draft that sketches flow high availability
> >>through
> >> >>PCP.
> >> >> >Please review.
> >> >> >
> >> >> >-Suresh
> >> >> >
> >> >> >On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
> >> >> ><internet-drafts@ietf.org> wrote:
> >> >> >
> >> >> >>
> >> >> >>A new version of I-D, draft-vinapamula-flow-ha-00.txt
> >> >> >>has been successfully submitted by Suresh Vinapamula and posted t=
o
> >>the
> >> >> >>IETF repository.
> >> >> >>
> >> >> >>Filename:	 draft-vinapamula-flow-ha
> >> >> >>Revision:	 00
> >> >> >>Title:		 Flow high availability through PCP
> >> >> >>Creation date:	 2013-10-14
> >> >> >>Group:		 Individual Submission
> >> >> >>Number of pages: 5
> >> >> >>URL:
> >> >> >>http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.t=
xt
> >> >> >>Status:
> >> >>http://datatracker.ietf.org/doc/draft-vinapamula-flow-ha
> >> >> >>Htmlized:
> >> >>http://tools.ietf.org/html/draft-vinapamula-flow-ha-00
> >> >> >>
> >> >> >>
> >> >> >>Abstract:
> >> >> >>   This document describes a mechanism for a host signal Network
> >> >>Address
> >> >> >>   Translator's (NAT) High Availability (HA) module to checkpoint
> >> >> >>   interested connections.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>Please note that it may take a couple of minutes from the time of
> >> >> >>submission
> >> >> >>until the htmlized version and diff are available at
> >>tools.ietf.org.
> >> >> >>
> >> >> >>The IETF Secretariat
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >>
> >
> >
> >
>=20


From sureshk@juniper.net  Tue Nov 19 11:27:32 2013
Return-Path: <sureshk@juniper.net>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A387B1AE1D2 for <pcp@ietfa.amsl.com>; Tue, 19 Nov 2013 11:27:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xnL2Aqu0DfLO for <pcp@ietfa.amsl.com>; Tue, 19 Nov 2013 11:27:29 -0800 (PST)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe001.messaging.microsoft.com [216.32.180.184]) by ietfa.amsl.com (Postfix) with ESMTP id B1A131AE1A5 for <pcp@ietf.org>; Tue, 19 Nov 2013 11:27:29 -0800 (PST)
Received: from mail167-co1-R.bigfish.com (10.243.78.254) by CO1EHSOBE035.bigfish.com (10.243.66.100) with Microsoft SMTP Server id 14.1.225.22; Tue, 19 Nov 2013 19:27:23 +0000
Received: from mail167-co1 (localhost [127.0.0.1])	by mail167-co1-R.bigfish.com (Postfix) with ESMTP id 4D5D4A00CE4;	Tue, 19 Nov 2013 19:27:23 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -27
X-BigFish: VPS-27(z579ehzbb2dI98dI9371I936eI542I1432I14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL17326ah8275bh8275dh1de097h186068hz2fh109h2a8h839h944he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1fe8h1ff5h209eh2216h22d0h1155h)
Received-SPF: pass (mail167-co1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=sureshk@juniper.net; helo=BL2PRD0510HT002.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(51704005)(377454003)(377424004)(479174003)(13464003)(199002)(189002)(53754006)(24454002)(74876001)(77982001)(81816001)(74706001)(87936001)(80976001)(47976001)(50986001)(83322001)(81686001)(59766001)(81542001)(81342001)(66066001)(54356001)(2656002)(79102001)(15202345003)(53806001)(63696002)(4396001)(54316002)(56776001)(76482001)(87266001)(19580395003)(46102001)(19580405001)(51856001)(49866001)(47736001)(80022001)(56816003)(83072001)(74366001)(76786001)(76796001)(31966008)(76176001)(36756003)(65816001)(74502001)(74662001)(85306002)(15975445006)(83506001)(69226001)(47446002); DIR:OUT; SFP:; SCL:1; SRVR:DM2PR05MB287; H:DM2PR05MB288.namprd05.prod.outlook.com; CLIP:66.129.239.13; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail167-co1 (localhost.localdomain [127.0.0.1]) by mail167-co1 (MessageSwitch) id 1384889241345320_369; Tue, 19 Nov 2013 19:27:21 +0000 (UTC)
Received: from CO1EHSMHS025.bigfish.com (unknown [10.243.78.245])	by mail167-co1.bigfish.com (Postfix) with ESMTP id 50A3CC00041; Tue, 19 Nov 2013 19:27:21 +0000 (UTC)
Received: from BL2PRD0510HT002.namprd05.prod.outlook.com (157.56.240.101) by CO1EHSMHS025.bigfish.com (10.243.66.35) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 19 Nov 2013 19:27:21 +0000
Received: from DM2PR05MB287.namprd05.prod.outlook.com (10.141.101.27) by BL2PRD0510HT002.namprd05.prod.outlook.com (10.255.100.37) with Microsoft SMTP Server (TLS) id 14.16.383.1; Tue, 19 Nov 2013 19:27:19 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com (10.141.101.11) by DM2PR05MB287.namprd05.prod.outlook.com (10.141.101.27) with Microsoft SMTP Server (TLS) id 15.0.800.7; Tue, 19 Nov 2013 19:27:16 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) by DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) with mapi id 15.00.0800.005; Tue, 19 Nov 2013 19:27:16 +0000
From: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHO2lmbQ60NWXm7bU68b/cwqgHqfJok5Y+A//+nOICAAr5pgIACSDUAgAJMEwCAAKBfAA==
Date: Tue, 19 Nov 2013 19:27:15 +0000
Message-ID: <CEB0E637.287FA%sureshk@juniper.net>
In-Reply-To: <913383AAA69FF945B8F946018B75898A24267498@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [66.129.239.13]
x-forefront-prvs: 0035B15214
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6E4312068F5F3B48AC47D77147BBA69C@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 19:27:32 -0000

Hi Tiru,=20

Please see inline.

On 11/18/13 5:53 PM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
wrote:

>Hi Suresh,
>
>Please see inline
>
>> -----Original Message-----
>> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
>> Sent: Monday, November 18, 2013 4:18 AM
>> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
>> Subject: Re: [pcp] New Version Notification for
>>draft-vinapamula-flow-ha-
>> 00.txt
>>=20
>> Hi Tiru,
>>=20
>> Thanks for your followup questions. Please see responses inline.
>>=20
>> On 11/15/13 7:57 PM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
>> wrote:
>>=20
>> >Hi Suresh,
>> >
>> >Please see inline
>> >
>> >> -----Original Message-----
>> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
>> >> Sent: Thursday, November 14, 2013 11:33 PM
>> >> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
>> >> Subject: Re: [pcp] New Version Notification for
>> >>draft-vinapamula-flow-ha-
>> >> 00.txt
>> >>
>> >> Hi Tiru,
>> >>
>> >> Thanks for your comments. Please see inline for responses.
>> >>
>> >> On 11/14/13 7:21 AM, "Tirumaleswar Reddy (tireddy)"
>><tireddy@cisco.com>
>> >> wrote:
>> >>
>> >> >Hi Suresh,
>> >> >
>> >> >My initial comments
>> >> >
>> >> >1)Why cannot the problem be solved for example by the PCP client
>> >>sending
>> >> >PEER with a long lifetime and if the lifetime is higher than a
>> >>particular
>> >> >threshold only those connections are synced implicitly ?
>> >> How would application know what is the threshold life time for it to
>> >> request life time greater than that? What if a connection is critical
>> >>but
>> >> is short lived than the configured HA life time?
>> >
>> >Good point. we don't want short-lived business critical sessions to set
>> >long lifetime just for HA.
>> >
>> >> Similarly, what if a
>> >> connection is not business critical, but its life time greater than
>> >> configured HA life time?
>> >
>> >The problem is how does the network know that the mapping is for a
>> >business critical application or not ?
>> >Network needs a mechanism to distinguish b/w the applications.
>> A bit in the PCP header indicates that it is critical right ? An
>> application can use PCP medium to communicate to network about this.
>
>The problem is any application can set this bit. How does the network
>distinguish b/w applications ?
Yes, any application can set, but user also has to honor it right?
>
>> >
>> >> >
>> >> >2)HA is applicable for both NAT and Firewall devices. I would
>>suggest
>> >>not
>> >> >to restrict the draft to only NAT scenarios.
>> >> Yes, the intention is to not restrict to NAT only service.
>> >> >
>> >> >3)In Active-Standby HA, switch-over is triggered not just because of
>> >> >Active rebooting but also because of WAN-link failures. Are you
>> >>assuming
>> >> >HA deployments with provider-independent or provider-dependent
>> >>addresses ?
>> >> I am not sure what you meant by provider-independent or
>> >>provider-dependent
>> >> addresses. Please clarify for my response.
>> >
>> >Refer to http://tools.ietf.org/html/rfc4116 on PI and PA.
>> Oh, you meant provider aggregatable and provider independent. Are you
>> talking in the context of multi-homing ?
>
>Yes.
>
>> Isn't this taken care at link level or route level redundancy/update? If
>> not, sorry, I am trying to understand your question.
>
>If you could add to the Appendix the deployment scenarios you had
>considered that would help.
>I was thinking of (Active-Standby) with multiple WAN links (Primary and
>Backup).
Yes, I can include some of the deployment scenarios. But I am still trying
to understand your question in the current context. If it is link level
redundancy with same provider, then it is taken care at the link level it
self right? If with multiple providers, it is taken care at routing right?
>
>> >
>> >> >
>> >> >4)
>> >> >
>> >> >a) PCP third-party authorization (draft-wing-pcp-third-party-authz)
>> >>could
>> >> >also be one way of telling the network that it's for a business
>> >>critical
>> >> >application and connection can be synced implicitly without explicit
>> >> >signaling.
>> >
>> >> Even without authorization also, if flows are to be check pointed,
>>they
>> >> will be check pointed with this option.
>> >
>> >With third party authorization, PCP-aware server knows that the mapping
>> >is for business critical applications and hence can sync the state.
>> AFAIU, this draft doesn't talk that third party authorization is for
>> business critical applications only. Please let me know if I am missing
>> something ?
>
>One application may be business critical in one domain and may not be
>another domain. For example let's say WebRTC calls to Stark Industries
>may be business critical in one Enterprise but there is no business
>tie-up for Stark in another Enterprise and hence not business critical.
>
>How does the PCP client set/reset this flag based on which network the
>BYOD device is attached to ?
Yes, this is the same usage I was giving in my previous mail.
In that case, application user will determine if it is critical for him,
when the application is launched.
>
>> >
>> >> >
>> >> >
>> >> >b) Other possible ways could be checkpoint based on destination
>> >> >port/address (For example HTTPS flows are more critical than HTTP).
>> >> Admin can always configure that. This option gives more flexibility.
>> >> >
>> >> >5)How does PCP ANNOUNCE work in this deployment ?
>> >> >I mean some connections on the host need to know that PCP-aware
>> >> >NAT/Firewall has rebooted but other connections may not because
>>their
>> >> >states are check-pointed.
>> >> I will get back to you on this.
>> >
>> >Ok.
>> I feel all connections should refresh their mappings just as how they do
>> on seeing PCP ANNOUNCE.
>> For the mappings that are already check pointed, applications are
>> guaranteed to receive previous state of the mappings.
>
>So check-pointed application will ignore PCP ANNOUNCE ?
Here is where I have two thoughts and WG can comment on them.
1) Application is given feedback that state is check pointed and PCP
Announce may be ignored, by those applications.
2) Application/PCP client on seeing ANNOUNCE, initiate requests for state
reconstruction on PCP. If the state is check pointed, then a success
response is received for the requests. If the success is not received,
then Applications can cleanup.
>
>> For the mappings that are not check pointed, depending on availability
>> they will be honored on first come first serve basis.
>> Is there an issue with this, so that I can update in the next version.
>
>This may work, you may want to explicitly mention the above information
>in the draft.
Sure.
>
>> >
>> >> >
>> >> >6) How does an application developer know if syncing the state is
>> >> >required or not ?
>> >> >The problem could be that if every application says it's connections
>> >>need
>> >> >to be check-pointed then there is no benefit.
>> >> It is application and user dependent. Please refer section 7 in the
>> >>draft.
>> >
>> >The problem is every App developer would think that his application is
>> >important and asks for HA. A set of guidelines is probably needed in
>>the
>> >draft for application developers to help decide when to ask for HA or
>>not
>> >?
>> Ok, I will include the guide lines in the next draft. But, note for some
>> set of applications, an application that is critical to one user may not
>> be critical to another user. That is where both user/application have to
>> determine if it is critical.
>
>I think there is one more aspect to consider, if the application can
>survive PCP server crash. For example if application based on PCP
>ANNOUNCE can do state resumption or application is using multiple paths
>(MPTCP) that though it is a business critical application but does not
>need to ask for check-pointing the connection.
If an application can survive PCP server crash, and if there is HA, then
it can still continue to use that path if state is check pointed right?
>
>> And as a security consideration, admin may
>> configure max checkpoints per user.
>
>Does that mean PCP auth (draft-ietf-pcp-authentication) is mandatory for
>the PCP server to identify a user ?
Are you saying in the context of rogue user or application?
>
>-Tiru.
>
>> Please comment, so I will update it in
>> the next version of draft.
>> >
>> >-Tiru.
>> >
>> >> >
>> >> >Cheers,
>> >> >-Tiru.
>> >> >
>> >> >> -----Original Message-----
>> >> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
>> >> >> Sent: Wednesday, November 06, 2013 12:33 AM
>> >> >> To: pcp@ietf.org
>> >> >> Subject: Re: [pcp] New Version Notification for
>> >> >>draft-vinapamula-flow-ha-
>> >> >> 00.txt
>> >> >>
>> >> >> Hi All,
>> >> >>
>> >> >> This draft talks about issues with checkpointing flows in current
>> >> >> deployment, and how they can be addressed and handled efficiently
>> >>with
>> >> >>PCP.
>> >> >> Please review and share your comments.
>> >> >>
>> >> >> Thanks
>> >> >> Suresh
>> >> >>
>> >> >> On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
>> >> >> <sureshk@juniper.net> wrote:
>> >> >>
>> >> >> >Dear All,
>> >> >> >
>> >> >> >We submitted a new draft that sketches flow high availability
>> >>through
>> >> >>PCP.
>> >> >> >Please review.
>> >> >> >
>> >> >> >-Suresh
>> >> >> >
>> >> >> >On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
>> >> >> ><internet-drafts@ietf.org> wrote:
>> >> >> >
>> >> >> >>
>> >> >> >>A new version of I-D, draft-vinapamula-flow-ha-00.txt
>> >> >> >>has been successfully submitted by Suresh Vinapamula and posted
>>to
>> >>the
>> >> >> >>IETF repository.
>> >> >> >>
>> >> >> >>Filename:	 draft-vinapamula-flow-ha
>> >> >> >>Revision:	 00
>> >> >> >>Title:		 Flow high availability through PCP
>> >> >> >>Creation date:	 2013-10-14
>> >> >> >>Group:		 Individual Submission
>> >> >> >>Number of pages: 5
>> >> >> >>URL:
>> >> >>=20
>>>>http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.txt
>> >> >> >>Status:
>> >> >>http://datatracker.ietf.org/doc/draft-vinapamula-flow-ha
>> >> >> >>Htmlized:
>> >> >>http://tools.ietf.org/html/draft-vinapamula-flow-ha-00
>> >> >> >>
>> >> >> >>
>> >> >> >>Abstract:
>> >> >> >>   This document describes a mechanism for a host signal Network
>> >> >>Address
>> >> >> >>   Translator's (NAT) High Availability (HA) module to
>>checkpoint
>> >> >> >>   interested connections.
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>Please note that it may take a couple of minutes from the time
>>of
>> >> >> >>submission
>> >> >> >>until the htmlized version and diff are available at
>> >>tools.ietf.org.
>> >> >> >>
>> >> >> >>The IETF Secretariat
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>>=20
>
>
>



From tireddy@cisco.com  Tue Nov 19 20:30:58 2013
Return-Path: <tireddy@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1E851AE2E9 for <pcp@ietfa.amsl.com>; Tue, 19 Nov 2013 20:30:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.026
X-Spam-Level: 
X-Spam-Status: No, score=-10.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7iqdn9KVwXjt for <pcp@ietfa.amsl.com>; Tue, 19 Nov 2013 20:30:55 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED251AE2E4 for <pcp@ietf.org>; Tue, 19 Nov 2013 20:30:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13231; q=dns/txt; s=iport; t=1384921849; x=1386131449; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=0sAcdHIye9NHHPWGkLB9jaGP2e+IP87zQHRpgwsNK/8=; b=Bm9Le1lxFK0uVW3wweAUxh7MSRLJCP3mrsc9gFAVCdpUtMb5WKU8w5fP /G+AN2DemKguTKVnQFWVtXaKsN4UtMjJP19KINRlKDdaD6QrZGeGNuxmG fkgYwO5IsVbzJ5dV+ySaTKOSc1tCweVLqPH/THp7VBmC+jLuUgw3+6Ed7 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFANc6jFKtJV2d/2dsb2JhbABPCoMHOFO+e4EVFnSCJQEBAQMBOjIEBgEHBwQCAQgRBAEBAQoUCQcyFAkIAgQBEggBEIdiBg3ACBeOAg8LAQGBCCwMBoMagRIDmUGQXoMogXE5
X-IronPort-AV: E=Sophos;i="4.93,734,1378857600";  d="scan'208";a="809916"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-6.cisco.com with ESMTP; 20 Nov 2013 04:30:33 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id rAK4UXhd023283 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 20 Nov 2013 04:30:33 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.47]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0123.003; Tue, 19 Nov 2013 22:30:32 -0600
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHO2mGhjLsh300HAEimsEM4ztlxb5oksKawgADGxgCAAGVBwIAEoV4A///YwdCAAxO6gIAABNXA
Date: Wed, 20 Nov 2013 04:30:32 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A242686A6@xmb-rcd-x10.cisco.com>
References: <913383AAA69FF945B8F946018B75898A24267498@xmb-rcd-x10.cisco.com> <CEB0E637.287FA%sureshk@juniper.net>
In-Reply-To: <CEB0E637.287FA%sureshk@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.59.169]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2013 04:30:58 -0000

Hi Suresh,

Please see inline

> -----Original Message-----
> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
> Sent: Wednesday, November 20, 2013 12:57 AM
> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
> Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-
> 00.txt
>=20
> Hi Tiru,
>=20
> Please see inline.
>=20
> On 11/18/13 5:53 PM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
> wrote:
>=20
> >Hi Suresh,
> >
> >Please see inline
> >
> >> -----Original Message-----
> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
> >> Sent: Monday, November 18, 2013 4:18 AM
> >> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
> >> Subject: Re: [pcp] New Version Notification for
> >>draft-vinapamula-flow-ha-
> >> 00.txt
> >>
> >> Hi Tiru,
> >>
> >> Thanks for your followup questions. Please see responses inline.
> >>
> >> On 11/15/13 7:57 PM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com=
>
> >> wrote:
> >>
> >> >Hi Suresh,
> >> >
> >> >Please see inline
> >> >
> >> >> -----Original Message-----
> >> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
> >> >> Sent: Thursday, November 14, 2013 11:33 PM
> >> >> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
> >> >> Subject: Re: [pcp] New Version Notification for
> >> >>draft-vinapamula-flow-ha-
> >> >> 00.txt
> >> >>
> >> >> Hi Tiru,
> >> >>
> >> >> Thanks for your comments. Please see inline for responses.
> >> >>
> >> >> On 11/14/13 7:21 AM, "Tirumaleswar Reddy (tireddy)"
> >><tireddy@cisco.com>
> >> >> wrote:
> >> >>
> >> >> >Hi Suresh,
> >> >> >
> >> >> >My initial comments
> >> >> >
> >> >> >1)Why cannot the problem be solved for example by the PCP client
> >> >>sending
> >> >> >PEER with a long lifetime and if the lifetime is higher than a
> >> >>particular
> >> >> >threshold only those connections are synced implicitly ?
> >> >> How would application know what is the threshold life time for it t=
o
> >> >> request life time greater than that? What if a connection is critic=
al
> >> >>but
> >> >> is short lived than the configured HA life time?
> >> >
> >> >Good point. we don't want short-lived business critical sessions to s=
et
> >> >long lifetime just for HA.
> >> >
> >> >> Similarly, what if a
> >> >> connection is not business critical, but its life time greater than
> >> >> configured HA life time?
> >> >
> >> >The problem is how does the network know that the mapping is for a
> >> >business critical application or not ?
> >> >Network needs a mechanism to distinguish b/w the applications.
> >> A bit in the PCP header indicates that it is critical right ? An
> >> application can use PCP medium to communicate to network about this.
> >
> >The problem is any application can set this bit. How does the network
> >distinguish b/w applications ?
> Yes, any application can set, but user also has to honor it right ?

Are you referring to some GUI option where the user will select HA is requi=
red or not ?

> >
> >> >
> >> >> >
> >> >> >2)HA is applicable for both NAT and Firewall devices. I would
> >>suggest
> >> >>not
> >> >> >to restrict the draft to only NAT scenarios.
> >> >> Yes, the intention is to not restrict to NAT only service.
> >> >> >
> >> >> >3)In Active-Standby HA, switch-over is triggered not just because =
of
> >> >> >Active rebooting but also because of WAN-link failures. Are you
> >> >>assuming
> >> >> >HA deployments with provider-independent or provider-dependent
> >> >>addresses ?
> >> >> I am not sure what you meant by provider-independent or
> >> >>provider-dependent
> >> >> addresses. Please clarify for my response.
> >> >
> >> >Refer to http://tools.ietf.org/html/rfc4116 on PI and PA.
> >> Oh, you meant provider aggregatable and provider independent. Are you
> >> talking in the context of multi-homing ?
> >
> >Yes.
> >
> >> Isn't this taken care at link level or route level redundancy/update? =
If
> >> not, sorry, I am trying to understand your question.
> >
> >If you could add to the Appendix the deployment scenarios you had
> >considered that would help.
> >I was thinking of (Active-Standby) with multiple WAN links (Primary and
> >Backup).
> Yes, I can include some of the deployment scenarios. But I am still tryin=
g
> to understand your question in the current context. If it is link level
> redundancy with same provider, then it is taken care at the link level it
> self right? If with multiple providers, it is taken care at routing right=
 ?

I am referring to a use case where two routers are used for Active-Standby =
with multiple WAN links one primary and other backup.=20
For HA, it will only work with PI addresses.

> >
> >> >
> >> >> >
> >> >> >4)
> >> >> >
> >> >> >a) PCP third-party authorization (draft-wing-pcp-third-party-authz=
)
> >> >>could
> >> >> >also be one way of telling the network that it's for a business
> >> >>critical
> >> >> >application and connection can be synced implicitly without explic=
it
> >> >> >signaling.
> >> >
> >> >> Even without authorization also, if flows are to be check pointed,
> >>they
> >> >> will be check pointed with this option.
> >> >
> >> >With third party authorization, PCP-aware server knows that the mappi=
ng
> >> >is for business critical applications and hence can sync the state.
> >> AFAIU, this draft doesn't talk that third party authorization is for
> >> business critical applications only. Please let me know if I am missin=
g
> >> something ?
> >
> >One application may be business critical in one domain and may not be
> >another domain. For example let's say WebRTC calls to Stark Industries
> >may be business critical in one Enterprise but there is no business
> >tie-up for Stark in another Enterprise and hence not business critical.
> >
> >How does the PCP client set/reset this flag based on which network the
> >BYOD device is attached to ?
> Yes, this is the same usage I was giving in my previous mail.
> In that case, application user will determine if it is critical for him,
> when the application is launched.

Are you referring to a user knob where for each application, user has to en=
ter critical or not (Something like High, Medium, Low priority) or input th=
at that application needs HA or not. I am not sure if user in all cases wil=
l be aware if application needs HA or not.

> >
> >> >
> >> >> >
> >> >> >
> >> >> >b) Other possible ways could be checkpoint based on destination
> >> >> >port/address (For example HTTPS flows are more critical than HTTP)=
.
> >> >> Admin can always configure that. This option gives more flexibility=
.
> >> >> >
> >> >> >5)How does PCP ANNOUNCE work in this deployment ?
> >> >> >I mean some connections on the host need to know that PCP-aware
> >> >> >NAT/Firewall has rebooted but other connections may not because
> >>their
> >> >> >states are check-pointed.
> >> >> I will get back to you on this.
> >> >
> >> >Ok.
> >> I feel all connections should refresh their mappings just as how they =
do
> >> on seeing PCP ANNOUNCE.
> >> For the mappings that are already check pointed, applications are
> >> guaranteed to receive previous state of the mappings.
> >
> >So check-pointed application will ignore PCP ANNOUNCE ?

> Here is where I have two thoughts and WG can comment on them.
> 1) Application is given feedback that state is check pointed and PCP
> Announce may be ignored, by those applications.
> 2) Application/PCP client on seeing ANNOUNCE, initiate requests for state
> reconstruction on PCP. If the state is check pointed, then a success
> response is received for the requests. If the success is not received,
> then Applications can cleanup.

Option 1 will reduce the chatter of check-pointed applications not initiati=
ng state resumption.=20

> >
> >> For the mappings that are not check pointed, depending on availability
> >> they will be honored on first come first serve basis.
> >> Is there an issue with this, so that I can update in the next version.
> >
> >This may work, you may want to explicitly mention the above information
> >in the draft.
> Sure.
> >
> >> >
> >> >> >
> >> >> >6) How does an application developer know if syncing the state is
> >> >> >required or not ?
> >> >> >The problem could be that if every application says it's connectio=
ns
> >> >>need
> >> >> >to be check-pointed then there is no benefit.
> >> >> It is application and user dependent. Please refer section 7 in the
> >> >>draft.
> >> >
> >> >The problem is every App developer would think that his application i=
s
> >> >important and asks for HA. A set of guidelines is probably needed in
> >>the
> >> >draft for application developers to help decide when to ask for HA or
> >>not
> >> >?
> >> Ok, I will include the guide lines in the next draft. But, note for so=
me
> >> set of applications, an application that is critical to one user may n=
ot
> >> be critical to another user. That is where both user/application have =
to
> >> determine if it is critical.
> >
> >I think there is one more aspect to consider, if the application can
> >survive PCP server crash. For example if application based on PCP
> >ANNOUNCE can do state resumption or application is using multiple paths
> >(MPTCP) that though it is a business critical application but does not
> >need to ask for check-pointing the connection.
> If an application can survive PCP server crash, and if there is HA, then
> it can still continue to use that path if state is check pointed right ?

But the goal is to check-point only few connections. The above category of =
applications though business-critical do not need check-pointing.

> >
> >> And as a security consideration, admin may
> >> configure max checkpoints per user.
> >
> >Does that mean PCP auth (draft-ietf-pcp-authentication) is mandatory for
> >the PCP server to identify a user ?
> Are you saying in the context of rogue user or application ?

PCP authentication ensures only valid users gain access to use the PCP serv=
ers and not rouge users. This will also help to enforce user-based policy l=
imits like number of mapping to checkpoint per user.

-Tiru.

> >
> >-Tiru.
> >
> >> Please comment, so I will update it in
> >> the next version of draft.
> >> >
> >> >-Tiru.
> >> >
> >> >> >
> >> >> >Cheers,
> >> >> >-Tiru.
> >> >> >
> >> >> >> -----Original Message-----
> >> >> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.ne=
t]
> >> >> >> Sent: Wednesday, November 06, 2013 12:33 AM
> >> >> >> To: pcp@ietf.org
> >> >> >> Subject: Re: [pcp] New Version Notification for
> >> >> >>draft-vinapamula-flow-ha-
> >> >> >> 00.txt
> >> >> >>
> >> >> >> Hi All,
> >> >> >>
> >> >> >> This draft talks about issues with checkpointing flows in curren=
t
> >> >> >> deployment, and how they can be addressed and handled efficientl=
y
> >> >>with
> >> >> >>PCP.
> >> >> >> Please review and share your comments.
> >> >> >>
> >> >> >> Thanks
> >> >> >> Suresh
> >> >> >>
> >> >> >> On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
> >> >> >> <sureshk@juniper.net> wrote:
> >> >> >>
> >> >> >> >Dear All,
> >> >> >> >
> >> >> >> >We submitted a new draft that sketches flow high availability
> >> >>through
> >> >> >>PCP.
> >> >> >> >Please review.
> >> >> >> >
> >> >> >> >-Suresh
> >> >> >> >
> >> >> >> >On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
> >> >> >> ><internet-drafts@ietf.org> wrote:
> >> >> >> >
> >> >> >> >>
> >> >> >> >>A new version of I-D, draft-vinapamula-flow-ha-00.txt
> >> >> >> >>has been successfully submitted by Suresh Vinapamula and poste=
d
> >>to
> >> >>the
> >> >> >> >>IETF repository.
> >> >> >> >>
> >> >> >> >>Filename:	 draft-vinapamula-flow-ha
> >> >> >> >>Revision:	 00
> >> >> >> >>Title:		 Flow high availability through PCP
> >> >> >> >>Creation date:	 2013-10-14
> >> >> >> >>Group:		 Individual Submission
> >> >> >> >>Number of pages: 5
> >> >> >> >>URL:
> >> >> >>
> >>>>http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.txt
> >> >> >> >>Status:
> >> >> >>http://datatracker.ietf.org/doc/draft-vinapamula-flow-ha
> >> >> >> >>Htmlized:
> >> >> >>http://tools.ietf.org/html/draft-vinapamula-flow-ha-00
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>Abstract:
> >> >> >> >>   This document describes a mechanism for a host signal Netwo=
rk
> >> >> >>Address
> >> >> >> >>   Translator's (NAT) High Availability (HA) module to
> >>checkpoint
> >> >> >> >>   interested connections.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>Please note that it may take a couple of minutes from the time
> >>of
> >> >> >> >>submission
> >> >> >> >>until the htmlized version and diff are available at
> >> >>tools.ietf.org.
> >> >> >> >>
> >> >> >> >>The IETF Secretariat
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >
> >> >
> >> >
> >>
> >
> >
> >
>=20


From sureshk@juniper.net  Tue Nov 19 21:56:14 2013
Return-Path: <sureshk@juniper.net>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0408C1AE32A for <pcp@ietfa.amsl.com>; Tue, 19 Nov 2013 21:56:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EzVI0kff-Fjx for <pcp@ietfa.amsl.com>; Tue, 19 Nov 2013 21:56:10 -0800 (PST)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe005.messaging.microsoft.com [213.199.154.208]) by ietfa.amsl.com (Postfix) with ESMTP id F32C51AE326 for <pcp@ietf.org>; Tue, 19 Nov 2013 21:56:09 -0800 (PST)
Received: from mail92-am1-R.bigfish.com (10.3.201.246) by AM1EHSOBE021.bigfish.com (10.3.207.143) with Microsoft SMTP Server id 14.1.225.22; Wed, 20 Nov 2013 05:56:02 +0000
Received: from mail92-am1 (localhost [127.0.0.1])	by mail92-am1-R.bigfish.com (Postfix) with ESMTP id EF31E2600FF; Wed, 20 Nov 2013 05:56:02 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT004.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -28
X-BigFish: VPS-28(z579ehzbb2dI98dI9371I936eI146fI542I1432I14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL17326ah8275bh8275dh1de097h186068hz2fh109h2a8h839h944he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1fe8h1ff5h209eh2216h22d0h1155h)
Received-SPF: pass (mail92-am1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=sureshk@juniper.net; helo=BL2PRD0510HT004.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(51704005)(377454003)(377424004)(479174003)(13464003)(199002)(189002)(53754006)(52314003)(24454002)(74876001)(77982001)(74706001)(81816001)(47976001)(87936001)(80976001)(81686001)(50986001)(83322001)(59766001)(81542001)(81342001)(66066001)(19580405001)(54356001)(15202345003)(79102001)(2656002)(53806001)(63696002)(4396001)(56776001)(54316002)(87266001)(76482001)(46102001)(51856001)(49866001)(19580395003)(47736001)(80022001)(56816003)(83072001)(74366001)(76786001)(76796001)(31966008)(76176001)(36756003)(65816001)(85306002)(74502001)(74662001)(83506001)(15975445006)(69226001)(47446002); DIR:OUT; SFP:; SCL:1; SRVR:DM2PR05MB288; H:DM2PR05MB288.namprd05.prod.outlook.com; CLIP:66.129.239.13; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail92-am1 (localhost.localdomain [127.0.0.1]) by mail92-am1 (MessageSwitch) id 1384926960376131_8853; Wed, 20 Nov 2013 05:56:00 +0000 (UTC)
Received: from AM1EHSMHS007.bigfish.com (unknown [10.3.201.246])	by mail92-am1.bigfish.com (Postfix) with ESMTP id 4730D380050;	Wed, 20 Nov 2013 05:56:00 +0000 (UTC)
Received: from BL2PRD0510HT004.namprd05.prod.outlook.com (157.56.240.101) by AM1EHSMHS007.bigfish.com (10.3.207.107) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 20 Nov 2013 05:55:57 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com (10.141.101.11) by BL2PRD0510HT004.namprd05.prod.outlook.com (10.255.100.39) with Microsoft SMTP Server (TLS) id 14.16.383.1; Wed, 20 Nov 2013 05:55:55 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com (10.141.101.11) by DM2PR05MB288.namprd05.prod.outlook.com (10.141.101.11) with Microsoft SMTP Server (TLS) id 15.0.800.7; Wed, 20 Nov 2013 05:55:53 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) by DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) with mapi id 15.00.0800.005; Wed, 20 Nov 2013 05:55:53 +0000
From: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHO2lmbQ60NWXm7bU68b/cwqgHqfJok5Y+A//+nOICAAr5pgIACSDUAgAJMEwCAAKBfAIABHfUA//+RuAA=
Date: Wed, 20 Nov 2013 05:55:52 +0000
Message-ID: <CEB1872B.289A3%sureshk@juniper.net>
In-Reply-To: <913383AAA69FF945B8F946018B75898A242686A6@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [66.129.239.13]
x-forefront-prvs: 0036736630
Content-Type: text/plain; charset="us-ascii"
Content-ID: <36D7FBFD42560941B150A2F4F7790C97@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2013 05:56:14 -0000

Hi Tiru,=20

Please see inline.

On 11/19/13 8:30 PM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
wrote:

>Hi Suresh,
>
>Please see inline
>
>> -----Original Message-----
>> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
>> Sent: Wednesday, November 20, 2013 12:57 AM
>> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
>> Subject: Re: [pcp] New Version Notification for
>>draft-vinapamula-flow-ha-
>> 00.txt
>>=20
>> Hi Tiru,
>>=20
>> Please see inline.
>>=20
>> On 11/18/13 5:53 PM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
>> wrote:
>>=20
>> >Hi Suresh,
>> >
>> >Please see inline
>> >
>> >> -----Original Message-----
>> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
>> >> Sent: Monday, November 18, 2013 4:18 AM
>> >> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
>> >> Subject: Re: [pcp] New Version Notification for
>> >>draft-vinapamula-flow-ha-
>> >> 00.txt
>> >>
>> >> Hi Tiru,
>> >>
>> >> Thanks for your followup questions. Please see responses inline.
>> >>
>> >> On 11/15/13 7:57 PM, "Tirumaleswar Reddy (tireddy)"
>><tireddy@cisco.com>
>> >> wrote:
>> >>
>> >> >Hi Suresh,
>> >> >
>> >> >Please see inline
>> >> >
>> >> >> -----Original Message-----
>> >> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
>> >> >> Sent: Thursday, November 14, 2013 11:33 PM
>> >> >> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
>> >> >> Subject: Re: [pcp] New Version Notification for
>> >> >>draft-vinapamula-flow-ha-
>> >> >> 00.txt
>> >> >>
>> >> >> Hi Tiru,
>> >> >>
>> >> >> Thanks for your comments. Please see inline for responses.
>> >> >>
>> >> >> On 11/14/13 7:21 AM, "Tirumaleswar Reddy (tireddy)"
>> >><tireddy@cisco.com>
>> >> >> wrote:
>> >> >>
>> >> >> >Hi Suresh,
>> >> >> >
>> >> >> >My initial comments
>> >> >> >
>> >> >> >1)Why cannot the problem be solved for example by the PCP client
>> >> >>sending
>> >> >> >PEER with a long lifetime and if the lifetime is higher than a
>> >> >>particular
>> >> >> >threshold only those connections are synced implicitly ?
>> >> >> How would application know what is the threshold life time for it
>>to
>> >> >> request life time greater than that? What if a connection is
>>critical
>> >> >>but
>> >> >> is short lived than the configured HA life time?
>> >> >
>> >> >Good point. we don't want short-lived business critical sessions to
>>set
>> >> >long lifetime just for HA.
>> >> >
>> >> >> Similarly, what if a
>> >> >> connection is not business critical, but its life time greater
>>than
>> >> >> configured HA life time?
>> >> >
>> >> >The problem is how does the network know that the mapping is for a
>> >> >business critical application or not ?
>> >> >Network needs a mechanism to distinguish b/w the applications.
>> >> A bit in the PCP header indicates that it is critical right ? An
>> >> application can use PCP medium to communicate to network about this.
>> >
>> >The problem is any application can set this bit. How does the network
>> >distinguish b/w applications ?
>> Yes, any application can set, but user also has to honor it right ?
>
>Are you referring to some GUI option where the user will select HA is
>required or not ?
Shouldn't this be left to implementation? For example, it could be at
installation also.
>
>> >
>> >> >
>> >> >> >
>> >> >> >2)HA is applicable for both NAT and Firewall devices. I would
>> >>suggest
>> >> >>not
>> >> >> >to restrict the draft to only NAT scenarios.
>> >> >> Yes, the intention is to not restrict to NAT only service.
>> >> >> >
>> >> >> >3)In Active-Standby HA, switch-over is triggered not just
>>because of
>> >> >> >Active rebooting but also because of WAN-link failures. Are you
>> >> >>assuming
>> >> >> >HA deployments with provider-independent or provider-dependent
>> >> >>addresses ?
>> >> >> I am not sure what you meant by provider-independent or
>> >> >>provider-dependent
>> >> >> addresses. Please clarify for my response.
>> >> >
>> >> >Refer to http://tools.ietf.org/html/rfc4116 on PI and PA.
>> >> Oh, you meant provider aggregatable and provider independent. Are you
>> >> talking in the context of multi-homing ?
>> >
>> >Yes.
>> >
>> >> Isn't this taken care at link level or route level
>>redundancy/update? If
>> >> not, sorry, I am trying to understand your question.
>> >
>> >If you could add to the Appendix the deployment scenarios you had
>> >considered that would help.
>> >I was thinking of (Active-Standby) with multiple WAN links (Primary and
>> >Backup).
>> Yes, I can include some of the deployment scenarios. But I am still
>>trying
>> to understand your question in the current context. If it is link level
>> redundancy with same provider, then it is taken care at the link level
>>it
>> self right? If with multiple providers, it is taken care at routing
>>right ?
>
>I am referring to a use case where two routers are used for
>Active-Standby with multiple WAN links one primary and other backup.
>For HA, it will only work with PI addresses.
I still don't understand this. When two routers belong to same provider,
now sure why it has to be PI addresses only. Also, when they are with
different providers, how do you expect state to be check pointed across
routers?=20
>
>> >
>> >> >
>> >> >> >
>> >> >> >4)
>> >> >> >
>> >> >> >a) PCP third-party authorization
>>(draft-wing-pcp-third-party-authz)
>> >> >>could
>> >> >> >also be one way of telling the network that it's for a business
>> >> >>critical
>> >> >> >application and connection can be synced implicitly without
>>explicit
>> >> >> >signaling.
>> >> >
>> >> >> Even without authorization also, if flows are to be check pointed,
>> >>they
>> >> >> will be check pointed with this option.
>> >> >
>> >> >With third party authorization, PCP-aware server knows that the
>>mapping
>> >> >is for business critical applications and hence can sync the state.
>> >> AFAIU, this draft doesn't talk that third party authorization is for
>> >> business critical applications only. Please let me know if I am
>>missing
>> >> something ?
>> >
>> >One application may be business critical in one domain and may not be
>> >another domain. For example let's say WebRTC calls to Stark Industries
>> >may be business critical in one Enterprise but there is no business
>> >tie-up for Stark in another Enterprise and hence not business critical.
>> >
>> >How does the PCP client set/reset this flag based on which network the
>> >BYOD device is attached to ?
>> Yes, this is the same usage I was giving in my previous mail.
>> In that case, application user will determine if it is critical for him,
>> when the application is launched.
>
>Are you referring to a user knob where for each application, user has to
>enter critical or not (Something like High, Medium, Low priority) or
>input that that application needs HA or not. I am not sure if user in all
>cases will be aware if application needs HA or not.
Yes, it is not for all applications. That is why I said it is for some set
of applications this may be required.
>
>> >
>> >> >
>> >> >> >
>> >> >> >
>> >> >> >b) Other possible ways could be checkpoint based on destination
>> >> >> >port/address (For example HTTPS flows are more critical than
>>HTTP).
>> >> >> Admin can always configure that. This option gives more
>>flexibility.
>> >> >> >
>> >> >> >5)How does PCP ANNOUNCE work in this deployment ?
>> >> >> >I mean some connections on the host need to know that PCP-aware
>> >> >> >NAT/Firewall has rebooted but other connections may not because
>> >>their
>> >> >> >states are check-pointed.
>> >> >> I will get back to you on this.
>> >> >
>> >> >Ok.
>> >> I feel all connections should refresh their mappings just as how
>>they do
>> >> on seeing PCP ANNOUNCE.
>> >> For the mappings that are already check pointed, applications are
>> >> guaranteed to receive previous state of the mappings.
>> >
>> >So check-pointed application will ignore PCP ANNOUNCE ?
>
>> Here is where I have two thoughts and WG can comment on them.
>> 1) Application is given feedback that state is check pointed and PCP
>> Announce may be ignored, by those applications.
>> 2) Application/PCP client on seeing ANNOUNCE, initiate requests for
>>state
>> reconstruction on PCP. If the state is check pointed, then a success
>> response is received for the requests. If the success is not received,
>> then Applications can cleanup.
>
>Option 1 will reduce the chatter of check-pointed applications not
>initiating state resumption.
Yes, but if we consider back to back failure scenario it _may_ have to
respond to ANNOUNCE.
>=20
>
>> >
>> >> For the mappings that are not check pointed, depending on
>>availability
>> >> they will be honored on first come first serve basis.
>> >> Is there an issue with this, so that I can update in the next
>>version.
>> >
>> >This may work, you may want to explicitly mention the above information
>> >in the draft.
>> Sure.
>> >
>> >> >
>> >> >> >
>> >> >> >6) How does an application developer know if syncing the state is
>> >> >> >required or not ?
>> >> >> >The problem could be that if every application says it's
>>connections
>> >> >>need
>> >> >> >to be check-pointed then there is no benefit.
>> >> >> It is application and user dependent. Please refer section 7 in
>>the
>> >> >>draft.
>> >> >
>> >> >The problem is every App developer would think that his application
>>is
>> >> >important and asks for HA. A set of guidelines is probably needed in
>> >>the
>> >> >draft for application developers to help decide when to ask for HA
>>or
>> >>not
>> >> >?
>> >> Ok, I will include the guide lines in the next draft. But, note for
>>some
>> >> set of applications, an application that is critical to one user may
>>not
>> >> be critical to another user. That is where both user/application
>>have to
>> >> determine if it is critical.
>> >
>> >I think there is one more aspect to consider, if the application can
>> >survive PCP server crash. For example if application based on PCP
>> >ANNOUNCE can do state resumption or application is using multiple paths
>> >(MPTCP) that though it is a business critical application but does not
>> >need to ask for check-pointing the connection.
>> If an application can survive PCP server crash, and if there is HA, then
>> it can still continue to use that path if state is check pointed right ?
>
>But the goal is to check-point only few connections. The above category
>of applications though business-critical do not need check-pointing.
Is it because if one path fails, other path provides service continuity?
Having HA at each path level is not a bad thing right? Anyway, if
application doesn't require HA it need not initiate HA. I feel the goal is
to check point any critical application that requested HA.
>
>> >
>> >> And as a security consideration, admin may
>> >> configure max checkpoints per user.
>> >
>> >Does that mean PCP auth (draft-ietf-pcp-authentication) is mandatory
>>for
>> >the PCP server to identify a user ?
>> Are you saying in the context of rogue user or application ?
>
>PCP authentication ensures only valid users gain access to use the PCP
>servers and not rouge users. This will also help to enforce user-based
>policy limits like number of mapping to checkpoint per user.
Yes, PCP authentication ensures that only valid users gain access to PCP
servers and not rogue user. But, that doesn't mean that every application
that does PCP authentication require HA and every application that doesn't
do PCP auth doesn't require HA, as Authentication and HA are addressing
two different issues. Or am I missing something? Note, the approach that
is suggested in the draft would work in both PCP authentication case and
non authentication case.
>
>-Tiru.
>
>> >
>> >-Tiru.
>> >
>> >> Please comment, so I will update it in
>> >> the next version of draft.
>> >> >
>> >> >-Tiru.
>> >> >
>> >> >> >
>> >> >> >Cheers,
>> >> >> >-Tiru.
>> >> >> >
>> >> >> >> -----Original Message-----
>> >> >> >> From: Suresh Kumar Vinapamula Venkata
>>[mailto:sureshk@juniper.net]
>> >> >> >> Sent: Wednesday, November 06, 2013 12:33 AM
>> >> >> >> To: pcp@ietf.org
>> >> >> >> Subject: Re: [pcp] New Version Notification for
>> >> >> >>draft-vinapamula-flow-ha-
>> >> >> >> 00.txt
>> >> >> >>
>> >> >> >> Hi All,
>> >> >> >>
>> >> >> >> This draft talks about issues with checkpointing flows in
>>current
>> >> >> >> deployment, and how they can be addressed and handled
>>efficiently
>> >> >>with
>> >> >> >>PCP.
>> >> >> >> Please review and share your comments.
>> >> >> >>
>> >> >> >> Thanks
>> >> >> >> Suresh
>> >> >> >>
>> >> >> >> On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
>> >> >> >> <sureshk@juniper.net> wrote:
>> >> >> >>
>> >> >> >> >Dear All,
>> >> >> >> >
>> >> >> >> >We submitted a new draft that sketches flow high availability
>> >> >>through
>> >> >> >>PCP.
>> >> >> >> >Please review.
>> >> >> >> >
>> >> >> >> >-Suresh
>> >> >> >> >
>> >> >> >> >On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
>> >> >> >> ><internet-drafts@ietf.org> wrote:
>> >> >> >> >
>> >> >> >> >>
>> >> >> >> >>A new version of I-D, draft-vinapamula-flow-ha-00.txt
>> >> >> >> >>has been successfully submitted by Suresh Vinapamula and
>>posted
>> >>to
>> >> >>the
>> >> >> >> >>IETF repository.
>> >> >> >> >>
>> >> >> >> >>Filename:	 draft-vinapamula-flow-ha
>> >> >> >> >>Revision:	 00
>> >> >> >> >>Title:		 Flow high availability through PCP
>> >> >> >> >>Creation date:	 2013-10-14
>> >> >> >> >>Group:		 Individual Submission
>> >> >> >> >>Number of pages: 5
>> >> >> >> >>URL:
>> >> >> >>
>> >>>>http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.txt
>> >> >> >> >>Status:
>> >> >> >>http://datatracker.ietf.org/doc/draft-vinapamula-flow-ha
>> >> >> >> >>Htmlized:
>> >> >> >>http://tools.ietf.org/html/draft-vinapamula-flow-ha-00
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>Abstract:
>> >> >> >> >>   This document describes a mechanism for a host signal
>>Network
>> >> >> >>Address
>> >> >> >> >>   Translator's (NAT) High Availability (HA) module to
>> >>checkpoint
>> >> >> >> >>   interested connections.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>Please note that it may take a couple of minutes from the
>>time
>> >>of
>> >> >> >> >>submission
>> >> >> >> >>until the htmlized version and diff are available at
>> >> >>tools.ietf.org.
>> >> >> >> >>
>> >> >> >> >>The IETF Secretariat
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >>
>> >> >
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>>=20
>
>
>



From tireddy@cisco.com  Wed Nov 20 00:05:02 2013
Return-Path: <tireddy@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E9A11AE37F for <pcp@ietfa.amsl.com>; Wed, 20 Nov 2013 00:05:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.026
X-Spam-Level: 
X-Spam-Status: No, score=-15.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rGN5eSWMUsLI for <pcp@ietfa.amsl.com>; Wed, 20 Nov 2013 00:04:58 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id E8BCE1AC7EE for <pcp@ietf.org>; Wed, 20 Nov 2013 00:04:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16495; q=dns/txt; s=iport; t=1384934692; x=1386144292; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=B29rDxOv+CfwypezvF/bktZGdQfOODNKwWkLxo2K1IE=; b=KHIvZsQTHOpwf7bmBP0tPJi+8k2XIy5I7lEJHp4MAWL0tH+AwZC4wKux Y+0gQ1t15tnK8pUh4reUl5XXDSuNFs+DMSrfDZHaxCzpFPXfWbwSqBjUq QRsYSmdcDymUubHP2VaxvyhxDcIU2UFDhT16D6POPLnCKk6UZti3eR/Ck k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAAlsjFKtJXG+/2dsb2JhbABPCoMHOFO+dIEQFnSCJQEBAQMBOjIEBgEHBwQCAQgRBAEBAQoUCQcyFAkIAgQBEggBEIdiBg3ADxeOAg8LAQGBCCwMBoMagRIDmUGQXoMogXE5
X-IronPort-AV: E=Sophos;i="4.93,735,1378857600"; d="scan'208";a="286305446"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-3.cisco.com with ESMTP; 20 Nov 2013 08:04:51 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id rAK84oir018365 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 20 Nov 2013 08:04:50 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.47]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0123.003; Wed, 20 Nov 2013 02:04:50 -0600
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHO2mGhjLsh300HAEimsEM4ztlxb5oksKawgADGxgCAAGVBwIAEoV4A///YwdCAAxO6gIAABNXAgACqzQD//59s8A==
Date: Wed, 20 Nov 2013 08:04:49 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A24268969@xmb-rcd-x10.cisco.com>
References: <913383AAA69FF945B8F946018B75898A242686A6@xmb-rcd-x10.cisco.com> <CEB1872B.289A3%sureshk@juniper.net>
In-Reply-To: <CEB1872B.289A3%sureshk@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.59.169]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2013 08:05:02 -0000

> -----Original Message-----
> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
> Sent: Wednesday, November 20, 2013 11:26 AM
> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
> Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-
> 00.txt
>=20
> Hi Tiru,
>=20
> Please see inline.
>=20
> On 11/19/13 8:30 PM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
> wrote:
>=20
> >Hi Suresh,
> >
> >Please see inline
> >
> >> -----Original Message-----
> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
> >> Sent: Wednesday, November 20, 2013 12:57 AM
> >> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
> >> Subject: Re: [pcp] New Version Notification for
> >>draft-vinapamula-flow-ha-
> >> 00.txt
> >>
> >> Hi Tiru,
> >>
> >> Please see inline.
> >>
> >> On 11/18/13 5:53 PM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com=
>
> >> wrote:
> >>
> >> >Hi Suresh,
> >> >
> >> >Please see inline
> >> >
> >> >> -----Original Message-----
> >> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
> >> >> Sent: Monday, November 18, 2013 4:18 AM
> >> >> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
> >> >> Subject: Re: [pcp] New Version Notification for
> >> >>draft-vinapamula-flow-ha-
> >> >> 00.txt
> >> >>
> >> >> Hi Tiru,
> >> >>
> >> >> Thanks for your followup questions. Please see responses inline.
> >> >>
> >> >> On 11/15/13 7:57 PM, "Tirumaleswar Reddy (tireddy)"
> >><tireddy@cisco.com>
> >> >> wrote:
> >> >>
> >> >> >Hi Suresh,
> >> >> >
> >> >> >Please see inline
> >> >> >
> >> >> >> -----Original Message-----
> >> >> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.ne=
t]
> >> >> >> Sent: Thursday, November 14, 2013 11:33 PM
> >> >> >> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
> >> >> >> Subject: Re: [pcp] New Version Notification for
> >> >> >>draft-vinapamula-flow-ha-
> >> >> >> 00.txt
> >> >> >>
> >> >> >> Hi Tiru,
> >> >> >>
> >> >> >> Thanks for your comments. Please see inline for responses.
> >> >> >>
> >> >> >> On 11/14/13 7:21 AM, "Tirumaleswar Reddy (tireddy)"
> >> >><tireddy@cisco.com>
> >> >> >> wrote:
> >> >> >>
> >> >> >> >Hi Suresh,
> >> >> >> >
> >> >> >> >My initial comments
> >> >> >> >
> >> >> >> >1)Why cannot the problem be solved for example by the PCP clien=
t
> >> >> >>sending
> >> >> >> >PEER with a long lifetime and if the lifetime is higher than a
> >> >> >>particular
> >> >> >> >threshold only those connections are synced implicitly ?
> >> >> >> How would application know what is the threshold life time for i=
t
> >>to
> >> >> >> request life time greater than that? What if a connection is
> >>critical
> >> >> >>but
> >> >> >> is short lived than the configured HA life time?
> >> >> >
> >> >> >Good point. we don't want short-lived business critical sessions t=
o
> >>set
> >> >> >long lifetime just for HA.
> >> >> >
> >> >> >> Similarly, what if a
> >> >> >> connection is not business critical, but its life time greater
> >>than
> >> >> >> configured HA life time?
> >> >> >
> >> >> >The problem is how does the network know that the mapping is for a
> >> >> >business critical application or not ?
> >> >> >Network needs a mechanism to distinguish b/w the applications.
> >> >> A bit in the PCP header indicates that it is critical right ? An
> >> >> application can use PCP medium to communicate to network about this=
.
> >> >
> >> >The problem is any application can set this bit. How does the network
> >> >distinguish b/w applications ?
> >> Yes, any application can set, but user also has to honor it right ?
> >
> >Are you referring to some GUI option where the user will select HA is
> >required or not ?
> Shouldn't this be left to implementation ? For example, it could be at
> installation also.

That will be static configuration.=20

> >
> >> >
> >> >> >
> >> >> >> >
> >> >> >> >2)HA is applicable for both NAT and Firewall devices. I would
> >> >>suggest
> >> >> >>not
> >> >> >> >to restrict the draft to only NAT scenarios.
> >> >> >> Yes, the intention is to not restrict to NAT only service.
> >> >> >> >
> >> >> >> >3)In Active-Standby HA, switch-over is triggered not just
> >>because of
> >> >> >> >Active rebooting but also because of WAN-link failures. Are you
> >> >> >>assuming
> >> >> >> >HA deployments with provider-independent or provider-dependent
> >> >> >>addresses ?
> >> >> >> I am not sure what you meant by provider-independent or
> >> >> >>provider-dependent
> >> >> >> addresses. Please clarify for my response.
> >> >> >
> >> >> >Refer to http://tools.ietf.org/html/rfc4116 on PI and PA.
> >> >> Oh, you meant provider aggregatable and provider independent. Are y=
ou
> >> >> talking in the context of multi-homing ?
> >> >
> >> >Yes.
> >> >
> >> >> Isn't this taken care at link level or route level
> >>redundancy/update? If
> >> >> not, sorry, I am trying to understand your question.
> >> >
> >> >If you could add to the Appendix the deployment scenarios you had
> >> >considered that would help.
> >> >I was thinking of (Active-Standby) with multiple WAN links (Primary a=
nd
> >> >Backup).
> >> Yes, I can include some of the deployment scenarios. But I am still
> >>trying
> >> to understand your question in the current context. If it is link leve=
l
> >> redundancy with same provider, then it is taken care at the link level
> >>it
> >> self right? If with multiple providers, it is taken care at routing
> >>right ?
> >
> >I am referring to a use case where two routers are used for
> >Active-Standby with multiple WAN links one primary and other backup.
> >For HA, it will only work with PI addresses.
> I still don't understand this. When two routers belong to same provider,
> now sure why it has to be PI addresses only. Also, when they are with
> different providers, how do you expect state to be check pointed across
> routers ?

Each vendor has its proprietary technique to sync Firewall and NAT states.=
=20

> >
> >> >
> >> >> >
> >> >> >> >
> >> >> >> >4)
> >> >> >> >
> >> >> >> >a) PCP third-party authorization
> >>(draft-wing-pcp-third-party-authz)
> >> >> >>could
> >> >> >> >also be one way of telling the network that it's for a business
> >> >> >>critical
> >> >> >> >application and connection can be synced implicitly without
> >>explicit
> >> >> >> >signaling.
> >> >> >
> >> >> >> Even without authorization also, if flows are to be check pointe=
d,
> >> >>they
> >> >> >> will be check pointed with this option.
> >> >> >
> >> >> >With third party authorization, PCP-aware server knows that the
> >>mapping
> >> >> >is for business critical applications and hence can sync the state=
.
> >> >> AFAIU, this draft doesn't talk that third party authorization is fo=
r
> >> >> business critical applications only. Please let me know if I am
> >>missing
> >> >> something ?
> >> >
> >> >One application may be business critical in one domain and may not be
> >> >another domain. For example let's say WebRTC calls to Stark Industrie=
s
> >> >may be business critical in one Enterprise but there is no business
> >> >tie-up for Stark in another Enterprise and hence not business critica=
l.
> >> >
> >> >How does the PCP client set/reset this flag based on which network th=
e
> >> >BYOD device is attached to ?
> >> Yes, this is the same usage I was giving in my previous mail.
> >> In that case, application user will determine if it is critical for hi=
m,
> >> when the application is launched.
> >
> >Are you referring to a user knob where for each application, user has to
> >enter critical or not (Something like High, Medium, Low priority) or
> >input that that application needs HA or not. I am not sure if user in al=
l
> >cases will be aware if application needs HA or not.
> Yes, it is not for all applications. That is why I said it is for some se=
t
> of applications this may be required.
> >
> >> >
> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> >b) Other possible ways could be checkpoint based on destination
> >> >> >> >port/address (For example HTTPS flows are more critical than
> >>HTTP).
> >> >> >> Admin can always configure that. This option gives more
> >>flexibility.
> >> >> >> >
> >> >> >> >5)How does PCP ANNOUNCE work in this deployment ?
> >> >> >> >I mean some connections on the host need to know that PCP-aware
> >> >> >> >NAT/Firewall has rebooted but other connections may not because
> >> >>their
> >> >> >> >states are check-pointed.
> >> >> >> I will get back to you on this.
> >> >> >
> >> >> >Ok.
> >> >> I feel all connections should refresh their mappings just as how
> >>they do
> >> >> on seeing PCP ANNOUNCE.
> >> >> For the mappings that are already check pointed, applications are
> >> >> guaranteed to receive previous state of the mappings.
> >> >
> >> >So check-pointed application will ignore PCP ANNOUNCE ?
> >
> >> Here is where I have two thoughts and WG can comment on them.
> >> 1) Application is given feedback that state is check pointed and PCP
> >> Announce may be ignored, by those applications.
> >> 2) Application/PCP client on seeing ANNOUNCE, initiate requests for
> >>state
> >> reconstruction on PCP. If the state is check pointed, then a success
> >> response is received for the requests. If the success is not received,
> >> then Applications can cleanup.
> >
> >Option 1 will reduce the chatter of check-pointed applications not
> >initiating state resumption.
> Yes, but if we consider back to back failure scenario it _may_ have to
> respond to ANNOUNCE.
> >
> >
> >> >
> >> >> For the mappings that are not check pointed, depending on
> >>availability
> >> >> they will be honored on first come first serve basis.
> >> >> Is there an issue with this, so that I can update in the next
> >>version.
> >> >
> >> >This may work, you may want to explicitly mention the above informati=
on
> >> >in the draft.
> >> Sure.
> >> >
> >> >> >
> >> >> >> >
> >> >> >> >6) How does an application developer know if syncing the state =
is
> >> >> >> >required or not ?
> >> >> >> >The problem could be that if every application says it's
> >>connections
> >> >> >>need
> >> >> >> >to be check-pointed then there is no benefit.
> >> >> >> It is application and user dependent. Please refer section 7 in
> >>the
> >> >> >>draft.
> >> >> >
> >> >> >The problem is every App developer would think that his applicatio=
n
> >>is
> >> >> >important and asks for HA. A set of guidelines is probably needed =
in
> >> >>the
> >> >> >draft for application developers to help decide when to ask for HA
> >>or
> >> >>not
> >> >> >?
> >> >> Ok, I will include the guide lines in the next draft. But, note for
> >>some
> >> >> set of applications, an application that is critical to one user ma=
y
> >>not
> >> >> be critical to another user. That is where both user/application
> >>have to
> >> >> determine if it is critical.
> >> >
> >> >I think there is one more aspect to consider, if the application can
> >> >survive PCP server crash. For example if application based on PCP
> >> >ANNOUNCE can do state resumption or application is using multiple pat=
hs
> >> >(MPTCP) that though it is a business critical application but does no=
t
> >> >need to ask for check-pointing the connection.
> >> If an application can survive PCP server crash, and if there is HA, th=
en
> >> it can still continue to use that path if state is check pointed right=
 ?
> >
> >But the goal is to check-point only few connections. The above category
> >of applications though business-critical do not need check-pointing.
> Is it because if one path fails, other path provides service continuity?
> Having HA at each path level is not a bad thing right? Anyway, if
> application doesn't require HA it need not initiate HA. I feel the goal i=
s
> to check point any critical application that requested HA.
> >
> >> >
> >> >> And as a security consideration, admin may
> >> >> configure max checkpoints per user.
> >> >
> >> >Does that mean PCP auth (draft-ietf-pcp-authentication) is mandatory
> >>for
> >> >the PCP server to identify a user ?
> >> Are you saying in the context of rogue user or application ?
> >
> >PCP authentication ensures only valid users gain access to use the PCP
> >servers and not rouge users. This will also help to enforce user-based
> >policy limits like number of mapping to checkpoint per user.
> Yes, PCP authentication ensures that only valid users gain access to PCP
> servers and not rogue user. But, that doesn't mean that every application
> that does PCP authentication require HA and every application that doesn'=
t
> do PCP auth doesn't require HA, as Authentication and HA are addressing
> two different issues. Or am I missing something ?=20

PCP Authentication can be done once and used by all the PCP-aware applicati=
ons on the endpoint.

-Tiru.

> Note, the approach that
> is suggested in the draft would work in both PCP authentication case and
> non authentication case.
> >
> >-Tiru.
> >
> >> >
> >> >-Tiru.
> >> >
> >> >> Please comment, so I will update it in
> >> >> the next version of draft.
> >> >> >
> >> >> >-Tiru.
> >> >> >
> >> >> >> >
> >> >> >> >Cheers,
> >> >> >> >-Tiru.
> >> >> >> >
> >> >> >> >> -----Original Message-----
> >> >> >> >> From: Suresh Kumar Vinapamula Venkata
> >>[mailto:sureshk@juniper.net]
> >> >> >> >> Sent: Wednesday, November 06, 2013 12:33 AM
> >> >> >> >> To: pcp@ietf.org
> >> >> >> >> Subject: Re: [pcp] New Version Notification for
> >> >> >> >>draft-vinapamula-flow-ha-
> >> >> >> >> 00.txt
> >> >> >> >>
> >> >> >> >> Hi All,
> >> >> >> >>
> >> >> >> >> This draft talks about issues with checkpointing flows in
> >>current
> >> >> >> >> deployment, and how they can be addressed and handled
> >>efficiently
> >> >> >>with
> >> >> >> >>PCP.
> >> >> >> >> Please review and share your comments.
> >> >> >> >>
> >> >> >> >> Thanks
> >> >> >> >> Suresh
> >> >> >> >>
> >> >> >> >> On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
> >> >> >> >> <sureshk@juniper.net> wrote:
> >> >> >> >>
> >> >> >> >> >Dear All,
> >> >> >> >> >
> >> >> >> >> >We submitted a new draft that sketches flow high availabilit=
y
> >> >> >>through
> >> >> >> >>PCP.
> >> >> >> >> >Please review.
> >> >> >> >> >
> >> >> >> >> >-Suresh
> >> >> >> >> >
> >> >> >> >> >On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
> >> >> >> >> ><internet-drafts@ietf.org> wrote:
> >> >> >> >> >
> >> >> >> >> >>
> >> >> >> >> >>A new version of I-D, draft-vinapamula-flow-ha-00.txt
> >> >> >> >> >>has been successfully submitted by Suresh Vinapamula and
> >>posted
> >> >>to
> >> >> >>the
> >> >> >> >> >>IETF repository.
> >> >> >> >> >>
> >> >> >> >> >>Filename:	 draft-vinapamula-flow-ha
> >> >> >> >> >>Revision:	 00
> >> >> >> >> >>Title:		 Flow high availability through PCP
> >> >> >> >> >>Creation date:	 2013-10-14
> >> >> >> >> >>Group:		 Individual Submission
> >> >> >> >> >>Number of pages: 5
> >> >> >> >> >>URL:
> >> >> >> >>
> >> >>>>http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.tx=
t
> >> >> >> >> >>Status:
> >> >> >> >>http://datatracker.ietf.org/doc/draft-vinapamula-flow-ha
> >> >> >> >> >>Htmlized:
> >> >> >> >>http://tools.ietf.org/html/draft-vinapamula-flow-ha-00
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>Abstract:
> >> >> >> >> >>   This document describes a mechanism for a host signal
> >>Network
> >> >> >> >>Address
> >> >> >> >> >>   Translator's (NAT) High Availability (HA) module to
> >> >>checkpoint
> >> >> >> >> >>   interested connections.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>Please note that it may take a couple of minutes from the
> >>time
> >> >>of
> >> >> >> >> >>submission
> >> >> >> >> >>until the htmlized version and diff are available at
> >> >> >>tools.ietf.org.
> >> >> >> >> >>
> >> >> >> >> >>The IETF Secretariat
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >
> >> >> >> >>
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >
> >> >
> >> >
> >>
> >
> >
> >
>=20


From ssenthil@cisco.com  Wed Nov 20 08:13:43 2013
Return-Path: <ssenthil@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DDA51ADF8E for <pcp@ietfa.amsl.com>; Wed, 20 Nov 2013 08:13:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.026
X-Spam-Level: 
X-Spam-Status: No, score=-10.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u9u58oFg1Hcp for <pcp@ietfa.amsl.com>; Wed, 20 Nov 2013 08:13:39 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) by ietfa.amsl.com (Postfix) with ESMTP id 612E01ADE8B for <pcp@ietf.org>; Wed, 20 Nov 2013 08:13:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14385; q=dns/txt; s=iport; t=1384964012; x=1386173612; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=MFIrD4EgeaUP/npTfw4WLEY3Bo1ESxddjRtU/s1pGAE=; b=hc2jjYnANUb5/DZXMWQOlImSE6AVAmvJ8fYjqCIQw4MgzJjQc88U8x8q OWVtcUUVkF02My60WparF4RoA0Pnkw8y00WmcF4YJ5gRJXA9IwsDT5cP0 Wgh/2SAUPsXpa/eTUKY3XPKx5DfnqdktFm0KyS80Fkr2M/osdYEZMqj1L A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAK/ejFKtJV2a/2dsb2JhbABPCoMHOFO+Y4EWFnSCJQEBAQQBAQE3MgICBgEOBgEIEQQBAQEeCS4LFAkIAgQBEgmHeA3AQReOAg8LAQGBNAwGhCwDmBKBL5BegyiBcTk
X-IronPort-AV: E=Sophos;i="4.93,738,1378857600";  d="scan'208";a="945268"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-7.cisco.com with ESMTP; 20 Nov 2013 16:13:31 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rAKGDVvt002659 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 20 Nov 2013 16:13:31 GMT
Received: from xmb-rcd-x15.cisco.com ([169.254.5.54]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0123.003; Wed, 20 Nov 2013 10:13:30 -0600
From: "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "Suresh Kumar Vinapamula Venkata" <sureshk@juniper.net>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHOyLL/gCwN85yQD0CDyU03potPTJn0KroAgCNbqgCADecOgIAALVcAgAI4SoCAAs5VAIABxfIAgAEmiYCAAJfLAIAAF9cAgAAkCICAACPxAA==
Date: Wed, 20 Nov 2013 16:13:29 +0000
Message-ID: <CEB248B3.CE9E7%ssenthil@cisco.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A24268969@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.8.130913
x-originating-ip: [64.102.83.140]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <051D40E49ABDF348B373B26F985D2433@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2013 16:13:43 -0000

<snip>
>> >> >> >
>> >> >> >The problem is how does the network know that the mapping is for
>>a
>> >> >> >business critical application or not ?
>> >> >> >Network needs a mechanism to distinguish b/w the applications.
>> >> >> A bit in the PCP header indicates that it is critical right ? An
>> >> >> application can use PCP medium to communicate to network about
>>this.
>> >> >
>> >> >The problem is any application can set this bit. How does the
>>network
>> >> >distinguish b/w applications ?
>> >> Yes, any application can set, but user also has to honor it right ?
>> >
>> >Are you referring to some GUI option where the user will select HA is
>> >required or not ?
>> Shouldn't this be left to implementation ? For example, it could be at
>> installation also.
>
>That will be static configuration.

I am not sure what the "user" is referred to here, but the operator who
controls the
PCP server and the middleboxes will have an administrative policy whether
to honor=20
the HA/Checkpoint required flag. So the application can request all it
wants, but the=20
authoritative control will reside in the network. The policy can allow all
applications for a given user,
Only certain applications or only certain flows or certain number of flow
per application etc.

Senthil



>
>> >
>> >> >
>> >> >> >
>> >> >> >> >
>> >> >> >> >2)HA is applicable for both NAT and Firewall devices. I would
>> >> >>suggest
>> >> >> >>not
>> >> >> >> >to restrict the draft to only NAT scenarios.
>> >> >> >> Yes, the intention is to not restrict to NAT only service.
>> >> >> >> >
>> >> >> >> >3)In Active-Standby HA, switch-over is triggered not just
>> >>because of
>> >> >> >> >Active rebooting but also because of WAN-link failures. Are
>>you
>> >> >> >>assuming
>> >> >> >> >HA deployments with provider-independent or provider-dependent
>> >> >> >>addresses ?
>> >> >> >> I am not sure what you meant by provider-independent or
>> >> >> >>provider-dependent
>> >> >> >> addresses. Please clarify for my response.
>> >> >> >
>> >> >> >Refer to http://tools.ietf.org/html/rfc4116 on PI and PA.
>> >> >> Oh, you meant provider aggregatable and provider independent. Are
>>you
>> >> >> talking in the context of multi-homing ?
>> >> >
>> >> >Yes.
>> >> >
>> >> >> Isn't this taken care at link level or route level
>> >>redundancy/update? If
>> >> >> not, sorry, I am trying to understand your question.
>> >> >
>> >> >If you could add to the Appendix the deployment scenarios you had
>> >> >considered that would help.
>> >> >I was thinking of (Active-Standby) with multiple WAN links (Primary
>>and
>> >> >Backup).
>> >> Yes, I can include some of the deployment scenarios. But I am still
>> >>trying
>> >> to understand your question in the current context. If it is link
>>level
>> >> redundancy with same provider, then it is taken care at the link
>>level
>> >>it
>> >> self right? If with multiple providers, it is taken care at routing
>> >>right ?
>> >
>> >I am referring to a use case where two routers are used for
>> >Active-Standby with multiple WAN links one primary and other backup.
>> >For HA, it will only work with PI addresses.
>> I still don't understand this. When two routers belong to same provider,
>> now sure why it has to be PI addresses only. Also, when they are with
>> different providers, how do you expect state to be check pointed across
>> routers ?
>
>Each vendor has its proprietary technique to sync Firewall and NAT
>states.=20
>
>> >
>> >> >
>> >> >> >
>> >> >> >> >
>> >> >> >> >4)
>> >> >> >> >
>> >> >> >> >a) PCP third-party authorization
>> >>(draft-wing-pcp-third-party-authz)
>> >> >> >>could
>> >> >> >> >also be one way of telling the network that it's for a
>>business
>> >> >> >>critical
>> >> >> >> >application and connection can be synced implicitly without
>> >>explicit
>> >> >> >> >signaling.
>> >> >> >
>> >> >> >> Even without authorization also, if flows are to be check
>>pointed,
>> >> >>they
>> >> >> >> will be check pointed with this option.
>> >> >> >
>> >> >> >With third party authorization, PCP-aware server knows that the
>> >>mapping
>> >> >> >is for business critical applications and hence can sync the
>>state.
>> >> >> AFAIU, this draft doesn't talk that third party authorization is
>>for
>> >> >> business critical applications only. Please let me know if I am
>> >>missing
>> >> >> something ?
>> >> >
>> >> >One application may be business critical in one domain and may not
>>be
>> >> >another domain. For example let's say WebRTC calls to Stark
>>Industries
>> >> >may be business critical in one Enterprise but there is no business
>> >> >tie-up for Stark in another Enterprise and hence not business
>>critical.
>> >> >
>> >> >How does the PCP client set/reset this flag based on which network
>>the
>> >> >BYOD device is attached to ?
>> >> Yes, this is the same usage I was giving in my previous mail.
>> >> In that case, application user will determine if it is critical for
>>him,
>> >> when the application is launched.
>> >
>> >Are you referring to a user knob where for each application, user has
>>to
>> >enter critical or not (Something like High, Medium, Low priority) or
>> >input that that application needs HA or not. I am not sure if user in
>>all
>> >cases will be aware if application needs HA or not.
>> Yes, it is not for all applications. That is why I said it is for some
>>set
>> of applications this may be required.
>> >
>> >> >
>> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >b) Other possible ways could be checkpoint based on
>>destination
>> >> >> >> >port/address (For example HTTPS flows are more critical than
>> >>HTTP).
>> >> >> >> Admin can always configure that. This option gives more
>> >>flexibility.
>> >> >> >> >
>> >> >> >> >5)How does PCP ANNOUNCE work in this deployment ?
>> >> >> >> >I mean some connections on the host need to know that
>>PCP-aware
>> >> >> >> >NAT/Firewall has rebooted but other connections may not
>>because
>> >> >>their
>> >> >> >> >states are check-pointed.
>> >> >> >> I will get back to you on this.
>> >> >> >
>> >> >> >Ok.
>> >> >> I feel all connections should refresh their mappings just as how
>> >>they do
>> >> >> on seeing PCP ANNOUNCE.
>> >> >> For the mappings that are already check pointed, applications are
>> >> >> guaranteed to receive previous state of the mappings.
>> >> >
>> >> >So check-pointed application will ignore PCP ANNOUNCE ?
>> >
>> >> Here is where I have two thoughts and WG can comment on them.
>> >> 1) Application is given feedback that state is check pointed and PCP
>> >> Announce may be ignored, by those applications.
>> >> 2) Application/PCP client on seeing ANNOUNCE, initiate requests for
>> >>state
>> >> reconstruction on PCP. If the state is check pointed, then a success
>> >> response is received for the requests. If the success is not
>>received,
>> >> then Applications can cleanup.
>> >
>> >Option 1 will reduce the chatter of check-pointed applications not
>> >initiating state resumption.
>> Yes, but if we consider back to back failure scenario it _may_ have to
>> respond to ANNOUNCE.
>> >
>> >
>> >> >
>> >> >> For the mappings that are not check pointed, depending on
>> >>availability
>> >> >> they will be honored on first come first serve basis.
>> >> >> Is there an issue with this, so that I can update in the next
>> >>version.
>> >> >
>> >> >This may work, you may want to explicitly mention the above
>>information
>> >> >in the draft.
>> >> Sure.
>> >> >
>> >> >> >
>> >> >> >> >
>> >> >> >> >6) How does an application developer know if syncing the
>>state is
>> >> >> >> >required or not ?
>> >> >> >> >The problem could be that if every application says it's
>> >>connections
>> >> >> >>need
>> >> >> >> >to be check-pointed then there is no benefit.
>> >> >> >> It is application and user dependent. Please refer section 7 in
>> >>the
>> >> >> >>draft.
>> >> >> >
>> >> >> >The problem is every App developer would think that his
>>application
>> >>is
>> >> >> >important and asks for HA. A set of guidelines is probably
>>needed in
>> >> >>the
>> >> >> >draft for application developers to help decide when to ask for
>>HA
>> >>or
>> >> >>not
>> >> >> >?
>> >> >> Ok, I will include the guide lines in the next draft. But, note
>>for
>> >>some
>> >> >> set of applications, an application that is critical to one user
>>may
>> >>not
>> >> >> be critical to another user. That is where both user/application
>> >>have to
>> >> >> determine if it is critical.
>> >> >
>> >> >I think there is one more aspect to consider, if the application can
>> >> >survive PCP server crash. For example if application based on PCP
>> >> >ANNOUNCE can do state resumption or application is using multiple
>>paths
>> >> >(MPTCP) that though it is a business critical application but does
>>not
>> >> >need to ask for check-pointing the connection.
>> >> If an application can survive PCP server crash, and if there is HA,
>>then
>> >> it can still continue to use that path if state is check pointed
>>right ?
>> >
>> >But the goal is to check-point only few connections. The above category
>> >of applications though business-critical do not need check-pointing.
>> Is it because if one path fails, other path provides service continuity?
>> Having HA at each path level is not a bad thing right? Anyway, if
>> application doesn't require HA it need not initiate HA. I feel the goal
>>is
>> to check point any critical application that requested HA.
>> >
>> >> >
>> >> >> And as a security consideration, admin may
>> >> >> configure max checkpoints per user.
>> >> >
>> >> >Does that mean PCP auth (draft-ietf-pcp-authentication) is mandatory
>> >>for
>> >> >the PCP server to identify a user ?
>> >> Are you saying in the context of rogue user or application ?
>> >
>> >PCP authentication ensures only valid users gain access to use the PCP
>> >servers and not rouge users. This will also help to enforce user-based
>> >policy limits like number of mapping to checkpoint per user.
>> Yes, PCP authentication ensures that only valid users gain access to PCP
>> servers and not rogue user. But, that doesn't mean that every
>>application
>> that does PCP authentication require HA and every application that
>>doesn't
>> do PCP auth doesn't require HA, as Authentication and HA are addressing
>> two different issues. Or am I missing something ?
>
>PCP Authentication can be done once and used by all the PCP-aware
>applications on the endpoint.
>
>-Tiru.
>
>> Note, the approach that
>> is suggested in the draft would work in both PCP authentication case and
>> non authentication case.
>> >
>> >-Tiru.
>> >
>> >> >
>> >> >-Tiru.
>> >> >
>> >> >> Please comment, so I will update it in
>> >> >> the next version of draft.
>> >> >> >
>> >> >> >-Tiru.
>> >> >> >
>> >> >> >> >
>> >> >> >> >Cheers,
>> >> >> >> >-Tiru.
>> >> >> >> >
>> >> >> >> >> -----Original Message-----
>> >> >> >> >> From: Suresh Kumar Vinapamula Venkata
>> >>[mailto:sureshk@juniper.net]
>> >> >> >> >> Sent: Wednesday, November 06, 2013 12:33 AM
>> >> >> >> >> To: pcp@ietf.org
>> >> >> >> >> Subject: Re: [pcp] New Version Notification for
>> >> >> >> >>draft-vinapamula-flow-ha-
>> >> >> >> >> 00.txt
>> >> >> >> >>
>> >> >> >> >> Hi All,
>> >> >> >> >>
>> >> >> >> >> This draft talks about issues with checkpointing flows in
>> >>current
>> >> >> >> >> deployment, and how they can be addressed and handled
>> >>efficiently
>> >> >> >>with
>> >> >> >> >>PCP.
>> >> >> >> >> Please review and share your comments.
>> >> >> >> >>
>> >> >> >> >> Thanks
>> >> >> >> >> Suresh
>> >> >> >> >>
>> >> >> >> >> On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
>> >> >> >> >> <sureshk@juniper.net> wrote:
>> >> >> >> >>
>> >> >> >> >> >Dear All,
>> >> >> >> >> >
>> >> >> >> >> >We submitted a new draft that sketches flow high
>>availability
>> >> >> >>through
>> >> >> >> >>PCP.
>> >> >> >> >> >Please review.
>> >> >> >> >> >
>> >> >> >> >> >-Suresh
>> >> >> >> >> >
>> >> >> >> >> >On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
>> >> >> >> >> ><internet-drafts@ietf.org> wrote:
>> >> >> >> >> >
>> >> >> >> >> >>
>> >> >> >> >> >>A new version of I-D, draft-vinapamula-flow-ha-00.txt
>> >> >> >> >> >>has been successfully submitted by Suresh Vinapamula and
>> >>posted
>> >> >>to
>> >> >> >>the
>> >> >> >> >> >>IETF repository.
>> >> >> >> >> >>
>> >> >> >> >> >>Filename:	 draft-vinapamula-flow-ha
>> >> >> >> >> >>Revision:	 00
>> >> >> >> >> >>Title:		 Flow high availability through PCP
>> >> >> >> >> >>Creation date:	 2013-10-14
>> >> >> >> >> >>Group:		 Individual Submission
>> >> >> >> >> >>Number of pages: 5
>> >> >> >> >> >>URL:
>> >> >> >> >>
>> >>=20
>>>>>>http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.txt
>> >> >> >> >> >>Status:
>> >> >> >> >>http://datatracker.ietf.org/doc/draft-vinapamula-flow-ha
>> >> >> >> >> >>Htmlized:
>> >> >> >> >>http://tools.ietf.org/html/draft-vinapamula-flow-ha-00
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>Abstract:
>> >> >> >> >> >>   This document describes a mechanism for a host signal
>> >>Network
>> >> >> >> >>Address
>> >> >> >> >> >>   Translator's (NAT) High Availability (HA) module to
>> >> >>checkpoint
>> >> >> >> >> >>   interested connections.
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>Please note that it may take a couple of minutes from the
>> >>time
>> >> >>of
>> >> >> >> >> >>submission
>> >> >> >> >> >>until the htmlized version and diff are available at
>> >> >> >>tools.ietf.org.
>> >> >> >> >> >>
>> >> >> >> >> >>The IETF Secretariat
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >>
>> >> >
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>>=20
>
>_______________________________________________
>pcp mailing list
>pcp@ietf.org
>https://www.ietf.org/mailman/listinfo/pcp


From internet-drafts@ietf.org  Wed Nov 20 08:19:24 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 752241ADFE3; Wed, 20 Nov 2013 08:19:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K4jEmy5GMJid; Wed, 20 Nov 2013 08:19:23 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 326FB1ADF8E; Wed, 20 Nov 2013 08:19:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131120161923.11850.5964.idtracker@ietfa.amsl.com>
Date: Wed, 20 Nov 2013 08:19:23 -0800
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-port-set-04.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2013 16:19:24 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Port Control Protocol Working Group of th=
e IETF.

	Title           : Port Control Protocol (PCP) Extension for Port Set Alloc=
ation
	Author(s)       : Qiong Sun
                          Mohamed Boucadair
                          Senthil Sivakumar
                          Cathy Zhou
                          Tina Tsou
                          Simon Perreault
	Filename        : draft-ietf-pcp-port-set-04.txt
	Pages           : 17
	Date            : 2013-11-20

Abstract:
   This document defines an extension to the Port Control Protocol (PCP)
   allowing clients to manipulate sets of ports as a whole.  This is
   accomplished by a new MAP option: PORT_SET.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pcp-port-set

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pcp-port-set-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcp-port-set-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From simon.perreault@viagenie.ca  Wed Nov 20 08:22:12 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BF721AE3F1 for <pcp@ietfa.amsl.com>; Wed, 20 Nov 2013 08:22:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.426
X-Spam-Level: 
X-Spam-Status: No, score=-2.426 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iOhODfWXGXM8 for <pcp@ietfa.amsl.com>; Wed, 20 Nov 2013 08:22:10 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 85D7D1AE06A for <pcp@ietf.org>; Wed, 20 Nov 2013 08:22:10 -0800 (PST)
Received: from porto.nomis80.org (ringo.viagenie.ca [206.123.31.67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 02EB0401FE for <pcp@ietf.org>; Wed, 20 Nov 2013 11:22:03 -0500 (EST)
Message-ID: <528CE1AB.4030008@viagenie.ca>
Date: Wed, 20 Nov 2013 11:22:03 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: pcp@ietf.org
References: <20131120161923.11850.5964.idtracker@ietfa.amsl.com>
In-Reply-To: <20131120161923.11850.5964.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [pcp] I-D Action: draft-ietf-pcp-port-set-04.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2013 16:22:12 -0000

This revision addresses comments received during WGLC and IETF 88. There 
are quite a few text changes, but no protocol changes.

Simon

Le 2013-11-20 11:19, internet-drafts@ietf.org a écrit :
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the Port Control Protocol Working Group of the IETF.
>
> 	Title           : Port Control Protocol (PCP) Extension for Port Set Allocation
> 	Author(s)       : Qiong Sun
>                            Mohamed Boucadair
>                            Senthil Sivakumar
>                            Cathy Zhou
>                            Tina Tsou
>                            Simon Perreault
> 	Filename        : draft-ietf-pcp-port-set-04.txt
> 	Pages           : 17
> 	Date            : 2013-11-20
>
> Abstract:
>     This document defines an extension to the Port Control Protocol (PCP)
>     allowing clients to manipulate sets of ports as a whole.  This is
>     accomplished by a new MAP option: PORT_SET.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-pcp-port-set
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-pcp-port-set-04
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-pcp-port-set-04
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp
>


-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From sureshk@juniper.net  Thu Nov 21 09:54:24 2013
Return-Path: <sureshk@juniper.net>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC6711AE0BD for <pcp@ietfa.amsl.com>; Thu, 21 Nov 2013 09:54:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id leWkF3o8c0_8 for <pcp@ietfa.amsl.com>; Thu, 21 Nov 2013 09:54:20 -0800 (PST)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0187.outbound.messaging.microsoft.com [213.199.154.187]) by ietfa.amsl.com (Postfix) with ESMTP id 7374D1AD79D for <pcp@ietf.org>; Thu, 21 Nov 2013 09:54:19 -0800 (PST)
Received: from mail117-db8-R.bigfish.com (10.174.8.235) by DB8EHSOBE038.bigfish.com (10.174.4.101) with Microsoft SMTP Server id 14.1.225.22; Thu, 21 Nov 2013 17:54:12 +0000
Received: from mail117-db8 (localhost [127.0.0.1])	by mail117-db8-R.bigfish.com (Postfix) with ESMTP id 0AE103C0357;	Thu, 21 Nov 2013 17:54:12 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -28
X-BigFish: VPS-28(z579ehzbb2dI98dI9371I936eI146fI542I1432I14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL17326ah8275bh8275dh1de097h186068hz2fh109h2a8h839h944he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1fe8h1ff5h209eh2216h22d0h1155h)
Received-SPF: pass (mail117-db8: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=sureshk@juniper.net; helo=BL2PRD0510HT002.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(51704005)(377454003)(377424004)(479174003)(13464003)(199002)(189002)(52314003)(53754006)(24454002)(47976001)(59766001)(74876001)(83322001)(81686001)(19580395003)(49866001)(87936001)(80976001)(74706001)(50986001)(51856001)(66066001)(54356001)(77982001)(81816001)(81342001)(19580405001)(2656002)(76482001)(79102001)(4396001)(54316002)(47736001)(56776001)(87266001)(46102001)(15202345003)(53806001)(63696002)(80022001)(56816003)(83072001)(74366001)(76796001)(76786001)(31966008)(36756003)(81542001)(83506001)(74502001)(47446002)(74662001)(15975445006)(85306002)(76176001)(65816001)(69226001); DIR:OUT; SFP:; SCL:1; SRVR:DM2PR05MB287; H:DM2PR05MB288.namprd05.prod.outlook.com; CLIP:66.129.239.13; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail117-db8 (localhost.localdomain [127.0.0.1]) by mail117-db8 (MessageSwitch) id 138505644919367_1615; Thu, 21 Nov 2013 17:54:09 +0000 (UTC)
Received: from DB8EHSMHS004.bigfish.com (unknown [10.174.8.226])	by mail117-db8.bigfish.com (Postfix) with ESMTP id F3BE0320081; Thu, 21 Nov 2013 17:54:08 +0000 (UTC)
Received: from BL2PRD0510HT002.namprd05.prod.outlook.com (157.56.240.101) by DB8EHSMHS004.bigfish.com (10.174.4.14) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 21 Nov 2013 17:54:02 +0000
Received: from DM2PR05MB287.namprd05.prod.outlook.com (10.141.101.27) by BL2PRD0510HT002.namprd05.prod.outlook.com (10.255.100.37) with Microsoft SMTP Server (TLS) id 14.16.383.1; Thu, 21 Nov 2013 17:53:58 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com (10.141.101.11) by DM2PR05MB287.namprd05.prod.outlook.com (10.141.101.27) with Microsoft SMTP Server (TLS) id 15.0.800.7; Thu, 21 Nov 2013 17:53:57 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) by DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) with mapi id 15.00.0800.005; Thu, 21 Nov 2013 17:53:57 +0000
From: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
Thread-Index: AQHO2lmbQ60NWXm7bU68b/cwqgHqfJok5Y+A//+nOICAAr5pgIACSDUAgAJMEwCAAKBfAIABHfUA//+RuACAAKomgIABsM6A
Date: Thu, 21 Nov 2013 17:53:56 +0000
Message-ID: <CEB21854.28A38%sureshk@juniper.net>
In-Reply-To: <913383AAA69FF945B8F946018B75898A24268969@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [66.129.239.13]
x-forefront-prvs: 0037FD6480
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FC5BF9497D02494A8F45C34EB48EE354@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [pcp] New Version Notification for draft-vinapamula-flow-ha-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2013 17:54:24 -0000

Please see inline.

On 11/20/13 12:04 AM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
wrote:

>> -----Original Message-----
>> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
>> Sent: Wednesday, November 20, 2013 11:26 AM
>> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
>> Subject: Re: [pcp] New Version Notification for
>>draft-vinapamula-flow-ha-
>> 00.txt
>>=20
>> Hi Tiru,
>>=20
>> Please see inline.
>>=20
>> On 11/19/13 8:30 PM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
>> wrote:
>>=20
>> >Hi Suresh,
>> >
>> >Please see inline
>> >
>> >> -----Original Message-----
>> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
>> >> Sent: Wednesday, November 20, 2013 12:57 AM
>> >> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
>> >> Subject: Re: [pcp] New Version Notification for
>> >>draft-vinapamula-flow-ha-
>> >> 00.txt
>> >>
>> >> Hi Tiru,
>> >>
>> >> Please see inline.
>> >>
>> >> On 11/18/13 5:53 PM, "Tirumaleswar Reddy (tireddy)"
>><tireddy@cisco.com>
>> >> wrote:
>> >>
>> >> >Hi Suresh,
>> >> >
>> >> >Please see inline
>> >> >
>> >> >> -----Original Message-----
>> >> >> From: Suresh Kumar Vinapamula Venkata [mailto:sureshk@juniper.net]
>> >> >> Sent: Monday, November 18, 2013 4:18 AM
>> >> >> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
>> >> >> Subject: Re: [pcp] New Version Notification for
>> >> >>draft-vinapamula-flow-ha-
>> >> >> 00.txt
>> >> >>
>> >> >> Hi Tiru,
>> >> >>
>> >> >> Thanks for your followup questions. Please see responses inline.
>> >> >>
>> >> >> On 11/15/13 7:57 PM, "Tirumaleswar Reddy (tireddy)"
>> >><tireddy@cisco.com>
>> >> >> wrote:
>> >> >>
>> >> >> >Hi Suresh,
>> >> >> >
>> >> >> >Please see inline
>> >> >> >
>> >> >> >> -----Original Message-----
>> >> >> >> From: Suresh Kumar Vinapamula Venkata
>>[mailto:sureshk@juniper.net]
>> >> >> >> Sent: Thursday, November 14, 2013 11:33 PM
>> >> >> >> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org
>> >> >> >> Subject: Re: [pcp] New Version Notification for
>> >> >> >>draft-vinapamula-flow-ha-
>> >> >> >> 00.txt
>> >> >> >>
>> >> >> >> Hi Tiru,
>> >> >> >>
>> >> >> >> Thanks for your comments. Please see inline for responses.
>> >> >> >>
>> >> >> >> On 11/14/13 7:21 AM, "Tirumaleswar Reddy (tireddy)"
>> >> >><tireddy@cisco.com>
>> >> >> >> wrote:
>> >> >> >>
>> >> >> >> >Hi Suresh,
>> >> >> >> >
>> >> >> >> >My initial comments
>> >> >> >> >
>> >> >> >> >1)Why cannot the problem be solved for example by the PCP
>>client
>> >> >> >>sending
>> >> >> >> >PEER with a long lifetime and if the lifetime is higher than a
>> >> >> >>particular
>> >> >> >> >threshold only those connections are synced implicitly ?
>> >> >> >> How would application know what is the threshold life time for
>>it
>> >>to
>> >> >> >> request life time greater than that? What if a connection is
>> >>critical
>> >> >> >>but
>> >> >> >> is short lived than the configured HA life time?
>> >> >> >
>> >> >> >Good point. we don't want short-lived business critical sessions
>>to
>> >>set
>> >> >> >long lifetime just for HA.
>> >> >> >
>> >> >> >> Similarly, what if a
>> >> >> >> connection is not business critical, but its life time greater
>> >>than
>> >> >> >> configured HA life time?
>> >> >> >
>> >> >> >The problem is how does the network know that the mapping is for
>>a
>> >> >> >business critical application or not ?
>> >> >> >Network needs a mechanism to distinguish b/w the applications.
>> >> >> A bit in the PCP header indicates that it is critical right ? An
>> >> >> application can use PCP medium to communicate to network about
>>this.
>> >> >
>> >> >The problem is any application can set this bit. How does the
>>network
>> >> >distinguish b/w applications ?
>> >> Yes, any application can set, but user also has to honor it right ?
>> >
>> >Are you referring to some GUI option where the user will select HA is
>> >required or not ?
>> Shouldn't this be left to implementation ? For example, it could be at
>> installation also.
>
>That will be static configuration.
Yes, for certain applications, it can be static. For certain applications,
user intervention may not be required. For certain applications, user
intervention is required, every time an application is started. I feel it
should be application specific. Please let me know if you think otherwise.
>=20
>
>> >
>> >> >
>> >> >> >
>> >> >> >> >
>> >> >> >> >2)HA is applicable for both NAT and Firewall devices. I would
>> >> >>suggest
>> >> >> >>not
>> >> >> >> >to restrict the draft to only NAT scenarios.
>> >> >> >> Yes, the intention is to not restrict to NAT only service.
>> >> >> >> >
>> >> >> >> >3)In Active-Standby HA, switch-over is triggered not just
>> >>because of
>> >> >> >> >Active rebooting but also because of WAN-link failures. Are
>>you
>> >> >> >>assuming
>> >> >> >> >HA deployments with provider-independent or provider-dependent
>> >> >> >>addresses ?
>> >> >> >> I am not sure what you meant by provider-independent or
>> >> >> >>provider-dependent
>> >> >> >> addresses. Please clarify for my response.
>> >> >> >
>> >> >> >Refer to http://tools.ietf.org/html/rfc4116 on PI and PA.
>> >> >> Oh, you meant provider aggregatable and provider independent. Are
>>you
>> >> >> talking in the context of multi-homing ?
>> >> >
>> >> >Yes.
>> >> >
>> >> >> Isn't this taken care at link level or route level
>> >>redundancy/update? If
>> >> >> not, sorry, I am trying to understand your question.
>> >> >
>> >> >If you could add to the Appendix the deployment scenarios you had
>> >> >considered that would help.
>> >> >I was thinking of (Active-Standby) with multiple WAN links (Primary
>>and
>> >> >Backup).
>> >> Yes, I can include some of the deployment scenarios. But I am still
>> >>trying
>> >> to understand your question in the current context. If it is link
>>level
>> >> redundancy with same provider, then it is taken care at the link
>>level
>> >>it
>> >> self right? If with multiple providers, it is taken care at routing
>> >>right ?
>> >
>> >I am referring to a use case where two routers are used for
>> >Active-Standby with multiple WAN links one primary and other backup.
>> >For HA, it will only work with PI addresses.
>> I still don't understand this. When two routers belong to same provider,
>> now sure why it has to be PI addresses only. Also, when they are with
>> different providers, how do you expect state to be check pointed across
>> routers ?
>
>Each vendor has its proprietary technique to sync Firewall and NAT states.
Yes, but across providers' routers do you expect sync to happen?
>=20
>
>> >
>> >> >
>> >> >> >
>> >> >> >> >
>> >> >> >> >4)
>> >> >> >> >
>> >> >> >> >a) PCP third-party authorization
>> >>(draft-wing-pcp-third-party-authz)
>> >> >> >>could
>> >> >> >> >also be one way of telling the network that it's for a
>>business
>> >> >> >>critical
>> >> >> >> >application and connection can be synced implicitly without
>> >>explicit
>> >> >> >> >signaling.
>> >> >> >
>> >> >> >> Even without authorization also, if flows are to be check
>>pointed,
>> >> >>they
>> >> >> >> will be check pointed with this option.
>> >> >> >
>> >> >> >With third party authorization, PCP-aware server knows that the
>> >>mapping
>> >> >> >is for business critical applications and hence can sync the
>>state.
>> >> >> AFAIU, this draft doesn't talk that third party authorization is
>>for
>> >> >> business critical applications only. Please let me know if I am
>> >>missing
>> >> >> something ?
>> >> >
>> >> >One application may be business critical in one domain and may not
>>be
>> >> >another domain. For example let's say WebRTC calls to Stark
>>Industries
>> >> >may be business critical in one Enterprise but there is no business
>> >> >tie-up for Stark in another Enterprise and hence not business
>>critical.
>> >> >
>> >> >How does the PCP client set/reset this flag based on which network
>>the
>> >> >BYOD device is attached to ?
>> >> Yes, this is the same usage I was giving in my previous mail.
>> >> In that case, application user will determine if it is critical for
>>him,
>> >> when the application is launched.
>> >
>> >Are you referring to a user knob where for each application, user has
>>to
>> >enter critical or not (Something like High, Medium, Low priority) or
>> >input that that application needs HA or not. I am not sure if user in
>>all
>> >cases will be aware if application needs HA or not.
>> Yes, it is not for all applications. That is why I said it is for some
>>set
>> of applications this may be required.
>> >
>> >> >
>> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >b) Other possible ways could be checkpoint based on
>>destination
>> >> >> >> >port/address (For example HTTPS flows are more critical than
>> >>HTTP).
>> >> >> >> Admin can always configure that. This option gives more
>> >>flexibility.
>> >> >> >> >
>> >> >> >> >5)How does PCP ANNOUNCE work in this deployment ?
>> >> >> >> >I mean some connections on the host need to know that
>>PCP-aware
>> >> >> >> >NAT/Firewall has rebooted but other connections may not
>>because
>> >> >>their
>> >> >> >> >states are check-pointed.
>> >> >> >> I will get back to you on this.
>> >> >> >
>> >> >> >Ok.
>> >> >> I feel all connections should refresh their mappings just as how
>> >>they do
>> >> >> on seeing PCP ANNOUNCE.
>> >> >> For the mappings that are already check pointed, applications are
>> >> >> guaranteed to receive previous state of the mappings.
>> >> >
>> >> >So check-pointed application will ignore PCP ANNOUNCE ?
>> >
>> >> Here is where I have two thoughts and WG can comment on them.
>> >> 1) Application is given feedback that state is check pointed and PCP
>> >> Announce may be ignored, by those applications.
>> >> 2) Application/PCP client on seeing ANNOUNCE, initiate requests for
>> >>state
>> >> reconstruction on PCP. If the state is check pointed, then a success
>> >> response is received for the requests. If the success is not
>>received,
>> >> then Applications can cleanup.
>> >
>> >Option 1 will reduce the chatter of check-pointed applications not
>> >initiating state resumption.
>> Yes, but if we consider back to back failure scenario it _may_ have to
>> respond to ANNOUNCE.
>> >
>> >
>> >> >
>> >> >> For the mappings that are not check pointed, depending on
>> >>availability
>> >> >> they will be honored on first come first serve basis.
>> >> >> Is there an issue with this, so that I can update in the next
>> >>version.
>> >> >
>> >> >This may work, you may want to explicitly mention the above
>>information
>> >> >in the draft.
>> >> Sure.
>> >> >
>> >> >> >
>> >> >> >> >
>> >> >> >> >6) How does an application developer know if syncing the
>>state is
>> >> >> >> >required or not ?
>> >> >> >> >The problem could be that if every application says it's
>> >>connections
>> >> >> >>need
>> >> >> >> >to be check-pointed then there is no benefit.
>> >> >> >> It is application and user dependent. Please refer section 7 in
>> >>the
>> >> >> >>draft.
>> >> >> >
>> >> >> >The problem is every App developer would think that his
>>application
>> >>is
>> >> >> >important and asks for HA. A set of guidelines is probably
>>needed in
>> >> >>the
>> >> >> >draft for application developers to help decide when to ask for
>>HA
>> >>or
>> >> >>not
>> >> >> >?
>> >> >> Ok, I will include the guide lines in the next draft. But, note
>>for
>> >>some
>> >> >> set of applications, an application that is critical to one user
>>may
>> >>not
>> >> >> be critical to another user. That is where both user/application
>> >>have to
>> >> >> determine if it is critical.
>> >> >
>> >> >I think there is one more aspect to consider, if the application can
>> >> >survive PCP server crash. For example if application based on PCP
>> >> >ANNOUNCE can do state resumption or application is using multiple
>>paths
>> >> >(MPTCP) that though it is a business critical application but does
>>not
>> >> >need to ask for check-pointing the connection.
>> >> If an application can survive PCP server crash, and if there is HA,
>>then
>> >> it can still continue to use that path if state is check pointed
>>right ?
>> >
>> >But the goal is to check-point only few connections. The above category
>> >of applications though business-critical do not need check-pointing.
>> Is it because if one path fails, other path provides service continuity?
>> Having HA at each path level is not a bad thing right? Anyway, if
>> application doesn't require HA it need not initiate HA. I feel the goal
>>is
>> to check point any critical application that requested HA.
>> >
>> >> >
>> >> >> And as a security consideration, admin may
>> >> >> configure max checkpoints per user.
>> >> >
>> >> >Does that mean PCP auth (draft-ietf-pcp-authentication) is mandatory
>> >>for
>> >> >the PCP server to identify a user ?
>> >> Are you saying in the context of rogue user or application ?
>> >
>> >PCP authentication ensures only valid users gain access to use the PCP
>> >servers and not rouge users. This will also help to enforce user-based
>> >policy limits like number of mapping to checkpoint per user.
>> Yes, PCP authentication ensures that only valid users gain access to PCP
>> servers and not rogue user. But, that doesn't mean that every
>>application
>> that does PCP authentication require HA and every application that
>>doesn't
>> do PCP auth doesn't require HA, as Authentication and HA are addressing
>> two different issues. Or am I missing something ?
>
>PCP Authentication can be done once and used by all the PCP-aware
>applications on the endpoint.
Ok. Just to clarify my point, HA doesn't mandate authentication.
>
>-Tiru.
>
>> Note, the approach that
>> is suggested in the draft would work in both PCP authentication case and
>> non authentication case.
>> >
>> >-Tiru.
>> >
>> >> >
>> >> >-Tiru.
>> >> >
>> >> >> Please comment, so I will update it in
>> >> >> the next version of draft.
>> >> >> >
>> >> >> >-Tiru.
>> >> >> >
>> >> >> >> >
>> >> >> >> >Cheers,
>> >> >> >> >-Tiru.
>> >> >> >> >
>> >> >> >> >> -----Original Message-----
>> >> >> >> >> From: Suresh Kumar Vinapamula Venkata
>> >>[mailto:sureshk@juniper.net]
>> >> >> >> >> Sent: Wednesday, November 06, 2013 12:33 AM
>> >> >> >> >> To: pcp@ietf.org
>> >> >> >> >> Subject: Re: [pcp] New Version Notification for
>> >> >> >> >>draft-vinapamula-flow-ha-
>> >> >> >> >> 00.txt
>> >> >> >> >>
>> >> >> >> >> Hi All,
>> >> >> >> >>
>> >> >> >> >> This draft talks about issues with checkpointing flows in
>> >>current
>> >> >> >> >> deployment, and how they can be addressed and handled
>> >>efficiently
>> >> >> >>with
>> >> >> >> >>PCP.
>> >> >> >> >> Please review and share your comments.
>> >> >> >> >>
>> >> >> >> >> Thanks
>> >> >> >> >> Suresh
>> >> >> >> >>
>> >> >> >> >> On 10/14/13 1:05 AM, "Suresh Kumar Vinapamula Venkata"
>> >> >> >> >> <sureshk@juniper.net> wrote:
>> >> >> >> >>
>> >> >> >> >> >Dear All,
>> >> >> >> >> >
>> >> >> >> >> >We submitted a new draft that sketches flow high
>>availability
>> >> >> >>through
>> >> >> >> >>PCP.
>> >> >> >> >> >Please review.
>> >> >> >> >> >
>> >> >> >> >> >-Suresh
>> >> >> >> >> >
>> >> >> >> >> >On 10/14/13 12:56 AM, "internet-drafts@ietf.org"
>> >> >> >> >> ><internet-drafts@ietf.org> wrote:
>> >> >> >> >> >
>> >> >> >> >> >>
>> >> >> >> >> >>A new version of I-D, draft-vinapamula-flow-ha-00.txt
>> >> >> >> >> >>has been successfully submitted by Suresh Vinapamula and
>> >>posted
>> >> >>to
>> >> >> >>the
>> >> >> >> >> >>IETF repository.
>> >> >> >> >> >>
>> >> >> >> >> >>Filename:	 draft-vinapamula-flow-ha
>> >> >> >> >> >>Revision:	 00
>> >> >> >> >> >>Title:		 Flow high availability through PCP
>> >> >> >> >> >>Creation date:	 2013-10-14
>> >> >> >> >> >>Group:		 Individual Submission
>> >> >> >> >> >>Number of pages: 5
>> >> >> >> >> >>URL:
>> >> >> >> >>
>> >>=20
>>>>>>http://www.ietf.org/internet-drafts/draft-vinapamula-flow-ha-00.txt
>> >> >> >> >> >>Status:
>> >> >> >> >>http://datatracker.ietf.org/doc/draft-vinapamula-flow-ha
>> >> >> >> >> >>Htmlized:
>> >> >> >> >>http://tools.ietf.org/html/draft-vinapamula-flow-ha-00
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>Abstract:
>> >> >> >> >> >>   This document describes a mechanism for a host signal
>> >>Network
>> >> >> >> >>Address
>> >> >> >> >> >>   Translator's (NAT) High Availability (HA) module to
>> >> >>checkpoint
>> >> >> >> >> >>   interested connections.
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>Please note that it may take a couple of minutes from the
>> >>time
>> >> >>of
>> >> >> >> >> >>submission
>> >> >> >> >> >>until the htmlized version and diff are available at
>> >> >> >>tools.ietf.org.
>> >> >> >> >> >>
>> >> >> >> >> >>The IETF Secretariat
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >>
>> >> >
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>>=20
>
>


