[IPFIX] I-D Action: draft-ietf-ipfix-protocol-rfc5101bis-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item
of the IP Flow Information Export Working Group of the IETF.

	Title           : Specification of the IP Flow Information eXport (IPFIX) Protocol for the Exchange of IP Traffic
Flow Information
	Author(s)       : Benoit Claise
                          Brian Trammell
	Filename        : draft-ietf-ipfix-protocol-rfc5101bis-00.txt
	Pages           : 73
	Date            : 2011-11-29

   This document specifies the IP Flow Information Export (IPFIX)
   protocol that serves for transmitting IP Traffic Flow information
   over the network.  In order to transmit IP Traffic Flow information
   from an Exporting Process to an information Collecting Process, a
   common representation of flow data and a standard means of
   communicating them is required.  This document describes how the
   IPFIX Data and Template Records are carried over a number of
   transport protocols from an IPFIX Exporting Process to an IPFIX
   Collecting Process.  This document obsoletes RFC 5101.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipfix-protocol-rfc5101bis-00.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipfix-protocol-rfc5101bis-00.txt

[IPFIX] Fwd: New Version Notification for draft-claise-export-application-info-in-ipfix-04.txt

_______________________________________________
IPFIX mailing list
IPFIX <at> ietf.org
https://www.ietf.org/mailman/listinfo/ipfix

Re: [IPFIX] Fwd: New Version Notification for draft-claise-export-application-info-in-ipfix-04.txt

_______________________________________________
IPFIX mailing list
IPFIX <at> ietf.org
https://www.ietf.org/mailman/listinfo/ipfix

Re: [IPFIX] review of draft-claise-ipfix-mediation-protocol-04

_______________________________________________
IPFIX mailing list
IPFIX <at> ietf.org
https://www.ietf.org/mailman/listinfo/ipfix

[IPFIX] I-D Action: draft-ietf-ipfix-mediation-protocol-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item
of the IP Flow Information Export Working Group of the IETF.

	Title           : Specification of the Protocol for IPFIX Mediation
	Author(s)       : Benoit Claise
                          Atsushi Kobayashi
                          Brian Trammell
	Filename        : draft-ietf-ipfix-mediation-protocol-00.txt
	Pages           : 33
	Date            : 2011-12-06

        This document specifies the IP Flow Information Export
        (IPFIX) protocol specific to Mediation.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipfix-mediation-protocol-00.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipfix-mediation-protocol-00.txt

_______________________________________________
IPFIX mailing list
IPFIX <at> ietf.org
https://www.ietf.org/mailman/listinfo/ipfix

Re: [IPFIX] I-D Action: draft-ietf-ipfix-mediation-protocol-00.txt

Dear all,

