[mpls] RFC 8372 on MPLS Flow Identification Considerations

rfc-editor@rfc-editor.org Wed, 02 May 2018 21:44 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5F8612DA2B; Wed, 2 May 2018 14:44:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 mBdgeeVmLS5B; Wed, 2 May 2018 14:44:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F54812708C; Wed, 2 May 2018 14:44:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C128EB8155D; Wed, 2 May 2018 14:44:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mpls@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180502214449.C128EB8155D@rfc-editor.org>
Date: Wed, 2 May 2018 14:44:49 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/vklp5dQX8Wt7qCVJXWA28lAcCcY>
Subject: [mpls] =?utf-8?q?RFC_8372_on_MPLS_Flow_Identification_Considerati?= =?utf-8?q?ons?=
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 21:44:56 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8372

        Title:      MPLS Flow Identification Considerations 
        Author:     S. Bryant,
                    C. Pignataro,
                    M. Chen,
                    Z. Li,
                    G. Mirsky
        Status:     Informational
        Stream:     IETF
        Date:       May 2018
        Mailbox:    stewart.bryant@gmail.com, 
                    cpignata@cisco.com, 
                    mach.chen@huawei.com,
                    lizhenbin@huawei.com, 
                    gregimirsky@gmail.com
        Pages:      11
        Characters: 26645
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-flow-ident-07.txt

        URL:        https://www.rfc-editor.org/info/rfc8372

        DOI:        10.17487/RFC8372

This document discusses aspects to consider when developing a
solution for MPLS flow identification.  The key application that
needs this solution is in-band performance monitoring of MPLS flows
when MPLS is used to encapsulate user data packets.

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC