Re: [Agentx] Empty context in rfc2742
Magnus Fromreide <magfr@lysator.liu.se> Mon, 31 August 2009 20:32 UTC
Return-Path: <magfr@lysator.liu.se>
X-Original-To: agentx@core3.amsl.com
Delivered-To: agentx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A6A428C2A2 for <agentx@core3.amsl.com>; Mon, 31 Aug 2009 13:32:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.046
X-Spam-Level:
X-Spam-Status: No, score=-1.046 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_15=0.6, J_CHICKENPOX_17=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SdjiCzX6U41U for <agentx@core3.amsl.com>; Mon, 31 Aug 2009 13:32:54 -0700 (PDT)
Received: from mail.lysator.liu.se (mail.lysator.liu.se [130.236.254.3]) by core3.amsl.com (Postfix) with ESMTP id 261053A6EE2 for <agentx@ietf.org>; Mon, 31 Aug 2009 13:32:53 -0700 (PDT)
Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id 9D083400C4; Mon, 31 Aug 2009 22:32:26 +0200 (CEST)
Received: by mail.lysator.liu.se (Postfix, from userid 1674) id 90B67400C7; Mon, 31 Aug 2009 22:32:26 +0200 (CEST)
Received: from [83.252.226.253] (c83-252-226-253.bredband.comhem.se [83.252.226.253]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.lysator.liu.se (Postfix) with ESMTP id AB236400C4; Mon, 31 Aug 2009 22:32:25 +0200 (CEST)
From: Magnus Fromreide <magfr@lysator.liu.se>
To: Mark Ellison <ellison@ieee.org>
In-Reply-To: <8a0268750908301523o390d9ff1kc951bfb24d49c9e1@mail.gmail.com>
References: <1251623843.6043.6.camel@sara.home> <8a0268750908301048i2b4a477dod97e582238098bbe@mail.gmail.com> <1251668476.3736.14.camel@sara.home> <8a0268750908301523o390d9ff1kc951bfb24d49c9e1@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Date: Mon, 31 Aug 2009 22:32:57 +0200
Message-Id: <1251750777.5149.52.camel@sara.home>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: agentx@ietf.org
Subject: Re: [Agentx] Empty context in rfc2742
X-BeenThere: agentx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SNMP Agent Extensibility <agentx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/agentx>, <mailto:agentx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/agentx>
List-Post: <mailto:agentx@ietf.org>
List-Help: <mailto:agentx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/agentx>, <mailto:agentx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Aug 2009 20:32:55 -0000
On Sun, 2009-08-30 at 18:23 -0400, Mark Ellison wrote: > Hi Magnus- Hello Mark. > On Sun, Aug 30, 2009 at 5:41 PM, Magnus Fromreide<magfr@lysator.liu.se> wrote: > > On Sun, 2009-08-30 at 13:48 -0400, Mark Ellison wrote: > >> On Sun, Aug 30, 2009 at 5:17 AM, Magnus Fromreide<magfr@lysator.liu.se> wrote: > >> > Hello. > >> > > >> > According to rfc2742 agentxRegContext (octet string) is > >> > "The context in which the session supports the objects in this > >> > region. A zero-length context indicates the default context. > >> > " > >> > > >> > Now I am would like to know how a zero-length context should be > >> > represented? > >> > > >> The default context is an OCTET STRING of zero-length. > > > > Not according to RFC 2741 6.1.1 ยง4. > > > > In agentxRegContext we are looking a AgentX registrations and in this > > domain it is explicitly stated that NON_DEFAULT_CONTEXT "" is distinct > > from DEFAULT_CONTEXT but I can see no provision for the MIB to represent > > that. > > Thanks for this reference- your original question was in regard to RFC > 2742. Well, they are somewhat related since 2742 has no purpose without 2741. > As the agentxRegContext object-type definition states, "A > zero-length context indicates the default context". I believe this is > consistent with my previous reply. I fear that we are speaking past each other and will do one last attempt to ask my question. > The 2741 section cited above applies to the AgentX header. > Effectively, for 2742 you won't have a zero-length context name for a > non default context. As I understand 2742 agentxRegistrationTable is a view into the set of registrations that the sessions have done with the master agent and thus the values of that table should match the values in the actual registrations as far as possible. > In the SNMP, the AgentX context is mapped from the SNMPv3 contextName > in the scoped PDU (most current is 3411 sxn 3.3.3). Since every > contextName within an SNMP entity MUST be unique there can not be both > the default context and a non default context with a zero-length > string. While this is true it is also true that the agent is free to map the AgentX-contexts to SNMP-contexts however it wish so I think this impose no limits on the values of AgentX-contexts. This question is only regarding the _values_ of the agentxRegContext column. As I said above it believe that agentxRegContext should represent the values of the AgentX-context for all AgentX-registrations that is made on the AgentX-side of the master agent. The problem is that the value set for AgentX-context contains one element more than the value set for OCTET STRING. I am asking how the AgentX-context value that don't fit into the mapping from AgentX-context to agentxRegContext should be handled. EXAMPLE: Assume that two AgentX registrations are made to a master agent that implements rfc 2741 and rfc 2742. 1: { r.flags = 0, <no r.context>, ... } 2: { r.flags = NON_DEFAULT_CONTEXT, r.context = "", ... } Now as I read 2742 the value of the agentxRegContext column for registration #1 is "" The question is what the value of the agentxRegContext column for registration #2 should be? /MF
- [Agentx] Empty context in rfc2742 Magnus Fromreide
- Re: [Agentx] Empty context in rfc2742 Mark Ellison
- Re: [Agentx] Empty context in rfc2742 Magnus Fromreide
- Re: [Agentx] Empty context in rfc2742 Mark Ellison
- Re: [Agentx] Empty context in rfc2742 Magnus Fromreide
- Re: [Agentx] Empty context in rfc2742 Mark Ellison
- Re: [Agentx] Empty context in rfc2742 Randy Presuhn
- Re: [Agentx] Empty context in rfc2742 Magnus Fromreide