
From nobody Fri Jul  4 03:11:02 2014
Return-Path: <phdgang@gmail.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 7F5951B2CC2 for <pcp@ietfa.amsl.com>; Fri,  4 Jul 2014 03:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 Bj37liNXDTAH for <pcp@ietfa.amsl.com>; Fri,  4 Jul 2014 03:11:00 -0700 (PDT)
Received: from mail-qa0-x22b.google.com (mail-qa0-x22b.google.com [IPv6:2607:f8b0:400d:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 146E21A0AB8 for <pcp@ietf.org>; Fri,  4 Jul 2014 03:11:00 -0700 (PDT)
Received: by mail-qa0-f43.google.com with SMTP id k15so1185005qaq.16 for <pcp@ietf.org>; Fri, 04 Jul 2014 03:10:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=qsmiB/EN57p9l8rIpeFCcc6f7cH8dB/k4VpPX32BlxY=; b=roBlaCdVXd88U85nsdCFv0CaIuCoFkNP5xmkmGf8Zny+JtdF52gA1+rDL0VcGFnO8D 8I7+71Id6DO2t/x4OxoNN5ADLXuSCRC4MKlkxz2Kn/oAwn8rINvz4feDT2h0Ys6KpWtu twOfJ0CFZJJjEr6IeGUNV+unW4tyecII4X13bLu6UjVcVcSj5Cu3USlvWpZyBqSrVTqC ig8Aw+pkuEr/Rj95FQANcSe+asGwLrnn0QQXXV6nNue5R/LxK4LODO7ezIoOUlpnd9GF hdmoE6vtYGYWEUI8g9E8nFc23q+RjGhGNaoIIyns8SBq4ug8v2exNA9rXdUmq4DmXF6V 1mAA==
MIME-Version: 1.0
X-Received: by 10.140.46.70 with SMTP id j64mr16227672qga.27.1404468659369; Fri, 04 Jul 2014 03:10:59 -0700 (PDT)
Received: by 10.224.80.138 with HTTP; Fri, 4 Jul 2014 03:10:59 -0700 (PDT)
In-Reply-To: <20140704100305.5871.22183.idtracker@ietfa.amsl.com>
References: <20140704100305.5871.22183.idtracker@ietfa.amsl.com>
Date: Fri, 4 Jul 2014 18:10:59 +0800
Message-ID: <CAM+vMESOe+wcFsMg4aOxr7q6J99Ubu0NWAPqch1-b1r=qMCGuA@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/W6fphH-DLOzyLKMQOeucToI1zxU
Subject: [pcp] Fwd: New Version Notification for draft-chen-pcp-authentication-sim-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: Fri, 04 Jul 2014 10:11:01 -0000

WG,

I have submitted a draft to describe the consideration of PCP
authentication with (U)SIM support. The process is detailed in EAP and
GBA framework.
Thank you for the comments in advance.

Best Regards

Gang

---------- Forwarded message ----------
From: internet-drafts@ietf.org
Date: Fri, 04 Jul 2014 03:03:05 -0700
Subject: New Version Notification for draft-chen-pcp-authentication-sim-00.txt
To: Gang Chen <phdgang@gmail.com>


A new version of I-D, draft-chen-pcp-authentication-sim-00.txt
has been successfully submitted by Gang Chen and posted to the
IETF repository.

Name:		draft-chen-pcp-authentication-sim
Revision:	00
Title:		(U)SIM based PCP Authentication
Document date:	2014-07-03
Group:		Individual Submission
Pages:		8
URL:
http://www.ietf.org/internet-drafts/draft-chen-pcp-authentication-sim-00.txt
Status:
https://datatracker.ietf.org/doc/draft-chen-pcp-authentication-sim/
Htmlized:       http://tools.ietf.org/html/draft-chen-pcp-authentication-sim-00


Abstract:
   With (U)SIM support, PCP authentication could leverage the
   credentials stored in (U)SIM.  The document details PCP
   authentication considerations based on (U)SIM support.  The
   authentication procedures in EAP and GBA framework have been
   specifically elaborated.  In order to complete the process, new code
   and option are also proposed.




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 nobody Fri Jul  4 04:05:36 2014
Return-Path: <Andreas.Ripke@neclab.eu>
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 3292B1B2D07 for <pcp@ietfa.amsl.com>; Fri,  4 Jul 2014 04:05:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.253
X-Spam-Level: 
X-Spam-Status: No, score=-3.253 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, 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 RMSYOrHJsMNx for <pcp@ietfa.amsl.com>; Fri,  4 Jul 2014 04:05:30 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9B5F1B2D01 for <pcp@ietf.org>; Fri,  4 Jul 2014 04:05:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 43B4B1079EF for <pcp@ietf.org>; Fri,  4 Jul 2014 13:05:28 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wkRW7f4PiisC for <pcp@ietf.org>; Fri,  4 Jul 2014 13:05:28 +0200 (CEST)
X-ENC: Last-Hop-TLS-encrypted
X-ENC: Last-Hop-TLS-encrypted
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 26E1E1079D3 for <pcp@ietf.org>; Fri,  4 Jul 2014 13:05:23 +0200 (CEST)
Received: from DAPHNIS.office.hd ([169.254.2.123]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Fri, 4 Jul 2014 13:05:22 +0200
From: Andreas Ripke <Andreas.Ripke@neclab.eu>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Version Notification for draft-ripke-pcp-tunnel-id-option-01.txt
Thread-Index: AQHPl3Ond1s//Hsjp0CcLYDTq0HzY5uPv3hA
Date: Fri, 4 Jul 2014 11:05:22 +0000
Message-ID: <2D2FFE4726FAF74285C45D69FDC30E798D60089F@DAPHNIS.office.hd>
References: <20140704103500.20587.59638.idtracker@ietfa.amsl.com>
In-Reply-To: <20140704103500.20587.59638.idtracker@ietfa.amsl.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.6.215]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/ih5zIKLX-sy1fOqAfVdHxq29MtI
Subject: [pcp] FW: New Version Notification for draft-ripke-pcp-tunnel-id-option-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: Fri, 04 Jul 2014 11:05:33 -0000

RGVhciBhbGwsDQoNClRoYW5rIHlvdSBmb3IgYWxsIHRoZSBmZWVkYmFjayB3ZSByZWNlaXZlZCBh
dCB0aGUgbGFzdCBtZWV0aW5nIG9uIHRoZSBUVU5ORUxfSUQgb3B0aW9uLiBUaGlzIHdhcyB2ZXJ5
IGhlbHBmdWwuIFdlIGhhdmUgdXBkYXRlZCBvdXIgZHJhZnQgYWNjb3JkaW5nbHkgYW5kIGFsaWdu
ZWQgb3VyIHVzZSBjYXNlIHdpdGggdXNlIGNhc2VzIGZyb20gZXhpc3RpbmcgUENQIGRyYWZ0cy9S
RkNzLiBQYXJ0aWN1bGFybHkgd2UgbW92ZWQgdGhlIGZvY3VzIGZyb20gYSByYXRoZXIgc3RhdGlj
IHdlYiBwb3J0YWwgc2NlbmFyaW8gdG8gYSBtb3JlIGR5bmFtaWMgVVBuUCBJbnRlcndvcmtpbmcg
c2NlbmFyaW8uIA0KDQpodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1y
aXBrZS1wY3AtdHVubmVsLWlkLW9wdGlvbi0wMS50eHQNCg0KUGxlYXNlIGhhdmUgYSBsb29rIGF0
IHRoZSBkcmFmdCBhbmQgZ2l2ZSB1cyB5b3VyIGZlZWRiYWNrLg0KDQpCZXN0IHJlZ2FyZHMsDQoN
CkFuZHJlYXMNCg0KDQpORUMgRXVyb3BlIEx0ZCB8IFJlZ2lzdGVyZWQgT2ZmaWNlOiBBdGhlbmUs
IE9keXNzZXkgQnVzaW5lc3MgUGFyaywgV2VzdCBFbmQgIFJvYWQsIExvbmRvbiwgSEE0IDZRRSwg
R0IgfCBSZWdpc3RlcmVkIGluIEVuZ2xhbmQgMjgzMjAxNA0KDQoNCg0KDQoNCg0KQSBuZXcgdmVy
c2lvbiBvZiBJLUQsIGRyYWZ0LXJpcGtlLXBjcC10dW5uZWwtaWQtb3B0aW9uLTAxLnR4dA0KaGFz
IGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBBbmRyZWFzIFJpcGtlIGFuZCBwb3N0ZWQg
dG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0KTmFtZToJCWRyYWZ0LXJpcGtlLXBjcC10dW5uZWwt
aWQtb3B0aW9uDQpSZXZpc2lvbjoJMDENClRpdGxlOgkJUENQIFR1bm5lbC1JRCBPcHRpb24NCkRv
Y3VtZW50IGRhdGU6CTIwMTQtMDctMDMNCkdyb3VwOgkJSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQpQ
YWdlczoJCTEwDQpVUkw6ICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1k
cmFmdHMvZHJhZnQtcmlwa2UtcGNwLXR1bm5lbC1pZC1vcHRpb24tMDEudHh0DQpTdGF0dXM6ICAg
ICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtcmlwa2UtcGNwLXR1
bm5lbC1pZC1vcHRpb24vDQpIdG1saXplZDogICAgICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0
bWwvZHJhZnQtcmlwa2UtcGNwLXR1bm5lbC1pZC1vcHRpb24tMDENCkRpZmY6ICAgICAgICAgICBo
dHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1yaXBrZS1wY3AtdHVubmVsLWlk
LW9wdGlvbi0wMQ0KDQpBYnN0cmFjdDoNCiAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGEgbmV3
IFBvcnQgQ29udHJvbCBQcm90b2NvbCAoUENQKSBvcHRpb24NCiAgIGNhbGxlZCBUVU5ORUxfSUQu
ICBJdCBzZXJ2ZXMgZm9yIGlkZW50aWZ5aW5nIGEgVGhpcmQgUGFydHkgaW4NCiAgIGFkZGl0aW9u
IHRvIHRoZSBtZWFucyB0aGF0IFBDUCdzIFRISVJEX1BBUlRZIG9wdGlvbiBhbHJlYWR5IHByb3Zp
ZGVzDQogICBmb3IgdGhhdCBwdXJwb3NlLg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQoN
Cg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20g
dGhlIHRpbWUgb2Ygc3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlm
ZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KDQpUaGUgSUVURiBTZWNyZXRhcmlh
dA0KDQo=


From nobody Wed Jul  9 01:42:36 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 9D3DC1A03A7 for <pcp@ietfa.amsl.com>; Wed,  9 Jul 2014 01:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 fHvxzUH6HDRK for <pcp@ietfa.amsl.com>; Wed,  9 Jul 2014 01:42:32 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E98DB1A03B1 for <pcp@ietf.org>; Wed,  9 Jul 2014 01:42:31 -0700 (PDT)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda13.si.francetelecom.fr (ESMTP service) with ESMTP id 382D71904D5; Wed,  9 Jul 2014 10:42:30 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.30]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id 185F4384055; Wed,  9 Jul 2014 10:42:30 +0200 (CEST)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.67]) by OPEXCLILH02.corporate.adroot.infra.ftgroup ([10.114.31.30]) with mapi id 14.03.0181.006; Wed, 9 Jul 2014 10:42:30 +0200
From: <mohamed.boucadair@orange.com>
To: Andreas Ripke <Andreas.Ripke@neclab.eu>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Version Notification for draft-ripke-pcp-tunnel-id-option-01.txt
Thread-Index: AQHPl3Ond1s//Hsjp0CcLYDTq0HzY5uPv3hAgAezYcA=
Date: Wed, 9 Jul 2014 08:42:29 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933002F541@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <20140704103500.20587.59638.idtracker@ietfa.amsl.com> <2D2FFE4726FAF74285C45D69FDC30E798D60089F@DAPHNIS.office.hd>
In-Reply-To: <2D2FFE4726FAF74285C45D69FDC30E798D60089F@DAPHNIS.office.hd>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
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.6.25.220919
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/4mY1xRfV8JhvqygCekHXP50V4cQ
Subject: Re: [pcp] New Version Notification for draft-ripke-pcp-tunnel-id-option-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: Wed, 09 Jul 2014 08:42:33 -0000

Hi Andreas,

Thank you for sharing this updated version of the document.=20

I'm not sure about the carrier-hosted IWF because one of the motivations fo=
r PCP to avoid overloading the carrier network with a chatty protocol.=20

FWIW, I have identified in this document as case that require an identifica=
tion information that cannot be included in a THIRD_PARTY option:
http://tools.ietf.org/html/draft-boucadair-pcp-sfc-classifier-control-00=20
"   o  Extended THIRD_PARTY option to include a L2 identifier (e.g., MAC
      address), an opaque subscriber-identifier, an IMSI, etc."

I suggest you change TUNNEL_ID to something that won't mislead the reader t=
hat a tunneling technique is always in place when this option is in use.

Cheers,
Med

>-----Message d'origine-----
>De=A0: pcp [mailto:pcp-bounces@ietf.org] De la part de Andreas Ripke
>Envoy=E9=A0: vendredi 4 juillet 2014 13:05
>=C0=A0: pcp@ietf.org
>Objet=A0: [pcp] FW: New Version Notification for draft-ripke-pcp-tunnel-id=
-
>option-01.txt
>
>Dear all,
>
>Thank you for all the feedback we received at the last meeting on the
>TUNNEL_ID option. This was very helpful. We have updated our draft
>accordingly and aligned our use case with use cases from existing PCP
>drafts/RFCs. Particularly we moved the focus from a rather static web
>portal scenario to a more dynamic UPnP Interworking scenario.
>
>http://www.ietf.org/internet-drafts/draft-ripke-pcp-tunnel-id-option-01.tx=
t
>
>Please have a look at the draft and give us your feedback.
>
>Best regards,
>
>Andreas
>
>
>NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park, West En=
d
>Road, London, HA4 6QE, GB | Registered in England 2832014
>
>
>
>
>
>
>A new version of I-D, draft-ripke-pcp-tunnel-id-option-01.txt
>has been successfully submitted by Andreas Ripke and posted to the IETF
>repository.
>
>Name:		draft-ripke-pcp-tunnel-id-option
>Revision:	01
>Title:		PCP Tunnel-ID Option
>Document date:	2014-07-03
>Group:		Individual Submission
>Pages:		10
>URL:            http://www.ietf.org/internet-drafts/draft-ripke-pcp-tunnel=
-
>id-option-01.txt
>Status:         https://datatracker.ietf.org/doc/draft-ripke-pcp-tunnel-id=
-
>option/
>Htmlized:       http://tools.ietf.org/html/draft-ripke-pcp-tunnel-id-
>option-01
>Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ripke-pcp-tunnel-=
id-
>option-01
>
>Abstract:
>   This document describes a new Port Control Protocol (PCP) option
>   called TUNNEL_ID.  It serves for identifying a Third Party in
>   addition to the means that PCP's THIRD_PARTY option already provides
>   for that purpose.
>
>
>
>
>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 nobody Wed Jul  9 03:02:55 2014
Return-Path: <Andreas.Ripke@neclab.eu>
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 AD90B1A03DE for <pcp@ietfa.amsl.com>; Wed,  9 Jul 2014 03:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.253
X-Spam-Level: 
X-Spam-Status: No, score=-3.253 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, 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 gAfN9fi4cdIW for <pcp@ietfa.amsl.com>; Wed,  9 Jul 2014 03:02:48 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A8231A03DB for <pcp@ietf.org>; Wed,  9 Jul 2014 03:02:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id AB3D510008A; Wed,  9 Jul 2014 12:02:46 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C_8w6D6AQR9J; Wed,  9 Jul 2014 12:02:46 +0200 (CEST)
X-ENC: Last-Hop-TLS-encrypted
X-ENC: Last-Hop-TLS-encrypted
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 8B3BAFFF49; Wed,  9 Jul 2014 12:02:36 +0200 (CEST)
Received: from HYDRA.office.hd ([169.254.4.11]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Wed, 9 Jul 2014 12:02:30 +0200
From: Andreas Ripke <Andreas.Ripke@neclab.eu>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Version Notification for draft-ripke-pcp-tunnel-id-option-01.txt
Thread-Index: AQHPl3Ond1s//Hsjp0CcLYDTq0HzY5uPv3hAgAezYcCAAA2OgA==
Date: Wed, 9 Jul 2014 10:02:23 +0000
Message-ID: <2D2FFE4726FAF74285C45D69FDC30E798D602C81@Hydra.office.hd>
References: <20140704103500.20587.59638.idtracker@ietfa.amsl.com> <2D2FFE4726FAF74285C45D69FDC30E798D60089F@DAPHNIS.office.hd> <787AE7BB302AE849A7480A190F8B933002F541@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933002F541@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.6.215]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/NOnADyYcltoRTYHD4xguzkTD4ws
Subject: Re: [pcp] New Version Notification for draft-ripke-pcp-tunnel-id-option-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: Wed, 09 Jul 2014 10:02:52 -0000

Hi Med,

Thanks for your comments.

Our scenario is a supplement to situations when PCP is not yet on hand in t=
he subscriber realm.
The carrier IWF is offered as a service to the subscribers.
It does not prevent subscribers to directly use PCP to control ports on the=
 CGN.

And thanks for your pointer to your pcp-sfc draft.
It looks like the PCP TUNNEL_ID option aligns to this direction of an exten=
sion proposal.

The decision we called the new option TUNNEL_ID was driven by the given sce=
nario.
Yes, it might be an idea to change and generalize the option name to ID ins=
tead of TUNNEL_ID.

Best,

Andreas

> -----Original Message-----
> From: mohamed.boucadair@orange.com
> [mailto:mohamed.boucadair@orange.com]
> Sent: Wednesday, July 09, 2014 10:42 AM
> To: Andreas Ripke; pcp@ietf.org
> Subject: RE: New Version Notification for draft-ripke-pcp-tunnel-id-optio=
n-
> 01.txt
>=20
> Hi Andreas,
>=20
> Thank you for sharing this updated version of the document.
>=20
> I'm not sure about the carrier-hosted IWF because one of the motivations
> for PCP to avoid overloading the carrier network with a chatty protocol.
>=20
> FWIW, I have identified in this document as case that require an
> identification information that cannot be included in a THIRD_PARTY optio=
n:
> http://tools.ietf.org/html/draft-boucadair-pcp-sfc-classifier-control-00
> "   o  Extended THIRD_PARTY option to include a L2 identifier (e.g., MAC
>       address), an opaque subscriber-identifier, an IMSI, etc."
>=20
> I suggest you change TUNNEL_ID to something that won't mislead the
> reader that a tunneling technique is always in place when this option is =
in
> use.
>=20
> Cheers,
> Med
>=20
> >-----Message d'origine-----
> >De=A0: pcp [mailto:pcp-bounces@ietf.org] De la part de Andreas Ripke
> >Envoy=E9=A0: vendredi 4 juillet 2014 13:05 =C0=A0: pcp@ietf.org Objet=A0=
: [pcp]
> >FW: New Version Notification for draft-ripke-pcp-tunnel-id-
> >option-01.txt
> >
> >Dear all,
> >
> >Thank you for all the feedback we received at the last meeting on the
> >TUNNEL_ID option. This was very helpful. We have updated our draft
> >accordingly and aligned our use case with use cases from existing PCP
> >drafts/RFCs. Particularly we moved the focus from a rather static web
> >portal scenario to a more dynamic UPnP Interworking scenario.
> >
> >http://www.ietf.org/internet-drafts/draft-ripke-pcp-tunnel-id-option-01
> >.txt
> >
> >Please have a look at the draft and give us your feedback.
> >
> >Best regards,
> >
> >Andreas
> >
> >
> >NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park, West
> >End Road, London, HA4 6QE, GB | Registered in England 2832014
> >
> >
> >
> >
> >
> >
> >A new version of I-D, draft-ripke-pcp-tunnel-id-option-01.txt
> >has been successfully submitted by Andreas Ripke and posted to the IETF
> >repository.
> >
> >Name:		draft-ripke-pcp-tunnel-id-option
> >Revision:	01
> >Title:		PCP Tunnel-ID Option
> >Document date:	2014-07-03
> >Group:		Individual Submission
> >Pages:		10
> >URL:            http://www.ietf.org/internet-drafts/draft-ripke-pcp-tunn=
el-
> >id-option-01.txt
> >Status:         https://datatracker.ietf.org/doc/draft-ripke-pcp-tunnel-=
id-
> >option/
> >Htmlized:       http://tools.ietf.org/html/draft-ripke-pcp-tunnel-id-
> >option-01
> >Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ripke-pcp-tunne=
l-id-
> >option-01
> >
> >Abstract:
> >   This document describes a new Port Control Protocol (PCP) option
> >   called TUNNEL_ID.  It serves for identifying a Third Party in
> >   addition to the means that PCP's THIRD_PARTY option already provides
> >   for that purpose.
> >
> >
> >
> >
> >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 nobody Wed Jul  9 07:27:27 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 B4DEB1A0AB8 for <pcp@ietfa.amsl.com>; Wed,  9 Jul 2014 07:27:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 iV4OFPiAS_Y6 for <pcp@ietfa.amsl.com>; Wed,  9 Jul 2014 07:27:13 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A611C1A0ABE for <pcp@ietf.org>; Wed,  9 Jul 2014 07:27:12 -0700 (PDT)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda14.si.francetelecom.fr (ESMTP service) with ESMTP id 51D1D2AC685; Wed,  9 Jul 2014 16:27:10 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.56]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id 32795C8061; Wed,  9 Jul 2014 16:27:10 +0200 (CEST)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.67]) by OPEXCLILH04.corporate.adroot.infra.ftgroup ([10.114.31.56]) with mapi id 14.03.0181.006; Wed, 9 Jul 2014 16:27:10 +0200
From: <mohamed.boucadair@orange.com>
To: Andreas Ripke <Andreas.Ripke@neclab.eu>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Version Notification for draft-ripke-pcp-tunnel-id-option-01.txt
Thread-Index: AQHPl3Ond1s//Hsjp0CcLYDTq0HzY5uPv3hAgAezYcCAAA2OgIAAU4rg
Date: Wed, 9 Jul 2014 14:27:09 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933002F965@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <20140704103500.20587.59638.idtracker@ietfa.amsl.com> <2D2FFE4726FAF74285C45D69FDC30E798D60089F@DAPHNIS.office.hd> <787AE7BB302AE849A7480A190F8B933002F541@OPEXCLILM23.corporate.adroot.infra.ftgroup> <2D2FFE4726FAF74285C45D69FDC30E798D602C81@Hydra.office.hd>
In-Reply-To: <2D2FFE4726FAF74285C45D69FDC30E798D602C81@Hydra.office.hd>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
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.7.9.34819
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/KZwpQPCUp9w6Q1THaqQji6VdBnA
Subject: Re: [pcp] New Version Notification for draft-ripke-pcp-tunnel-id-option-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: Wed, 09 Jul 2014 14:27:16 -0000

Re-,

Please see inline.

Cheers,
Med

>-----Message d'origine-----
>De=A0: Andreas Ripke [mailto:Andreas.Ripke@neclab.eu]
>Envoy=E9=A0: mercredi 9 juillet 2014 12:02
>=C0=A0: BOUCADAIR Mohamed IMT/OLN; pcp@ietf.org
>Objet=A0: RE: New Version Notification for draft-ripke-pcp-tunnel-id-optio=
n-
>01.txt
>
>Hi Med,
>
>Thanks for your comments.
>
>Our scenario is a supplement to situations when PCP is not yet on hand in
>the subscriber realm.
>The carrier IWF is offered as a service to the subscribers.
>It does not prevent subscribers to directly use PCP to control ports on th=
e
>CGN.

[Med] But how the CPE will decide to leak UPnP IGD outside the LAN? Shouldn=
't this require an upgrade of the CPE to support some "kind" of UPnP IGD re=
lay?=20

>
>And thanks for your pointer to your pcp-sfc draft.
>It looks like the PCP TUNNEL_ID option aligns to this direction of an
>extension proposal.
>
>The decision we called the new option TUNNEL_ID was driven by the given
>scenario.
>Yes, it might be an idea to change and generalize the option name to ID
>instead of TUNNEL_ID.

[Med] Great!=20

