Subject: [mpls] FW: New Version Notification for draft-manral-mpls-rfc3811bis-03.txt

From: "Will Liu (Shucheng)" <[email-masked]>
Date: Fri, 28 Jun 2013 04:58:20 +0000

Hi Folks,

We uploaded a new version to address the comments about MplsLSPID description as below. We are looking forward to your further comments. Thanks.

Cheers,
Will

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: Friday, June 28, 2013 12:54 PM
To: Tina TSOU; Will Liu (Shucheng); Francesco Fondelli; Vishwas Manral; Will Liu (Shucheng)
Subject: New Version Notification for draft-manral-mpls-rfc3811bis-03.txt

A new version of I-D, draft-manral-mpls-rfc3811bis-03.txt
has been successfully submitted by Vishwas Manral and posted to the
IETF repository.

Filename:	 draft-manral-mpls-rfc3811bis
Revision:	 03
Title:		 Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management
Creation date:	 2013-06-28
Group:		 Individual Submission
Number of pages: 22
URL:             http://www.ietf.org/internet-drafts/draft-manral-mpls-rfc3811bis-03.txt
Status:          http://datatracker.ietf.org/doc/draft-manral-mpls-rfc3811bis
Htmlized:        http://tools.ietf.org/html/draft-manral-mpls-rfc3811bis-03
Diff:            http://www.ietf.org/rfcdiff?url2=draft-manral-mpls-rfc3811bis-03

Abstract:
   This memo defines a Management Information Base (MIB) module which
   contains Textual Conventions to represent commonly used Multiprotocol
   Label Switching (MPLS) management information.  The intent is that
   these TEXTUAL CONVENTIONS (TCs) will be imported and used in MPLS
   related MIB modules that would otherwise define their own
   representations.

   This document obsoletes RFC3811 as it addresses the need to support
   IPv6 extended TunnelID's by defining a new TC-
   MplsNewExtendedTunnelID which suggests using IPv4 address of the
   ingress or egress LSR for the tunnel for an IPv6 network.  Changes
   from RFC3811 and the effect of the new TC to other related documents
   are summarized in Section 4 and 5, respectively.

The IETF Secretariat