From psamp-bounces@ietf.org  Thu Sep 11 02:15:02 2008
Return-Path: <psamp-bounces@ietf.org>
X-Original-To: psamp-text-archive@optimus.ietf.org
Delivered-To: ietfarch-psamp-text-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 275DC3A6904;
	Thu, 11 Sep 2008 02:15:02 -0700 (PDT)
X-Original-To: psamp@ietf.org
Delivered-To: psamp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 6E7663A6904; Thu, 11 Sep 2008 02:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080911091501.6E7663A6904@core3.amsl.com>
Date: Thu, 11 Sep 2008 02:15:01 -0700 (PDT)
Cc: psamp@ietf.org
Subject: [PSAMP] I-D Action:draft-ietf-psamp-info-10.txt
X-BeenThere: psamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This mailing list is used for discussion within the IETF packet
	sampling \(PSAMP\) WG" <psamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/psamp>,
	<mailto:psamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/psamp>
List-Post: <mailto:psamp@ietf.org>
List-Help: <mailto:psamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/psamp>,
	<mailto:psamp-request@ietf.org?subject=subscribe>
Sender: psamp-bounces@ietf.org
Errors-To: psamp-bounces@ietf.org


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Packet Sampling Working Group of the IETF.


	Title           : Information Model for Packet Sampling Exports
	Author(s)       : T. Dietz, et al.
	Filename        : draft-ietf-psamp-info-10.txt
	Pages           : 53
	Date            : 2008-09-11

This memo defines an information model for the Packet Sampling
(PSAMP) protocol.  It is used by the PSAMP protocol for encoding
sampled packet data and information related to the Sampling process.
As the PSAMP protocol is based on the IPFIX protocol, this
information model is an extension to the IPFIX information
model.Conventions used in this document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-psamp-info-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-psamp-info-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-09-11020238.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
PSAMP mailing list
PSAMP@ietf.org
https://www.ietf.org/mailman/listinfo/psamp

--NextPart--


From psamp-bounces@ietf.org  Mon Sep 15 08:56:55 2008
Return-Path: <psamp-bounces@ietf.org>
X-Original-To: psamp-text-archive@optimus.ietf.org
Delivered-To: ietfarch-psamp-text-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F06A3A6AFD;
	Mon, 15 Sep 2008 08:56:55 -0700 (PDT)
X-Original-To: psamp@ietf.org
Delivered-To: psamp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id AE89D28C130; Mon, 15 Sep 2008 07:51:03 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20080915145103.AE89D28C130@core3.amsl.com>
Date: Mon, 15 Sep 2008 07:51:03 -0700 (PDT)
X-Mailman-Approved-At: Mon, 15 Sep 2008 08:56:53 -0700
Cc: psamp@ietf.org
Subject: [PSAMP] Last Call: draft-ietf-psamp-info (Information Model for
 Packet Sampling Exports) to Proposed Standard
X-BeenThere: psamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "This mailing list is used for discussion within the IETF packet
	sampling \(PSAMP\) WG" <psamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/psamp>,
	<mailto:psamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/psamp>
List-Post: <mailto:psamp@ietf.org>
List-Help: <mailto:psamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/psamp>,
	<mailto:psamp-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: psamp-bounces@ietf.org
Errors-To: psamp-bounces@ietf.org

The IESG has received a request from the Packet Sampling WG (psamp) to 
consider the following document:

- 'Information Model for Packet Sampling Exports '
   <draft-ietf-psamp-info-10.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2008-09-29. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-psamp-info-10.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=11074&rfc_flag=0

_______________________________________________
PSAMP mailing list
PSAMP@ietf.org
https://www.ietf.org/mailman/listinfo/psamp


From psamp-bounces@ietf.org  Thu Sep 18 07:14:44 2008
Return-Path: <psamp-bounces@ietf.org>
X-Original-To: psamp-text-archive@optimus.ietf.org
Delivered-To: ietfarch-psamp-text-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 940DD3A696D;
	Thu, 18 Sep 2008 07:14:44 -0700 (PDT)
