Re: [IPFIX] comments on draft-scholz-ipfix-rtp-msg-00
Hadriel Kaplan <HKaplan@acmepacket.com> Wed, 28 March 2012 10:56 UTC
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88F9C21F896A for <ipfix@ietfa.amsl.com>; Wed, 28 Mar 2012 03:56:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level:
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mJW3CY2tbc0W for <ipfix@ietfa.amsl.com>; Wed, 28 Mar 2012 03:56:05 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 25F0621F89C7 for <ipfix@ietf.org>; Wed, 28 Mar 2012 03:56:05 -0700 (PDT)
Received: from MAIL1.acmepacket.com (10.0.0.21) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 28 Mar 2012 06:56:02 -0400
Received: from MAIL2.acmepacket.com ([169.254.2.197]) by Mail1.acmepacket.com ([169.254.1.170]) with mapi id 14.02.0283.003; Wed, 28 Mar 2012 06:56:02 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Aamer Akhter (aakhter)" <aakhter@cisco.com>
Thread-Topic: [IPFIX] comments on draft-scholz-ipfix-rtp-msg-00
Thread-Index: AQHNDNFdm5pcXpkw0kaR2dMa2rWSPg==
Date: Wed, 28 Mar 2012 10:56:01 +0000
Message-ID: <13B5187B-06D6-4E44-9E85-D092D3348954@acmepacket.com>
References: <4F702CF4.4040203@123.org><7EF1B485-21D1-4D3E-9C55-15C327D771C5@acmepacket.com><4F71A577.5000105@voipfuture.com> <90A8412F-65CE-42FB-9BEF-B8BA30C1A0AF@acmepacket.com> <7F298ACC76CC154F832B6D02852D169F079F3D37@XMB-RCD-101.cisco.com>
In-Reply-To: <7F298ACC76CC154F832B6D02852D169F079F3D37@XMB-RCD-101.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <43ECA6BFD5725746A385B1A9A7FE0135@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<ipfix@ietf.org>" <ipfix@ietf.org>
Subject: Re: [IPFIX] comments on draft-scholz-ipfix-rtp-msg-00
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2012 10:56:06 -0000
Makes sense to me. OK, so as I said in another email, the tricky part about this will be coming up with a consistent set of metrics across vendors, because if it's just one vendor's implementation model then it really shouldn't get an IANA-allocated IE number, should it? It's effectively proprietary and that's what PENs are for, no? Otherwise we'll be allocating hundreds of IANA-numberspace IEs, different ones for each vendor (my company alone has around few dozen different reported fields for RTP/RTCP). -hadriel p.s. why are your drafts in OPSAWG? On Mar 28, 2012, at 12:56 AM, Aamer Akhter (aakhter) wrote: > Hadriel, > > Multiple SSRC within the 5-tuple is how the CTS product line encodes > multiple audio/video channels. Other implementations eg. T3 series use > different 5-tuples. > > (5-tuple = ipsrc, ipdst, iprotocol, l4ports) > > " we should treat is as a separate flow from an IPFIX reporting > perspective, right?" > > this is exactly what is done in the implementation of: > > draft-akhter-opsawg-perfmon-ipfix > draft-akhter-opsawg-perfmon-method > > In fact, the key fields for the default RTP template (IOS configuration > follows): > > match ipv4 protocol > match ipv4 source address > match ipv4 destination address > match transport source-port > match transport destination-port > match transport rtp ssrc > > and the collect fields are: > > collect routing forwarding-status > collect ipv4 dscp > collect ipv4 ttl > collect transport packets expected counter > collect transport packets lost counter > collect transport packets lost rate > collect transport event packet-loss counter > collect transport rtp jitter mean > collect transport rtp jitter minimum > collect transport rtp jitter maximum > collect interface input > collect interface output > collect counter bytes > collect counter packets > collect counter bytes rate > collect counter packets dropped > collect timestamp interval > collect application media bytes counter > collect application media bytes rate > collect application media packets counter > collect application media packets rate > collect application media event > collect monitor event > > If the 'rtp ssrc' is not set as a key field, the various metrics form > the differing SSRC flows are aggregated to how a IPFIX 'flow' is > defined. > > > > -----Original Message----- > From: ipfix-bounces@ietf.org [mailto:ipfix-bounces@ietf.org] On Behalf > Of Hadriel Kaplan > Sent: Tuesday, March 27, 2012 5:41 PM > To: Hendrik Scholz > Cc: <ipfix@ietf.org> > Subject: Re: [IPFIX] comments on draft-scholz-ipfix-rtp-msg-00 > > > On Mar 27, 2012, at 1:33 PM, Hendrik Scholz wrote: > >>> 3) Some of the IEs imply there's a single SSRC for a flow - are you >>> assuming a flow is by definition the 6-tuple of IP src/dest, port >>> src/dest, transport type, and SSRC? In other words, if there are two > >>> or more SSRCs in the same 5-tuple, would they be separate IPFIX >>> flows? (they're only one "RTP" session from an RTP and SDP >>> perspective) >> >> Yes, a separate SSRC in between two nodes should be recorded in >> separate records. After all these streams would most likely belong to >> separate calls. > > As much as I'd love for that to be the case, technically they might or > might not. For normal voice between two users it's always the case. > But RFC 3550 always supported separate SSRCs in the same RTP session and > thus in the same 5-tuple, and RTCWeb and CLUE Working Groups have both > been talking about using that ability. (so for example video from > multiple cameras goes in the same RTP session, with separate SSRCs) At > least that's what I believe they're thinking of. And of course even for > a normal voice call there could be an SSRC collision, changing the SSRC > mid-call. > > I'm ok with assuming one, just wondering what we do if we get a second > one. I think you're saying we should treat is as a separate flow from > an IPFIX reporting perspective, right? > > -hadriel > > _______________________________________________ > IPFIX mailing list > IPFIX@ietf.org > https://www.ietf.org/mailman/listinfo/ipfix
- [IPFIX] initial draft for RTP message transport i… Hendrik Scholz
- [IPFIX] comments on draft-scholz-ipfix-rtp-msg-00 Hadriel Kaplan
- Re: [IPFIX] comments on draft-scholz-ipfix-rtp-ms… Hendrik Scholz
- Re: [IPFIX] comments on draft-scholz-ipfix-rtp-ms… Hadriel Kaplan
- Re: [IPFIX] comments on draft-scholz-ipfix-rtp-ms… Aamer Akhter (aakhter)
- Re: [IPFIX] comments on draft-scholz-ipfix-rtp-ms… Hadriel Kaplan
- Re: [IPFIX] comments on draft-scholz-ipfix-rtp-ms… Aamer Akhter (aakhter)
- Re: [IPFIX] comments on draft-scholz-ipfix-rtp-ms… Hadriel Kaplan
- Re: [IPFIX] comments on draft-scholz-ipfix-rtp-ms… Paul Aitken