Re: [v6ops] [Idr] BGP Identifier

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
>
>