IETF Logo Mail Archive

[Asap] draft-ietf-asap-siptrunkingcapability-link WGLC (Re: sip-trunking-capability draft)

"A. Jean Mahoney" <mahoney@nostrum.com> Tue, 08 November 2022 12:35 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 0C3A7C14CE25; Tue, 8 Nov 2022 04:35:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level:
X-Spam-Status: No, score=-2.086 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_ZEN_BLOCKED_OPENDNS=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dnsj9PsCVnrJ; Tue, 8 Nov 2022 04:35:43 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59DBEC14CF08; Tue, 8 Nov 2022 04:35:43 -0800 (PST)
Received: from [IPV6:2001:67c:1232:144:9dbd:410:8c70:4fba] ([IPv6:2001:67c:1232:144:9dbd:410:8c70:4fba]) (authenticated bits=0) by nostrum.com (8.17.1/8.17.1) with ESMTPSA id 2A8CZdvD009954 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 8 Nov 2022 06:35:41 -0600 (CST) (envelope-from mahoney@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1667910942; bh=XnYNA2B6ogLklVdXf2syBTzWec+FLoczDhpzReFJFho=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=g5sa6Xvc1+X65y9BG6UV7nJHrrQXDwMXB3aj8NeeN9MSByTn2U7ynCYZnbE0U6a02 UwBE2BP340FgF3YkomoQrrIIpB6pgmnLGE8pVHkyyVjIRMt9ALizVEXV+p/2Nr+j9t jOG8Ud5H5R6oMe7485Bx+LgzZ+TlS/QhoCBovzKQ=
Content-Type: multipart/alternative; boundary="------------5E65Fsir5JqMUkJTjW9SSY8g"
Message-ID: <17b2d9ee-c959-3f71-040a-fcd97ff2a384@nostrum.com>
Date: Tue, 08 Nov 2022 12:35:30 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.4.2
Content-Language: en-US
To: "Derek Engi (deengi)" <deengi=40cisco.com@dmarc.ietf.org>
Cc: "asap@ietf.org" <asap@ietf.org>
References: <DS7PR11MB60384382C75576ECA43172D8C43C9@DS7PR11MB6038.namprd11.prod.outlook.com>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
In-Reply-To: <DS7PR11MB60384382C75576ECA43172D8C43C9@DS7PR11MB6038.namprd11.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/asap/0yRe-5Y3CifEXpl-O5qo4MqLftA>
Subject: [Asap] draft-ietf-asap-siptrunkingcapability-link WGLC (Re: sip-trunking-capability draft)
X-BeenThere: asap@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 08 Nov 2022 12:35:47 -0000

Derek,

Thank you for the updated document.

All, this starts a two-week Working Group Last Call on 
draft-ietf-asap-siptrunkingcapability-link-01.

https://datatracker.ietf.org/doc/draft-ietf-asap-siptrunkingcapability-link/

Please provide any feedback by 2022 November 22.

Thank you,

Jean, as co-chair

On 11/7/22 4:39 PM, Derek Engi (deengi) wrote:
>
> Hi Jean, We have completed working with the IANA designated expert and 
> have gotten the new Link Relation published in the Link Relation 
> registry. We have uploaded a new version of the draft to align with 
> the naming convention of the Link Registry (use of hyphens in the Link 
> Relation name). We feel this document has received enough review from 
> the Working Group and IANA and think it is ready for WGLC.
>
> Here is the link to the latest revision of the draft:
> https://datatracker.ietf.org/doc/html/draft-ietf-asap-siptrunkingcapability-link-01
>
>
> Thanks,
>
> Derek
>
> --
>
> Derek Engi
>
> deengi@cisco.com
>
>

v2.23.0 | Report a Bug | By Email