>
>Best,
>
>Andreas
>
>> -----Original Message-----
>> From: mohamed.boucadair@orange.com
>> [mailto:mohamed.boucadair@orange.com]
>> Sent: Wednesday, July 09, 2014 10:42 AM
>> To: Andreas Ripke; pcp@ietf.org
>> Subject: RE: New Version Notification for draft-ripke-pcp-tunnel-id-
>option-
>> 01.txt
>>
>> Hi Andreas,
>>
>> Thank you for sharing this updated version of the document.
>>
>> I'm not sure about the carrier-hosted IWF because one of the motivations
>> for PCP to avoid overloading the carrier network with a chatty protocol.
>>
>> FWIW, I have identified in this document as case that require an
>> identification information that cannot be included in a THIRD_PARTY
>option:
>> http://tools.ietf.org/html/draft-boucadair-pcp-sfc-classifier-control-00
>> "   o  Extended THIRD_PARTY option to include a L2 identifier (e.g., MAC
>>       address), an opaque subscriber-identifier, an IMSI, etc."
>>
>> I suggest you change TUNNEL_ID to something that won't mislead the
>> reader that a tunneling technique is always in place when this option is
>in
>> use.
>>
>> Cheers,
>> Med
>>
>> >-----Message d'origine-----
>> >De=A0: pcp [mailto:pcp-bounces@ietf.org] De la part de Andreas Ripke
>> >Envoy=E9=A0: vendredi 4 juillet 2014 13:05 =C0=A0: pcp@ietf.org Objet=
=A0: [pcp]
>> >FW: New Version Notification for draft-ripke-pcp-tunnel-id-
>> >option-01.txt
>> >
>> >Dear all,
>> >
>> >Thank you for all the feedback we received at the last meeting on the
>> >TUNNEL_ID option. This was very helpful. We have updated our draft
>> >accordingly and aligned our use case with use cases from existing PCP
>> >drafts/RFCs. Particularly we moved the focus from a rather static web
>> >portal scenario to a more dynamic UPnP Interworking scenario.
>> >
>> >http://www.ietf.org/internet-drafts/draft-ripke-pcp-tunnel-id-option-01
>> >.txt
>> >
>> >Please have a look at the draft and give us your feedback.
>> >
>> >Best regards,
>> >
>> >Andreas
>> >
>> >
>> >NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park, West
>> >End Road, London, HA4 6QE, GB | Registered in England 2832014
>> >
>> >
>> >
>> >
>> >
>> >
>> >A new version of I-D, draft-ripke-pcp-tunnel-id-option-01.txt
>> >has been successfully submitted by Andreas Ripke and posted to the IETF
>> >repository.
>> >
>> >Name:		draft-ripke-pcp-tunnel-id-option
>> >Revision:	01
>> >Title:		PCP Tunnel-ID Option
>> >Document date:	2014-07-03
>> >Group:		Individual Submission
>> >Pages:		10
>> >URL:            http://www.ietf.org/internet-drafts/draft-ripke-pcp-
>tunnel-
>> >id-option-01.txt
>> >Status:         https://datatracker.ietf.org/doc/draft-ripke-pcp-tunnel=
-
>id-
>> >option/
>> >Htmlized:       http://tools.ietf.org/html/draft-ripke-pcp-tunnel-id-
>> >option-01
>> >Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ripke-pcp-tunn=
el-
>id-
>> >option-01
>> >
>> >Abstract:
>> >   This document describes a new Port Control Protocol (PCP) option
>> >   called TUNNEL_ID.  It serves for identifying a Third Party in
>> >   addition to the means that PCP's THIRD_PARTY option already provides
>> >   for that purpose.
>> >
>> >
>> >
>> >
>> >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 nobody Fri Jul 11 07:42:16 2014
Return-Path: <Andreas.Ripke@neclab.eu>
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 D73871B2B34 for <pcp@ietfa.amsl.com>; Fri, 11 Jul 2014 07:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.253
X-Spam-Level: 
X-Spam-Status: No, score=-3.253 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, 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 OOVkzajveX8d for <pcp@ietfa.amsl.com>; Fri, 11 Jul 2014 07:42:11 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C73521B2B17 for <pcp@ietf.org>; Fri, 11 Jul 2014 07:42:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 3D8DB1002A3; Fri, 11 Jul 2014 16:42:09 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8U6hZfD1MrfV; Fri, 11 Jul 2014 16:42:09 +0200 (CEST)
X-ENC: Last-Hop-TLS-encrypted
X-ENC: Last-Hop-TLS-encrypted
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 13EBE100297; Fri, 11 Jul 2014 16:41:59 +0200 (CEST)
Received: from HYDRA.office.hd ([169.254.4.11]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Fri, 11 Jul 2014 16:41:58 +0200
From: Andreas Ripke <Andreas.Ripke@neclab.eu>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Version Notification for draft-ripke-pcp-tunnel-id-option-01.txt
Thread-Index: AQHPl3Ond1s//Hsjp0CcLYDTq0HzY5uPv3hAgAezYcCAAA2OgIAAU4rggAMmp6A=
Date: Fri, 11 Jul 2014 14:41:57 +0000
Message-ID: <2D2FFE4726FAF74285C45D69FDC30E798D607FF9@Hydra.office.hd>
References: <20140704103500.20587.59638.idtracker@ietfa.amsl.com> <2D2FFE4726FAF74285C45D69FDC30E798D60089F@DAPHNIS.office.hd> <787AE7BB302AE849A7480A190F8B933002F541@OPEXCLILM23.corporate.adroot.infra.ftgroup> <2D2FFE4726FAF74285C45D69FDC30E798D602C81@Hydra.office.hd> <787AE7BB302AE849A7480A190F8B933002F965@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933002F965@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.6.215]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/aRoXUtyTRhzxfI4TbZFkmWAR2_I
Subject: Re: [pcp] New Version Notification for draft-ripke-pcp-tunnel-id-option-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: Fri, 11 Jul 2014 14:42:14 -0000

Hi Med,

Thanks for the hint on UPnP relay. This might not be necessary.
Apparently, we have to describe the scenario in more detail.

Best,

Andreas

> -----Original Message-----
> From: mohamed.boucadair@orange.com
> [mailto:mohamed.boucadair@orange.com]
> Sent: Wednesday, July 09, 2014 4:27 PM
> To: Andreas Ripke; pcp@ietf.org
> Subject: RE: New Version Notification for draft-ripke-pcp-tunnel-id-optio=
n-
> 01.txt
>=20
> Re-,
>=20
> Please see inline.
>=20
> Cheers,
> Med
>=20
> >-----Message d'origine-----
> >De=A0: Andreas Ripke [mailto:Andreas.Ripke@neclab.eu] Envoy=E9=A0: mercr=
edi 9
> >juillet 2014 12:02 =C0=A0: BOUCADAIR Mohamed IMT/OLN; pcp@ietf.org Objet=
=A0:
> >RE: New Version Notification for draft-ripke-pcp-tunnel-id-option-
> >01.txt
> >
> >Hi Med,
> >
> >Thanks for your comments.
> >
> >Our scenario is a supplement to situations when PCP is not yet on hand
> >in the subscriber realm.
> >The carrier IWF is offered as a service to the subscribers.
> >It does not prevent subscribers to directly use PCP to control ports on
> >the CGN.
>=20
> [Med] But how the CPE will decide to leak UPnP IGD outside the LAN?
> Shouldn't this require an upgrade of the CPE to support some "kind" of UP=
nP
> IGD relay?
>=20
> >
> >And thanks for your pointer to your pcp-sfc draft.
> >It looks like the PCP TUNNEL_ID option aligns to this direction of an
> >extension proposal.
> >
> >The decision we called the new option TUNNEL_ID was driven by the given
> >scenario.
> >Yes, it might be an idea to change and generalize the option name to ID
> >instead of TUNNEL_ID.
>=20
> [Med] Great!
>=20
> >
> >Best,
> >
> >Andreas
> >
> >> -----Original Message-----
> >> From: mohamed.boucadair@orange.com
> >> [mailto:mohamed.boucadair@orange.com]
> >> Sent: Wednesday, July 09, 2014 10:42 AM
> >> To: Andreas Ripke; pcp@ietf.org
> >> Subject: RE: New Version Notification for draft-ripke-pcp-tunnel-id-
> >option-
> >> 01.txt
> >>
> >> Hi Andreas,
> >>
> >> Thank you for sharing this updated version of the document.
> >>
> >> I'm not sure about the carrier-hosted IWF because one of the
> >> motivations for PCP to avoid overloading the carrier network with a
> chatty protocol.
> >>
> >> FWIW, I have identified in this document as case that require an
> >> identification information that cannot be included in a THIRD_PARTY
> >option:
> >> http://tools.ietf.org/html/draft-boucadair-pcp-sfc-classifier-control-=
00
> >> "   o  Extended THIRD_PARTY option to include a L2 identifier (e.g., M=
AC
> >>       address), an opaque subscriber-identifier, an IMSI, etc."
> >>
> >> I suggest you change TUNNEL_ID to something that won't mislead the
> >> reader that a tunneling technique is always in place when this option
> >> is
> >in
> >> use.
> >>
> >> Cheers,
> >> Med
> >>
> >> >-----Message d'origine-----
> >> >De=A0: pcp [mailto:pcp-bounces@ietf.org] De la part de Andreas Ripke
> >> >Envoy=E9=A0: vendredi 4 juillet 2014 13:05 =C0=A0: pcp@ietf.org Objet=
=A0:
> >> >[pcp]
> >> >FW: New Version Notification for draft-ripke-pcp-tunnel-id-
> >> >option-01.txt
> >> >
> >> >Dear all,
> >> >
> >> >Thank you for all the feedback we received at the last meeting on
> >> >the TUNNEL_ID option. This was very helpful. We have updated our
> >> >draft accordingly and aligned our use case with use cases from
> >> >existing PCP drafts/RFCs. Particularly we moved the focus from a
> >> >rather static web portal scenario to a more dynamic UPnP Interworking
> scenario.
> >> >
> >> >http://www.ietf.org/internet-drafts/draft-ripke-pcp-tunnel-id-option
> >> >-01
> >> >.txt
> >> >
> >> >Please have a look at the draft and give us your feedback.
> >> >
> >> >Best regards,
> >> >
> >> >Andreas
> >> >
> >> >
> >> >NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park,
> >> >West End Road, London, HA4 6QE, GB | Registered in England 2832014
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >A new version of I-D, draft-ripke-pcp-tunnel-id-option-01.txt
> >> >has been successfully submitted by Andreas Ripke and posted to the
> >> >IETF repository.
> >> >
> >> >Name:		draft-ripke-pcp-tunnel-id-option
> >> >Revision:	01
> >> >Title:		PCP Tunnel-ID Option
> >> >Document date:	2014-07-03
> >> >Group:		Individual Submission
> >> >Pages:		10
> >> >URL:            http://www.ietf.org/internet-drafts/draft-ripke-pcp-
> >tunnel-
> >> >id-option-01.txt
> >> >Status:         https://datatracker.ietf.org/doc/draft-ripke-pcp-tunn=
el-
> >id-
> >> >option/
> >> >Htmlized:       http://tools.ietf.org/html/draft-ripke-pcp-tunnel-id-
> >> >option-01
> >> >Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ripke-pcp-tu=
nnel-
> >id-
> >> >option-01
> >> >
> >> >Abstract:
> >> >   This document describes a new Port Control Protocol (PCP) option
> >> >   called TUNNEL_ID.  It serves for identifying a Third Party in
> >> >   addition to the means that PCP's THIRD_PARTY option already provid=
es
> >> >   for that purpose.
> >> >
> >> >
> >> >
> >> >
> >> >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 nobody Fri Jul 11 07:45:34 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 9B1CF1B2908 for <pcp@ietfa.amsl.com>; Fri, 11 Jul 2014 07:45:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 O_NjsA74gIR0 for <pcp@ietfa.amsl.com>; Fri, 11 Jul 2014 07:45:30 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02EB01B28F6 for <pcp@ietf.org>; Fri, 11 Jul 2014 07:45:30 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 758BD324236; Fri, 11 Jul 2014 16:45:28 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.55]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 56DA135C05A; Fri, 11 Jul 2014 16:45:28 +0200 (CEST)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.67]) by OPEXCLILH03.corporate.adroot.infra.ftgroup ([10.114.31.55]) with mapi id 14.03.0181.006; Fri, 11 Jul 2014 16:45:28 +0200
From: <mohamed.boucadair@orange.com>
To: Andreas Ripke <Andreas.Ripke@neclab.eu>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Version Notification for draft-ripke-pcp-tunnel-id-option-01.txt
Thread-Index: AQHPl3Ond1s//Hsjp0CcLYDTq0HzY5uPv3hAgAezYcCAAA2OgIAAU4rggAMmp6CAAAPKEA==
Date: Fri, 11 Jul 2014 14:45:27 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933003175D@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <20140704103500.20587.59638.idtracker@ietfa.amsl.com> <2D2FFE4726FAF74285C45D69FDC30E798D60089F@DAPHNIS.office.hd> <787AE7BB302AE849A7480A190F8B933002F541@OPEXCLILM23.corporate.adroot.infra.ftgroup> <2D2FFE4726FAF74285C45D69FDC30E798D602C81@Hydra.office.hd> <787AE7BB302AE849A7480A190F8B933002F965@OPEXCLILM23.corporate.adroot.infra.ftgroup> <2D2FFE4726FAF74285C45D69FDC30E798D607FF9@Hydra.office.hd>
In-Reply-To: <2D2FFE4726FAF74285C45D69FDC30E798D607FF9@Hydra.office.hd>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
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.6.25.81224
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/F7fgh5TnhM6KM0m9_n-YWftheQE
Subject: Re: [pcp] New Version Notification for draft-ripke-pcp-tunnel-id-option-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: Fri, 11 Jul 2014 14:45:32 -0000

Hi Andreas,

I'm curious to see how this can work with legacy CPEs.

Looking forward to reading an updated version of the draft.

Cheers,
Med

