IETF Logo Mail Archive

[sfc] Fwd: I-D Action: draft-mirsky-sfc-pmamm-08.txt

Greg Mirsky <gregimirsky@gmail.com> Wed, 19 June 2019 02:34 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1626C120455; Tue, 18 Jun 2019 19:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 r90P8ngWNnWx; Tue, 18 Jun 2019 19:34:39 -0700 (PDT)
Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C18F12042B; Tue, 18 Jun 2019 19:34:39 -0700 (PDT)
Received: by mail-lf1-x133.google.com with SMTP id p24so10814265lfo.6; Tue, 18 Jun 2019 19:34:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=yHOEaQ2u1BpRKWEeT9JVc3e39FwrMGxzw0Om5mOoK1M=; b=WU3GIO0Q04ipZKNnk2tyzifWOgat8XIFBpNHWmJU7QKOmcoGhEGz8UWcxIeN5q571f bTojWNNckNBfGQ0j2vnJR58GoMc6OtiaPMe225HMoPTJi1Fb5lKOnd04LEUb4XqzRYfp Vccm2ORFTQynG07yzlekKvGE+d7JvJzjyBgYCfblOPdfkq2cJkwWNpb2WCnoTFPu5mSb dTPChPa1t0VqSggYX2TBjF1eeedryYN1obiXqt5Nz/EtWyBWcMSXhuUrJ+TfRqGfnZnM Bf8eaWU5GRrkXIMuTxsIL0slkSB4aaQgZCXrrHMIhktRkyrwkBoTIaqoir0n2a8oTOw7 bekQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=yHOEaQ2u1BpRKWEeT9JVc3e39FwrMGxzw0Om5mOoK1M=; b=jMz9ZY3ZAEWHqEOfR0NOsaW/6GhanArGvFgXNOUfOIX23jSPBKZ8QYLxcwtJKDU1wG KHztSQXKOpKfChuaIHRecLdfF0PHz+dftTAgrOF+8YXq4V4vFTUwupzPuDH9pLrlQu+B 4xLQtBBV20u8Mu/U1BjBX/oCRHGFAmStD4g623k6JNFoxYncDaTuxFij24iQH4UBxXgR WWWQu/yCgzF5TVGmmCgIeJx7pB04ugxSO37rzrX/787gDMi37TYnZzQrwEdK5zRTSfGa Z9oNhXrRQThYca3IKsbHjax23/XHWyYZmLrR923lvk9VW/Glw4FJpRe0cYu4VlGcLczI NMfQ==
X-Gm-Message-State: APjAAAURPgwpw3yKYnjJWbWkkeFP58TvItV/bAfzT6KIrIw5LW1vloAA 4tzntg/p4BYeuZ8Q6elauYbGf11e3Gh0fx+AlsspIdX+f2M=
X-Google-Smtp-Source: APXvYqzjCzUZyrKyeXx4ph1ecVtaI9nBZTfZ4B8fL4iIZkFd//6enbE1dhVaf9+6IQFGjBIE+lc/ET23n1XrQUFF4Ws=
X-Received: by 2002:a05:6512:24a:: with SMTP id b10mr57992311lfo.37.1560911676856; Tue, 18 Jun 2019 19:34:36 -0700 (PDT)
MIME-Version: 1.0
References: <156091138590.6812.10199318977186808996@ietfa.amsl.com>
In-Reply-To: <156091138590.6812.10199318977186808996@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 19 Jun 2019 11:34:22 +0900
Message-ID: <CA+RyBmV1Szjirvhtg+NfbQBtHJQoU62v+Z0swAK-mzfMr=oPTg@mail.gmail.com>
To: Service Function Chaining IETF list <sfc@ietf.org>, sfc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000065c9f058ba41236"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/40dQP2tTk-VX28G-Kr684qniB-s>
Subject: [sfc] Fwd: I-D Action: draft-mirsky-sfc-pmamm-08.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2019 02:34:48 -0000

Dear All,
the updates are to address comments from Carlos on the characterization of
the AltMark method and the classification of the performance measurement
methods in RFC 7799. Authors are committed to continuing working on updates
to address all the comments received during the WG AP.

Regards,
Greg
---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Wed, Jun 19, 2019 at 11:30 AM
Subject: [sfc] I-D Action: draft-mirsky-sfc-pmamm-08.txt
To: <i-d-announce@ietf.org>
Cc: <sfc@ietf.org>



A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Service Function Chaining WG of the IETF.

        Title           : Performance Measurement (PM) with Alternate
Marking Method in Service Function Chaining (SFC) Domain
        Authors         : Greg Mirsky
                          Giuseppe Fioccola
                          Tal Mizrahi
        Filename        : draft-mirsky-sfc-pmamm-08.txt
        Pages           : 8
        Date            : 2019-06-18

Abstract:
   This document describes how the alternate marking method can be used
   as the efficient performance measurement method taking advantage of
   the actual data flows in a Service Function Chaining (SFC) domain.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-mirsky-sfc-pmamm/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-mirsky-sfc-pmamm-08
https://datatracker.ietf.org/doc/html/draft-mirsky-sfc-pmamm-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-mirsky-sfc-pmamm-08


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
sfc mailing list
sfc@ietf.org
https://www.ietf.org/mailman/listinfo/sfc

v2.23.0 | Report a Bug | By Email