Re: Routing between hosts in ULA subnets

Rajiv Asati <rajiva@cisco.com> Fri, 23 March 2012 19:51 UTC

Return-Path: <rajiva@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C367121F85F0; Fri, 23 Mar 2012 12:51:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.117
X-Spam-Level:
X-Spam-Status: No, score=-10.117 tagged_above=-999 required=5 tests=[AWL=0.482, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 WHwP36VLueK0; Fri, 23 Mar 2012 12:51:53 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 58C8721F85E3; Fri, 23 Mar 2012 12:51:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rajiva@cisco.com; l=3136; q=dns/txt; s=iport; t=1332532313; x=1333741913; h=date:subject:from:to:message-id:in-reply-to:mime-version: content-transfer-encoding; bh=1DXCX6PY58i2PiFDy9FzkyAbthXoZ+mX6U7JiAnSCmU=; b=MGadmurNjOYViTaoqe7NMB0re9M5rWxy5A2JyY7IJ0bCs+doqZstz9Wt PqlXyRXDCkzZ0eDY3qEB4Arpxuz6xoRtOMdN61CPYNQofHyWWZEo0TGBT n74gqcDVza2D1eh+EuZr+bu2rOU7N6+9KXyUX7VH9E1dd0FJFZXyWr8sF w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAOPTbE+tJV2Z/2dsb2JhbABFDrgHgQeCCQEBAQMBAQEBDwEnAgExEAcHCBEDAQJQBigIBgESIodjBQuZeJ51BIlthxgElWCFboVCgxSBaIIwUw
X-IronPort-AV: E=Sophos;i="4.73,637,1325462400"; d="scan'208";a="68994671"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-8.cisco.com with ESMTP; 23 Mar 2012 19:51:53 +0000
Received: from [64.102.202.94] (dhcp-64-102-202-94.cisco.com [64.102.202.94]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q2NJpjKl006982; Fri, 23 Mar 2012 19:51:48 GMT
User-Agent: Microsoft-MacOutlook/14.14.0.111121
Date: Fri, 23 Mar 2012 15:51:43 -0400
Subject: Re: Routing between hosts in ULA subnets
From: Rajiv Asati <rajiva@cisco.com>
To: Anders Brandt <Anders_Brandt@sigmadesigns.com>, 6man <ipv6@ietf.org>, Tim Chown <tjc@ecs.soton.ac.uk>, Don Sturek <d.sturek@att.net>, "homenet@ietf.org Group" <homenet@ietf.org>, Ray Hunter <v6ops@globis.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Thomas Herbst <therbst@silverspringnet.com>
Message-ID: <CB924828.44FD%rajiva@cisco.com>
Thread-Topic: Routing between hosts in ULA subnets
In-Reply-To: <03F31C213F2C6941BFDDBB4336E9E6CD0ABC216F@cph-ex1>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Mar 2012 19:51:57 -0000

Andres,

Thanks for writing up this use-case.  Quick Q - What global ID would get
used in the ULA (assuming GUA is not known yet)?

> In a homenet case, why cannot the default ULA policy be boiled down to
>"Discard 
> ULA packets trying to pass the CER"?


That would be reasonable. Perhaps, just deny forwarding any traffic over
an interface that doesn't have any ULA assigned.

Cheers,
Rajiv

-----Original Message-----
From: Anders Brandt <Anders_Brandt@sigmadesigns.com>
Date: Thu, 22 Mar 2012 10:00:56 +0000
To: 6man <ipv6@ietf.org>, Tim Chown <tjc@ecs.soton.ac.uk>, Don Sturek
<d.sturek@att.net>, "homenet@ietf.org Group" <homenet@ietf.org>, Ray
Hunter <v6ops@globis.net>, Brian E Carpenter
<brian.e.carpenter@gmail.com>, Thomas Herbst <therbst@silverspringnet.com>
Subject: Routing between hosts in ULA subnets

>As a branch of the discussion [homenet] ULA scope
>[draft-ietf-6man-rfc3484-revise-05.txt],
>I would like some clear explanation of the actual issues related to
>routing between hosts in ULA subnets.
>Some people seems to be concerned for a reason that seems pretty unclear
>to me.
> 
>Here is my use case:
>=================
> 
>I have a new house. The electrician installs lighting devices from two
>vendors using different LLN technologies,
>e.g. power line and RF.
>The ISP has not installed a CER router yet, so there is no central source
>of prefixes or naming service.
> 
>The electrician completes his installation by including devices with
>their respective border routers and testing
>
>with a stand-alone tool that all devices communicate correctly.
> 
>Now a technician sets up advanced rules for how timers and sensors
>control lights and window blinds.
>He plugs a cable between the two LLN border routers and connects a PC.
>He uses mDNS to discover the devices via Resource Directories in the LLN
>border routers.
>Devices are configured to control other devices using some application
>protocol.
>Everything works when the technician leaves the house.
> 
>A week later the ISP installs the CER router. Everything still works.
> 
> 
>Here is my question(s):
>==================
> 
>Why should homenet require the subnet ULAs to be distributed from another
>router?
>
>It works without extra routers in the scenario described above.
>
>(Actually, the technician's configuration would break if new ULAs were
>distributed by another router later on).
> 
>Why cannot two border routers connected to the homenet LAN make routing
>protocol announcements
>
>for two different ULA prefixes - such as:
>"I am the router with LAN link-local address X and you can use me to
>reach ULA subnet XX"  ?
> 
>In a homenet case, why cannot the default ULA policy be boiled down to
>"Discard ULA packets trying to pass the CER"?
> 
> 
>Thanks,
>  Anders
> 
> 
>
>
>--------------------------------------------------------------------
>IETF IPv6 working group mailing list
>ipv6@ietf.org
>Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>--------------------------------------------------------------------