>-----Message d'origine-----
>De=A0: Andreas Ripke [mailto:Andreas.Ripke@neclab.eu]
>Envoy=E9=A0: vendredi 11 juillet 2014 16:42
>=C0=A0: BOUCADAIR Mohamed IMT/OLN; pcp@ietf.org
>Objet=A0: RE: New Version Notification for draft-ripke-pcp-tunnel-id-optio=
n-
>01.txt
>
>Hi Med,
>
>Thanks for the hint on UPnP relay. This might not be necessary.
>Apparently, we have to describe the scenario in more detail.
>
>Best,
>
>Andreas
>
>> -----Original Message-----
>> From: mohamed.boucadair@orange.com
>> [mailto:mohamed.boucadair@orange.com]
>> Sent: Wednesday, July 09, 2014 4:27 PM
>> To: Andreas Ripke; pcp@ietf.org
>> Subject: RE: New Version Notification for draft-ripke-pcp-tunnel-id-
>option-
>> 01.txt
>>
>> Re-,
>>
>> Please see inline.
>>
>> Cheers,
>> Med
>>
>> >-----Message d'origine-----
>> >De=A0: Andreas Ripke [mailto:Andreas.Ripke@neclab.eu] Envoy=E9=A0: merc=
redi 9
>> >juillet 2014 12:02 =C0=A0: BOUCADAIR Mohamed IMT/OLN; pcp@ietf.org Obje=
t=A0:
>> >RE: New Version Notification for draft-ripke-pcp-tunnel-id-option-
>> >01.txt
>> >
>> >Hi Med,
>> >
>> >Thanks for your comments.
>> >
>> >Our scenario is a supplement to situations when PCP is not yet on hand
>> >in the subscriber realm.
>> >The carrier IWF is offered as a service to the subscribers.
>> >It does not prevent subscribers to directly use PCP to control ports on
>> >the CGN.
>>
>> [Med] But how the CPE will decide to leak UPnP IGD outside the LAN?
>> Shouldn't this require an upgrade of the CPE to support some "kind" of
>UPnP
>> IGD relay?
>>
>> >
>> >And thanks for your pointer to your pcp-sfc draft.
>> >It looks like the PCP TUNNEL_ID option aligns to this direction of an
>> >extension proposal.
>> >
>> >The decision we called the new option TUNNEL_ID was driven by the given
>> >scenario.
>> >Yes, it might be an idea to change and generalize the option name to ID
>> >instead of TUNNEL_ID.
>>
>> [Med] Great!
>>
>> >
>> >Best,
>> >
>> >Andreas
>> >
>> >> -----Original Message-----
>> >> From: mohamed.boucadair@orange.com
>> >> [mailto:mohamed.boucadair@orange.com]
>> >> Sent: Wednesday, July 09, 2014 10:42 AM
>> >> To: Andreas Ripke; pcp@ietf.org
>> >> Subject: RE: New Version Notification for draft-ripke-pcp-tunnel-id-
>> >option-
>> >> 01.txt
>> >>
>> >> Hi Andreas,
>> >>
>> >> Thank you for sharing this updated version of the document.
>> >>
>> >> I'm not sure about the carrier-hosted IWF because one of the
>> >> motivations for PCP to avoid overloading the carrier network with a
>> chatty protocol.
>> >>
>> >> FWIW, I have identified in this document as case that require an
>> >> identification information that cannot be included in a THIRD_PARTY
>> >option:
>> >> http://tools.ietf.org/html/draft-boucadair-pcp-sfc-classifier-control=
-
>00
>> >> "   o  Extended THIRD_PARTY option to include a L2 identifier (e.g.,
>MAC
>> >>       address), an opaque subscriber-identifier, an IMSI, etc."
>> >>
>> >> I suggest you change TUNNEL_ID to something that won't mislead the
>> >> reader that a tunneling technique is always in place when this option
>> >> is
>> >in
>> >> use.
>> >>
>> >> Cheers,
>> >> Med
>> >>
>> >> >-----Message d'origine-----
>> >> >De=A0: pcp [mailto:pcp-bounces@ietf.org] De la part de Andreas Ripke
>> >> >Envoy=E9=A0: vendredi 4 juillet 2014 13:05 =C0=A0: pcp@ietf.org Obje=
t=A0:
>> >> >[pcp]
>> >> >FW: New Version Notification for draft-ripke-pcp-tunnel-id-
>> >> >option-01.txt
>> >> >
>> >> >Dear all,
>> >> >
>> >> >Thank you for all the feedback we received at the last meeting on
>> >> >the TUNNEL_ID option. This was very helpful. We have updated our
>> >> >draft accordingly and aligned our use case with use cases from
>> >> >existing PCP drafts/RFCs. Particularly we moved the focus from a
>> >> >rather static web portal scenario to a more dynamic UPnP Interworkin=
g
>> scenario.
>> >> >
>> >> >http://www.ietf.org/internet-drafts/draft-ripke-pcp-tunnel-id-option
>> >> >-01
>> >> >.txt
>> >> >
>> >> >Please have a look at the draft and give us your feedback.
>> >> >
>> >> >Best regards,
>> >> >
>> >> >Andreas
>> >> >
>> >> >
>> >> >NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park,
>> >> >West End Road, London, HA4 6QE, GB | Registered in England 2832014
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >A new version of I-D, draft-ripke-pcp-tunnel-id-option-01.txt
>> >> >has been successfully submitted by Andreas Ripke and posted to the
>> >> >IETF repository.
>> >> >
>> >> >Name:		draft-ripke-pcp-tunnel-id-option
>> >> >Revision:	01
>> >> >Title:		PCP Tunnel-ID Option
>> >> >Document date:	2014-07-03
>> >> >Group:		Individual Submission
>> >> >Pages:		10
>> >> >URL:            http://www.ietf.org/internet-drafts/draft-ripke-pcp-
>> >tunnel-
>> >> >id-option-01.txt
>> >> >Status:         https://datatracker.ietf.org/doc/draft-ripke-pcp-
>tunnel-
>> >id-
>> >> >option/
>> >> >Htmlized:       http://tools.ietf.org/html/draft-ripke-pcp-tunnel-id=
-
>> >> >option-01
>> >> >Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ripke-pcp-
>tunnel-
>> >id-
>> >> >option-01
>> >> >
>> >> >Abstract:
>> >> >   This document describes a new Port Control Protocol (PCP) option
>> >> >   called TUNNEL_ID.  It serves for identifying a Third Party in
>> >> >   addition to the means that PCP's THIRD_PARTY option already
>provides
>> >> >   for that purpose.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >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 rafaelalejandro.lopezdasilva@telefonica.com  Fri Jul 11 08:00:46 2014
Return-Path: <rafaelalejandro.lopezdasilva@telefonica.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 606FC1B2B6E for <pcp@ietfa.amsl.com>; Fri, 11 Jul 2014 08:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 f3ZaaGYGseKL for <pcp@ietfa.amsl.com>; Fri, 11 Jul 2014 08:00:38 -0700 (PDT)
Received: from smtpjc.telefonica.com (smtpjc.telefonica.com [81.47.204.76]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2E0C1B2B93 for <pcp@ietf.org>; Fri, 11 Jul 2014 08:00:28 -0700 (PDT)
Received: from smtpjc.telefonica.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7D2792F016D; Fri, 11 Jul 2014 17:00:22 +0200 (CEST)
Received: from ESTGVMSP110.EUROPE.telefonica.corp (unknown [10.92.4.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtpjc.telefonica.com (Postfix) with ESMTPS id 07B602F0156; Fri, 11 Jul 2014 17:00:22 +0200 (CEST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (10.92.5.139) by tls.telefonica.com (10.93.6.53) with Microsoft SMTP Server (TLS) id 14.3.146.2; Fri, 11 Jul 2014 17:00:21 +0200
Received: from AM3PR06MB051.eurprd06.prod.outlook.com (10.242.242.154) by AM3PR06MB051.eurprd06.prod.outlook.com (10.242.242.154) with Microsoft SMTP Server (TLS) id 15.0.980.8; Fri, 11 Jul 2014 15:00:19 +0000
Received: from AM3PR06MB051.eurprd06.prod.outlook.com ([169.254.7.144]) by AM3PR06MB051.eurprd06.prod.outlook.com ([169.254.7.144]) with mapi id 15.00.0980.000; Fri, 11 Jul 2014 15:00:19 +0000
From: RAFAEL ALEJANDRO LOPEZ DA SILVA <rafaelalejandro.lopezdasilva@telefonica.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "Andreas Ripke" <Andreas.Ripke@neclab.eu>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Version Notification for draft-ripke-pcp-tunnel-id-option-01.txt
Thread-Index: AQHPl3Ond1s//Hsjp0CcLYDTq0HzY5uPv3hAgAezYcCAAA2OgIAAU4rggAMmp6CAAAPKEIAAAUqA
Date: Fri, 11 Jul 2014 15:00:18 +0000
Message-ID: <03602cb0aef34faa9efca9d623003235@AM3PR06MB051.eurprd06.prod.outlook.com>
References: <20140704103500.20587.59638.idtracker@ietfa.amsl.com> <2D2FFE4726FAF74285C45D69FDC30E798D60089F@DAPHNIS.office.hd> <787AE7BB302AE849A7480A190F8B933002F541@OPEXCLILM23.corporate.adroot.infra.ftgroup> <2D2FFE4726FAF74285C45D69FDC30E798D602C81@Hydra.office.hd> <787AE7BB302AE849A7480A190F8B933002F965@OPEXCLILM23.corporate.adroot.infra.ftgroup> <2D2FFE4726FAF74285C45D69FDC30E798D607FF9@Hydra.office.hd> <787AE7BB302AE849A7480A190F8B933003175D@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933003175D@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: es-ES
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [195.235.92.27]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 02698DF457
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(189002)(51914003)(377424004)(13464003)(51704005)(55784002)(199002)(377454003)(74502001)(85306003)(54356999)(15202345003)(77982001)(85852003)(87936001)(46102001)(77096002)(4396001)(107046002)(92566001)(76176999)(101416001)(15975445006)(107886001)(74662001)(105586002)(106356001)(93886003)(2656002)(80022001)(21056001)(33646001)(86362001)(99396002)(81342001)(76576001)(81542001)(106116001)(31966008)(79102001)(20776003)(95666004)(83072002)(19580405001)(19580395003)(50986999)(561944003)(83322001)(64706001)(76482001)(66066001)(74316001)(108616002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:AM3PR06MB051; H:AM3PR06MB051.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en; 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: telefonica.com
X-TM-AS-MML: No
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/P9yYkdgbubQDd051xB-SAiJvy28
Subject: Re: [pcp] New Version Notification for draft-ripke-pcp-tunnel-id-option-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: Fri, 11 Jul 2014 15:02:55 -0000

Hi Med:

Thank you for your suggestions, and as Andreas says we will have to describ=
e better the scenario in a next version.

Just as an advance though on the options for the UPnP IGD-PCP IWF. Some ope=
rators are deploying layer 2 CPEs, while moving some layer 3 CPE functional=
ities to the network. With that you are extending the Layer 2 domain of the=
 Home LAN into the ISP network. One of the Layer 3 CPE functionalities shif=
ted to the network could be the UPnP IGD to PCP IWF, for allowing devices w=
ithout PCP support request dynamic mappings to a CGN. To achieve scalabilit=
y this IWF could be located off-path (even though with Layer 2 visibility o=
f the Home devices) and use a mediation system to signal the mappings to th=
e CGN on its behalf using the Tunnel Id option.

That is achievable with legacy CPEs in bridge mode.

Best
Rafael L=F3pez da Silva


-----Mensaje original-----
De: pcp [mailto:pcp-bounces@ietf.org] En nombre de mohamed.boucadair@orange=
.com
Enviado el: viernes, 11 de julio de 2014 16:45
Para: Andreas Ripke; pcp@ietf.org
Asunto: Re: [pcp] New Version Notification for draft-ripke-pcp-tunnel-id-op=
tion-01.txt

Hi Andreas,

I'm curious to see how this can work with legacy CPEs.

Looking forward to reading an updated version of the draft.

Cheers,
Med

>-----Message d'origine-----
>De : Andreas Ripke [mailto:Andreas.Ripke@neclab.eu] Envoy=E9 : vendredi
>11 juillet 2014 16:42 =C0 : BOUCADAIR Mohamed IMT/OLN; pcp@ietf.org Objet
>: RE: New Version Notification for draft-ripke-pcp-tunnel-id-option-
>01.txt
>
>Hi Med,
>
>Thanks for the hint on UPnP relay. This might not be necessary.
>Apparently, we have to describe the scenario in more detail.
>
>Best,
>
>Andreas
>
>> -----Original Message-----
>> From: mohamed.boucadair@orange.com
>> [mailto:mohamed.boucadair@orange.com]
>> Sent: Wednesday, July 09, 2014 4:27 PM
>> To: Andreas Ripke; pcp@ietf.org
>> Subject: RE: New Version Notification for draft-ripke-pcp-tunnel-id-
>option-
>> 01.txt
>>
>> Re-,
>>
>> Please see inline.
>>
>> Cheers,
>> Med
>>
>> >-----Message d'origine-----
>> >De : Andreas Ripke [mailto:Andreas.Ripke@neclab.eu] Envoy=E9 :
>> >mercredi 9 juillet 2014 12:02 =C0 : BOUCADAIR Mohamed IMT/OLN; pcp@ietf=
.org Objet :
>> >RE: New Version Notification for draft-ripke-pcp-tunnel-id-option-
>> >01.txt
>> >
>> >Hi Med,
>> >
>> >Thanks for your comments.
>> >
>> >Our scenario is a supplement to situations when PCP is not yet on
>> >hand in the subscriber realm.
>> >The carrier IWF is offered as a service to the subscribers.
>> >It does not prevent subscribers to directly use PCP to control ports
>> >on the CGN.
>>
>> [Med] But how the CPE will decide to leak UPnP IGD outside the LAN?
>> Shouldn't this require an upgrade of the CPE to support some "kind"
>> of
>UPnP
>> IGD relay?
>>
>> >
>> >And thanks for your pointer to your pcp-sfc draft.
>> >It looks like the PCP TUNNEL_ID option aligns to this direction of
>> >an extension proposal.
>> >
>> >The decision we called the new option TUNNEL_ID was driven by the
>> >given scenario.
>> >Yes, it might be an idea to change and generalize the option name to
>> >ID instead of TUNNEL_ID.
>>
>> [Med] Great!
>>
>> >
>> >Best,
>> >
>> >Andreas
>> >
>> >> -----Original Message-----
>> >> From: mohamed.boucadair@orange.com
>> >> [mailto:mohamed.boucadair@orange.com]
>> >> Sent: Wednesday, July 09, 2014 10:42 AM
>> >> To: Andreas Ripke; pcp@ietf.org
>> >> Subject: RE: New Version Notification for
>> >> draft-ripke-pcp-tunnel-id-
>> >option-
>> >> 01.txt
>> >>
>> >> Hi Andreas,
>> >>
>> >> Thank you for sharing this updated version of the document.
>> >>
>> >> I'm not sure about the carrier-hosted IWF because one of the
>> >> motivations for PCP to avoid overloading the carrier network with
>> >> a
>> chatty protocol.
>> >>
>> >> FWIW, I have identified in this document as case that require an
>> >> identification information that cannot be included in a
>> >> THIRD_PARTY
>> >option:
>> >> http://tools.ietf.org/html/draft-boucadair-pcp-sfc-classifier-cont
>> >> rol-
>00
>> >> "   o  Extended THIRD_PARTY option to include a L2 identifier (e.g.,
>MAC
>> >>       address), an opaque subscriber-identifier, an IMSI, etc."
>> >>
>> >> I suggest you change TUNNEL_ID to something that won't mislead the
>> >> reader that a tunneling technique is always in place when this
>> >> option is
>> >in
>> >> use.
>> >>
>> >> Cheers,
>> >> Med
>> >>
>> >> >-----Message d'origine-----
>> >> >De : pcp [mailto:pcp-bounces@ietf.org] De la part de Andreas
>> >> >Ripke Envoy=E9 : vendredi 4 juillet 2014 13:05 =C0 : pcp@ietf.org Ob=
jet :
>> >> >[pcp]
>> >> >FW: New Version Notification for draft-ripke-pcp-tunnel-id-
>> >> >option-01.txt
>> >> >
>> >> >Dear all,
>> >> >
>> >> >Thank you for all the feedback we received at the last meeting on
>> >> >the TUNNEL_ID option. This was very helpful. We have updated our
>> >> >draft accordingly and aligned our use case with use cases from
>> >> >existing PCP drafts/RFCs. Particularly we moved the focus from a
>> >> >rather static web portal scenario to a more dynamic UPnP
>> >> >Interworking
>> scenario.
>> >> >
>> >> >http://www.ietf.org/internet-drafts/draft-ripke-pcp-tunnel-id-opt
>> >> >ion
>> >> >-01
>> >> >.txt
>> >> >
>> >> >Please have a look at the draft and give us your feedback.
>> >> >
>> >> >Best regards,
>> >> >
>> >> >Andreas
>> >> >
>> >> >
>> >> >NEC Europe Ltd | Registered Office: Athene, Odyssey Business
>> >> >Park, West End Road, London, HA4 6QE, GB | Registered in England
>> >> >2832014
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >A new version of I-D, draft-ripke-pcp-tunnel-id-option-01.txt
>> >> >has been successfully submitted by Andreas Ripke and posted to
>> >> >the IETF repository.
>> >> >
>> >> >Name:            draft-ripke-pcp-tunnel-id-option
>> >> >Revision:        01
>> >> >Title:           PCP Tunnel-ID Option
>> >> >Document date:   2014-07-03
>> >> >Group:           Individual Submission
>> >> >Pages:           10
>> >> >URL:            http://www.ietf.org/internet-drafts/draft-ripke-pcp-
>> >tunnel-
>> >> >id-option-01.txt
>> >> >Status:         https://datatracker.ietf.org/doc/draft-ripke-pcp-
>tunnel-
>> >id-
>> >> >option/
>> >> >Htmlized:       http://tools.ietf.org/html/draft-ripke-pcp-tunnel-id=
-
>> >> >option-01
>> >> >Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ripke-pcp-
>tunnel-
>> >id-
>> >> >option-01
>> >> >
>> >> >Abstract:
>> >> >   This document describes a new Port Control Protocol (PCP) option
>> >> >   called TUNNEL_ID.  It serves for identifying a Third Party in
>> >> >   addition to the means that PCP's THIRD_PARTY option already
>provides
>> >> >   for that purpose.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >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

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=F3n privilegiada o confidencial y es para uso exclus=
ivo de la persona o entidad de destino. Si no es usted. el destinatario ind=
icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o=
 copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci=
=F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo =
comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti=
al information intended only for the use of the individual or entity named =
above. If the reader of this message is not the intended recipient, you are=
 hereby notified that any dissemination, distribution or copying of this co=
mmunication is strictly prohibited. If you have received this transmission =
in error, do not read it. Please immediately reply to the sender that you h=
ave received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio=
, pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex=
clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des=
tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div=
ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude=
 da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe =
que nos o comunique imediatamente por esta mesma via e proceda a sua destru=
i=E7=E3o


From nobody Fri Jul 11 08:12:12 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 236BE1B2B17 for <pcp@ietfa.amsl.com>; Fri, 11 Jul 2014 08:12:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 rKAYvuA2i2LB for <pcp@ietfa.amsl.com>; Fri, 11 Jul 2014 08:12:02 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A0891B2B06 for <pcp@ietf.org>; Fri, 11 Jul 2014 08:12:01 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 573E318C224; Fri, 11 Jul 2014 17:11:59 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.56]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 350B8238059; Fri, 11 Jul 2014 17:11:59 +0200 (CEST)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.67]) by OPEXCLILH04.corporate.adroot.infra.ftgroup ([10.114.31.56]) with mapi id 14.03.0181.006; Fri, 11 Jul 2014 17:11:59 +0200
From: <mohamed.boucadair@orange.com>
To: RAFAEL ALEJANDRO LOPEZ DA SILVA <rafaelalejandro.lopezdasilva@telefonica.com>, Andreas Ripke <Andreas.Ripke@neclab.eu>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Version Notification for draft-ripke-pcp-tunnel-id-option-01.txt
Thread-Index: AQHPl3Ond1s//Hsjp0CcLYDTq0HzY5uPv3hAgAezYcCAAA2OgIAAU4rggAMmp6CAAAPKEIAAAUqAgAAEtMA=
Date: Fri, 11 Jul 2014 15:11:58 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300317D1@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <20140704103500.20587.59638.idtracker@ietfa.amsl.com> <2D2FFE4726FAF74285C45D69FDC30E798D60089F@DAPHNIS.office.hd> <787AE7BB302AE849A7480A190F8B933002F541@OPEXCLILM23.corporate.adroot.infra.ftgroup> <2D2FFE4726FAF74285C45D69FDC30E798D602C81@Hydra.office.hd> <787AE7BB302AE849A7480A190F8B933002F965@OPEXCLILM23.corporate.adroot.infra.ftgroup> <2D2FFE4726FAF74285C45D69FDC30E798D607FF9@Hydra.office.hd> <787AE7BB302AE849A7480A190F8B933003175D@OPEXCLILM23.corporate.adroot.infra.ftgroup> <03602cb0aef34faa9efca9d623003235@AM3PR06MB051.eurprd06.prod.outlook.com>
In-Reply-To: <03602cb0aef34faa9efca9d623003235@AM3PR06MB051.eurprd06.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
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.6.25.81224
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/YeuZgEsN4a_voySQtj8qC_cBINQ
Subject: Re: [pcp] New Version Notification for draft-ripke-pcp-tunnel-id-option-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: Fri, 11 Jul 2014 15:12:10 -0000

Hi Rafael,

Thank you for the clarification.=20

But given that a legacy CPE, even in the bridge mode, does not leak UPnP IG=
D messages in the WAN interface, I guess an upgrade is still needed to rela=
x that?

BTW, are you aware of tests that have been conducted to confirm this behavi=
or (I'm talking about the UPnP IGD leg)?

Thank you.

Cheers,
Med

>-----Message d'origine-----
>De=A0: RAFAEL ALEJANDRO LOPEZ DA SILVA
>[mailto:rafaelalejandro.lopezdasilva@telefonica.com]
>Envoy=E9=A0: vendredi 11 juillet 2014 17:00
>=C0=A0: BOUCADAIR Mohamed IMT/OLN; Andreas Ripke; pcp@ietf.org
>Objet=A0: RE: New Version Notification for draft-ripke-pcp-tunnel-id-optio=
n-
>01.txt
>
>Hi Med:
>
>Thank you for your suggestions, and as Andreas says we will have to
>describe better the scenario in a next version.
>
>Just as an advance though on the options for the UPnP IGD-PCP IWF. Some
>operators are deploying layer 2 CPEs, while moving some layer 3 CPE
>functionalities to the network. With that you are extending the Layer 2
>domain of the Home LAN into the ISP network. One of the Layer 3 CPE
>functionalities shifted to the network could be the UPnP IGD to PCP IWF,
>for allowing devices without PCP support request dynamic mappings to a CGN=
.
>To achieve scalability this IWF could be located off-path (even though wit=
h
>Layer 2 visibility of the Home devices) and use a mediation system to
>signal the mappings to the CGN on its behalf using the Tunnel Id option.
>
>That is achievable with legacy CPEs in bridge mode.
>
>Best
>Rafael L=F3pez da Silva
>
>
>-----Mensaje original-----
>De: pcp [mailto:pcp-bounces@ietf.org] En nombre de
>mohamed.boucadair@orange.com
>Enviado el: viernes, 11 de julio de 2014 16:45
>Para: Andreas Ripke; pcp@ietf.org
>Asunto: Re: [pcp] New Version Notification for draft-ripke-pcp-tunnel-id-
>option-01.txt
>
>Hi Andreas,
>
>I'm curious to see how this can work with legacy CPEs.
>
>Looking forward to reading an updated version of the draft.
>
>Cheers,
>Med
>
>>-----Message d'origine-----
>>De : Andreas Ripke [mailto:Andreas.Ripke@neclab.eu] Envoy=E9 : vendredi
>>11 juillet 2014 16:42 =C0 : BOUCADAIR Mohamed IMT/OLN; pcp@ietf.org Objet
>>: RE: New Version Notification for draft-ripke-pcp-tunnel-id-option-
>>01.txt
>>
>>Hi Med,
>>
>>Thanks for the hint on UPnP relay. This might not be necessary.
>>Apparently, we have to describe the scenario in more detail.
>>
>>Best,
>>
>>Andreas
>>
>>> -----Original Message-----
>>> From: mohamed.boucadair@orange.com
>>> [mailto:mohamed.boucadair@orange.com]
>>> Sent: Wednesday, July 09, 2014 4:27 PM
>>> To: Andreas Ripke; pcp@ietf.org
>>> Subject: RE: New Version Notification for draft-ripke-pcp-tunnel-id-
>>option-
>>> 01.txt
>>>
>>> Re-,
>>>
>>> Please see inline.
>>>
>>> Cheers,
>>> Med
>>>
>>> >-----Message d'origine-----
>>> >De : Andreas Ripke [mailto:Andreas.Ripke@neclab.eu] Envoy=E9 :
>>> >mercredi 9 juillet 2014 12:02 =C0 : BOUCADAIR Mohamed IMT/OLN;
>pcp@ietf.org Objet :
>>> >RE: New Version Notification for draft-ripke-pcp-tunnel-id-option-
>>> >01.txt
>>> >
>>> >Hi Med,
>>> >
>>> >Thanks for your comments.
>>> >
>>> >Our scenario is a supplement to situations when PCP is not yet on
>>> >hand in the subscriber realm.
>>> >The carrier IWF is offered as a service to the subscribers.
>>> >It does not prevent subscribers to directly use PCP to control ports
>>> >on the CGN.
>>>
>>> [Med] But how the CPE will decide to leak UPnP IGD outside the LAN?
>>> Shouldn't this require an upgrade of the CPE to support some "kind"
>>> of
>>UPnP
>>> IGD relay?
>>>
>>> >
>>> >And thanks for your pointer to your pcp-sfc draft.
>>> >It looks like the PCP TUNNEL_ID option aligns to this direction of
>>> >an extension proposal.
>>> >
>>> >The decision we called the new option TUNNEL_ID was driven by the
>>> >given scenario.
>>> >Yes, it might be an idea to change and generalize the option name to
>>> >ID instead of TUNNEL_ID.
>>>
>>> [Med] Great!
>>>
>>> >
>>> >Best,
>>> >
>>> >Andreas
>>> >
>>> >> -----Original Message-----
>>> >> From: mohamed.boucadair@orange.com
>>> >> [mailto:mohamed.boucadair@orange.com]
>>> >> Sent: Wednesday, July 09, 2014 10:42 AM
>>> >> To: Andreas Ripke; pcp@ietf.org
>>> >> Subject: RE: New Version Notification for
>>> >> draft-ripke-pcp-tunnel-id-
>>> >option-
>>> >> 01.txt
>>> >>
>>> >> Hi Andreas,
>>> >>
>>> >> Thank you for sharing this updated version of the document.
>>> >>
>>> >> I'm not sure about the carrier-hosted IWF because one of the
>>> >> motivations for PCP to avoid overloading the carrier network with
>>> >> a
>>> chatty protocol.
>>> >>
>>> >> FWIW, I have identified in this document as case that require an
>>> >> identification information that cannot be included in a
>>> >> THIRD_PARTY
>>> >option:
>>> >> http://tools.ietf.org/html/draft-boucadair-pcp-sfc-classifier-cont
>>> >> rol-
>>00
>>> >> "   o  Extended THIRD_PARTY option to include a L2 identifier (e.g.,
>>MAC
>>> >>       address), an opaque subscriber-identifier, an IMSI, etc."
>>> >>
>>> >> I suggest you change TUNNEL_ID to something that won't mislead the
>>> >> reader that a tunneling technique is always in place when this
>>> >> option is
>>> >in
>>> >> use.
>>> >>
>>> >> Cheers,
>>> >> Med
>>> >>
>>> >> >-----Message d'origine-----
>>> >> >De : pcp [mailto:pcp-bounces@ietf.org] De la part de Andreas
>>> >> >Ripke Envoy=E9 : vendredi 4 juillet 2014 13:05 =C0 : pcp@ietf.org O=
bjet
>:
>>> >> >[pcp]
>>> >> >FW: New Version Notification for draft-ripke-pcp-tunnel-id-
>>> >> >option-01.txt
>>> >> >
>>> >> >Dear all,
>>> >> >
>>> >> >Thank you for all the feedback we received at the last meeting on
>>> >> >the TUNNEL_ID option. This was very helpful. We have updated our
>>> >> >draft accordingly and aligned our use case with use cases from
>>> >> >existing PCP drafts/RFCs. Particularly we moved the focus from a
>>> >> >rather static web portal scenario to a more dynamic UPnP
>>> >> >Interworking
>>> scenario.
>>> >> >
>>> >> >http://www.ietf.org/internet-drafts/draft-ripke-pcp-tunnel-id-opt
>>> >> >ion
>>> >> >-01
>>> >> >.txt
>>> >> >
>>> >> >Please have a look at the draft and give us your feedback.
>>> >> >
>>> >> >Best regards,
>>> >> >
>>> >> >Andreas
>>> >> >
>>> >> >
>>> >> >NEC Europe Ltd | Registered Office: Athene, Odyssey Business
>>> >> >Park, West End Road, London, HA4 6QE, GB | Registered in England
>>> >> >2832014
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >A new version of I-D, draft-ripke-pcp-tunnel-id-option-01.txt
>>> >> >has been successfully submitted by Andreas Ripke and posted to
>>> >> >the IETF repository.
>>> >> >
>>> >> >Name:            draft-ripke-pcp-tunnel-id-option
>>> >> >Revision:        01
>>> >> >Title:           PCP Tunnel-ID Option
>>> >> >Document date:   2014-07-03
>>> >> >Group:           Individual Submission
>>> >> >Pages:           10
>>> >> >URL:            http://www.ietf.org/internet-drafts/draft-ripke-pcp=
-
>>> >tunnel-
>>> >> >id-option-01.txt
>>> >> >Status:         https://datatracker.ietf.org/doc/draft-ripke-pcp-
>>tunnel-
>>> >id-
>>> >> >option/
>>> >> >Htmlized:       http://tools.ietf.org/html/draft-ripke-pcp-tunnel-
>id-
>>> >> >option-01
>>> >> >Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ripke-pcp-
>>tunnel-
>>> >id-
>>> >> >option-01
>>> >> >
>>> >> >Abstract:
>>> >> >   This document describes a new Port Control Protocol (PCP) option
>>> >> >   called TUNNEL_ID.  It serves for identifying a Third Party in
>>> >> >   addition to the means that PCP's THIRD_PARTY option already
>>provides
>>> >> >   for that purpose.
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >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
>
>________________________________
>
>Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
>puede contener informaci=F3n privilegiada o confidencial y es para uso
>exclusivo de la persona o entidad de destino. Si no es usted. el
>destinatario indicado, queda notificado de que la lectura, utilizaci=F3n,
>divulgaci=F3n y/o copia sin autorizaci=F3n puede estar prohibida en virtud=
 de
>la legislaci=F3n vigente. Si ha recibido este mensaje por error, le rogamo=
s
>que nos lo comunique inmediatamente por esta misma v=EDa y proceda a su
>destrucci=F3n.
>
>The information contained in this transmission is privileged and
>confidential information intended only for the use of the individual or
>entity named above. If the reader of this message is not the intended
>recipient, you are hereby notified that any dissemination, distribution or
>copying of this communication is strictly prohibited. If you have received
>this transmission in error, do not read it. Please immediately reply to th=
e
>sender that you have received this communication in error and then delete
>it.
>
>Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1ri=
o,
>pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso exc=
lusivo
>da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o destinat=
=E1rio
>indicado, fica notificado de que a leitura, utiliza=E7=E3o, divulga=E7=E3o=
 e/ou
>c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude da legisla=E7=
=E3o vigente.
>Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
>imediatamente por esta mesma via e proceda a sua destrui=E7=E3o


From nobody Fri Jul 11 08:18:10 2014
Return-Path: <rafaelalejandro.lopezdasilva@telefonica.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 953CE1B2B71 for <pcp@ietfa.amsl.com>; Fri, 11 Jul 2014 08:18:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 3OYzRG3dwlHc for <pcp@ietfa.amsl.com>; Fri, 11 Jul 2014 08:18:04 -0700 (PDT)
Received: from smtpjc.telefonica.com (smtpjc.telefonica.com [81.47.204.76]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E58B21B2B74 for <pcp@ietf.org>; Fri, 11 Jul 2014 08:17:53 -0700 (PDT)
Received: from smtpjc.telefonica.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3F3D01B812D; Fri, 11 Jul 2014 17:17:51 +0200 (CEST)
Received: from ESTGVMSP113.EUROPE.telefonica.corp (unknown [10.92.4.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtpjc.telefonica.com (Postfix) with ESMTPS id 31F4A1B8129; Fri, 11 Jul 2014 17:17:51 +0200 (CEST)
Received: from emea01-db3-obe.outbound.protection.outlook.com (10.92.5.139) by tls.telefonica.com (10.92.6.55) with Microsoft SMTP Server (TLS) id 14.3.146.2; Fri, 11 Jul 2014 17:17:50 +0200
Received: from AM3PR06MB051.eurprd06.prod.outlook.com (10.242.242.154) by AM3PR06MB049.eurprd06.prod.outlook.com (10.242.242.143) with Microsoft SMTP Server (TLS) id 15.0.980.8; Fri, 11 Jul 2014 15:17:49 +0000
Received: from AM3PR06MB051.eurprd06.prod.outlook.com ([169.254.7.144]) by AM3PR06MB051.eurprd06.prod.outlook.com ([169.254.7.144]) with mapi id 15.00.0980.000; Fri, 11 Jul 2014 15:17:48 +0000
From: RAFAEL ALEJANDRO LOPEZ DA SILVA <rafaelalejandro.lopezdasilva@telefonica.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "Andreas Ripke" <Andreas.Ripke@neclab.eu>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Version Notification for draft-ripke-pcp-tunnel-id-option-01.txt
Thread-Index: AQHPl3Ond1s//Hsjp0CcLYDTq0HzY5uPv3hAgAezYcCAAA2OgIAAU4rggAMmp6CAAAPKEIAAAUqAgAAEtMCAAAIGoA==
Date: Fri, 11 Jul 2014 15:17:48 +0000
Message-ID: <fee10e77fb8f4e9d82fcf0f0a3dc7278@AM3PR06MB051.eurprd06.prod.outlook.com>
References: <20140704103500.20587.59638.idtracker@ietfa.amsl.com> <2D2FFE4726FAF74285C45D69FDC30E798D60089F@DAPHNIS.office.hd> <787AE7BB302AE849A7480A190F8B933002F541@OPEXCLILM23.corporate.adroot.infra.ftgroup> <2D2FFE4726FAF74285C45D69FDC30E798D602C81@Hydra.office.hd> <787AE7BB302AE849A7480A190F8B933002F965@OPEXCLILM23.corporate.adroot.infra.ftgroup> <2D2FFE4726FAF74285C45D69FDC30E798D607FF9@Hydra.office.hd> <787AE7BB302AE849A7480A190F8B933003175D@OPEXCLILM23.corporate.adroot.infra.ftgroup> <03602cb0aef34faa9efca9d623003235@AM3PR06MB051.eurprd06.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93300317D1@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93300317D1@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: es-ES
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [195.235.92.27]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 02698DF457
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(377454003)(13464003)(377424004)(51704005)(55784002)(199002)(51914003)(189002)(107886001)(83072002)(87936001)(21056001)(77982001)(79102001)(76482001)(92566001)(54356999)(15975445006)(19580395003)(74662001)(76176999)(101416001)(33646001)(76576001)(95666004)(85306003)(4396001)(86362001)(2656002)(31966008)(74316001)(81542001)(64706001)(105586002)(20776003)(66066001)(74502001)(107046002)(561944003)(19580405001)(15202345003)(93886003)(46102001)(99396002)(83322001)(81342001)(106116001)(77096002)(80022001)(85852003)(50986999)(106356001)(108616002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:AM3PR06MB049; H:AM3PR06MB051.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en; 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: telefonica.com
X-TM-AS-MML: No
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/igZHAwFExcYEDQyjTSstb53D7Vw
Subject: Re: [pcp] New Version Notification for draft-ripke-pcp-tunnel-id-option-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: Fri, 11 Jul 2014 15:18:08 -0000

Hi Med,

Well then it seems that it may be dependent on the specific vendor/model, b=
ecause I can assure that some do leak the UPnP IGD messages to the WAN in b=
ridge mode.

And in any case, it isn't a functionality that with a firmware update could=
 not be supported in a legacy CPE (even though it would make the migration =
to the model more complex)

Regards
Rafael

-----Mensaje original-----
De: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com]
Enviado el: viernes, 11 de julio de 2014 17:12
Para: RAFAEL ALEJANDRO LOPEZ DA SILVA; Andreas Ripke; pcp@ietf.org
Asunto: RE: New Version Notification for draft-ripke-pcp-tunnel-id-option-0=
1.txt

Hi Rafael,

Thank you for the clarification.

But given that a legacy CPE, even in the bridge mode, does not leak UPnP IG=
D messages in the WAN interface, I guess an upgrade is still needed to rela=
x that?

BTW, are you aware of tests that have been conducted to confirm this behavi=
or (I'm talking about the UPnP IGD leg)?

Thank you.

Cheers,
Med

>-----Message d'origine-----
>De : RAFAEL ALEJANDRO LOPEZ DA SILVA
>[mailto:rafaelalejandro.lopezdasilva@telefonica.com]
>Envoy=E9 : vendredi 11 juillet 2014 17:00 =C0 : BOUCADAIR Mohamed IMT/OLN;
>Andreas Ripke; pcp@ietf.org Objet : RE: New Version Notification for
>draft-ripke-pcp-tunnel-id-option-
>01.txt
>
>Hi Med:
>
>Thank you for your suggestions, and as Andreas says we will have to
>describe better the scenario in a next version.
>
>Just as an advance though on the options for the UPnP IGD-PCP IWF. Some
>operators are deploying layer 2 CPEs, while moving some layer 3 CPE
>functionalities to the network. With that you are extending the Layer 2
>domain of the Home LAN into the ISP network. One of the Layer 3 CPE
>functionalities shifted to the network could be the UPnP IGD to PCP
>IWF, for allowing devices without PCP support request dynamic mappings to =
a CGN.
>To achieve scalability this IWF could be located off-path (even though
>with Layer 2 visibility of the Home devices) and use a mediation system
>to signal the mappings to the CGN on its behalf using the Tunnel Id option=
.
>
>That is achievable with legacy CPEs in bridge mode.
>
>Best
>Rafael L=F3pez da Silva
>
>
>-----Mensaje original-----
>De: pcp [mailto:pcp-bounces@ietf.org] En nombre de
>mohamed.boucadair@orange.com Enviado el: viernes, 11 de julio de 2014
>16:45
>Para: Andreas Ripke; pcp@ietf.org
>Asunto: Re: [pcp] New Version Notification for
>draft-ripke-pcp-tunnel-id- option-01.txt
>
>Hi Andreas,
>
>I'm curious to see how this can work with legacy CPEs.
>
>Looking forward to reading an updated version of the draft.
>
>Cheers,
>Med
>
>>-----Message d'origine-----
>>De : Andreas Ripke [mailto:Andreas.Ripke@neclab.eu] Envoy=E9 : vendredi
>>11 juillet 2014 16:42 =C0 : BOUCADAIR Mohamed IMT/OLN; pcp@ietf.org
>>Objet
>>: RE: New Version Notification for draft-ripke-pcp-tunnel-id-option-
>>01.txt
>>
>>Hi Med,
>>
>>Thanks for the hint on UPnP relay. This might not be necessary.
>>Apparently, we have to describe the scenario in more detail.
>>
>>Best,
>>
>>Andreas
>>
>>> -----Original Message-----
>>> From: mohamed.boucadair@orange.com
>>> [mailto:mohamed.boucadair@orange.com]
>>> Sent: Wednesday, July 09, 2014 4:27 PM
>>> To: Andreas Ripke; pcp@ietf.org
>>> Subject: RE: New Version Notification for draft-ripke-pcp-tunnel-id-
>>option-
>>> 01.txt
>>>
>>> Re-,
>>>
>>> Please see inline.
>>>
>>> Cheers,
>>> Med
>>>
>>> >-----Message d'origine-----
>>> >De : Andreas Ripke [mailto:Andreas.Ripke@neclab.eu] Envoy=E9 :
>>> >mercredi 9 juillet 2014 12:02 =C0 : BOUCADAIR Mohamed IMT/OLN;
>pcp@ietf.org Objet :
>>> >RE: New Version Notification for draft-ripke-pcp-tunnel-id-option-
>>> >01.txt
>>> >
>>> >Hi Med,
>>> >
>>> >Thanks for your comments.
>>> >
>>> >Our scenario is a supplement to situations when PCP is not yet on
>>> >hand in the subscriber realm.
>>> >The carrier IWF is offered as a service to the subscribers.
>>> >It does not prevent subscribers to directly use PCP to control
>>> >ports on the CGN.
>>>
>>> [Med] But how the CPE will decide to leak UPnP IGD outside the LAN?
>>> Shouldn't this require an upgrade of the CPE to support some "kind"
>>> of
>>UPnP
>>> IGD relay?
>>>
>>> >
>>> >And thanks for your pointer to your pcp-sfc draft.
>>> >It looks like the PCP TUNNEL_ID option aligns to this direction of
>>> >an extension proposal.
>>> >
>>> >The decision we called the new option TUNNEL_ID was driven by the
>>> >given scenario.
>>> >Yes, it might be an idea to change and generalize the option name
>>> >to ID instead of TUNNEL_ID.
>>>
>>> [Med] Great!
>>>
>>> >
>>> >Best,
>>> >
>>> >Andreas
>>> >
>>> >> -----Original Message-----
>>> >> From: mohamed.boucadair@orange.com
>>> >> [mailto:mohamed.boucadair@orange.com]
>>> >> Sent: Wednesday, July 09, 2014 10:42 AM
>>> >> To: Andreas Ripke; pcp@ietf.org
>>> >> Subject: RE: New Version Notification for
>>> >> draft-ripke-pcp-tunnel-id-
>>> >option-
>>> >> 01.txt
>>> >>
>>> >> Hi Andreas,
>>> >>
>>> >> Thank you for sharing this updated version of the document.
>>> >>
>>> >> I'm not sure about the carrier-hosted IWF because one of the
>>> >> motivations for PCP to avoid overloading the carrier network with
>>> >> a
>>> chatty protocol.
>>> >>
>>> >> FWIW, I have identified in this document as case that require an
>>> >> identification information that cannot be included in a
>>> >> THIRD_PARTY
>>> >option:
>>> >> http://tools.ietf.org/html/draft-boucadair-pcp-sfc-classifier-con
>>> >> t
>>> >> rol-
>>00
>>> >> "   o  Extended THIRD_PARTY option to include a L2 identifier (e.g.,
>>MAC
>>> >>       address), an opaque subscriber-identifier, an IMSI, etc."
>>> >>
>>> >> I suggest you change TUNNEL_ID to something that won't mislead
>>> >> the reader that a tunneling technique is always in place when
>>> >> this option is
>>> >in
>>> >> use.
>>> >>
>>> >> Cheers,
>>> >> Med
>>> >>
>>> >> >-----Message d'origine-----
>>> >> >De : pcp [mailto:pcp-bounces@ietf.org] De la part de Andreas
>>> >> >Ripke Envoy=E9 : vendredi 4 juillet 2014 13:05 =C0 : pcp@ietf.org
>>> >> >Objet
>:
>>> >> >[pcp]
>>> >> >FW: New Version Notification for draft-ripke-pcp-tunnel-id-
>>> >> >option-01.txt
>>> >> >
>>> >> >Dear all,
>>> >> >
>>> >> >Thank you for all the feedback we received at the last meeting
>>> >> >on the TUNNEL_ID option. This was very helpful. We have updated
>>> >> >our draft accordingly and aligned our use case with use cases
>>> >> >from existing PCP drafts/RFCs. Particularly we moved the focus
>>> >> >from a rather static web portal scenario to a more dynamic UPnP
>>> >> >Interworking
>>> scenario.
>>> >> >
>>> >> >http://www.ietf.org/internet-drafts/draft-ripke-pcp-tunnel-id-op
>>> >> >t
>>> >> >ion
>>> >> >-01
>>> >> >.txt
>>> >> >
>>> >> >Please have a look at the draft and give us your feedback.
>>> >> >
>>> >> >Best regards,
>>> >> >
>>> >> >Andreas
>>> >> >
>>> >> >
>>> >> >NEC Europe Ltd | Registered Office: Athene, Odyssey Business
>>> >> >Park, West End Road, London, HA4 6QE, GB | Registered in England
>>> >> >2832014
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >A new version of I-D, draft-ripke-pcp-tunnel-id-option-01.txt
>>> >> >has been successfully submitted by Andreas Ripke and posted to
>>> >> >the IETF repository.
>>> >> >
>>> >> >Name:            draft-ripke-pcp-tunnel-id-option
>>> >> >Revision:        01
>>> >> >Title:           PCP Tunnel-ID Option
>>> >> >Document date:   2014-07-03
>>> >> >Group:           Individual Submission
>>> >> >Pages:           10
>>> >> >URL:            http://www.ietf.org/internet-drafts/draft-ripke-pcp=
-
>>> >tunnel-
>>> >> >id-option-01.txt
>>> >> >Status:         https://datatracker.ietf.org/doc/draft-ripke-pcp-
>>tunnel-
>>> >id-
>>> >> >option/
>>> >> >Htmlized:       http://tools.ietf.org/html/draft-ripke-pcp-tunnel-
>id-
>>> >> >option-01
>>> >> >Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ripke-pcp-
>>tunnel-
>>> >id-
>>> >> >option-01
>>> >> >
>>> >> >Abstract:
>>> >> >   This document describes a new Port Control Protocol (PCP) option
>>> >> >   called TUNNEL_ID.  It serves for identifying a Third Party in
>>> >> >   addition to the means that PCP's THIRD_PARTY option already
>>provides
>>> >> >   for that purpose.
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >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
>
>________________________________
>
>Este mensaje y sus adjuntos se dirigen exclusivamente a su
>destinatario, puede contener informaci=F3n privilegiada o confidencial y
>es para uso exclusivo de la persona o entidad de destino. Si no es
>usted. el destinatario indicado, queda notificado de que la lectura,
>utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede estar
>prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este
>mensaje por error, le rogamos que nos lo comunique inmediatamente por
>esta misma v=EDa y proceda a su destrucci=F3n.
>
>The information contained in this transmission is privileged and
>confidential information intended only for the use of the individual or
>entity named above. If the reader of this message is not the intended
>recipient, you are hereby notified that any dissemination, distribution
>or copying of this communication is strictly prohibited. If you have
>received this transmission in error, do not read it. Please immediately
>reply to the sender that you have received this communication in error
>and then delete it.
>
>Esta mensagem e seus anexos se dirigem exclusivamente ao seu
>destinat=E1rio, pode conter informa=E7=E3o privilegiada ou confidencial e =
=E9
>para uso exclusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa
>senhoria o destinat=E1rio indicado, fica notificado de que a leitura,
>utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar=
 proibida em virtude da legisla=E7=E3o vigente.
>Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
>imediatamente por esta mesma via e proceda a sua destrui=E7=E3o

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=F3n privilegiada o confidencial y es para uso exclus=
ivo de la persona o entidad de destino. Si no es usted. el destinatario ind=
icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o=
 copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci=
=F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo =
comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti=
al information intended only for the use of the individual or entity named =
above. If the reader of this message is not the intended recipient, you are=
 hereby notified that any dissemination, distribution or copying of this co=
mmunication is strictly prohibited. If you have received this transmission =
in error, do not read it. Please immediately reply to the sender that you h=
ave received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio=
, pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex=
clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des=
tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div=
ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude=
 da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe =
que nos o comunique imediatamente por esta mesma via e proceda a sua destru=
i=E7=E3o


From nobody Mon Jul 14 18:33:49 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 070E81B27D4; Mon, 14 Jul 2014 18:33:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.553
X-Spam-Level: 
X-Spam-Status: No, score=-107.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 pA16pCeN7m1K; Mon, 14 Jul 2014 18:33:30 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id A8D5B1B27C4; Mon, 14 Jul 2014 18:33:30 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 38E6818001B; Mon, 14 Jul 2014 18:32:43 -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: <20140715013243.38E6818001B@rfc-editor.org>
Date: Mon, 14 Jul 2014 18:32:43 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/10FnDUUuBefHTUF9Ohl-22_hDx8
Cc: drafts-update-ref@iana.org, pcp@ietf.org, rfc-editor@rfc-editor.org
Subject: [pcp] RFC 7291 on DHCP Options 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: Tue, 15 Jul 2014 01:33:36 -0000

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

        
        RFC 7291

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

        I-D Tag:    draft-ietf-pcp-dhcp-13.txt

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

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 scenarios.  The set
of deployment scenarios to which DHCPv4 or DHCPv6 can be applied is
outside the scope of this document.

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 Mon Jul 14 23:04:55 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 412281B27DB for <pcp@ietfa.amsl.com>; Mon, 14 Jul 2014 23:04:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.778
X-Spam-Level: 
X-Spam-Status: No, score=0.778 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] 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 Z8Yvyv3hZRdg for <pcp@ietfa.amsl.com>; Mon, 14 Jul 2014 23:04:52 -0700 (PDT)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.199]) by ietfa.amsl.com (Postfix) with ESMTP id 6A2C41B2819 for <pcp@ietf.org>; Mon, 14 Jul 2014 23:04:33 -0700 (PDT)
Received: from poro.lan (84.248.80.109) by jenni2.inet.fi (8.5.140.03) (authenticated as stenma-47) id 53A17F6002044DBF; Tue, 15 Jul 2014 09:03:54 +0300
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93300317D1@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Date: Tue, 15 Jul 2014 09:03:52 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A465D93-30B8-4A74-A806-C173A8D3EB28@iki.fi>
References: <20140704103500.20587.59638.idtracker@ietfa.amsl.com> <2D2FFE4726FAF74285C45D69FDC30E798D60089F@DAPHNIS.office.hd> <787AE7BB302AE849A7480A190F8B933002F541@OPEXCLILM23.corporate.adroot.infra.ftgroup> <2D2FFE4726FAF74285C45D69FDC30E798D602C81@Hydra.office.hd> <787AE7BB302AE849A7480A190F8B933002F965@OPEXCLILM23.corporate.adroot.infra.ftgroup> <2D2FFE4726FAF74285C45D69FDC30E798D607FF9@Hydra.office.hd> <787AE7BB302AE849A7480A190F8B933003175D@OPEXCLILM23.corporate.adroot.infra.ftgroup> <03602cb0aef34faa9efca9d623003235@AM3PR06MB051.eurprd06.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93300317D1@OPEXCLILM23.corporate.adroot.infra.ftgroup>
To: mohamed.boucadair@orange.com
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/k4PKlmdjkeGTUyF4xt-WNn6GlBA
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] New Version Notification for draft-ripke-pcp-tunnel-id-option-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, 15 Jul 2014 06:04:54 -0000

