
From nobody Fri May  2 01:10:44 2014
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 60FD71A0A7D for <pcp@ietfa.amsl.com>; Fri,  2 May 2014 01:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.552
X-Spam-Level: 
X-Spam-Status: No, score=-9.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_24=0.6, RP_MATCHES_RCVD=-0.651, 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 sK7G7m-DIxm6 for <pcp@ietfa.amsl.com>; Fri,  2 May 2014 01:10:40 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id A8D261A0A25 for <pcp@ietf.org>; Fri,  2 May 2014 01:10:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6972; q=dns/txt; s=iport; t=1399018238; x=1400227838; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=2p+iMz9vdGc99iwJldpvDlUVXqx4hrIPr102CVCuM1Y=; b=LBmikFQgwtGlIcz3OLwnYc1xfKmupFBISVVoWjbj5jIpVPaIrLvbPJBd 2R8GQMbhKtki+ATs0SVYz8dMOGA8vI7e2pt2fttHsmasdM6mIt62WC9uU e3Ye8yUPXsj/t/uBLXchllCrdnJdjz64bBQyQZhJng/p9oti82dPal/oN E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFADpSY1OtJV2c/2dsb2JhbABQCoMGT1eCZ8FmGXcWdIIlAQEBAwEjET4TBgEIEQEDAQEDAgYdAwIEHxEUAQIGCQEEARIIE4gSAwkIDaV1nSUNhkUXgSqLEYE7KxYogmk1gRUElz6DLotYhVuDNIFrJBw
X-IronPort-AV: E=Sophos;i="4.97,971,1389744000"; d="scan'208";a="40487150"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-5.cisco.com with ESMTP; 02 May 2014 08:10:38 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s428Abin007526 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 2 May 2014 08:10:38 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.104]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0123.003; Fri, 2 May 2014 03:10:37 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: GangChen <phdgang@gmail.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] review on draft-penno-pcp-mobile-qos
Thread-Index: Ac9l3eoIVgjV7EqXRHGwEHuUaRDMJw==
Date: Fri, 2 May 2014 08:10:36 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A2431F96A@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.65.42.244]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/ZlEQnmzKAf7drgkIMYBbH2MTtrE
Subject: Re: [pcp] review on draft-penno-pcp-mobile-qos
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: Fri, 02 May 2014 08:10:42 -0000

