You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2017/02/26 06:15:44 UTC
[jira] [Commented] (LOG4J2-1376) RFC5424 Enterprise Number should
be an OID fragment.
[ https://issues.apache.org/jira/browse/LOG4J2-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884565#comment-15884565 ]
Ralph Goers commented on LOG4J2-1376:
-------------------------------------
Any update on this?
> RFC5424 Enterprise Number should be an OID fragment.
> ----------------------------------------------------
>
> Key: LOG4J2-1376
> URL: https://issues.apache.org/jira/browse/LOG4J2-1376
> Project: Log4j 2
> Issue Type: Bug
> Components: Core, Layouts
> Affects Versions: 2.5
> Reporter: Mark Niggemann
>
> Rfc5424Layout incorrectly implements the Enterprise Number as a simple integer value for StructuredDataId types that are not assigned by IANA.
> This is incorrect according to RFC5424. The implementation should allow for this to be an OID fragment representing the private enterprise subtree which is interpreted as the suffix to the IANA SMI Network Management Private Enterprise Code prefix 1.3.6.1.4.1. Refer to RFC5424, section 7.2.2.
> For example, GE Healthcare IT has IANA private enterprise number 22005 and there are several other systems we support that are hierarchically assigned subtree OID fragments. Ordinarily, these codes would have the following form: 1.3.6.1.4.1.22005.<subtree-oid>. RFC5424 allows for truncating the SMI prefix and leaving the private enterprise number subtree in the message. So they would appear as 22005.<subtree-oid> (e.g., 22005.42.1.21).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org