Session Initiation Proposal Investigation (sipping)

RFC Errata System | 21 Sep 2011 19:27

[Editorial Errata Reported] RFC3398 (2977)


The following errata report has been submitted for RFC3398,
"Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3398&eid=2977

--------------------------------------
Type: Editorial
Reported by: Jeff Dyer <jeff.dyer <at> sasktel.com>

Section: 7.2.4.1

Original Text
-------------
(+) If the cause location is 'user' than the 6xx code could be given rather than the 4xx code (i.e., 403
becomes 603)

Corrected Text
--------------
(+) If the cause location is 'user' then the 6xx code could be given rather than the 4xx code (i.e., 403
becomes 603)

Notes
-----
Than is used for comparisons.  Then is used to denote something follows in sequence.

Instructions:
-------------

(Continue reading)

headers

Gonzalo Camarillo | 22 Sep 2011 13:16

Re: [Editorial Errata Reported] RFC3398 (2977)

Hi,

yes, s/than/then/ would resolve the issue. However, this erratum is not
likely to create interoperability problems. So, my take is that we
should classify it as "hold for document update".

Thanks,

Gonzalo

On 21/09/2011 8:27 PM, RFC Errata System wrote:
> 
> The following errata report has been submitted for RFC3398,
> "Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3398&eid=2977
> 
> --------------------------------------
> Type: Editorial
> Reported by: Jeff Dyer <jeff.dyer <at> sasktel.com>
> 
> Section: 7.2.4.1
> 
> Original Text
> -------------
> (+) If the cause location is 'user' than the 6xx code could be given rather than the 4xx code (i.e., 403
becomes 603)
>

(Continue reading)