Issue 1427:  Clean up description of QoS properties (notif_service-rtf)
Source:  (, )
Nature:  Revision
Severity: 
Summary: Summary: 5) In general we need to clean up the description of QoS properties to
    clearly distinguish which properties are valid in the optional header
    field of a structured event, and which can be set on proxies, admins,
    or channels. Certain properties only make sense on a per-message basis,
    and others make no sense on a per-message basis. Currently the spec is
    very unclear on this distinction, and we should fix this.
 

Resolution: 
Revised Text: 
Actions taken:
May 28, 1998: received issue
February 23, 1999: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <mjg@syl.nj.nec.com>
From: "Michael J. Greenberg" <mjg@syl.nj.nec.com>
Subject: Issues for discussion...
To: notif_service-rtf@omg.org
Date: Thu, 28 May 1998 17:19:29 -0400 (EDT)
Cc: juergen@omg.org, dsm@syl.nj.nec.com

Hello,

First off, I'd like to remind everyone that there is an official
meeting of the Notification Service Revision Taskforce scheduled
for Monday, 6/8 at 5PM in Orlando. Please attend if possible!

The main reason for this message is to initiate an official "Issues
List",
enumerating changes to the Notification Service spec that we should
discuss
during our meeting.

Here is my first cut at a list of known issues:


5) In general we need to clean up the description of QoS properties to
   clearly distinguish which properties are valid in the optional
header
   field of a structured event, and which can be set on proxies,
admins,
   or channels. Certain properties only make sense on a per-message
basis,
   and others make no sense on a per-message basis. Currently the spec
is
   very unclear on this distinction, and we should fix this.