Re: [Fwd: I-D Action: draft-carpenter-6man-why64-01.txt]

sthaug@nethelp.no Wed, 12 March 2014 10:04 UTC

Return-Path: <sthaug@nethelp.no>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 353761A0644 for <ipv6@ietfa.amsl.com>; Wed, 12 Mar 2014 03:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level:
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] 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 Imv4jFXXQyDX for <ipv6@ietfa.amsl.com>; Wed, 12 Mar 2014 03:04:53 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id EA2621A0381 for <ipv6@ietf.org>; Wed, 12 Mar 2014 03:04:52 -0700 (PDT)
Received: (qmail 35263 invoked from network); 12 Mar 2014 10:04:44 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 12 Mar 2014 10:04:44 -0000
Date: Wed, 12 Mar 2014 11:04:44 +0100
Message-Id: <20140312.110444.78735090.sthaug@nethelp.no>
To: furry13@gmail.com
Subject: Re: [Fwd: I-D Action: draft-carpenter-6man-why64-01.txt]
From: sthaug@nethelp.no
In-Reply-To: <CAFU7BASks087R1NgU=ojvBYqTpwm9ukwEp_+4z5AZ6L-phTkzA@mail.gmail.com>
References: <CAFU7BATyuEoK_TEqAXqz2ONvuO9P0y45SpJ-q7DHsmF4pBaezg@mail.gmail.com> <531816D9.4050200@fud.no> <CAFU7BASks087R1NgU=ojvBYqTpwm9ukwEp_+4z5AZ6L-phTkzA@mail.gmail.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/8P2fe30U4Zd0ljL--WkTsMm2Tnc
Cc: tore@fud.no, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 12 Mar 2014 10:04:58 -0000

> > Could you be more specific? Which vendors, products, software versions,
> > have what kind of issue(s) specifically with prefixes >/64, exactly?
> 
> Juniper PTX has some h/w limitation so they initially could not
> install /65 - /126 into FIB. Currently it is possible but for limited
> number of routes.

Given the intended target market for PTX (high-end MPLS P routers) the
only IPv6 routes I would expect such a box to have are loopbacks and
maybe links.

Not being able to install such prefixes at all is a problem. Allowing
only a very limited number of such prefixes = "works as intended".

Steinar Haug, AS 2116