Re: [lisp] Moving draft-ietf-lisp-name-encoding to standard track?

Jordi Paillissé <jordi.paillisse@upc.edu> Fri, 12 January 2024 11:51 UTC

Return-Path: <jordi.paillisse@upc.edu>
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 A01CDC14F738 for <lisp@ietfa.amsl.com>; Fri, 12 Jan 2024 03:51:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=upc-edu.20230601.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I2I-bENEJ322 for <lisp@ietfa.amsl.com>; Fri, 12 Jan 2024 03:51:17 -0800 (PST)
Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F30AC14F749 for <lisp@ietf.org>; Fri, 12 Jan 2024 03:51:17 -0800 (PST)
Received: by mail-lf1-x133.google.com with SMTP id 2adb3069b0e04-50eabd1c701so7762767e87.3 for <lisp@ietf.org>; Fri, 12 Jan 2024 03:51:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=upc-edu.20230601.gappssmtp.com; s=20230601; t=1705060275; x=1705665075; darn=ietf.org; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=2zX26jpPtRfG99Pt37rX6zNdkzEcMcrfEXY8tFiSgno=; b=UD2n+o1zYjj9jx27TEH2TJ4XpCc2zHe5Mr8Jxhev8YIdF+Pg01PFSgEFOSXN1Z/CS6 N9rbKYq6iIy2dGrdw0Xyz774tP9kclvys+zuDH+VLmvoc3ecGxyg9J+j9sifs4at5oYw 2BoQLvpIG+Heiz3I8jhoE/M/a5HPcZfBfJEujh5SaODgpIfsEJtnAZK1yeg+CIaS5S/E pFIgf7MxYAXvPB1CRU0kZgHe1rhKwoTXADrA7NYISumOetx3be6OZ4I1ljvCnLYEMmtq LMpTg3ETakK6sWBqhpI4urDyEswgYf5HwXm+EaHu0AtoAg2eFP4X/Okz8rSdAGy0QTeV FMfw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705060275; x=1705665075; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=2zX26jpPtRfG99Pt37rX6zNdkzEcMcrfEXY8tFiSgno=; b=BJxU1dkZbIeWOuS1DqTgrf1O0I4wssSjjGZMHz0MtTfc32+HUvxMwmIc+mYOBlet9C Ab7j+dCP+hbjSrRfwnGfcjY7IvIgzNLFb+5QtFTPLDAm8rNGFHugbPVcPvFlbHaJLqav JuNMQw2vTGksa+03Fka22jA4CU7bO35U2HP00UpFko79pOGAgoWaN0BGqslEdPPXkcNY gljaqmkE+f0QoVSfPSI4lhhWi6edzJbLlYiPmFZswgA4Hb33b6mTEKLIoMtmI3+hoOnn HKkrmokcPHThYCd6FnnUU6u0ql6o/Btu/G83hgjZnPbnF344vYE01ln95POf//RjyIgu ctIg==
X-Gm-Message-State: AOJu0YwiOvzVLmWhHQshPzwpdLxYjy0300NuU5qCSVlUNier38ht3Z+D 4sLtEi/1Djzgs8PLeQV3/Dk67iVkbcIJ0ogY748xJ1a+BJQOj4fu/qWs9BYOcx0CwyKCNZmuYve aATHknnzAHbtF1Crbmk/ibpbV35hTWsd7qYZ1VoRTPExHFQUtDb5drq8c1WJ7HX3LYMXCXWIZE/ g=
X-Google-Smtp-Source: AGHT+IHuMQv+QX07GeU6+0gxLZJm7NgRRRb8jekbnuPDw7LRjFg0c2aaTedIVaHcXzWo8UesTNj7tw==
X-Received: by 2002:a05:6512:398f:b0:50e:7479:79da with SMTP id j15-20020a056512398f00b0050e747979damr824210lfu.24.1705060275224; Fri, 12 Jan 2024 03:51:15 -0800 (PST)
Received: from [192.168.68.104] (70.red-83-46-67.dynamicip.rima-tde.net. [83.46.67.70]) by smtp.gmail.com with ESMTPSA id w4-20020ac254a4000000b0050e7663a31csm475201lfk.223.2024.01.12.03.51.14 for <lisp@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 12 Jan 2024 03:51:15 -0800 (PST)
Content-Type: multipart/alternative; boundary="------------2YFp515PE48msBmhRRqKiAZX"
Message-ID: <68570c65-e257-42a1-ad0a-b999337300e5@upc.edu>
Date: Fri, 12 Jan 2024 12:51:14 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: ca, en-GB, es-ES
To: lisp@ietf.org
References: <BYAPR11MB35913B8053FC21D7D0A5D082B69EA@BYAPR11MB3591.namprd11.prod.outlook.com> <A9558658-31AD-4197-8232-75D982D22D2B@gigix.net> <BY5PR11MB43696CA18CF7C1C8F2525517C2682@BY5PR11MB4369.namprd11.prod.outlook.com>
From: Jordi Paillissé <jordi.paillisse@upc.edu>
In-Reply-To: <BY5PR11MB43696CA18CF7C1C8F2525517C2682@BY5PR11MB4369.namprd11.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/-lh1XSwQTIRdbRRy-9DA0driPyU>
Subject: Re: [lisp] Moving draft-ietf-lisp-name-encoding to standard track?
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 12 Jan 2024 11:51:19 -0000

