Re: [lisp] Move RFC7954 and RFC7955 to HISTORIC

Luigi Iannone <ggx@gigix.net> Thu, 28 November 2019 11:34 UTC

Return-Path: <ggx@gigix.net>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04F77120812 for <lisp@ietfa.amsl.com>; Thu, 28 Nov 2019 03:34:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gigix-net.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 EYrHoloSJRr2 for <lisp@ietfa.amsl.com>; Thu, 28 Nov 2019 03:34:16 -0800 (PST)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 53CDD120819 for <lisp@ietf.org>; Thu, 28 Nov 2019 03:34:13 -0800 (PST)
Received: by mail-wm1-x329.google.com with SMTP id l1so10605218wme.2 for <lisp@ietf.org>; Thu, 28 Nov 2019 03:34:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=irY6aq5VcuYJWkNm2pFLnj4/ksMjURdkvv5GqNVTYHM=; b=Pbls6voOEV2dlahgfQuryYZcd/qPQYUwwHFdF5Pp2ZZe9BXjX/1KQbpI76tBwYNFpw 4DF1pbBGDKoYhD03Kk7OPXdRZEnbF3lkMK3kcMBV9MR6tOwtMVT+F4zPftIjvuckCLK/ PrezQEGbO8M8cHIUvq0sJCFg30gnK7wC0BJt1I1e6ize22Ym9On8yzZ3viW02sycrS0I /Bek4zwv+OIt9h4YbH4Tb30+d158can2oh7J5pCpaoXBBTQBMYJpLhfUMtuYd/UJ690J Pq+RzBJHqduXwg1BRMnGfIc59nAUchhtvyIl6XnfBOUttm2i6LF4v+nNigsqPayPdFyG YStg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=irY6aq5VcuYJWkNm2pFLnj4/ksMjURdkvv5GqNVTYHM=; b=XVTX2YDtQjYths0dXWTfOvSswzbVJivAcEx+YoDADnIs+HycAHcHbHE2Ze/CUtro4y PL4LlSv4bo2Td5VVFLBD9NTdnCND4+0YnTOpE1DL6UnzpgSBnm7Rs660nXidbttsd9Lt 6gZyBUY/bSpF1hTtQCMEWZ2IlkgzN//YlaR64cGoolyv2GEk5dfk52FC5snMqzkNa0Qu Ggy5Xfk4Ae64GYqcw7dLiZHt5Odb4ciEXR1/ISXLPRjnwIjymj9cvym+pT8VIJVxx2um pwJdKsqnbKZzI38A8pDfpoOaDzTtjh9NsJA74oHWqZnPhWhuRO2lykSdNlGCb3KR4zb1 Dv2g==
X-Gm-Message-State: APjAAAX0yYDJwOhvmWUuudIF1ALpOorPSHWCoerJyejXNTXrvDhhFDhb y42D1VmqFCPhRZydAzniCV6mZj1Jq1s=
X-Google-Smtp-Source: APXvYqzyAUHWdvtncHUGB3hTBToL72rbe9AbSqXvV67fM48GM3Yp87Z+JV9ycJAPGM3kmVqb0mBXXg==
X-Received: by 2002:a05:600c:24ce:: with SMTP id 14mr8545838wmu.122.1574940851124; Thu, 28 Nov 2019 03:34:11 -0800 (PST)
Received: from ?IPv6:2a04:8ec0:0:176:b10c:65ca:ea3c:45dd? ([2a04:8ec0:0:176:b10c:65ca:ea3c:45dd]) by smtp.gmail.com with ESMTPSA id v14sm22862747wrm.28.2019.11.28.03.34.09 for <lisp@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Nov 2019 03:34:09 -0800 (PST)
From: Luigi Iannone <ggx@gigix.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_65F2E7E2-B13E-48E4-950B-480F75BE71AB"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Date: Thu, 28 Nov 2019 12:34:08 +0100
References: <BAA76C55-E0D9-4267-A694-7E7947963D24@gigix.net>
To: lisp@ietf.org
In-Reply-To: <BAA76C55-E0D9-4267-A694-7E7947963D24@gigix.net>
Message-Id: <C40AF569-CFEB-4DC1-B9AC-A06E60507ECE@gigix.net>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/x8tEHiLZauNcwNAiXyOFA3FSmAo>
Subject: Re: [lisp] Move RFC7954 and RFC7955 to HISTORIC
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2019 11:34:19 -0000

All,

no objections have been received.

We will move forward and ask to put these two documents in HISTORIC state.

Thanks

Ciao

L.


> On 20 Nov 2019, at 03:43, Luigi Iannone <ggx@gigix.net> wrote:
> 
> Folks,
> 
> as discussed yesterday during the f2f meeting, we plan to move RFC7954 and RFC7955 to HISTORIC state.
> 
> Rationale is described in the text provide below. This text will be associated to the documents so to keep track of the LISP EID prefix experiment.
> 
> Please let us know if you have any comment.
> 
> We plan to move forward in one week time.
> 
> Thanks
> 
> Ciao
> 
> L.
>  
> 
> 
> 
> 
> —————————————— PROPOSED TEXT———————————————
> 
> RFC 7954 created an experimental IPv6 prefix, namely 2001:5::/32, to be used as Endpoint-IDentifier (EID) space for the Locator/Identifier Separation Protocol (LISP).  The reserved address space was requested for an initial 3-year period
> starting in September 2016 (until September 2019), with an option to extend it by three years (until September 2022) upon the decision of the IETF.
> RFC 7955 describes a framework for the management of the prefix crested by RFC 7954. As described in RFC 7955, RIPE NCC volunteered to provide registration service during the experiment (up to 2022 at latest).
> 
> The initial experiment was supposed to last three years, until September 2019.
> The option to extend the experiment to three more years was subject to the requirements written in section 10 of RFC 7954:
> 
>  Following the policies outlined in
>   [RFC5226], upon IETF Review, the decision should be made on whether
>   to have a permanent EID block assignment by September 2019.  If no
>   explicit action is taken or, if the IETF Review outcome is that it is
>   not worth having a reserved prefix as a global EID space, the whole
>   /32 will be taken out from the "IANA IPv6 Special-Purpose Address
>   Registry" and put back in the free pool managed by IANA.
> 
> In August 2019 RIPE NCC contacted the LISP WG asking if any action was ongoing concerning the extension of the experiment. The LISP WG concluded that very few requests have been made during three years and there was no compelling reason to extent the experiment. No further action has been taken by the LISP WG or the IETF. As such, in accordance with Section 10 of RFC 7954, RIPE NCC de-registered the existing assignments and IANA put the prefix back in the free pool (removing the entry from https://www.iana.org/assignments/iana-ipv6-special-registry <https://www.iana.org/assignments/iana-ipv6-special-registry>).
> 
> At this point, RFC 7954 and RFC 7955 refer to a prefix that does not exists anymore. As such it make sense to move both documents to the status of "HISTORIC". This note, associated with the status change of the two RFCs will allow to keep track of the LISP EID prefix experiment.