{"abstract": "   Message types defined by the BGP Monitoring Protocol (BMP) do\n   provision for data in TLV - Type, Length, Value - format, either in\n   the shape of a TLV message body, ie.  Route Mirroring and Stats\n   Reports, or optional TLVs at the end of a BMP message, ie.  Peer Up\n   and Peer Down.  However the space for Type value is unique and\n   governed by IANA.  To allow the usage of vendor-specific TLVs, a\n   mechanism to define per-vendor Type values is required.  In this\n   document we introduce an Enterprise Bit, or E-bit, for such purpose.\n", "ad": null, "expires": "2025-07-21T13:27:30Z", "external_url": "", "group": "/api/v1/group/group/1584/", "id": 109844, "intended_std_level": null, "keywords": "[]", "name": "draft-ietf-grow-bmp-tlv-ebit", "note": "", "notify": "", "pages": 7, "resource_uri": "/api/v1/doc/document/draft-ietf-grow-bmp-tlv-ebit/", "rev": "06", "rfc": null, "rfc_number": null, "shepherd": null, "states": ["/api/v1/doc/state/4/", "/api/v1/doc/state/150/", "/api/v1/doc/state/38/"], "std_level": null, "stream": "/api/v1/name/streamname/ietf/", "submissions": ["/api/v1/submit/submission/127446/", "/api/v1/submit/submission/130029/", "/api/v1/submit/submission/132576/", "/api/v1/submit/submission/135640/", "/api/v1/submit/submission/137888/", "/api/v1/submit/submission/141423/", "/api/v1/submit/submission/148565/"], "tags": [], "time": "2025-07-21T07:09:07Z", "title": "Support for Enterprise-specific TLVs in the BGP Monitoring Protocol", "type": "/api/v1/name/doctypename/draft/", "uploaded_filename": "", "words": null}