[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: some comments on draft-ietf-psamp-framework-09.txt
> >> !
> >> ! SHOULD WE MAKE IT EXPLICIT THAT OBERSVATION POINT,
> >> ! PROCESS AND EXPORTING PROCESS IDS SHOULD BE CONTAINED IN
> >> ! PACKET REPORT?
> >Since an export packet may contain multiple packet reports, the
> >process id can be included once per export packet.
> Did we say anywhere that exporting process IDs are included?
Currently, Section 6.4 says about the reporting process:
6.4 Report Interpretation
Information for use in Report Interpretation must include
(iv) identifiers for Observation Point, Measurement Process, and
I'm thinking now that responsibility for inserting identifiers should be
split as follows:
. Reporting Process inserts IDs for Observation Point and Measurement
. Exporting Process inserts IDs for Export Process.
Reasoning: we don't exclude the case that a report on a given packet is
sent by more than one exporting process. Example: send one copy to a
local on board processor, and one copy to a remote collector. I don't
see a need for the reporting process to include both exporting process
identifiers in this case; instead each exporting process can insert its
own ID. Also, one can imagine in some configurations that the reporting
process wouldn't have the information on exporting process ID available
(i.e. processes are run on different hosts).
Following suggestions from a number of folks, the IDs would now
explicitly be inserted per report or packet, i.e.:
. packet reports each contain ID for observation point and measurement
. export packets (which may contain multiple report packets from
multiple measurement processes) each contain an ID for the exporting
to unsubscribe send a message to email@example.com with
the word 'unsubscribe' in a single line as the message text body.