Return-Path: X-Original-To: auth48archive@mail2.ietf.org Delivered-To: auth48archive@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id AA247FDFF83E for ; Tue, 9 Jun 2026 05:12:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1781007120; bh=FiPtOyA5Oy8i6tFERj18M51zmWuvAi2/yAF56wrmxf0=; h=References:In-Reply-To:From:Date:Subject:To:Cc; b=JW+dqqOxTmI836Q76A0N8B44l4u1NGDDMGI6CrTilRhOVLjIHK6+oweEAzGyw+bAT O5JD1Y7q+njdiu+RfA6EQ6QuQBPVwTkI5jN1NMzaVyo2IPznXfEv/czxb3S9mJPj8x AWEsylEUkimlal/rzWDqvuo5VDdFsyR24NTpyH8A= X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, 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 (2048-bit key) header.d=gmail.com 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 E742btAEqhUd for ; Tue, 9 Jun 2026 05:11:59 -0700 (PDT) Received: from mail-yx1-xb12c.google.com (mail-yx1-xb12c.google.com [IPv6:2607:f8b0:4864:20::b12c]) (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 E6A01FDFF82D for ; Tue, 9 Jun 2026 05:11:59 -0700 (PDT) Received: by mail-yx1-xb12c.google.com with SMTP id 956f58d0204a3-66061993121so5169787d50.0 for ; Tue, 09 Jun 2026 05:11:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1781007119; cv=none; d=google.com; s=arc-20240605; b=iV5eWaifTWvPW4EVHjAdYs/Ued8Jkva7zH+TAxPPzr5tjxduBAksegnfkP47lBytou UztrgfdPdVrmvm9As3S2D2q76jHDiEG3P6B+Q2PzLwob/+CU619XF48eFhA92kaEH3UG l7tyhrAF8/S64x3KiNlywk1Eg1r6YbFSjSoJy2eLtRljMoWcn8n63pSDNoDKe1kCDwiF x6pqxypwCh6aEUwQ7pAYcMGtlKu0LQVQfxti0FCnB7RmzInwGKshjReb0lYUFgbM2O2H VtCY5DGYPpaNYuo61qP+QSlSptoLIoLEczJAb8Jvhl3JL5ZAOtswAGQNLED5s1tcK+PV EiAw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=euwFyrzly1cUv/BL9vnNcrwGcZAwz4eQJWD8amj+GnI=; fh=ek1YPdGwRhu2SHYXPd4wZ5QSjiGg2CL0W1sgaRBtSic=; b=ehd7m43zlTpQOO774scsuSbdSeRA5aUNOtyOZG4VGY8YQIT+RHQRh3dTf3W1MONI1Q POrokF8PSEu3tXKBHLIBy6Ncg2x2bf/8ThnuLqXmM8Pyx2DxB7wx0FegYz2WiLxYSyve dcm90BE5PMWptVO9Gm4UKjRKcBLYodMlxLtE3tFgG3zs64N6CwY09msVpcL0DPR09skr xqH9tqc5PRNSFeQUg9dyuy8XSBjuSBH9s87zlqJkPWD4eqMdnc4owLqujEkZYdtbwfoD w+tf37tDmQy9nUQx3hE9ftYEs72QO/MzEkuemV9gSMS4jDtyuQNUTlP2ORhjH5cZ2xD8 mf6g==; darn=rfc-editor.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1781007119; x=1781611919; darn=rfc-editor.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=euwFyrzly1cUv/BL9vnNcrwGcZAwz4eQJWD8amj+GnI=; b=NiepMkN6SnlaJxQIrKkLytUa3NtjAiTkS6JtwwjGOdYZnfMuEDYgT4ipqVHN57H2JU Z8aOGWq4E8/VYrTnUJbOa2GqLxsT2B2QVZdB4PjjMiSkZJQxuyBEYp8tx5wiLrLUG/u1 E8G47rLNtzdmmMmh4XcxrUDb5MfSI8gzTlSAqv9/QeuWkvhLsmAYe5kbI5vtkQ6gxlvo QPz88KQ3k4S53+t9ALOB/CkR/a51EvKz9x4YfcSAsf3Fzr2OOEvvOyszEbnriINAB1Jk pVJ7CvKJwMPlW3V2nYCrY363mrf18FJbHhVi3c9oZHXJN/nuGtcwaWJZ/i62Qjpe/HOU /KSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1781007119; x=1781611919; 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=euwFyrzly1cUv/BL9vnNcrwGcZAwz4eQJWD8amj+GnI=; b=lN1ZKpS7II0t0/UD9q7GJEnXczm9eJknsLFL0i2VlI6aHIRNBVpneMl4btpLbhxTVr 0BdW4jOrA22uPcqq+NUxonqrpH20TT/yp2Ijwze65Z+/U6Jx1msY/1ago532+Bz5E7C/ 2A4vFa0kNMK+S1pwESGxd3dnsgzfoxMmEBQ9l0PvQyz42t5ezoogiQcSZTH7DlToCkyZ IOBz2yQNF3T4+WZT3LqALfRc4Ztg3Q0kXqXjQDCNO/eY5GSx52CXJYg8oFoHdh+D6X3p Ymz1t0emJJe44ZY8seT3Ftpn6mO2svAo85OMoYDEIcNkQRjLlt4Vd0AnMsi3L+aL1YVl v83A== X-Forwarded-Encrypted: i=1; AFNElJ/x+ndpEglTKRruP0eWQAB6d56iIUa4skftY82u4j5vmaooZ0fCY64quyJnEBpAjd2prs6BS2nk0umkvcdP@rfc-editor.org X-Gm-Message-State: AOJu0YwmcgBhuXmhTuUoyY4WmSiBJ73fBVnfkTUEfQNf7ot1EpX56GIx dd4rxINaAzGiVLTKQgXlsdhPbZxOBavsbq2qa0blTmCUNJYKu3KkQJds+V1MBGzZN9iBuO9xbIL hmDKiZ/dtHhcUF3nB+Fo49A4mBoc0GqA= X-Gm-Gg: Acq92OFGmo/5mwq86BCc97veXUioi+X97LVRSghlhlmXJY7Dyg+sbQSmKj8d9zwNwle XLoDZz+1a+oLZQOG0VHIZ4B9BkKf9n16wMxsj2bITFKrzmH5iLlPXJpu+7xOa+sualCPyJlRGBv d2Zrxcv2TvO7QO2vIf6ps4KxeYfQ0+ENAVWUyBUgIWgYr+/Dc0+pPLJ+R3Awc8aTQmO4ml2pwZq fAZGStwlAt50Gfwq5VitnuCu65y5FrPT5UOd3MDfZjzIL3SFazjtcBgS8ON6paJV/hyWLFij9G+ lXTuZ2wmwcyi6KO7aW3HtYuz+MsI33pdSZDPF7WO5P/PCHBc5tSweSYrBaJUqHFevUltcB3UJfW XsGdPMPxqq0mnSefRyC1a4O2I6rkv6zLdt2fOGWRijyGMYPbTb0K1lPxh7XMuevdRqxDKTIKcJS 8z4ogz16azRX/kaT8fI4IamA== X-Received: by 2002:a53:ac87:0:b0:661:1307:3d4f with SMTP id 956f58d0204a3-6611307413fmr14967522d50.46.1781007119302; Tue, 09 Jun 2026 05:11:59 -0700 (PDT) MIME-Version: 1.0 References: <177948070467.17.6248200274862467227@rfc-editor.org> In-Reply-To: From: Italo Busi Date: Tue, 9 Jun 2026 14:11:48 +0200 X-Gm-Features: AVVi8CeA84TtcXt2GYXyx5D6IpM_se1lpPNYtbZ_-G4DIwKysO9g7o8hbP7lLhs Message-ID: To: Sarah Tarrant Content-Type: multipart/alternative; boundary="000000000000b0427a0653d108b9" Message-ID-Hash: P5T5N5F7U7A4Y7TINACA5N7PXGODSFCP X-Message-ID-Hash: P5T5N5F7U7A4Y7TINACA5N7PXGODSFCP X-MailFrom: italo.busi@gmail.com 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 CC: zhenghaomian@huawei.com, xufeng.liu.ietf@gmail.com, sergio.belotti@nokia.com, oscar.gonzalezdedios@telefonica.com, ketant.ietf@gmail.com, james.n.guichard@futurewei.com, gunter.van_de_velde@nokia.com, d.king@lancaster.ac.uk, RFC Editor , auth48archive@rfc-editor.org, Italo Busi X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5Bauth48=5D_Re=3A_Document_intake_questions_about_draft-ietf-ccam?= =?utf-8?q?p-otn-topo-yang?= List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000b0427a0653d108b9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Sarah, Thanks for the reminder We are planning to reply by the end of this week Italo Il ven 5 giu 2026, 23:00 Sarah Tarrant ha scritto: > Hi Author(s), > > This is a second friendly reminder that we await answers to the questions > below before continuing with the editing process for this document. > > If we do not hear back in the next week, we will continue with processing > this document, but some of these questions may be repeated during Final > Review. > > Thank you, > Sarah Tarrant > RFC Production Center > > > On May 29, 2026, at 11:11=E2=80=AFAM, Sarah Tarrant < > starrant@staff.rfc-editor.org> wrote: > > > > Hi Author(s), > > > > This is a friendly reminder that we await answers to the questions belo= w > before continuing with the editing process for this document. > > > > Thank you, > > Sarah Tarrant > > RFC Production Center > > > >> On May 22, 2026, at 3:11=E2=80=AFPM, rfc-editor@rfc-editor.org wrote: > >> > >> Author(s), > >> > >> Congratulations, your document has been successfully added to the RFC > Editor queue! > >> The team at the RFC Production Center (RPC) is looking forward to > working with you > >> as your document moves forward toward publication. To help reduce > processing time > >> and improve editing accuracy, please respond to the questions below. > Please confer > >> with your coauthors (or authors of other documents if your document is > in a > >> cluster) as necessary prior to taking action in order to streamline > communication. > >> If your document has multiple authors, only one author needs to reply > to this > >> message. > >> > >> As you read through the rest of this email: > >> > >> * If you need/want to make updates to your document, we encourage you > to make those > >> changes and resubmit to the Datatracker. This allows for the easy > creation of diffs, > >> which facilitates review by interested parties (e.g., authors, ADs, do= c > shepherds). > >> * If you feel no updates to the document are necessary, please reply > with any > >> applicable rationale/comments. > >> > >> > >> Please note that the RPC team will not work on your document until we > hear from you > >> (that is, your document will remain in AUTH state until we receive a > reply). Even > >> if you don't have guidance or don't feel that you need to make any > updates to the > >> document, you need to let us know. After we hear from you, your > document will start > >> moving through the queue. You will be able to review and approve our > updates > >> during AUTH48. > >> > >> Please feel free to contact us with any questions you may have at > >> rfc-editor@rfc-editor.org. > >> > >> Thank you! > >> The RPC Team > >> > >> -- > >> > >> 1) As there may have been multiple updates made to the document during > Last Call, > >> please review the current version of the document: > >> > >> * Is the text in the Abstract still accurate? > >> * Are the Authors' Addresses, Contributors, and Acknowledgments > >> sections current? > >> > >> > >> 2) Please share any style information that could help us with editing > your > >> document. For example: > >> > >> * Is your document's format or its terminology based on another > document, > >> WG style guide, etc.? If so, please provide a pointer to that > information > >> (e.g., "This document's terminology should match DNS terminology in > >> RFC 9499." or "This document uses the style info at > >> ."). > >> * Is there a general pattern of capitalization or formatting of terms > that > >> editors can follow (e.g., "Field names should have initial > capitalization." > >> or "Parameter names should be in double quotes." or " should be > used > >> for token names." etc.)? > >> > >> > >> 3) Please carefully review the entries and their URLs in the > >> References section with the following in mind. Note that we will > >> update as follows unless we hear otherwise at this time: > >> > >> * References to obsoleted RFCs will be updated to point to the current > >> RFC on the topic in accordance with Section 4.8.6 of RFC 7322 > >> (RFC Style Guide). > >> > >> * References to I-Ds that have been replaced by another I-D will be > >> updated to point to the replacement I-D. > >> > >> * References to documents from other organizations that have been > >> superseded will be updated to their superseding version. > >> > >> Note: To check for outdated RFC and I-D references, you can use > >> idnits . You can also help the > >> IETF Tools Team by testing idnits3 < > https://author-tools.ietf.org/idnits3/> > >> with your document and reporting any issues to them. > >> > >> > >> 4) Is there any text that requires special handling? For example: > >> * Are there any sections that were contentious when the document was > drafted? > >> * Are any sections that need to be removed before publication marked a= s > such > >> (e.g., Implementation Status sections (per RFC 7942)). > >> * Are there any instances of repeated text/sections that should be > edited > >> the same way? > >> > >> > >> 5) This document contains sourcecode: > >> > >> * Does the sourcecode validate? > >> * Some sourcecode types (e.g., YANG) require certain references and/or > text > >> in the Security Considerations section. Is this information correct? > >> * Is the sourcecode type indicated in the XML? (See information about > >> types: https://www.rfc-editor.org/rpc/wiki/doku.php?id=3Dsourcecode-ty= pes > .) > >> > >> > >> 6) This document is part of Cluster 517: > >> https://queue.rfc-editor.org/clusters/517/ > >> > >> * To help the reader understand the content of the cluster, is there a > >> document in the cluster that should be read first? Next? If so, please > provide > >> the order and we will provide RFC numbers for the documents > accordingly. > >> If order is not important, please let us know. > >> * Is there any text that has been repeated within the cluster document > that > >> should be edited in the same way (for instance, parallel introductory > text or > >> Security Considerations)? > >> * For more information about clusters, see: > >> https://authors.ietf.org/en/rfc-publication-process#clusters > >> * For a list of all current clusters, see: > >> https://queue.rfc-editor.org/clusters/ > >> > >> > >> 7) Is there anything else that the RPC should be aware of while editin= g > this > >> document? > >> > > > > --000000000000b0427a0653d108b9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Sarah,

