IETF Logo Mail Archive

Re: [Forces-protocol] RE: GET/SET in one msg ?

Steven Blake <slblake@petri-meat.com> Fri, 22 October 2004 01:14 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20264 for <forces-protocol-web-archive@ietf.org>; Thu, 21 Oct 2004 21:14:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKoDS-0008SL-HT for forces-protocol-web-archive@ietf.org; Thu, 21 Oct 2004 21:27:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKlMQ-0004by-Ro; Thu, 21 Oct 2004 18:24:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKjrU-0003i1-0V for forces-protocol@megatron.ietf.org; Thu, 21 Oct 2004 16:48:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23332 for <forces-protocol@ietf.org>; Thu, 21 Oct 2004 16:48:37 -0400 (EDT)
Received: from server26.totalchoicehosting.com ([209.152.177.32]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKk49-0007xn-H4 for forces-protocol@ietf.org; Thu, 21 Oct 2004 17:01:46 -0400
Received: from [204.85.2.252] (helo=[192.168.168.85]) by server26.totalchoicehosting.com with esmtp (Exim 4.43) id 1CKjqh-0004jj-7p; Thu, 21 Oct 2004 16:47:51 -0400
Subject: Re: [Forces-protocol] RE: GET/SET in one msg ?
From: Steven Blake <slblake@petri-meat.com>
To: Robert Haas <rha@zurich.ibm.com>
In-Reply-To: <41781915.1030401@zurich.ibm.com>
References: <468F3FDA28AA87429AD807992E22D07E025791E9@orsmsx408> <04ab01c4b5c7$1332c430$845c21d2@Necom.hzic.edu.cn> <417573E8.7070502@zurich.ibm.com> <1098385216.2340.239.camel@localhost.localdomain> <41781915.1030401@zurich.ibm.com>
Content-Type: text/plain
Message-Id: <1098391662.2340.276.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2)
Date: Thu, 21 Oct 2004 16:47:42 -0400
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server26.totalchoicehosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - petri-meat.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
Cc: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>, ram.gopal@nokia.com, "Yang, Lily L" <lily.l.yang@intel.com>, Zsolt Haraszti <zsolt@nc.rr.com>, "Joel M. Halpern" <jhalpern@MEGISTO.com>, forces-protocol@ietf.org, hadi@znyx.com, Alan DeKok <alan.dekok@idt.com>, "Deleganes, Ellen M" <ellen.m.deleganes@intel.com>, "Wang, Weiming" <wmwang@mail.hzic.edu.cn>
X-BeenThere: forces-protocol@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: forces-protocol <forces-protocol.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/forces-protocol>, <mailto:forces-protocol-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/forces-protocol>
List-Post: <mailto:forces-protocol@ietf.org>
List-Help: <mailto:forces-protocol-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/forces-protocol>, <mailto:forces-protocol-request@ietf.org?subject=subscribe>
Sender: forces-protocol-bounces@ietf.org
Errors-To: forces-protocol-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit

On Thu, 2004-10-21 at 16:27, Steven Blake wrote:

> Note that I don't see much use in needing to map a single LFB instance
> ID (MIID) to multiple instance IDs on a single ID; i.e., I don't see the
                                                 ^FE

BTW, Wieming's address always bounces when I respond to these threads.

// Steve


_______________________________________________
Forces-protocol mailing list
Forces-protocol@ietf.org
https://www1.ietf.org/mailman/listinfo/forces-protocol

v2.23.0 | Report a Bug | By Email