IETF Logo Mail Archive

Re: [Asap] Call for WG adoption: draft-engi-siptrunkingcapability-link (was Re: Update: Draft for link relation type

"A. Jean Mahoney" <mahoney@nostrum.com> Wed, 22 June 2022 23:21 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 E7D59C16477F for <asap@ietfa.amsl.com>; Wed, 22 Jun 2022 16:21:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.964
X-Spam-Level:
X-Spam-Status: No, score=-3.964 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=-1.876, RCVD_IN_DNSWL_BLOCKED=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZIdit6kKjpnL for <asap@ietfa.amsl.com>; Wed, 22 Jun 2022 16:21:29 -0700 (PDT)
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 5D658C16477B for <asap@ietf.org>; Wed, 22 Jun 2022 16:21:29 -0700 (PDT)
Received: from [192.168.1.252] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.17.1) with ESMTPSA id 25MNLP7P026718 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <asap@ietf.org>; Wed, 22 Jun 2022 18:21:26 -0500 (CDT) (envelope-from mahoney@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1655940086; bh=x6eJKj1SO7pBuuduxjAk6Zy/ged/R8gUoMB0BdBU570=; h=Date:Subject:To:References:From:In-Reply-To; b=QRCfgDv3g5gMvkDwGD9Zvq2CG+DDsBJhFtRaHlYCTA9U3D1zHPJirnx5EIIhnXoW9 nxHYSSMp1RXH1rSotgWeow0fvm9wHGTXkEz+ToLxDuwVOJyhBPt+zyA2WzKIrwoUbX D9BsFiVsADWEeeNYQ8lG24Q776n7Eu2zq2+xot6I=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.252]
Message-ID: <d574b6f3-af8a-0c47-f66d-72eac56982f2@nostrum.com>
Date: Wed, 22 Jun 2022 18:21:20 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: asap@ietf.org
References: <BYAPR11MB28214607109D0905D15E2E42DD2F9@BYAPR11MB2821.namprd11.prod.outlook.com> <5F0F7B94-4D90-4801-8C0D-516960259B3D@gmail.com> <7a0ce5cc-e2f0-6447-6b09-179a554ccb34@nostrum.com> <0906e336-5439-3c85-8d99-acef21bb1ac9@nostrum.com>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
In-Reply-To: <0906e336-5439-3c85-8d99-acef21bb1ac9@nostrum.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/asap/wW9o6XaZV6yAG0x8toofKzwu74E>
Subject: Re: [Asap] Call for WG adoption: draft-engi-siptrunkingcapability-link (was Re: Update: Draft for link relation type
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: Wed, 22 Jun 2022 23:21:33 -0000

Hi all,

Since there were no comments received, either for or against, the chairs 
can't call consensus on adopting this as a WG document.

The deadline has been extended -- please provide feedback by July 8th.

Thanks!
Jean


On 6/16/22 8:49 AM, A. Jean Mahoney wrote:
> Hi all,
> 
> The mailing list hasn't seen any comments on this document so far. Are 
> there any objections? Anyone have feedback?
> 
> Thanks!
> Jean
> 
> On 6/1/22 6:26 PM, A. Jean Mahoney wrote:
>> Hi all,
>>
>> As discussed at IETF 111 and confirmed on list [1], the WG was in 
>> favor of defining and registering a link relation type.
>>
>> Please provide feedback on whether this document should be adopted by 
>> the working group by June 17th.
>>
>> Thanks!
>> Jean, as co-chair
>>
>> [1] 
>> https://mailarchive.ietf.org/arch/msg/asap/fA48N343wIQGjpoaDkbQcEO0_QY/
>>
>> On 5/20/22 12:17 AM, Kaustubh Inamdar wrote:
>>> Hi All,
>>> A  draft that defines a new link relation type - namely 
>>> ‘sipTrunkingCapabilities’,  has been uploaded and can be found at the 
>>> following URL:
>>> https://datatracker.ietf.org/doc/html/draft-engi-siptrunkingcapability-link 
>>> <https://datatracker.ietf.org/doc/html/draft-engi-siptrunkingcapability-link> 
>>>
>>>
>>> The primary reason for defining a new relation type in the context of 
>>> ASAP is to ensure provisions for a service discovery mechanism are 
>>> made. A service discover mechanism (leveraging the new link relation 
>>> type and webFinger) lends the sip auto peer framework better to 
>>> automation - from discovering the capability server to provisioning 
>>> the enterprise edge element.
>>>
>>> Any comments or observations on the link relation draft are welcome.
>>>
>>> Thanks,
>>> Kaustubh
>>>
>>>> On 10-Feb-2022, at 12:26 PM, Sreekanth Narayanan (sreenara) 
>>>> <sreenara=40cisco.com@dmarc.ietf.org 
>>>> <mailto:sreenara=40cisco.com@dmarc.ietf.org>> wrote:
>>>>
>>>> Hi All,
>>>> Just wanted to provide an update on the ASAP effort to the larger 
>>>> group. We are currently working on the second draft that defines a 
>>>> link relation type for the capabilitySet in order to complete the 
>>>> discovery approach with WebFinger in the ASAP configuration 
>>>> workflow. The first version of this draft should be ready in a 
>>>> couple of weeks from now. We will send a follow-up email notifying 
>>>> the group regarding publication.
>>>> Regards
>>>> Sreekanth
>>>> -- 
>>>> Asap mailing list
>>>> Asap@ietf.org <mailto:Asap@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/asap 
>>>> <https://www.ietf.org/mailman/listinfo/asap>
>>>
>>>
>>
>

v2.23.0 | Report a Bug | By Email