Subject: [ipfix] Comments on IPFIX requirements

From: "Kevin Zhang" <[email-masked]>
Date: Sun, 9 Dec 2001 01:27:46 -0500

Hi All,

I have the following comments on the IPFIX requirement document. They all relate to section 5.3 Data Transfer section of the draft.  Time permitting, I hope we can talk about them and consider their inclusion in the requirement draft.

See you at Salt Lake City!

Kevin Zhang
XACCT Technologies, Inc.
Mobile 1 (301) 992-4697 

-----------------------------

Comments 

   Section 5.3 Data Transfer  
    
   No change 
    
   Section 5.3.1 Congestion Awareness 
    
   Data transfer MUST use a congestion aware protocol. A congestion 
   aware protocol MUST implement congestion control and avoidance 
   algorithms that maintain stability of the Internet.  The algorithms 
   SHOULD have behaviors that are well understood and acceptable by the 
   Internet community. An example of such an algorithm is the additive-
   increase/multiplicative-decrease (AIMD), which is implemented by the 
   TCP and SCTP.    
    
   Section 5.3.2 Reliability 
    
   Data transfer SHOULD be reliable.  In this context, Reliability 
   refers to the in-sequence, error free delivery of data from the 
   exporter to external systems. Absence of reliability MUST be 
   indicated by the IPFIX system covering data loss, data errors, out-
   of-sequence data, and duplicated data. 
    
   Reliability may be achieved without using a reliable transport layer 
   protocol.  In this case, reliability should be provided by higher 
   layer functions.  
    
   For certain applications that do not require reliability data 
   transfer, an unreliable transport protocol is typically used.  In 
   such a case, lack of overall reliability MUST be indicated.  
    
   Section 5.3.3 Security 
    
   No change 
    
   Section 5.3.4 Push and Pull Mode Reporting 
    
   No change 
    
   Section 5.3.5 Regular Reporting Interval 
    
   No change 
    
   Section 5.3.6 Notification on Specific Events   
    
   No change 
    
   Section 5.3.7 Anonymization 
    
   No change  
    
   Section 5.3.8 Flow Control 
    
   When reliable data transfer is required, flow control SHOULD be 
   supported.  Flow control functions protect the data receiver from 
   being overwhelmed by the amount of received data, which may lead to 
   data loss.         
    
   Section 5.3.9 Robustness 
    
   Data transfer SHOULD be robust against network and system fault 
   conditions.  Robustness may be supported by deploying redundant data 
   receiving systems, and fail-over/fail-back procedures. 
    
   Section 5.3.10 Efficiency 
    
   Data transfer MUST be efficient. Efficiency can be measured by 
   assessing data transfer overhead, which include message encoding 
   overhead, and data encoding overhead. 
    
-------------------------------------------------��ޖ���[h�f���h���z�ݢ+��+��njwlk/�zZ��y��Ơy��I칻�&ޙ�����j:+v���w���"��"���v�vƲ��칻�&ފ�������,j��܀��b��m����*_�ݢ+��+��n��܆+