RFC 5115, "Telephony Routing over IP (TRIP) Attribute for Resource Priority", January 2008Source of RFC: IETF - NON WORKING GROUP
Area Assignment: rai
Errata ID: 1358
Status: Held for Document Update
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-03-11
Held for Document Update by: Robert Sparks
Section 3, 2nd para says:
The requirements in [rfc3487] produced the corresponding document | [rfc4412] in the SIP working group, which defines a new header for | SIP called Resource-Priority. This new header, which is optional, is divided into two parts: a NameSpace and a Value. [...]
It should say:
The requirements in [rfc3487] produced the corresponding document | [rfc4412] in the SIP working group, which defines a new header field | for SIP called Resource-Priority. This new header field, which is | optional, has a field value divided into two parts: a NameSpace and a Value. [...]
a) Abuse of language / non-use of established precise terminology:
"header" --> "header field.
This issue recurs twice in Section 3.1 (first and last paragraph).
b) Any header field is divided into two parts, the header field name
and the header field value. Hence, the RFC text is misleading.
Apparently, it wants to indicate that the field value is further
subdivided into two parts.
The proposed correction tries to clarify this with minimal rewording.