RFC 7547 on Management of Networks with Constrained Devices: Problem Statement and Requirements

rfc-editor@rfc-editor.org Wed, 13 May 2015 22:56 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 357DA1B31A6; Wed, 13 May 2015 15:56:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 SGWK0hyHGkav; Wed, 13 May 2015 15:56:51 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 266D31B31A2; Wed, 13 May 2015 15:56:51 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7B9CA180452; Wed, 13 May 2015 15:55:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7547 on Management of Networks with Constrained Devices: Problem Statement and Requirements
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150513225504.7B9CA180452@rfc-editor.org>
Date: Wed, 13 May 2015 15:55:04 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/-zmkkvBmsE1p_LmFr4zjjpfw_tw>
Cc: opsawg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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, 13 May 2015 22:56:53 -0000

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

        
        RFC 7547

        Title:      Management of Networks with Constrained
                    Devices: Problem Statement and Requirements 
        Author:     M. Ersue, Ed.,
                    D. Romascanu,
                    J. Schoenwaelder,
                    U. Herberg
        Status:     Informational
        Stream:     IETF
        Date:       May 2015
        Mailbox:    mehmet.ersue@nsn.com, 
                    dromasca@avaya.com, 
                    j.schoenwaelder@jacobs-university.de,
                    ulrich@herberg.name
        Pages:      44
        Characters: 87357
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opsawg-coman-probstate-reqs-05.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7547

This document provides a problem statement, deployment and management
topology options, as well as requirements addressing the different
use cases of the management of networks where constrained devices are
involved.

This document is a product of the Operations and Management Area Working Group 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/rfc.html

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