[pcp] Spencer Dawkins' Discuss on draft-ietf-pcp-proxy-08: (with DISCUSS and COMMENT)
"Spencer Dawkins" <spencerdawkins.ietf@gmail.com> Thu, 09 July 2015 12:15 UTC
Return-Path: <spencerdawkins.ietf@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 D84FB1AD2DF; Thu, 9 Jul 2015 05:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=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 1XjX2J-fHR_H; Thu, 9 Jul 2015 05:15:13 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 87DD31A8A58; Thu, 9 Jul 2015 05:15:13 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.4.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150709121513.3109.99513.idtracker@ietfa.amsl.com>
Date: Thu, 09 Jul 2015 05:15:13 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/pcp/b7F9VK4gpyRNUtTcXtD0WpwdM0g>
Cc: pcp@ietf.org
Subject: [pcp] Spencer Dawkins' Discuss on draft-ietf-pcp-proxy-08: (with DISCUSS and COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Jul 2015 12:15:16 -0000
Spencer Dawkins has entered the following ballot position for draft-ietf-pcp-proxy-08: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-pcp-proxy/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- This should be an easy Discuss to resolve. I was surprised to see In addition, this goes against the spirit of NAT gateways. The main purpose of a NAT gateway is to make multiple downstream client devices making outgoing TCP connections to appear, from the point of ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ view of everything upstream of the NAT gateway, to be a single client device making outgoing TCP connections. In the same spirit, it makes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sense for a PCP-capable NAT gateway to make multiple downstream client devices requesting port mappings to appear, from the point of view of everything upstream of the NAT gateway, to be a single client device requesting port mappings. limited to TCP connections. Is this intentional? https://tools.ietf.org/html/rfc6887#section-2.2 certainly lists other transport protocols. Is it correct to say In addition, this goes against the spirit of NAT gateways. The main purpose of a NAT gateway is to make multiple downstream client devices to appear, from the point of view of everything upstream of the NAT gateway, to be a single client device. ? Please note that I'm not objecting to the focus on TCP in this text: Where this document uses the terms "upstream" and "downstream", the term "upstream" refers to the direction outbound packets travel towards the public Internet, and the term "downstream" refers to the direction inbound packets travel from the public Internet towards client systems. Typically when a home user views a web site, their computer sends an outbound TCP SYN packet upstream towards the public Internet, and an inbound downstream TCP SYN ACK reply comes back from the public Internet. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I share Stephen's curiosity in his Discuss, but I'll follow along there (I saw Med responded 15 minutes ago).
- [pcp] Spencer Dawkins' Discuss on draft-ietf-pcp-… Spencer Dawkins
- Re: [pcp] Spencer Dawkins' Discuss on draft-ietf-… mohamed.boucadair
- Re: [pcp] Spencer Dawkins' Discuss on draft-ietf-… Spencer Dawkins at IETF