RFC 8454 on Information Model for Abstraction and Control of TE Networks (ACTN)

rfc-editor@rfc-editor.org Fri, 07 September 2018 00:14 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 9F55E130FB8; Thu, 6 Sep 2018 17:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 pNIQPH8_EqbM; Thu, 6 Sep 2018 17:14:20 -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 2CD79130FA5; Thu, 6 Sep 2018 17:14:20 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 08162B814E9; Thu, 6 Sep 2018 17:14:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg0NTQgb24gSW5mb3JtYXRpb24gTW9kZWwgZm9yIEFic3RyYWN0aW9uIGFuZCBDb250cm9sIG9mIFRFIE5ldHdvcmtzIChBQ1ROKQ==?=
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, teas@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180907001420.08162B814E9@rfc-editor.org>
Date: Thu, 6 Sep 2018 17:14:20 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/oGHTqv4alHQ1bvIQoo3toPKV9sw>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 07 Sep 2018 00:14:28 -0000

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

        
        RFC 8454

        Title:      Information Model for Abstraction and 
                    Control of TE Networks (ACTN) 
        Author:     Y. Lee, 
                    S. Belotti,
                    D. Dhody,
                    D. Ceccarelli,
                    B. Yoon
        Status:     Informational
        Stream:     IETF
        Date:       September 2018
        Mailbox:    leeyoung@huawei.com, 
                    sergio.belotti@nokia.com, 
                    dhruv.ietf@gmail.com,
                    daniele.ceccarelli@ericsson.com, 
                    byyun@etri.re.kr
        Pages:      23
        Characters: 39983
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-teas-actn-info-model-10.txt

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

        DOI:        10.17487/RFC8454

This document provides an information model for Abstraction and
Control of TE Networks (ACTN).

This document is a product of the Traffic Engineering Architecture and Signaling 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