SGkgR2FuZywNCg0KVGhhbmtzIGZvciB0aGUgcmV2aWV3LiBQbGVhc2Ugc2VlIGlubGluZQ0KDQo+
IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEdhbmdDaGVuIFttYWlsdG86cGhk
Z2FuZ0BnbWFpbC5jb21dDQo+IFNlbnQ6IFR1ZXNkYXksIEFwcmlsIDI5LCAyMDE0IDExOjM3IEFN
DQo+IFRvOiBwY3BAaWV0Zi5vcmc7IGRyYWZ0LXBlbm5vLXBjcC1tb2JpbGUtcW9zQHRvb2xzLmll
dGYub3JnDQo+IFN1YmplY3Q6IFtwY3BdIHJldmlldyBvbiBkcmFmdC1wZW5uby1wY3AtbW9iaWxl
LXFvcw0KPiANCj4gSGVsbG8gQXV0aG9ycywNCj4gDQo+IEkgaGF2ZSByZXZpZXdlZCB0aGUgZHJh
ZnQuIFRoZSBiZWxvdyBpcyB0aGUgY29tbWVudHMuDQo+IA0KPiAgICBIb3dldmVyLCB0aGUgTW9i
aWxlIE5ldHdvcmsgbWF5IG5vdA0KPiAgICB0cnVzdCB0aGUgaG9zdCAoVUUpIHRvIHNpZ25hbCB0
aGUgY29ycmVjdCBmbG93IGNoYXJhY3RlcmlzdGljcw0KPiAgICBwZXJtaXR0ZWQgYnkgdGhlIFdl
YlJUQyBzZXJ2ZXIuDQo+IA0KPiA9PiBJZiB5b3UgdGFrZSBsb29rIGF0IFRSMjMuNzAxLCAzR1BQ
IHByZWZlcnMgV2ViUlRDIHNpZ25hbGxpbmcgZnVuY3Rpb24gc2VydmluZw0KPiBhIEFGIHRvIGN1
c3RvbWl6ZSB0aGUgcG9saWN5LiBXZWJSVEMgc2lnbmFsbGluZyBmdW5jdGlvbiBlbnRpdHkgaXMg
YXdhcmUgb2YgdGhlDQo+IGZsb3cgY2hhcmFjdGVyaXN0aWNzLCBhZnRlcndhcmRzIHRoZSBlbnRp
dHkgY291bGQgZGlyZWN0IGNvcnJlY3QgbmV0d29yayBhY3Rpb25zLg0KPiBTbywgSSBndWVzcyB0
aGUgc2VudGVuY2Ugb2YgIkhvd2V2ZXIiIHdlIGNvdWxkIHJlbW92ZS4NCg0KSW4gVFIyMy43MDEs
IFdlYlJUQyBzZXJ2aWNlIChBRikgaXMgY28tbG9jYXRlZCBpbiB0aGUgTW9iaWxlIE5ldHdvcmss
IHRoaXMgc2NlbmFyaW8gaXMgYWxzbyBkaXNjdXNzZWQgaW4gaHR0cDovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtcmVkZHktcnRjd2ViLW1vYmlsZS0wMyNzZWN0aW9uLTQuMy4gVGhpcyBkcmFm
dCBpcyBzb2x2aW5nIGEgZGlmZmVyZW50IHByb2JsZW0gb2YgcHJpb3JpdGl6aW5nIHRoZSBtZWRp
YSBzdHJlYW1zIGZvciBPdmVyLXRoZS10b3AgKE9UVCkgc2VydmljZXMuIEZvciBleGFtcGxlIGxl
dCdzIHNheSBXZWJSVEMgc2VydmljZSBpcyBwcm92aWRlZCBieSBhIHNvY2lhbCBuZXR3b3JraW5n
IHNpdGUgdGhhdCBoYXMgdGllLXVwIHdpdGggdGhlIE1vYmlsZSBuZXR3b3JrLiBJbiB0aGlzIGNh
c2UsIE1vYmlsZSBOZXR3b3JrIG5lZWRzIGEgbWVjaGFuaXNtIHRvIGlkZW50aWZ5IHRoZSBtZWRp
YSBzdHJlYW1zIHRyaWdnZWQgYmVjYXVzZSBvZiB1c2luZyB0aGUgc29jaWFsIG5ldHdvcmtpbmcg
c2l0ZSB0byBwcm92aWRlIGRpZmZlcmVudGlhdGVkIHNlcnZpY2UuIA0KDQo+IA0KPiANCj4gICAg
ICAgIEZvciB0aGlyZCBwYXJ0eSBhcHBsaWNhdGlvbnMgZGlmZmVyZW50aWF0ZWQgUW9TDQo+ICAg
ICAgICBzZXJ2aWNlcyBjYW4gYmUgaW5zdGFsbGVkIGV2ZW4gaWYgdGhlIFVFIGlzIGJlaGluZCBO
QVQgcHJvdmlkZWQNCj4gICAgICAgIGJ5IHRoZSBNb2JpbGUgTmV0d29yay4gIEluIGNvbnRyYXN0
LCBvdGhlciBtZWNoYW5pc21zIHN0cnVnZ2xlIHRvDQo+ICAgICAgICBpbnN0YWxsIGRpZmZlcmVu
dGlhdGVkIFFPUyBpZiB0aGUgVUUgaXMgYmVoaW5kIE5BVC4NCj4gDQo+ID0+IFRlIHNjZW5hcmlv
IHlvdSBpbmRpY2F0ZWQgbWF5IHdvcnRoIHRvIGJlIGNsYXJpZmllZC4gWW91IG1heSBpbmRpY2F0
ZSB0aGUNCj4gY2FzZSB3aGVyZSB0aGVyZSB0aGUgYmVhcmVyIGluIFBHVyBpcyBpZGVudGlmaWVk
IGJ5IHByaXZhdGUgNSB0dXBsZSBhbmQgUENSRiBhc2tzDQo+IFBHVyB0byBiaW5kaW5nIGEgU2Vy
dmljZSBEYXRhIEZsb3cgd2l0aCBwdWJsaWMgYWRkcmVzcy4gTG9va2luZyBhdCB0aGUNCj4gYXJj
aGl0ZWN0dXJlIG9mIFRSMjMuNzAxLCBpdCdzIG1heSBub3QgaGFwcGVuZWQgYXQgdGhpcyB0aW1l
LCBiZWNhdXNlIHRoZXJlIGlzIG5vDQo+IE5BVCBiZXR3ZWVuIFBHVyBhbmQgV2ViUlRDIHNpZ25h
bGxpbmcgZnVuY3Rpb24gZW50aXR5KEFGKS4NCg0KWWVzLCBhcyBJIGhhdmUgcHJldmlvdXNseSBl
eHBsYWluZWQgaXQncyBub3QgYSBwcm9ibGVtIHdoZW4gdGhlIEFGIGlzIGNvLWxvY2F0ZWQgaW4g
dGhlIE1vYmlsZSBOZXR3b3JrLiBJdCdzIGEgcHJvYmxlbSB3aGVuIHRoZSBBRiBpcyBhIHRoaXJk
IHBhcnR5IHByb3ZpZGVyIG5vdCBjby1sb2NhdGVkIGluIHRoZSBNb2JpbGUgTmV0d29yayBidXQg
aGFzIHRpZS11cCB3aXRoIHRoZSBNb2JpbGUgb3BlcmF0b3IuDQogDQo+IA0KPiANCj4gICAgYi4g
IE1vYmlsZSBOZXR3b3JrIGNhbiBhdXRob3JpemUgdGhlIGRpZmZlcmVudGlhdGVkIHNlcnZpY2Ug
cmVxdWVzdA0KPiAgICAgICAgZnJvbSB0aGlyZCBwYXJ0eSBhcHBsaWNhdGlvbiBiZWNhdXNlIHRo
ZSBwcm9wb3NlZCBtZWNoYW5pc20gaXMNCj4gICAgICAgIGNvbXBsaWFudCB3aXRoIHRoZSAzR1BQ
J3MgbmV0d29yay10cmlnZ2VyZWQgUW9TIHBvbGljeQ0KPiAgICAgICAgZW5mb3JjZW1lbnQgbW9k
ZWwuDQo+IA0KPiA9PiBBRihmcm9tIHRoaXJkIHBhcnR5KSBhc3NpZ25zIHBhcnRpY3VsYXIgcG9s
aWNpZXMgdG8gUENSRiwgd2hpY2ggdHJhbnNsYXRlDQo+IGFwcGxpY2F0aW9uIHNwZWNpZmljIGxh
bmd1YWdlIHRvIDNHUFAgY29tcGxpYW50LiBJIGd1ZXNzIHRoZXJlIGlzIG5vIG5lZWQgdG8gYXNr
DQo+IDNyZCBwYXJ0eSBhcHAgaW5mb3JtcyBQQ1JGIDNHUFAgc3BlY2lmaWMgbGFuZ3VhZ2UuDQoN
Ck5vLCB0aGUgM3JkIHBhcnR5IGFwcGxpY2F0aW9uIGlzIG5vdCB1c2luZyBQQ1JGIDNHUFAgc3Bl
Y2lmaWMgbGFuZ3VhZ2UuIEF0IGhpZ2gtbGV2ZWwgdGhlIG1lY2hhbmlzbSBzdWdnZXN0ZWQgaW4g
dGhlIGRyYWZ0IGlzIGFzIGZvbGxvd3M6DQpQQ1AgY2xpZW50IG9idGFpbnMgYSBjcnlwdG9ncmFw
aGljIHRva2VuIG9idGFpbmVkIGZyb20gdGhlIHRoaXJkIHBhcnR5IFdlYlJUQyBzaWduYWxpbmcg
ZnVuY3Rpb24gZW50aXR5IChBRikgYW5kIGluY2x1ZGVzIHRoZSB0b2tlbiBpbiB0aGUgUENQIHJl
cXVlc3Qgd2l0aCB0aGUgZmxvdyBjaGFyYWN0ZXJpc3RpY3Mgc2lnbmFsZWQgaW4gUENQIEZMT1dE
QVRBLiBQQ1Agc2VydmVyIGluIHRoZSBNb2JpbGUgbmV0d29yayB2YWxpZGF0ZXMgdGhlIHRva2Vu
IGFuZCBncmFudHMgdGhlIHJlcXVlc3QuIEl0J3MgYmFzZWQgb24gaHR0cDovL3Rvb2xzLmlldGYu
b3JnL2h0bWwvZHJhZnQtd2luZy1wY3AtdGhpcmQtcGFydHktYXV0aHotMDMuIA0KDQo+IA0KPiAN
Cj4gICAgMS4gIEl0IGlzIG91dCBvZiBzY29wZSBvZiB0aGlzIGRvY3VtZW50IHRvIGRpc2N1c3Mg
dGhlIHRyYWRlLW9mZnMNCj4gICAgICAgIGJldHdlZW4gdGhlIHByb3Bvc2VkIGFwcHJvYWNoIHZz
LiBkZXBsb3lpbmcgbG9jYWwgV2ViUlRDLUlNUw0KPiAgICAgICAgR2F0ZXdheXMgd2l0aGluIHRo
ZSBNb2JpbGUgTmV0d29yay4NCj4gDQo+ID0+IEl0J3MgYW4gaW1wb3J0YW50IGluZm9ybWF0aW9u
LiBNYXkgSSBzdWdnZXN0IGVsYWJvcmF0ZSB0aGlzIGluZm9ybWF0aW9uIGluIHRoZQ0KPiBtYWlu
IGJvZHkuIEl0IGFsc28gd291bGQgYmUgZ29vZCB0byBzYXkgd2hhdCB0aGUgcmVsYXRpb24gb2Yg
bG9jYWwgV2ViUlRDLUlNUw0KPiBzb2x1dGlvbiB0byB0aGUgcHJvcG9zZWQgc29sdXRpb24uDQoN
ClRoZSBwcm9wb3NlZCBzb2x1dGlvbiBpbiB0aGUgZHJhZnQgaXMgbm90IHRhcmdldGluZyBXZWJS
VEMtSU1TIHNvbHV0aW9uLg0KDQo+IA0KPiANCj4gICAgICAgIFBDUCBzdWNjZXNzIHJlc3BvbnNl
IHdvdWxkIGJlIHNlbnQgd2l0aG91dCB3YWl0aW5nDQo+ICAgICAgICBmb3IgbmV0d29yay1pbml0
aWF0ZWQgYmVhcmVyIGFjdGl2YXRpb24gb3IgbW9kaWZpY2F0aW9uIHRvIGJlDQo+ICAgICAgICBj
b21wbGV0ZTogaS5lLiwgUENQIHN1Y2Nlc3MgcmVzcG9uc2Ugd291bGQgYmUgc2VudCBiYXNlZCBv
biB0aGUNCj4gICAgICAgIHJlc291cmNlIGF2YWlsYWJpbGl0eSB0byBzZXR1cCBvciBtb2RpZnkg
YmVhcmVycy4NCj4gDQo+IHdoeSBub3Qgd2FpdGluZyBmb3IgdGhlIGNvbXBsZXRpb24gb2YgRVBD
IGJlYXJlciBhbGxvY2F0aW9uID8NCg0KVGhlIGlkZWEgaXMgdG8gcXVpY2tseSByZXNwb25kIHRv
IHRoZSBQQ1AgcmVxdWVzdCwgb3RoZXJ3aXNlIHRoZSBjbGllbnQgaGF2ZSB0byB3YWl0IGZvciB0
aGUgcmVzcG9uc2UuICBUaGUgc3VjY2VzcyByZXNwb25zZSBpcyBzZW50IG9ubHkgaWYgdGhlcmUg
YXJlIHN1ZmZpY2llbnQgcmVzb3VyY2VzIGF2YWlsYWJsZSB0byBzZXR1cCBiZWFyZXJzLg0KDQo+
IA0KPiAgICAzLiAgVGhlIFBETi1HVyB3aWxsIGNvbW11bmljYXRlIHdpdGggdGhlIFBDUkYgdG8g
dHJpZ2dlciB0aGUNCj4gICAgICAgIGFwcHJvcHJpYXRlIFBvbGljeSBjaGFyZ2luZyBhbmQgY29u
dHJvbCAoUENDKSBkZWNpc2lvbiBiYXNlZCBvbg0KPiAgICAgICAgd2hpY2ggUEROLUdXIHdpbGwg
aW5pdGlhdGUgYmVhcmVyIGFjdGl2YXRpb24gb3IgbW9kaWZpY2F0aW9uDQo+ICAgICAgICBwcm9j
ZWR1cmUuDQo+IA0KPiBJIGNhbid0IHVuZGVyc3RhbmQgdGhlIGludGVudGlvbiBvZiBQQ1JGIHNl
bGVjdGluZyBkaWZmZXJlbnQgUEdXcy4gVGhlIHByb2Nlc3MNCj4gdGhlIGRyYWZ0IGRlc2NyaWJl
ZCBpcyBtb3JlIGxpa2UgQURDIHByb2NlZHVyZS4gVGhlIFBHVyBtb25pdG9yIHRoZSBwYXJ0aWN1
bGFyDQo+IGV2ZW50IChpLmUuIFBDUCByZXF1ZXN0IGluIHRoaXMgZHJhZnQpIGFuZCBpbmZvcm0g
UENSRiwgYWZ0ZXIgdGhlbiBQQ1JGIG9ubHkgbmVlZHMNCj4gdG8gcGVybWl0IHRoZSByZXNvdXJj
ZSB1c2FnZSBvbiB0aGUgaW5pdGlhdGVkIFBHVy4NCg0KUENSRiBpcyBub3Qgc2VsZWN0aW5nIGRp
ZmZlcmVudCBQR1dzLiBJdCdzIGp1c3QgZm9sbG93aW5nIHRoZSBwcm9jZWR1cmUgZ2l2ZW4gaW4g
M0dQUCBUUyAyMy40MDEgc2VjdGlvbiAiUEROIEdXIGluaXRpYXRlZCBiZWFyZXIgbW9kaWZpY2F0
aW9uIHdpdGggYmVhcmVyIFFvUyB1cGRhdGUiLg0KDQpDaGVlcnMsDQotVGlydQ0KDQo+IA0KPiAN
Cj4gQlJzDQo+IA0KPiBHYW5nDQo=


From nobody Mon May  5 11:00:01 2014
Return-Path: <markus.stenberg@iki.fi>
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 E2D7F1A0443 for <pcp@ietfa.amsl.com>; Mon,  5 May 2014 10:59:57 -0700 (PDT)
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, 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 CO5sVognwsO3 for <pcp@ietfa.amsl.com>; Mon,  5 May 2014 10:59:55 -0700 (PDT)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.199]) by ietfa.amsl.com (Postfix) with ESMTP id 576301A0444 for <pcp@ietf.org>; Mon,  5 May 2014 10:59:55 -0700 (PDT)
Received: from [192.168.43.129] (80.220.67.193) by jenni2.inet.fi (8.5.140.03) (authenticated as stenma-47) id 534D2ABA01818E63; Mon, 5 May 2014 20:59:51 +0300
From: Markus Stenberg <markus.stenberg@iki.fi>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Mon, 5 May 2014 19:59:32 +0200
Message-Id: <FDB45976-B7A3-4C59-B2D1-C01982D0205F@iki.fi>
To: pcp@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/NB-vNM2YSgvPM0uSeG_VzZK5eIQ
Subject: [pcp] How can I make a ~stateless forwarding PCP proxy again?
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: Mon, 05 May 2014 17:59:58 -0000

