rfc-5133

Terminal Endpoint Identifier (TEI) Query Request Number Change

M. Tuexen, K. Morneault

date2007-12 streamIETF arearai wgsigtran statusPROPOSED STANDARD pages4 canonicalhttps://www.rfc-editor.org/rfc/rfc5133 doi10.17487/RFC5133

The Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer (IUA) Protocol, described in RFC 4233, defines the message type of Terminal Endpoint Identifier (TEI) Query Request messages as 5. However, this number is already being used by the Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions (DUA) to the IUA Protocol described in RFC 4129. This document updates RFC 4233 such that the message type of TEI Query Request messages is 8. [STANDARDS-TRACK]

updates

rfc-4233 — Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer

Extracted elements (5)

design-rationale §1

The message type 5 originally assigned to TEI Query Request in RFC 4233 conflicts with the DLC Status message type 5 introduced by the DUA protocol (RFC 4129), making it impossible to differentiate the two messages. The type is therefore changed to 8.

realtime

interoperability-note §1

RFC 4233 and RFC 4129 assigned conflicting message type values (both using type 5) for TEI Query Request and DLC Status messages respectively. This document resolves the conflict by renumbering the TEI Query Request to type 8, updating RFC 4233.

realtime

normative-requirement §3 MUST

TEI Query Request messages MUST be encoded with a message type of 8 instead of 5 as previously described in RFC 4233.

realtime

registry §4

IANA has reserved message type 8 of Management Messages in the 'Message Types' section of the 'Signaling User Adaptation Layer Assignments' registry for TEI Query Request messages.

registry, realtime

security-consideration §5

This document does not introduce any security considerations beyond those already present in RFC 4233.

security, realtime