Th= anks for the reminder

We= are planning to reply by the end of this week=C2=A0
<= br>
Italo

Il ven 5 = giu 2026, 23:00 Sarah Tarrant <starrant@staff.rfc-editor.org> ha scritto:
Hi Author(s),

This is a second friendly reminder that we await answers to the questions b= elow before continuing with the editing process for this document.

If we do not hear back in the next week, we will continue with processing t= his document, but some of these questions may be repeated during Final Revi= ew.

Thank you,
Sarah Tarrant
RFC Production Center

> On May 29, 2026, at 11:11=E2=80=AFAM, Sarah Tarrant <sta= rrant@staff.rfc-editor.org> wrote:
>
> Hi Author(s),
>
> This is a friendly reminder that we await answers to the questions bel= ow before continuing with the editing process for this document.
>
> Thank you,
> Sarah Tarrant
> RFC Production Center
>
>> On May 22, 2026, at 3:11=E2=80=AFPM, rfc-editor@rfc-editor.= org wrote:
>>
>> Author(s),
>>
>> Congratulations, your document has been successfully added to the = RFC Editor queue!=C2=A0
>> The team at the RFC Production Center (RPC) is looking forward to = working with you
>> as your document moves forward toward publication. To help reduce = processing time
>> and improve editing accuracy, please respond to the questions belo= w. Please confer
>> with your coauthors (or authors of other documents if your documen= t is in a
>> cluster) as necessary prior to taking action in order to streamlin= e communication.
>> If your document has multiple authors, only one author needs to re= ply to this
>> message.
>>
>> As you read through the rest of this email:
>>
>> * If you need/want to make updates to your document, we encourage = you to make those
>> changes and resubmit to the Datatracker. This allows for the easy = creation of diffs,
>> which facilitates review by interested parties (e.g., authors, ADs= , doc shepherds).
>> * If you feel no updates to the document are necessary, please rep= ly with any
>> applicable rationale/comments.
>>
>>
>> Please note that the RPC team will not work on your document until= we hear from you
>> (that is, your document will remain in AUTH state until we receive= a reply). Even
>> if you don't have guidance or don't feel that you need to = make any updates to the
>> document, you need to let us know. After we hear from you, your do= cument will start
>> moving through the queue. You will be able to review and approve o= ur updates
>> during AUTH48.
>>
>> Please feel free to contact us with any questions you may have at =
>> rfc-editor@rfc-editor.org.
>>
>> Thank you!
>> The RPC Team
>>
>> --
>>
>> 1) As there may have been multiple updates made to the document du= ring Last Call,
>> please review the current version of the document:
>>
>> * Is the text in the Abstract still accurate?
>> * Are the Authors' Addresses, Contributors, and Acknowledgment= s
>> sections current?
>>
>>
>> 2) Please share any style information that could help us with edit= ing your
>> document. For example:
>>
>> * Is your document's format or its terminology based on anothe= r document,
>> WG style guide, etc.? If so, please provide a pointer to that info= rmation
>> (e.g., "This document's terminology should match DNS term= inology in
>> RFC 9499." or "This document uses the style info at
>> <https://httpwg.org/admin/edito= rs/style-guide>.").
>> * Is there a general pattern of capitalization or formatting of te= rms that
>> editors can follow (e.g., "Field names should have initial ca= pitalization."
>> or=C2=A0 "Parameter names should be in double quotes." o= r "<tt/> should be used
>> for token names." etc.)?
>>
>>
>> 3) Please carefully review the entries and their URLs in the
>> References section with the following in mind. Note that we will <= br> >> update as follows unless we hear otherwise at this time:
>>
>> * References to obsoleted RFCs will be updated to point to the cur= rent
>> RFC on the topic in accordance with Section 4.8.6 of RFC 7322
>> (RFC Style Guide).
>>
>> * References to I-Ds that have been replaced by another I-D will b= e
>> updated to point to the replacement I-D.
>>
>> * References to documents from other organizations that have been =
>> superseded will be updated to their superseding version.
>>
>> Note: To check for outdated RFC and I-D references, you can use >> idnits <https://author-tools.ietf.org/idn= its>. You can also help the
>> IETF Tools Team by testing idnits3 <htt= ps://author-tools.ietf.org/idnits3/>
>> with your document and reporting any issues to them.
>>
>>
>> 4) Is there any text that requires special handling? For example:<= br> >> * Are there any sections that were contentious when the document w= as drafted?
>> * Are any sections that need to be removed before publication mark= ed as such
>> (e.g., Implementation Status sections (per RFC 7942)).
>> * Are there any instances of repeated text/sections that should be= edited
>> the same way?
>>
>>
>> 5) This document contains sourcecode:
>>
>> * Does the sourcecode validate?
>> * Some sourcecode types (e.g., YANG) require certain references an= d/or text
>> in the Security Considerations section. Is this information correc= t?
>> * Is the sourcecode type indicated in the XML? (See information ab= out
>> types: https:= //www.rfc-editor.org/rpc/wiki/doku.php?id=3Dsourcecode-types.)
>>
>>
>> 6) This document is part of Cluster 517:
>> https://queue.rfc-editor.org/clusters/= 517/
>>
>> * To help the reader understand the content of the cluster, is the= re a
>> document in the cluster that should be read first? Next? If so, pl= ease provide
>> the order and we will provide RFC numbers for the documents accord= ingly.
>> If order is not important, please let us know.
>> * Is there any text that has been repeated within the cluster docu= ment that
>> should be edited in the same way (for instance, parallel introduct= ory text or
>> Security Considerations)?
>> * For more information about clusters, see:
>> https://authors.ietf= .org/en/rfc-publication-process#clusters
>> * For a list of all current clusters, see:
>> https://queue.rfc-editor.org/clusters/=
>>
>>
>> 7) Is there anything else that the RPC should be aware of while ed= iting this
>> document?
>>
>

--000000000000b0427a0653d108b9--