On 11.7.2014, at 18.11, mohamed.boucadair@orange.com wrote:
> Thank you for the clarification.=20
>=20
> But given that a legacy CPE, even in the bridge mode, does not leak =
UPnP IGD messages in the WAN interface, I guess an upgrade is still =
needed to relax that?

If it=92s in ~L2 bridging mode, and doesn=92t do anything clever (such =
as bridge-firewalling), why would it not leak UPnP messages on WAN?=20

I have CPEs that basically convert media from X to Y (notably, =
ethernet-ish to something {A,V}DSL-ish), and when they=92re in L2 =
bridging mode, what you stick in from ethernet port, goes on the line, =
without any clever bits working. If they=92re _not_ in bridged mode, all =
sorts of obvious things happen such as NAT, hop count handling, etc, =
which would obviously do bad things to UPnP traffic destined to WAN =
port.

I doubt that any CPE that is _not_ in L2 bridging mode would work with =
this CGN-side IGD scheme out of the box (given some configuration, yes, =
but not otherwise).

Cheers,

-Markus

P.S. I consider L2 CPEs good _for advanced users_ and not that great =
idea as a default. However, I=92m sure this draft has it=92s place, =
somewhere.. ;)


From nobody Wed Jul 16 18:41:52 2014
Return-Path: <trac@tools.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 1D3B11A03F5 for <pcp@ietfa.amsl.com>; Wed, 16 Jul 2014 18:41:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 c8riZespsttg for <pcp@ietfa.amsl.com>; Wed, 16 Jul 2014 18:41:50 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 041D71A03F4 for <pcp@ietf.org>; Wed, 16 Jul 2014 18:41:50 -0700 (PDT)
Received: from localhost ([::1]:43458 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac@tools.ietf.org>) id 1X7ahW-0005Qa-E6; Wed, 16 Jul 2014 18:41:38 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "pcp issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-pcp-port-set@tools.ietf.org, dthaler@microsoft.com
X-Trac-Project: pcp
Date: Thu, 17 Jul 2014 01:41:38 -0000
X-URL: http://tools.ietf.org/pcp/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/pcp/trac/ticket/70#comment:1
Message-ID: <074.c0bd5bc90e7b754256a42a5de5aa3a3d@tools.ietf.org>
References: <059.9c890c190a530694044ddc4e563b8d72@tools.ietf.org>
X-Trac-Ticket-ID: 70
In-Reply-To: <059.9c890c190a530694044ddc4e563b8d72@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-pcp-port-set@tools.ietf.org, dthaler@microsoft.com, pcp@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: cathy.zhou@huawei.com, mohamed.boucadair@orange.com, simon@per.reau.lt, ssenthil@cisco.com, sunqiong@ctbri.com.cn, tina.tsou.zouting@huawei.com
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/LQHw_26hjxsUrc16JW0EiBLF1t0
Cc: pcp@ietf.org
Subject: Re: [pcp] #70 (port-set): IETF 88 meeting feedback on draft-ietf-pcp-port-set-04
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: Thu, 17 Jul 2014 01:41:51 -0000

#70: IETF 88 meeting feedback on draft-ietf-pcp-port-set-04

Changes (by dthaler@microsoft.com):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Fixed in -05

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-pcp-port-
  dthaler@microsoft.com  |  set@tools.ietf.org
     Type:  defect       |      Status:  closed
 Priority:  major        |   Milestone:  milestone1
Component:  port-set     |     Version:  1.0
 Severity:  Active WG    |  Resolution:  fixed
  Document               |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/pcp/trac/ticket/70#comment:1>
pcp <http://tools.ietf.org/pcp/>


From nobody Wed Jul 16 18:53:03 2014
Return-Path: <trac@tools.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 A49D01A03EF for <pcp@ietfa.amsl.com>; Wed, 16 Jul 2014 18:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 i7eylwbSxCRs for <pcp@ietfa.amsl.com>; Wed, 16 Jul 2014 18:52:59 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68C491A03F5 for <pcp@ietf.org>; Wed, 16 Jul 2014 18:52:59 -0700 (PDT)
Received: from localhost ([::1]:43852 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac@tools.ietf.org>) id 1X7asT-0005kr-4s; Wed, 16 Jul 2014 18:52:57 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "pcp issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-pcp-server-selection@tools.ietf.org, dthaler@microsoft.com
X-Trac-Project: pcp
Date: Thu, 17 Jul 2014 01:52:57 -0000
X-URL: http://tools.ietf.org/pcp/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/pcp/trac/ticket/68#comment:1
Message-ID: <074.a2cce5942f6f5f26f7f03131efa6c804@tools.ietf.org>
References: <059.8c54e37692f360ec6114d97c4ee4c134@tools.ietf.org>
X-Trac-Ticket-ID: 68
In-Reply-To: <059.8c54e37692f360ec6114d97c4ee4c134@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-pcp-server-selection@tools.ietf.org, dthaler@microsoft.com, pcp@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: dwing@cisco.com, mohamed.boucadair@orange.com, praspati@cisco.com,  repenno@cisco.com, tireddy@cisco.com
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/nde9toZFjCeDe-mtALxBEm_Eya8
Cc: pcp@ietf.org
Subject: Re: [pcp] #68 (server-selection): Server selection feedback from Dave Thaler
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: Thu, 17 Jul 2014 01:53:00 -0000

#68: Server selection feedback from Dave Thaler

Changes (by dthaler@microsoft.com):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Addressed in -03.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-pcp-server-
  dthaler@microsoft.com  |  selection@tools.ietf.org
     Type:  defect       |      Status:  closed
 Priority:  major        |   Milestone:  milestone1
Component:  server-      |     Version:  1.0
  selection              |  Resolution:  fixed
 Severity:  In WG Last   |
  Call                   |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/pcp/trac/ticket/68#comment:1>
pcp <http://tools.ietf.org/pcp/>


From nobody Wed Jul 16 19:07:33 2014
Return-Path: <trac@tools.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 973AD1A03F9 for <pcp@ietfa.amsl.com>; Wed, 16 Jul 2014 19:07:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 dk0uu_6n18d7 for <pcp@ietfa.amsl.com>; Wed, 16 Jul 2014 19:07:30 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D1991A03F5 for <pcp@ietf.org>; Wed, 16 Jul 2014 19:07:30 -0700 (PDT)
Received: from localhost ([::1]:44487 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac@tools.ietf.org>) id 1X7b6U-0001zb-0D; Wed, 16 Jul 2014 19:07:26 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "pcp issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-pcp-server-selection@tools.ietf.org, dthaler@microsoft.com
X-Trac-Project: pcp
Date: Thu, 17 Jul 2014 02:07:25 -0000
X-URL: http://tools.ietf.org/pcp/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/pcp/trac/ticket/67#comment:1
Message-ID: <080.440fedac32478a932ed3e7448c017da9@tools.ietf.org>
References: <065.afb63ecc150bcf708a7b04d61f012f95@tools.ietf.org>
X-Trac-Ticket-ID: 67
In-Reply-To: <065.afb63ecc150bcf708a7b04d61f012f95@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-pcp-server-selection@tools.ietf.org, dthaler@microsoft.com, pcp@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: dwing@cisco.com, mohamed.boucadair@orange.com, praspati@cisco.com,  repenno@cisco.com, tireddy@cisco.com
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/U1RvMAYDD1GaDjm6Y3scCEa23bM
Cc: pcp@ietf.org
Subject: Re: [pcp] #67 (server-selection): Server selection feedback from Simon Perreault
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: Thu, 17 Jul 2014 02:07:31 -0000

#67: Server selection feedback from Simon Perreault

Changes (by dthaler@microsoft.com):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Addressed in -03.

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |       Owner:  draft-ietf-pcp-server-
  simon.perreault@viagenie.ca        |  selection@tools.ietf.org
     Type:  defect                   |      Status:  closed
 Priority:  major                    |   Milestone:  milestone1
Component:  server-selection         |     Version:  1.0
 Severity:  In WG Last Call          |  Resolution:  fixed
 Keywords:                           |
-------------------------------------+-------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/pcp/trac/ticket/67#comment:1>
pcp <http://tools.ietf.org/pcp/>


From nobody Wed Jul 16 19:09:09 2014
Return-Path: <trac@tools.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 3B7EE1A03F5 for <pcp@ietfa.amsl.com>; Wed, 16 Jul 2014 19:09:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 nmihg9yUpchL for <pcp@ietfa.amsl.com>; Wed, 16 Jul 2014 19:09:02 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3740F1A03F4 for <pcp@ietf.org>; Wed, 16 Jul 2014 19:09:02 -0700 (PDT)
Received: from localhost ([::1]:44540 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac@tools.ietf.org>) id 1X7b7x-0002EE-BS; Wed, 16 Jul 2014 19:08:57 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "pcp issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-pcp-base@tools.ietf.org, dthaler@microsoft.com, cheshire@apple.com
X-Trac-Project: pcp
Date: Thu, 17 Jul 2014 02:08:57 -0000
X-URL: http://tools.ietf.org/pcp/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/pcp/trac/ticket/49#comment:8
Message-ID: <074.a4425138cbd7a6ee6ede5aa5479c775f@tools.ietf.org>
References: <059.1abaaf1dbe2b764801b50b06a104fce1@tools.ietf.org>
X-Trac-Ticket-ID: 49
In-Reply-To: <059.1abaaf1dbe2b764801b50b06a104fce1@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-pcp-base@tools.ietf.org, dthaler@microsoft.com,  cheshire@apple.com, pcp@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: cheshire@apple.com, dwing@cisco.com, mohamed.boucadair@orange.com,  pselkirk@isc.org, repenno@cisco.com
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/MUeyhlDw7S3i7qJSt8I-yaXosBk
Cc: pcp@ietf.org
Subject: Re: [pcp] #49 (server-selection): Multihoming confusion
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: Thu, 17 Jul 2014 02:09:06 -0000

#49: Multihoming confusion

Changes (by dthaler@microsoft.com):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 Addressed in -03.
 Please open a new ticket for any feedback on -03.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-pcp-base@tools.ietf.org
  dthaler@microsoft.com  |      Status:  closed
     Type:  defect       |   Milestone:
 Priority:  major        |     Version:
Component:  server-      |  Resolution:  fixed
  selection              |
 Severity:  -            |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/pcp/trac/ticket/49#comment:8>
pcp <http://tools.ietf.org/pcp/>


