Re: [mpls] should draft-ietf-mpls-spring-entropy-label be published as a RFC on the standards track?
"Andrew G. Malis" <agmalis@gmail.com> Wed, 02 May 2018 13:01 UTC
Return-Path: <agmalis@gmail.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 2AC76126DCA; Wed, 2 May 2018 06:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 rZBxSBBY8gg4; Wed, 2 May 2018 06:01:37 -0700 (PDT)
Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::22a]) (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 F4158126D05; Wed, 2 May 2018 06:01:36 -0700 (PDT)
Received: by mail-ot0-x22a.google.com with SMTP id l22-v6so16461880otj.0; Wed, 02 May 2018 06:01:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=n5rwujTtKbJc2Z5KeLwX4a9h57ROX+ENVte/odneXdA=; b=jVfHKWKUhipK4PRSnlbhxkpJW3B7bQG0p+TdfRKoUXS3pbdRbWGI3XKxm36okvqWCx diMYZAQ/smLZkKo6b/j1OEe8i+QT9OMfTeWJCmHYM+RTcEgZzT2NUJ4Dpx3rpfuRnxPz qJhwLuIo1lX9tyvwjF8tD40xqil9jzPBNIcV2T/aLbWO9MRAtAXcTc6J6THQ0XOTURpm npMwAYU6W3DE1S6DZz4NwTc9a85Uq/bdl6vmy1np387HS+3gdyTjsyY2tvjFzBourGVC 3Ro+dtFbAvFhDUZQJDW7SLvABGGxvl/USNcoLMDM6l80BbAjMtBP8ZbIDmFJZMJANs2w foJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=n5rwujTtKbJc2Z5KeLwX4a9h57ROX+ENVte/odneXdA=; b=lW6fc1gOXf2TYShRvlWcxRHFMuJo3l1ZoHccn4Vq1fy626Q7fajL/mQZGtESqEYfUx seS0QqFg8fegDlJolrKEs7Hra+UjIp2mKtffTITbtJguOy2pB225G+AOAPZCMdDZk8kD ujaf0YZtzBoYIu0ld/AoDSJFjbIV+jjxN0M9STwQ4eBcVd7YJgCDqklakH2zSqWYbUf3 PFEa2x3Y02boKDN3s/Vh6NjwJ+hZ7ee/T0ossLj0Q7r1huKffCPEeOGMOhjbuvKbSFWW mJ3FWit9zpkGiFoI6MU4vQfCY/pFYbsW/zl+dK04dQ714Wf1XjP1uD5qPIE/h73SjU8Q D5MQ==
X-Gm-Message-State: ALQs6tAMO83Z1IrBDsV9RmwBI6hGVwbuw2iGdfW2RYWsBnKAkf6kylXF HbDg/q5eYYk/tgJulDlPjXlqkKo7euql/g75m6E=
X-Google-Smtp-Source: AB8JxZrvqgtCkcXUsKD073SxLiPsfy84g5wUIR1x+SIt/ukxquurc+suuSMV6XOyq8IU6Ga9lwiAjJEqmFZz3idA7SU=
X-Received: by 2002:a9d:26e2:: with SMTP id i31-v6mr12828039otd.27.1525266095629; Wed, 02 May 2018 06:01:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:1f27:0:0:0:0:0 with HTTP; Wed, 2 May 2018 06:01:15 -0700 (PDT)
In-Reply-To: <a3dbc94b-061c-8eb8-7302-3a60f3db4a3f@pi.nu>
References: <a3dbc94b-061c-8eb8-7302-3a60f3db4a3f@pi.nu>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 02 May 2018 09:01:15 -0400
Message-ID: <CAA=duU3Xc3BvYT1cmVN97vsEYQMsmm6kGqZaibuGOr6QrX42_w@mail.gmail.com>
To: 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>
Content-Type: multipart/alternative; boundary="000000000000d169ad056b38af9f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/CZJbTwbQzRBkNTJwaZF5hC2Q7oo>
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 13:01:39 -0000
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> 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-ent > ropy-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 ). > > /Loa > for the mpls wf co-chairs > > PS > > I'm copying the spring working group on this mail. > -- > > > Loa Andersson email: loa@pi.nu > Senior MPLS Expert > Bronze Dragon Consulting phone: +46 739 81 21 64 > > _______________________________________________ > mpls mailing list > mpls@ietf.org > https://www.ietf.org/mailman/listinfo/mpls >
- [mpls] should draft-ietf-mpls-spring-entropy-labe… Loa Andersson
- Re: [mpls] should draft-ietf-mpls-spring-entropy-… Andrew G. Malis
- Re: [mpls] [spring] should draft-ietf-mpls-spring… Alexander Vainshtein
- Re: [mpls] [spring] should draft-ietf-mpls-spring… Stewart Bryant
- Re: [mpls] [spring] should draft-ietf-mpls-spring… Eric Gray
- Re: [mpls] [spring] should draft-ietf-mpls-spring… Eric Gray
- Re: [mpls] [spring] should draft-ietf-mpls-spring… Loa Andersson
- Re: [mpls] [spring] should draft-ietf-mpls-spring… John E Drake
- Re: [mpls] [spring] should draft-ietf-mpls-spring… Rob Shakir
- Re: [mpls] [spring] should draft-ietf-mpls-spring… Stewart Bryant
- Re: [mpls] should draft-ietf-mpls-spring-entropy-… Eric Gray
- Re: [mpls] should draft-ietf-mpls-spring-entropy-… Andrew G. Malis
- [mpls] Closed: should draft-ietf-mpls-spring-entr… Loa Andersson