Let=92s assume I have client, proxy, and server. Proxy isn=92t even =
firewall, nor is it NAT.=20

[1] Client sends to proxy (first-hop router).  Proxy replaces internal =
IP with it=92s own, adds THIRD_PARTY, and forwards to real server it =
decides based on magic.

[2] Server sends back response to proxy.

[3] Proxy has no per-client state, and drops packet as it can=92t find =
client=92s address from anywhere.

Motivation:

For homenet use cases, for inner routers within home, you _won=92t_ want =
actually firewall or NAT to be involved, but you _do_ need a proxy to =
make decisions about which CER to talk to with different source =
addresses as it=92s not really addressed by current solutions and =
routers know more about network topology changes than the client will in =
any case.

For example, IPv4 uplink may change somewhere =91in the network=92, and =
current PCP client implementations I play with wouldn=92t even know =
about how to learn of it, not to even mention react to it. This is =
reality in my NAT-=91enabled=92 home, as at a time I have only one =
upstream NAT active, but it may change, based on active-standby model =
(and yes, it could be on different routers).

As another example, IPv6 traffic within a home network is routed based =
on source prefix, but I have yet to see PCP client implementation that =
does server selection based on this (is it even specified?).  Yet making =
firewall holes would be still nice.

As I _do_ control both (mostly fictional) proxy implementation as well =
as the (mostly functional) server implementation, my current plan is to =
add option which just contains client=92s address at proxy, and strip it =
on way back from proxy to client. Is there a better solution?

Cheers,

-Markus

P.S. I=92ll accept that it=92s host=92s responsibility always if and =
only if every device (mostly with fruity logo on them) on my home that =
talks PCP actually deals with this stuff somehow magically. I=92m not =
holding my breath, though.


From nobody Mon May  5 12:41:32 2014
Return-Path: <repenno@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 9C2881A019A for <pcp@ietfa.amsl.com>; Mon,  5 May 2014 12:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 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.651, 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 rg6EaI5_zYQ1 for <pcp@ietfa.amsl.com>; Mon,  5 May 2014 12:41:27 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 94A481A01AF for <pcp@ietf.org>; Mon,  5 May 2014 12:41:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2863; q=dns/txt; s=iport; t=1399318884; x=1400528484; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=IBpEGokNUaOpmpp8+dgmJgrzH1FcC/rg5HggbGBJQIk=; b=hnxkxpo7PZvW+gWFLVZDCF/ail5BIBWs10S9Sy4ES+JXrD8Z6MvEYJ50 Gh1PdFuSa2hB+PdKeT1ffAcdIZEX4vDtv/8TIGhuoejjQtJOpcfgHP7xv sZQTlIuwaIEanLaHVDjdPhOOZiEGbH1V/kUS80J4VTD46QRAg984lUE7H k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwFAOroZ1OtJV2c/2dsb2JhbABZgwZPWL0LhzuBGhZ0giUBAQEEAQEBaxsCAQgRBAEBCyQnCx0IAgQBEggTiCYNzTETBI4hOIMqgRUErCiDNIIv
X-IronPort-AV: E=Sophos;i="4.97,990,1389744000"; d="scan'208";a="322611108"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-4.cisco.com with ESMTP; 05 May 2014 19:41:23 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s45JfN0R017719 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 5 May 2014 19:41:23 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.212]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0123.003; Mon, 5 May 2014 14:41:23 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Markus Stenberg <markus.stenberg@iki.fi>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] How can I make a ~stateless forwarding PCP proxy again?
Thread-Index: AQHPaIvbEzCvnrZ5eUCbgJ908UuMc5syYlxh
Date: Mon, 5 May 2014 19:41:22 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F06040B8C957D@xmb-rcd-x04.cisco.com>
References: <FDB45976-B7A3-4C59-B2D1-C01982D0205F@iki.fi>
In-Reply-To: <FDB45976-B7A3-4C59-B2D1-C01982D0205F@iki.fi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.127.192]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/OJbU0xJe6LMe0FoBWuCE8UPdHXo
Subject: Re: [pcp] How can I make a ~stateless forwarding PCP proxy again?
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: Mon, 05 May 2014 19:41:30 -0000

Hi Markus,=0A=
=0A=
we had this discussion in the past but and I, for one, backed the idea of P=
CP being able to support stateless proxies.  So, you are not alone there bu=
t maybe you want to write a draft about it so the WG can discuss it.=0A=
=0A=
thanks,=0A=
=0A=
Reinaldo=0A=
=0A=
________________________________________=0A=
From: pcp [pcp-bounces@ietf.org] on behalf of Markus Stenberg [markus.stenb=
erg@iki.fi]=0A=
Sent: Monday, May 05, 2014 10:59 AM=0A=
To: pcp@ietf.org=0A=
Subject: [pcp] How can I make a ~stateless forwarding PCP proxy again?=0A=
=0A=
Let=92s assume I have client, proxy, and server. Proxy isn=92t even firewal=
l, nor is it NAT.=0A=
=0A=
[1] Client sends to proxy (first-hop router).  Proxy replaces internal IP w=
ith it=92s own, adds THIRD_PARTY, and forwards to real server it decides ba=
sed on magic.=0A=
=0A=
[2] Server sends back response to proxy.=0A=
=0A=
[3] Proxy has no per-client state, and drops packet as it can=92t find clie=
nt=92s address from anywhere.=0A=
=0A=
Motivation:=0A=
=0A=
For homenet use cases, for inner routers within home, you _won=92t_ want ac=
tually firewall or NAT to be involved, but you _do_ need a proxy to make de=
cisions about which CER to talk to with different source addresses as it=92=
s not really addressed by current solutions and routers know more about net=
work topology changes than the client will in any case.=0A=
=0A=
For example, IPv4 uplink may change somewhere =91in the network=92, and cur=
rent PCP client implementations I play with wouldn=92t even know about how =
to learn of it, not to even mention react to it. This is reality in my NAT-=
=91enabled=92 home, as at a time I have only one upstream NAT active, but i=
t may change, based on active-standby model (and yes, it could be on differ=
ent routers).=0A=
=0A=
As another example, IPv6 traffic within a home network is routed based on s=
ource prefix, but I have yet to see PCP client implementation that does ser=
ver selection based on this (is it even specified?).  Yet making firewall h=
oles would be still nice.=0A=
=0A=
As I _do_ control both (mostly fictional) proxy implementation as well as t=
he (mostly functional) server implementation, my current plan is to add opt=
ion which just contains client=92s address at proxy, and strip it on way ba=
ck from proxy to client. Is there a better solution?=0A=
=0A=
Cheers,=0A=
=0A=
-Markus=0A=
=0A=
P.S. I=92ll accept that it=92s host=92s responsibility always if and only i=
f every device (mostly with fruity logo on them) on my home that talks PCP =
actually deals with this stuff somehow magically. I=92m not holding my brea=
th, though.=0A=
=0A=
_______________________________________________=0A=
pcp mailing list=0A=
pcp@ietf.org=0A=
https://www.ietf.org/mailman/listinfo/pcp=0A=


From nobody Mon May  5 13:15:19 2014
Return-Path: <markus.stenberg@iki.fi>
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 EBCFB1A0195 for <pcp@ietfa.amsl.com>; Mon,  5 May 2014 13:15:17 -0700 (PDT)
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, 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 AN3CavI_dZiL for <pcp@ietfa.amsl.com>; Mon,  5 May 2014 13:15:15 -0700 (PDT)
Received: from jenni1.inet.fi (mta-out1.inet.fi [62.71.2.198]) by ietfa.amsl.com (Postfix) with ESMTP id 40A6D1A0156 for <pcp@ietf.org>; Mon,  5 May 2014 13:15:14 -0700 (PDT)
Received: from [192.168.43.129] (80.220.67.193) by jenni1.inet.fi (8.5.140.03) (authenticated as stenma-47) id 534D293001840916; Mon, 5 May 2014 23:15:02 +0300
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F06040B8C957D@xmb-rcd-x04.cisco.com>
Date: Mon, 5 May 2014 22:14:57 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2B975F36-4E46-4D93-891B-DB4E480FF190@iki.fi>
References: <FDB45976-B7A3-4C59-B2D1-C01982D0205F@iki.fi> <45A697A8FFD7CF48BCF2BE7E106F06040B8C957D@xmb-rcd-x04.cisco.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/pjsDpRDNDCDSgwjOu33518ddb9E
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] How can I make a ~stateless forwarding PCP proxy again?
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: Mon, 05 May 2014 20:15:18 -0000

On 5.5.2014, at 21.41, Reinaldo Penno (repenno) <repenno@cisco.com> =
wrote:
> we had this discussion in the past but and I, for one, backed the idea =
of PCP being able to support stateless proxies.  So, you are not alone =
there but maybe you want to write a draft about it so the WG can discuss =
it.


Nods. Personally I like to minimize the amount of state in a system, so =
I=92m a fan of stateless designs. My current design for a proxy has just =
3 logical pieces of =91state=92 per supported remote server:

- (client) source prefix + prefix length to match
- address of the server
- server epoch + when was it received

And currently I=92m trying to make sure it=92s actually doable to do all =
I want with just that and few hundred lines of C. After looking at how =
big PCP client libraries are, last thing I want is really PCP client =
glued to PCP server.

Getting back to my previous question, now that I think of it, actually, =
the IP address of the client is in the THIRD_PARTY option. Only thing =
that isn=92t explicitly stored somewhere is the address client contacts =
the proxy on (it probably has 1-N addresses per M interfaces). If proxy =
uses same source address for talking with server as client used to =
contact it (with different port, obviously), it should work fine, =
without per-client or per-request state.=20

e.g.

C -> P [IntIP=3DC]
P -> S [IntIP=3DP, TP=3DC]
S -> P [TP=3DC]
P -> C [no TP]

