Re: [Editorial Errata Reported] RFC4666 (4475)

"Brian F. G. Bidulock" <[email protected]> Tue, 15 Sep 2015 07:42:16 -0600
Newsgroups gmane.ietf.sigtran
Organization http://www.openss7.org/
Message-ID <[email protected]>
This is a good correction.  We certainly meant 32 bits.

--brian

RFC Errata System wrote:                     (Mon, 14 Sep 2015 16:48:27)
> The following errata report has been submitted for RFC4666,
> "Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=4666&eid=4475
> 
> --------------------------------------
> Type: Editorial
> Reported by: Valentin Micic <[email protected]>
> 
> Section: 3.6.1, Pg 53
> 
> Original Text
> -------------
> The optional SI [7,8] field contains one or more Service
>       Indicators from the values described in the MTP3-User Identity
>       field of the DUPU message.  The absence of the SI parameter in the
>       Routing Key indicates the use of any SI value, excluding of course
>       MTP management.  Where an SI parameter does not contain a multiple
>       of four SIs, the parameter is padded out to 32-byte alignment.
> 
> Corrected Text
> --------------
> The optional SI [7,8] field contains one or more Service
>       Indicators from the values described in the MTP3-User Identity
>       field of the DUPU message.  The absence of the SI parameter in the
>       Routing Key indicates the use of any SI value, excluding of course
>       MTP management.  Where an SI parameter does not contain a multiple
>       of four SIs, the parameter is padded out to 32-bit alignment.
> 
> Notes
> -----
> It seems obvious that diagram is referring to 32-bit and not 32-byte (as in 32-octets) alignment.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC4666 (draft-ietf-sigtran-rfc3332bis-06)
> --------------------------------------
> Title               : Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)
> Publication Date    : September 2006
> Author(s)           : K. Morneault, Ed., J. Pastor-Balbas, Ed.
> Category            : PROPOSED STANDARD
> Source              : Signaling Transport
> Area                : Real-time Applications and Infrastructure
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> Sigtran mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/