RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent
0 sources
RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent
Summary
RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent is a Request for Comments[1].
Key Facts
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent authored V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent — author (P50): Bert Wijnen[2].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's instance of is recorded as V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent — instance of (P31): Request for Comments[3].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's publisher is recorded as V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent — publisher (P123): Internet Engineering Task Force[4].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's DOI is recorded as 10.17487/RFC2089[5].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's language of work or name is recorded as V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent — language of work or name (P407): English[6].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's publication date is recorded as +1997-01-01T00:00:00Z[7].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's RfC ID is recorded as 2089[8].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's work available at URL is recorded as https://tools.ietf.org/html/rfc2089[9].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's work available at URL is recorded as https://tools.ietf.org/rfc/rfc2089.txt[10].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc2089.txt[11].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc2089.txt.pdf[12].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's number of pages is recorded as {'unit': '1', 'amount': '+12'}[13].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's replaced by is recorded as V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent — replaced by (P1366): RFC 2576: Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework[14].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's title is recorded as V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent[15].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's author name string is recorded as D. Levi[16].
- RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's DBLP publication ID is recorded as journals/rfc/rfc2089[17].
Body
Designation and Status
RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent's instance of is recorded as V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent — instance of (P31): Request for Comments[3].