Re: [mpls] Last Call: <draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt> (LabelSwitched Path (LSP) Ping for IPv6 Pseudowire FECs) toProposed Standard

t.p. <daedulus@btconnect.com> Fri, 02 November 2012 18:07 UTC

Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE5891F0C5C for <ietf@ietfa.amsl.com>; Fri, 2 Nov 2012 11:07:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fxt71TnogdIj for <ietf@ietfa.amsl.com>; Fri, 2 Nov 2012 11:07:12 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe003.messaging.microsoft.com [216.32.180.13]) by ietfa.amsl.com (Postfix) with ESMTP id E1D7B21F8858 for <ietf@ietf.org>; Fri, 2 Nov 2012 11:07:11 -0700 (PDT)
Received: from mail216-va3-R.bigfish.com (10.7.14.249) by VA3EHSOBE004.bigfish.com (10.7.40.24) with Microsoft SMTP Server id 14.1.225.23; Fri, 2 Nov 2012 18:07:10 +0000
Received: from mail216-va3 (localhost [127.0.0.1]) by mail216-va3-R.bigfish.com (Postfix) with ESMTP id 22A9B8402A5 for <ietf@ietf.org>; Fri, 2 Nov 2012 18:07:10 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.197; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0710HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zz9371I936eI542M1432Izz1de0h1202h1d1ah1d2ahzz1033IL17326ah8275dhz2dh2a8h5a9h668h839hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h304l1155h)
Received: from mail216-va3 (localhost.localdomain [127.0.0.1]) by mail216-va3 (MessageSwitch) id 1351879627361084_27597; Fri, 2 Nov 2012 18:07:07 +0000 (UTC)
Received: from VA3EHSMHS027.bigfish.com (unknown [10.7.14.251]) by mail216-va3.bigfish.com (Postfix) with ESMTP id 4B777180053 for <ietf@ietf.org>; Fri, 2 Nov 2012 18:07:07 +0000 (UTC)
Received: from DBXPRD0710HT005.eurprd07.prod.outlook.com (157.56.253.197) by VA3EHSMHS027.bigfish.com (10.7.99.37) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 2 Nov 2012 18:07:02 +0000
Received: from AMSPRD0510HT004.eurprd05.prod.outlook.com (157.56.248.53) by pod51017.outlook.com (10.255.79.168) with Microsoft SMTP Server (TLS) id 14.16.233.3; Fri, 2 Nov 2012 18:06:39 +0000
Message-ID: <028101cdb924$b77260a0$4001a8c0@gateway.2wire.net>
From: "t.p." <daedulus@btconnect.com>
To: ietf@ietf.org
References: <20121024213116.29724.2375.idtracker@ietfa.amsl.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt> (LabelSwitched Path (LSP) Ping for IPv6 Pseudowire FECs) toProposed Standard
Date: Fri, 02 Nov 2012 18:05:53 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.248.53]
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 18:07:12 -0000

I worry about the allocation of sub-TLVs in this I-D.

It calls for
"The following Sub-TLV changes, which comprise three updates and two
   additions, are made for two TLV Types in the aforementioned sub-
   registry: TLV Type 1 for "Target FEC Stack", and TLV Type 21 for
   "Reply Path"."
and it is the Type 21 that worries me.

IANA has, for Type 21,

Reply Path (TEMPORARY - expires 2012-01-20)
[draft-ietf-mpls-return-path-specified-lsp-ping]

and I am unclear what the rules are about updates to expired, TEMPORARY,
allocations.

I worry too that
[draft-ietf-mpls-return-path-specified-lsp-ping]
while confirming the reservation of Type 21 takes a different tack for
sub-TLVs, namely
"
According to the guidelines defined in [RFC5226], the sub-TLV range
   of Reply Path TLV are partitioned as following:
   0-31743 - Reserved, and MUST NOT be allocated."
so quite what this I-D will do to that I-D worries me.

And I worry yet more that other I-Ds, such as
draft-zjns-mpls-lsp-ping-relay-reply-00
are heading down the track with further updates in this area of the MPLS
namespace (except that this particular one seems to have abandoned
sub-TLVs).

Tom Petch

----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: <mpls@ietf.org>
Sent: Wednesday, October 24, 2012 9:31 PM

>
> The IESG has received a request from the Multiprotocol Label Switching
WG
> (mpls) to consider the following document:
> - 'Label Switched Path (LSP) Ping for IPv6 Pseudowire FECs'
>   <draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt> as Proposed Standard
>
> 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
> ietf@ietf.org mailing lists by 2012-11-09. Exceptionally, comments may
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>    Multi-Protocol Label Switching (MPLS) Label Switched Path (LSP)
Ping
>    and traceroute mechanisms are commonly used to detect and isolate
>    data plane failures in all MPLS LSPs including Pseudowire (PW)
LSPs.
>    The PW LSP Ping and traceroute elements, however, are not specified
>    for IPv6 address usage.
>
>    This document extends the PW LSP Ping and traceroute mechanisms so
>    they can be used with IPv6 PWs, and updates RFC 4379.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-ipv6-pw-lsp-ping/
>
> IESG discussion can be tracked via
>
http://datatracker.ietf.org/doc/draft-ietf-mpls-ipv6-pw-lsp-ping/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>