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

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Fri, 10 February 2017 11:58 UTC

Return-Path: <ietf@kuehlewind.net>
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 142B512962B for <ioam@ietfa.amsl.com>; Fri, 10 Feb 2017 03:58:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 zEW0dKX7J6bU for <ioam@ietfa.amsl.com>; Fri, 10 Feb 2017 03:58:09 -0800 (PST)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE148129631 for <ioam@ietf.org>; Fri, 10 Feb 2017 03:58:08 -0800 (PST)
Received: (qmail 19559 invoked from network); 10 Feb 2017 12:58:07 +0100
Received: from p5dec2a07.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (93.236.42.7) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 10 Feb 2017 12:58:07 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <05a1d761-aed9-f62f-920b-93ed587a9fd4@gmail.com>
Date: Fri, 10 Feb 2017 12:58:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D1C9BC63-88D9-4DC0-87E4-9269E62A1E41@kuehlewind.net>
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> <05a1d761-aed9-f62f-920b-93ed587a9fd4@gmail.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ioam/fKXKKOuQmfBHLz4-GUhbPHH_fmo>
X-Mailman-Approved-At: Fri, 10 Feb 2017 04:32:24 -0800
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: Fri, 10 Feb 2017 11:58:12 -0000

Hi all,

as a side notice: marking is define as hybrid measurement in the already cited IPPM RFC 7799:

"Augmentation or modification of the stream of interest, or
      employment of methods that modify the treatment of the stream =>
      Hybrid Type I“

Mirja


> Am 10.02.2017 um 10:32 schrieb Stewart Bryant <stewart.bryant@gmail.com>:
> 
> 
> 
> On 09/02/2017 19:30, Carlos Pignataro (cpignata) wrote:
>> Hi, Stewart,
>> 
>> Many thanks for the comments, please see inline.
>> 
>>> On Feb 9, 2017, at 1:50 PM, Stewart Bryant <stewart.bryant@gmail.com> wrote:
>>> 
>>> 
>>> 
>>> On 09/02/2017 17:18, Carlos Pignataro (cpignata) wrote:
>>>> Passive means ‘solely by observation and without modification to the packet’ (https://tools.ietf.org/html/draft-ietf-ippm-active-passive-06#section-3.6).
>>> Carlos, that is not quit where we are going with passive. We use packet marking to batch the packets for loss measurement, and we are planning to trigger delay/jitter measurement through marking.
>>> 
>> I’ll follow down this tangent for a bit.
>> 
>> I understand and as you know I’m well aware of the (alternate) packet marking techniques and different methods.
>> 
>> However, the *current* definition is quite unambiguous:
>> 
>> https://tools.ietf.org/html/rfc7799#section-3.6
>> “
>> 3.6.  Passive Methods
>> 
>>    Passive Methods of Measurement are:
>> 
>>    o  based solely on observations of an undisturbed and unmodified
>>       packet stream of interest (in other words, the method of
>>       measurement MUST NOT add, change, or remove packets or fields or
>>       change field values anywhere along the path).
>> “
>> 
>> Since both those datapoints are rooted in IPPM, I’d suggest working through the definitions on IPPM and how marking fits (since it is not only on observation points)
>> 
>> Now, bringing this back to the relevance of the In-situ OAM (ioam) charter, my only point is that In-situ OAM is neither passive nor active.
> 
> ... and the point I make is that packet marking (which I think we have established is the only viable way of making accurate loss measurements in connectionless networking) is also neither active of passive according to these definitions.
> 
>> 
>>> As you know marking is much easier in MPLS that IP.
>>> 
>>> 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 suppose you could say: It is based on telemetry information which is embedded within live data packets and is distinct from packet parking methods being developed elsewhere in the IETF.
> 
> I have not thought it through, but I am wondering what distinguishes the packet types you list (IPv4, IPv6, VXLAN-GPE, LISP, NSH, SRv6, Geneve) from other packet types, the obvious one being MPLS. Not that I am at all keen on trying to get this into the simple fast forwarders we use for MPLS. In other words what is the generic class of packets you are targetting?
> 
> Stewart
> 
>> 
>> Thanks!
>> 
>>> - Stewart
>> 
>> —
>> Carlos Pignataro, carlos@cisco.com
>> 
>> “Sometimes I use big words that I do not fully understand, to make myself sound more photosynthesis."
>> 
>