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

Luigi Iannone <ggx@gigix.net> Thu, 11 January 2024 12:53 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 74E31C15108F for <lisp@ietfa.amsl.com>; Thu, 11 Jan 2024 04:53:27 -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=gigix-net.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 KTY4SS7lBdro for <lisp@ietfa.amsl.com>; Thu, 11 Jan 2024 04:53:25 -0800 (PST)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 28FC0C15107E for <lisp@ietf.org>; Thu, 11 Jan 2024 04:53:24 -0800 (PST)
Received: by mail-wm1-x334.google.com with SMTP id 5b1f17b1804b1-40e54f233abso21989695e9.0 for <lisp@ietf.org>; Thu, 11 Jan 2024 04:53:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20230601.gappssmtp.com; s=20230601; t=1704977602; x=1705582402; darn=ietf.org; h=message-id:to:cc:references:date:subject:mime-version:from:from:to :cc:subject:date:message-id:reply-to; bh=K2wRzXKHmCrld1f01OkbkRwo01Dty2/BlTIEhsdVJd4=; b=p2cnJlU0AyCZuCWadcp/QNpkPOzFmskR3Uo4XuXZkmMGAcJPANUTa/N9B+TkoUSkhP wgXWgWcw5BrRDl7d/NG6gtFVs0xQXtHfVhCSmiUUnoSJwK+/26M4aQ6X0KFz53mIcrmR VecM7s2g2KjNgZvLYjVOHF6f5CJqYqgJQWV/bf70UZ7TJ/1NQhsru0uhPM++8XBO6aVL 7tU5MPCMaZHI4FSwxGAKRhLccYrX6xhSrusZi8xn4CoU3SfURyqHViL49F1wA9GoYTtw hXAMk65SJ+jDd45ZVqffW0QAW/BxVjnFOPWPhQtrLsDp+TKnzX3pXNKC4QgMKf11hq1Z K6Ew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704977602; x=1705582402; h=message-id:to:cc:references:date:subject:mime-version:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=K2wRzXKHmCrld1f01OkbkRwo01Dty2/BlTIEhsdVJd4=; b=I7wZPqxAd6VtNrLQ6uA6FxE4nV7xkd59HeA0x8r81RSvy5gkuoUIT5fcKrmvcBJ083 M5Zaeac9BL1E1MPxsOkYiPylOjjzKZfr3UopCjmdcU1yLgMYrWV+dRSEDvDx/j6yn1ht /OFuIfppyTwdYs9iHDAC7E0/K3YcvlQR8opZ82omqbB0HVlAmkRqkuFqbdBR9ZY4qkF7 OfJ02SYJrqjjPRRNrEZdpoKM0amINPYP4A8EbZbM6u3VcsGD6V4G4/9hVnBdz9CJjw/e b74zA0Nmri7+7HUWuvrLlRIT1QkIrgHZinbCfSl0rDFSZ/3eB2xCdHS/tL1qPtezBG1S 0B0Q==
X-Gm-Message-State: AOJu0YznihJ/C/tHiZxVnasaz/4trnjrmD9NjmJxuuZW+eje5geUnS/1 liOlSpAuKhxDpYP5Sn31N11XjvkdXwG2+QpUITTPiA9z1rlE+w==
X-Google-Smtp-Source: AGHT+IGxyl7TZyssO5/u2dTho2uj6mQdJXgim17o1jlptuq0Tj6tCaRX77WPNgFt1OEGxZOVy8y8Eg==
X-Received: by 2002:a05:600c:4f56:b0:40e:4267:cfc4 with SMTP id m22-20020a05600c4f5600b0040e4267cfc4mr407245wmq.112.1704977601584; Thu, 11 Jan 2024 04:53:21 -0800 (PST)
Received: from smtpclient.apple (91-167-176-17.subs.proxad.net. [91.167.176.17]) by smtp.gmail.com with ESMTPSA id m7-20020a5d4a07000000b003365fc41bcasm1161793wrq.51.2024.01.11.04.53.20 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Jan 2024 04:53:21 -0800 (PST)
From: Luigi Iannone <ggx@gigix.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5EF8DCB2-78F2-4A17-9851-F21FADA13FF8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\))
Date: Thu, 11 Jan 2024 13:52:50 +0100
References: <BYAPR11MB35913B8053FC21D7D0A5D082B69EA@BYAPR11MB3591.namprd11.prod.outlook.com>
Cc: lisp-chairs@ietf.org
To: LISP mailing list list <lisp@ietf.org>
Message-Id: <A9558658-31AD-4197-8232-75D982D22D2B@gigix.net>
X-Mailer: Apple Mail (2.3774.300.61.1.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/dX5v0KOlVofhQEVA6Ozkl1FEjXQ>
Subject: [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: Thu, 11 Jan 2024 12:53:27 -0000

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/
>  
> 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