Beyond that, some ANNOUNCE handling is needed, but as long as you stick =
to multicast, that can be also stateless. (Connected clients know if =
they have state with the particular proxy that spams ANNOUNCEs.)

Perhaps I=92ll write up about it somewhere (pcp or homenet), although =
it=92s more of an implementation detail draft, than actual protocol =
change requiring one.

Cheers,

-Markus

P.S. This scheme works fine with IPv4. With IPv6, it may have issues, =
when C contacts P using link-local address and I don=92t think there is =
anything preventing that. P is probably unable to contact S using that. =
Oh well. I guess doing other IPv6 scopes would work, and falling back to =
IPv4 if client doesn=92t do DHCP*/RA/something else option to learn the =
IPv6 GUA/ULA of the proxy on first hop.



From nobody Mon May  5 14:38:11 2014
Return-Path: <repenno@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 B56A81A0547 for <pcp@ietfa.amsl.com>; Mon,  5 May 2014 14:38:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.152
X-Spam-Level: 
X-Spam-Status: No, score=-10.152 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.651, 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 aaE8M_mk3NXV for <pcp@ietfa.amsl.com>; Mon,  5 May 2014 14:38:08 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id 8AED21A0522 for <pcp@ietf.org>; Mon,  5 May 2014 14:38:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3208; q=dns/txt; s=iport; t=1399325885; x=1400535485; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=i/UELGpC8VQzyM/Vno9RwUjlYNo0jE2fgPlOATNSaOM=; b=Cfe4x1I64EFNfigJPT0id1uRfTMgCeQsWsWQCJW+UJqVgBqFqS9VylT7 6U7cFYtGVt9kk6aFFl51CXyQOkOqwKcABYLK14EA5/CrlZrjrFdQ8ERpK aZfT/qIlVyzz5FtgWcUAovxgg7AnapTMO8hBAnRDGpaOUy91fLeI8IWC+ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjoFAJcDaFOtJV2b/2dsb2JhbABZgwaBJ8RGgRwWdIIlAQEBBCdSEAIBCBEEAQEBCiQyHQgCBA4FCIg5zVUXjiExBwaDJIEVAQOsKIM0gi8
X-IronPort-AV: E=Sophos;i="4.97,991,1389744000"; d="scan'208";a="41207522"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-3.cisco.com with ESMTP; 05 May 2014 21:38:04 +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 s45Lc4nV020075 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 5 May 2014 21:38:04 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.212]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0123.003; Mon, 5 May 2014 16:38:04 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Markus Stenberg <markus.stenberg@iki.fi>
Thread-Topic: [pcp] How can I make a ~stateless forwarding PCP proxy again?
Thread-Index: AQHPaIvbEzCvnrZ5eUCbgJ908UuMc5syYlxhgABdvID//8MLKA==
Date: Mon, 5 May 2014 21:38:04 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F06040B8C95CC@xmb-rcd-x04.cisco.com>
References: <FDB45976-B7A3-4C59-B2D1-C01982D0205F@iki.fi> <45A697A8FFD7CF48BCF2BE7E106F06040B8C957D@xmb-rcd-x04.cisco.com>, <2B975F36-4E46-4D93-891B-DB4E480FF190@iki.fi>
In-Reply-To: <2B975F36-4E46-4D93-891B-DB4E480FF190@iki.fi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.121.139]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/QrU7G2TXJetOIbGg6gdABTnaUsk
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] How can I make a ~stateless forwarding PCP proxy again?
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: Mon, 05 May 2014 21:38:09 -0000

"Getting back to my previous question, now that I think of it, actually, th=
e IP address of the client is in the THIRD_PARTY option. Only thing that is=
n=92t explicitly stored somewhere is the address client contacts the proxy =
on (it probably has 1-N addresses per M interfaces)."=0A=
=0A=
Yes, but I believe in the current back-to-back proxy proposal (newest draft=
) the third party option would/should be completely removed by the proxy be=
fore forwarding a message.=0A=
 =0A=
________________________________________=0A=
From: Markus Stenberg [markus.stenberg@iki.fi]=0A=
Sent: Monday, May 05, 2014 1:14 PM=0A=
To: Reinaldo Penno (repenno)=0A=
Cc: Markus Stenberg; pcp@ietf.org=0A=
Subject: Re: [pcp] How can I make a ~stateless forwarding PCP proxy again?=
=0A=
=0A=
On 5.5.2014, at 21.41, Reinaldo Penno (repenno) <repenno@cisco.com> wrote:=
=0A=
> we had this discussion in the past but and I, for one, backed the idea of=
 PCP being able to support stateless proxies.  So, you are not alone there =
but maybe you want to write a draft about it so the WG can discuss it.=0A=
=0A=
=0A=
Nods. Personally I like to minimize the amount of state in a system, so I=
=92m a fan of stateless designs. My current design for a proxy has just 3 l=
ogical pieces of =91state=92 per supported remote server:=0A=
=0A=
- (client) source prefix + prefix length to match=0A=
- address of the server=0A=
- server epoch + when was it received=0A=
=0A=
And currently I=92m trying to make sure it=92s actually doable to do all I =
want with just that and few hundred lines of C. After looking at how big PC=
P client libraries are, last thing I want is really PCP client glued to PCP=
 server.=0A=
=0A=
Getting back to my previous question, now that I think of it, actually, the=
 IP address of the client is in the THIRD_PARTY option. Only thing that isn=
=92t explicitly stored somewhere is the address client contacts the proxy o=
n (it probably has 1-N addresses per M interfaces). If proxy uses same sour=
ce address for talking with server as client used to contact it (with diffe=
rent port, obviously), it should work fine, without per-client or per-reque=
st state.=0A=
=0A=
e.g.=0A=
=0A=
C -> P [IntIP=3DC]=0A=
P -> S [IntIP=3DP, TP=3DC]=0A=
S -> P [TP=3DC]=0A=
P -> C [no TP]=0A=
=0A=
Beyond that, some ANNOUNCE handling is needed, but as long as you stick to =
multicast, that can be also stateless. (Connected clients know if they have=
 state with the particular proxy that spams ANNOUNCEs.)=0A=
=0A=
Perhaps I=92ll write up about it somewhere (pcp or homenet), although it=92=
s more of an implementation detail draft, than actual protocol change requi=
ring one.=0A=
=0A=
Cheers,=0A=
=0A=
-Markus=0A=
=0A=
P.S. This scheme works fine with IPv4. With IPv6, it may have issues, when =
C contacts P using link-local address and I don=92t think there is anything=
 preventing that. P is probably unable to contact S using that. Oh well. I =
guess doing other IPv6 scopes would work, and falling back to IPv4 if clien=
t doesn=92t do DHCP*/RA/something else option to learn the IPv6 GUA/ULA of =
the proxy on first hop.=0A=
=0A=
=0A=


From nobody Mon May  5 15:03:47 2014
Return-Path: <markus.stenberg@iki.fi>
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 40A2A1A03D5 for <pcp@ietfa.amsl.com>; Mon,  5 May 2014 15:03:46 -0700 (PDT)
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, 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 Te74kmP1D5zk for <pcp@ietfa.amsl.com>; Mon,  5 May 2014 15:03:44 -0700 (PDT)
Received: from jenni1.inet.fi (mta-out1.inet.fi [62.71.2.198]) by ietfa.amsl.com (Postfix) with ESMTP id E35EB1A037A for <pcp@ietf.org>; Mon,  5 May 2014 15:03:43 -0700 (PDT)
Received: from [192.168.43.129] (80.220.67.193) by jenni1.inet.fi (8.5.140.03) (authenticated as stenma-47) id 534D29300184F881; Tue, 6 May 2014 01:03:33 +0300
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F06040B8C95CC@xmb-rcd-x04.cisco.com>
Date: Tue, 6 May 2014 00:03:26 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD197DE0-9FDF-4489-B80F-659DE6585F3C@iki.fi>
References: <FDB45976-B7A3-4C59-B2D1-C01982D0205F@iki.fi> <45A697A8FFD7CF48BCF2BE7E106F06040B8C957D@xmb-rcd-x04.cisco.com>, <2B975F36-4E46-4D93-891B-DB4E480FF190@iki.fi> <45A697A8FFD7CF48BCF2BE7E106F06040B8C95CC@xmb-rcd-x04.cisco.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/gRFKTm3DFbCl72YOpX0z7c_7-Ho
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] How can I make a ~stateless forwarding PCP proxy again?
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: Mon, 05 May 2014 22:03:46 -0000

On 5.5.2014, at 23.38, Reinaldo Penno (repenno) <repenno@cisco.com> =
wrote:
> "Getting back to my previous question, now that I think of it, =
actually, the IP address of the client is in the THIRD_PARTY option. =
Only thing that isn=92t explicitly stored somewhere is the address =
client contacts the proxy on (it probably has 1-N addresses per M =
interfaces)."
>=20
> Yes, but I believe in the current back-to-back proxy proposal (newest =
draft) the third party option would/should be completely removed by the =
proxy before forwarding a message.


Well, it actually behaves the same way what I said - it _does_ (in =
firewall case) insert THIRD_PARTY options on way to server and back. =
Only difference is that in my case, I don=92t even want to think of =
being a NAT that proxies requests onward (I=92m sure you need lots of =
state at that point and the content of the current draft seems focused =
mostly on that).

I wonder if someone=92s implemented the back-to-back draft yet? It looks =
like a lot of work. The minimal state design I sketched is about 500 LoC =
of C[1] (with quite short line lengths too, debug messages, etc that I =
wrote today). Perhaps it would be a bit more if I actually bother to =
send ANNOUNCEs some day, but not much.

And that=92s all you really need, given

a) you don=92t want to cascade that proxy (you can=92t have multiple =
THIRD_PARTY options)

b) you can live with =91someone else=92 having the control of server =
selection and PCP-forwarder being just dumb element following orders.

Perhaps I=92ll write a draft on my thoughts on homenet + PCP angle for =
the next IETF (sigh, too full calendar, but one day of hacking this was =
amusing enough).

Cheers,

-Markus

