
From tireddy@cisco.com  Mon Dec  2 01:55:55 2013
Return-Path: <tireddy@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8DBA1AE0F9 for <pcp@ietfa.amsl.com>; Mon,  2 Dec 2013 01:55:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.501
X-Spam-Level: 
X-Spam-Status: No, score=-9.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 0auUKJtTLb5I for <pcp@ietfa.amsl.com>; Mon,  2 Dec 2013 01:55:53 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 04E4B1AE08F for <pcp@ietf.org>; Mon,  2 Dec 2013 01:55:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20282; q=dns/txt; s=iport; t=1385978151; x=1387187751; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=fysqglMA69BxMIae0ChGP6dg0othFeJUn0tYZnt3Ehc=; b=dGDcO+fGMJypsWeWJI6MxSqbKhDnklPj6RAtuoG+CQ+/idMHKVzKzbrH iNag7WggJKpT9mOBRdhhq13wUwNr+yWxpyFqr7EqDMsR2PiDnT0SADXr6 X7/PhFO5gEFql9bfMWu5iqpJqzWRaqnm1ELHfg63amiQUeh1oto1+CkPY s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhsFAPxYnFKtJV2Z/2dsb2JhbABZgkNEOFO4V4EhFnSCJQEBAQQtXAIBCBEEAQELFgcHMhQJCAIEARIIh3m/IheOVzcBgyCBEwOJCqEdgymCKg
X-IronPort-AV: E=Sophos;i="4.93,809,1378857600"; d="scan'208,217";a="3582019"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-4.cisco.com with ESMTP; 02 Dec 2013 09:55:43 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rB29thxX030979 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <pcp@ietf.org>; Mon, 2 Dec 2013 09:55:43 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.250]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Mon, 2 Dec 2013 03:55:42 -0600
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "Prashanth Patil (praspati)" <praspati@cisco.com>, "Reinaldo Penno (repenno)" <repenno@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] Comments on draft-ietf-pcp-optimize-keepalives-00
Thread-Index: AQHOzo/D4iCDjuIyjkqi4oYMprmUs5pA62nQ
Date: Mon, 2 Dec 2013 09:55:42 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A24271415@xmb-rcd-x10.cisco.com>
References: <45A697A8FFD7CF48BCF2BE7E106F06040B7320E5@xmb-rcd-x04.cisco.com> <B235506D63D65E43B2E40FD27715372E1CEFB7A4@xmb-rcd-x07.cisco.com>
In-Reply-To: <B235506D63D65E43B2E40FD27715372E1CEFB7A4@xmb-rcd-x07.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [173.39.66.116]
Content-Type: multipart/alternative; boundary="_000_913383AAA69FF945B8F946018B75898A24271415xmbrcdx10ciscoc_"
MIME-Version: 1.0
Subject: Re: [pcp] Comments on draft-ietf-pcp-optimize-keepalives-00
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, 02 Dec 2013 09:55:56 -0000

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

Hi Reinaldo,

Responding to your comments in the pdf

Comment1> The application keepalive would keep the state alive in the FW/NA=
T as well, right ? This sentence seems out of place here.

Reply1> No. The time interval to send keepalives for maintaining state on t=
he Application Server could be greater than FW/NAT mapping lifetime. In thi=
s case application keepalives will not maintain the FW/NAT mappings. For ex=
ample in case where application keepalive interval every 60 minutes is requ=
ired whereas FW/NAT keepalive interval is 30 minutes.

Comment2>  I believe this section should have an introduction and two sub-s=
ections. One sub=ACsection should be called "PCP based detection" and have =
the first paragraph part of it since it only talks about PCP based detectio=
n. The second sub=ACsection should talk about application based detection.

Reply2> Agreed, updated the draft.

Comment3> Then the title of this section needs to change to "NAT Topologies=
 and Detection"

Reply3> Yes, changed the title.

Comment4> Suggest to change title to "Detection of..". But more generally, =
I wonder if this discussion of detection belongs in this draft. Can this  s=
ection be removed ?

Reply4> Yes, changed the title. In the previous WG discussions there was sp=
ecific ask to add this section explaining the "Detection of PCP Unaware Fir=
ewalls".

Comment5> Needs RFC reference
Reply4> RFC reference is already provided

Comment 6>It will insert if it supports this experimental RFC, if it has an=
other IP address, etc. I believe some more clarification is needed.
Reply6> Agreed, updated the text.

Comment 7> Application layer protocols ?
Reply7> Yes

Comment 8> This is all STUN, why this is in this draft ?
Reply8> In the previous WG discussions there was specific ask from Dave to =
add this section and explain the Keepalive Interval determination procedure=
 when PCP unaware Firewall or NAT is detected.

-Tiru.
From: Prashanth Patil (praspati)
Sent: Monday, October 21, 2013 3:51 AM
To: Reinaldo Penno (repenno); pcp@ietf.org
Subject: Re: [pcp] Comments on draft-ietf-pcp-optimize-keepalives-00

Hi Reinaldo,
Sections "3.3 Detect PCP Unaware Firewall" and "4. Keepalive Interval Deter=
mination Procedure when PCP unaware Firewall or NAT is detected" were added=
 based on Dave's recommendation.

Section 3.3 does not introduce anything new, it only provides an example on=
 how a PCP unaware firewall can be detected using STUN. Section 4 is also a=
 recommendation on what can be potentially done if a PCP unaware firewall w=
as detected.

Dave, what are your thoughts on this?

-Prashanth

On 11/10/13 4:45 PM, "Reinaldo Penno (repenno)" <repenno@cisco.com<mailto:r=
epenno@cisco.com>> wrote:

I reviewed this draft for a possible WGLC but I do not think it is ready.
My summary is that this draft has lots of text related to detection of PCP
unaware NAT/FW using STUN which IMO belong in a separate draft, or some
other document since it is generic text. Maybe the WG sees value in having
a separate document that talks exclusively about detection of PCP unaware
FWs.

This draft could just say "assuming all NAT/FW in the path are PCP
aware..." and take it from there since the goal is optimizing keep-alive
and not standardizing detection mechanisms.

Removing all detection text would make this draft quite short and easier
to understand its purpose.

Thanks,

Reinaldo



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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: bre=
ak-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class=3D"Section1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Hi Reinaldo,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Responding to your comments in the pdf<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Comment1&gt; The application keepalive would keep the state =
alive in the FW/NAT as well, right ? This sentence seems out of place here.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Reply1&gt; No. The time interval to send keepalives for main=
taining state on the Application Server could be greater than FW/NAT mappin=
g lifetime. In this case
 application keepalives will not maintain the FW/NAT mappings. For example =
in case where application keepalive interval every 60 minutes is required w=
hereas FW/NAT keepalive interval is 30 minutes.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Comment2&gt;&nbsp; I believe this section should have an int=
roduction and two sub-sections. One sub=ACsection should be called &#8220;P=
CP based detection&#8221; and have the first
 paragraph part of it since it only talks about PCP based detection. The se=
cond sub=ACsection should talk about application based detection.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Reply2&gt; Agreed, updated the draft.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Comment3&gt; Then the title of this section needs to change =
to &#8220;NAT Topologies and Detection&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Reply3&gt; Yes, changed the title.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Comment4&gt; Suggest to change title to &#8220;Detection of.=
.&#8221;. But more generally, I wonder if this discussion of detection belo=
ngs in this draft. Can this&nbsp; section
 be removed ? <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Reply4&gt; Yes, changed the title. In the previous WG discus=
sions there was specific ask to add this section explaining the &quot;Detec=
tion of PCP Unaware Firewalls&quot;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Comment5&gt; Needs RFC reference<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Reply4&gt; RFC reference is already provided
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Comment 6&gt;It will insert if it supports this experimental=
 RFC, if it has another IP address, etc. I believe some more clarification =
is needed.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Reply6&gt; Agreed, updated the text.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Comment 7&gt; Application layer protocols ?<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Reply7&gt; Yes<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Comment 8&gt; This is all STUN, why this is in this draft ?<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Reply8&gt; In the previous WG discussions there was specific=
 ask from Dave to add this section and explain the Keepalive Interval deter=
mination procedure when
 PCP unaware Firewall or NAT is detected.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">-Tiru.<o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Prashant=
h Patil (praspati)
<br>
<b>Sent:</b> Monday, October 21, 2013 3:51 AM<br>
<b>To:</b> Reinaldo Penno (repenno); pcp@ietf.org<br>
<b>Subject:</b> Re: [pcp] Comments on draft-ietf-pcp-optimize-keepalives-00=
<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">Hi Reinaldo,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">Sections &quot;<i>3.3 Detect PCP Unaware Firewall</i>&quot; an=
d &quot;<i>4. Keepalive Interval Determination Procedure when PCP unaware F=
irewall or NAT is detected</i>&quot; were
 added based on Dave's recommendation.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">Section 3.3 does not introduce anything new, it only provides =
an example on how a PCP unaware firewall can be detected using STUN. Sectio=
n 4 is also a recommendation
 on what can be potentially done if a PCP unaware firewall was detected.<o:=
p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">Dave, what are your thoughts on this?<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">-Prashanth<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">On 11/10/13 4:45 PM, &quot;Reinaldo Penno (repenno)&quot; &lt;=
<a href=3D"mailto:repenno@cisco.com">repenno@cisco.com</a>&gt; wrote:<o:p><=
/o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;
margin-left:3.75pt;margin-right:0in" id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUO=
TE">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">I reviewed this draft for a possible WGLC but I do not think i=
t is ready.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">My summary is that this draft has lots of text related to dete=
ction of PCP<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">unaware NAT/FW using STUN which IMO belong in a separate draft=
, or some<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">other document since it is generic text. Maybe the WG sees val=
ue in having<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">a separate document that talks exclusively about detection of =
PCP unaware<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">FWs.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">This draft could just say &quot;assuming all NAT/FW in the pat=
h are PCP<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">aware...&quot; and take it from there since the goal is optimi=
zing keep-alive<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">and not standardizing detection mechanisms.<o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">Removing all detection text would make this draft quite short =
and easier<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">to understand its purpose.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">Thanks,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black">Reinaldo<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:black"><o:p>&nbsp;</o:p></span></p>
</div>
</blockquote>
</div>
</div>
</body>
</html>

--_000_913383AAA69FF945B8F946018B75898A24271415xmbrcdx10ciscoc_--

From repenno@cisco.com  Mon Dec  2 02:32:57 2013
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 0D7DD1AE303 for <pcp@ietfa.amsl.com>; Mon,  2 Dec 2013 02:32:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 r9GO9HBZI0iq for <pcp@ietfa.amsl.com>; Mon,  2 Dec 2013 02:32:54 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 7DE5F1AE10F for <pcp@ietf.org>; Mon,  2 Dec 2013 02:32:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21189; q=dns/txt; s=iport; t=1385980372; x=1387189972; h=from:to:subject:date:message-id:in-reply-to:mime-version; bh=/zmr0VKzbc9zDbbdabQ6vi/iZsidCnlPfvKfe6hOtJw=; b=FXGgNsl+55KSPMokWJABjTtVvXNoP4vOQe8NGzpjvzxQNaBrcj7jhfEB SGvsQKdOKMEnexLfigeBIQjz22x/l8woekurI0W7mmlPzYxJBRogNHE2L L3Rgz64zM8bs+7TXGBrr+CjqTSqH293WIAy1VKcOhFqTpT4DLi1Ps6VA6 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAKVgnFKtJV2Z/2dsb2JhbABZgkNEOFO4V4EiFnSCJQEBAQQtXgEIEQMBAQEhBzkUCQgCBAESiAG/JReOdxcBhDMDmBSSE4Mpgio
X-IronPort-AV: E=Sophos;i="4.93,810,1378857600";  d="scan'208,217";a="288741056"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-3.cisco.com with ESMTP; 02 Dec 2013 10:32:52 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rB2AWmnA014859 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <pcp@ietf.org>; Mon, 2 Dec 2013 10:32:49 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0123.003; Mon, 2 Dec 2013 04:32:48 -0600
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "Prashanth Patil (praspati)" <praspati@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] Comments on draft-ietf-pcp-optimize-keepalives-00
Thread-Index: AQHOxnM3cE0GfrO1FEuZq+aBikbnCppA62nQ///5BoA=
Date: Mon, 2 Dec 2013 10:32:47 +0000
Message-ID: <CEC1A115.6CFB%repenno@cisco.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A24271415@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.94.183]
Content-Type: multipart/alternative; boundary="_000_CEC1A1156CFBrepennociscocom_"
MIME-Version: 1.0
Subject: Re: [pcp] Comments on draft-ietf-pcp-optimize-keepalives-00
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, 02 Dec 2013 10:32:57 -0000