From nobody Wed Jul 16 22:50:08 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 645741A0658 for <pcp@ietfa.amsl.com>; Wed, 16 Jul 2014 22:50: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 BuSNQ827QZ4N for <pcp@ietfa.amsl.com>; Wed, 16 Jul 2014 22:50:01 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FB481A04B8 for <pcp@ietf.org>; Wed, 16 Jul 2014 22:50:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=980; q=dns/txt; s=iport; t=1405576201; x=1406785801; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=ET4Zg97hOJB/pngS8Y3zLtVrMpVeiWPhZRKWaXqY2rU=; b=I9vnYmBO7l6k4hkHLCxJXYDgRYsDapleWy/H/y87Uo9ynYCdJ6GtOKes 12eKnF+D0LZUGuyfgeVg/TIhdmKm9LtH8qSpd2DvWWnC84Ex0Y9pHcvjU X7LXnA0BH+uefUG4c6BMMtlm3Ra2KLYSSLokGyRo9l++zvuvTB/qaLYcX M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEFAJ1jx1OtJV2Q/2dsb2JhbABZgw6BLcwIFnaECjo0HQE+QicEiFWjXaZdF5QVBZsdlCyDRIIx
X-IronPort-AV: E=Sophos;i="5.01,676,1400025600"; d="scan'208";a="340421875"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-1.cisco.com with ESMTP; 17 Jul 2014 05:50:00 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id s6H5o0GI030508 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <pcp@ietf.org>; Thu, 17 Jul 2014 05:50:00 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.176]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0123.003; Thu, 17 Jul 2014 00:50:00 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: Discussion about Closing PCP WG
Thread-Index: AQHPoYLyCP/Gj5Y9hkitXO7sLwNpIw==
Date: Thu, 17 Jul 2014 05:50:00 +0000
Message-ID: <CFECB216.D03B%repenno@cisco.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.126.122]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B23B6373E23AF9428367726B96BFBFBB@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/40UXQ7eNKH9lnFwucDooSxmmZYg
Subject: [pcp] Discussion about Closing PCP WG
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, 17 Jul 2014 05:50:05 -0000

The chairs and AD have been discussing the lack of activity on the mailing
list compounded with the low number of agenda requests and lack of any
agenda requests for WG documents.

Therefore we propose that after Server Selection and Anycast drafts are
done it would be a good point to close the WG. This has been a very
successful WG, we delivered what was in the original charter, adapted
quickly to incorporate new documents and delivered those.


Furthermore we would propose to hold a webex interim meeting in lieu of
the f2f meeting at the IETF. The WebEx interim meeting will be scheduled
to occur shortly after WGLC completes on the Server Selection draft, and
we plan to start the WGLC shortly.

The two agenda requests we received for discussion of new individual
drafts would be deferred to the interim meeting.

If you feel that closing the WG is premature, we need to see real progress
on other WG documents.


Thanks,

Reinaldo, Dave & Ted.


From nobody Fri Jul 18 05:32:53 2014
Return-Path: <praspati@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 6AB051A049F for <pcp@ietfa.amsl.com>; Fri, 18 Jul 2014 05:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 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.001, 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 VhXYwHhZtKug for <pcp@ietfa.amsl.com>; Fri, 18 Jul 2014 05:32:50 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 439BE1A0AB0 for <pcp@ietf.org>; Fri, 18 Jul 2014 05:32:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1322; q=dns/txt; s=iport; t=1405686770; x=1406896370; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=frPiG6HC/goydCST12OgwpJS9Fs3X3PIVdo/s5yRrl4=; b=J1EerP+iqMozjKyv7kqaNLPfrcL+ghXhgjuYIVscoCMlhFmz5bBYNOIE VOzRta8XA1Ar4YNetyYb11lbkzBbXaFuGIxp9OmVBwtiZHNo88jVQZ3Tv Z21+EO7HTPu0f8qVi1eC66G6HKe9sGEZvKAautqkGr4Gqkdw0Gkzkrk7n A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAFcTyVOtJA2J/2dsb2JhbABZgw5SW8RmCohLFnaEBAEBBAEBATc0HQEINjcLJwQBEohCDcQfEwSUGAWbJZQvg0RsgUU
X-IronPort-AV: E=Sophos;i="5.01,684,1400025600"; d="scan'208";a="61984682"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-4.cisco.com with ESMTP; 18 Jul 2014 12:32:49 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s6ICWnlB017175 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <pcp@ietf.org>; Fri, 18 Jul 2014 12:32:49 GMT
Received: from xmb-rcd-x07.cisco.com ([169.254.7.100]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0123.003; Fri, 18 Jul 2014 07:32:49 -0500
From: "Prashanth Patil (praspati)" <praspati@cisco.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] Discussion about Closing PCP WG
Thread-Index: AQHPooRizEIso6bDt0SX34yXdsKtMQ==
Date: Fri, 18 Jul 2014 12:32:49 +0000
Message-ID: <CFEF11A4.43FCA%praspati@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.3.140616
x-originating-ip: [173.39.65.55]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9F384D90775AC0498DAA9F2B8DE2BD21@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/YvD_3NRCaosILolDrjUjfHzLntc
Subject: Re: [pcp] Discussion about Closing PCP WG
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, 18 Jul 2014 12:32:52 -0000

I think we should see drafts like PCP Auth to completion before
considering WG closure.

-Prashanth


On 7/17/14 11:20 AM, "Reinaldo Penno (repenno)" <repenno@cisco.com> wrote:

>The chairs and AD have been discussing the lack of activity on the mailing
>list compounded with the low number of agenda requests and lack of any
>agenda requests for WG documents.
>
>Therefore we propose that after Server Selection and Anycast drafts are
>done it would be a good point to close the WG. This has been a very
>successful WG, we delivered what was in the original charter, adapted
>quickly to incorporate new documents and delivered those.
>
>
>Furthermore we would propose to hold a webex interim meeting in lieu of
>the f2f meeting at the IETF. The WebEx interim meeting will be scheduled
>to occur shortly after WGLC completes on the Server Selection draft, and
>we plan to start the WGLC shortly.
>
>The two agenda requests we received for discussion of new individual
>drafts would be deferred to the interim meeting.
>
>If you feel that closing the WG is premature, we need to see real progress
>on other WG documents.
>
>
>Thanks,
>
>Reinaldo, Dave & Ted.
>
>_______________________________________________
>pcp mailing list
>pcp@ietf.org
>https://www.ietf.org/mailman/listinfo/pcp


From nobody Fri Jul 18 07:10:30 2014
Return-Path: <margaretw42@gmail.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 ABC3A1A063E for <pcp@ietfa.amsl.com>; Fri, 18 Jul 2014 07:10:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-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 H43Yl72EcMje for <pcp@ietfa.amsl.com>; Fri, 18 Jul 2014 07:10:24 -0700 (PDT)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E3771A0349 for <pcp@ietf.org>; Fri, 18 Jul 2014 07:10:24 -0700 (PDT)
Received: by mail-qc0-f174.google.com with SMTP id o8so3416512qcw.33 for <pcp@ietf.org>; Fri, 18 Jul 2014 07:10:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UrWyqdXVmv9iBk83Q75cIVtvIVf1YDbg60C0qGWCiFY=; b=bYa5f0KXxBGu1DVALMr21tsVWtTgJmq8ALv87mlV2g3K1XutM9MyQQX4wolx5R37Qd kXo5xHJy1vHkdiG44JVPHooVAMXNERvXiIerarXB9vz9ut8NHZNqpTqBi2c+pFCWA+g7 PANV5D9QqexkXJVDpKvil2ckLUhIzGg0P9WrQM0ivYEDx7EIXlb27p9I2yFtoEU8lrKw jRVyQhHWNqnFSdCXJMVs3b/oISUsiCr0tvmsTYT/+9M1ChIMzo2po79xvPkZLA5eXsbw dngbl4YdhrQdUc6BkYs7C7Mou37dl9KX1xLHENtcrPOBc+Qlh5kpUPl3HvTekaFQo1z3 TX+w==
X-Received: by 10.224.129.68 with SMTP id n4mr8753435qas.66.1405692623706; Fri, 18 Jul 2014 07:10:23 -0700 (PDT)
Received: from new-host.home (pool-108-20-149-183.bstnma.fios.verizon.net. [108.20.149.183]) by mx.google.com with ESMTPSA id r10sm10095712qar.40.2014.07.18.07.10.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Jul 2014 07:10:22 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <CFECB216.D03B%repenno@cisco.com>
Date: Fri, 18 Jul 2014 10:10:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C388038D-1DA9-4934-979E-E8054FD82D11@gmail.com>
References: <CFECB216.D03B%repenno@cisco.com>
To: Reinaldo Penno (repenno) <repenno@cisco.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/DVaCm3x05ExP-p1wCjBhYt9ZVWk
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] Discussion about Closing PCP WG
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, 18 Jul 2014 14:10:27 -0000

Hi Reinaldo,

I think we should send the PCP Security document to WG last call before =
closing the working group.  The work is nearly complete, and hopefully a =
last call would thresh out any remaining issues.  I would strongly =
prefer that we do not declare the PCP work to be complete without any =
published security solution.

Thanks,
Margaret


On Jul 17, 2014, at 1:50 AM, Reinaldo Penno (repenno) =
<repenno@cisco.com> wrote:

> The chairs and AD have been discussing the lack of activity on the =
mailing
> list compounded with the low number of agenda requests and lack of any
> agenda requests for WG documents.
>=20
> Therefore we propose that after Server Selection and Anycast drafts =
are
> done it would be a good point to close the WG. This has been a very
> successful WG, we delivered what was in the original charter, adapted
> quickly to incorporate new documents and delivered those.
>=20
>=20
> Furthermore we would propose to hold a webex interim meeting in lieu =
of
> the f2f meeting at the IETF. The WebEx interim meeting will be =
scheduled
> to occur shortly after WGLC completes on the Server Selection draft, =
and
> we plan to start the WGLC shortly.
>=20
> The two agenda requests we received for discussion of new individual
> drafts would be deferred to the interim meeting.
>=20
> If you feel that closing the WG is premature, we need to see real =
progress
> on other WG documents.
>=20
>=20
> Thanks,
>=20
> Reinaldo, Dave & Ted.
>=20
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From nobody Fri Jul 18 13:33:27 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 C5DF81A01E0 for <pcp@ietfa.amsl.com>; Fri, 18 Jul 2014 13:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 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.001, 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 U7lWerCndDT4 for <pcp@ietfa.amsl.com>; Fri, 18 Jul 2014 13:33:20 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AE141A00C3 for <pcp@ietf.org>; Fri, 18 Jul 2014 13:33:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1961; q=dns/txt; s=iport; t=1405715601; x=1406925201; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=VuBmtCoqex3fnFUCGv5D3VTWTU2FD4i3XcGBfsnaG4Q=; b=Ihy5nkEvnPdUlvMJAMFclrPnB77khCOjjto7KUUH2cJMHFOQmOQFQjly 9Ajhrj81brJI9k1nqlKlLwknsyVBv/U6VikBowX0XItFJlKMDutN6wO4d hik/60PU9EhM40NbweJj49XgBZ/2lEodaS6Rt725tBag2V4nRiM79IKVi 4=;
X-IronPort-AV: E=Sophos;i="5.01,687,1400025600"; d="scan'208";a="341159808"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-8.cisco.com with ESMTP; 18 Jul 2014 20:33:21 +0000
Received: from [10.21.72.30] ([10.21.72.30]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s6IKXHcB025588 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 18 Jul 2014 20:33:18 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <C388038D-1DA9-4934-979E-E8054FD82D11@gmail.com>
Date: Fri, 18 Jul 2014 13:33:17 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6CCBA472-0B08-45E5-A245-536E3CA37B50@cisco.com>
References: <CFECB216.D03B%repenno@cisco.com> <C388038D-1DA9-4934-979E-E8054FD82D11@gmail.com>
To: Margaret Wasserman <margaretw42@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/vwoyKQqoK-m4E-7vOLvx39MQ3sc
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] Discussion about Closing PCP WG
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, 18 Jul 2014 20:33:26 -0000

On Jul 18, 2014, at 7:10 AM, Margaret Wasserman <margaretw42@gmail.com> =
wrote:

> Hi Reinaldo,
>=20
> I think we should send the PCP Security document to WG last call =
before closing the working group.  The work is nearly complete, and =
hopefully a last call would thresh out any remaining issues.  I would =
strongly prefer that we do not declare the PCP work to be complete =
without any published security solution.

Agreed.

-d


>=20
> Thanks,
> Margaret
>=20
>=20
> On Jul 17, 2014, at 1:50 AM, Reinaldo Penno (repenno) =
<repenno@cisco.com> wrote:
>=20
>> The chairs and AD have been discussing the lack of activity on the =
mailing
>> list compounded with the low number of agenda requests and lack of =
any
>> agenda requests for WG documents.
>>=20
>> Therefore we propose that after Server Selection and Anycast drafts =
are
>> done it would be a good point to close the WG. This has been a very
>> successful WG, we delivered what was in the original charter, adapted
>> quickly to incorporate new documents and delivered those.
>>=20
>>=20
>> Furthermore we would propose to hold a webex interim meeting in lieu =
of
>> the f2f meeting at the IETF. The WebEx interim meeting will be =
scheduled
>> to occur shortly after WGLC completes on the Server Selection draft, =
and
>> we plan to start the WGLC shortly.
>>=20
>> The two agenda requests we received for discussion of new individual
>> drafts would be deferred to the interim meeting.
>>=20
>> If you feel that closing the WG is premature, we need to see real =
progress
>> on other WG documents.
>>=20
>>=20
>> Thanks,
>>=20
>> Reinaldo, Dave & Ted.
>>=20
>> _______________________________________________
>> 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 nobody Sat Jul 19 23:49:00 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 720E41B2B72 for <pcp@ietfa.amsl.com>; Sat, 19 Jul 2014 23:48:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 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.001, 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 ofU7VaD3CA4E for <pcp@ietfa.amsl.com>; Sat, 19 Jul 2014 23:48:58 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9AF21B2B71 for <pcp@ietf.org>; Sat, 19 Jul 2014 23:48:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2522; q=dns/txt; s=iport; t=1405838938; x=1407048538; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=PFft9Juj55ncjLlMV4dDNdou3ompIma1iWcQBoSuBa8=; b=Vx1x9cpr+2T+fWqcT0Ca5VJuVIMsAaO86RwEivgArIyBpRp32gODQ6OK 06koYm0kQqPiPXUZlFJA6TFiASI3kkbS/G6Fo/HrALKMo/AjcssCmnyBE Dkr8Cf8QcyscLtbpaivvXBSQork+kWOMXYjCr0IZ4h9TuTYlYVvL7iPjJ k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjMFAPxky1OtJA2F/2dsb2JhbABZgw5SVwTFCAqHRAGBBxZ2hAMBAQEEAQEBNzQLDAQCAQgRBAEBAQoUECEGCx0IAgQBDQUIE4gTAxENuwYNhyMTBI0egXwxBwaDKIEYAQSZIpAWhhyDRGyBRQ
X-IronPort-AV: E=Sophos;i="5.01,694,1400025600"; d="scan'208";a="62365137"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-6.cisco.com with ESMTP; 20 Jul 2014 06:48:57 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id s6K6mvnw016926 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 20 Jul 2014 06:48:57 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.102]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0123.003; Sun, 20 Jul 2014 01:48:56 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "Dan Wing (dwing)" <dwing@cisco.com>, Margaret Wasserman <margaretw42@gmail.com>
Thread-Topic: [pcp] Discussion about Closing PCP WG
Thread-Index: AQHPo4OsKvQ5DWewIEmK8sSUSBHcppuohGEA
Date: Sun, 20 Jul 2014 06:48:56 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A282F5C32@xmb-rcd-x10.cisco.com>
References: <CFECB216.D03B%repenno@cisco.com> <C388038D-1DA9-4934-979E-E8054FD82D11@gmail.com> <6CCBA472-0B08-45E5-A245-536E3CA37B50@cisco.com>
In-Reply-To: <6CCBA472-0B08-45E5-A245-536E3CA37B50@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.207.217]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/vNAkiZNLPg8Dr5qfKoAXg2v7BnU
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] Discussion about Closing PCP WG
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: Sun, 20 Jul 2014 06:48:59 -0000

In addition to PCP Authentication other pending WG documents should also be=
 taken to completion.  I see various interesting individual drafts like dra=
ft-boucadair-pcp-sfc-classifier-control-00, draft-chen-pcp-authentication-s=
im-00 etc. it seems too early to close the WG.

-Tiru

> -----Original Message-----
> From: Dan Wing (dwing)
> Sent: Saturday, July 19, 2014 2:03 AM
> To: Margaret Wasserman
> Cc: pcp@ietf.org
> Subject: Re: [pcp] Discussion about Closing PCP WG
>=20
> On Jul 18, 2014, at 7:10 AM, Margaret Wasserman <margaretw42@gmail.com>
> wrote:
>=20
> > Hi Reinaldo,
> >
> > I think we should send the PCP Security document to WG last call before
> closing the working group.  The work is nearly complete, and hopefully a =
last call
> would thresh out any remaining issues.  I would strongly prefer that we d=
o not
> declare the PCP work to be complete without any published security soluti=
on.
>=20
> Agreed.
>=20
> -d
>=20
>=20
> >
> > Thanks,
> > Margaret
> >
> >
> > On Jul 17, 2014, at 1:50 AM, Reinaldo Penno (repenno) <repenno@cisco.co=
m>
> wrote:
> >
> >> The chairs and AD have been discussing the lack of activity on the
> >> mailing list compounded with the low number of agenda requests and
> >> lack of any agenda requests for WG documents.
> >>
> >> Therefore we propose that after Server Selection and Anycast drafts
> >> are done it would be a good point to close the WG. This has been a
> >> very successful WG, we delivered what was in the original charter,
> >> adapted quickly to incorporate new documents and delivered those.
> >>
> >>
> >> Furthermore we would propose to hold a webex interim meeting in lieu
> >> of the f2f meeting at the IETF. The WebEx interim meeting will be
> >> scheduled to occur shortly after WGLC completes on the Server
> >> Selection draft, and we plan to start the WGLC shortly.
> >>
> >> The two agenda requests we received for discussion of new individual
> >> drafts would be deferred to the interim meeting.
> >>
> >> If you feel that closing the WG is premature, we need to see real
> >> progress on other WG documents.
> >>
> >>
> >> Thanks,
> >>
> >> Reinaldo, Dave & Ted.
> >>
> >> _______________________________________________
> >> 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
>=20


From nobody Sun Jul 20 04:54:32 2014
Return-Path: <Ted.Lemon@nominum.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 5F84C1B2BBD for <pcp@ietfa.amsl.com>; Sun, 20 Jul 2014 04:54:30 -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, RP_MATCHES_RCVD=-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 tOQ8WQAm08qS for <pcp@ietfa.amsl.com>; Sun, 20 Jul 2014 04:54:29 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E88C01B2BBE for <pcp@ietf.org>; Sun, 20 Jul 2014 04:54:28 -0700 (PDT)
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 B3CFB1B8724 for <pcp@ietf.org>; Sun, 20 Jul 2014 04:54:28 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (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 ESMTP id 67BCB190060; Sun, 20 Jul 2014 04:54:28 -0700 (PDT)
Received: from [192.168.0.10] (99.232.25.196) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 20 Jul 2014 04:54:27 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A282F5C32@xmb-rcd-x10.cisco.com>
Date: Sun, 20 Jul 2014 07:54:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <11D98142-2566-4B9B-BD34-877E0A89F6FD@nominum.com>
References: <CFECB216.D03B%repenno@cisco.com> <C388038D-1DA9-4934-979E-E8054FD82D11@gmail.com> <6CCBA472-0B08-45E5-A245-536E3CA37B50@cisco.com> <913383AAA69FF945B8F946018B75898A282F5C32@xmb-rcd-x10.cisco.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [99.232.25.196]
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/DwXk5DQyFeqIdzqUgmPcHv8GVSE
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] Discussion about Closing PCP WG
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: Sun, 20 Jul 2014 11:54:30 -0000

On Jul 20, 2014, at 2:48 AM, Tirumaleswar Reddy (tireddy) =
<tireddy@cisco.com> wrote:
> In addition to PCP Authentication other pending WG documents should =
also be taken to completion.  I see various interesting individual =
drafts like draft-boucadair-pcp-sfc-classifier-control-00, =
draft-chen-pcp-authentication-sim-00 etc. it seems too early to close =
the WG.

The trick with taking work to completion is that the work has to be =
worked on; I think what the chairs were getting at is that they feel =
there's no energy to do the work.   If that's not the case, the way to =
show us that is to do the work, not to say that the work needs to be =
done. :)

That said, the two drafts you mentioned are not pcp working group =
documents.


From nobody Sun Jul 20 10:36:18 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 F389E1B28E8 for <pcp@ietfa.amsl.com>; Sun, 20 Jul 2014 10:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 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.001, 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 QcsqETYa3x62 for <pcp@ietfa.amsl.com>; Sun, 20 Jul 2014 10:36:15 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8F021B28E1 for <pcp@ietf.org>; Sun, 20 Jul 2014 10:36:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1173; q=dns/txt; s=iport; t=1405877775; x=1407087375; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=+DTZsus8vEkA+toR5Ohw2IwBNLAfI+YM8IY2M/XMA3w=; b=RZh8wqQuyyvqlZ3eWtO35EmuQ11975lMxjiV5ae+3K3pjEHh8ZukDbJH MCeay4bVcqZmU9rIWiwyxdaBPicRuWCp3Q/NOSC/K53iYnStr/b9Ae0p3 hAyWa70IkeGw0AtxxHxPGkf0ggRr4HzaCJGJFZxrr/yUMRZGEK0byzbfb U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAJX9y1OtJA2D/2dsb2JhbABZgw6BLcxgAYEGFnaEAwEBAQMBOj8MBgEIEQQBAQEKFAk5FAkJAQQOBQiIMgjBERePGjENgyiBGAEEr1SDRGyBRQ
X-IronPort-AV: E=Sophos;i="5.01,696,1400025600"; d="scan'208";a="341463967"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-8.cisco.com with ESMTP; 20 Jul 2014 17:36:15 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s6KHaF6a003034 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 20 Jul 2014 17:36:15 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.102]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0123.003; Sun, 20 Jul 2014 12:36:14 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Ted Lemon <ted.lemon@nominum.com>
Thread-Topic: [pcp] Discussion about Closing PCP WG
Thread-Index: Ac+kQRReHbvhTFfTRAKbhXM6ezo21g==
Date: Sun, 20 Jul 2014 17:36:14 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A282F5EA7@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.48.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/h0w9ogzWh1Arw7-L6vYHV3RZIHw
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] Discussion about Closing PCP WG
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: Sun, 20 Jul 2014 17:36:17 -0000

> -----Original Message-----
> From: Ted Lemon [mailto:ted.lemon@nominum.com]
> Sent: Sunday, July 20, 2014 5:24 PM
> To: Tirumaleswar Reddy (tireddy)
> Cc: Dan Wing (dwing); Margaret Wasserman; pcp@ietf.org
> Subject: Re: [pcp] Discussion about Closing PCP WG
>=20
> On Jul 20, 2014, at 2:48 AM, Tirumaleswar Reddy (tireddy) <tireddy@cisco.=
com>
> wrote:
> > In addition to PCP Authentication other pending WG documents should als=
o be
> taken to completion.  I see various interesting individual drafts like dr=
aft-
> boucadair-pcp-sfc-classifier-control-00, draft-chen-pcp-authentication-si=
m-00
> etc. it seems too early to close the WG.
>=20
> The trick with taking work to completion is that the work has to be worke=
d on; I
> think what the chairs were getting at is that they feel there's no energy=
 to do the
> work.   If that's not the case, the way to show us that is to do the work=
, not to
> say that the work needs to be done. :)

Agreed. I will review PCP Proxy and PCP Auth drafts early next month and po=
st my comments.

-Tiru

>=20
> That said, the two drafts you mentioned are not pcp working group documen=
ts.


From nobody Sun Jul 20 10:51:35 2014
Return-Path: <dthaler@microsoft.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 E47BD1B291B for <pcp@ietfa.amsl.com>; Sun, 20 Jul 2014 10:51:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.602
X-Spam-Level: 
X-Spam-Status: No, score=-102.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 SR9R-Y21YKHj for <pcp@ietfa.amsl.com>; Sun, 20 Jul 2014 10:51:30 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0244.outbound.protection.outlook.com [207.46.163.244]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C76A41B2919 for <pcp@ietf.org>; Sun, 20 Jul 2014 10:51:30 -0700 (PDT)
Received: from BY2PR03MB412.namprd03.prod.outlook.com (10.141.141.25) by BY2PR03MB409.namprd03.prod.outlook.com (10.141.141.11) with Microsoft SMTP Server (TLS) id 15.0.990.7; Sun, 20 Jul 2014 17:51:29 +0000
Received: from BY2PR03MB412.namprd03.prod.outlook.com ([10.141.141.25]) by BY2PR03MB412.namprd03.prod.outlook.com ([10.141.141.25]) with mapi id 15.00.0990.007; Sun, 20 Jul 2014 17:51:29 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Thread-Topic: [pcp] Discussion about Closing PCP WG
Thread-Index: Ac+kQRReCP/Gj5Y9hkitXO7sLwNpIwAAWFdQ
Date: Sun, 20 Jul 2014 17:51:28 +0000
Message-ID: <86fd91ac72324d14963805df0e1e65fc@BY2PR03MB412.namprd03.prod.outlook.com>
References: <913383AAA69FF945B8F946018B75898A282F5EA7@xmb-rcd-x10.cisco.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A282F5EA7@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [31.133.163.94]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 02788FF38E
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(377454003)(189002)(51704005)(13464003)(199002)(24454002)(86362001)(74502001)(2656002)(80022001)(81542001)(92566001)(74316001)(85306003)(81342001)(83072002)(87936001)(83322001)(85852003)(106356001)(95666004)(31966008)(66066001)(79102001)(4396001)(77982001)(20776003)(21056001)(101416001)(99286002)(19580405001)(99396002)(15975445006)(74662001)(110136001)(54356999)(86612001)(76576001)(76176999)(64706001)(50986999)(46102001)(107046002)(105586002)(19580395003)(76482001)(33646002)(108616002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR03MB409; H:BY2PR03MB412.namprd03.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/QsqB6DDhhMSywLCaXIIk_k-ORxY
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] Discussion about Closing PCP WG
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: Sun, 20 Jul 2014 17:51:33 -0000

