RFC 8134 on Management Incident Lightweight Exchange (MILE) Implementation Report

rfc-editor@rfc-editor.org Wed, 17 May 2017 19:43 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85E7D1274D2; Wed, 17 May 2017 12:43:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.304
X-Spam-Level:
X-Spam-Status: No, score=-2.304 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 iJCCt67LdKFf; Wed, 17 May 2017 12:43:00 -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 97FE5127868; Wed, 17 May 2017 12:41:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A3365B80CB0; Wed, 17 May 2017 12:41:30 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8134 on Management Incident Lightweight Exchange (MILE) Implementation Report
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, mile@ietf.org
Message-Id: <20170517194130.A3365B80CB0@rfc-editor.org>
Date: Wed, 17 May 2017 12:41:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/RgYmZfAALprWWPzlwRa2EU2PL78>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 May 2017 19:43:04 -0000

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

        
        RFC 8134

        Title:      Management Incident Lightweight Exchange (MILE) 
                    Implementation Report 
        Author:     C. Inacio, D. Miyamoto
        Status:     Informational
        Stream:     IETF
        Date:       May 2017
        Mailbox:    inacio@andrew.cmu.edu, 
                    daisu-mi@nc.u-tokyo.ac.jp
        Pages:      16
        Characters: 36004
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mile-implementreport-10.txt

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

        DOI:        10.17487/RFC8134

This document is a collection of implementation reports from vendors,
consortiums, and researchers who have implemented one or more of the
standards published from the IETF INCident Handling (INCH) and
Management Incident Lightweight Exchange (MILE) working groups.

This document is a product of the Managed Incident Lightweight Exchange 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