[v6ops] Re: Advancing RFC7757, RFC7755, and RFC7756 to standard
Nick Buraglio <buraglio@forwardingplane.net> Thu, 13 November 2025 22:51 UTC
Return-Path: <buraglio@forwardingplane.net>
X-Original-To: v6ops@mail2.ietf.org
Delivered-To: v6ops@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id BDB6389112DC for <v6ops@mail2.ietf.org>; Thu, 13 Nov 2025 14:51:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=forwardingplane.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8MJf8VgsUf84 for <v6ops@mail2.ietf.org>; Thu, 13 Nov 2025 14:51:03 -0800 (PST)
Received: from mail-qv1-xf2f.google.com (mail-qv1-xf2f.google.com [IPv6:2607:f8b0:4864:20::f2f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 7A8C189112B1 for <v6ops@ietf.org>; Thu, 13 Nov 2025 14:51:03 -0800 (PST)
Received: by mail-qv1-xf2f.google.com with SMTP id 6a1803df08f44-8823e39c581so16583586d6.3 for <v6ops@ietf.org>; Thu, 13 Nov 2025 14:51:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forwardingplane.net; s=google; t=1763074257; x=1763679057; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=fptHCnpatDh61qhm8paCzpF3763WSdhHhE4sd532la4=; b=fghx8Nf1lxvMl3IbmoHxZQOvNjvqTBPJl/a8b5gKNgAhdJLpPfnGy55pQzzLH7NNHW mfI/q3Ss51m/00stHqQs1oMVZ7xl+VQoce+j1bksZwbsYPBmVxL/1geI3HGSFJjLeEbf Ricjg3seVeEGKqGzA3J370pua729XM5s/oJbA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763074257; x=1763679057; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=fptHCnpatDh61qhm8paCzpF3763WSdhHhE4sd532la4=; b=u1PQKp5phB0Bi4p4Wpkq9DHXXYaKtwxydSczSTuuTJ/WayofQmRYn1AnoVhy6gjGL6 BlPuR6sBQfrdrcR0Rq/HxbyaoNbWF9ZT6ZiePf7FhKPcYAh43lsCXrqUMdLGQQbAqtXB z9wa5NM2GqkCBFDcVmcEpJ0y25hVih6Hu26hPgE5kJhyI1TRSjhmZ7aPJqWkHP8BYGrZ BF0KLKtucQahkbXufzwWVRBUY/QzI9TP/KN5iaFY4UZgUehSDKSva+tbmzkGXqEZMtLK 6c+7icjDz+mr6ITQSyFbtGzVAhXpsGXwe9fZVbQrMv/x06r6f1T/RS3wtDjENDKAOYUT MfNQ==
X-Gm-Message-State: AOJu0YzzFjEb5DCYaaJvdb/8p0lNJB5TazFNbdy8hlthwCFayPQkdWlk pQrVGi/Xb5cUAv9+nYH9bThmHfOOJdHeGuGYdwkY6p+cGrLqEBTDQDzArES/wkEY8oHrWl0op2q u/JoHM8IbIvs381tP/asWnrSG/AkT03mUGStEUXZa
X-Gm-Gg: ASbGnctGasbspibc8XOs9hG9dKntHAwaKn2Hl772l2Dslx6HhhG8Bu54a2e62veX0Dk mjF9O+F0SuNBRHA0gOWFcNG6vUAx+mKJ4HewGuwk9earhblg8Iz7Yi2tJjqWs3j9ChYmG+zHZdh lpfiQbWZX/xd8b1uKRkPpehlsWv5UFrRCSkNEL3fYA+YC0yHTCfkInW+PC3WaaBEy7HFhJrxqlQ tUSMl22ax8RdRtykMvTasavMTJonQckBXYRdgTPxW1VbKlL8l2UQgj6+scFa8iZ0geNJClBAPUx 9EEdAitC5uf9AE61Jw==
X-Google-Smtp-Source: AGHT+IEEaTVB7MCL6ebaOr3UPrV0Px0kX7pMO0WSdpinaeRBLK5md38qU/5A52lgwJoac4iyJGJgMGmGXTMxnVBwfus=
X-Received: by 2002:ad4:4ea5:0:b0:882:4632:cf7e with SMTP id 6a1803df08f44-882925bdb7amr13090396d6.12.1763074256811; Thu, 13 Nov 2025 14:50:56 -0800 (PST)
MIME-Version: 1.0
References: <CACMsEX_sH7=Vra3s4LAocZg-z7zkHPL__Y-MaRvnf_pfJGYk0A@mail.gmail.com> <CAMMESszW+7rV5Zo_Gf7wJ4O0Whs9i05s5292M+ODTHpUxo0P9w@mail.gmail.com>
In-Reply-To: <CAMMESszW+7rV5Zo_Gf7wJ4O0Whs9i05s5292M+ODTHpUxo0P9w@mail.gmail.com>
From: Nick Buraglio <buraglio@forwardingplane.net>
Date: Thu, 13 Nov 2025 16:50:46 -0600
X-Gm-Features: AWmQ_bmz_fGIsjtkQBnnCFeXKG_Sn7U5il7ocJ13eR9ffnfPyWAiX-c5Nni1LNk
Message-ID: <CACMsEX_80PVCAFJNuED+sAqogZPa6wW5zzUAbfM5udY+sqPSFw@mail.gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000ca4397064381b6bf"
Message-ID-Hash: KJ2XFXUWGZ67QN3NW2WXRVVAO2PKMH25
X-Message-ID-Hash: KJ2XFXUWGZ67QN3NW2WXRVVAO2PKMH25
X-MailFrom: buraglio@forwardingplane.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-v6ops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: IPv6 Operations <v6ops@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [v6ops] Re: Advancing RFC7757, RFC7755, and RFC7756 to standard
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/jd3nlsEe32ZxKc9IxeaFXbJkBCs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Owner: <mailto:v6ops-owner@ietf.org>
List-Post: <mailto:v6ops@ietf.org>
List-Subscribe: <mailto:v6ops-join@ietf.org>
List-Unsubscribe: <mailto:v6ops-leave@ietf.org>
Great point, thanks for the clarification. Yes, the intention is to promote each status one step, but only update the status - no editorial changes. RFC 7757 - Internet Standard RFC 7755 - Proposed Standard RFC 7756 - Proposed Standard Before progressing Jordi should adjust the title of draft-palet-v6ops-siit-dc-std and draft-palet-v6ops-eam-std to reflect that detail. nb On Thu, Nov 13, 2025 at 3:42 PM Alvaro Retana <aretana.ietf@gmail.com> wrote: > Nick: > > Hi! > > I don’t have an opinion on the RFCs themselves, but I have a comment on > the process. > > rfc7757 is already on the Standards Track. Jordi’s draft says that the > intent is to change its status to “Internet Standard”, is that what you > really want to do? > > The other two are, as you mentioned, Informational, but the supporting > drafts indicate that the intent is to change the status to “Internet > Standard”, which is not possible without first becoming a Proposed Standard. > > > The intent mentioned below is to move the RFCs to the Standards Track. > rfc7757 is already there. > > Thanks! > > Alvaro. > > On November 13, 2025 at 3:56:55 PM, Nick Buraglio ( > buraglio@forwardingplane.net) wrote: > > All, > > At IETF 124 we discussed advancing RFC7757, RFC7755, and RFC7756 from > Informational to standards track. The advice of the AD was that we make a > call for any *objections* to this process. So, please take a look at the > following three documents, and if there is consensus from the WG that this > is acceptable, we can fairly quickly make the request for change. > > https://datatracker.ietf.org/doc/draft-palet-v6ops-eam-std/ > https://datatracker.ietf.org/doc/draft-palet-v6ops-siit-dc-std/ > https://datatracker.ietf.org/doc/draft-palet-v6ops-siit-dc-dtm-std/ > > Please review the documents and voice any concerns about this process. > > Thanks > > Nick, Xipeng > _______________________________________________ > v6ops mailing list -- v6ops@ietf.org > To unsubscribe send an email to v6ops-leave@ietf.org > >
- [v6ops] Advancing RFC7757, RFC7755, and RFC7756 t… Nick Buraglio
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… Alvaro Retana
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… Nick Buraglio
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… jordi.palet@consulintel.es
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… mohamed.boucadair
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… jordi.palet@consulintel.es
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… mohamed.boucadair
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… jordi.palet@consulintel.es
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… jordi.palet@consulintel.es
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… jordi.palet@consulintel.es
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… Nick Buraglio
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… Brian E Carpenter
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… Michael Richardson
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… jordi.palet@consulintel.es
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… Nick Buraglio
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… Nick Buraglio
- [v6ops] Re: Advancing RFC7757, RFC7755, and RFC77… mohamed.boucadair