Re: [v6ops] What can v6ops do? [was: RIPE-555 fundamentaly changes the way how we can filter IPv6 & IPv4 martians?]

Tim Chown <tjc@ecs.soton.ac.uk> Thu, 12 July 2012 21:38 UTC

Return-Path: <tjc@ecs.soton.ac.uk>
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 D030F11E80D2 for <v6ops@ietfa.amsl.com>; Thu, 12 Jul 2012 14:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 0CcrTqo1MXrp for <v6ops@ietfa.amsl.com>; Thu, 12 Jul 2012 14:38:29 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id F2B1611E80A6 for <v6ops@ietf.org>; Thu, 12 Jul 2012 14:38:28 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q6CLd0ML000851 for <v6ops@ietf.org>; Thu, 12 Jul 2012 22:39:00 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk q6CLd0ML000851
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1342129140; bh=B/3MmtPrbvPqT8Kl9Yi8MZ+hBEU=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=WIe3Ji9Gl4+OfCLRhCu4MtlJ+gdcjg/MupwUTpeUf4eFPnvaA+VLfs6GxB3wvTwQ7 eA+Q9iIOVLvEINu6OV2ZTDCA3SBrMOHlLfjdipSqi9ztExFB3kF7k+nYHDa6nzJ6tH D0EGrqxQN6a437ORXA26KfWNxGx1P8PKw/F4G9lk=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id o6BMd01397511775zK ret-id none; Thu, 12 Jul 2012 22:39:00 +0100
Received: from [192.168.1.102] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q6CLcYwE005847 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <v6ops@ietf.org>; Thu, 12 Jul 2012 22:38:34 +0100
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1278)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20120712175734.GM38127@Space.Net>
Date: Thu, 12 Jul 2012 22:38:33 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|ce382c67941771e7d3f631a139de3271o6BMd003tjc|ecs.soton.ac.uk|2AA82FB4-F8D5-4B6E-BB07-D2AB19CE2A43@ecs.soton.ac.uk>
References: <4FFEC0A4.2070509@gmail.com> <m2k3y9du17.wl%randy@psg.com> <20120712131000.GC38127@Space.Net> <20120712.154239.133898240.he@uninett.no> <20120712142354.GH38127@Space.Net> <4FFF01AF.3000502@gmail.com> <20120712175734.GM38127@Space.Net> <2AA82FB4-F8D5-4B6E-BB07-D2AB19CE2A43@ecs.soton.ac.uk>
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1278)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=o6BMd0139751177500; tid=o6BMd01397511775zK; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: q6CLd0ML000851
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: Re: [v6ops] What can v6ops do? [was: RIPE-555 fundamentaly changes the way how we can filter IPv6 & IPv4 martians?]
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: Thu, 12 Jul 2012 21:38:30 -0000

On 12 Jul 2012, at 18:57, Gert Doering wrote:

> So - what can IETF do?
> 
> - make "multihoming with dual-/48" *work*, so one of the incentives for
>   end-site multihoming with a globally visible route goes away

Gert,

A perfect advertisement for the 6renum WG drafts, which are in need of review:

https://datatracker.ietf.org/doc/draft-ietf-6renum-enterprise

https://datatracker.ietf.org/doc/draft-liu-6renum-gap-analysis

https://datatracker.ietf.org/doc/draft-carpenter-6renum-static-problem

You can join the renum list here: https://www.ietf.org/mailman/listinfo/renum

Tim