IETF Logo Mail Archive

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

Stewart Bryant <stewart@g3ysx.org.uk> Wed, 28 June 2017 13:25 UTC

Return-Path: <stewart@g3ysx.org.uk>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8BCE12EC42 for <rtg-dir@ietfa.amsl.com>; Wed, 28 Jun 2017 06:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=g3ysx-org-uk.20150623.gappssmtp.com
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 ulARciyC0FjA for <rtg-dir@ietfa.amsl.com>; Wed, 28 Jun 2017 06:25:04 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C48EC12EC40 for <rtg-dir@ietf.org>; Wed, 28 Jun 2017 06:25:03 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id i127so58832065wma.0 for <rtg-dir@ietf.org>; Wed, 28 Jun 2017 06:25:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=g3ysx-org-uk.20150623.gappssmtp.com; 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; d=1e100.net; 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=fEWyGqH0G8G7+crkBgPcCAVaPl0W5vLxmdN2DkEONJqzcvYfcc5nx9kDUD8aEQ6Zga rfA9iyADmur0Ya2AIclZpfV/9p1P7FTlFtqURCK76FhiWcOtWnEkny8BpaNj8iuNTK2I DL6Ttm5EJVp/Pw9FSPh5OZEuz4V9wB5OesufMg1FZAzAd6u7Eo/rKur+DKXcZs2PCAHz 7mgQfBReAoz6kDEsRtfpV2b7n2jlM9zlsHFHpIeEsR5ELQgNFtKPcP5WG2uEmfBmDUAR mMVxLrAS/aQ5y/K27TnZmM01aVKi89fQnV1G5HgWPtoAGbzqYMmAB+kXBpteu0MK2dnU eNaw==
X-Gm-Message-State: AKS2vOy8W+L5KgnlwRYi3Hpc5M1e3EQqDi+SR6HrduvSyZmrkmpYml4z exe5MA9JQbzjfJ53wUNRcw==
X-Received: by 10.28.46.3 with SMTP id u3mr7199296wmu.68.1498656302138; Wed, 28 Jun 2017 06:25:02 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id k75sm8423662wmh.10.2017.06.28.06.25.01 (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 <erosen@juniper.net>, rtg-dir@ietf.org
Cc: mpls@ietf.org, draft-ietf-mpls-rfc3107bis.all@ietf.org, ietf@ietf.org
References: <149859539754.31085.2059230421371020521@ietfa.amsl.com> <3c405108-c18f-8f1b-b9e7-25d08157e1ee@juniper.net>
From: Stewart Bryant <stewart@g3ysx.org.uk>
Message-ID: <4f25a6b2-a912-ce02-819c-73c3b4ba9ced@g3ysx.org.uk>
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: <3c405108-c18f-8f1b-b9e7-25d08157e1ee@juniper.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/d9equiU16U5LtvmXmNrHvWUUb2A>
Subject: Re: [RTG-DIR] Rtgdir last call review of draft-ietf-mpls-rfc3107bis-02
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=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

v2.23.0 | Report a Bug | By Email