I would love to see the other WG documents make progress.

The DHCP document was just published (thanks to those who
Worked on that one!)

Two WG documents are making good progress and don't need
face to face discussion this week:
port-set is likely to be handed to the IESG this week
server-selection should start WGLC as soon as the update is posted.
Other than those two, we haven't seen any progress on other
WG docs since last IETF.

I completely agree that it would be good to finish auth, but we
need to see progress/energy/discussion around the doc or there's
not much we can do.

So we propose to hold an interim webex meeting in late August
after WGLC on server selection completes.

-Dave

> -----Original Message-----
> From: pcp [mailto:pcp-bounces@ietf.org] On Behalf Of Tirumaleswar Reddy
> (tireddy)
> Sent: Sunday, July 20, 2014 1:36 PM
> To: Ted Lemon
> Cc: pcp@ietf.org
> Subject: Re: [pcp] Discussion about Closing PCP WG
>=20
> > -----Original Message-----
> > From: Ted Lemon [mailto:ted.lemon@nominum.com]
> > Sent: Sunday, July 20, 2014 5:24 PM
> > To: Tirumaleswar Reddy (tireddy)
> > Cc: Dan Wing (dwing); Margaret Wasserman; pcp@ietf.org
> > Subject: Re: [pcp] Discussion about Closing PCP WG
> >
> > On Jul 20, 2014, at 2:48 AM, Tirumaleswar Reddy (tireddy)
> > <tireddy@cisco.com>
> > wrote:
> > > In addition to PCP Authentication other pending WG documents should
> > > also be
> > taken to completion.  I see various interesting individual drafts like
> > draft- boucadair-pcp-sfc-classifier-control-00,
> > draft-chen-pcp-authentication-sim-00
> > etc. it seems too early to close the WG.
> >
> > The trick with taking work to completion is that the work has to be
> > worked on; I think what the chairs were getting at is that they feel th=
ere's
> no energy to do the
> > work.   If that's not the case, the way to show us that is to do the wo=
rk, not
> to
> > say that the work needs to be done. :)
>=20
> Agreed. I will review PCP Proxy and PCP Auth drafts early next month and =
post
> my comments.
>=20
> -Tiru
>=20
> >
> > That said, the two drafts you mentioned are not pcp working group
> documents.
>=20
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From nobody Sun Jul 20 18:54:15 2014
Return-Path: <zhang_dacheng@hotmail.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 6D7C21B2AC4 for <pcp@ietfa.amsl.com>; Sun, 20 Jul 2014 18:54:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.448
X-Spam-Level: **
X-Spam-Status: No, score=2.448 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FREEMAIL_FROM=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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 BVB3lRc-bynG for <pcp@ietfa.amsl.com>; Sun, 20 Jul 2014 18:54:10 -0700 (PDT)
Received: from BLU004-OMC2S33.hotmail.com (blu004-omc2s33.hotmail.com [65.55.111.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D86E31B2ABE for <pcp@ietf.org>; Sun, 20 Jul 2014 18:54:09 -0700 (PDT)
Received: from BLU436-SMTP160 ([65.55.111.72]) by BLU004-OMC2S33.hotmail.com with Microsoft SMTPSVC(7.5.7601.22712);  Sun, 20 Jul 2014 18:54:09 -0700
X-TMN: [pKL1qQawDQtwOK8Ki8lTQ3msY4MUFU2L]
X-Originating-Email: [zhang_dacheng@hotmail.com]
Message-ID: <BLU436-SMTP160D767D9F6D8DA38BFCCC388F00@phx.gbl>
Received: from dhcp-9316.meeting.ietf.org ([31.133.147.22]) by BLU436-SMTP160.smtp.hotmail.com over TLS secured channel with Microsoft SMTPSVC(8.0.9200.16384); Sun, 20 Jul 2014 18:54:07 -0700
MIME-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="GB2312"
From: Dacheng Zhang <zhang_dacheng@hotmail.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A282F5EA7@xmb-rcd-x10.cisco.com>
Date: Mon, 21 Jul 2014 09:54:08 +0800
Content-Transfer-Encoding: quoted-printable
References: <913383AAA69FF945B8F946018B75898A282F5EA7@xmb-rcd-x10.cisco.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
X-Mailer: Apple Mail (2.1283)
X-OriginalArrivalTime: 21 Jul 2014 01:54:07.0713 (UTC) FILETIME=[A8889510:01CFA486]
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/3wb_N9blRDeMzq7eLk3lVysvTq4
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] Discussion about Closing PCP WG
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, 21 Jul 2014 01:54:13 -0000

Thanks. I will definitly make an update by the end of this month.=20


=D4=DA 2014-7-21=A3=AC=C9=CF=CE=E71:36=A3=AC Tirumaleswar Reddy =
(tireddy) =D0=B4=B5=C0=A3=BA

>> -----Original Message-----
>> From: Ted Lemon [mailto:ted.lemon@nominum.com]
>> Sent: Sunday, July 20, 2014 5:24 PM
>> To: Tirumaleswar Reddy (tireddy)
>> Cc: Dan Wing (dwing); Margaret Wasserman; pcp@ietf.org
>> Subject: Re: [pcp] Discussion about Closing PCP WG
>>=20
>> On Jul 20, 2014, at 2:48 AM, Tirumaleswar Reddy (tireddy) =
<tireddy@cisco.com>
>> wrote:
>>> In addition to PCP Authentication other pending WG documents should =
also be
>> taken to completion.  I see various interesting individual drafts =
like draft-
>> boucadair-pcp-sfc-classifier-control-00, =
draft-chen-pcp-authentication-sim-00
>> etc. it seems too early to close the WG.
>>=20
>> The trick with taking work to completion is that the work has to be =
worked on; I
>> think what the chairs were getting at is that they feel there's no =
energy to do the
>> work.   If that's not the case, the way to show us that is to do the =
work, not to
>> say that the work needs to be done. :)
>=20
> Agreed. I will review PCP Proxy and PCP Auth drafts early next month =
and post my comments.
>=20
> -Tiru
>=20
>>=20
>> That said, the two drafts you mentioned are not pcp working group =
documents.
>=20
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp
>=20


From nobody Sun Jul 20 22:45:26 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 C07301B2DBD; Sun, 20 Jul 2014 22:45:10 -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 tJwpEFZPjPTi; Sun, 20 Jul 2014 22:45:03 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B2101B2DB6; Sun, 20 Jul 2014 22:44:45 -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.6.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140721054445.14855.91521.idtracker@ietfa.amsl.com>
Date: Sun, 20 Jul 2014 22:44:45 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/_qRBVr9uwMnkg6S4OWz-y7TKzFM
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-server-selection-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: Mon, 21 Jul 2014 05:45:12 -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           : PCP Server Selection
        Authors         : Mohamed Boucadair
                          Reinaldo Penno
                          Dan Wing
                          Prashanth Patil
                          Tirumaleswar Reddy
	Filename        : draft-ietf-pcp-server-selection-04.txt
	Pages           : 11
	Date            : 2014-07-20

Abstract:
   The document specifies the behavior to be followed by a PCP client to
   contact its PCP server(s) when one or several PCP server IP addresses
   are configured.

   This document updates RFC6887.



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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-pcp-server-selection-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 nobody Mon Jul 21 04:30:21 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 4C9421B2D6C; Mon, 21 Jul 2014 04:30:19 -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 79AOU9fwEub7; Mon, 21 Jul 2014 04:30:18 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 19DE21B2D4D; Mon, 21 Jul 2014 04:30:18 -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.6.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140721113018.27784.76939.idtracker@ietfa.amsl.com>
Date: Mon, 21 Jul 2014 04:30:18 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/PX7cYXJPJFCv0DB1I5MBIrw8m1Q
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-port-set-06.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: Mon, 21 Jul 2014 11:30:19 -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-06.txt
	Pages           : 17
	Date            : 2014-07-21

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

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


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 Jul 21 06:29:19 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 0EF6E1B2DF0; Mon, 21 Jul 2014 06:29:12 -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 vMJpeg1rgQkF; Mon, 21 Jul 2014 06:29:04 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 383971B2BDD; Mon, 21 Jul 2014 06:27:17 -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.6.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140721132717.8597.69523.idtracker@ietfa.amsl.com>
Date: Mon, 21 Jul 2014 06:27:17 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/XETukrzF-eVPWj6fC5ZY2c9KaPo
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-authentication-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: Mon, 21 Jul 2014 13:29:12 -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) Authentication Mechanism
        Authors         : Margaret Wasserman
                          Sam Hartman
                          Dacheng Zhang
	Filename        : draft-ietf-pcp-authentication-04.txt
	Pages           : 24
	Date            : 2014-07-21

Abstract:
   An IPv4 or IPv6 host can use the Port Control Protocol (PCP) to
   flexibly manage the IP address and port mapping information on
   Network Address Translators (NATs) or firewalls, to facilitate
   communications with remote hosts.  However, the un-controlled
   generation or deletion of IP address mappings on such network devices
   may cause security risks and should be avoided.  In some cases the
   client may need to prove that it is authorized to modify, create or
   delete PCP mappings.  This document proposes an in-band
   authentication mechanism for PCP that can be used in those cases.
   The Extensible Authentication Protocol (EAP) is used to perform
   authentication between PCP devices.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-pcp-authentication-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 nobody Mon Jul 21 06:43:04 2014
Return-Path: <trac@tools.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 E87DD1B2E13 for <pcp@ietfa.amsl.com>; Mon, 21 Jul 2014 06:42:47 -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, RP_MATCHES_RCVD=-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 rc0CVBQ_xwLl for <pcp@ietfa.amsl.com>; Mon, 21 Jul 2014 06:42:41 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38ABF1B2E29 for <pcp@ietf.org>; Mon, 21 Jul 2014 06:38:45 -0700 (PDT)
Received: from localhost ([::1]:38324 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac@tools.ietf.org>) id 1X9DnX-0000LU-I7; Mon, 21 Jul 2014 06:38:35 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "pcp issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-pcp-port-set@tools.ietf.org, dthaler@microsoft.com
X-Trac-Project: pcp
Date: Mon, 21 Jul 2014 13:38:35 -0000
X-URL: http://tools.ietf.org/pcp/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/pcp/trac/ticket/69#comment:1
Message-ID: <074.619f0afe2723765ff038f3e5f13cbacd@tools.ietf.org>
References: <059.3374a8816348b43c84919b7b9ca03a7f@tools.ietf.org>
X-Trac-Ticket-ID: 69
In-Reply-To: <059.3374a8816348b43c84919b7b9ca03a7f@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-pcp-port-set@tools.ietf.org, dthaler@microsoft.com, pcp@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: cathy.zhou@huawei.com, mohamed.boucadair@orange.com, sperreault@jive.com, ssenthil@cisco.com, sunqiong@ctbri.com.cn, tina.tsou.zouting@huawei.com
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/UQ9Vz5GE3iIm_scRKtTLklHde24
Cc: pcp@ietf.org
Subject: Re: [pcp] #69 (port-set): Dave Thaler comments on draft-ietf-pcp-port-set-04
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: Mon, 21 Jul 2014 13:42:48 -0000

#69: Dave Thaler comments on draft-ietf-pcp-port-set-04

Changes (by dthaler@microsoft.com):

 * status:  new => closed
 * resolution:   => fixed
 * severity:  Active WG Document => In WG Last Call


Comment:

 Addressed in -06

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-pcp-port-
  dthaler@microsoft.com  |  set@tools.ietf.org
     Type:  defect       |      Status:  closed
 Priority:  major        |   Milestone:  milestone1
Component:  port-set     |     Version:  1.0
 Severity:  In WG Last   |  Resolution:  fixed
  Call                   |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/pcp/trac/ticket/69#comment:1>
pcp <http://tools.ietf.org/pcp/>


From nobody Mon Jul 21 06:43:45 2014
Return-Path: <trac@tools.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 EE11C1B2BE7 for <pcp@ietfa.amsl.com>; Mon, 21 Jul 2014 06:43:36 -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, RP_MATCHES_RCVD=-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 GeDA0g2VspeS for <pcp@ietfa.amsl.com>; Mon, 21 Jul 2014 06:43:31 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8E721B2BEE for <pcp@ietf.org>; Mon, 21 Jul 2014 06:40:01 -0700 (PDT)
Received: from localhost ([::1]:38374 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac@tools.ietf.org>) id 1X9Dor-0000ex-F0; Mon, 21 Jul 2014 06:39:57 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "pcp issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-pcp-server-selection@tools.ietf.org, dthaler@microsoft.com
X-Trac-Project: pcp
Date: Mon, 21 Jul 2014 13:39:57 -0000
X-URL: http://tools.ietf.org/pcp/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/pcp/trac/ticket/66#comment:1
Message-ID: <079.673819502d606e87cb22f4c3b6a0d76b@tools.ietf.org>
References: <064.7b3a3e19faa89c6a5e8c0ab56fb13946@tools.ietf.org>
X-Trac-Ticket-ID: 66
In-Reply-To: <064.7b3a3e19faa89c6a5e8c0ab56fb13946@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-pcp-server-selection@tools.ietf.org, dthaler@microsoft.com, pcp@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: dwing@cisco.com, mohamed.boucadair@orange.com, praspati@cisco.com,  repenno@cisco.com, tireddy@cisco.com
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/qAohPqvoJ2j68FNsGyQJhkgaZZI
Cc: pcp@ietf.org
Subject: Re: [pcp] #66 (server-selection): server-selection comments from Hassnaa Moustafa
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: Mon, 21 Jul 2014 13:43:37 -0000

#66: server-selection comments from Hassnaa Moustafa

Changes (by dthaler@microsoft.com):

 * status:  new => closed
 * resolution:   => fixed
 * severity:  In WG Last Call => Active WG Document


Comment:

 Addressed in -04

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |       Owner:  draft-ietf-pcp-server-
  hassnaa.moustafa@intel.com         |  selection@tools.ietf.org
     Type:  defect                   |      Status:  closed
 Priority:  minor                    |   Milestone:  milestone1
Component:  server-selection         |     Version:  1.0
 Severity:  Active WG Document       |  Resolution:  fixed
 Keywords:                           |
-------------------------------------+-------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/pcp/trac/ticket/66#comment:1>
pcp <http://tools.ietf.org/pcp/>


From nobody Mon Jul 21 06:55:49 2014
Return-Path: <dthaler@microsoft.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 7C9D81A007C for <pcp@ietfa.amsl.com>; Mon, 21 Jul 2014 06:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.602
X-Spam-Level: 
X-Spam-Status: No, score=-102.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 c-GMb2qlZj7v for <pcp@ietfa.amsl.com>; Mon, 21 Jul 2014 06:55:39 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0241.outbound.protection.outlook.com [207.46.163.241]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B6001A0007 for <pcp@ietf.org>; Mon, 21 Jul 2014 06:52:48 -0700 (PDT)
Received: from BY2PR03MB412.namprd03.prod.outlook.com (10.141.141.25) by BY2PR03MB409.namprd03.prod.outlook.com (10.141.141.11) with Microsoft SMTP Server (TLS) id 15.0.990.7; Mon, 21 Jul 2014 13:52:46 +0000
Received: from BY2PR03MB412.namprd03.prod.outlook.com ([10.141.141.25]) by BY2PR03MB412.namprd03.prod.outlook.com ([10.141.141.25]) with mapi id 15.00.0990.007; Mon, 21 Jul 2014 13:52:46 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: WGLC: draft-ietf-pcp-server-selection-04.txt comments due by AUG 18
Thread-Index: Ac+k6q786HDy4hc9ST28nwMIu/iDVQ==
Date: Mon, 21 Jul 2014 13:52:46 +0000
Message-ID: <b8f62d41c0da4327ad79bada16a3b8a2@BY2PR03MB412.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [31.133.163.94]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 0279B3DD0D
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(377454003)(13464003)(164054003)(377424004)(199002)(189002)(85306003)(99286002)(95666004)(15202345003)(105586002)(106356001)(86362001)(66066001)(46102001)(15975445006)(20776003)(76482001)(64706001)(33646002)(80022001)(110136001)(86612001)(81542001)(81342001)(85852003)(74662001)(74316001)(74502001)(229853001)(19580395003)(77982001)(101416001)(76576001)(79102001)(92566001)(87936001)(83072002)(99396002)(21056001)(2656002)(4396001)(2351001)(50986999)(54356999)(107046002)(83322001)(31966008)(19580405001)(107886001)(108616002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR03MB409; H:BY2PR03MB412.namprd03.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/LANaMXo_21bPJ-m0cC37WJP6oKY
Subject: [pcp] WGLC: draft-ietf-pcp-server-selection-04.txt comments due by AUG 18
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, 21 Jul 2014 13:55:44 -0000

-02 of this document went through a WGLC back in February but has had some
significant changes since then.  This email initiates a new Working Group L=
ast Call on
draft-ietf-pcp-server-selection-04 to conclude on Monday, August 18th.
We believe that this should give sufficient time to review, taking into acc=
ount
IETF week and various travel plans.  Please send comments to the list.

As a reminder, when responding to a WGLC, what we chairs are looking for is=
 a statement=20
about 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,
-Dave

-----Original Message-----
From: pcp [mailto:pcp-bounces@ietf.org] On Behalf Of internet-drafts@ietf.o=
rg
Sent: Monday, July 21, 2014 1:45 AM
To: i-d-announce@ietf.org
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-server-selection-04.txt


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           : PCP Server Selection
        Authors         : Mohamed Boucadair
                          Reinaldo Penno
                          Dan Wing
                          Prashanth Patil
                          Tirumaleswar Reddy
	Filename        : draft-ietf-pcp-server-selection-04.txt
	Pages           : 11
	Date            : 2014-07-20

Abstract:
   The document specifies the behavior to be followed by a PCP client to
   contact its PCP server(s) when one or several PCP server IP addresses
   are configured.

   This document updates RFC6887.



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

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

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


Please note that it may take a couple of minutes from the time of submissio=
n 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 nobody Mon Jul 21 07:17:32 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 822F21A001D for <pcp@ietfa.amsl.com>; Mon, 21 Jul 2014 07:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 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.001, 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 kAaFtxCez_cR for <pcp@ietfa.amsl.com>; Mon, 21 Jul 2014 07:17:16 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B77A1A0008 for <pcp@ietf.org>; Mon, 21 Jul 2014 07:17:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3198; q=dns/txt; s=iport; t=1405952236; x=1407161836; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=FkIdMPa/z/2jiKIQwzAVMBZQujecykjq3niSiqujh+Q=; b=PpwLMycISl4CL5JgBZTIvZwPc001zJGoueTXIMQD07l39m36mWjvHE/i jMAQsO4+Fin6t5CtsEC9U35esuJBJgpvP/HGOHYmxpF9iHty235z5lNBC 26dux7jnuVk/+tJd5FN19E/64uEHP0MT11XOrm0TBoYqad7o+WnJtmGqw o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFALwfzVOtJV2Z/2dsb2JhbABZgw5SW4J0wlyHQQEZfRZ2hAMBAQECAQEjEUMHBwYBCBEDAQEBAwIGDg8DAgQfERQBCAkBBAESCAGIJQMJCA2nSo9WDYcjF4Esi1wWgXwWKBKCYDaBGAWXB4Ibg1CMRoYcggKBQmwBgUQ
X-IronPort-AV: E=Sophos;i="5.01,701,1400025600"; d="scan'208";a="341670125"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-3.cisco.com with ESMTP; 21 Jul 2014 14:17:15 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s6LEHFIC019136 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 21 Jul 2014 14:17:15 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.102]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0123.003; Mon, 21 Jul 2014 09:17:15 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: GangChen <phdgang@gmail.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] Fwd: New Version Notification for draft-chen-pcp-authentication-sim-00.txt
Thread-Index: Ac+k7nNqTXulltUXSJy2fLmOyv1+RQ==
Date: Mon, 21 Jul 2014 14:17:14 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A282F66EC@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.61.193.86]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/qwNhJBCW59OC2qnsx_8VsHqq1Yo
Subject: Re: [pcp] Fwd: New Version Notification for draft-chen-pcp-authentication-sim-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: Mon, 21 Jul 2014 14:17:19 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBHYW5nQ2hlbiBbbWFpbHRvOnBo
ZGdhbmdAZ21haWwuY29tXQ0KPiBTZW50OiBGcmlkYXksIEp1bHkgMDQsIDIwMTQgMzo0MSBQTQ0K
PiBUbzogcGNwQGlldGYub3JnDQo+IFN1YmplY3Q6IFtwY3BdIEZ3ZDogTmV3IFZlcnNpb24gTm90
aWZpY2F0aW9uIGZvciBkcmFmdC1jaGVuLXBjcC1hdXRoZW50aWNhdGlvbi0NCj4gc2ltLTAwLnR4
dA0KPiANCj4gV0csDQo+IA0KPiBJIGhhdmUgc3VibWl0dGVkIGEgZHJhZnQgdG8gZGVzY3JpYmUg
dGhlIGNvbnNpZGVyYXRpb24gb2YgUENQIGF1dGhlbnRpY2F0aW9uDQo+IHdpdGggKFUpU0lNIHN1
cHBvcnQuIFRoZSBwcm9jZXNzIGlzIGRldGFpbGVkIGluIEVBUCBhbmQgR0JBIGZyYW1ld29yay4N
Cg0KSW50ZXJlc3RpbmcgZHJhZnQuIFRoaXMgc29sdmVzIHRoZSBwcm9ibGVtIHRoYXQgZm9yIFBD
UCBhdXRoZW50aWNhdGlvbiB0byB3b3JrIGluIE1vYmlsZSBuZXR3b3JrcywgUENQIGNsaWVudCBk
b2VzIG5vdCBoYXZlIHVzZSB1c2VybmFtZSBhbmQgcGFzc3dvcmQgYnV0IG9ubHkgdXNlIFNJTSBj
cmVkZW50aWFscyAoRUFQLVNJTSkuICBPdGhlciBvcGVyYXRvcnMgbGlrZSBEZXV0c2NoZS1UZWxl
a29tIGFyZSBhbHJlYWR5IHVzaW5nIFNJTSBhdXRoZW50aWNhdGlvbiBmb3IgSVNQIG9mZmVyZWQg
c2VydmljZXMgKFNsaWRlIDExIGh0dHA6Ly93d3cuZ3NtYS5jb20vcGVyc29uYWxkYXRhL3dwLWNv
bnRlbnQvdXBsb2Fkcy8yMDE0LzAzL09wZW5JRC1Db25uZWN0LWF0LURldXRzY2hlLVRlbGVrb20t
VG9yc3Rlbi1Mb2RkZXJzdGVkdC5wZGYpDQoNCi1UaXJ1DQoNCj4gVGhhbmsgeW91IGZvciB0aGUg
Y29tbWVudHMgaW4gYWR2YW5jZS4NCj4gDQo+IEJlc3QgUmVnYXJkcw0KPiANCj4gR2FuZw0KPiAN
Cj4gLS0tLS0tLS0tLSBGb3J3YXJkZWQgbWVzc2FnZSAtLS0tLS0tLS0tDQo+IEZyb206IGludGVy
bmV0LWRyYWZ0c0BpZXRmLm9yZw0KPiBEYXRlOiBGcmksIDA0IEp1bCAyMDE0IDAzOjAzOjA1IC0w
NzAwDQo+IFN1YmplY3Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtY2hlbi1w
Y3AtYXV0aGVudGljYXRpb24tc2ltLTAwLnR4dA0KPiBUbzogR2FuZyBDaGVuIDxwaGRnYW5nQGdt
YWlsLmNvbT4NCj4gDQo+IA0KPiBBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtY2hlbi1wY3At
YXV0aGVudGljYXRpb24tc2ltLTAwLnR4dA0KPiBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0
dGVkIGJ5IEdhbmcgQ2hlbiBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRvcnkuDQo+IA0K
PiBOYW1lOgkJZHJhZnQtY2hlbi1wY3AtYXV0aGVudGljYXRpb24tc2ltDQo+IFJldmlzaW9uOgkw
MA0KPiBUaXRsZToJCShVKVNJTSBiYXNlZCBQQ1AgQXV0aGVudGljYXRpb24NCj4gRG9jdW1lbnQg
ZGF0ZToJMjAxNC0wNy0wMw0KPiBHcm91cDoJCUluZGl2aWR1YWwgU3VibWlzc2lvbg0KPiBQYWdl
czoJCTgNCj4gVVJMOg0KPiBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFm
dC1jaGVuLXBjcC1hdXRoZW50aWNhdGlvbi1zaW0tMDAudHh0DQo+IFN0YXR1czoNCj4gaHR0cHM6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtY2hlbi1wY3AtYXV0aGVudGljYXRpb24t
c2ltLw0KPiBIdG1saXplZDogICAgICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQt
Y2hlbi1wY3AtYXV0aGVudGljYXRpb24tc2ltLTAwDQo+IA0KPiANCj4gQWJzdHJhY3Q6DQo+ICAg
IFdpdGggKFUpU0lNIHN1cHBvcnQsIFBDUCBhdXRoZW50aWNhdGlvbiBjb3VsZCBsZXZlcmFnZSB0
aGUNCj4gICAgY3JlZGVudGlhbHMgc3RvcmVkIGluIChVKVNJTS4gIFRoZSBkb2N1bWVudCBkZXRh
aWxzIFBDUA0KPiAgICBhdXRoZW50aWNhdGlvbiBjb25zaWRlcmF0aW9ucyBiYXNlZCBvbiAoVSlT
SU0gc3VwcG9ydC4gIFRoZQ0KPiAgICBhdXRoZW50aWNhdGlvbiBwcm9jZWR1cmVzIGluIEVBUCBh
bmQgR0JBIGZyYW1ld29yayBoYXZlIGJlZW4NCj4gICAgc3BlY2lmaWNhbGx5IGVsYWJvcmF0ZWQu
ICBJbiBvcmRlciB0byBjb21wbGV0ZSB0aGUgcHJvY2VzcywgbmV3IGNvZGUNCj4gICAgYW5kIG9w
dGlvbiBhcmUgYWxzbyBwcm9wb3NlZC4NCj4gDQo+IA0KPiANCj4gDQo+IFBsZWFzZSBub3RlIHRo
YXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1p
c3Npb24NCj4gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJs
ZSBhdCB0b29scy5pZXRmLm9yZy4NCj4gDQo+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQo+IA0KDQo=


