IETF Logo Mail Archive

Re: [homenet] [94attendees] IPv6 Prefix delegation on IETF network, please ?

Ted Lemon <mellon@fugue.com> Thu, 05 November 2015 04:29 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 482451B361A; Wed, 4 Nov 2015 20:29:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 WFXagpzlBmDB; Wed, 4 Nov 2015 20:29:33 -0800 (PST)
Received: from fugue.com (mail-2.fugue.com [IPv6:2a01:7e01::f03c:91ff:fee4:ad68]) by ietfa.amsl.com (Postfix) with ESMTP id 32DD61B362D; Wed, 4 Nov 2015 20:29:29 -0800 (PST)
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="----sinikael-?=_1-14466977398810.1076087539549917"
From: Ted Lemon <mellon@fugue.com>
To: joelja@gmail.com
In-Reply-To: <563A938E.503@gmail.com>
References: <20151102055200.GI31730@cisco.com> <7iio5k5kpz.wl-jch@pps.univ-paris-diderot.fr> <5136.1446543935@dooku.sandelman.ca> <563A938E.503@gmail.com>
Date: Thu, 05 Nov 2015 04:28:59 +0000
Message-Id: <1446697740188-c19e4b9d-85a556f4-c02a14bb@fugue.com>
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/XdMm8_b4G28E2Gk4y2HCp86UF20>
Cc: eckert@cisco.com, jch@pps.univ-paris-diderot.fr, mcr+ietf@sandelman.ca, hackathon@ietf.org, 94attendees@ietf.org, homenet@ietf.org
Subject: Re: [homenet] [94attendees] IPv6 Prefix delegation on IETF network, please ?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 05 Nov 2015 04:29:35 -0000

Thursday, Nov 5, 2015 8:23 AM joel jaeggli wrote:
> we have discussed doing it before, it's mostly a question of having
> the right pieces in place and tested before hand. we have enough
> moving parts this time with new routers that it's maybe not the best
> place to be doing that also.
> 
> this network with respect to model/deployment looks more like an
> interprise or campus build and less like an ISP, it also has to
> contend with (in the case of the hotel net extensions) running on top
> of third party gear which it doesn't control.

There might be grist for a hackathon in this question.   I suspect that the needed tools are not all present.


--
Sent from Whiteout Mail - https://whiteout.io

My PGP key: https://keys.whiteout.io/mellon@fugue.com

v2.23.0 | Report a Bug | By Email