Re: [v6ops] [Idr] BGP Identifier

George Michaelson <ggm@algebras.org> Tue, 18 February 2014 04:12 UTC

Return-Path: <ggm@algebras.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 787351A0331 for <v6ops@ietfa.amsl.com>; Mon, 17 Feb 2014 20:12:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 w2_GDYSnsrB2 for <v6ops@ietfa.amsl.com>; Mon, 17 Feb 2014 20:12:19 -0800 (PST)
Received: from mail-pb0-f42.google.com (mail-pb0-f42.google.com [209.85.160.42]) by ietfa.amsl.com (Postfix) with ESMTP id E0BBB1A030F for <v6ops@ietf.org>; Mon, 17 Feb 2014 20:12:18 -0800 (PST)
Received: by mail-pb0-f42.google.com with SMTP id jt11so16234172pbb.29 for <v6ops@ietf.org>; Mon, 17 Feb 2014 20:12:16 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=yqgmQL1h/TgQqpDFEudTHTmxRGOJk109/EUAFzkrvYk=; b=RmLhyJ2RWpvsuA75T7BflEiqn3ZZmMGhKdN+kgtSDlmcJnrxIZor+Pz3E20lUQ65hf n9v48N2tp4Nb2Jtmz9zhdq3hjwBbB9HAHheq2I5e5xiaEBZ5T1TFfkfF6bID1xzFR3+6 BYOpuNgvlNUPqWc1v0lSrJBFJ7BeySmQu1YL7ENiVWrJ0SnWIRdd5kes+II8BldxLgFT IkL/F7Cw1ByuLAK9e+cDIQdUSMJuiH/fw3usVFP+v4Y5+28rRHkdlqpIYUSdBx/nlTVp zYkRzRrj7ol9tc8L+3GdUfRSjiXcOkTedTYM7527SIfh5L0vw/o0hAF4QT6/eQLwZYaA yfCg==
X-Gm-Message-State: ALoCoQl6ZK0PYH9Wv7VNiG4A546GXhjwNXU0FzjEtrRFbkalZZJAfqXUEdjTqN8B0sEcDOwAy1NA
MIME-Version: 1.0
X-Received: by 10.66.176.143 with SMTP id ci15mr30390904pac.35.1392696736231; Mon, 17 Feb 2014 20:12:16 -0800 (PST)
Received: by 10.70.88.203 with HTTP; Mon, 17 Feb 2014 20:12:16 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:7c40:c788:ae6f:c53c]
In-Reply-To: <5302D994.1030801@bogus.com>
References: <12AA6714-4BBE-4ACE-8191-AA107D04FBF4@cisco.com> <m2wqgyjifd.wl%randy@psg.com> <006801cf2b34$22837cd0$678a7670$@chinamobile.com> <m2a9dqfr6k.wl%randy@psg.com> <009e01cf2b8b$26a43d20$73ecb760$@chinamobile.com> <CA+b+ERnD8yeeT-KzNZzJU4ZJYqMSW9YjD5JYdwhDR=dPHfuSkw@mail.gmail.com> <002401cf2bc8$8d1a7a50$a74f6ef0$@chinamobile.com> <m21tz22fyz.wl%randy@psg.com> <009801cf2bea$cd5eafb0$681c0f10$@chinamobile.com> <m2wqgtu72t.wl%randy@psg.com> <CAL9jLaZg4_4bhyaR7vUvmqZ9hiQkFy=mQFPCq-zwDJ=RSiwWGg@mail.gmail.com> <2014021810450694712020@chinamobile.com> <5302D994.1030801@bogus.com>
Date: Tue, 18 Feb 2014 14:12:16 +1000
Message-ID: <CAKr6gn3YUVus7gPoWYa896mDfXNTe7-9kZbPgDC7z7r4tzV-Jw@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
To: joel jaeggli <joelja@bogus.com>
Content-Type: multipart/alternative; boundary=047d7bd751603e482e04f2a67a89
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/7IuqM7vnSeEM99TcHe374fpx1iM
Cc: idr wg <idr@ietf.org>, V6 Ops List <v6ops@ietf.org>, Christopher Morrow <morrowc.lists@gmail.com>
Subject: Re: [v6ops] [Idr] BGP Identifier
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 18 Feb 2014 04:12:21 -0000

240/4 had drafts against it. NEVER is alas, not a normative word in what
Joel said.

Juniper already includes a flag to use 240/4 in cloud, at the request of a
cloud services company.


On Tue, Feb 18, 2014 at 1:55 PM, joel jaeggli <joelja@bogus.com> wrote:

> On 2/17/14, 6:45 PM, lizhenqiang@chinamobile.com wrote:
> >
> >
> >
> >
> >
> >
> > Thank you very much, Mr. Morrow. Yes, it is a good start. I will
> > contact Vijay for detail. However, I do not see the function that we
> > want from the slides. In fact, we also use some tools to assist our
> > network plan. However, the tools can not satisfy such complex
> > requirement. In a hierarchical operation network, the tools to
> > implement the logic we want is not a easy job. Zhenqiang Li
>
> We allocate ipv4 addresses today presumably, which implies the existence
> of business logic in basically all isps that accounts for the hierarchic
> allocation of 32 bit numbers.
>
> A brief cruise over to
>
> http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml
>
> Reveals a pool of  at least 28 bits (a /4 in ipv4 land) worth of 32bit
> numbers that will never overlap with ipv4 unicast address assignments
> that you traditionally use for router-ids. embedding those in family iso
> addresses if you like seems harmless and you'll never accidentally
> configure one as a unicast address on an interface. it'll be a little
> while before I need 268 million bgp speaking routers in the same AS.
>
>
> >
> > From: Christopher MorrowDate: 2014-02-17 23:59To: Randy BushCC: idr
> > wg; V6 Ops List; Robert RaszukSubject: Re: [Idr] [v6ops] BGP
> > Identifierhttp://
> www.nanog.org/meetings/nanog44/presentations/Monday/Gill_programatic_N44.pdf
> >
> >  Mike's presentation (given by vijay) is a decent start...
> >
> > On Mon, Feb 17, 2014 at 9:50 AM, Randy Bush <randy@psg.com> wrote:
> >>> Would you please give me an example about how modern large ISPs
> >>> manage their networks?
> >>
> >> programmatic generation of configurations from databases.
> >>
> >> 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
> >
> >
> >
> >
> > _______________________________________________ v6ops mailing list
> > v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
> >
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
>