[1] https://github.com/fingon/minimalist-pcproxy=


From nobody Mon May  5 23:02:07 2014
Return-Path: <dwing@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 C3A531A073F for <pcp@ietfa.amsl.com>; Mon,  5 May 2014 23:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 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.651, 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 9OCEG7fjMt7X for <pcp@ietfa.amsl.com>; Mon,  5 May 2014 23:02:03 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 40B3B1A073E for <pcp@ietf.org>; Mon,  5 May 2014 23:02:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3260; q=dns/txt; s=iport; t=1399356120; x=1400565720; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=7tuyLIqNIG9YQ2gAnfZT/QiCJFdnQCF/40KBsiQ5HFc=; b=j6gMMuQjhQLqNvbtg2etv19bO3kafm3MzgXXafFSOz6VFCmAShElgNsH noMQA9+g8BwhuPu6fDCHNVPgrFNnwK3UaB1+mWiq8Is2e+Zmc2GmkWZuM KsTbLdHP7VQdKe4B7M78Pu6UOO/q+l3KtZE8pRI7ZerQH/wSYCIVxg9BL U=;
X-IronPort-AV: E=Sophos;i="4.97,994,1389744000"; d="scan'208";a="109452375"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 06 May 2014 06:01:59 +0000
Received: from [10.21.102.179] ([10.21.102.179]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s4661VT1021109; Tue, 6 May 2014 06:01:32 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <2B975F36-4E46-4D93-891B-DB4E480FF190@iki.fi>
Date: Mon, 5 May 2014 23:01:31 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <320291FF-E45B-40E6-9D54-617419713506@cisco.com>
References: <FDB45976-B7A3-4C59-B2D1-C01982D0205F@iki.fi> <45A697A8FFD7CF48BCF2BE7E106F06040B8C957D@xmb-rcd-x04.cisco.com> <2B975F36-4E46-4D93-891B-DB4E480FF190@iki.fi>
To: Markus Stenberg <markus.stenberg@iki.fi>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/Kg9Cd8WgdyA-oXRqoinFMVwc9h4
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] How can I make a ~stateless forwarding PCP proxy again?
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, 06 May 2014 06:02:04 -0000

On May 5, 2014, at 1:14 PM, Markus Stenberg <markus.stenberg@iki.fi> =
wrote:

> On 5.5.2014, at 21.41, Reinaldo Penno (repenno) <repenno@cisco.com> =
wrote:
>> we had this discussion in the past but and I, for one, backed the =
idea of PCP being able to support stateless proxies.  So, you are not =
alone there but maybe you want to write a draft about it so the WG can =
discuss it.
>=20
>=20
> Nods. Personally I like to minimize the amount of state in a system, =
so I=92m a fan of stateless designs. My current design for a proxy has =
just 3 logical pieces of =91state=92 per supported remote server:
>=20
> - (client) source prefix + prefix length to match
> - address of the server
> - server epoch + when was it received
>=20
> And currently I=92m trying to make sure it=92s actually doable to do =
all I want with just that and few hundred lines of C. After looking at =
how big PCP client libraries are, last thing I want is really PCP client =
glued to PCP server.
>=20
> Getting back to my previous question, now that I think of it, =
actually, the IP address of the client is in the THIRD_PARTY option. =
Only thing that isn=92t explicitly stored somewhere is the address =
client contacts the proxy on (it probably has 1-N addresses per M =
interfaces). If proxy uses same source address for talking with server =
as client used to contact it (with different port, obviously), it should =
work fine, without per-client or per-request state.=20
>=20
> e.g.
>=20
> C -> P [IntIP=3DC]
> P -> S [IntIP=3DP, TP=3DC]
> S -> P [TP=3DC]
> P -> C [no TP]
>=20
> Beyond that, some ANNOUNCE handling is needed, but as long as you =
stick to multicast, that can be also stateless. (Connected clients know =
if they have state with the particular proxy that spams ANNOUNCEs.)
>=20
> Perhaps I=92ll write up about it somewhere (pcp or homenet), although =
it=92s more of an implementation detail draft, than actual protocol =
change requiring one.
>=20
> Cheers,
>=20
> -Markus
>=20
> P.S. This scheme works fine with IPv4. With IPv6, it may have issues, =
when C contacts P using link-local address and I don=92t think there is =
anything preventing that.

Correct, nothing prevents it.  But C is unable to show it owns another =
address (so can't use THIRD_PARTY), and link-local doesn't do anything =
on the other side of the router (firewall), so seems fruitless for C's =
PCP client to use link local.  I would even think P or any PCP server =
should just return an error if the PCP request came from an IPv6 link =
local address and the proxy (or PCP server) is not doing NPTv6 or NAT66. =
 Link local can't go anywhere, so seems an error no matter if proxy or =
PCP server returns an error -- link-local won't do any good as a =
firewall rule because it isn't routable from the Internet.

-d


> P is probably unable to contact S using that. Oh well. I guess doing =
other IPv6 scopes would work, and falling back to IPv4 if client doesn=92t=
 do DHCP*/RA/something else option to learn the IPv6 GUA/ULA of the =
proxy on first hop.
>=20
>=20
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From nobody Tue May  6 02:48:22 2014
Return-Path: <mohamed.boucadair@orange.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 2C4CB1A028C for <pcp@ietfa.amsl.com>; Tue,  6 May 2014 02:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.549
X-Spam-Level: 
X-Spam-Status: No, score=-1.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
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 SXss22vo069a for <pcp@ietfa.amsl.com>; Tue,  6 May 2014 02:48:19 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by ietfa.amsl.com (Postfix) with ESMTP id C5F101A0173 for <pcp@ietf.org>; Tue,  6 May 2014 02:48:18 -0700 (PDT)
Received: from omfeda05.si.francetelecom.fr (unknown [xx.xx.xx.198]) by omfeda13.si.francetelecom.fr (ESMTP service) with ESMTP id 816A41901EB; Tue,  6 May 2014 11:48:14 +0200 (CEST)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfeda05.si.francetelecom.fr (ESMTP service) with ESMTP id 31DCB18006E; Tue,  6 May 2014 11:48:14 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.13]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Tue, 6 May 2014 11:48:14 +0200
From: <mohamed.boucadair@orange.com>
To: Markus Stenberg <markus.stenberg@iki.fi>, "Reinaldo Penno (repenno)" <repenno@cisco.com>
Date: Tue, 6 May 2014 11:48:08 +0200
Thread-Topic: [pcp] How can I make a ~stateless forwarding PCP proxy again?
Thread-Index: Ac9onrxoLkBQKfPtSjiPpU5yew2H6QAcP7eg
Message-ID: <94C682931C08B048B7A8645303FDC9F36F5B63D4ED@PUEXCB1B.nanterre.francetelecom.fr>
References: <FDB45976-B7A3-4C59-B2D1-C01982D0205F@iki.fi> <45A697A8FFD7CF48BCF2BE7E106F06040B8C957D@xmb-rcd-x04.cisco.com> <2B975F36-4E46-4D93-891B-DB4E480FF190@iki.fi>
In-Reply-To: <2B975F36-4E46-4D93-891B-DB4E480FF190@iki.fi>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.5.5.221820
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/tr8XI__GealaCOkqqhUhVqLxIbk
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] How can I make a ~stateless forwarding PCP proxy again?
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, 06 May 2014 09:48:20 -0000

Hi Markus,

It seems that your design is close to what is documented in http://tools.ie=
tf.org/html/draft-ietf-pcp-proxy-04#section-8, no?

FWIW, the heaviness of the b2b model was raised in slide 6 of http://tools.=
ietf.org/agenda/89/slides/slides-89-pcp-4.pdf but I don't know what was the=
 outcome of that discussion.

Cheers,
Med

>-----Message d'origine-----
>De=A0: pcp [mailto:pcp-bounces@ietf.org] De la part de Markus Stenberg
>Envoy=E9=A0: lundi 5 mai 2014 22:15
>=C0=A0: Reinaldo Penno (repenno)
>Cc=A0: pcp@ietf.org
>Objet=A0: Re: [pcp] How can I make a ~stateless forwarding PCP proxy again=
?
>
>On 5.5.2014, at 21.41, Reinaldo Penno (repenno) <repenno@cisco.com> wrote:
>> we had this discussion in the past but and I, for one, backed the idea o=
f
>PCP being able to support stateless proxies.  So, you are not alone there
>but maybe you want to write a draft about it so the WG can discuss it.
>
>
>Nods. Personally I like to minimize the amount of state in a system, so I'=
m
>a fan of stateless designs. My current design for a proxy has just 3
>logical pieces of 'state' per supported remote server:
>
>- (client) source prefix + prefix length to match
>- address of the server
>- server epoch + when was it received
>
>And currently I'm trying to make sure it's actually doable to do all I wan=
t
>with just that and few hundred lines of C. After looking at how big PCP
>client libraries are, last thing I want is really PCP client glued to PCP
>server.
>
>Getting back to my previous question, now that I think of it, actually, th=
e
>IP address of the client is in the THIRD_PARTY option. Only thing that
>isn't explicitly stored somewhere is the address client contacts the proxy
>on (it probably has 1-N addresses per M interfaces). If proxy uses same
>source address for talking with server as client used to contact it (with
>different port, obviously), it should work fine, without per-client or per=
-
>request state.
>
>e.g.
>
>C -> P [IntIP=3DC]
>P -> S [IntIP=3DP, TP=3DC]
>S -> P [TP=3DC]
>P -> C [no TP]
>
>Beyond that, some ANNOUNCE handling is needed, but as long as you stick to
>multicast, that can be also stateless. (Connected clients know if they hav=
e
>state with the particular proxy that spams ANNOUNCEs.)
>
>Perhaps I'll write up about it somewhere (pcp or homenet), although it's
>more of an implementation detail draft, than actual protocol change
>requiring one.
>
>Cheers,
>
>-Markus
>
>P.S. This scheme works fine with IPv4. With IPv6, it may have issues, when
>C contacts P using link-local address and I don't think there is anything
>preventing that. P is probably unable to contact S using that. Oh well. I
>guess doing other IPv6 scopes would work, and falling back to IPv4 if
>client doesn't do DHCP*/RA/something else option to learn the IPv6 GUA/ULA
>of the proxy on first hop.
>
>
>_______________________________________________
>pcp mailing list
>pcp@ietf.org
>https://www.ietf.org/mailman/listinfo/pcp


