[IPFIX] IPFIX and PSAMP status
Benoit Claise <bclaise@cisco.com> Thu, 22 November 2007 16:45 UTC
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvFAs-0006H7-Uq; Thu, 22 Nov 2007 11:45:11 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvFAr-0006Da-My; Thu, 22 Nov 2007 11:45:09 -0500
Received: from no-more.cisco.com ([64.104.206.251] helo=av-tac-apt.cisco.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IvFAq-0004tp-LE; Thu, 22 Nov 2007 11:45:09 -0500
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1]) by av-tac-apt.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id lAMGj1j11747; Fri, 23 Nov 2007 03:45:03 +1100 (EST)
Received: from [10.61.82.26] (ams3-vpn-dhcp4635.cisco.com [10.61.82.26]) by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id lAMGiqI14391; Thu, 22 Nov 2007 17:44:58 +0100 (CET)
Message-ID: <4745B204.70400@cisco.com>
Date: Thu, 22 Nov 2007 17:44:52 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: "ipfix@ietf.org" <ipfix@ietf.org>, psamp@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5
Cc:
Subject: [IPFIX] IPFIX and PSAMP status
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1703221688=="
Errors-To: ipfix-bounces@ietf.org
Dear all,
I made this little summary for myself, to understand what the next
bottleneck(s) is/are in IPFIX and as a consequence in PSAMP
Then I thought about sharing this info, as it might be useful for others
as well...
_IPFIX_
Drafts in the RFC-editor queue:
_STATE_
_DEPENDENCIES_
draft-ietf-ipfix-info AUTH, but I
replied so will become EDIT IPFIX-PROTO: in queue
draft-ietf-ipfix-protocol EDIT
IPIFX-INFO: in queue
draft-ietf-ipfix-biflow EDIT
IPFIX-PROTO,
IPFIX-INFO: in queue
draft-ietf-ipfix-architecture EDIT
IPFIX-PROTO,
IPFIX-INFO, IPFIX-AS: in queue
draft-ietf-ipfix-as
MISSREF IPFIX-INFO,
IPFIX-PROTO: in queue
Missing PSAMP-INFO
draft-ietf-ipfix-reducing-redundancy
MISSREF
IPFIX-PROTO, IPFIX-INFO: in queue
Missing PSAMP-PROTO
Drafts not yet in the RFC-editor queue:
_STATUS_
_DEPENDENCIES___
draft-ietf-ipfix-implementation-guidelines In last call, version
posted IPFIX-PROTO, IPFIX-INFO: in queue
(but
missed the deadline)
draft-ietf-ipfix-testing In last
call, new version posted IPFIX-PROTO, IPFIX-INFO,
IPFIX-ARCH, IPFIX-AS: in queue
draft-ietf-ipfix-mib One more
version needed before the last call IPFIX-PROTO, IPFIX-INFO: in queue
_PSAMP_
Drafts not yet in the RFC-editor queue:
_STATUS_ __
draft-ietf-psamp-framework IESG review
draft-ietf-psamp-sample-tech IESG review
draft-ietf-psamp-protocol IESG review,
Received some feedback from Dan and Suresh Krishnan, addressed already
Will
receive some more feedback from the transport area directors
draft-ietf-psamp-info WG Last call
Juergen: "I will not close the call without knowing of at least
three solid reviews from non-authors"
In conclusion: the next bottleneck is [PSAMP-INFO].
Some more reviews would be appreciated in order to have the first series
of IPFIX RFCs
Regards, Benoit.
_______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www1.ietf.org/mailman/listinfo/ipfix
- [IPFIX] IPFIX and PSAMP status Benoit Claise