Re: [Asap] Consensus check: Use of JSON for the capability set document
"A. Jean Mahoney" <mahoney@nostrum.com> Fri, 27 August 2021 19:02 UTC
Return-Path: <mahoney@nostrum.com>
X-Original-To: asap@ietfa.amsl.com
Delivered-To: asap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3E593A0858; Fri, 27 Aug 2021 12:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.08
X-Spam-Level:
X-Spam-Status: No, score=-2.08 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, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X3kqZ5aCujH5; Fri, 27 Aug 2021 12:02:14 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD3A33A083C; Fri, 27 Aug 2021 12:02:14 -0700 (PDT)
Received: from Zexmenia.localdomain ([47.186.34.206]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 17RJ2B5Q065126 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 27 Aug 2021 14:02:11 -0500 (CDT) (envelope-from mahoney@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1630090932; bh=wq6JKJ5FoKyeKhRe/5HHh6BiquT6zZXFqasEoYfRYpY=; h=Subject:To:References:From:Date:In-Reply-To; b=gG1sIoTM+YdPzTC3/9nB+l+5B9g4dlOzdA2csMBHgeRSye75qXeLzLH1ZZhmQrhCK JyTqSbgENgD1GBvuMYYbskoaRSmEmunNKHTVdoE5i1mZcbExhsTZjkZ54VQUXsqSp6 QeUcHoGJv0wFpk8OboeeOfxQTKdAtW3GMjuHn6yY=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.34.206] claimed to be Zexmenia.localdomain
To: asap@ietf.org, draft-ietf-asap-sip-auto-peer.authors@ietf.org
References: <4cdcc67a-e6e6-d001-0222-4cb5a61a6b76@nostrum.com>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <ca0f8ac1-7d45-3b29-8f32-700cd4428720@nostrum.com>
Date: Fri, 27 Aug 2021 14:02:05 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <4cdcc67a-e6e6-d001-0222-4cb5a61a6b76@nostrum.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/asap/MVU8yjNjjuIiP64d1I2aCWLHAHY>
Subject: Re: [Asap] Consensus check: Use of JSON for the capability set document
X-BeenThere: asap@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Automatic SIP trunking And Peering WG <asap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/asap>, <mailto:asap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/asap/>
List-Post: <mailto:asap@ietf.org>
List-Help: <mailto:asap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/asap>, <mailto:asap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Aug 2021 19:02:33 -0000
Since no concerns have been raised, draft-ietf-asap-sip-auto-peer can be updated to support JSON. Thanks! Jean, as co-chair On 8/9/21 11:47 AM, A. Jean Mahoney wrote: > Hi all, > > At the IETF 111 ASAP WG session, it was discussed that one format for > the capability set document should be selected and supported, and a > preference for JSON was indicated. > > Please raise any concerns by August 23 if you have any. > > Thanks! > > Jean, as cochair >
- [Asap] Consensus check: Use of JSON for the capab… A. Jean Mahoney
- Re: [Asap] Consensus check: Use of JSON for the c… A. Jean Mahoney