Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\))
From: Sarah Tarrant <starrant@staff.rfc-editor.org>
In-Reply-To: <20260429135518.865972D92DE@rfcpa.rfc-editor.org>
Date: Wed, 29 Apr 2026 08:59:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <71560DD2-ECBA-40A5-BF51-44511F52A469@staff.rfc-editor.org>
References: <20260429135518.865972D92DE@rfcpa.rfc-editor.org>
To: liuyisong@chinamobile.com,
 linchangwang.04414@h3c.com,
 zhang.zheng@zte.com.cn,
 gengxuesong@huawei.com,
 vinkumar@juniper.net
Message-ID-Hash: 5T3425YSNATJXXP5U67MKE7VPVSRNEVM
CC: austin.mantz@hpe.com, mohamed.boucadair@orange.com,
 rfc-editor@rfc-editor.org, auth48archive@rfc-editor.org
Precedence: list
Subject: =?utf-8?q?=5Bauth48=5D_Document_intake_questions_about_=3Cdraft-ietf-mboned-?=
	=?utf-8?q?amt-yang-09=3E?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/auth48archive/AEYf3bO2t2F7VWsr3cvQTeVuGqk>

Author(s),=20

Congratulations, your document has been successfully added to the RFC =
Editor queue!=20
The team at the RFC Production Center (RPC) is looking forward to =
working with you=20
as your document moves forward toward publication. To help reduce =
processing time=20
and improve editing accuracy, please respond to the questions below. =
Please confer=20
with your coauthors (or authors of other documents if your document is =
in a=20
cluster) as necessary prior to taking action in order to streamline =
communication.=20
If your document has multiple authors, only one author needs to reply to =
this=20
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=20
changes and resubmit to the Datatracker. This allows for the easy =
creation of diffs,=20
which facilitates review by interested parties (e.g., authors, ADs, doc =
shepherds).
* If you feel no updates to the document are necessary, please reply =
with any=20
applicable rationale/comments.


Please note that the RPC team will not work on your document until we =
hear from you=20
(that is, your document will remain in AUTH state until we receive a =
reply). Even=20
if you don't have guidance or don't feel that you need to make any =
updates to the=20
document, you need to let us know. After we hear from you, your document =
will start=20
moving through the queue. You will be able to review and approve our =
updates=20
during AUTH48.

Please feel free to contact us with any questions you may have at=20
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,=20
please review the current version of the document:=20

* Is the text in the Abstract still accurate?
* Are the Authors' Addresses, Contributors, and Acknowledgments=20
sections current?


2) Please share any style information that could help us with editing =
your=20
document. For example:

* Is your document's format or its terminology based on another =
document,=20
WG style guide, etc.? If so, please provide a pointer to that =
information=20
(e.g., "This document's terminology should match DNS terminology in=20
RFC 9499." or "This document uses the style info at=20
<https://httpwg.org/admin/editors/style-guide>.").
* Is there a general pattern of capitalization or formatting of terms =
that=20
editors can follow (e.g., "Field names should have initial =
capitalization."=20
or  "Parameter names should be in double quotes." or "<tt/> should be =
used=20
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=20
update as follows unless we hear otherwise at this time:

* References to obsoleted RFCs will be updated to point to the current=20=

RFC on the topic in accordance with Section 4.8.6 of RFC 7322=20
(RFC Style Guide).

* References to I-Ds that have been replaced by another I-D will be=20
updated to point to the replacement I-D.

* References to documents from other organizations that have been=20
superseded will be updated to their superseding version.

Note: To check for outdated RFC and I-D references, you can use=20
idnits <https://author-tools.ietf.org/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 as =
such=20
(e.g., Implementation Status sections (per RFC 7942)).
* Are there any instances of repeated text/sections that should be =
edited=20
the same way?


5) This document contains sourcecode:=20

* Does the sourcecode validate?
* Some sourcecode types (e.g., YANG) require certain references and/or =
text=20
in the Security Considerations section. Is this information correct?
* Is the sourcecode type indicated in the XML? (See information about=20
types: =
https://www.rfc-editor.org/rpc/wiki/doku.php?id=3Dsourcecode-types.)


6) Would you like to participate in the RPC Pilot Test for editing in =
kramdown-rfc?
If so, please let us know and provide a self-contained kramdown-rfc =
file. For more
information about this experiment, see:
https://www.rfc-editor.org/rpc/wiki/doku.php?id=3Dpilot_test_kramdown_rfc.=



7) Would you like to participate in the RPC Pilot Test for completing =
AUTH48 in=20
GitHub? If so, please let us know and provide all author, AD, and/or =
document=20
shepherd GitHub usernames. For more information about this experiment, =
see:
=
https://www.rfc-editor.org/rpc/wiki/doku.php?id=3Drpc-github-phase-0-pilot=
-test.


8) Is there anything else that the RPC should be aware of while editing =
this=20
document?=20


> On Apr 29, 2026, at 8:55=E2=80=AFAM, rfc-editor@rfc-editor.org wrote:
>=20
> Author(s),
>=20
> Your document draft-ietf-mboned-amt-yang-09, which has been approved =
for publication as=20
> an RFC, has been added to the RFC Editor queue=20
> <https://www.rfc-editor.org/current_queue.php>.=20
>=20
> If your XML file was submitted using the I-D submission tool=20
> <https://datatracker.ietf.org/submit/>, we have already retrieved it=20=

> and have started working on it.=20
>=20
> If you did not submit the file via the I-D submission tool, or=20
> if you have an updated version (e.g., updated contact information),=20
> please send us the file at this time by attaching it=20
> in your reply to this message and specifying any differences=20
> between the approved I-D and the file that you are providing.
>=20
> You will receive a separate message from us asking for style input.=20
> Please respond to that message.  When we have received your response,=20=

> your document will then move through the queue. The first step that=20
> we take as your document moves through the queue is converting it to=20=

> RFCXML (if it is not already in RFCXML) and applying the formatting=20
> steps listed at =
<https://www.rfc-editor.org/pubprocess/how-we-update/>.
> Next, we will edit for clarity and apply the style guide
> (<https://www.rfc-editor.org/styleguide/>).
>=20
> You can check the status of your document at=20
> <https://www.rfc-editor.org/current_queue.php>.=20
>=20
> You will receive automatic notifications as your document changes=20
> queue state (for more information about these states, please see=20
> <https://www.rfc-editor.org/about/queue/>). When we have completed=20
> our edits, we will move your document to AUTH48 state and ask you
> to perform a final review of the document.=20
>=20
> Please let us know if you have any questions.
>=20
> Thank you.
>=20
> The RFC Editor Team
>=20