[Asap] [Technical Errata Reported] RFC10006 (9148)
rfc-editor@rfc-editor.org Thu, 27 August 2026 16:42 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: asap@ietf.org
Delivered-To: asap@mail2.ietf.org
Received: from errata-celery-6f84c7996-wb2x7 (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 366021307EBC5; Thu, 27 Aug 2026 09:42:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1787848921; bh=ovOque+VU38QyReQWhGp3AeU7YZjGjh1OWjK8FOJRQg=; h=Subject:From:To:Cc:Date; b=r5dOCbcP2V1aV/funsLk4cDTOpKAR21xkbu5TpaVL3LJF+BYo3QYzRRX8Behn90DL FahKZkIDoBMhI1dsEebENpTBr3yqSWmwzhAxuKsVteeJRWZ5GJU19+QACU0fScEZL1 E0qsynacQshVT+HFB6eJeSs62SKwTl/j+J1ejpu4=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: rfc-editor@rfc-editor.org
To: eckelcu@cisco.com, andy@hxr.us, kaustubh.ietf@gmail.com, marc@petit-huguenin.org, fluffy@iii.ca, sknth.n@protonmail.com
Date: Thu, 27 Aug 2026 16:42:01 -0000
message-id: <178784892112.14.10081502414613310189@rfc-editor.org>
Message-ID-Hash: OPDAZLAU4VQRTNO2XR7DC73BOLUDUFUU
X-Message-ID-Hash: OPDAZLAU4VQRTNO2XR7DC73BOLUDUFUU
X-MailFrom: rfc-editor@rfc-editor.org
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: rfc-editor@rfc-editor.org, paitken@ciena.com, asap@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Asap] [Technical Errata Reported] RFC10006 (9148)
List-Id: "Discussion list for the Automatic SIP trunking And Peering (ASAP) Working Group" <asap.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/asap/Qq3ERpyJhWEs6-CJ8CsYuZZZVks>
List-Archive: <https://mailarchive.ietf.org/arch/browse/asap>
List-Help: <mailto:asap-request@ietf.org?subject=help>
List-Owner: <mailto:asap-owner@ietf.org>
List-Post: <mailto:asap@ietf.org>
List-Subscribe: <mailto:asap-join@ietf.org>
List-Unsubscribe: <mailto:asap-leave@ietf.org>
The following errata report has been submitted for RFC10006, "Automatic SIP Trunking and Peering" -------------------------------------- You may review the report below and at: https://errata.rfc-editor.org/eid9148/ -------------------------------------- Type: Technical Reported by: Paul Aitken <paitken@ciena.com> Section 11.3 says: Original Text ------------- The capability set document SHOULD be formatted as a JSON file. Corrected Text -------------- The capability set document MUST be formatted as a JSON file. Notes ----- Section 4.6 says "Capability set documents MUST be formatted in JSON" but Section 11.3 says "The capability set document SHOULD be formatted as a JSON file." Since Section 4.6 is the normative specification and Section 11.3 is providing context in the Security Considerations, the SHOULD in 11.3 looks like it should be MUST to match. Instructions: ------------- This erratum is currently posted as "Reported". Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- RFC10006 (draft-ietf-asap-sip-auto-peer) -------------------------------------- Title : Automatic SIP Trunking and Peering Publication Date : August 2026 Author(s) : K. Inamdar, S. Narayanan, C. Jennings Category : Proposed Standard Source : asap (art) Stream : IETF Verifying Party : IESG