From nobody Mon Jul 21 08:05:12 2014
Return-Path: <zhang_dacheng@hotmail.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 EC5E01A0208 for <pcp@ietfa.amsl.com>; Mon, 21 Jul 2014 08:05:08 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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 SQUOMJY9N1du for <pcp@ietfa.amsl.com>; Mon, 21 Jul 2014 08:05:03 -0700 (PDT)
Received: from BLU004-OMC3S1.hotmail.com (blu004-omc3s1.hotmail.com [65.55.116.76]) (using TLSv1.2 with cipher AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 967E71A01C6 for <pcp@ietf.org>; Mon, 21 Jul 2014 08:04:47 -0700 (PDT)
Received: from BLU436-SMTP171 ([65.55.116.73]) by BLU004-OMC3S1.hotmail.com with Microsoft SMTPSVC(7.5.7601.22712);  Mon, 21 Jul 2014 08:04:46 -0700
X-TMN: [RuBM02AiHdCGCK1ap6mes4IXNomQFhd9]
X-Originating-Email: [zhang_dacheng@hotmail.com]
Message-ID: <BLU436-SMTP17122E359DE03F7D50A210888F00@phx.gbl>
Received: from dhcp-a6cd.meeting.ietf.org ([31.133.166.205]) by BLU436-SMTP171.smtp.hotmail.com over TLS secured channel with Microsoft SMTPSVC(8.0.9200.16384); Mon, 21 Jul 2014 08:04:44 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Apple Message framework v1283)
From: Dacheng Zhang <zhang_dacheng@hotmail.com>
In-Reply-To: <20140721132717.8597.69523.idtracker@ietfa.amsl.com>
Date: Mon, 21 Jul 2014 11:04:43 -0400
Content-Transfer-Encoding: quoted-printable
References: <20140721132717.8597.69523.idtracker@ietfa.amsl.com>
To: pcp@ietf.org
X-Mailer: Apple Mail (2.1283)
X-OriginalArrivalTime: 21 Jul 2014 15:04:44.0718 (UTC) FILETIME=[1B311CE0:01CFA4F5]
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/hmpSpmcwzAv3lrFAKoKtmzpCmG4
Subject: [pcp]  I-D Action: draft-ietf-pcp-authentication-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: Mon, 21 Jul 2014 15:05:09 -0000

Hi, in this version of the document, we try to address the comments got =
since the last meeting.  Particularly, we:
   o  Refine the retransmission policies.

   o  Provide the discussion about how to instruct a PCP client to
      choose proper credential during authenticaiton, and an ID
      Indication Option is defined for that purpose.
In addition, it is advised that we should remove the key ID from the PCP =
authentication message, and only use one key for a PCP session. However, =
this indicates we will use the MSK to generate MACs for PCP message =
directly. We would like to check with the group again before including =
it into the document.=20

Any comments and suggestions are appreciated.

Cheers

Dacheng


>=20
> 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.
>=20
>        Title           : Port Control Protocol (PCP) Authentication =
Mechanism
>        Authors         : Margaret Wasserman
>                          Sam Hartman
>                          Dacheng Zhang
> 	Filename        : draft-ietf-pcp-authentication-04.txt
> 	Pages           : 24
> 	Date            : 2014-07-21
>=20
> Abstract:
>   An IPv4 or IPv6 host can use the Port Control Protocol (PCP) to
>   flexibly manage the IP address and port mapping information on
>   Network Address Translators (NATs) or firewalls, to facilitate
>   communications with remote hosts.  However, the un-controlled
>   generation or deletion of IP address mappings on such network =
devices
>   may cause security risks and should be avoided.  In some cases the
>   client may need to prove that it is authorized to modify, create or
>   delete PCP mappings.  This document proposes an in-band
>   authentication mechanism for PCP that can be used in those cases.
>   The Extensible Authentication Protocol (EAP) is used to perform
>   authentication between PCP devices.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-pcp-authentication/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-pcp-authentication-04
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcp-authentication-04
>=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
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp
>=20


From nobody Mon Jul 21 08:09:40 2014
Return-Path: <dthaler@microsoft.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 B105D1A0142 for <pcp@ietfa.amsl.com>; Mon, 21 Jul 2014 08:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.602
X-Spam-Level: 
X-Spam-Status: No, score=-102.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 hbmZe5sgpClj for <pcp@ietfa.amsl.com>; Mon, 21 Jul 2014 08:09:34 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0208.outbound.protection.outlook.com [207.46.163.208]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DB871A0172 for <pcp@ietf.org>; Mon, 21 Jul 2014 08:09:30 -0700 (PDT)
Received: from BY2PR03MB412.namprd03.prod.outlook.com (10.141.141.25) by BY2PR03MB412.namprd03.prod.outlook.com (10.141.141.25) with Microsoft SMTP Server (TLS) id 15.0.990.7; Mon, 21 Jul 2014 15:09:22 +0000
Received: from BY2PR03MB412.namprd03.prod.outlook.com ([10.141.141.25]) by BY2PR03MB412.namprd03.prod.outlook.com ([10.141.141.25]) with mapi id 15.00.0990.007; Mon, 21 Jul 2014 15:09:22 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Dacheng Zhang <zhang_dacheng@hotmail.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp]  I-D Action: draft-ietf-pcp-authentication-04.txt
Thread-Index: AQHPpPVZtuYV+B2M0UqHbD7/XsADtJuqoQdA
Date: Mon, 21 Jul 2014 15:09:21 +0000
Message-ID: <541289246ca04073983e553985021c4c@BY2PR03MB412.namprd03.prod.outlook.com>
References: <20140721132717.8597.69523.idtracker@ietfa.amsl.com> <BLU436-SMTP17122E359DE03F7D50A210888F00@phx.gbl>
In-Reply-To: <BLU436-SMTP17122E359DE03F7D50A210888F00@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [31.133.163.94]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 0279B3DD0D
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(377454003)(13464003)(189002)(51704005)(377424004)(199002)(33646002)(66066001)(83072002)(77982001)(81342001)(85852003)(46102001)(85306003)(107046002)(2656002)(81542001)(106356001)(76176999)(76576001)(50986999)(54356999)(76482001)(86612001)(87936001)(80022001)(106116001)(4396001)(31966008)(20776003)(19580395003)(19580405001)(99286002)(95666004)(15202345003)(86362001)(74662001)(74502001)(79102001)(64706001)(21056001)(83322001)(92566001)(101416001)(15975445006)(74316001)(105586002)(107886001)(99396002)(108616002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR03MB412; H:BY2PR03MB412.namprd03.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/ctFYUwl9BunP4EaCcfILv4grT3s
Subject: Re: [pcp] I-D Action: draft-ietf-pcp-authentication-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: Mon, 21 Jul 2014 15:09:36 -0000

Thanks Dacheng for the update!

There are currently 4 open tickets (see
http://trac.tools.ietf.org/wg/pcp/trac/query?status=3Dnew&status=3Dassigned=
&status=3Dreopened&component=3Dauthentication).
What do you believe the current status of each is, based on this update?

-Dave

> -----Original Message-----
> From: pcp [mailto:pcp-bounces@ietf.org] On Behalf Of Dacheng Zhang
> Sent: Monday, July 21, 2014 11:05 AM
> To: pcp@ietf.org
> Subject: [pcp] I-D Action: draft-ietf-pcp-authentication-04.txt
>=20
> Hi, in this version of the document, we try to address the comments got s=
ince
> the last meeting.  Particularly, we:
>    o  Refine the retransmission policies.
>=20
>    o  Provide the discussion about how to instruct a PCP client to
>       choose proper credential during authenticaiton, and an ID
>       Indication Option is defined for that purpose.
> In addition, it is advised that we should remove the key ID from the PCP
> authentication message, and only use one key for a PCP session. However,
> this indicates we will use the MSK to generate MACs for PCP message direc=
tly.
> We would like to check with the group again before including it into the
> document.
>=20
> Any comments and suggestions are appreciated.
>=20
> Cheers
>=20
> Dacheng
>=20
>=20
> >
> > 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) Authentication Mec=
hanism
> >        Authors         : Margaret Wasserman
> >                          Sam Hartman
> >                          Dacheng Zhang
> > 	Filename        : draft-ietf-pcp-authentication-04.txt
> > 	Pages           : 24
> > 	Date            : 2014-07-21
> >
> > Abstract:
> >   An IPv4 or IPv6 host can use the Port Control Protocol (PCP) to
> >   flexibly manage the IP address and port mapping information on
> >   Network Address Translators (NATs) or firewalls, to facilitate
> >   communications with remote hosts.  However, the un-controlled
> >   generation or deletion of IP address mappings on such network devices
> >   may cause security risks and should be avoided.  In some cases the
> >   client may need to prove that it is authorized to modify, create or
> >   delete PCP mappings.  This document proposes an in-band
> >   authentication mechanism for PCP that can be used in those cases.
> >   The Extensible Authentication Protocol (EAP) is used to perform
> >   authentication between PCP devices.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-pcp-authentication/
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-ietf-pcp-authentication-04
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcp-authentication-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.i=
etf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Jul 21 11:34:53 2014
Return-Path: <zhang_dacheng@hotmail.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 93C9E1A0370 for <pcp@ietfa.amsl.com>; Mon, 21 Jul 2014 11:34:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.549
X-Spam-Level: 
X-Spam-Status: No, score=0.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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 MgEayqmQKBlJ for <pcp@ietfa.amsl.com>; Mon, 21 Jul 2014 11:34:50 -0700 (PDT)
Received: from BLU004-OMC1S35.hotmail.com (blu004-omc1s35.hotmail.com [65.55.116.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E61D31A011D for <pcp@ietf.org>; Mon, 21 Jul 2014 11:34:49 -0700 (PDT)
Received: from BLU436-SMTP110 ([65.55.116.7]) by BLU004-OMC1S35.hotmail.com with Microsoft SMTPSVC(7.5.7601.22712);  Mon, 21 Jul 2014 11:34:48 -0700
X-TMN: [s06NSOC03TU2iJp4tXHdtCq4fXd2JdrG]
X-Originating-Email: [zhang_dacheng@hotmail.com]
Message-ID: <BLU436-SMTP110D22A16847284A9B4BDCB88F00@phx.gbl>
Received: from dhcp-9316.meeting.ietf.org ([31.133.147.22]) by BLU436-SMTP110.smtp.hotmail.com over TLS secured channel with Microsoft SMTPSVC(8.0.9200.16384); Mon, 21 Jul 2014 11:34:46 -0700
MIME-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="GB2312"
From: Dacheng Zhang <zhang_dacheng@hotmail.com>
In-Reply-To: <541289246ca04073983e553985021c4c@BY2PR03MB412.namprd03.prod.outlook.com>
Date: Mon, 21 Jul 2014 14:34:43 -0400
Content-Transfer-Encoding: quoted-printable
References: <20140721132717.8597.69523.idtracker@ietfa.amsl.com> <BLU436-SMTP17122E359DE03F7D50A210888F00@phx.gbl> <541289246ca04073983e553985021c4c@BY2PR03MB412.namprd03.prod.outlook.com>
To: Dave Thaler <dthaler@microsoft.com>
X-Mailer: Apple Mail (2.1283)
X-OriginalArrivalTime: 21 Jul 2014 18:34:46.0998 (UTC) FILETIME=[72BC6F60:01CFA512]
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/ybg90WSg65Ek55x5Tm7ytykdw18
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] I-D Action: draft-ietf-pcp-authentication-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: Mon, 21 Jul 2014 18:34:51 -0000

Hi, Dave:

We didn't see any discussion about #60 and #62 in =
draft-reddy-pcp-auth-req-04. It seems the group didn't reach conclusions =
on those two issues.  Follows are the current status of the tickets.

#60: In the design we do not explicitly define the relationship between =
the life period of mappings and PCP-Auth sessions. However, it is =
assumed that the life period of a mapping could be longer than the =
period of the session where the mapping information is generated.

#61:  Unsolicited re-authenticaiton is defined in Section 3.3 since it =
is listed in draft-reddy-pcp-auth-req-04

#62: In the current design, re-transmission could be driven by either =
the client or the server. The PCP-auth protocol rather than EAP is =
responsible for retransmission.

=A3=A372=A3=BAAn new Option is defined in Section 6.11 to transport the =
information helping client to choose proper credentials during =
authentication.  That option MAY be transported in the initial PA-Sever =
message. But the way of specifying such information is out of scope of =
this paper.

Cheers

Dacheng


=D4=DA 2014-7-21=A3=AC=C9=CF=CE=E711:09=A3=AC Dave Thaler =D0=B4=B5=C0=A3=BA=


> Thanks Dacheng for the update!
>=20
> There are currently 4 open tickets (see
> =
http://trac.tools.ietf.org/wg/pcp/trac/query?status=3Dnew&status=3Dassigne=
d&status=3Dreopened&component=3Dauthentication).
> What do you believe the current status of each is, based on this =
update?
>=20
> -Dave
>=20
>> -----Original Message-----
>> From: pcp [mailto:pcp-bounces@ietf.org] On Behalf Of Dacheng Zhang
>> Sent: Monday, July 21, 2014 11:05 AM
>> To: pcp@ietf.org
>> Subject: [pcp] I-D Action: draft-ietf-pcp-authentication-04.txt
>>=20
>> Hi, in this version of the document, we try to address the comments =
got since
>> the last meeting.  Particularly, we:
>>   o  Refine the retransmission policies.
>>=20
>>   o  Provide the discussion about how to instruct a PCP client to
>>      choose proper credential during authenticaiton, and an ID
>>      Indication Option is defined for that purpose.
>> In addition, it is advised that we should remove the key ID from the =
PCP
>> authentication message, and only use one key for a PCP session. =
However,
>> this indicates we will use the MSK to generate MACs for PCP message =
directly.
>> We would like to check with the group again before including it into =
the
>> document.
>>=20
>> Any comments and suggestions are appreciated.
>>=20
>> Cheers
>>=20
>> Dacheng
>>=20
>>=20
>>>=20
>>> 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.
>>>=20
>>>       Title           : Port Control Protocol (PCP) Authentication =
Mechanism
>>>       Authors         : Margaret Wasserman
>>>                         Sam Hartman
>>>                         Dacheng Zhang
>>> 	Filename        : draft-ietf-pcp-authentication-04.txt
>>> 	Pages           : 24
>>> 	Date            : 2014-07-21
>>>=20
>>> Abstract:
>>>  An IPv4 or IPv6 host can use the Port Control Protocol (PCP) to
>>>  flexibly manage the IP address and port mapping information on
>>>  Network Address Translators (NATs) or firewalls, to facilitate
>>>  communications with remote hosts.  However, the un-controlled
>>>  generation or deletion of IP address mappings on such network =
devices
>>>  may cause security risks and should be avoided.  In some cases the
>>>  client may need to prove that it is authorized to modify, create or
>>>  delete PCP mappings.  This document proposes an in-band
>>>  authentication mechanism for PCP that can be used in those cases.
>>>  The Extensible Authentication Protocol (EAP) is used to perform
>>>  authentication between PCP devices.
>>>=20
>>>=20
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-pcp-authentication/
>>>=20
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-ietf-pcp-authentication-04
>>>=20
>>> A diff from the previous version is available at:
>>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcp-authentication-04
>>>=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
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>=20
>=20


From nobody Tue Jul 22 11:14:06 2014
Return-Path: <ietf-secretariat@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 DAA241A017E; Tue, 22 Jul 2014 11:14:04 -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 EPaw0actLgtO; Tue, 22 Jul 2014 11:14:04 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 33F941A0061; Tue, 22 Jul 2014 11:14:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: 90all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140722181404.4815.62278.idtracker@ietfa.amsl.com>
Date: Tue, 22 Jul 2014 11:14:04 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/ID5HhzWHlhxNQc7V2mm1QZBQk38
Cc: pcp@ietf.org
Subject: [pcp] IETF 90 Agenda Change
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: pcp@ietf.org
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, 22 Jul 2014 18:14:05 -0000

The PCP Working Group session scheduled on Thursday, July 24, 2014 at 0900 EDT in Salon A has been canceled.

Thank you,

The IETF Secretariat


From nobody Tue Jul 22 11:45:15 2014
Return-Path: <dthaler@microsoft.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 4387A1B2BAD for <pcp@ietfa.amsl.com>; Tue, 22 Jul 2014 11:45:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.602
X-Spam-Level: 
X-Spam-Status: No, score=-102.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 fRjLKljhtVuq for <pcp@ietfa.amsl.com>; Tue, 22 Jul 2014 11:45:12 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0209.outbound.protection.outlook.com [207.46.163.209]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A08DF1B2BA4 for <pcp@ietf.org>; Tue, 22 Jul 2014 11:45:11 -0700 (PDT)
Received: from BY2PR03MB412.namprd03.prod.outlook.com (10.141.141.25) by BY2PR03MB409.namprd03.prod.outlook.com (10.141.141.11) with Microsoft SMTP Server (TLS) id 15.0.990.7; Tue, 22 Jul 2014 18:45:09 +0000
Received: from BY2PR03MB412.namprd03.prod.outlook.com ([10.141.141.25]) by BY2PR03MB412.namprd03.prod.outlook.com ([10.141.141.25]) with mapi id 15.00.0990.007; Tue, 22 Jul 2014 18:45:09 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: PCP WG meeting postponed to WebEx meeting next month
Thread-Index: Ac+l2vM8zoZE4rq8SOK8MBKi5YGtNg==
Date: Tue, 22 Jul 2014 18:45:09 +0000
Message-ID: <7c80c8c730504d128f1b6a056ef24708@BY2PR03MB412.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [31.133.162.235]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 02801ACE41
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(51704005)(199002)(189002)(377454003)(24454002)(13464003)(21056001)(2656002)(2351001)(4396001)(83072002)(92566001)(107886001)(83322001)(77982001)(101416001)(19580395003)(31966008)(79102001)(76576001)(87936001)(99396002)(19580405001)(99936001)(54356999)(50986999)(106356001)(74316001)(107046002)(66066001)(86362001)(85306003)(99286002)(105586002)(86612001)(95666004)(15975445006)(81342001)(74662001)(85852003)(229853001)(74502001)(110136001)(76482001)(46102001)(33646002)(20776003)(80022001)(81542001)(64706001)(108616002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR03MB409; H:BY2PR03MB412.namprd03.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en; 
Content-Type: multipart/mixed; boundary="_002_7c80c8c730504d128f1b6a056ef24708BY2PR03MB412namprd03pro_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/LGNZOFXFwo0_ZLiu2gCIkNTsRkU
Subject: [pcp] PCP WG meeting postponed to WebEx meeting next month
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, 22 Jul 2014 18:45:14 -0000

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

Earlier today, we submitted the official agenda request to
cancel the Thursday morning meeting this week due to lack of
any agenda requests for WG documents.  Attached is the
announcement.

As discussed in my previous email below, we plan to hold a
Webex interim meeting after the server-selection WGLC=20
closes (it closes on August 18).  Currently looking at Tuesday
August 26, 7AM Pacific =3D=3D 10 AM Eastern time as a possibility,
for a two-hour block (depending on agenda requests received).
If that date would be a problem, let us know now and we can look
at alternatives.

We hope that folks interested in other WG docs will be able
to show progress, and list discussion, by then as well.  For folks
who sent agenda requests for non-WG-drafts, we can keep you
on the agenda list for the WebEx interim.

-Dave

> The DHCP document was just published (thanks to those who Worked on that
> one!)
> Two WG documents are making good progress and don't need face to face
> discussion this week:
> port-set is likely to be handed to the IESG this week server-selection sh=
ould
> start WGLC as soon as the update is posted.
> Other than those two, we haven't seen any progress on other WG docs since
> last IETF.
>=20
> I completely agree that it would be good to finish auth, but we need to s=
ee
> progress/energy/discussion around the doc or there's not much we can do.
>=20
> So we propose to hold an interim webex meeting in late August after WGLC
> on server selection completes.
>=20
> -Dave
>=20
> > -----Original Message-----
> > From: pcp [mailto:pcp-bounces@ietf.org] On Behalf Of Tirumaleswar
> > Reddy
> > (tireddy)
> > Sent: Sunday, July 20, 2014 1:36 PM
> > To: Ted Lemon
> > Cc: pcp@ietf.org
> > Subject: Re: [pcp] Discussion about Closing PCP WG
> >
> > > -----Original Message-----
> > > From: Ted Lemon [mailto:ted.lemon@nominum.com]
> > > Sent: Sunday, July 20, 2014 5:24 PM
> > > To: Tirumaleswar Reddy (tireddy)
> > > Cc: Dan Wing (dwing); Margaret Wasserman; pcp@ietf.org
> > > Subject: Re: [pcp] Discussion about Closing PCP WG
> > >
> > > On Jul 20, 2014, at 2:48 AM, Tirumaleswar Reddy (tireddy)
> > > <tireddy@cisco.com>
> > > wrote:
> > > > In addition to PCP Authentication other pending WG documents
> > > > should also be
> > > taken to completion.  I see various interesting individual drafts
> > > like
> > > draft- boucadair-pcp-sfc-classifier-control-00,
> > > draft-chen-pcp-authentication-sim-00
> > > etc. it seems too early to close the WG.
> > >
> > > The trick with taking work to completion is that the work has to be
> > > worked on; I think what the chairs were getting at is that they feel
> > > there's
> > no energy to do the
> > > work.   If that's not the case, the way to show us that is to do the =
work,
> not
> > to
> > > say that the work needs to be done. :)
> >
> > Agreed. I will review PCP Proxy and PCP Auth drafts early next month
> > and post my comments.
> >
> > -Tiru
> >
> > >
> > > That said, the two drafts you mentioned are not pcp working group
> > documents.
> >
> > _______________________________________________
> > pcp mailing list
> > pcp@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcp

--_002_7c80c8c730504d128f1b6a056ef24708BY2PR03MB412namprd03pro_
Content-Type: message/rfc822
Content-Disposition: attachment;
	creation-date="Tue, 22 Jul 2014 18:45:05 GMT";
	modification-date="Tue, 22 Jul 2014 18:45:05 GMT"

Received: from BL2PR03MB404.namprd03.prod.outlook.com (10.141.91.149) by
 BY2PR03MB412.namprd03.prod.outlook.com (10.141.141.25) with Microsoft SMTP
 Server (TLS) id 15.0.990.7 via Mailbox Transport; Tue, 22 Jul 2014 18:14:11
 +0000
Received: from BY2PR03CA041.namprd03.prod.outlook.com (10.141.249.14) by
 BL2PR03MB404.namprd03.prod.outlook.com (10.141.91.149) with Microsoft SMTP
 Server (TLS) id 15.0.990.7; Tue, 22 Jul 2014 18:14:09 +0000
Received: from BL2FFO11FD060.protection.gbl (2a01:111:f400:7c09::172) by
 BY2PR03CA041.outlook.office365.com (2a01:111:e400:2c5d::14) with Microsoft
 SMTP Server (TLS) id 15.0.995.14 via Frontend Transport; Tue, 22 Jul 2014
 18:14:08 +0000
Received: from mail.ietf.org (4.31.198.44) by
 BL2FFO11FD060.mail.protection.outlook.com (10.173.161.188) with Microsoft
 SMTP Server (TLS) id 15.0.980.11 via Frontend Transport; Tue, 22 Jul 2014
 18:14:08 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1])
	by ietfa.amsl.com (Postfix) with ESMTP id BDDB31A017E;
	Tue, 22 Jul 2014 11:14:06 -0700 (PDT)
