Re: [Rfid] Control Plane Architectural Elements
Scott Barvick <sbarvick@revasystems.com> Fri, 22 July 2005 20:32 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dw4CN-0003gX-Ul; Fri, 22 Jul 2005 16:32:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dw4CM-0003Z2-IU for rfid@megatron.ietf.org; Fri, 22 Jul 2005 16:32:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24495 for <rfid@ietf.org>; Fri, 22 Jul 2005 16:32:43 -0400 (EDT)
Received: from mse3fe1.mse3.exchange.ms ([69.25.50.165]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dw4ge-0007D8-9Z for rfid@ietf.org; Fri, 22 Jul 2005 17:04:05 -0400
Received: from [192.168.1.45] ([157.130.221.86]) by mse3fe1.mse3.exchange.ms with Microsoft SMTPSVC(6.0.3790.211); Fri, 22 Jul 2005 16:32:17 -0400
Subject: Re: [Rfid] Control Plane Architectural Elements
From: Scott Barvick <sbarvick@revasystems.com>
To: Margaret Wasserman <margaret@thingmagic.com>
In-Reply-To: <p062007d3bf06f09306d8@[192.168.1.105]>
References: <p062007d3bf06f09306d8@[192.168.1.105]>
Content-Type: text/plain
Message-Id: <1122064335.27520.124.camel@saco.revasystems.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2)
Date: Fri, 22 Jul 2005 16:32:15 -0400
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Jul 2005 20:32:18.0225 (UTC) FILETIME=[7431CA10:01C58EFC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Content-Transfer-Encoding: 7bit
Cc: rfid@ietf.org
X-BeenThere: rfid@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Control and Access of Infrastructure for RFID Operations Discussion List <rfid.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rfid>, <mailto:rfid-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rfid>
List-Post: <mailto:rfid@lists.ietf.org>
List-Help: <mailto:rfid-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rfid>, <mailto:rfid-request@lists.ietf.org?subject=subscribe>
Sender: rfid-bounces@lists.ietf.org
Errors-To: rfid-bounces@lists.ietf.org
Margaret, Before we start down this path, I think we need to step back and note that we have been working with Bert and the folks at EPCGlobal to make sure that outputs from this group are compatible with the interacting layers of the EPCGlobal Architecture Framework Version 1.0 which can be found at: http://www.epcglobalinc.org/standards_technology/specifications.html The original charter proposal from the SLRRP BoF is quite consistent with the definition of the Reader Protocol (Interface) in Section 9.1.5 of the Architecture Framework. In fact, you'll find concepts from the original SLRRP draft used directly in specifying this interface, and SLRRP appropriately referenced in the References section. I am concerned that starting to work on a general reader architecture would lead us into conflict with the architecture work that is done and published by EPCGlobal. I believe that many of your concerns (autonomous operation, XML interface) are satisfied by the Filtering and Collection (Interface), also known as Application Level Events or ALE, in the EPCGlobal Architecture, and we have never wanted to duplicate this effort with this proposed working group. As you know, ALE is an interface that higher end readers will choose to run, but EPCGlobal also recognizes that there is a need for an interface to readers that is at a lower level in the architecture. Therefore, I think we need to stay more true to the CAIRO proposed charter until the group and/or Bert/IESG decides to change it to take it in a different direction. We have made a lot of progress with the spec and resulting implementations on the reader, RNC, and tools ends of things based on the current charter proposal, and I strongly recommend we stay focused. Thanks, Scott On Fri, 2005-07-22 at 14:55, Margaret Wasserman wrote: > Hi All, > > I made this diagram of what I think the architectural elements should > be in the Reader control plane: > > +----------+ +----------+ > | Single | | Multi- | > | Reader | | Reader | > | App | | App | > +----------+ +----------+ > +- - - - - - - - -|- - - - - - - |- - - - -+ > | Basic | +- - - |- - - - -|- - - - - - + > | Reader | | +----V-----+ | Smart | > | Controller | | | Multi- | | Reader | > | | | | Reader | | Controller | > | | | |Controller| | | > | | | +----------+ | | > | | +- - - |- - - - -|- - - - - - + > +- - -|- - - - - - - - -|- - - - - - - |- - - -+ | > | | +----V--------------V----+ | | > | | | Single | | | > | | | Reader | | | > | | | Controller | | | > | | +------------------------+ | | > | +- - - - - - - - - - - - -|- - - - - - - |-+ > | +- - - - - - - |- - - - - - - |- - - - - - - + > | | +------------V-----------+ | | > | | | Low-Level | | | > | | | RFID | | | > | | | Funcitons | | Basic | > |Smart | +------------------------+ | Reader | > |Reader +- - - - - - - - - - - - - - -|- - - - - - - + > +- - - - - - - - - - - - - - - - - - - - - - - + > > > As you can see, I think that we should separate the control plane > into separate multi-reader and single reader control elements, to > allow flexibility regarding the "intelligence" level of readers and > the corresponding interface for controllers. > > If I get a chance, I will make a similar diagram for the data plane, > where I also beleive that there shold be more than two architectural > elements. > > Thoughts? > > Margaret > > _______________________________________________ > Rfid mailing list > Rfid@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/rfid _______________________________________________ Rfid mailing list Rfid@lists.ietf.org https://www1.ietf.org/mailman/listinfo/rfid
- [Rfid] Control Plane Architectural Elements Margaret Wasserman
- Re: [Rfid] Control Plane Architectural Elements Scott Barvick
- Re: [Rfid] Control Plane Architectural Elements Margaret Wasserman
- Re: [Rfid] Control Plane Architectural Elements Margaret Wasserman
- RE: [Rfid] Control Plane Architectural Elements P. Krishna
- RE: [Rfid] Control Plane Architectural Elements Margaret Wasserman
- Re: [Rfid] Control Plane Architectural Elements P. Krishna