X-Original-To: psamp@core3.amsl.com
Delivered-To: psamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DFC4C3A696D
	for <psamp@core3.amsl.com>; Thu, 18 Sep 2008 07:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 GQ8uV+6xfb55 for <psamp@core3.amsl.com>;
	Thu, 18 Sep 2008 07:14:37 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id C9CA63A6895
	for <psamp@ietf.org>; Thu, 18 Sep 2008 07:14:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,422,1217808000"; d="scan'208";a="20172650"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 18 Sep 2008 14:14:29 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m8IEETMX012467; 
	Thu, 18 Sep 2008 16:14:29 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m8IEESsS012090;
	Thu, 18 Sep 2008 14:14:28 GMT
Received: from [10.61.103.50] (dhcp-10-61-103-50.cisco.com [10.61.103.50])
	by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id m8IEEN127836;
	Thu, 18 Sep 2008 15:14:23 +0100 (BST)
Message-ID: <48D26242.6050404@cisco.com>
Date: Thu, 18 Sep 2008 15:14:26 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11
MIME-Version: 1.0
To: Thomas Dietz <Thomas.Dietz@nw.neclab.eu>
References: <804B13F8F3D94A4AB18B9B01ACB68FA101F5A5F9@EXCHSRV.fokus.fraunhofer.de>
	<489AB8F2.2050800@cisco.com>
	<547F018265F92642B577B986577D671C31737D@VENUS.office>
In-Reply-To: <547F018265F92642B577B986577D671C31737D@VENUS.office>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3348; t=1221747269;
	x=1222611269; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[PSAMP]=20PSAMP-INFO=20IE=20realtiveErr
	or=3A=20Open=20Points |Sender:=20;
	bh=3RTsw8Hqge0GKa10I9pBUu+GSPJws2GHKVeksbUhJCs=;
	b=qxRj0vzJC4pVX/pWArWpLxzfaQQfyEilBRbDvmJjnTm0Qx9nAUq13E8EXC
	cFOcKtHmcqnMq+fXRq2K5+9OU8pDp7jhAwWAq3E0AMQevDsQlhJRkKWFsJTj
	oGicby28Rp;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: psamp <psamp@ietf.org>, Juergen Quittek <Quittek@nw.neclab.eu>,
	psamp-chairs@tools.ietf.org, "Zseby,
	Tanja" <Tanja.Zseby@fokus.fraunhofer.de>
Subject: Re: [PSAMP] PSAMP-INFO IE realtiveError: Open Points
X-BeenThere: psamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This mailing list is used for discussion within the IETF packet
	sampling \(PSAMP\) WG" <psamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/psamp>,
	<mailto:psamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/psamp>
List-Post: <mailto:psamp@ietf.org>
List-Help: <mailto:psamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/psamp>,
	<mailto:psamp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: psamp-bounces@ietf.org
Errors-To: psamp-bounces@ietf.org

Thomas, all,

> as you may have noticed I just posted a new version of the draft. The
> only open points I see are your concerns expressed in the attached
> mail...
> 
> If you'd like to have those issues included in the draft then please
> suggest text for it.


Thanks. See inline:


>>>> absoluteError
>>>> 
>>>> This Information Element specifies the maximum possible
>>>> measurement error of the reported value for a given Information
>>>> Element. The
>> 
>> We should indicate how to connect the *Error values to specific
>> fields, eg by using an option with the specific field as scope.
>> Else, someone may put the *Error elements adjacent to the relative
>> fields in the data record - which could work, but is open to
>> misinterpretation.

"absoluteError should be used in an option template scoped to the
observation to which it refers.  See section 3.4.2.1 of RFC 5102."



>>>> absoluteError has the same unit as the information element it
>>>> is associated to. The real value of the metric can differ by absoluteError
>> 
>> "with" ------^^

ie, "has the same unit as the information element it is associated with".


>>>> (positive or negative) from the measured value. This
>>>> information element
>>>> provides only the error for measured values. If an information element
>>>> contains an estimated values (from sampling) the confidence boundaries
>>>> and confidence level have to be provided instead.
>> 
>> I would name the IEs: "the confidence boundaries and confidence
>> level have to be provided instead (with the upperCILimit,
>> lowerCILimit and confidenceLevel).

Use the text provided above ^^^^


