Re: [mpls] should draft-ietf-mpls-spring-entropy-label be published as a RFC on the standards track?

Eric Gray <eric.gray@ericsson.com> Wed, 02 May 2018 18:23 UTC

Return-Path: <eric.gray@ericsson.com>
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 AFB1B12DA01 for <mpls@ietfa.amsl.com>; Wed, 2 May 2018 11:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level:
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 oWaRTz0UGmeK for <mpls@ietfa.amsl.com>; Wed, 2 May 2018 11:23:49 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3BC712DA02 for <mpls@ietf.org>; Wed, 2 May 2018 11:23:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1525285427; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=RNzOl5jyPmgR9uU2GzgNtzUS1dDSIL5Z7r+kfps5jQM=; b=X4GPCldbK0bCR1rzQ5GmNYL0c/uFVYngphqNGi1iT/y4OUPSGNDHfMTWdVFSO8+J 50IXnv76NTWeAkzUR+X80Xwnp50FSNAvCUZixdE9/7LoEEvz3yNqc07mGPWrqQOW kUBZUJ0upOiMnlTfLOLPxacLkjtNk6GU9Q/Ql521Mhk=;
X-AuditID: c6180641-1ebff70000003b41-73-5aea02327c13
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id 62.F9.15169.2320AEA5; Wed, 2 May 2018 20:23:47 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0382.000; Wed, 2 May 2018 14:23:46 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, Loa Andersson <loa@pi.nu>
CC: "mpls@ietf.org" <mpls@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "mpls-ads@ietf.org" <mpls-ads@ietf.org>, "draft-ietf-mpls-spring-entropy-label@ietf.org" <draft-ietf-mpls-spring-entropy-label@ietf.org>
Thread-Topic: [mpls] should draft-ietf-mpls-spring-entropy-label be published as a RFC on the standards track?
Thread-Index: AQHT4el6ZIcVzVRy2kS2hLPPOzbs5qQcqomAgAAU0FA=
Date: Wed, 02 May 2018 18:23:45 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF64BA5FDB4@eusaamb107.ericsson.se>
References: <a3dbc94b-061c-8eb8-7302-3a60f3db4a3f@pi.nu> <CAA=duU3Xc3BvYT1cmVN97vsEYQMsmm6kGqZaibuGOr6QrX42_w@mail.gmail.com>
In-Reply-To: <CAA=duU3Xc3BvYT1cmVN97vsEYQMsmm6kGqZaibuGOr6QrX42_w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.9]
Content-Type: multipart/alternative; boundary="_000_48E1A67CB9CA044EADFEAB87D814BFF64BA5FDB4eusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprPIsWRmVeSWpSXmKPExsUyuXRPrK4x06sog2v/2SxOPz/FZrGtW9ni 39w5zBbrj29isri1dCWrxfELvxkd2Dx2zrrL7rFkyU8mj1nT29gCmKO4bFJSczLLUov07RK4 Mt5vvcpasKqmYu2co2wNjH8quhg5OSQETCS2/+1g7GLk4hASOMoosXrJVTYIZxmjxMLP/Uwg VWwCGhLH7qxlBLFFBFwkjv3tZQIpYha4wShx6cFf5i5GDg5hgXyJlVNNIWoKJHYvecMOYVtJ tB1eBTaHRUBFYt2yHWBzeAV8Ja4sfAdWIyRQL7H82HSwOKdAoMS55j1sIDajgJjE91NrwHqZ BcQlbj2ZzwRxtYDEkj3nmSFsUYmXj/+xQtiKEvv6p7ND1OdLzNmylxVil6DEyZlPWCYwisxC MmoWkrJZSMpmAX3DLKApsX6XPkSJosSU7ofsELaGROucuezI4gsY2VcxcpQWF+TkphsZbmIE RtsxCTbHHYx7ez0PMQpwMCrx8KrfeRklxJpYVlyZe4hRgoNZSYR3ZcezKCHelMTKqtSi/Pii 0pzU4kOM0hwsSuK85zx5o4QE0hNLUrNTUwtSi2CyTBycUg2M3X1bTtp5Ff61E50epf6e922w YU5Ogc28e6+Pq6ssr2uUuLh+WaO6fcZLE8knK40f7J/ufu5WocPsOW7vuO2D9GWWnrypY35D vTEn/4/53sSPS8/bHD/4O7r6RvrHG394f2ue+p1gtvTVj5zCPbfkdp9NkArfGfuiKnxXwSxW p7afIaq98+WKlFiKMxINtZiLihMBiONtqLICAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/3--1MXZ8NZ57NAqZTxLG9n9Q7R0>
Subject: Re: [mpls] should draft-ietf-mpls-spring-entropy-label be published as a RFC on the standards track?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 02 May 2018 18:23:51 -0000

Andy,

                Don’t you feel that this is just a bit of a flip observation?

                Personally I agree that RFC 2119 “language” and even a reference to RFC 2119 itself seems inappropriate in an “FYI” RFC.

                But I have been over-ridden on that before.

                I have to say, however that making something a standards track document _because_ it has RFC 2119 “language” in it is a tad extreme.

                Know another RFC that has a lot of RFC 2119 “language” in it that is not a standards track RFC?  RFC 2119…

                😊

--
Eric

From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Andrew G. Malis
Sent: Wednesday, May 02, 2018 9:01 AM
To: Loa Andersson <loa@pi.nu>
Cc: mpls@ietf.org; spring@ietf.org; mpls-ads@ietf.org; draft-ietf-mpls-spring-entropy-label@ietf.org
Subject: Re: [mpls] should draft-ietf-mpls-spring-entropy-label be published as a RFC on the standards track?

Loa,

There’s plenty of RFC 2119 language in the draft, so I support making this standards track.

Cheers,
Andy


On Wed, May 2, 2018 at 3:44 AM, Loa Andersson <loa@pi.nu<mailto:loa@pi.nu>> wrote:
Working Group,

February 1st the MPLS working Group requested that draft-ietf-mpls-
spring-entropy-label should be published as an Informational RFC.

During the RTG Directorate and AD reviews the question whether the
document should instead be published as a RFC on the Standards Track
has been raised.

The decision to make the document Informational was taken "a long time
ago", based on discussions between the authors and involving the
document shepherd, on the wg mailing list. At that point it we were
convinced that the document should be progressed as an Informational
document.

It turns out that there has been such changes to the document that we
now would like to request input from the working group if we should make
the document a Standards Track RFC.

Daniele's RTG Directorate review can be found at at:
https://datatracker.ietf.org/doc/review-ietf-mpls-spring-entropy-label-08-rtgdir-lc-ceccarelli-2018-02-21/

All the issues, with the exception whether it should be Informational
or Standards track, has been resolved as part AD review.

If the document is progressed as a Standard Tracks document then we
also need to answer the question whether this is an update RFC 6790.

This mail starts a one week poll (ending May 9) to see if we have
support to make the document a Standards Track document. If you support
placing it on the Standards Track also consider if it is an update to
RFC 6790.

Please send your comments to the MPLS wg mailing list ( mpls@ietf.org<mailto:mpls@ietf.org> ).

/Loa
for the mpls wf co-chairs

PS

I'm copying the spring working group on this mail.
--


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

_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls