logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1376) RFC5424 Enterprise Number should be an OID fragment.
Date Mon, 02 May 2016 21:15:12 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267524#comment-15267524

Gary Gregory commented on LOG4J2-1376:

Should we use Java's own https://docs.oracle.com/javase/7/docs/api/org/ietf/jgss/Oid.html

> 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 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:<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

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message