--_000_CEC1A1156CFBrepennociscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Thanks, looking forward to the new version

From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com<mailto:tireddy@cisc=
o.com>>
Date: Monday, December 2, 2013 at 1:55 AM
To: "Prashanth Patil (praspati)" <praspati@cisco.com<mailto:praspati@cisco.=
com>>, Cisco Employee <repenno@cisco.com<mailto:repenno@cisco.com>>, "pcp@i=
etf.org<mailto:pcp@ietf.org>" <pcp@ietf.org<mailto:pcp@ietf.org>>
Subject: RE: [pcp] Comments on draft-ietf-pcp-optimize-keepalives-00

Hi Reinaldo,

Responding to your comments in the pdf

Comment1> The application keepalive would keep the state alive in the FW/NA=
T as well, right ? This sentence seems out of place here.

Reply1> No. The time interval to send keepalives for maintaining state on t=
he Application Server could be greater than FW/NAT mapping lifetime. In thi=
s case application keepalives will not maintain the FW/NAT mappings. For ex=
ample in case where application keepalive interval every 60 minutes is requ=
ired whereas FW/NAT keepalive interval is 30 minutes.

Comment2>  I believe this section should have an introduction and two sub-s=
ections. One sub=ACsection should be called =93PCP based detection=94 and h=
ave the first paragraph part of it since it only talks about PCP based dete=
ction. The second sub=ACsection should talk about application based detecti=
on.

Reply2> Agreed, updated the draft.

Comment3> Then the title of this section needs to change to =93NAT Topologi=
es and Detection=94

Reply3> Yes, changed the title.

Comment4> Suggest to change title to =93Detection of..=94. But more general=
ly, I wonder if this discussion of detection belongs in this draft. Can thi=
s  section be removed ?

Reply4> Yes, changed the title. In the previous WG discussions there was sp=
ecific ask to add this section explaining the "Detection of PCP Unaware Fir=
ewalls".

Comment5> Needs RFC reference
Reply4> RFC reference is already provided

Comment 6>It will insert if it supports this experimental RFC, if it has an=
other IP address, etc. I believe some more clarification is needed.
Reply6> Agreed, updated the text.

Comment 7> Application layer protocols ?
Reply7> Yes

Comment 8> This is all STUN, why this is in this draft ?
Reply8> In the previous WG discussions there was specific ask from Dave to =
add this section and explain the Keepalive Interval determination procedure=
 when PCP unaware Firewall or NAT is detected.

-Tiru.
From: Prashanth Patil (praspati)
Sent: Monday, October 21, 2013 3:51 AM
To: Reinaldo Penno (repenno); pcp@ietf.org<mailto:pcp@ietf.org>
Subject: Re: [pcp] Comments on draft-ietf-pcp-optimize-keepalives-00

Hi Reinaldo,
Sections "3.3 Detect PCP Unaware Firewall" and "4. Keepalive Interval Deter=
mination Procedure when PCP unaware Firewall or NAT is detected" were added=
 based on Dave's recommendation.

