Re: Gen-ART LC review of draft-ietf-pcp-description-option-03

Simon Perreault <simon.perreault@viagenie.ca> Mon, 27 January 2014 15:46 UTC

Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46F1A1A0228 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 07:46:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level:
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, 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 ihB6oh-Dretb for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 07:46:02 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id CDA911A0235 for <ietf@ietf.org>; Mon, 27 Jan 2014 07:45:58 -0800 (PST)
Received: from porto.nomis80.org (ringo.viagenie.ca [IPv6:2620:0:230:c000:3e97:eff:fe0b:dd8a]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 85554403CA for <ietf@ietf.org>; Mon, 27 Jan 2014 10:45:56 -0500 (EST)
Message-ID: <52E67F34.1050404@viagenie.ca>
Date: Mon, 27 Jan 2014 10:45:56 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Gen-ART LC review of draft-ietf-pcp-description-option-03
References: <033d01cf1b42$854c10e0$8fe432a0$@gmail.com> <CF0B68F0.8395%repenno@cisco.com> <035301cf1b46$d54ba980$7fe2fc80$@gmail.com>
In-Reply-To: <035301cf1b46$d54ba980$7fe2fc80$@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 15:46:04 -0000

Le 2014-01-27 05:02, Roni Even a écrit :
> This should be stated and I assume that it is not for standardization
> but not clear why the entity operating the PCP server needs it, is it
> described in another document.
>
> I am curious why querying the PCP server is “out of scope” and not is
> “for further work”.

Example use case: you have several hosts in your home that do PCP 
automatically. For example, you start up Transmission, a BitTorrent 
client, and that automatically fires a PCP request to create a mapping. 
Transmission could set a description such as "Transmission BitTorrent 
client running on Roni Even's MacBook Pro". This is useful when you 
access your home router's administration web interface and see the list 
of mappings created with PCP. You can immediately understand what it is 
that is opening holes in your firewall/NAT.

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