From nobody Tue May  6 06:54:30 2014
Return-Path: <hassnaa.moustafa@intel.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 759ED1A065C for <pcp@ietfa.amsl.com>; Tue,  6 May 2014 06:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.552
X-Spam-Level: 
X-Spam-Status: No, score=-7.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, 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 74csvtd75diY for <pcp@ietfa.amsl.com>; Tue,  6 May 2014 06:54:28 -0700 (PDT)
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by ietfa.amsl.com (Postfix) with ESMTP id ED2FC1A04A2 for <pcp@ietf.org>; Tue,  6 May 2014 06:54:27 -0700 (PDT)
Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 06 May 2014 06:54:23 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.97,997,1389772800"; d="scan'208";a="506742638"
Received: from orsmsx103.amr.corp.intel.com ([10.22.225.130]) by orsmga001.jf.intel.com with ESMTP; 06 May 2014 06:54:17 -0700
Received: from orsmsx154.amr.corp.intel.com (10.22.226.12) by ORSMSX103.amr.corp.intel.com (10.22.225.130) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 6 May 2014 06:54:17 -0700
Received: from orsmsx114.amr.corp.intel.com ([169.254.8.17]) by ORSMSX154.amr.corp.intel.com ([169.254.11.72]) with mapi id 14.03.0123.003; Tue, 6 May 2014 06:54:17 -0700
From: "Moustafa, Hassnaa" <hassnaa.moustafa@intel.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Version Notification for draft-mou-pcp-application-network-feedback-01.txt
Thread-Index: AQHPaTGBexFV2amMpUmU1d+C3YM7VZszkb+Q
Date: Tue, 6 May 2014 13:54:17 +0000
Message-ID: <F893BEC192403B489DBA38999068CF19063A1052@ORSMSX114.amr.corp.intel.com>
References: <20140506134539.19037.23151.idtracker@ietfa.amsl.com>
In-Reply-To: <20140506134539.19037.23151.idtracker@ietfa.amsl.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
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/NNRtgNUSHbSusuzeW96E0Y9MvY4
Cc: "Moses, Danny" <danny.moses@intel.com>
Subject: [pcp] FW: New Version Notification for draft-mou-pcp-application-network-feedback-01.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, 06 May 2014 13:54:29 -0000

SGkgQWxsLA0KDQpBbiB1cGRhdGVkIHZlcnNpb24gZm9yIHRoZSBkcmFmdCAoZHJhZnQtbW91LXBj
cC1hcHBsaWNhdGlvbi1uZXR3b3JrLWZlZWRiYWNrKSBpcyBwb3N0ZWQgKFVSTDogaHR0cDovL3d3
dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtbW91LXBjcC1hcHBsaWNhdGlvbi1uZXR3
b3JrLWZlZWRiYWNrLTAxLnR4dCkuDQoNClRoZSBmb2xsb3dpbmcgdXBkYXRlcyBhcmUgZG9uZSBm
b2xsb3dpbmcgdGhlIGRpZmZlcmVudCBjb21tZW50cyB0aGF0IHdlIGhhZDoNCi0gYWRkaW5nIG1v
cmUgY2xhcmlmaWNhdGlvbiBvbiB0aGUgYWJzdHJhY3QgYW5kIGludHJvZHVjdGlvbg0KLSBsaW1p
dGluZyB1c2UtY2FzZXMgdG8gb25lIHVzZS1jYXNlIChyZWFsLXRpbWUgdmlkZW8gdHJhbnNjb2Rp
bmcpDQotIHJlbW92aW5nIGZlZWRiYWNrIGluZm9ybWF0aW9uIHJlZ2FyZGluZyB0aGUgZW52aXJv
bm1lbnQgbm9pc2UgYW5kIGxpZ2h0IChmcm9tIHRleHQgYW5kIGZyb20gUENQIHNpZ25hbGluZyBh
bHNvKQ0KDQoNCkxvb2tpbmcgZm9yd2FyZCB0byByZWNlaXZpbmcgeW91ciBjb21tZW50cyBhbmQg
dG8gbW9yZSBkaXNjdXNzaW9uLg0KDQpIYXNzbmFhDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t
LS0tDQpGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFm
dHNAaWV0Zi5vcmddIA0KU2VudDogVHVlc2RheSwgTWF5IDA2LCAyMDE0IDY6NDYgQU0NClRvOiBN
b3VzdGFmYSwgSGFzc25hYTsgTW9oYW1lZCBCb3VjYWRhaXI7IE1vdXN0YWZhLCBIYXNzbmFhOyBN
b3NlcywgRGFubnk7IE1vaGFtZWQgQm91Y2FkYWlyOyBNb3NlcywgRGFubnkNClN1YmplY3Q6IE5l
dyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtbW91LXBjcC1hcHBsaWNhdGlvbi1uZXR3
b3JrLWZlZWRiYWNrLTAxLnR4dA0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1tb3Ut
cGNwLWFwcGxpY2F0aW9uLW5ldHdvcmstZmVlZGJhY2stMDEudHh0DQpoYXMgYmVlbiBzdWNjZXNz
ZnVsbHkgc3VibWl0dGVkIGJ5IEhhc3NuYWEgTW91c3RhZmEgYW5kIHBvc3RlZCB0byB0aGUgSUVU
RiByZXBvc2l0b3J5Lg0KDQpOYW1lOgkJZHJhZnQtbW91LXBjcC1hcHBsaWNhdGlvbi1uZXR3b3Jr
LWZlZWRiYWNrDQpSZXZpc2lvbjoJMDENClRpdGxlOgkJUENQIEV4dGVuc2lvbiBmb3IgU2lnbmFs
aW5nIEZlZWRiYWNrIEluZm9ybWF0aW9uIGZyb20gdGhlIEVuZC1Vc2VyIEFwcGxpY2F0aW9uIHRv
IHRoZSBBcHBsaWNhdGlvbiBTZXZlciBhbmQgdG8gdGhlIE5ldHdvcmsNCkRvY3VtZW50IGRhdGU6
CTIwMTQtMDUtMDYNCkdyb3VwOgkJSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQpQYWdlczoJCTEzDQpV
Ukw6ICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQt
bW91LXBjcC1hcHBsaWNhdGlvbi1uZXR3b3JrLWZlZWRiYWNrLTAxLnR4dA0KU3RhdHVzOiAgICAg
ICAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LW1vdS1wY3AtYXBwbGlj
YXRpb24tbmV0d29yay1mZWVkYmFjay8NCkh0bWxpemVkOiAgICAgICBodHRwOi8vdG9vbHMuaWV0
Zi5vcmcvaHRtbC9kcmFmdC1tb3UtcGNwLWFwcGxpY2F0aW9uLW5ldHdvcmstZmVlZGJhY2stMDEN
CkRpZmY6ICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1t
b3UtcGNwLWFwcGxpY2F0aW9uLW5ldHdvcmstZmVlZGJhY2stMDENCg0KQWJzdHJhY3Q6DQogICBO
b3dhZGF5cyB1c2VycyBjb25zdW1wdGlvbiBzdHlsZSBmb3IgdmlkZW8gYW5kIG11bHRpbWVkaWEN
CiAgIGFwcGxpY2F0aW9ucyBpcyBzdHJvbmdseSBjaGFuZ2luZy4gIFVzZXJzIGFyZSBjb25zdW1p
bmcgY29udGVudA0KICAgdGhyb3VnaCBtdWx0aS1zY3JlZW4gYW5kIGFyZSBoZWF2aWx5IGNvdW50
aW5nIG9uIHdpcmVsZXNzIGFuZCBtb2JpbGUNCiAgIGRldmljZXMgZm9yIHZpZGVvIHN0cmVhbWlu
ZyBhbmQgaW50ZXJhY3RpdmUgdmlkZW8gYW5kIG11bHRpbWVkaWENCiAgIGFwcGxpY2F0aW9ucy4g
IFRoaXMgbmVjZXNzaXRhdGVzIG1vcmUgaW50ZWxsaWdlbmNlIGluIHRoZSBzZXJ2aWNlIGFuZA0K
ICAgdGhlIG5ldHdvcmsgaW5mcmFzdHJ1Y3R1cmUgdG8gYmV0dGVyIHN1aXQgYSBkaWZmZXJlbnRp
YXRlZCB1c2Vycw0KICAgY29uc3VtcHRpb24gc3R5bGUsIHdoaWNoIGNhbiBiZSBhY2hpZXZlZCB0
aHJvdWdoIGhhdmluZzogKGkpIGENCiAgIGtub3dsZWRnZSBpbiB0aGUgbmV0d29yayBhbmQgc2Vy
dmljZSBwbGF0Zm9ybSBhYm91dCB0aGUgYXZhaWxhYmxlDQogICBkZXZpY2UgYW5kIG5ldHdvcmsg
Y29uZGl0aW9ucyBmb3IgdGhlIGVuZC11c2VyIGFuZCAoaWkpIGEga25vd2xlZGdlDQogICBpbiB0
aGUgbmV0d29yayBhYm91dCB0aGUgY29udGVudCByZXF1aXJlbWVudHMgaW4gdGVybXMgb2YgZGV2
aWNlcw0KICAgY2FwYWJpbGl0aWVzIGFuZCBuZXR3b3JrIHJlc291cmNlcyBmb3IgY29udGVudCBz
dG9yZWQgZWl0aGVyIGluIHRoZQ0KICAgbmV0d29yayBvciBpbiB0aGUgYXBwbGljYXRpb24gc2Vy
dmVyLiAgVG8gb2J0YWluIHN1Y2gga25vd2xlZGdlIHdpdGgNCiAgIG5vIG5lZWQgZm9yIGNoYW5n
aW5nIHRoZSBjdXJyZW50IGluZnJhc3RydWN0dXJlIGFuZCBpbiBhIGdlbmVyYWxpemVkDQogICB3
YXkgdG8gYWxsIGFwcGxpY2F0aW9ucywgZmVlZGJhY2svbm90aWZpY2F0aW9uIG1lY2hhbmlzbXMg
YmV0d2VlbiB0aGUNCiAgIGVuZC11c2VyIGFwcGxpY2F0aW9uLCB0aGUgbmV0d29yayBhbmQgdGhl
IHNlcnZpY2UgcGxhdGZvcm0gaXMgbmVlZGVkDQogICB0byBwcm92aWRlIGluZm9ybWF0aW9uIGhl
bHBpbmcgdGhlIGNvbnRlbnQgZGVsaXZlcnkgYW5kIGFkYXB0YXRpb24NCiAgIGRlY2lzaW9ucy4g
IFRoaXMgZG9jdW1lbnQgaXMgaW52ZXN0aWdhdGluZyBzdWNoIGFwcGxpY2F0aW9uLWFnbm9zdGlj
DQogICB0cmFjay4NCg0KICAgVGhpcyBkb2N1bWVudCBleHRlbmRzIHRoZSBQb3J0IENvbnRyb2wg
UHJvdG9jb2wgKFBDUCkgUkZDIDY4ODcNCiAgIFtSRkM2ODg3XSB0byBhbGxvdzogKGkpIHRoZSB1
c2VycyBhcHBsaWNhdGlvbiB0byBub3RpZnkgdGhlIG5ldHdvcmsNCiAgIGFuZCBhcHBsaWNhdGlv
biBzZXJ2ZXIgYWJvdXQgaXRzIGF2YWlsYWJsZSByZXNvdXJjZXMgaW4gdGVybXMgb2YNCiAgIGRl
dmljZXMgY2FwYWJpbGl0aWVzIGFuZCBuZXR3b3JrIGNvbmRpdGlvbnMgYXMgd2VsbCBhcyBpbmZv
cm1hdGlvbg0KICAgYWJvdXQgdGhlIHVzZXIgKGUuZy4sIGxvY2F0aW9uLCBtb2JpbGl0eSBzdGF0
dXMpIGFuZCAoaWkpIHRoZQ0KICAgYXBwbGljYXRpb24gc2VydmVyIHRvIG5vdGlmeSB0aGUgbmV0
d29yayBhYm91dCB0aGUgcmVxdWlyZW1lbnRzIG9mDQogICB0aGUgY29udGVudCBpdCBzdG9yZXMg
aW4gdGVybXMgb2YgZGV2aWNlcyBhbmQgbmV0d29yayByZXNvdXJjZXMuICBBDQogICBuZXcgUENQ
IG9wdGlvbiwgZGVub3RlZCB0aGUgRkVFREJBQ0ssIGlzIHNwZWNpZmllZCB0byBhbGxvdyBzdWNo
DQogICBmZWVkYmFjayBub3RpZmljYXRpb24gc2lnbmFsaW5nLiAgVGhpcyBvcHRpb24gaXMgdXNl
ZCB3aXRoIGJvdGggUEVFUg0KICAgYW5kIE1BUCBPcGNvZGVzLg0KDQogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgDQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBt
aW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVy
c2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KDQpUaGUgSUVU
RiBTZWNyZXRhcmlhdA0KDQo=