Section 3.3 does not introduce anything new, it only provides an example on=
 how a PCP unaware firewall can be detected using STUN. Section 4 is also a=
 recommendation on what can be potentially done if a PCP unaware firewall w=
as detected.

Dave, what are your thoughts on this?

-Prashanth

On 11/10/13 4:45 PM, "Reinaldo Penno (repenno)" <repenno@cisco.com<mailto:r=
epenno@cisco.com>> wrote:

I reviewed this draft for a possible WGLC but I do not think it is ready.
My summary is that this draft has lots of text related to detection of PCP
unaware NAT/FW using STUN which IMO belong in a separate draft, or some
other document since it is generic text. Maybe the WG sees value in having
a separate document that talks exclusively about detection of PCP unaware
FWs.

This draft could just say "assuming all NAT/FW in the path are PCP
aware..." and take it from there since the goal is optimizing keep-alive
and not standardizing detection mechanisms.

Removing all detection text would make this draft quite short and easier
to understand its purpose.

Thanks,

Reinaldo



--_000_CEC1A1156CFBrepennociscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <96FB2ECAA6EC604E94C5D1548E9988D9@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Thanks, looking forward to the new version</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&quot;Tirumaleswar Reddy (tir=
eddy)&quot; &lt;<a href=3D"mailto:tireddy@cisco.com">tireddy@cisco.com</a>&=
gt;<br>
<span style=3D"font-weight:bold">Date: </span>Monday, December 2, 2013 at 1=
:55 AM<br>
<span style=3D"font-weight:bold">To: </span>&quot;Prashanth Patil (praspati=
)&quot; &lt;<a href=3D"mailto:praspati@cisco.com">praspati@cisco.com</a>&gt=
;, Cisco Employee &lt;<a href=3D"mailto:repenno@cisco.com">repenno@cisco.co=
m</a>&gt;, &quot;<a href=3D"mailto:pcp@ietf.org">pcp@ietf.org</a>&quot;
 &lt;<a href=3D"mailto:pcp@ietf.org">pcp@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>RE: [pcp] Comments on draf=
t-ietf-pcp-optimize-keepalives-00<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: brea=
k-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class=3D"Section1">
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Hi Reinaldo,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Responding to your comments in the =
pdf<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Comment1&gt; The application keepal=
ive would keep the state alive in the FW/NAT as well, right ? This sentence=
 seems out of place here.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Reply1&gt; No. The time interval to=
 send keepalives for maintaining state on the Application Server could be g=
reater than FW/NAT mapping lifetime. In
 this case application keepalives will not maintain the FW/NAT mappings. Fo=
r example in case where application keepalive interval every 60 minutes is =
required whereas FW/NAT keepalive interval is 30 minutes.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Comment2&gt;&nbsp; I believe this s=
ection should have an introduction and two sub-sections. One sub=ACsection =
should be called =93PCP based detection=94 and have
 the first paragraph part of it since it only talks about PCP based detecti=
on. The second sub=ACsection should talk about application based detection.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Reply2&gt; Agreed, updated the draf=
t.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Comment3&gt; Then the title of this=
 section needs to change to =93NAT Topologies and Detection=94<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Reply3&gt; Yes, changed the title.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Comment4&gt; Suggest to change titl=
e to =93Detection of..=94. But more generally, I wonder if this discussion =
of detection belongs in this draft. Can this&nbsp;
 section be removed ? <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Reply4&gt; Yes, changed the title. =
In the previous WG discussions there was specific ask to add this section e=
xplaining the &quot;Detection of PCP Unaware
 Firewalls&quot;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Comment5&gt; Needs RFC reference<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Reply4&gt; RFC reference is already=
 provided
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Comment 6&gt;It will insert if it s=
upports this experimental RFC, if it has another IP address, etc. I believe=
 some more clarification is needed.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Reply6&gt; Agreed, updated the text=
