Re: [Sigtran] [Editorial Errata Reported] RFC4666 (4475)

"Brian F. G. Bidulock" <bidulock@openss7.org> Tue, 15 September 2015 13:42 UTC

Return-Path: <bidulock@openss7.org>
X-Original-To: sigtran@ietfa.amsl.com
Delivered-To: sigtran@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C7EC1A8746 for <sigtran@ietfa.amsl.com>; Tue, 15 Sep 2015 06:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q8KiaGBeyTYH for <sigtran@ietfa.amsl.com>; Tue, 15 Sep 2015 06:42:21 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 120281A7D82 for <sigtran@ietf.org>; Tue, 15 Sep 2015 06:42:20 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id t8FDgGwS000372 for <sigtran@ietf.org>; Tue, 15 Sep 2015 07:42:16 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id t8FDgGhS010734 for <sigtran@ietf.org>; Tue, 15 Sep 2015 07:42:16 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id t8FDgGh0010733 for sigtran@ietf.org; Tue, 15 Sep 2015 07:42:16 -0600
Date: Tue, 15 Sep 2015 07:42:16 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: sigtran@ietf.org
Message-ID: <20150915134216.GA10477@openss7.org>
Mail-Followup-To: sigtran@ietf.org
References: <20150914234827.471FD187E4F@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20150914234827.471FD187E4F@rfc-editor.org>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sigtran/L_142RPElx3PVYqqeX1iJUEbbo8>
Subject: Re: [Sigtran] [Editorial Errata Reported] RFC4666 (4475)
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sigtran/>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2015 13:42:24 -0000

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 <v@pharos-avantgard.com>
> 
> 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
> Sigtran@ietf.org
> https://www.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/