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

Jon Mitchell <jrmitche@puck.nether.net> Tue, 11 December 2012 18:59 UTC

Return-Path: <jrmitche@puck.nether.net>
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 6106621E8030 for <idr@ietfa.amsl.com>; Tue, 11 Dec 2012 10:59:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level:
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
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 32kj-i+PfB3I for <idr@ietfa.amsl.com>; Tue, 11 Dec 2012 10:59:19 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id BCB8521E802E for <idr@ietf.org>; Tue, 11 Dec 2012 10:59:19 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by puck.nether.net (8.14.4/8.14.4) with ESMTP id qBBIxH4g001104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Dec 2012 13:59:18 -0500
Received: (from jrmitche@localhost) by puck.nether.net (8.14.4/8.14.4/Submit) id qBBIxH6O001101; Tue, 11 Dec 2012 13:59:17 -0500
Date: Tue, 11 Dec 2012 13:59:17 -0500
From: Jon Mitchell <jrmitche@puck.nether.net>
To: Russ White <russw@riw.us>
Message-ID: <20121211185917.GA21813@puck.nether.net>
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> <CA+b+ERnSVvewSpftXs3FhW12-S+sgnB1SwD4L+xqFW+hhbQayw@mail.gmail.com> <7120600D-71BD-4E61-8F06-25B7C2BAE6A8@riw.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <7120600D-71BD-4E61-8F06-25B7C2BAE6A8@riw.us>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Tue, 11 Dec 2012 13:59:18 -0500 (EST)
Cc: idr wg <idr@ietf.org>, Robert Raszuk <robert@raszuk.net>
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 18:59:20 -0000

Russ -

I agree with this view, however this was already my intention and I
believe how the draft reads today.  There is very little text overall
and none that purports to be a use case for the new range in the draft.
There is a brief introduction that mentions that BGP use in lot of
applications has expanded, some may have interpeted this to be a use
case but it sure doesn't try to provide any guidance on it nor in the
subsequent text.  I volunteered to remove the last sentence of the first
paragraph in case it was being misinterpeted in this fashion... but
unless people have some other *specific* wording changes besides that
(that stay away from getting into more specific use cases, for instance
about large DCs), I don't plan to make any further changes to the draft.

Jon

On Tue, Dec 11, 2012 at 01:26:03PM -0500, Russ White wrote:
> 
> +1
> 
> Lets steer away from the justifications in a draft, as they might well change over the next 5 years anyway. The justification seems well supported o list, so make the draft simple...
> 
> :-)
> 
> Russ
> 
> <><
> russw@riw.us
> riwhite@verisign.com
> 
> On Dec 11, 2012, at 11:54 AM, Robert Raszuk <robert@raszuk.net> wrote:
> 
> > 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
> > _______________________________________________
> > Idr mailing list
> > Idr@ietf.org
> > https://www.ietf.org/mailman/listinfo/idr
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr