[tsvwg] FW: New Version Notification for draft-choukir-tsvwg-flow-metadata-encoding-00.txt

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Tue, 09 July 2013 21:08 UTC

Return-Path: <eckelcu@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4148121F9DB5 for <tsvwg@ietfa.amsl.com>; Tue, 9 Jul 2013 14:08:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 sL05nSpA0RGN for <tsvwg@ietfa.amsl.com>; Tue, 9 Jul 2013 14:08:40 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id BF78621F9D0F for <tsvwg@ietf.org>; Tue, 9 Jul 2013 14:08:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4780; q=dns/txt; s=iport; t=1373404120; x=1374613720; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=2LNnDhHIsBxSOzxjSw7VHsju2PGgq9U5UU4PN5BQHJE=; b=XBAFef5DRhGizB47EbjRxLoyzfwcGk4/DqmprGGHKtLdJmAwM1tJmah0 8zygHquRiOefgS2n755pKBx4/aTXKJNe5JfRknJhzF8Y91lXAz3GFIDMA +Rdx5YftJW/BOkjoNHyoITfwSRvIjzSidePB3FY84oyHslPxwuzRkPftp M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFANR63FGtJV2b/2dsb2JhbABbgwkyTYMIvgkXgQQWdIIjAQEBBCMRQw4GAQgRBAEBAwIGHQMCBDAUAQYBAQUEAQQTCAGIBQEMmWCOfZEpgSaOFA8vglAzawOYfZAggViBOYIo
X-IronPort-AV: E=Sophos;i="4.87,1030,1363132800"; d="scan'208";a="232815259"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-3.cisco.com with ESMTP; 09 Jul 2013 21:08:39 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r69L8dSj017435 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Tue, 9 Jul 2013 21:08:39 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.187]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.02.0318.004; Tue, 9 Jul 2013 16:08:38 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: New Version Notification for draft-choukir-tsvwg-flow-metadata-encoding-00.txt
Thread-Index: Ac586HrbP3VYJaT6Rgu7o3L6GEcq0A==
Date: Tue, 09 Jul 2013 21:08:37 +0000
Message-ID: <92B7E61ADAC1BB4F941F943788C08828048B0832@xmb-aln-x08.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [171.68.16.40]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [tsvwg] FW: New Version Notification for draft-choukir-tsvwg-flow-metadata-encoding-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2013 21:08:45 -0000

This is one of a set of drafts for communicating flow characteristics (a.k.a. metadata) in a consistent manner between applications and the network to provide better visibility of application flows.

The framework is described in:
http://tools.ietf.org/html/draft-eckert-intarea-flow-metadata-framework-00

This document (http://tools.ietf.org/html/draft-choukir-tsvwg-flow-metadata-encoding-00) describes a protocol independent encoding for flow metadata. A flow is defined as a set of IP packets passing through a network in a given direction.  All packets belonging to a particular flow have a set of common properties (e.g. IP, port, transport).
Flow metadata exposes key characteristics of the flow, such as the bandwidth, the tolerance to delay and loss, and others as defined in the framework draft. This information is signaled along the same path as the actual flow.

The mapping of flow metadata encoding to different signaling protocols is outside the scope of this document. The following drafts provide mapping to PCP, RSVP, and STUN:
http://tools.ietf.org/html/draft-wing-pcp-flowdata-00
http://tools.ietf.org/html/draft-zamfir-tsvwg-flow-metadata-rsvp-00
http://tools.ietf.org/html/draft-martinsen-mmusic-malice-00

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, July 08, 2013 3:13 PM
To: Toerless Eckert (eckert); Amine Choukir (amchouki); Anca Zamfir (ancaz); Charles Eckel (eckelcu)
Subject: New Version Notification for draft-choukir-tsvwg-flow-metadata-encoding-00.txt


A new version of I-D, draft-choukir-tsvwg-flow-metadata-encoding-00.txt
has been successfully submitted by Toerless Eckert and posted to the
IETF repository.

Filename:	 draft-choukir-tsvwg-flow-metadata-encoding
Revision:	 00
Title:		 Protocol Independent Encoding for Signaling Flow Characteristics
Creation date:	 2013-07-09
Group:		 Individual Submission
Number of pages: 18
URL:             http://www.ietf.org/internet-drafts/draft-choukir-tsvwg-flow-metadata-encoding-00.txt
Status:          http://datatracker.ietf.org/doc/draft-choukir-tsvwg-flow-metadata-encoding
Htmlized:        http://tools.ietf.org/html/draft-choukir-tsvwg-flow-metadata-encoding-00


Abstract:
   This document describes a protocol independent encoding for flow
   characteristics (a.k.a. metadata).  A flow is defined as a set of IP
   packets passing through a network in a given direction.  All packets
   belonging to a particular flow have a set of common properties (e.g.
   IP, port, transport).  Flow metadata exposes key characteristics of
   the flow such as the originating application, the type of media in
   use (e.g.  audio, video) and others as defined in
   [I-D.eckert-intarea-flow-metadata-framework].  The flow
   characteristics are expressed in terms of information elements.
   These information elements are signaled either out of band or in band
   but always along the same path of the flow associated with the
   application.

   [I-D.eckert-intarea-flow-metadata-framework] defines the overall
   framework for flow metadata and the definition of the flow
   characteristics, whereas this document captures the encoding of these
   characteristics.  The mapping of flow metadata encoding to different
   signaling protocols is outside the scope of this document.

                                                                                  


The IETF Secretariat