RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area
0 sources
RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area
Summary
RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area is a Request for Comments[1].
Key Facts
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area authored Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area — author (P50): Jon Peterson[2].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area authored Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area — author (P50): Robert J. Sparks[3].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area authored Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area — author (P50): Cullen Frishman Jennings[4].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's instance of is recorded as Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area — instance of (P31): Request for Comments[5].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's publisher is recorded as Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area — publisher (P123): Internet Engineering Task Force[6].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's based on is recorded as Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area — based on (P144): RFC 3265: Session Initiation Protocol (SIP)-Specific Event Notification[7].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's based on is recorded as Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area — based on (P144): RFC 3969: The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)[8].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's DOI is recorded as 10.17487/RFC5727[9].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's language of work or name is recorded as Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area — language of work or name (P407): English[10].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's publication date is recorded as +2010-03-01T00:00:00Z[11].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's RfC ID is recorded as 5727[12].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's main subject is recorded as Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area — main subject (P921): Session Initiation Protocol[13].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's work available at URL is recorded as https://tools.ietf.org/html/rfc5727[14].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's work available at URL is recorded as https://tools.ietf.org/rfc/rfc5727.txt[15].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc5727.txt[16].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc5727.txt.pdf[17].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's number of pages is recorded as {'unit': '1', 'amount': '+14'}[18].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's replaces is recorded as Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area — replaces (P1365): RFC 3427: Change Process for the Session Initiation Protocol (SIP)[19].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's title is recorded as Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area[20].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's amended by is recorded as Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area — amended by (P2567): RFC 7957: DISPATCH-Style Working Groups and the SIP Change Process[21].
- RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's DBLP publication ID is recorded as journals/rfc/rfc5727[22].
Body
Designation and Status
RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area's instance of is recorded as Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area — instance of (P31): Request for Comments[5].