Last Call: <draft-kumaki-murai-l3vpn-rsvp-te-06.txt> (Support for RSVP-TE in L3VPNs) to Experimental RFC

The IESG <> Wed, 05 September 2012 22:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 451EB21F86EF for <>; Wed, 5 Sep 2012 15:43:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.245
X-Spam-Status: No, score=-102.245 tagged_above=-999 required=5 tests=[AWL=-0.246, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id slJ7t7Fh2cr8 for <>; Wed, 5 Sep 2012 15:43:57 -0700 (PDT)
Received: from (localhost []) by (Postfix) with ESMTP id D8FD921F86B7 for <>; Wed, 5 Sep 2012 15:43:57 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-kumaki-murai-l3vpn-rsvp-te-06.txt> (Support for RSVP-TE in L3VPNs) to Experimental RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <>
Date: Wed, 05 Sep 2012 15:43:57 -0700
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 05 Sep 2012 22:43:58 -0000

The IESG has received a request from an individual submitter to consider
the following document:
- 'Support for RSVP-TE in L3VPNs'
  <draft-kumaki-murai-l3vpn-rsvp-te-06.txt> as Experimental RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2012-10-03. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   IP Virtual Private Networks (VPNs) provide connectivity between sites
   across an IP/MPLS backbone. These VPNs can be operated using BGP/MPLS
   and a single provider edge (PE) node may provide access to multiple
   customer sites belonging to different VPNs.

   The VPNs may support a number of customer services including RSVP and
   RSVP-TE traffic. This document describes how to support RSVP-TE
   between customer sites when a single PE supports multiple VPNs.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.

Due to an error by the sponsoring Area Director, the Last Call on 
this document (which completed on 3rd September) incorrectly 
stated that this draft was intended that it be published as Informational.
The correct intention (as stated in the draft itself) is that it  be 
published as Experimental. 

This Last Call is to verify community consensus for publication of
this draft as Experimental.