Re: [pcp] I-D Action: draft-ietf-pcp-optimize-keepalives-02.txt

Suresh Kumar Vinapamula Venkata <sureshk@juniper.net> Wed, 06 August 2014 01:56 UTC

Return-Path: <sureshk@juniper.net>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DEBC1A0AA2 for <pcp@ietfa.amsl.com>; Tue, 5 Aug 2014 18:56:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.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] 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 1Rj3CSnkL3YS for <pcp@ietfa.amsl.com>; Tue, 5 Aug 2014 18:56:16 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0235.outbound.protection.outlook.com [207.46.163.235]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D64E41A064A for <pcp@ietf.org>; Tue, 5 Aug 2014 18:56:15 -0700 (PDT)
Received: from DM2PR05MB288.namprd05.prod.outlook.com (10.141.101.11) by DM2PR05MB286.namprd05.prod.outlook.com (10.141.101.12) with Microsoft SMTP Server (TLS) id 15.0.995.14; Wed, 6 Aug 2014 01:56:13 +0000
Received: from DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) by DM2PR05MB288.namprd05.prod.outlook.com ([10.141.101.11]) with mapi id 15.00.0995.014; Wed, 6 Aug 2014 01:56:13 +0000
From: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Thread-Topic: [pcp] I-D Action: draft-ietf-pcp-optimize-keepalives-02.txt
Thread-Index: AQHPp/2D+8xIngxWNkG2Wk4iRIA4lJvCbdkA
Date: Wed, 06 Aug 2014 01:56:12 +0000
Message-ID: <D006BD6E.48D64%sureshk@juniper.net>
In-Reply-To: <20140725114217.27827.1300.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [66.129.239.10]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 02951C14DC
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(377424004)(24454002)(51704005)(199002)(189002)(479174003)(377454003)(36756003)(101416001)(87936001)(46102001)(4396001)(110136001)(21056001)(83072002)(86362001)(85852003)(74502001)(15202345003)(92726001)(85306004)(105586002)(81342001)(76482001)(81542001)(20776003)(106116001)(106356001)(64706001)(80022001)(107046002)(99286002)(66066001)(95666004)(50986999)(54356999)(79102001)(83506001)(15975445006)(77982001)(99396002)(19580395003)(83322001)(19580405001)(2656002); DIR:OUT; SFP:; SCL:1; SRVR:DM2PR05MB286; H:DM2PR05MB288.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-ID: <53E7FF1E40532A4F9619F2F7874F12A4@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/SFpf6M9xka5CPKYvXbENeV8vJ-s
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] I-D Action: draft-ietf-pcp-optimize-keepalives-02.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, 06 Aug 2014 01:56:18 -0000

Hi Tiru, 

Very important problem to solve especially in mobile deployments, and
interesting solution.

1) When you say PCP unaware NAT/FW you also meant, NAT/FW deployments with
PCP server and PCP clients are not ware of that PCP server credentials
right?

2) In typical deployments, inactivity timeout would be configured at the
application level in NAT/Firewall boxes. In case of PCP unaware FW/NAT, if
approach in section 4 is followed, wouldn't applications may determine
false inactivity timeouts which could result in disruption of traffic?

3) There is a typo in section 3.4. I think you meant RFC 6887 and not RFC
6877 and also the hyperlinks seems to be broken. And how is 3.4 different
from 10.3 in 6887?


-Suresh


On 7/25/14 4:42 AM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>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/
>
>_______________________________________________
>pcp mailing list
>pcp@ietf.org
>https://www.ietf.org/mailman/listinfo/pcp