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

Brian Dickson <brian.peter.dickson@gmail.com> Mon, 10 December 2012 21:58 UTC

Return-Path: <brian.peter.dickson@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 EF7AC21F8566 for <idr@ietfa.amsl.com>; Mon, 10 Dec 2012 13:58:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 KEI4lw0+ruSz for <idr@ietfa.amsl.com>; Mon, 10 Dec 2012 13:58:26 -0800 (PST)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id AD7F521F8496 for <idr@ietf.org>; Mon, 10 Dec 2012 13:58:17 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id a1so1381520eaa.31 for <idr@ietf.org>; Mon, 10 Dec 2012 13:58:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3c9UJvRP3+MWd+hBsZJ+pjDGiKbG5M2SCWE4KBUbVCc=; b=UchSOtAMnSvwOyW1x+pEnz1He8ErUVGmX/JllN5veRPg81KanKr1Y6qvdGj5QZVmcr ZheVddDH3h+/zD2yN2o0lRideELoRe+pHVbxNbe89mM0JMVpV13Wwp/Cf49XgxGAGRtA bYgvZXD6/5AT9N+XSIYjM/CmR7RhbPgfL9mYfeWrK2aB5rP1Sbc0cJKTCCv8POqmypVU 6tiRd7U2+qHwJ9h5ss+eSZA+KbNZtQdO+Vk3v9Tk19oBTxCwqfU4CMaLApthSiEnw8UJ rfAQrY0Y0III8FLzvWysWOI2qSKPs5ZiK3m7/qK66a131Fc87nUI7lnUdgdX/TkdKPOO Ui2g==
MIME-Version: 1.0
Received: by 10.14.225.194 with SMTP id z42mr54004721eep.22.1355176696856; Mon, 10 Dec 2012 13:58:16 -0800 (PST)
Received: by 10.223.173.199 with HTTP; Mon, 10 Dec 2012 13:58:16 -0800 (PST)
In-Reply-To: <CAPWAtbKA9vqk1W+Gm+iGdnV0QB+tENZnEyesFLXhJNjUydd5og@mail.gmail.com>
References: <B6B72499-E9D0-4281-84EB-6CA53694866E@juniper.net> <CAPWAtbJ72pHKCte5192tLzyDQ2RWWZPkDGfbbWOd2GGJCQ48Tg@mail.gmail.com> <20121210184009.GA20478@puck.nether.net> <CAPWAtbKA9vqk1W+Gm+iGdnV0QB+tENZnEyesFLXhJNjUydd5og@mail.gmail.com>
Date: Mon, 10 Dec 2012 16:58:16 -0500
Message-ID: <CAH1iCiqrto6VQkwZhhXHuBNH-VRZQ_3V_=DZWesg38Q4XgKpdA@mail.gmail.com>
From: Brian Dickson <brian.peter.dickson@gmail.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
Content-Type: multipart/alternative; boundary="047d7b66f24b9fc24f04d086a9ec"
Cc: idr@ietf.org
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: Mon, 10 Dec 2012 21:58:27 -0000

The as-dot/bit-boundary style typically uses a lot less space, and there
are several "nice" candidates:

64512.0 = 4227858432 (same start, shifted 16 bits left)
64850.0 = 4250009600 (the 4250000000 and up range is more human-friendly
without eating too much)
65000.0 = 4259840000 (has a bunch of zeros at the end, more
asplain-obvious?)
65280.0 = 4278190080 (currently in the draft)

Of course, it may also be reasonable to set aside a third range:
4000000000 through TBD2 as Reserved (not part of new range, nor part of
Public range, just "off limits", as a kind of DMZ).

That range can be freed up if need be later, e.g. once we have colonized
the galaxy. :-)

Brian

On Mon, Dec 10, 2012 at 4:18 PM, Jeff Wheeler <jsw@inconcepts.biz> wrote:

> On Mon, Dec 10, 2012 at 1:40 PM, Jon Mitchell <jrmitche@puck.nether.net>
> wrote:
> > The draft originally was more human/decimal boundary friendly before it
> > was a WG doc.  There has been some on list, some on meeting (Vancouver)
> > and some out of meeting discussions I did before we moved from nice
> > decimal boundary to nice bit or asplain friendly boundary).  Here is one
> > of the emails:
>
> I read the mail thread you linked, but it did not give me any
> understanding why folks prefer a bit-boundary instead of a
> human-readable boundary.  I will ask some more operator colleagues to
> give their opinions.  I am surprised anyone would think bit-boundary
> is the smartest choice if one of the alternatives looks nicer in the
> CLI/NMS.
>
> I understand what you mean if the CLI/NMS allows you to customize and
> create multiple prefixes like PRIVATEn and this might be nice for some
> applications.  However, VPLS has clearly figured this out with label
> blocks.  The applications for making numerous PRIVATEn prefixes within
> a network are likely to have conceptually similar demands, in so far
> as the management of number ranges is concerned.  Even if they aren't,
> though, it seems clear that router software developers have mastery of
> subtraction and addition, along with the bit-wise operators.
> --
> Jeff S Wheeler <jsw@inconcepts.biz>
> Sr Network Operator  /  Innovative Network Concepts
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>