Re: [v6ops] PCP server in draft-ietf-v6ops-6204bis

james woodyatt <jhw@apple.com> Mon, 30 January 2012 20:17 UTC

Return-Path: <jhw@apple.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53AFC21F84F7; Mon, 30 Jan 2012 12:17:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.998
X-Spam-Level:
X-Spam-Status: No, score=-109.998 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Su2YZ7O0+B69; Mon, 30 Jan 2012 12:17:14 -0800 (PST)
Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 92D9821F84C9; Mon, 30 Jan 2012 12:17:14 -0800 (PST)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_2E1OyrqytBL2F0MU9bXWkw)"
Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0LYM00KCEOCFPUK1@mail-out.apple.com>; Mon, 30 Jan 2012 12:17:14 -0800 (PST)
X-AuditID: 11807136-b7c60ae000007a90-bb-4f26fac93ef7
Received: from kallisti.apple.com (kallisti.apple.com [17.193.13.64]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay15.apple.com (Apple SCV relay) with SMTP id B1.54.31376.9CAF62F4; Mon, 30 Jan 2012 12:17:13 -0800 (PST)
From: james woodyatt <jhw@apple.com>
In-reply-to: <2D09D61DDFA73D4C884805CC7865E611025B49@GAALPA1MSGUSR9N.ITServices.sbc.com>
Date: Mon, 30 Jan 2012 12:17:13 -0800
Message-id: <4A687585-399D-4077-91AC-A1DC4F101E03@apple.com>
References: "29 Jan 2012 09:51:52 PST." <85BE2EBF-C8AC-45E1-BF93-1E3066AD3172@apple.com> <201201301936.q0UJaEft000156@givry.fdupont.fr> <2D09D61DDFA73D4C884805CC7865E611025B49@GAALPA1MSGUSR9N.ITServices.sbc.com>
To: "STARK, BARBARA H" <bs7652@att.com>
X-Mailer: Apple Mail (2.1251.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNLMWRmVeSWpSXmKPExsUieJDXQffkLzV/g4YWa4tJf38yWty8epHF YvKx36wWp4/tZXZg8XjZP4fRY8mSn0weXy5/ZgtgjuKySUnNySxLLdK3S+DKODf7EkvBWa2K fe0bWRoYN6p0MXJySAiYSMx795ERwhaTuHBvPVsXIxeHkMBsJonbdxtYQBLCAtYSe9sfsYLY vALGEmtuvQOLMwskSPzsmcEMYrMJqEh8u3yXCcTmFIiQWDV7N1g9i4CqxPPX7awQ9akSG+9e Y4eYYyMxqec7E8Syy4wSve0/wYpEBNQlVk2bzgpxkbxEy9c7bBMY+WYh2T0LyW4IW1ti2cLX QDYHkK0jMXkhI6owhP3x/BGmBYxsqxgFi1JzEisNTfUSCwpyUvWS83M3MYKCuKHQbAfjjr9y hxgFOBiVeHh3vFfzF2JNLCuuzD3EKMHBrCTC+2Y1UIg3JbGyKrUoP76oNCe1+BCjNAeLkjjv VmtlfyGB9MSS1OzU1ILUIpgsEwenVAMjc9CqQzt5FK49W991lk+RN67RoXnzQ6a7EdHny4tK N5suU972K/NpEcOEY08S5j0NljqZ9OPxav1zfouWq3zN2p3udjzIzGY7i3rDHulwjytt8+Y0 9WbddPKoP+x185XuRFv5jb1Zr9YI3dikba229XBSnpF/XmsJl6fRivO3VAP3+TeeX6anxFKc kWioxVxUnAgAgJHXyF4CAAA=
Cc: IPv6 Operations <v6ops@ietf.org>, PCP <pcp@ietf.org>, draft-ietf-v6ops-6204bis@tools.ietf.org
Subject: Re: [v6ops] PCP server in draft-ietf-v6ops-6204bis
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jan 2012 20:17:15 -0000

On Jan 30, 2012, at 11:58 , STARK, BARBARA H wrote:
> 
> To come at this from a procedural angle, then...
> 
> With the advent of the homenet WG, I thought we agreed that we would not make any attempt to address new additional LAN technology recommendations in a 6204bis document. We said 6204bis would only try to deal with WAN-side transition technologies, and other "fix existing 6204 recommendations, because now we know better" changes.
> 
> Recommending PCP as a LAN technology is, IMO, a homenet issue. It has no place in 6204bis.


This reasoning applies just as well to the recommendation of RFC 6092 Simple Security, which is about protecting LAN hosts according to local network policy.

If recommending a PCP server is for HOMENET to do, and it has no place in RFC 6204bis from V6OPS, then recommending RFC 6092 Simple Security neither has any place in RFC 6204bis and it should therefore be removed, and a notice inserted into RFC 6204bis to explain why the previous document was in error and to note that forthcoming documents from HOMENET will address the issue properly.

I would very much like to get a better understanding of how you are reasoning on this issue.


--
j h woodyatt <jhw@apple.com>