Received: from localhost (ietfa.amsl.com [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id DAA241A017E;
 Tue, 22 Jul 2014 11:14:04 -0700 (PDT)
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 EPaw0actLgtO; Tue, 22 Jul 2014 11:14:04 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1])
 by ietfa.amsl.com (Postfix) with ESMTP id 33F941A0061;
 Tue, 22 Jul 2014 11:14:04 -0700 (PDT)
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: "90all@ietf.org" <90all@ietf.org>
CC: "pcp@ietf.org" <pcp@ietf.org>
Subject: [pcp] IETF 90 Agenda Change
Thread-Topic: [pcp] IETF 90 Agenda Change
Thread-Index: AQHPpdi8dTa3zGnrek6Bb+xD2DTEeQ==
Sender: pcp <pcp-bounces@ietf.org>
Date: Tue, 22 Jul 2014 18:14:04 +0000
Message-ID: <20140722181404.4815.62278.idtracker@ietfa.amsl.com>
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>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>,
 <mailto:pcp-request@ietf.org?subject=unsubscribe>
Reply-To: "pcp@ietf.org" <pcp@ietf.org>
Content-Language: en-US
X-MS-Exchange-Organization-AuthSource: BL2FFO11FD060.protection.gbl
X-MS-Has-Attach: 
X-Auto-Response-Suppress: All
X-MS-TNEF-Correlator: 
x-spam-status: No, score=-1.9 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9] autolearn=ham
x-spam-level: 
auto-submitted: auto-generated
x-virus-scanned: amavisd-new at amsl.com
x-spam-flag: NO
received-spf: Pass (: domain of ietf.org designates 4.31.198.44 as permitted
 sender) receiver=; client-ip=4.31.198.44; helo=mail.ietf.org;
dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1406052846; bh=NX0tPSCZQ1oosw/sN/5jc0qFG3BwJHhGQbgEiqShRaE=;
	h=MIME-Version:From:To:Message-ID:Date:Cc:Subject:Reply-To:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 Content-Type:Content-Transfer-Encoding:Sender;
	b=i504OYzBO6z297sm0fqmIoxw6F0/jay9NaR+KDDAz/hQ8VC1axD/HXFgRFBbnXXMA
	 nHZPYctjo91s3wBZbKgcqA3sfqpFRAPFI9x1lbbEjc6PM7dFkHKnHtXasuHO5Q3aA8
	 IZ9yk7oIlPQGXhl3u6SWdS+UAoXQop7r8L5UpXyU=
list-id: PCP wg discussion list <pcp.ietf.org>
list-post: <mailto:pcp@ietf.org>
x-beenthere: pcp@ietf.org
x-mailman-version: 2.1.15
errors-to: pcp-bounces@ietf.org
x-spam-score: -1.9
list-archive: <http://www.ietf.org/mail-archive/web/pcp/>
authentication-results: spf=pass (sender IP is 4.31.198.44)
 smtp.mailfrom=pcp-bounces@ietf.org; 
delivered-to: pcp@ietfa.amsl.com
x-original-to: pcp@ietfa.amsl.com
x-test-idtracker: no
x-forefront-antispam-report: CIP:4.31.198.44;CTRY:US;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(6009001)(438002)(189002)(199002)(156002)(21056001)(64706001)(81342001)(79102001)(47776003)(20776003)(87836001)(95666004)(77982001)(102836001)(76482001)(46102001)(110136001)(106466001)(15975445006)(19580395003)(85306003)(74662001)(80022001)(77096002)(37156001)(81542001)(107046002)(23726002)(53416004)(76506005)(4396001)(85852003)(99396002)(50466002)(558084003)(53806999)(76806002)(46406003)(6806004)(103116003)(74502001)(76786999)(44976005)(19580405001)(50986999)(2351001)(92726001)(43066003)(81446001)(78456001)(83072002)(229853001)(2361001)(97746001)(33646002)(956001)(83322001)(47976999)(97756001)(146001)(54356999)(57326002);DIR:INB;SFP:;SCL:1;SRVR:BL2PR03MB404;H:mail.ietf.org;FPR:;MLV:sfv;PTR:mail.ietf.org;MX:1;A:1;LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A6943768FF74D84980F426931A2CD35F@namprd03.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

The PCP Working Group session scheduled on Thursday, July 24, 2014 at 0900 =
EDT in Salon A has been canceled.

Thank you,

The IETF Secretariat

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

--_002_7c80c8c730504d128f1b6a056ef24708BY2PR03MB412namprd03pro_--


From nobody Wed Jul 23 04:47:06 2014
Return-Path: <phdgang@gmail.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 53FE31ABB2A for <pcp@ietfa.amsl.com>; Wed, 23 Jul 2014 04:47:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 vyZN2aGnaKY3 for <pcp@ietfa.amsl.com>; Wed, 23 Jul 2014 04:47:00 -0700 (PDT)
Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 160111ABB2D for <pcp@ietf.org>; Wed, 23 Jul 2014 04:46:59 -0700 (PDT)
Received: by mail-qa0-f45.google.com with SMTP id cm18so1085239qab.4 for <pcp@ietf.org>; Wed, 23 Jul 2014 04:46:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vPTx+js7ey5h/xHJig2hbHOPrDiaWEq2GlfXd/flU7M=; b=chn4y/W1b85sFTRpdevc2chHyUwX0C+SEc6+l18aqK/VxDavAMb1l8W7pDDbdlDyO1 npnlRXundGirMYmBsV1e1mFr227b/zK740kSaHwAQtx+OIk/uqkWvzpdyqlxzFTqCZb+ y9oBkUe5JyDjNv6YTyoVDGHH14/YN1H5d3KnFFbbG2axr+pqlzBs4Rd3ZD3w0fy+1HNH /MAiiJ+5bd8nDOasSxswF4EQ5qFIS0ubcKdHB/nV4FER2vDD7fNubBgvHiAsvGYlQKsF 0uOnBg2Fvc33y0w0zxNYN5ERlZVGJIp6y+mogw8ceXTVFGkFE4tOwWZmm6MPrDJe1nB3 /9DQ==
MIME-Version: 1.0
X-Received: by 10.140.34.167 with SMTP id l36mr971053qgl.61.1406116018779; Wed, 23 Jul 2014 04:46:58 -0700 (PDT)
Received: by 10.224.57.2 with HTTP; Wed, 23 Jul 2014 04:46:58 -0700 (PDT)
In-Reply-To: <913383AAA69FF945B8F946018B75898A282F66EC@xmb-rcd-x10.cisco.com>
References: <913383AAA69FF945B8F946018B75898A282F66EC@xmb-rcd-x10.cisco.com>
Date: Wed, 23 Jul 2014 19:46:58 +0800
Message-ID: <CAM+vMEQw5F4CpZ5_q+4e=+K8y0CoH1K+cCGBmkXhNig72+LEzA@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/g7A6kyERQR1dTEP_eqWVaqabYCM
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] Fwd: New Version Notification for draft-chen-pcp-authentication-sim-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, 23 Jul 2014 11:47:04 -0000

2014-07-21 22:17 GMT+08:00, Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>:
>> -----Original Message-----
>> From: GangChen [mailto:phdgang@gmail.com]
>> Sent: Friday, July 04, 2014 3:41 PM
>> To: pcp@ietf.org
>> Subject: [pcp] Fwd: New Version Notification for
>> draft-chen-pcp-authentication-
>> sim-00.txt
>>
>> WG,
>>
>> I have submitted a draft to describe the consideration of PCP
>> authentication
>> with (U)SIM support. The process is detailed in EAP and GBA framework.
>
> Interesting draft. This solves the problem that for PCP authentication to
> work in Mobile networks, PCP client does not have use username and password
> but only use SIM credentials (EAP-SIM).  Other operators like
> Deutsche-Telekom are already using SIM authentication for ISP offered
> services (Slide 11
> http://www.gsma.com/personaldata/wp-content/uploads/2014/03/OpenID-Connect-at-Deutsche-Telekom-Torsten-Lodderstedt.pdf)

Thank you for the comments. I would like to further highlight the
technical advantage using GBA to PCP. The thought is to leverage the
deployed GBA infrastructure. AFAIK, GBA is indispensable to the mobile
operators, who like to offer voice service in the LTE age. It's
low-cost and lightweight implementation to the PCP server.(only one
simply message extension makes it work, as draft proposed at Section
3).

BRs

Gang


>
> -Tiru
>
>> Thank you for the comments in advance.
>>
>> Best Regards
>>
>> Gang
>>
>> ---------- Forwarded message ----------
>> From: internet-drafts@ietf.org
>> Date: Fri, 04 Jul 2014 03:03:05 -0700
>> Subject: New Version Notification for
>> draft-chen-pcp-authentication-sim-00.txt
>> To: Gang Chen <phdgang@gmail.com>
>>
>>
>> A new version of I-D, draft-chen-pcp-authentication-sim-00.txt
>> has been successfully submitted by Gang Chen and posted to the IETF
>> repository.
>>
>> Name:		draft-chen-pcp-authentication-sim
>> Revision:	00
>> Title:		(U)SIM based PCP Authentication
>> Document date:	2014-07-03
>> Group:		Individual Submission
>> Pages:		8
>> URL:
>> http://www.ietf.org/internet-drafts/draft-chen-pcp-authentication-sim-00.txt
>> Status:
>> https://datatracker.ietf.org/doc/draft-chen-pcp-authentication-sim/
>> Htmlized:
>> http://tools.ietf.org/html/draft-chen-pcp-authentication-sim-00
>>
>>
>> Abstract:
>>    With (U)SIM support, PCP authentication could leverage the
>>    credentials stored in (U)SIM.  The document details PCP
>>    authentication considerations based on (U)SIM support.  The
>>    authentication procedures in EAP and GBA framework have been
>>    specifically elaborated.  In order to complete the process, new code
>>    and option are also proposed.
>>
>>
>>
>>
>> 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 nobody Fri Jul 25 04:42:23 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 386FD1B27F7; Fri, 25 Jul 2014 04:42:19 -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 R0eOgOih4BPh; Fri, 25 Jul 2014 04:42:17 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9293E1B27B5; Fri, 25 Jul 2014 04:42:17 -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.6.2.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140725114217.27827.1300.idtracker@ietfa.amsl.com>
Date: Fri, 25 Jul 2014 04:42:17 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/XvYYYHioapHlzlmAEe_kWaD5QWo
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-optimize-keepalives-02.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: Fri, 25 Jul 2014 11:42:19 -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           : Optimizing NAT and Firewall Keepalives Using Port Control Protocol (PCP)
        Authors         : Tirumaleswar Reddy
                          Markus Isomaki
                          Dan Wing
                          Prashanth Patil
	Filename        : draft-ietf-pcp-optimize-keepalives-02.txt
	Pages           : 15
	Date            : 2014-07-25

Abstract:
   This document describes how Port Control Protocol is useful in
   reducing NAT and firewall keepalive messages for a variety of
   applications.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-pcp-optimize-keepalives-02


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 Thu Jul 31 10:32:15 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 9AF551A0310 for <pcp@ietfa.amsl.com>; Thu, 31 Jul 2014 10:32:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 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.001, 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 oFHTt4C35DS0 for <pcp@ietfa.amsl.com>; Thu, 31 Jul 2014 10:32:09 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26A341A02E3 for <pcp@ietf.org>; Thu, 31 Jul 2014 10:32:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5096; q=dns/txt; s=iport; t=1406827930; x=1408037530; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=vtqlCiLNkKmfdsfqhRUCugJR6l2m1zGhiNUpXipB8pA=; b=JWS1YzskpSKx//oin87/j/lieKKcztXpNKysMsNulxClTuKjWcCTGCtz 1NSmmrJqnSdm51xUbOg3+7xBdv6OFtHNIhvcQ+yt9zjysbgsov3jnOELS BbBrdHjXM4LbnphlhSumNGUpEZ8yBT2zIB8Zf5fjb9TIWpd7S7rsMo8jt g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwFAP182lOtJV2Z/2dsb2JhbABbgw5SVwSCdMg5h0sBGXIWd4QDAQEBAQIBIxFDAgwEAgEIEQMBAQEDAgYODwMCAgIfERQBCAgBAQQOBQgBiCUDCQgNr2aQRw2HDxeBLItdFoF8FhsHBhKCYTaBGwWXPoIhg1eMXIYlggOBRmyBRQ
X-IronPort-AV: E=Sophos;i="5.01,773,1400025600"; d="scan'208";a="65544312"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-8.cisco.com with ESMTP; 31 Jul 2014 17:32:09 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s6VHW8oH023122 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 31 Jul 2014 17:32:08 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.102]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.03.0123.003; Thu, 31 Jul 2014 12:32:08 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: GangChen <phdgang@gmail.com>
Thread-Topic: [pcp] Fwd: New Version Notification for draft-chen-pcp-authentication-sim-00.txt
Thread-Index: Ac+k7nNqTXulltUXSJy2fLmOyv1+RQBp0RQAAZO+egA=
Date: Thu, 31 Jul 2014 17:32:07 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A282FEFA3@xmb-rcd-x10.cisco.com>
References: <913383AAA69FF945B8F946018B75898A282F66EC@xmb-rcd-x10.cisco.com> <CAM+vMEQw5F4CpZ5_q+4e=+K8y0CoH1K+cCGBmkXhNig72+LEzA@mail.gmail.com>
In-Reply-To: <CAM+vMEQw5F4CpZ5_q+4e=+K8y0CoH1K+cCGBmkXhNig72+LEzA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.33.173]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/YRS8RhtK3eYQGpZmaQsWXaXEiiY
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] Fwd: New Version Notification for draft-chen-pcp-authentication-sim-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, 31 Jul 2014 17:32:12 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBHYW5nQ2hlbiBbbWFpbHRvOnBo
ZGdhbmdAZ21haWwuY29tXQ0KPiBTZW50OiBXZWRuZXNkYXksIEp1bHkgMjMsIDIwMTQgNToxNyBQ
TQ0KPiBUbzogVGlydW1hbGVzd2FyIFJlZGR5ICh0aXJlZGR5KQ0KPiBDYzogcGNwQGlldGYub3Jn
DQo+IFN1YmplY3Q6IFJlOiBbcGNwXSBGd2Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3Ig
ZHJhZnQtY2hlbi1wY3AtDQo+IGF1dGhlbnRpY2F0aW9uLXNpbS0wMC50eHQNCj4gDQo+IDIwMTQt
MDctMjEgMjI6MTcgR01UKzA4OjAwLCBUaXJ1bWFsZXN3YXIgUmVkZHkgKHRpcmVkZHkpDQo+IDx0
aXJlZGR5QGNpc2NvLmNvbT46DQo+ID4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+
IEZyb206IEdhbmdDaGVuIFttYWlsdG86cGhkZ2FuZ0BnbWFpbC5jb21dDQo+ID4+IFNlbnQ6IEZy
aWRheSwgSnVseSAwNCwgMjAxNCAzOjQxIFBNDQo+ID4+IFRvOiBwY3BAaWV0Zi5vcmcNCj4gPj4g
U3ViamVjdDogW3BjcF0gRndkOiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yDQo+ID4+IGRy
YWZ0LWNoZW4tcGNwLWF1dGhlbnRpY2F0aW9uLQ0KPiA+PiBzaW0tMDAudHh0DQo+ID4+DQo+ID4+
IFdHLA0KPiA+Pg0KPiA+PiBJIGhhdmUgc3VibWl0dGVkIGEgZHJhZnQgdG8gZGVzY3JpYmUgdGhl
IGNvbnNpZGVyYXRpb24gb2YgUENQDQo+ID4+IGF1dGhlbnRpY2F0aW9uIHdpdGggKFUpU0lNIHN1
cHBvcnQuIFRoZSBwcm9jZXNzIGlzIGRldGFpbGVkIGluIEVBUA0KPiA+PiBhbmQgR0JBIGZyYW1l
d29yay4NCj4gPg0KPiA+IEludGVyZXN0aW5nIGRyYWZ0LiBUaGlzIHNvbHZlcyB0aGUgcHJvYmxl
bSB0aGF0IGZvciBQQ1AgYXV0aGVudGljYXRpb24NCj4gPiB0byB3b3JrIGluIE1vYmlsZSBuZXR3
b3JrcywgUENQIGNsaWVudCBkb2VzIG5vdCBoYXZlIHVzZSB1c2VybmFtZSBhbmQNCj4gPiBwYXNz
d29yZCBidXQgb25seSB1c2UgU0lNIGNyZWRlbnRpYWxzIChFQVAtU0lNKS4gIE90aGVyIG9wZXJh
dG9ycyBsaWtlDQo+ID4gRGV1dHNjaGUtVGVsZWtvbSBhcmUgYWxyZWFkeSB1c2luZyBTSU0gYXV0
aGVudGljYXRpb24gZm9yIElTUCBvZmZlcmVkDQo+ID4gc2VydmljZXMgKFNsaWRlIDExDQo+ID4g
aHR0cDovL3d3dy5nc21hLmNvbS9wZXJzb25hbGRhdGEvd3AtY29udGVudC91cGxvYWRzLzIwMTQv
MDMvT3BlbklELQ0KPiBDb24NCj4gPiBuZWN0LWF0LURldXRzY2hlLVRlbGVrb20tVG9yc3Rlbi1M
b2RkZXJzdGVkdC5wZGYpDQo+IA0KPiBUaGFuayB5b3UgZm9yIHRoZSBjb21tZW50cy4gSSB3b3Vs
ZCBsaWtlIHRvIGZ1cnRoZXIgaGlnaGxpZ2h0IHRoZSB0ZWNobmljYWwNCj4gYWR2YW50YWdlIHVz
aW5nIEdCQSB0byBQQ1AuIFRoZSB0aG91Z2h0IGlzIHRvIGxldmVyYWdlIHRoZSBkZXBsb3llZCBH
QkENCj4gaW5mcmFzdHJ1Y3R1cmUuIEFGQUlLLCBHQkEgaXMgaW5kaXNwZW5zYWJsZSB0byB0aGUg
bW9iaWxlIG9wZXJhdG9ycywgd2hvIGxpa2UgdG8NCj4gb2ZmZXIgdm9pY2Ugc2VydmljZSBpbiB0
aGUgTFRFIGFnZS4gSXQncyBsb3ctY29zdCBhbmQgbGlnaHR3ZWlnaHQgaW1wbGVtZW50YXRpb24N
Cj4gdG8gdGhlIFBDUCBzZXJ2ZXIuKG9ubHkgb25lIHNpbXBseSBtZXNzYWdlIGV4dGVuc2lvbiBt
YWtlcyBpdCB3b3JrLCBhcyBkcmFmdA0KPiBwcm9wb3NlZCBhdCBTZWN0aW9uIDMpLg0KDQpUaGUg
b3RoZXIgdGVjaG5pcXVlIG1lbnRpb25lZCBpbiB0aGUgZHJhZnQgaXMgdXNpbmcgSFRUUCBhdXRo
ZW50aWNhdGlvbiBhbmQgbm90IEVBUC4gDQoNCjEuIHdoYXQgaXMgdGhlIG5lZWQgZm9yIHRoaXMg
bWVjaGFuaXNtIHdoZW4gRUFQLVNJTSBjYW4gYmUgdXNlZCA/DQoyLiBJdCBkZXZpYXRlcyBmcm9t
IFJFUS02IG9mIGZhdGUgc2hhcmluZyBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1y
ZWRkeS1wY3AtYXV0aC1yZXEtMDQgdGhhdCB3YXMgZGlzY3Vzc2VkIGluIHRoZSBXRyBzb21ldGlt
ZSBiYWNrLg0KDQotVGlydQ0KDQo+IA0KPiBCUnMNCj4gDQo+IEdhbmcNCj4gDQo+IA0KPiA+DQo+
ID4gLVRpcnUNCj4gPg0KPiA+PiBUaGFuayB5b3UgZm9yIHRoZSBjb21tZW50cyBpbiBhZHZhbmNl
Lg0KPiA+Pg0KPiA+PiBCZXN0IFJlZ2FyZHMNCj4gPj4NCj4gPj4gR2FuZw0KPiA+Pg0KPiA+PiAt
LS0tLS0tLS0tIEZvcndhcmRlZCBtZXNzYWdlIC0tLS0tLS0tLS0NCj4gPj4gRnJvbTogaW50ZXJu
ZXQtZHJhZnRzQGlldGYub3JnDQo+ID4+IERhdGU6IEZyaSwgMDQgSnVsIDIwMTQgMDM6MDM6MDUg
LTA3MDANCj4gPj4gU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvcg0KPiA+PiBk
cmFmdC1jaGVuLXBjcC1hdXRoZW50aWNhdGlvbi1zaW0tMDAudHh0DQo+ID4+IFRvOiBHYW5nIENo
ZW4gPHBoZGdhbmdAZ21haWwuY29tPg0KPiA+Pg0KPiA+Pg0KPiA+PiBBIG5ldyB2ZXJzaW9uIG9m
IEktRCwgZHJhZnQtY2hlbi1wY3AtYXV0aGVudGljYXRpb24tc2ltLTAwLnR4dA0KPiA+PiBoYXMg
YmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IEdhbmcgQ2hlbiBhbmQgcG9zdGVkIHRvIHRo
ZSBJRVRGDQo+ID4+IHJlcG9zaXRvcnkuDQo+ID4+DQo+ID4+IE5hbWU6CQlkcmFmdC1jaGVuLXBj
cC1hdXRoZW50aWNhdGlvbi1zaW0NCj4gPj4gUmV2aXNpb246CTAwDQo+ID4+IFRpdGxlOgkJKFUp
U0lNIGJhc2VkIFBDUCBBdXRoZW50aWNhdGlvbg0KPiA+PiBEb2N1bWVudCBkYXRlOgkyMDE0LTA3
LTAzDQo+ID4+IEdyb3VwOgkJSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQo+ID4+IFBhZ2VzOgkJOA0K
PiA+PiBVUkw6DQo+ID4+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0
LWNoZW4tcGNwLWF1dGhlbnRpY2F0aW9uLXNpbQ0KPiA+PiAtMDAudHh0DQo+ID4+IFN0YXR1czoN
Cj4gPj4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtY2hlbi1wY3AtYXV0
aGVudGljYXRpb24tc2ltLw0KPiA+PiBIdG1saXplZDoNCj4gPj4gaHR0cDovL3Rvb2xzLmlldGYu
b3JnL2h0bWwvZHJhZnQtY2hlbi1wY3AtYXV0aGVudGljYXRpb24tc2ltLTAwDQo+ID4+DQo+ID4+
DQo+ID4+IEFic3RyYWN0Og0KPiA+PiAgICBXaXRoIChVKVNJTSBzdXBwb3J0LCBQQ1AgYXV0aGVu
dGljYXRpb24gY291bGQgbGV2ZXJhZ2UgdGhlDQo+ID4+ICAgIGNyZWRlbnRpYWxzIHN0b3JlZCBp
biAoVSlTSU0uICBUaGUgZG9jdW1lbnQgZGV0YWlscyBQQ1ANCj4gPj4gICAgYXV0aGVudGljYXRp
b24gY29uc2lkZXJhdGlvbnMgYmFzZWQgb24gKFUpU0lNIHN1cHBvcnQuICBUaGUNCj4gPj4gICAg
YXV0aGVudGljYXRpb24gcHJvY2VkdXJlcyBpbiBFQVAgYW5kIEdCQSBmcmFtZXdvcmsgaGF2ZSBi
ZWVuDQo+ID4+ICAgIHNwZWNpZmljYWxseSBlbGFib3JhdGVkLiAgSW4gb3JkZXIgdG8gY29tcGxl
dGUgdGhlIHByb2Nlc3MsIG5ldyBjb2RlDQo+ID4+ICAgIGFuZCBvcHRpb24gYXJlIGFsc28gcHJv
cG9zZWQuDQo+ID4+DQo+ID4+DQo+ID4+DQo+ID4+DQo+ID4+IFBsZWFzZSBub3RlIHRoYXQgaXQg
bWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mDQo+ID4+IHN1Ym1p
c3Npb24gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBh
dA0KPiA+PiB0b29scy5pZXRmLm9yZy4NCj4gPj4NCj4gPj4gVGhlIElFVEYgU2VjcmV0YXJpYXQN
Cj4gPj4NCj4gPg0KPiA+DQo=

