Re: [Idr] WGLC on draft-ietf-idr-as-private-reservation-00

Robert Raszuk <robert@raszuk.net> Tue, 11 December 2012 16:54 UTC

Return-Path: <rraszuk@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D768221F8762 for <idr@ietfa.amsl.com>; Tue, 11 Dec 2012 08:54:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.64
X-Spam-Level:
X-Spam-Status: No, score=-2.64 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_LOW=-1]
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 HCwlHCi+1zhP for <idr@ietfa.amsl.com>; Tue, 11 Dec 2012 08:54:03 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 665E121F871A for <idr@ietf.org>; Tue, 11 Dec 2012 08:54:03 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so3380137lah.31 for <idr@ietf.org>; Tue, 11 Dec 2012 08:54:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=nZBiKqE9eC17sDMJfJprqpebcTavVeeHdvNptALD8aU=; b=aWvc/F+TlxrXelblVP768OxcGngPYs6oAvDelp9pyZXIg29K+AkpOiiOmex7tmV3Ht 0OM54PzET+OKZmBXfr9USqOxNQ2UFqdl2j6ur07DaYH/SeoD4A5uwktVgkXqep6IILsp JTYxGa8H/FPBroLdk4XeaK16ZbtVb7R9OvU+UBP+wziAELKIXpgwa84Aijszokb0s6ak VF+960bU1wMT49RbdMlQ9E3tJ+3i/hp8EWFbXsPY0pxibECxe3NZ9e8Msd1vsnwlYnHN 9t+KmoqM/ltJHSe3EuqJ9Yw04ZkDyN+BBGOGUA001TdJ10LnoZ81vY8RtEzhP977gc/4 qLXw==
MIME-Version: 1.0
Received: by 10.152.104.226 with SMTP id gh2mr2543065lab.24.1355244842243; Tue, 11 Dec 2012 08:54:02 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.112.133.41 with HTTP; Tue, 11 Dec 2012 08:54:02 -0800 (PST)
In-Reply-To: <m2d2yh32cw.wl%randy@psg.com>
References: <CA+b+ERnuWZ+r2O-eFhe3hU00uoU4UKnRcbhLNVXU7p5+DjoWbQ@mail.gmail.com> <C6C16AE3B7961044B04A1BCEC6E2F93603D12A0C@xmb-rcd-x14.cisco.com> <20121210225858.GC24937@puck.nether.net> <m2d2yh32cw.wl%randy@psg.com>
Date: Tue, 11 Dec 2012 17:54:02 +0100
X-Google-Sender-Auth: WSy0f-DPRi6v_PAqfwRU_PuDtH0
Message-ID: <CA+b+ERnSVvewSpftXs3FhW12-S+sgnB1SwD4L+xqFW+hhbQayw@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: idr wg <idr@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: Re: [Idr] WGLC on draft-ietf-idr-as-private-reservation-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2012 16:54:06 -0000

All,

I think Jon should remove any use case examples from the draft as
there is no way one could enforce that the new range will _only_ be
used in those use cases.

I think Jon in fact already said it very clearly that the point of the
draft is to get IANA registration. That' it - no more no less.

It would be up to individual operators to use such new range in L3VPNs
as Shane points out, in DCs or for that matter in ISPs.

Also it seems that it could be useful for dynamically routed home
gateways and in that respect I think the current range may be in fact
too small so I am sympathetic to broaden this space. If this is bit
boundary aligned or human aligned I think is secondary .. I have no
personal preference.

Many thx,
R.



On Tue, Dec 11, 2012 at 12:37 AM, Randy Bush <randy@psg.com> wrote:
> this misses my point entirely.  we know not to announce private ASs.
>
> my point was
>
>   o i do not accept the use example in the draft as justification
>     for an allocation of more private ASs.  in fact, i object to
>     it and specifically object to the draft being advanced.  we do
>     this already without your requested allocation which then can
>     only be viewed as an end-run around the IR system.
>
>   o i can see tli's point about use in large datacenter deployments.
>     if the draft is changed to use that (or a similar real need) as
>     the motivation, i would reconsider my objection.
>
> apologies, but i do not know how to be more clear.
>
> randy
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr