IETF Logo Mail Archive

Re: [Ioam] Internal WG Review: In-situ OAM (ioam)

Joe Clarke <jclarke@cisco.com> Sat, 11 February 2017 10:47 UTC

Return-Path: <jclarke@cisco.com>
X-Original-To: ioam@ietfa.amsl.com
Delivered-To: ioam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6888D12943F; Sat, 11 Feb 2017 02:47:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vGX-9bE57S3j; Sat, 11 Feb 2017 02:47:01 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CDB0129446; Sat, 11 Feb 2017 02:47:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=964; q=dns/txt; s=iport; t=1486810020; x=1488019620; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=XaNm/82RbomHjWJvQXLitUhqw02Jg/NdjmHoK+TripQ=; b=jJf8uBgCCm5BHtnepHjjEF8o3t7NwFUjLtk9fkzmQzEa9hK25SVPL8d3 uoa+Dfad2MKaiKjVIpsXHmYzt0iEfcxyvD9PM6aFjRNbwO/9/kndIjtxj /9Qv9MYJWfkNDSUnKqBg+isESt1akheCY39YQAkHyJBbVM/Pm6n6uaRox I=;
X-IronPort-AV: E=Sophos;i="5.35,145,1484006400"; d="scan'208";a="207441486"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Feb 2017 10:47:00 +0000
Received: from [10.82.254.64] (rtp-vpn6-1594.cisco.com [10.82.254.64]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v1BAkvLA002562; Sat, 11 Feb 2017 10:46:58 GMT
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Stewart Bryant <stewart.bryant@gmail.com>
References: <148657872835.4362.4208222446069276322.idtracker@ietfa.amsl.com> <CAKKJt-cwinU_f+Kgb+PuUfufZdAL788ZyYjd_2o3UCLwE5FJmQ@mail.gmail.com> <5EADB2FC-9112-4C6F-956D-C9B0A7FA405F@cisco.com> <6F7EEE4C-2D31-438E-B672-49FEED30C1A4@cisco.com> <4f16e222-97e4-6f87-e1a3-79115db8f355@gmail.com> <A011008B-F1A7-4EE0-8693-E66471B456E4@cisco.com>
From: Joe Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
Message-ID: <45cb7ac3-bca6-84fa-9cc0-b7ba3eec47f9@cisco.com>
Date: Sat, 11 Feb 2017 05:46:57 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <A011008B-F1A7-4EE0-8693-E66471B456E4@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ioam/56KtGxKu0vXOqvp8myTZpjsibtw>
Cc: "Alvaro Retana (aretana)" <aretana@cisco.com>, The IAB <iab@iab.org>, "ioam@ietf.org" <ioam@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Subject: Re: [Ioam] Internal WG Review: In-situ OAM (ioam)
X-BeenThere: ioam@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion on In-Situ OAM <ioam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ioam>, <mailto:ioam-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ioam/>
List-Post: <mailto:ioam@ietf.org>
List-Help: <mailto:ioam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ioam>, <mailto:ioam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 10:47:03 -0000

On 2/9/17 14:30, Carlos Pignataro (cpignata) wrote:
>> I think the key distinguisher is really that in-situ is about embedding OAM meta-data in user data traffic.
> 
> This is a good point.
> 
> I agree.
> 
> I believe this is already clear in the charter, all the way from the very first sentence:
> 
> “ It is based on telemetry information which is embedded within live data packets.”
> 
> Do you believe this is not clear in the charter? Do you have specific suggestions or concrete recommendations that can improve the charter text?

I'm not sure this is clear (i.e., "live data").  Intuitively, I know
what IOAM is trying to do, but the expression live data or even user
data may not be ultimately clear as to the scope.  For example, would
IOAM headers be excluded from packets that did not have any data payload?

Yeah, this is a bikeshed, but would text such as "packets within
existing network flows" be better or clearer?

Joe

v2.23.0 | Report a Bug | By Email