IETF Logo Mail Archive

[Yang-sid-logistics] Fwd: New Version Notification for draft-pelov-sid-procedure-00.txt

Alexander PELOV <alexander.pelov@imt-atlantique.fr> Tue, 05 November 2024 15:58 UTC

Return-Path: <alexander.pelov@imt-atlantique.fr>
X-Original-To: yang-sid-logistics@ietfa.amsl.com
Delivered-To: yang-sid-logistics@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 600F8C180B65; Tue, 5 Nov 2024 07:58:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 (1024-bit key) header.d=imt-atlantique.fr
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 lEUiMK92KHEu; Tue, 5 Nov 2024 07:58:40 -0800 (PST)
Received: from zproxy3.enst.fr (zproxy3.enst.fr [IPv6:2001:660:330f:2::de]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B284C16943A; Tue, 5 Nov 2024 07:58:35 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by zproxy3.enst.fr (Postfix) with ESMTP id 48568A07EB; Tue, 5 Nov 2024 16:58:32 +0100 (CET)
Received: from zproxy3.enst.fr ([IPv6:::1]) by localhost (zproxy3.enst.fr [IPv6:::1]) (amavis, port 10032) with ESMTP id V3n0oAmWGAAM; Tue, 5 Nov 2024 16:58:31 +0100 (CET)
Received: from localhost (localhost [IPv6:::1]) by zproxy3.enst.fr (Postfix) with ESMTP id AA000A07D5; Tue, 5 Nov 2024 16:58:31 +0100 (CET)
DKIM-Filter: OpenDKIM Filter v2.10.3 zproxy3.enst.fr AA000A07D5
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imt-atlantique.fr; s=50EA75E8-DE22-11E6-A6DE-0662BA474D24; t=1730822311; bh=XksU9+1kD8786CeM7vXMfrrzv48W2W9UdxvG2a4MH3U=; h=Date:From:To:Message-ID:MIME-Version; b=IoXGcGLFgNGYKglcHp6VnXeh5yGA3fBzaJHtj0JIUe6yhn3FgLHRQhqJN9M8kBTnq kFKV71SLIMJusda5JtVqeJswVXuS4fxgnIAZQUEhDePGjxNMmHv6gLB6nSLEaKHgnu 9g0jes5dPHNJbq0PpVV8DMCY6QG/wu5HH8EmP46Y=
X-Virus-Scanned: amavis at enst.fr
Received: from zproxy3.enst.fr ([IPv6:::1]) by localhost (zproxy3.enst.fr [IPv6:::1]) (amavis, port 10026) with ESMTP id QaohfU-lMlau; Tue, 5 Nov 2024 16:58:31 +0100 (CET)
Received: from zmail-imta1.enst.fr (zmail-imta1.enst.fr [137.194.2.216]) by zproxy3.enst.fr (Postfix) with ESMTP id 8E25AA07BA; Tue, 5 Nov 2024 16:58:31 +0100 (CET)
Date: Tue, 05 Nov 2024 16:58:31 +0100
From: Alexander PELOV <alexander.pelov@imt-atlantique.fr>
To: yang-sid-logistics@ietf.org, core <core@ietf.org>, schc <schc@ietf.org>
Message-ID: <1390262650.15218404.1730822309376.JavaMail.zimbra@imt-atlantique.fr>
In-Reply-To: <173081740880.50534.5317268382668428309@dt-datatracker-5f77bcf4bd-vglkb>
References: <173081740880.50534.5317268382668428309@dt-datatracker-5f77bcf4bd-vglkb>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_d47eddac-6233-4e7c-b364-b3df5137ecce"
X-Originating-IP: [::ffff:31.133.143.93]
X-Mailer: Zimbra 9.0.0_GA_4653 (ZimbraWebClient - FF132 (Mac)/9.0.0_GA_4653)
Thread-Topic: New Version Notification for draft-pelov-sid-procedure-00.txt
Thread-Index: 0qqNIWL0cYh9rAyhpXoE+NpKH3lVQg==
Message-ID-Hash: EFQDD37L6ILLB6UOTMFRXFC4OBAXNFFX
X-Message-ID-Hash: EFQDD37L6ILLB6UOTMFRXFC4OBAXNFFX
X-MailFrom: alexander.pelov@imt-atlantique.fr
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Yang-sid-logistics] Fwd: New Version Notification for draft-pelov-sid-procedure-00.txt
List-Id: "Communication facilitating the logistics of handling YANG SIDs (RFC 9595) in IANA registration and RFC Production Center processes" <yang-sid-logistics.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-sid-logistics/zOP8s0eFJLmDfShMchTYfqyce0I>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-sid-logistics>
List-Help: <mailto:yang-sid-logistics-request@ietf.org?subject=help>
List-Owner: <mailto:yang-sid-logistics-owner@ietf.org>
List-Post: <mailto:yang-sid-logistics@ietf.org>
List-Subscribe: <mailto:yang-sid-logistics-join@ietf.org>
List-Unsubscribe: <mailto:yang-sid-logistics-leave@ietf.org>

Dear all, 

We've been discussing for some time how SIDs can be allocated manually. 
I think we need to discuss a process that can be used by the different WG. 
This is a short documents that tries to take a stab at the question. 

It is of course open for discussion. 

Cheers, 
Alexander 



De: internet-drafts@ietf.org 
À: "Alexander PELOV" <alexander.pelov@imt-atlantique.fr> 
Envoyé: Mardi 5 Novembre 2024 14:36:48 
Objet: New Version Notification for draft-pelov-sid-procedure-00.txt 

A new version of Internet-Draft draft-pelov-sid-procedure-00.txt has been 
successfully submitted by Alexander PELOV and posted to the 
IETF repository. 

Name: draft-pelov-sid-procedure 
Revision: 00 
Title: Procedure for YANG SID Allocation 
Date: 2024-11-05 
Group: Individual Submission 
Pages: 6 
URL: https://www.ietf.org/archive/id/draft-pelov-sid-procedure-00.txt 
Status: https://datatracker.ietf.org/doc/draft-pelov-sid-procedure/ 
HTMLized: https://datatracker.ietf.org/doc/html/draft-pelov-sid-procedure 


Abstract: 

This document defines a standardized procedure for the allocation of 
YANG SID Ranges (YANG Schema Item iDentifier ranges) and the 
subsequent assignment of SIDs for IETF RFCs with YANG files. 



The IETF Secretariat

v2.45.0 | Report a Bug | By Email | System Status