Re: [mpls] Rtgdir last call review of draft-ietf-mpls-rfc3107bis-02

Stewart Bryant <> Wed, 28 June 2017 13:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B4EAF129B04 for <>; Wed, 28 Jun 2017 06:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id QRNwT1UkYLyy for <>; Wed, 28 Jun 2017 06:25:05 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D55C412EC44 for <>; Wed, 28 Jun 2017 06:25:03 -0700 (PDT)
Received: by with SMTP id b184so58729301wme.1 for <>; Wed, 28 Jun 2017 06:25:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=GaOHiSZhI0FSejZtco/TyhzU7VbkOGNvIq7u5i6axtc=; b=L7h+joh1D+o1UI8tiaiyZjLjy/Ak80aoeyd6W8UhkdBN909fIo/qK0nRf+DuuiBPxD l/Mz1Xx3FroSKgchBnqvWExv7hJl5zZquet6ZCY/qRkbLWyCBDCV4XrPPWDo4z3LV81+ yAGPx3xeRzERFPk4i5vUSlWwjVezo31BKCNf5w5l6M8ZQmKd8P1KejpRtmVuwS0+2jcR zY41vrgkY3GjmuZfcoklXdUQjB+wf3wtzC7AjGeDSdNOyL6DWDZfZBrQs492YXsq4Cfe nWKsF+eRfnpIUk8KnX7sVZj5lCqbMEA1eSsnkMmbyr0I+aGXY+VERG/Rq9fSDblUBG0L HNww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=GaOHiSZhI0FSejZtco/TyhzU7VbkOGNvIq7u5i6axtc=; b=DnrcrJNj2ocwwdfAaLk3sxxqLsAXfz0zlwZ71QGyHhXwjlqzV95QaSfHkJnrfTEp+Z RQaMkd4bOhSj5S0UAAWOlBECSR+xDflEpT8SA90LHAbqaJuF3TwmarQ1P8NfSgbG20Ao xwUuXUuBfZbW+9teFS6V79eBPHdSMNhpcKjs+nWrTGZznSr4uMV/EbFMICKVUIdsoDNt FossrRx0EQOpSzRttahfrQyH+gobc2Wl6wWL+eCuy06i7jr6LauI0KwEirV6zU1InoFQ 5nKnyAnZdxCx6CuPROpN2sd89RBvsI27aPuTU/CC9L18k+cFww1Cm7ZZKyF4FGWVumVf WS5g==
X-Gm-Message-State: AKS2vOxojqyIfREnzkBXv0kPhasiwFajDwOM4bSRu/LT0bHJRoRZhHs5 Dj8WPPzMITODnHij
X-Received: by with SMTP id u3mr7199296wmu.68.1498656302138; Wed, 28 Jun 2017 06:25:02 -0700 (PDT)
Received: from [] ( []) by with ESMTPSA id k75sm8423662wmh.10.2017. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Jun 2017 06:25:01 -0700 (PDT)
To: Eric C Rosen <>,
References: <> <>
From: Stewart Bryant <>
Message-ID: <>
Date: Wed, 28 Jun 2017 14:24:59 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <>
Subject: Re: [mpls] Rtgdir last call review of draft-ietf-mpls-rfc3107bis-02
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 28 Jun 2017 13:25:07 -0000

On 28/06/2017 13:52, Eric C Rosen wrote:
> On 6/27/2017 4:29 PM, Stewart Bryant wrote:
>> In the introduction it says: "In [RFC3107], this feature was 
>> controlled by a
>> BGP Capability Code that has never been implemented, and is now 
>> essentially
>> obsolete." which left me wondering whether there was the intention to 
>> formally
>> deprecate the feature through the RFC system.
> The IANA consideration section of this document requests that the 
> "multiple routes to a destination" capability code be marked as 
> deprecated, with a reference to this document.  Isn't that sufficient?

Hi Eric,

Sorry I missed that.

I am not sure if the same protocol applies to IANA codepoints as RFCs, 
but if you were obsoleting an RFC it would need to be noted in the 
abstract and the introduction.

If you do a respin it might be better to note the deprecation near the 
text on obsolescence, since people tend to read the main text and not 
the IANA section. However at the end of the day it is up to the AD how 
they want to handle this.

- Stewart