Re: [pcp] WGLC: draft-ietf-pcp-anycast-02 comments due by NOV 10

🔓Dan Wing <dwing@cisco.com> Tue, 04 November 2014 08:55 UTC

Return-Path: <dwing@cisco.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 EBFA91A890D for <pcp@ietfa.amsl.com>; Tue, 4 Nov 2014 00:55:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.795
X-Spam-Level:
X-Spam-Status: No, score=-14.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 hNuycKnRYxDc for <pcp@ietfa.amsl.com>; Tue, 4 Nov 2014 00:55:02 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CBD71A890F for <pcp@ietf.org>; Tue, 4 Nov 2014 00:55:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2236; q=dns/txt; s=iport; t=1415091302; x=1416300902; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=v6Y8z9DiHuM/74WvYENNbeIzQjO4lrGYClFkPcmPdXY=; b=kJTZQ1zMKGRxWHbNnroA97mpfpeUhDXPWiWAy2ws/HhPjvHhxVxaOCvh zgNuQ0PsKfDPi4PNdHvIbMYA1lfdiB9soEgRAIjx2PJw9MvxbJJjz437r 56jiOm0kIDrTbrMgIU7Pqsnik4j/+v/sFbfBaVxJs9sHQ2IZ6snhW8OjG Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAIyTWFStJV2Z/2dsb2JhbABcgw6BLNYoAoEgFgEBAQEBfYQCAQEBAwF5BQsLGC5XBhOIOAnLOwEBAQEBAQEBAQEBAQEBAQEBAQEBAReNQYJtCgcBHTMHgy2BHgWFG4ZbkguBMYNNgneOW4IOggscL4EGCReBJQEBAQ
X-IronPort-AV: E=Sophos;i="5.07,312,1413244800"; d="scan'208";a="93115087"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-3.cisco.com with ESMTP; 04 Nov 2014 08:55:01 +0000
Received: from [10.21.78.243] ([10.21.78.243]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id sA48sxTd001350 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 4 Nov 2014 08:55:00 GMT
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: 🔓Dan Wing <dwing@cisco.com>
In-Reply-To: <E9BFF7F2-AF64-4787-BFD6-C4F619C95B04@iki.fi>
Date: Tue, 04 Nov 2014 00:54:59 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B7123503-88EB-4274-BC3D-3F55AA31C4AB@cisco.com>
References: <0d54be2504534facaaaddfb275ba982d@BY2PR03MB412.namprd03.prod.outlook.com> <E9BFF7F2-AF64-4787-BFD6-C4F619C95B04@iki.fi>
To: Markus Stenberg <markus.stenberg@iki.fi>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/pUelwInYG9Zr3jZlu7zl9wWvjdU
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] WGLC: draft-ietf-pcp-anycast-02 comments due by NOV 10
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: Tue, 04 Nov 2014 08:55:04 -0000

On Oct 30, 2014, at 1:33 AM, Markus Stenberg <markus.stenberg@iki.fi> wrote:

> On 27.10.2014, at 22.23, Dave Thaler <dthaler@microsoft.com> wrote:
>> This email initiates a Working Group Last Call on : draft-ietf-pcp-anycast-02 to conclude on
>> Monday, November 10th at the PCP WG meeting in Honolulu.  Please send comments to the list.
>> 
>> As a reminder, when responding to a WGLC, what we chairs are looking for is a statement about
>> document quality (not really about whether the mechanism should move forward).  That is,
>> state whether you think the document is ready as is, or if not, what issues you see.
> 
> I think the document (and the mechanism) is mostly fine and needed.
> 
> What I am wondering about is security considerations section; given implementations not aware of this draft, a host on the inner side can also advertise the anycast address, and potentially get traffic meant for first-hop PCP server. Given the scheme defined in section 2.1 (SHOULD use first-hop first), it is possible, although not probable. But still, I would say the same problem is both on local network(s) _and_ on the other side of the firewall.

I agree such an attack would work if the PCP client (or the router) listen to a routing protocol and the attacker advertises the PCP anycast address's network using that routing protocol.  But on the local network the PCP client won't ARP for an address beyond its own subnet, so the attack seems limited to where a routing protocol is being used?

> (It could also state that finding (platform independently) next-hop gateway programmatically can be hard for pure ‘applications’ sometimes, but I wonder if this is too much detail.

Earlier in PCP's development I recall some sample code was rolling around for how to find first-hop gateway on several OSs.

> But if app just chose anycast address, the above SHOULD would not be followed and the security considerations problems would be more severe.)
> 
> Also.. Is there actually defined mechanism to redirect or provide list of PCP servers that is mentioned in the introduction?

There isn't; that sentence should be removed.

-d