The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2006-Nov> msg00084



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

[mpls] Fwd: I-D ACTION:draft-vasseur-mpls-3209-patherr-00.txt

  • From: JP Vasseur <jvasseur@cisco.com>
  • Date: Tue, 14 Nov 2006 09:06:51 -0500
  • Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass (sig from cisco.com/rtpdkim1001 verified; );
  • DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=22943; t=1163513215;x=1164377215; c=relaxed/simple; s=rtpdkim1001;h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;d=cisco.com; i=jvasseur@cisco.com;z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>|Subject:=20Fwd=3A=20I-D=20ACTION=3Adraft-vasseur-mpls-3209-patherr-00.txt=20 |Sender:=20 |To:=20mpls@ietf.org;bh=qvyObqXCLEJw2N+0fHqYjUY+/d1H2Uq5yMFOr277+lA=;b=iLokK8EC8O3KSUXHcl89ZDAQXEaa1Ciz28T0PINtu0HxOwfpzY5zWs9hZbEYA6WJEr+RNk+qIOXcYxjzcA8EskAoKYSbCpy0zLd+HKkCLfP5xO6rTDkxS1GG2+LSVl5k;
  • X-OriginalArrivalTime: 14 Nov 2006 14:06:53.0758 (UTC)FILETIME=[233825E0:01C707F6]

Hi,

As discussed last week, there's a need to document this behavior, implementor's feed-back is more than welcome on this ID.

Thanks.

JP.

Begin forwarded message:

From: JP Vasseur <jvasseur@cisco.com>
Date: September 13, 2006 6:01:12 PM EDT
Cc: Adrian Farrel <adrian@olddog.co.uk>, George Swallow <swallow@cisco.com>, Loa Andersson <loa@pi.se>
Subject: Fwd: I-D ACTION:draft-vasseur-mpls-3209-patherr-00.txt 

Dear WG members,

Some of you might recall the in-depth discussion that we had some time ago wrt to Soft Preemption. I think that we got a pretty clear consensus on the proposed solution. There was still a remaining issue related to the definition of "Hard Preemption" used in the ID. More precisely, some of you required clarifications on RFC3209 with regards to the behavior of a node upon the reception of a Path Error. Thus we have produced this ID, the aim of which is simply to clarify this aspect, thus hopping to be able to move forward on the Soft Preemption ID (of course, we will produce a new revision of the Soft Preemption ID referring to this new ID, once we'll get a consensus).

Thanks.

JP, Adrian and George.

Begin forwarded message:

Date: September 10, 2006 3:50:01 PM EDT
Subject: I-D ACTION:draft-vasseur-mpls-3209-patherr-00.txt 

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.


Title : Node behavior upon originating and receiving 
                          Resource ReserVation Protocol (RSVP) Path Error message
Author(s) : J. Vasseur, et al.
Filename : draft-vasseur-mpls-3209-patherr-00.txt
Pages : 8
Date : 2006-9-10

The aim of this document is to describe a common practice with regard
to the behavior of a node sending a Resource ReserVation Protocol
(RSVP) Path Error message and to the behavior of a node receiving an
RSVP Path Error message for a particular Multi-Protocol Label
Switching - Traffic Engineering (MPLS-TE) Label Switched Path (LSP).
This text does not define any new protocol extensions.


A URL for this Internet-Draft is:

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-vasseur-mpls-3209-patherr-00.txt".

A list of Internet-Drafts directories can be found in

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
"FILE /internet-drafts/draft-vasseur-mpls-3209-patherr-00.txt".

NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility.  To use this
feature, insert the command "ENCODING mime" before the "FILE"
command.  To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader.  Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Content-Type: text/plain

_______________________________________________
I-D-Announce mailing list


_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls