[c-nsp] Cisco BGP Capability type code 131

[Bruce Pinsky]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Rathlev wrote:
> On Thu, 2007-11-29 at 09:50 +1030, Tom Storey wrote:
>> google "bgp capability 131"
>>
>> http://www.rfc-editor.org/rfc/rfc4760.txt
>>
> <snip>
> 
> I may have misunderstood something here, but as far as I can see,
> RFC4760 chapter 9 describes the SAFI namespace as per
> 
> http://www.iana.org/assignments/safi-namespace.
> 
> It does not descibe BGP capabilities, as defined in
> 
> http://www.iana.org/assignments/capability-codes.
> 
> RFC 4760 (and 2858 which it obsoletes) descibes sending BGP capability 1
> ("Multiprotocol Extensions for BGP-4") with a capability parameter that
> includes a SAFI, which could be 131 as per RFC 4760. (The RFC does not
> describe what SAFI 131 is though, just that it's part of a group which
> was "private use" and is now reserved/unallocated.)
> 
> If the OPs question really is: "What is BGP capability 131?" then the
> answer is "Vendor specific" as per IANA definitions.
> 
> Maybe OP can add some information to establish a context?
> 

BGP Multisession is capability 131

http://tools.ietf.org/html/draft-ietf-idr-bgp-multisession-03

- --
=========
bep

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHTiJfE1XcgMgrtyYRAt8XAJ9LJW3XME6z/cRbvimLJZ8bQn5++ACg0R/c
iNh+aCAUFQF8RGAq1IX1ZlY=
=DcNF
-----END PGP SIGNATURE-----