RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)
0 sources
RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)
Summary
RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP) is a Request for Comments[1].
Key Facts
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP) authored Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP) — author (P50): Eliot Lear[2].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s instance of is recorded as Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP) — instance of (P31): Request for Comments[3].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s publisher is recorded as Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP) — publisher (P123): Internet Engineering Task Force[4].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s DOI is recorded as 10.17487/RFC4744[5].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s language of work or name is recorded as Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP) — language of work or name (P407): English[6].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s publication date is recorded as +2006-12-01T00:00:00Z[7].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s RfC ID is recorded as 4744[8].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s main subject is recorded as Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP) — main subject (P921): NETCONF[9].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s main subject is recorded as Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP) — main subject (P921): BEEP[10].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s work available at URL is recorded as https://tools.ietf.org/html/rfc4744[11].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s work available at URL is recorded as https://tools.ietf.org/rfc/rfc4744.txt[12].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc4744.txt[13].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc4744.txt.pdf[14].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s number of pages is recorded as {'unit': '1', 'amount': '+10'}[15].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s title is recorded as Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)[16].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s author name string is recorded as K. Crozier[17].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s amended by is recorded as Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP) — amended by (P2567): RFC 8996: Deprecating TLS 1.0 and TLS 1.1[18].
- RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s DBLP publication ID is recorded as journals/rfc/rfc4744[19].
Body
Designation and Status
RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)'s instance of is recorded as Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP) — instance of (P31): Request for Comments[3].