Re: [mpls] draft-andersson-mpls-lsp-ping-registries-update-01 - Updating the LSP Ping IANA registries

Loa Andersson <loa@pi.nu> Fri, 16 August 2019 11:11 UTC

Return-Path: <loa@pi.nu>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB97012008A; Fri, 16 Aug 2019 04:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F-iC24PgSlF4; Fri, 16 Aug 2019 04:10:59 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 824CA120018; Fri, 16 Aug 2019 04:10:59 -0700 (PDT)
Received: from [192.168.0.101] (81-236-221-251-no93.tbcn.telia.com [81.236.221.251]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 69F7E363205; Fri, 16 Aug 2019 13:10:57 +0200 (CEST)
To: Carlos Pignataro <cpignata@gmail.com>
Cc: draft-andersson-mpls-lsp-ping-registries-update@ietf.org, mpls <mpls@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
References: <21011742-C1D6-4F64-852A-4C399139B840@gmail.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <cda5c3c8-5e9e-21ba-6062-fc00a841e52b@pi.nu>
Date: Fri, 16 Aug 2019 13:10:56 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <21011742-C1D6-4F64-852A-4C399139B840@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/04V38zoYZRqe_9iyeT58_kUqhmg>
Subject: Re: [mpls] draft-andersson-mpls-lsp-ping-registries-update-01 - Updating the LSP Ping IANA registries
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2019 11:11:02 -0000

Folks, (adding Adrian as Shepherd),

It has take me a long tiime to start updating the draft according to the
much appreciated comments from Carlos and Adrian.

I have a question on one of the comments from Carlos:

On 2019-08-06 22:14, Carlos Pignataro wrote:
> 
> 
>     [RFC8611]  Akiya, N., Swallow, G., Litkowski, S., Decraene, B.,
>                Drake, J., and M. Chen, "Label Switched Path (LSP) Ping
>                and Traceroute Multipath Support for Link Aggregation
>                Group (LAG) Interfaces", RFC 8611, DOI 10.17487/RFC8611,
>                June 2019, <https://www.rfc-editor.org/info/rfc8611>.
> 
> 
> CMP: This should be Informative.

Adrain comment on updating RFC 8611 (his suggested text for Section 1):

NEW
    When RFC 8029 [RFC8029] where published it contained among other
    things updates to the "Multiprotocol Label Switching (MPLS) Label
    Switched Paths (LSPs) Ping Parameters" IANA name space
    [IANA-LSP-PING].

    RFC 8126 [RFC8126] updated the LSP Ping IANA registries to match
    RFC 8029, but there were still some ambiguities, that were
    reflected in the registries.

    This document updates [RFC8029] and [RFC8126] by updating two
    groups of registries.
END

So we are updating RFC 8611, and the text that we add/change will be
normative, does thai not make RFC 8611 a normative refrenece?

/Loa



-- 


Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert
Bronze Dragon Consulting             phone: +46 739 81 21 64