.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Comment 7&gt; Application layer pro=
tocols ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Reply7&gt; Yes<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Comment 8&gt; This is all STUN, why=
 this is in this draft ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Reply8&gt; In the previous WG discu=
ssions there was specific ask from Dave to add this section and explain the=
 Keepalive Interval determination procedure
 when PCP unaware Firewall or NAT is detected.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">-Tiru.<o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif;">From:</span></b><span style=3D"font-size: 10pt; font-famil=
y: Tahoma, sans-serif;"> Prashanth Patil (praspati)
<br>
<b>Sent:</b> Monday, October 21, 2013 3:51 AM<br>
<b>To:</b> Reinaldo Penno (repenno); <a href=3D"mailto:pcp@ietf.org">pcp@ie=
tf.org</a><br>
<b>Subject:</b> Re: [pcp] Comments on draft-ietf-pcp-optimize-keepalives-00=
<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">Hi Reinaldo,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">Sections &quot;<i>3.3 Detect PCP Unaware Fir=
ewall</i>&quot; and &quot;<i>4. Keepalive Interval Determination Procedure =
when PCP unaware Firewall or NAT is detected</i>&quot; were
 added based on Dave's recommendation.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">Section 3.3 does not introduce anything new,=
 it only provides an example on how a PCP unaware firewall can be detected =
using STUN. Section 4 is also a recommendation
 on what can be potentially done if a PCP unaware firewall was detected.<o:=
p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">Dave, what are your thoughts on this?<o:p></=
o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">-Prashanth<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">On 11/10/13 4:45 PM, &quot;Reinaldo Penno (r=
epenno)&quot; &lt;<a href=3D"mailto:repenno@cisco.com">repenno@cisco.com</a=
>&gt; wrote:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;
margin-left:3.75pt;margin-right:0in" id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUO=
TE">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">I reviewed this draft for a possible WGLC bu=
t I do not think it is ready.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">My summary is that this draft has lots of te=
xt related to detection of PCP<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">unaware NAT/FW using STUN which IMO belong i=
n a separate draft, or some<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">other document since it is generic text. May=
be the WG sees value in having<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">a separate document that talks exclusively a=
bout detection of PCP unaware<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">FWs.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">This draft could just say &quot;assuming all=
 NAT/FW in the path are PCP<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">aware...&quot; and take it from there since =
the goal is optimizing keep-alive<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">and not standardizing detection mechanisms.<=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">Removing all detection text would make this =
draft quite short and easier<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">to understand its purpose.<o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">Thanks,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;">Reinaldo<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_CEC1A1156CFBrepennociscocom_--

From internet-drafts@ietf.org  Mon Dec  2 20:13:35 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0B81ADF38; Mon,  2 Dec 2013 20:13:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5NcuUhlZptKy; Mon,  2 Dec 2013 20:13:33 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C87101ADE84; Mon,  2 Dec 2013 20:13:33 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131203041333.27596.30225.idtracker@ietfa.amsl.com>
Date: Mon, 02 Dec 2013 20:13:33 -0800
Cc: pcp@ietf.org
Subject: [pcp] I-D Action: draft-ietf-pcp-optimize-keepalives-01.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: Tue, 03 Dec 2013 04:13:35 -0000

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

	Title           : Optimizing NAT and Firewall Keepalives Using Port Contro=
l Protocol (PCP)
	Author(s)       : Tirumaleswar Reddy
                          Markus Isomaki
                          Dan Wing
                          Prashanth Patil
	Filename        : draft-ietf-pcp-optimize-keepalives-01.txt
	Pages           : 15
	Date            : 2013-12-02