>>>> relativeError
>>>> 
>>>> This Information Element specifies the maximum possible
>>>> measurement error of the reported value for a given Information
>>>> Element as percentage of the measured value. The real value of
>>>> the metric can differ by relativeError percent (positive or
>>>> negative) from the measured
>>>> value. This information element provides only the error for
>>>> measured values. If an information element contains an
>>>> estimated values (from sampling) the confidence boundaries and
>>>> confidence level have to be provided instead.
>> 
>> Again, as above, I would specifically name the IEs for this.

Use the same text as above.



>> We should specify that upperCILimit, lowerCILimit and
>> confidenceLevel are all required, and what to do if too few of them
>> are provided.

In these sections:

   8.6.5. upperCILimit
   8.6.6. lowerCILimit
   8.6.7. confidenceLevel

Add

   Note that the upperCILimit, lowerCILimit and confidenceLevel are all
   required to specify confidence, and should be disregarded unless all
   three are specified.



>>>> The accuracy for an estimated information element (from
>>>> sampling) SHOULD
>>>> be reported with confidence limits and confidence
>>>> level.[PSAMP-INFO]
>> 
>> Agreed. I'd also like to add something indicating how this can be
>> done, eg by using an option with the correct scope.

"upperCILimit, lowerCILimit and confidenceLevel should all be used in an
option template scoped to the observation to which they refer.   See
section 3.4.2.1 of RFC 5102."



Cheers.
-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
PSAMP mailing list
PSAMP@ietf.org
https://www.ietf.org/mailman/listinfo/psamp


From psamp-bounces@ietf.org  Thu Sep 18 07:14:44 2008
Return-Path: <psamp-bounces@ietf.org>
X-Original-To: psamp-text-archive@optimus.ietf.org
Delivered-To: ietfarch-psamp-text-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B9C963A6D6F;
	Thu, 18 Sep 2008 07:14:44 -0700 (PDT)
X-Original-To: psamp@core3.amsl.com
Delivered-To: psamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F1EFB3A6895
	for <psamp@core3.amsl.com>; Thu, 18 Sep 2008 07:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 HuhBpL69Mhxj for <psamp@core3.amsl.com>;
	Thu, 18 Sep 2008 07:14:36 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 36CAA3A68E8
	for <psamp@ietf.org>; Thu, 18 Sep 2008 07:14:35 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,422,1217808000"; d="scan'208";a="20172635"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 18 Sep 2008 14:14:23 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m8IEENoI012439; 
	Thu, 18 Sep 2008 16:14:23 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m8IEEMHs012058;
	Thu, 18 Sep 2008 14:14:22 GMT
Received: from [10.61.103.50] (dhcp-10-61-103-50.cisco.com [10.61.103.50])
	by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id m8IEEH127812;
	Thu, 18 Sep 2008 15:14:17 +0100 (BST)
Message-ID: <48D2623C.3070102@cisco.com>
Date: Thu, 18 Sep 2008 15:14:20 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11
MIME-Version: 1.0
To: Thomas.Dietz@nw.neclab.eu, psamp <psamp@ietf.org>
References: <20080911090238.B413B3A67F2@core3.amsl.com>
In-Reply-To: <20080911090238.B413B3A67F2@core3.amsl.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5426; t=1221747263;
	x=1222611263; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20New=20Version=20Notification=20for=20dr
	aft-ietf-psamp-info-10 |Sender:=20;
	bh=17XjZpT4gO2xjc6hPqeZ3CrYg0+uOrdOT8ZDnYBtcZM=;
	b=ClzbYgcGJvEsL8z4RX/wI+KFD+r1FBAWFUPk/aHCisMe58as/J57bDgMbQ
	2BsA17LVfVUo90yaCfKVPDRTmVCl7MrP6BRXWAsWS/m4wfGBPESzDlPJKD5D
	fiuOKLKUAw;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: psamp-chairs@tools.ietf.org
Subject: Re: [PSAMP] New Version Notification for draft-ietf-psamp-info-10
X-BeenThere: psamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This mailing list is used for discussion within the IETF packet
	sampling \(PSAMP\) WG" <psamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/psamp>,
	<mailto:psamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/psamp>