From nobody Wed May  7 10:26:56 2014
Return-Path: <markus.stenberg@iki.fi>
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 65B3F1A0842 for <pcp@ietfa.amsl.com>; Wed,  7 May 2014 10:26:55 -0700 (PDT)
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, 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 AJybatIGJyun for <pcp@ietfa.amsl.com>; Wed,  7 May 2014 10:26:53 -0700 (PDT)
Received: from kirsi1.inet.fi (mta-out1.inet.fi [62.71.2.198]) by ietfa.amsl.com (Postfix) with ESMTP id E142D1A083E for <pcp@ietf.org>; Wed,  7 May 2014 10:26:52 -0700 (PDT)
Received: from [192.168.43.129] (80.220.67.193) by kirsi1.inet.fi (8.5.140.03) (authenticated as stenma-47) id 534D34B501AE9EF9; Wed, 7 May 2014 20:26:32 +0300
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36F5B63D4ED@PUEXCB1B.nanterre.francetelecom.fr>
Date: Wed, 7 May 2014 19:26:16 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F51B354-E2E2-44AC-B96C-8AD424D27BA5@iki.fi>
References: <FDB45976-B7A3-4C59-B2D1-C01982D0205F@iki.fi> <45A697A8FFD7CF48BCF2BE7E106F06040B8C957D@xmb-rcd-x04.cisco.com> <2B975F36-4E46-4D93-891B-DB4E480FF190@iki.fi> <94C682931C08B048B7A8645303FDC9F36F5B63D4ED@PUEXCB1B.nanterre.francetelecom.fr>
To: mohamed.boucadair@orange.com
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/T4BLJgS5Bal0g4BHrj5kgabTIKk
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] How can I make a ~stateless forwarding PCP proxy again?
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, 07 May 2014 17:26:55 -0000

On 6.5.2014, at 11.48, <mohamed.boucadair@orange.com> =
<mohamed.boucadair@orange.com> wrote:

> Hi Markus,
>=20
> It seems that your design is close to what is documented in =
http://tools.ietf.org/html/draft-ietf-pcp-proxy-04#section-8, no?
>=20
> FWIW, the heaviness of the b2b model was raised in slide 6 of =
http://tools.ietf.org/agenda/89/slides/slides-89-pcp-4.pdf but I don't =
know what was the outcome of that discussion.

It=92s perhaps similar, yes. There are differences, though, in which =
it=92s also somewhat similar to the current proxy draft (own epoch =
tracking, multiple servers,  etc). I wrote it up in a rather brief draft =
here - comments and criticism welcome:

=
http://tools.ietf.org/html/draft-stenberg-homenet-minimalist-pcp-proxy-00

I=92m not really sure I=92m going to push that in homenet (or here), but =
I am tinkering with an implementation and seeing if it fulfills the need =
I have in homenet cases where I need PCP proxying (as opposed to the =
full-blown draft-ietf-pcp-proxy-05).

Cheers,

-Markus=


From nobody Wed May 14 03:50:30 2014
Return-Path: <markus.stenberg@iki.fi>
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 89F6E1A004A for <pcp@ietfa.amsl.com>; Wed, 14 May 2014 03:50:28 -0700 (PDT)
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 NaUtPgZIxfZb for <pcp@ietfa.amsl.com>; Wed, 14 May 2014 03:50:26 -0700 (PDT)
Received: from kirsi1.inet.fi (mta-out1.inet.fi [62.71.2.199]) by ietfa.amsl.com (Postfix) with ESMTP id B9AC91A0041 for <pcp@ietf.org>; Wed, 14 May 2014 03:50:25 -0700 (PDT)
Received: from [192.168.43.129] (80.220.67.193) by kirsi1.inet.fi (8.5.140.03) (authenticated as stenma-47) id 534D34B5023290E7; Wed, 14 May 2014 13:50:12 +0300
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <320291FF-E45B-40E6-9D54-617419713506@cisco.com>
Date: Wed, 14 May 2014 13:50:11 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F94795C-EF78-4579-82C7-F1CB538D75AF@iki.fi>
References: <FDB45976-B7A3-4C59-B2D1-C01982D0205F@iki.fi> <45A697A8FFD7CF48BCF2BE7E106F06040B8C957D@xmb-rcd-x04.cisco.com> <2B975F36-4E46-4D93-891B-DB4E480FF190@iki.fi> <320291FF-E45B-40E6-9D54-617419713506@cisco.com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/zQOw_aDZq7g8kCtzHe_Y31w_-f0
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] How can I make a ~stateless forwarding PCP proxy again?
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, 14 May 2014 10:50:28 -0000

