Re: [PSAMP] New Version Notification for draft-ietf-psamp-info-10
Paul Aitken <paitken@cisco.com> Thu, 18 September 2008 14:14 UTC
Return-Path: <psamp-bounces@ietf.org>
X-Original-To: psamp-archive@lists.ietf.org
Delivered-To: ietfarch-psamp-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