List-Post: <mailto:psamp@ietf.org>
List-Help: <mailto:psamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/psamp>,
	<mailto:psamp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: psamp-bounces@ietf.org
Errors-To: psamp-bounces@ietf.org

Thomas, all,

> A new version of I-D, draft-ietf-psamp-info-10.txt has been
> successfuly submitted by Thomas Dietz and posted to the IETF
> repository.

Thanks for this. Here's some feedback:



The table at the end of section 8 (right above the 8.1 title) is not
wide enough to accommodate the full names of #318 and #319. These have
been truncated, and should be fixed.



Section "8.2.1. selectorAlgorithm":

       Further method identifiers may be added to the list below.  It
       might be necessary to define new Information Elements to specify
       their parameters

   - full stop (period) is missing at the end.



OLD

       The selectorAlgorithm registry is maintained by IANA and can be
       updated when specifications of the new method(s) and any new
       Information Elements are provided.

       New assignments for the PSAMP selectionAlgorithm will be
       administered by IANA, and subject to Expert Review [RFC5226].  The
       group of experts must double check the selection method
       definitions and Information Elements with already defined
       selection methods and Information Elements for completeness,
       accuracy and redundancy.  Those experts will initially be drawn
       from the Working Group Chairs and document editors of the IPFIX
       and PSAMP Working Groups.

NEW

       The selectorAlgorithm registry is maintained by IANA.  New
       assignments for the registry will be administered by IANA,
       and subject to Expert Review [RFC5226].  The registry can be
       updated when specifications of the new method(s) and any new
       Information Elements are provided.

       The group of experts must double check the selectorAlgorithm
       definitions and Information Elements with already defined
       selectorAlgorithms and Information Elements for completeness,
       accuracy and redundancy.  Those experts will initially be drawn
       from the Working Group Chairs and document editors of the IPFIX
       and PSAMP Working Groups.

END



OLD

       The following packet selection methods identifiers are defined in
       [I-D.ietf-psamp-info]:
       +----+------------------------+------------------------+
       | ID |        Method          |      Parameters        |
       +----+------------------------+------------------------+

NEW

       The following selectorAlgorithm identifiers are defined here:

       +----+------------------------+------------------------+
       | ID |        Method          |      Parameters        |
       +----+------------------------+------------------------+

END



       There is a broad variety of possible parameters that could be used
       Property match Filtering (5) but currently there are no agreed
       parameters specified.

   - Should say "*for* Property match Filtering". However, the
information in the table above makes this paragraph redundant.

ie,
       +----+------------------------+------------------------+
       | 5  | Property match         | no agreed parameters   |
       |    | Filtering              |                        |
       +----+------------------------+------------------------+

Therefore, the paragraph should be removed.



Section "8.3. Hash Configuration (326-334)"

- It isn't immediately clear that "as well as in sections 3.8 and 7.1."
does NOT refer to this document itself:

OLD

    The following Information Elements can be used for describing the
    sampling configuration of a Selection Process.  The individual
    parameters are explained in more detail in the
    [I-D.ietf-psamp-sample-tech] in section 6.2 as well as in sections
    3.8 and 7.1.

NEW

    The following Information Elements can be used for describing the
    sampling configuration of a Selection Process.  The individual
    parameters are explained in more detail in sections 6.2, 3.8 and 7.1
    of [I-D.ietf-psamp-sample-tech].

END



Sections:

   8.3.1. digestHashValue
   8.3.2. hashIPPayloadOffset
   8.3.3. hashIPPayloadSize
   8.3.4. hashOutputRangeMin
   8.3.5. hashOutputRangeMax
   8.3.6. hashSelectedRangeMin
   8.3.7. hashSelectedRangeMax
   8.3.8. hashDigestOutput
   8.3.9. hashInitialiserValue

- It isn't immediately clear that "See also section 6.2" does NOT refer
to this document itself:

OLD

       See also section 6.2 as well sections 3.8 and 7.1 in [I-D.ietf-
       psamp-sample-tech].

NEW

       See also sections 6.2, 3.8 and 7.1 in
       [I-D.ietf-psamp-sample-tech].

END



