Re: [OPS-AREA] assumption about number of octets encoding PENs

David Harrington <ietfdbh@comcast.net> Thu, 24 May 2012 07:30 UTC

Return-Path: <ietfdbh@comcast.net>
X-Original-To: ops-area@ietfa.amsl.com
Delivered-To: ops-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0721521F84B2 for <ops-area@ietfa.amsl.com>; Thu, 24 May 2012 00:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.24
X-Spam-Level:
X-Spam-Status: No, score=-101.24 tagged_above=-999 required=5 tests=[AWL=1.359, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6md2Waz4c8LM for <ops-area@ietfa.amsl.com>; Thu, 24 May 2012 00:30:49 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by ietfa.amsl.com (Postfix) with ESMTP id E996721F84A7 for <ops-area@ietf.org>; Thu, 24 May 2012 00:30:48 -0700 (PDT)
Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta01.westchester.pa.mail.comcast.net with comcast id DjWo1j0030EZKEL51jWo08; Thu, 24 May 2012 07:30:48 +0000
Received: from [192.168.1.34] ([71.233.85.150]) by omta01.westchester.pa.mail.comcast.net with comcast id DjWl1j0013Ecudz3MjWmAi; Thu, 24 May 2012 07:30:48 +0000
User-Agent: Microsoft-MacOutlook/14.2.2.120421
Date: Thu, 24 May 2012 03:30:44 -0400
From: David Harrington <ietfdbh@comcast.net>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Randy Presuhn <randy_presuhn@mindspring.com>
Message-ID: <CBE358A7.22480%ietfdbh@comcast.net>
Thread-Topic: [OPS-AREA] assumption about number of octets encoding PENs
In-Reply-To: <20120524062516.GA5397@elstar.local>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: Alan DeKok <aland@deployingradius.com>, ops-area@ietf.org, pearl.liang@icann.org
Subject: Re: [OPS-AREA] assumption about number of octets encoding PENs
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2012 07:30:50 -0000

On 5/24/12 2:25 AM, "Juergen Schoenwaelder"
<j.schoenwaelder@jacobs-university.de> wrote:

>
>And because of this, sub-identifiers were restricted to 32 bits in
>SMIv2. In other words, assuming PENs can be larger than 32 bits will
>surely not work with SNMP.
>/js

Notes:
1) sysObjectID includes SMI PENs, and many SNMP network monitoring systems
use sysObjectID to identify devices, as suggested by RFC1065.
Auto-discovery is especially reliant on these values.
2) syslog (RFC5424) uses the SMI PEN registry.
3) ipfix (RFC5101) uses the SMI PEN registry.
4) sipclf IDs use the SMI PEN registry.
5) middisc ID does not use the SMI PEN registry because it is too large
for its intended use, and requests a smaller (8-bit) vendor code registry.

I am not sure how these uses would be impacted by a PEN larger than 32
bits.


--
David Harrington
Internet Engineering Task Force (IETF)
Ietfdbh@comcast.net
+1-603-828-1401





>