IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 18 July 2013 23:20 UTC

Return-Path: <brian.e.carpenter@gmail.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 1FD9121E8145 for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 16:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level:
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 kqOSVMGFj9CW for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 16:20:34 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 23C1821E8143 for <int-area@ietf.org>; Thu, 18 Jul 2013 16:20:34 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un1so3727953pbc.29 for <int-area@ietf.org>; Thu, 18 Jul 2013 16:20:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1LoJEoYzX2UIy3WNHUEPlDXY19FLI9md73sRDoKrM5g=; b=bM6C92oshIBUIBYDxR0XV9vC9ZahINA5Fzh+CGKSIMIxoRU21w7M60BWWwPTXZYrT8 weGHkDs1uakFnJXmJU0WyKJHBBRVqPjnqiPfXCqvQL9dfZGGo55q1NeNof8/KlfTtR3Z PVyx/lAtNA3i01rF+nhsr1TiwZljtYtdNwTC7kIWP9MY/MoihLetrNgx3u10OhBZJSZK riw+i5vbeZTFyJpYygn/Y3Di/ODBXr0E1OKQ4EOdiyTwsmG9VE0ZpiLgBSMeJJ0xQZyM w4BFykSnULwKwPWzrC9JwSAgZuTMgvspr5+yu4qw9kTzZjtJVcrHVA5FF7CzpG/avSRk 6e7w==
X-Received: by 10.66.219.135 with SMTP id po7mr15516029pac.21.1374189633881; Thu, 18 Jul 2013 16:20:33 -0700 (PDT)
Received: from [192.168.178.23] (127.199.69.111.dynamic.snap.net.nz. [111.69.199.127]) by mx.google.com with ESMTPSA id sp4sm15897052pbc.45.2013.07.18.16.20.31 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Jul 2013 16:20:33 -0700 (PDT)
Message-ID: <51E87848.2030805@gmail.com>
Date: Fri, 19 Jul 2013 11:20:40 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>
References: <45A697A8FFD7CF48BCF2BE7E106F0604090C8B4D@xmb-rcd-x04.cisco.com>
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F0604090C8B4D@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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: Thu, 18 Jul 2013 23:20:36 -0000

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.
>>
> 
>

v2.23.0 | Report a Bug | By Email