IETF Logo Mail Archive

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

Ted Lemon <ted.lemon@nominum.com> Sat, 01 February 2014 21:07 UTC

Return-Path: <Ted.Lemon@nominum.com>
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 DFE0E1ABD2A for <ietf@ietfa.amsl.com>; Sat, 1 Feb 2014 13:07:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 YV4mRIS4etrg for <ietf@ietfa.amsl.com>; Sat, 1 Feb 2014 13:07:29 -0800 (PST)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id 6D8271A1F76 for <ietf@ietf.org>; Sat, 1 Feb 2014 13:07:29 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKUu1iDQeTCKgp0SVPe7U205pXEZF3y3CE@postini.com; Sat, 01 Feb 2014 13:07:25 PST
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 186EC1B82F4 for <ietf@ietf.org>; Sat, 1 Feb 2014 13:07:25 -0800 (PST)
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 F3C17190052; Sat, 1 Feb 2014 13:07:24 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 1 Feb 2014 13:07:24 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Gen-ART LC review of draft-ietf-pcp-description-option-03
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52E67F34.1050404@viagenie.ca>
Date: Sat, 01 Feb 2014 16:07:22 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <FB1343A5-63DE-42FF-BE11-4B4CB82CE8C9@nominum.com>
References: <033d01cf1b42$854c10e0$8fe432a0$@gmail.com> <CF0B68F0.8395%repenno@cisco.com> <035301cf1b46$d54ba980$7fe2fc80$@gmail.com> <52E67F34.1050404@viagenie.ca>
To: Simon Perreault <simon.perreault@viagenie.ca>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: IETF Discussion <ietf@ietf.org>
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: Sat, 01 Feb 2014 21:07:31 -0000

On Jan 27, 2014, at 10:45 AM, Simon Perreault <simon.perreault@viagenie.ca> wrote:
> 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.

Any reason not to add some text to the document that talks about this?   I have to admit that I wasn't confused by this after reading the document, but if Roni was, that's an indication that at least something ought to be tweaked, since there will be other readers who similarly lack context.

v2.23.0 | Report a Bug | By Email