This version takes into account all the feedback received from Paul 
Aitken (I replied to Paul's email to the list yesterday).
On the top of that, the timestamps issue has been fixed by Brian.
Note that some points, which might require some discussions, have been 
listed in the open issues in the draft.

Regards, Benoit.
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work
item of the IP Flow Information Export Working Group of the IETF.
>
> 	Title           : Specification of the Protocol for IPFIX Mediation
> 	Author(s)       : Benoit Claise
>                            Atsushi Kobayashi
>                            Brian Trammell
> 	Filename        : draft-ietf-ipfix-mediation-protocol-00.txt
> 	Pages           : 33
> 	Date            : 2011-12-06
>
>          This document specifies the IP Flow Information Export
>          (IPFIX) protocol specific to Mediation.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ipfix-mediation-protocol-00.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipfix-mediation-protocol-00.txt
>
> _______________________________________________
> IPFIX mailing list
> IPFIX <at> ietf.org
> https://www.ietf.org/mailman/listinfo/ipfix
>
>

_______________________________________________
IPFIX mailing list
IPFIX <at> ietf.org
https://www.ietf.org/mailman/listinfo/ipfix

[IPFIX] WGLC: draft-ietf-bmwg-ipflow-meth-05

BMWG,
CC: IPFIX WG,

This message begins the *fourth* WG Last call on the draft:

IP Flow Information Accounting and Export Benchmarking Methodology

A URL for this draft is:
http://tools.ietf.org/html/draft-ietf-bmwg-ipflow-meth-05

The Last Call will end on January 1, 2012.

We have discussed this draft in the working group for
over three years and made many improvements.
We have also benefited from review by folks from IPFIX WG.

*We have now looked in detail at comments from the 3rd WGLC
and their resolution, including 5 open issues identified
and resolved on the list.*

I now ask everyone to consider items where they commented earlier,
and make sure that the resolutions are satisfactory (and thanks to
those who did this during the second WGLC).

Please weigh-in on whether or not this Internet-Draft
should be given to the Area Directors and IESG for consideration and
publication as an Informational RFC.  Send your comments
to this list and/or acmorton <at> att.com.

Al
bmwg chair

_______________________________________________
IPFIX mailing list
IPFIX <at> ietf.org
https://www.ietf.org/mailman/listinfo/ipfix

[IPFIX] sip-msg-02 SIP messages and aggregation

Hi!

My main interest is to write a single data record describing an
entire SIP dialog (e.g. a call between two parties) and not
a single SIP message.

Below are numerous points where I feel the current definition
may clash with that use case.

2.1 sipObservationType

There is a 'receiver' and 'sender' metering process type for
metering processes co-located with the SIP entity.
I case I want to aggregate multiple SIP messages into a single
entry what should I set here?
It does make a different whether the monitoring process was
co-located with the device or whether it pass 'mid-point'
(option 3 aka 'passive').

Another way of looking at the sipObservationType would be
'unknown', 'co-located' (aka 'end-point') and 'mid-point'.
This drops the 'sender'/'receiver' differentiation.
Could we extend it to have both bits of information encoded
in the sipObservationType?

2.5. sipFromURI
2.7. sipToURI

Would this include URI parameters?
sample: sip:user:password <at> host:port;uri-parameters?headers

This effectively duplicates the 2.6. sipFromTag and
2.8. sipToTag.

A system may opt to display sipFromURI and sipToURI which
may (rare case I guess) include the password. Often
sip:user <at> host would be enough, although it may be up
to the collector to remove unneeded bits.

2.9 sipCallId

Session-ID as defined in draft-kaplan-dispatch-session-id-03
won't be added for now as it's not a WG item, correct?

2.10. sipResponseStatus

In case multiple SIP messages are aggregated into one record
this should be allowed to hold the 'final response', e.g.
a 408 timeout even multiple callees responded with 486 or
early media (180, 183, ...).

3.1. sipContactURI

In the 'aggregated information' usage scenario there would
be (at least) two Contact URIs, e.g. named sipCallerURI and
sipCalleeURI (or UAS/UAC).

4. Template additions

For an aggregated 'sip session' the template would not only
need the observationTimeMilliseconds IE but also
a start/end time plus an optional PostDialDelay etc.
Essentially everything to calculate the RFC6076 SIP
performance metrics.

Finally we should allow SIPS URIs in the SIP URI fields or
point out that this is not intended.

Should I contribute a separate document with additional
Information Elements needed to describe SIP sessions
and a matching recommended template?

Regards,
 Hendrik

--

-- 
VOIPFUTURE GmbH   Wendenstraße 4   20097 Hamburg   Germany
Phone +49 40 688 900 163    Fax +49 40 688 900 199
Email hendrik.scholz <at> voipfuture.com   Web http://www.voipfuture.com

CEO Jan Bastian
Commercial Court AG Hamburg   HRB 109896
VAT ID DE263738086

_______________________________________________
IPFIX mailing list
IPFIX <at> ietf.org
https://www.ietf.org/mailman/listinfo/ipfix

[IPFIX] RTP media stream template?

Hi!

Is anybody working on a template and related IEs for RTP media streams?
I am happy to contribute and/or author the needed documents.

The use cases for this include active VoIP components which handle
RTP streams and want to provide data records as well as passive
monitoring systems which are build to monitor RTP streams.
IEs include general RTP information (source, destination, codec)
as well as IP transport quality (jitter, packet loss, ..) and
higher-level metrics such as R-Factor and MOS value where available.

The template should allow both data records on entire streams (i.e.
part of calls minutes or even hours long) as well as fixed time slices
such as 10 seconds to allow monitoring with a high granularity.

Regards,
 Hendrik

--

-- 
VOIPFUTURE GmbH   Wendenstraße 4   20097 Hamburg   Germany
Phone +49 40 688 900 163    Fax +49 40 688 900 199
Email hendrik.scholz <at> voipfuture.com   Web http://www.voipfuture.com

CEO Jan Bastian
Commercial Court AG Hamburg   HRB 109896
VAT ID DE263738086

_______________________________________________
IPFIX mailing list
IPFIX <at> ietf.org
https://www.ietf.org/mailman/listinfo/ipfix

Re: [IPFIX] RTP media stream template?

Hey Hendrik,
Argus has RTP specific flow records, with its own IEs for reporting attributes
and metrics for the media streams.   The argus sensor does RTP discovery
on the fly, generating the extended flow attributes without configuration.

The argus DSRs provide the RTP specific information, such as codec, as
well as jitter, ( adjusting for silence suppression when encountered ), loss
and out of order indications, and the argus-client aggregation deals with
handling both entire streams and fixed/variable time slices, no problem.

Argus is not IPFIX, but you may find the argus approach useful.

http://qosient.com/argus

Carter

Carter Bullard
CEO/President
QoSient, LLC
150 E 57th Street Suite 12D
New York, New York  10022

+1 212 588-9133 Phone
+1 212 588-9134 Fax

On Dec 7, 2011, at 11:16 AM, Hendrik Scholz wrote:

> Hi!
> 
> Is anybody working on a template and related IEs for RTP media streams?
> I am happy to contribute and/or author the needed documents.
> 
> The use cases for this include active VoIP components which handle
> RTP streams and want to provide data records as well as passive
> monitoring systems which are build to monitor RTP streams.
> IEs include general RTP information (source, destination, codec)
> as well as IP transport quality (jitter, packet loss, ..) and
> higher-level metrics such as R-Factor and MOS value where available.
> 
> The template should allow both data records on entire streams (i.e.
> part of calls minutes or even hours long) as well as fixed time slices
> such as 10 seconds to allow monitoring with a high granularity.
> 
> Regards,
> Hendrik
> 
> -- 
> VOIPFUTURE GmbH   Wendenstraße 4   20097 Hamburg   Germany
> Phone +49 40 688 900 163    Fax +49 40 688 900 199
> Email hendrik.scholz <at> voipfuture.com   Web http://www.voipfuture.com
> 
> CEO Jan Bastian
> Commercial Court AG Hamburg   HRB 109896
> VAT ID DE263738086
> 
> _______________________________________________
> IPFIX mailing list
> IPFIX <at> ietf.org
> https://www.ietf.org/mailman/listinfo/ipfix
> 

_______________________________________________
IPFIX mailing list
IPFIX <at> ietf.org
https://www.ietf.org/mailman/listinfo/ipfix