On 6.5.2014, at 9.01, Dan Wing <dwing@cisco.com> wrote:
> On May 5, 2014, at 1:14 PM, Markus Stenberg <markus.stenberg@iki.fi> =
wrote:
>> On 5.5.2014, at 21.41, Reinaldo Penno (repenno) <repenno@cisco.com> =
wrote:
>>> we had this discussion in the past but and I, for one, backed the =
idea of PCP being able to support stateless proxies.  So, you are not =
alone there but maybe you want to write a draft about it so the WG can =
discuss it.
>>=20
>>=20
>> Nods. Personally I like to minimize the amount of state in a system, =
so I=92m a fan of stateless designs. My current design for a proxy has =
just 3 logical pieces of =91state=92 per supported remote server:
>>=20
>> - (client) source prefix + prefix length to match
>> - address of the server
>> - server epoch + when was it received
>>=20
>> And currently I=92m trying to make sure it=92s actually doable to do =
all I want with just that and few hundred lines of C. After looking at =
how big PCP client libraries are, last thing I want is really PCP client =
glued to PCP server.
>>=20
>> Getting back to my previous question, now that I think of it, =
actually, the IP address of the client is in the THIRD_PARTY option. =
Only thing that isn=92t explicitly stored somewhere is the address =
client contacts the proxy on (it probably has 1-N addresses per M =
interfaces). If proxy uses same source address for talking with server =
as client used to contact it (with different port, obviously), it should =
work fine, without per-client or per-request state.=20
>>=20
>> e.g.
>>=20
>> C -> P [IntIP=3DC]
>> P -> S [IntIP=3DP, TP=3DC]
>> S -> P [TP=3DC]
>> P -> C [no TP]
>>=20
>> Beyond that, some ANNOUNCE handling is needed, but as long as you =
stick to multicast, that can be also stateless. (Connected clients know =
if they have state with the particular proxy that spams ANNOUNCEs.)
>>=20
>> Perhaps I=92ll write up about it somewhere (pcp or homenet), although =
it=92s more of an implementation detail draft, than actual protocol =
change requiring one.
>>=20
>> Cheers,
>>=20
>> -Markus
>>=20
>> P.S. This scheme works fine with IPv4. With IPv6, it may have issues, =
when C contacts P using link-local address and I don=92t think there is =
anything preventing that.
>=20
> Correct, nothing prevents it.  But C is unable to show it owns another =
address (so can't use THIRD_PARTY), and link-local doesn't do anything =
on the other side of the router (firewall), so seems fruitless for C's =
PCP client to use link local.  I would even think P or any PCP server =
should just return an error if the PCP request came from an IPv6 link =
local address and the proxy (or PCP server) is not doing NPTv6 or NAT66. =
 Link local can=92t go anywhere, so seems an error no matter if proxy or =
PCP server returns an error -- link-local won't do any good as a =
firewall rule because it isn't routable from the Internet.

The main problem is if this happens:

C uses GUA IPv6 address
 .. and has only link-local next-hop route to P to find IPv6 PCP server
=3D> contacts P with src =3D GUA, dst =3D link-local

=3D> P cannot meaningfully forward it to S using src =3D C=92s =
linklocal.

I=92m not sure how IPv6 PCP in general should work (I haven=92t seen =
that many implementations of it in the wild), is it supposed to work =
only given DHCP* option?

Cheers,

-Markus=


From nobody Wed May 14 03:55:34 2014
Return-Path: <markus.stenberg@iki.fi>
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 898FA1A0032 for <pcp@ietfa.amsl.com>; Wed, 14 May 2014 03:55:32 -0700 (PDT)
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 ivLC_WnImAWV for <pcp@ietfa.amsl.com>; Wed, 14 May 2014 03:55:31 -0700 (PDT)
Received: from jenni1.inet.fi (mta-out1.inet.fi [62.71.2.198]) by ietfa.amsl.com (Postfix) with ESMTP id 1E8381A002A for <pcp@ietf.org>; Wed, 14 May 2014 03:55:30 -0700 (PDT)
Received: from [192.168.43.129] (80.220.67.193) by jenni1.inet.fi (8.5.140.03) (authenticated as stenma-47) id 534D2930023323F8; Wed, 14 May 2014 13:55:19 +0300
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <4F94795C-EF78-4579-82C7-F1CB538D75AF@iki.fi>
Date: Wed, 14 May 2014 13:55:15 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <786B9B35-631D-4941-9CDC-5D800EF201C3@iki.fi>
References: <FDB45976-B7A3-4C59-B2D1-C01982D0205F@iki.fi> <45A697A8FFD7CF48BCF2BE7E106F06040B8C957D@xmb-rcd-x04.cisco.com> <2B975F36-4E46-4D93-891B-DB4E480FF190@iki.fi> <320291FF-E45B-40E6-9D54-617419713506@cisco.com> <4F94795C-EF78-4579-82C7-F1CB538D75AF@iki.fi>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/HH4qG1J0HAqh3coy4d_QIQ6lG4o
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] How can I make a ~stateless forwarding PCP proxy again?
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, 14 May 2014 10:55:32 -0000

On 14.5.2014, at 13.50, Markus Stenberg <markus.stenberg@iki.fi> wrote:
> =3D> P cannot meaningfully forward it to S using src =3D C=92s =
linklocal.

Argh. Should=92ve reread what I wrote. It should have been:

using src =3D P=92s linklocal that is (so that the reverse chain towards =
C will be able to get the address from the reply=92s dst).

Having looked at various ways on how e.g. homenet solution can work, =
there=92s few different ways to do it. This limited minimalist stateless =
proxy may not be the long-term correct way, but I=92m not convinced =
we=92ll see good working general-purpose proxies any time soon either.

(And of course I=92m hoping to be proven wrong, and in open source, =
preferably..)

Cheers,

-Markus=


From nobody Wed May 14 14:12:35 2014
Return-Path: <wwwrun@rfc-editor.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 D25821A0126; Wed, 14 May 2014 14:12:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level: 
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 ZciMn7boAaAK; Wed, 14 May 2014 14:12:30 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4FA201A0195; Wed, 14 May 2014 14:12:30 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5D46D180016; Wed, 14 May 2014 14:11:26 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140514211126.5D46D180016@rfc-editor.org>
Date: Wed, 14 May 2014 14:11:26 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/0jGxf-OvUWgRuYp3NiZ9PcQbMi0
Cc: drafts-update-ref@iana.org, pcp@ietf.org, rfc-editor@rfc-editor.org
Subject: [pcp] RFC 7220 on Description Option for the Port Control Protocol (PCP)
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, 14 May 2014 21:12:33 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7220

        Title:      Description Option for the Port 
                    Control Protocol (PCP) 
        Author:     M. Boucadair,
                    R. Penno,
                    D. Wing
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2014
        Mailbox:    mohamed.boucadair@orange.com, 
                    repenno@cisco.com, 
                    dwing@cisco.com
        Pages:      6
        Characters: 11332
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pcp-description-option-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7220.txt

This document extends the Port Control Protocol (PCP) with the ability to
associate a description with a PCP-instantiated mapping.  It does this
by defining a new DESCRIPTION option.

This document is a product of the Port Control Protocol Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


From nobody Fri May 16 14:39:51 2014
Return-Path: <wwwrun@rfc-editor.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 CA93F1A0254; Fri, 16 May 2014 14:39:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level: 
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 hBs1HULBmOaU; Fri, 16 May 2014 14:39:39 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 79EF41A0260; Fri, 16 May 2014 14:39:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A3494180013; Fri, 16 May 2014 14:38:25 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140516213825.A3494180013@rfc-editor.org>
Date: Fri, 16 May 2014 14:38:25 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/wMOGEDZyCKAnFWyTA9suNN0GgnM
Cc: drafts-update-ref@iana.org, pcp@ietf.org, rfc-editor@rfc-editor.org
Subject: [pcp] RFC 7225 on Discovering NAT64 IPv6 Prefixes Using the Port Control Protocol (PCP)
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: Fri, 16 May 2014 21:39:45 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7225

        Title:      Discovering NAT64 IPv6 Prefixes Using 
                    the Port Control Protocol (PCP) 
        Author:     M. Boucadair
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2014
        Mailbox:    mohamed.boucadair@orange.com
        Pages:      17
        Characters: 40239
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pcp-nat64-prefix64-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7225.txt

This document defines a new Port Control Protocol (PCP) option to learn
the IPv6 prefix(es) used by a PCP-controlled NAT64 device to build 
IPv4-converted IPv6 addresses.  This option is needed for successful 
communications when IPv4 addresses are used in referrals.

This document is a product of the Port Control Protocol Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Sun May 25 15:22:18 2014
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 A114B1A03FE; Sun, 25 May 2014 15:22:15 -0700 (PDT)
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 K3bRXANJVq1m; Sun, 25 May 2014 15:22:14 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A87FB1A03F5; Sun, 25 May 2014 15:22:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140525222214.13666.51626.idtracker@ietfa.amsl.com>
Date: Sun, 25 May 2014 15:22:14 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/vlqyBJAhjDwSwWsVP8rf_Zeousk
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-port-set-05.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: Sun, 25 May 2014 22:22:16 -0000

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
        Authors         : Qiong Sun
                          Mohamed Boucadair
                          Senthil Sivakumar
                          Cathy Zhou
                          Tina Tsou
                          Simon Perreault
	Filename        : draft-ietf-pcp-port-set-05.txt
	Pages           : 17
	Date            : 2014-05-24

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

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


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 nobody Mon May 26 06:51:56 2014
Return-Path: <simon@per.reau.lt>
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 25A9F1A0157 for <pcp@ietfa.amsl.com>; Mon, 26 May 2014 06:51:56 -0700 (PDT)
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, SPF_HELO_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 fOnTkow1TJfF for <pcp@ietfa.amsl.com>; Mon, 26 May 2014 06:51:54 -0700 (PDT)
Received: from nomis80.org (nomis80.org [IPv6:2600:3c03::f03c:91ff:fe69:7108]) by ietfa.amsl.com (Postfix) with ESMTP id 2AF241A015F for <pcp@ietf.org>; Mon, 26 May 2014 06:51:54 -0700 (PDT)
Received: from [192.168.1.96] (unknown [24.48.120.98]) by nomis80.org (Postfix) with ESMTPSA id BBF021D1002 for <pcp@ietf.org>; Mon, 26 May 2014 13:53:21 +0000 (UTC)
Message-ID: <538346FE.50503@per.reau.lt>
Date: Mon, 26 May 2014 09:51:58 -0400
From: Simon Perreault <simon@per.reau.lt>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: pcp@ietf.org
References: <20140525222214.13666.51626.idtracker@ietfa.amsl.com>
In-Reply-To: <20140525222214.13666.51626.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/NMc6P-5EbYnrKjV049reA5kEjNU
Subject: Re: [pcp] I-D Action: draft-ietf-pcp-port-set-05.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: Mon, 26 May 2014 13:51:56 -0000

This new revision addresses comments received at IETF 88. (Yeah, that 
was two IETFs ago. Long overdue. Very sorry.) To this editor's knowledge 
this closes all open issues.

Changes:

- Added text about capability discovery, specifically that a server may 
reset the epoch when port set capability is added or removed.

- Mentioned in the security considerations section that an eavesdropper 
could mount an amplification attack since a single request may generate 
multiple responses.

Simon

Le 2014-05-25 18:22, 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
>          Authors         : Qiong Sun
>                            Mohamed Boucadair
>                            Senthil Sivakumar
>                            Cathy Zhou
>                            Tina Tsou
>                            Simon Perreault
> 	Filename        : draft-ietf-pcp-port-set-05.txt
> 	Pages           : 17
> 	Date            : 2014-05-24
>
> 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-05
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-pcp-port-set-05
>
>
> 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
>

