Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt

Toerless Eckert <eckert@cisco.com> Fri, 19 July 2013 01:35 UTC

Return-Path: <eckert@cisco.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5592A11E824D for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 18:35:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.239
X-Spam-Level:
X-Spam-Status: No, score=-10.239 tagged_above=-999 required=5 tests=[AWL=-0.195, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_OBFU_PRESENTLY=0.555]
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 VoLBuVNr+FgG for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 18:35:12 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id F1E5211E81B6 for <int-area@ietf.org>; Thu, 18 Jul 2013 18:35:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1791; q=dns/txt; s=iport; t=1374197711; x=1375407311; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=uDZZZU5tZ18IBDKXgaEcHjEhpvzggb9I8ptS+ymbDY0=; b=mU5tuVGkEySWXqY/mNvSo7dnmFDGgKuF5nuk7BtMsYrNPcKiytWAsDIs KYvYjPl4XCMPA3g8y+/ovo92/ClU19otjjkRfjessPAF6ftaCRrua0SRX vYEuO/Dj6QXTzyMQpiazr59UY9YZlxeO8m2Wn2AiCRBSGSLTREaaWl2gl c=;
X-IronPort-AV: E=Sophos;i="4.89,697,1367971200"; d="scan'208";a="83405622"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 19 Jul 2013 01:35:11 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6J1ZBOZ002917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jul 2013 01:35:11 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r6J1ZAKH001488; Thu, 18 Jul 2013 18:35:10 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r6J1ZA2Q001487; Thu, 18 Jul 2013 18:35:10 -0700
Date: Thu, 18 Jul 2013 18:35:10 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20130719013510.GI23170@cisco.com>
References: <45A697A8FFD7CF48BCF2BE7E106F0604090C8B4D@xmb-rcd-x04.cisco.com> <51E87848.2030805@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <51E87848.2030805@gmail.com>
User-Agent: Mutt/1.4.2.2i
X-Mailman-Approved-At: Fri, 19 Jul 2013 07:55:40 -0700
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 01:35:16 -0000

Brian,

Let me give you a comparison: I think DNS is a system with
a standardized data-model for information about specific objects,
primarily hosts and services. The result/action from using DNS is
most commonly some TCP connection(s). That does not make DNS a
TSV target. The metadata framework is in my eyes about a system
with a standardized data-model for traffic-flows and the result/action
is most commonly some form of QoS for the traffic flows. Go figure.

Having said this, we asked to preesent in TSVWG as well, but it does 
not seem as if it would get onto the TSVWG WG agenda. I think there 
would be good collaborators to be found from TSV because like DNS
i would expect that the folks interested in the actions taken
have an interest to build a data-model to make their actions easier.

Cheers
    Toerless

On Fri, Jul 19, 2013 at 11:20:40AM +1200, Brian E Carpenter wrote:
> On 19/07/2013 09:41, Reinaldo Penno (repenno) wrote:
> > Hi Brian,
> > 
> > Metadata has many uses and not just QoS.
> 
> Sure, but some of them clearly concern layers above 3.
> 
> > 
> > Therefore we believe int-area to be appropriate. What are your thoughts?
> 
> I think this is a case where early discussion in TSVWG would avoid
> problems later. In the end the choice of WG doesn't matter as long as
> cross-area issues are caught as soon as possible.
> 
>    Brian
> 
> > On 7/18/13 4:58 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> > wrote:
> > 
> >> Why is this an intarea topic? To my mind it fits in tsvwg, which is
> >> currently discussing things like QoS for rtcweb.
> >>
> > 
> > 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area