Abstract:
   This document describes how Port Control Protocol is useful to reduce
   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-01

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


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 mohamed.boucadair@orange.com  Mon Dec  2 23:20:48 2013
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 CF24D1AE07E for <pcp@ietfa.amsl.com>; Mon,  2 Dec 2013 23:20:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.549
X-Spam-Level: 
X-Spam-Status: No, score=-1.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54TeSFuxm1_5 for <pcp@ietfa.amsl.com>; Mon,  2 Dec 2013 23:20:47 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) by ietfa.amsl.com (Postfix) with ESMTP id 147621AE063 for <pcp@ietf.org>; Mon,  2 Dec 2013 23:20:46 -0800 (PST)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda13.si.francetelecom.fr (ESMTP service) with ESMTP id 771A41903BE for <pcp@ietf.org>; Tue,  3 Dec 2013 08:20:43 +0100 (CET)
Received: from PUEXCH51.nanterre.francetelecom.fr (unknown [10.101.44.31]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id 6114EC8089 for <pcp@ietf.org>; Tue,  3 Dec 2013 08:20:43 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by PUEXCH51.nanterre.francetelecom.fr ([10.101.44.31]) with mapi; Tue, 3 Dec 2013 08:20:43 +0100
From: <mohamed.boucadair@orange.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Date: Tue, 3 Dec 2013 08:20:40 +0100
Thread-Topic: I-D Action: draft-boucadair-pcp-flow-examples-03.txt
Thread-Index: Ac7v97FSCuE2QWtGT7KG7rg1R4y6kwAAEzrQ
Message-ID: <94C682931C08B048B7A8645303FDC9F36F38DAB88B@PUEXCB1B.nanterre.francetelecom.fr>
References: <20131203071659.10550.58773.idtracker@ietfa.amsl.com>
In-Reply-To: <20131203071659.10550.58773.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.12.2.94815
Subject: [pcp] TR: I-D Action: draft-boucadair-pcp-flow-examples-03.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, 03 Dec 2013 07:20:49 -0000

Dear all,

The document is updated to reflect recent changes to the base PCP spec (e.g=
., new nonce validation behavior).  You may refer to the diff for further d=
etails.

Cheers,
Med

-----Message d'origine-----
De=A0: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part de in=
ternet-drafts@ietf.org
Envoy=E9=A0: mardi 3 d=E9cembre 2013 08:17
=C0=A0: i-d-announce@ietf.org
Objet=A0: I-D Action: draft-boucadair-pcp-flow-examples-03.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.


	Title           : Port Control Protocol (PCP) Flow Examples
	Author(s)       : Mohamed Boucadair
	Filename        : draft-boucadair-pcp-flow-examples-03.txt
	Pages           : 34
	Date            : 2013-12-02

Abstract:
   This document provides a set of examples to illustrate Port Control
   Protocol (PCP) operations.  It is a companion document to the base
   PCP specification.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-boucadair-pcp-flow-examples-03

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


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/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

From tireddy@cisco.com  Tue Dec  3 01:49:55 2013
Return-Path: <tireddy@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 309E01AE0D8 for <pcp@ietfa.amsl.com>; Tue,  3 Dec 2013 01:49:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.502
X-Spam-Level: 
X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.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 xnBAeFD2iNQc for <pcp@ietfa.amsl.com>; Tue,  3 Dec 2013 01:49:53 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id C68EC1A1F71 for <pcp@ietf.org>; Tue,  3 Dec 2013 01:49:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2102; q=dns/txt; s=iport; t=1386064191; x=1387273791; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=tlK0fc4SSn5uWC1L3xOGeHSK64WjlHHqiaTIoOY6S4I=; b=BKfeAFCLPGeeD/kzMTihl0zKG38GWspb/p4O7rF4DoZ7ObVvAu1lTzDI ytJFukeeiaocbKyYqcWKJFpueNohrOshZDisMcJsMx2Lk+RiNZ0phDNpd hxGrgjGprwPs7/b3wqvjLnhq1f+OppmoTCxQCnxKWUA8gFD+fWHHIUhmG 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Am4GABipnVKtJV2d/2dsb2JhbABagwc4TQaCerVtGIEBFm0HgiUBAQEEIxFDDgYBCBEEAQEDAgYdAwIEMBQBBgEBBQUEEwgBh3gIBaFMjwuQPBeBKY0kPoJlNYETA5lEkGODKYIq
X-IronPort-AV: E=Sophos;i="4.93,816,1378857600";  d="scan'208";a="3903243"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-5.cisco.com with ESMTP; 03 Dec 2013 09:49:51 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id rB39npB9014082 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <pcp@ietf.org>; Tue, 3 Dec 2013 09:49:51 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.250]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0123.003; Tue, 3 Dec 2013 03:49:50 -0600
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Version Notification for draft-ietf-pcp-optimize-keepalives-01.txt
Thread-Index: AQHO794Jcz6WLg3xg0WYUrWaN2xRdJpB42Kw
Date: Tue, 3 Dec 2013 09:49:50 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A24271DD9@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.103.237.29]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [pcp] FW: New Version Notification for draft-ietf-pcp-optimize-keepalives-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, 03 Dec 2013 09:49:55 -0000