10.2. PSAMP Related Considerations

OLD

    Each new selection method MUST be assigned a unique value for the
    selectorAlgorithm Information Element.  Its configuration
    parameter(s), along with the way to report it/them with an Options
    Template, MUST be clearly specified.  The initial content of the
    selection method registry is found in section 8.2.1.

NEW

    Each new selection method MUST be assigned a unique value in the
    selectorAlgorithm registry.  Its configuration parameter(s), along
    with the way to report it/them with an Options Template, MUST be
    clearly specified.  The initial content of the selectorAlgorithm
    registry is found in section 8.2.1.

END



Cheers.
-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
PSAMP mailing list
PSAMP@ietf.org
https://www.ietf.org/mailman/listinfo/psamp


From psamp-bounces@ietf.org  Sun Sep 21 07:02:01 2008
Return-Path: <psamp-bounces@ietf.org>
X-Original-To: psamp-text-archive@optimus.ietf.org
Delivered-To: ietfarch-psamp-text-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C2573A6983;
	Sun, 21 Sep 2008 07:02:01 -0700 (PDT)
X-Original-To: psamp@core3.amsl.com
Delivered-To: psamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AEEEB3A6983;
	Sun, 21 Sep 2008 07:01:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300, 
	BAYES_00=-2.599]
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 AFvrdV7vUhPT; Sun, 21 Sep 2008 07:01:58 -0700 (PDT)
Received: from av-tac-bru.cisco.com (odd-brew.cisco.com [144.254.15.119])
	by core3.amsl.com (Postfix) with ESMTP id 2B9D73A63C9;
	Sun, 21 Sep 2008 07:01:58 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	m8LE29L05276; Sun, 21 Sep 2008 16:02:09 +0200 (CEST)
Received: from [10.61.84.176] (ams3-vpn-dhcp5297.cisco.com [10.61.84.176])
	by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	m8LE1oA05781; Sun, 21 Sep 2008 16:02:08 +0200 (CEST)
Message-ID: <48D653CE.1000403@cisco.com>
Date: Sun, 21 Sep 2008 07:01:50 -0700
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: ietf@ietf.org
References: <20080915145103.AE89D28C130@core3.amsl.com>
In-Reply-To: <20080915145103.AE89D28C130@core3.amsl.com>
Cc: psamp@ietf.org
Subject: Re: [PSAMP] Last Call: draft-ietf-psamp-info (Information Model for
 Packet Sampling Exports) to Proposed Standard
X-BeenThere: psamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This mailing list is used for discussion within the IETF packet
	sampling \(PSAMP\) WG" <psamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/psamp>,
	<mailto:psamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/psamp>
List-Post: <mailto:psamp@ietf.org>
List-Help: <mailto:psamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/psamp>,
	<mailto:psamp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: psamp-bounces@ietf.org
Errors-To: psamp-bounces@ietf.org

Dear all,

Because dataLinkFrameSize and dataLinkFrameSection have been removed, 
the editor renumbered all the I.E. assignments.
That could generate some problems for existing implementations, if any. 
However, I can live with that.
However, where there is a bigger problem is that IANA is working on the 
IPFIX registry right now and there is a clash
It's a question of days (hopefully) before the registry official... See 
http://www.iana.org/assignments/ipfix/ipfix.xhtml
selectorName is already assigned 335, so you'll have to free that one 
(currently upperCILimit)
Proposal:

336 | lowerCILimit               |
337 | upperCILimit               |
338 | confidenceLevel            |

Regards, Benoit.
> The IESG has received a request from the Packet Sampling WG (psamp) to 
> consider the following document:
>
> - 'Information Model for Packet Sampling Exports '
>    <draft-ietf-psamp-info-10.txt> as a Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send substantive comments to the
> ietf@ietf.org mailing lists by 2008-09-29. Exceptionally, 
> comments may be sent to iesg@ietf.org instead. In either case, please 
> retain the beginning of the Subject line to allow automated sorting.
>
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-psamp-info-10.txt
>
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=11074&rfc_flag=0
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>   

_______________________________________________
PSAMP mailing list
PSAMP@ietf.org
https://www.ietf.org/mailman/listinfo/psamp


