IETF Logo Mail Archive

Re: [homenet] I-D Action: draft-haddad-homenet-multihomed-00

Michael Thomas <mike@mtcc.com> Tue, 23 October 2012 17:28 UTC

Return-Path: <mike@mtcc.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0014B1F0C89 for <homenet@ietfa.amsl.com>; Tue, 23 Oct 2012 10:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level:
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id exy0EDiW4Ubb for <homenet@ietfa.amsl.com>; Tue, 23 Oct 2012 10:28:28 -0700 (PDT)
Received: from mtcc.com (mtcc.com [IPv6:2001:5a8:4:9fe0:224:8cff:feaa:6d9b]) by ietfa.amsl.com (Postfix) with ESMTP id 473701F0425 for <homenet@ietf.org>; Tue, 23 Oct 2012 10:28:28 -0700 (PDT)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.14.3/8.14.3) with ESMTP id q9NHSONL003496 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 23 Oct 2012 10:28:25 -0700
Message-ID: <5086D3B8.3040909@mtcc.com>
Date: Tue, 23 Oct 2012 10:28:24 -0700
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Teco Boot <teco@inf-net.nl>
References: <201210011801.q91I1tfW056624@gateway1.orleans.occnc.com> <7F6EA97D-5DA8-4872-A647-D879B1955824@gmail.com> <49FCFE49-9DFB-44D2-ADAD-636A3C80F906@ecs.soton.ac.uk> <EMEW3|09bc323dc12a06be7c21e18f2752cd05o9LECn03tjc|ecs.soton.ac.uk|49FCFE49-9DFB-44D2-ADAD-636A3C80F906@ecs.soton.ac.uk> <7F4B245F-9355-4134-9176-EB7DB1634469@apple.com> <77A8749D-DF81-4816-8277-CB69861E524A@fugue.com> <C3720598-400C-4B83-9CEC-878B3FA8109E@ecs.soton.ac.uk> <EMEW3|3e5d3f7836c5b4ddbd99d74df88ecc6ao9LJ8r03tjc|ecs.soton.ac.uk|C3720598-400C-4B83-9CEC-878B3FA8109E@ecs.soton.ac.uk> <5085905A.8030206@mtcc.com> <52E31542-3B7C-4EC1-9B2C-3C9D8E6B3BB1@apple.com> <50859C1B.7070707@mtcc.com> <CAKD1Yr0v3NdN+QCj=jFiZcv0ox1S-YAj29dZyMd6kAWAv723dg@mail.gmail.com> <5086B5A7.3040706@mtcc.com> <BCBB5332-50EF-40CB-A741-76CD8239CF2A@inf-n! et.nl> <5086D19C.4040002@mtcc.com> <91FB983E-7D99-434E-9B09-B842D53F7A31@inf-net.nl>
In-Reply-To: <91FB983E-7D99-434E-9B09-B842D53F7A31@inf-net.nl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=648; t=1351013308; x=1351877308; c=relaxed/simple; s=thundersaddle.kirkwood; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:=20Michael=20Thomas=20<mike@mtcc.com> |Subject:=20Re=3A=20[homenet]=20I-D=20Action=3A=20draft-had dad-homenet-multihomed-00 |Sender:=20 |To:=20Teco=20Boot=20<teco@inf-net.nl> |Content-Type:=20text/plain=3B=20charset=3DISO-8859-1=3B=20 format=3Dflowed |Content-Transfer-Encoding:=207bit |MIME-Version:=201.0; bh=f3OQ1X00ShC7Qe3ftGl43EXgk+hxdUg4vMj7hF8+Vxc=; b=Lyh3573+D7YngIDC+68Q5SbE3kt/3Cnj80SzQvp687DNJ6f816FIpPBZKw jg6hInNBmDiPaGwBd0Sp27EFVCodWBgvCuUNHdyjjMJULn5cipjyofrqs6+h TXvfI4Fhq2YEcCyBMrzMepznBfIfqVPFQPhsXkwhHPuJGIqNk8Y+I=;
Authentication-Results: ; v=0.1; dkim=pass header.i=mike@mtcc.com ( sig from mtcc.com/thundersaddle.kirkwood verified; ); dkim-asp=pass header.From=mike@mtcc.com
Cc: homenet@ietf.org
Subject: Re: [homenet] I-D Action: draft-haddad-homenet-multihomed-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 17:28:29 -0000

On 10/23/2012 10:25 AM, Teco Boot wrote:
>
> I'm not sure if giving each host a
> prefix in 2001:yyyy's address space is scalable either for the hosts, the SLAAC
> announcements, or just carving up 2001:yyyy's addresses, especially if you have
> a large VPN population. I've done that myself, and I have doubts that it's the
> right approach.
> I can't get why employer doesn't assign a 2000:: address to the server, other
> than test uRPF filters and get protocol designers crazy :-)
>

They ran of space in the 2000:: allocation? They merged two companies?
There's lots of reasons why a company would have multiple prefixes.

Mike

v2.23.0 | Report a Bug | By Email