[6tsch] Fwd: RFC 7025 on Requirements for GMPLS Applications of PCE

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 18 September 2013 05:27 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: 6tsch@ietfa.amsl.com
Delivered-To: 6tsch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C78C11E810F for <6tsch@ietfa.amsl.com>; Tue, 17 Sep 2013 22:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.873
X-Spam-Level:
X-Spam-Status: No, score=-8.873 tagged_above=-999 required=5 tests=[AWL=-0.575, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_TRNFER=2.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ABKV4oP2QrrR for <6tsch@ietfa.amsl.com>; Tue, 17 Sep 2013 22:27:34 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 281FA11E80FD for <6tsch@ietf.org>; Tue, 17 Sep 2013 22:27:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8982; q=dns/txt; s=iport; t=1379482054; x=1380691654; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=frDVZNVawNZsApoSAYrVoilIHu9ku1v3Lp2033SjuHo=; b=ekaj5gfB3I7s+JEN7o1wzA2kN1B0V+h/IFbAKWQEP1K/k+Hgjt18LX49 eyb7Gs5iw/aC0bD+L+FFTDAep+6Jfrrb5/KAhybJagAPXkPGv3Pwsgpn7 ALG4NSdy3nRLVd1QA4Duoq35efFxeuP/KrZ+vw6Uu3/XWtCNtzi5VR8fZ s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuMGAPg4OVKtJV2d/2dsb2JhbABAGoMHOLk/iEqBGBZtB4ImAQEEAQEBCUI7AgEcEBsHJwoBFAcKAgQTCQsHAgSHYgw2uWyOLYEYERcBgx6BAAOJAI57gS+LDIU5gySBcQ
X-IronPort-AV: E=Sophos; i="4.90,928,1371081600"; d="scan'208,217"; a="261220802"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-6.cisco.com with ESMTP; 18 Sep 2013 05:27:33 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r8I5RXSV029603 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <6tsch@ietf.org>; Wed, 18 Sep 2013 05:27:33 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.197]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Wed, 18 Sep 2013 00:27:33 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "6tsch@ietf.org" <6tsch@ietf.org>
Thread-Topic: RFC 7025 on Requirements for GMPLS Applications of PCE
Thread-Index: AQHOtBVWIXKUbbcKp0SdyHbZBo3MM5nK92Lo
Date: Wed, 18 Sep 2013 05:27:32 +0000
Message-ID: <E3A80AE6-7815-4627-AEED-AACE3FE35FC3@cisco.com>
References: <20130918021110.69A4AB1E011@rfc-editor.org>
In-Reply-To: <20130918021110.69A4AB1E011@rfc-editor.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_E3A80AE678154627AEEDAACE3FE35FC3ciscocom_"
MIME-Version: 1.0
Subject: [6tsch] Fwd: RFC 7025 on Requirements for GMPLS Applications of PCE
X-BeenThere: 6tsch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tsch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tsch>, <mailto:6tsch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6tsch>
List-Post: <mailto:6tsch@ietf.org>
List-Help: <mailto:6tsch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tsch>, <mailto:6tsch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2013 05:27:39 -0000

FYI

Pascal

Début du message transféré :

Expéditeur: <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>>
Date: 18 septembre 2013 04:11:10 UTC+02:00
Destinataire: <ietf-announce@ietf.org<mailto:ietf-announce@ietf.org>>, <rfc-dist@rfc-editor.org<mailto:rfc-dist@rfc-editor.org>>
Cc: <drafts-update-ref@iana.org<mailto:drafts-update-ref@iana.org>>, <pce@ietf.org<mailto:pce@ietf.org>>, <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>>
Objet: RFC 7025 on Requirements for GMPLS Applications of PCE
Répondre à: <ietf@ietf.org<mailto:ietf@ietf.org>>

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


       RFC 7025

       Title:      Requirements for GMPLS Applications of PCE
       Author:     T. Otani, K. Ogaki,
                   D. Caviglia, F. Zhang,
                   C. Margaria
       Status:     Informational
       Stream:     IETF
       Date:       September 2013
       Mailbox:    tm-otani@kddi.com<mailto:tm-otani@kddi.com>,
                   ke-oogaki@kddi.com<mailto:ke-oogaki@kddi.com>,
                   diego.caviglia@ericsson.com<mailto:diego.caviglia@ericsson.com>,
                   zhangfatai@huawei.com<mailto:zhangfatai@huawei.com>,
                   cyril.margaria@coriant.com<mailto:cyril.margaria@coriant.com>
       Pages:      12
       Characters: 26498
       Updates/Obsoletes/SeeAlso:   None

       I-D Tag:    draft-ietf-pce-gmpls-aps-req-09.txt

       URL:        http://www.rfc-editor.org/rfc/rfc7025.txt

The initial effort of the PCE (Path Computation Element) WG focused
mainly on MPLS.  As a next step, this document describes functional
requirements for GMPLS applications of PCE.

This document is a product of the Path Computation Element 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
 http://www.ietf.org/mailman/listinfo/ietf-announce
 http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://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<mailto: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