VGhpcyByZXZpc2lvbiBhZGRyZXNzZXMgdGhlIGNvbW1lbnRzIGZyb20gUmVpbmFsZG8gYW5kIEFu
Y2EuIA0KDQotVGlydS4NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGludGVy
bmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10gDQpT
ZW50OiBUdWVzZGF5LCBEZWNlbWJlciAwMywgMjAxMyA5OjQ0IEFNDQpUbzogTWFya3VzIElzb21h
a2k7IFRpcnVtYWxlc3dhciBSZWRkeSAodGlyZWRkeSk7IERhbiBXaW5nIChkd2luZyk7IFByYXNo
YW50aCBQYXRpbCAocHJhc3BhdGkpDQpTdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24g
Zm9yIGRyYWZ0LWlldGYtcGNwLW9wdGltaXplLWtlZXBhbGl2ZXMtMDEudHh0DQoNCg0KQSBuZXcg
dmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWlldGYtcGNwLW9wdGltaXplLWtlZXBhbGl2ZXMtMDEudHh0
DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFRpcnVtYWxlc3dhciBSZWRkeSBh
bmQgcG9zdGVkIHRvIHRoZQ0KSUVURiByZXBvc2l0b3J5Lg0KDQpGaWxlbmFtZToJIGRyYWZ0LWll
dGYtcGNwLW9wdGltaXplLWtlZXBhbGl2ZXMNClJldmlzaW9uOgkgMDENClRpdGxlOgkJIE9wdGlt
aXppbmcgTkFUIGFuZCBGaXJld2FsbCBLZWVwYWxpdmVzIFVzaW5nIFBvcnQgQ29udHJvbCBQcm90
b2NvbCAoUENQKQ0KQ3JlYXRpb24gZGF0ZToJIDIwMTMtMTItMDMNCkdyb3VwOgkJIHBjcA0KTnVt
YmVyIG9mIHBhZ2VzOiAxNQ0KVVJMOiAgICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL2lu
dGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLXBjcC1vcHRpbWl6ZS1rZWVwYWxpdmVzLTAxLnR4dA0K
U3RhdHVzOiAgICAgICAgICBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWll
dGYtcGNwLW9wdGltaXplLWtlZXBhbGl2ZXMNCkh0bWxpemVkOiAgICAgICAgaHR0cDovL3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1wY3Atb3B0aW1pemUta2VlcGFsaXZlcy0wMQ0KRGlm
ZjogICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1pZXRm
LXBjcC1vcHRpbWl6ZS1rZWVwYWxpdmVzLTAxDQoNCkFic3RyYWN0Og0KICAgVGhpcyBkb2N1bWVu
dCBkZXNjcmliZXMgaG93IFBvcnQgQ29udHJvbCBQcm90b2NvbCBpcyB1c2VmdWwgdG8gcmVkdWNl
DQogICBOQVQgYW5kIGZpcmV3YWxsIGtlZXBhbGl2ZSBtZXNzYWdlcyBmb3IgYSB2YXJpZXR5IG9m
IGFwcGxpY2F0aW9ucy4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KDQoNClBsZWFzZSBu
b3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9m
IHN1Ym1pc3Npb24NCnVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFp
bGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0DQoNCg==
