[c-nsp] BGP Max-Prefix - Notification Data Decode Options ?

[Darin Herteen]

I would've expected to see 1F4 or 500 of which I should've been under. I am anticipating needing to be around 550 before too long. 

Because we have multiple circuits with said upstream, I can't rule out they modified the wrong session, and will have to press them later today.

> From: mack.mcbride at viawest.com
> To: synack at live.com; nick at foobar.org; cisco-nsp at puck.nether.net
> Subject: RE: [c-nsp] BGP Max-Prefix - Notification Data Decode Options ?
> Date: Tue, 10 Mar 2015 21:08:42 +0000
> 
> What is the value you are expecting?
> The last four digits indicate 400 (190 is hex obviously).
> I mean, how many prefixes are you expecting to send to your provider?
> 
> Mack McBride | Network Architect | ViaWest, Inc.
> O: 720.891.2502 | mack.mcbride at viawest.com | www.viawest.com | LinkedIn | Twitter | YouTube
> 
> 
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Darin Herteen
> Sent: Tuesday, March 10, 2015 1:38 PM
> To: Nick Hilliard; cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] BGP Max-Prefix - Notification Data Decode Options ?
> 
> 
> 
> > Date: Tue, 10 Mar 2015 17:24:36 +0000
> > From: nick at foobar.org
> > To: synack at live.com; cisco-nsp at puck.nether.net
> > Subject: Re: [c-nsp] BGP Max-Prefix - Notification Data Decode Options ?
> >
> > On 10/03/2015 17:13, Darin Herteen wrote:
> > > which the provider states should fall within their allowed
> > > max-prefix range for our session [...]
> >
> > then, your provider is lying.
> >
> > Nick
> 
> Agreed, especially after reading RFC 4486. Assuming I'm understanding "Subcode Usage" correctly...
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
> This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply and immediately delete all copies of the message.