[mpls] New version of Bundling Draft
Yakov Rekhter <yakov@juniper.net> Mon, 22 November 2004 19:46 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07678; Mon, 22 Nov 2004 14:46:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWKCP-0000zs-Mb; Mon, 22 Nov 2004 14:50:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWK6g-0006kt-1i; Mon, 22 Nov 2004 14:44:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWK1y-0005sD-PU for mpls@megatron.ietf.org; Mon, 22 Nov 2004 14:39:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06775 for <mpls@ietf.org>; Mon, 22 Nov 2004 14:39:21 -0500 (EST)
Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWK5U-0008Q5-Dq for mpls@ietf.org; Mon, 22 Nov 2004 14:43:00 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id iAMJcoBm029502; Mon, 22 Nov 2004 11:38:50 -0800 (PST) (envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id iAMJcoe91197; Mon, 22 Nov 2004 11:38:50 -0800 (PST) (envelope-from yakov@juniper.net)
Message-Id: <200411221938.iAMJcoe91197@merlot.juniper.net>
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: [mpls] New version of Bundling Draft
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <94734.1101152330.1@juniper.net>
Date: Mon, 22 Nov 2004 11:38:50 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: ccamp@ops.ietf.org, mpls@ietf.org, lberger@movaz.com
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Adrian,
> Thank you for the new version of this draft. I assume that the
> changes are to address the issues raised at the MPLS WG meeting in
> Washington.
>
> Since the draft was already through WG and IETF last call, I wonder
> if you would be kind enough to summarize the issues you were
> addressing and what changes you made to the draft.
Here is the summary:
draft-ietf-mpls-bundle-05.txt has been updated to reflect the comments made
in the MPLS WG and on the list. The issues raised are:
1. Scope of component identifiers is open to interpretation (i.e., node vs
link)
2. No way to specify different upstream and downstream components then
using TLV types 1, 2 and 3
3. Ambiguity of contents of the IP address field in TLV types 3, 4, 5
4. Lack of IPv6 support for types 3, 4, and 5.
5. Ambiguity of when to use types 4 and 5 and when to use type 3.
6. No coverage of ERO and RRO implications
These issues have been addressed in the following ways:
Issue 1: The -05 document states that all component link TLV types
have Node/IP scope
Issue 2: -05 Tightly defines support for different components in each
direction (for bidirectional LSPs, and for all TLV types)
Issue 3: Format of the Value field for types 3, 4 and 5 now has the
identical format as the contents of the C-Type 1
LSP_TUNNEL_INTERFACE_ID object defined in [RFC3477].
Issue 4: Based on the previous change, support of IPv6 unnumbered
components is now tied to, and the same as, the support of
IPv6 unnumber TE links.
Issue 5: -05 allows, but recommend against use of types 4 and 5
Issue 6: EROs, RROs remain out of scope of bundling document
Current planned changes are:
- Fix nits found by Adrian and Loa
- Insert a Table of Contents
- Section numbering will remain unchanged so as not to break any
potentially existing references to the draft
Yakov.
_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls
- [mpls] New version of Bundling Draft Adrian Farrel
- [mpls] Re: New version of Bundling Draft Lou Berger
- [mpls] New version of Bundling Draft Yakov Rekhter