Support!

Jordi

El 11/1/24 a les 18:34, Fabio Maino (fmaino) ha escrit:
>
> I support moving this document to standard track
>
> Fabio
>
> *From: *lisp <lisp-bounces@ietf.org> on behalf of Luigi Iannone 
> <ggx@gigix.net>
> *Date: *Thursday, January 11, 2024 at 4:53 AM
> *To: *LISP mailing list list <lisp@ietf.org>
> *Cc: *lisp-chairs@ietf.org <lisp-chairs@ietf.org>
> *Subject: *[lisp] Moving draft-ietf-lisp-name-encoding to standard track?
>
> Hi All,
>
> Happy new year!
>
> As you may have seen from Alberto’s shepherd review of the name 
> encoding document, it is suggested to move the document to standard track.
>
> Jim Guichard (our AD) is OK as long as the WG is OK with this change 
> and that deployment experience is added to the document.
>
> Hence, this email opens a two weeks call to check if you agree with 
> the change.
>
> Please reply to this email stating whether you are in favor or you are 
> against.
>
> (Silence does not count)
>
> Please reply.
>
> Ciao
>
> L.
>
>
>
>     Begin forwarded message:
>
>     *From: *"Alberto Rodriguez-Natal \(natal\)"
>     <natal=40cisco.com@dmarc.ietf.org>
>
>     *Subject: [lisp] Shepherd's review of draft-ietf-lisp-name-encoding*
>
>     *Date: *December 28, 2023 at 12:00:33 GMT+1
>
>     *To: *"lisp@ietf.org" <lisp@ietf.org>
>
>     Hi all,
>
>     The shepherd’s review of the LISP Distinguished Name Encoding has
>     been posted. The document is in good shape and minor identified
>     nits have been fixed. Please find the review here:
>
>     https://datatracker.ietf.org/doc/draft-ietf-lisp-name-encoding/shepherdwriteup/
>     <https://datatracker.ietf.org/doc/draft-ietf-lisp-name-encoding/shepherdwriteup/>
>
>     However, as part of the review, it was raised the question if the
>     document is in the right stream (currently in Experimental). Given
>     that there are known implementations of the spec and that it has
>     been running in production for some time, my suggestion is to
>     consider moving this document to Standards track instead.
>
>     Thanks,
>
>     Alberto
>
>     _______________________________________________
>     lisp mailing list
>     lisp@ietf.org <mailto:lisp@ietf.org>
>     https://www.ietf.org/mailman/listinfo/lisp
>     <https://www.ietf.org/mailman/listinfo/lisp>
>
>
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp