IETF Logo Mail Archive

Re: [dispatch] PROPOSED CHARTER FOR ASAP (Automatic SIP trunking And Peering)

Cullen Jennings <fluffy@iii.ca> Thu, 09 January 2020 23:30 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 966C7120830 for <dispatch@ietfa.amsl.com>; Thu, 9 Jan 2020 15:30:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 KZgiKv6rjMUS for <dispatch@ietfa.amsl.com>; Thu, 9 Jan 2020 15:30:28 -0800 (PST)
Received: from smtp93.iad3a.emailsrvr.com (smtp93.iad3a.emailsrvr.com [173.203.187.93]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75A3212003E for <dispatch@ietf.org>; Thu, 9 Jan 2020 15:30:28 -0800 (PST)
X-Auth-ID: fluffy@iii.ca
Received: by smtp12.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 1F08A24E4C; Thu, 9 Jan 2020 18:30:27 -0500 (EST)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.91] (d75-159-246-1.abhsia.telus.net [75.159.246.1]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Thu, 09 Jan 2020 18:30:27 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail=_04B909F4-ECA9-4C9B-BDCF-42D8AAA33ABF"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <AM0PR07MB3987F4A6F92302E1776D477C933E0@AM0PR07MB3987.eurprd07.prod.outlook.com>
Date: Thu, 09 Jan 2020 16:30:25 -0700
Cc: Ben Campbell <ben@nostrum.com>, "Kaustubh Inamdar (kinamdar)" <kinamdar@cisco.com>, "dispatch@ietf.org" <dispatch@ietf.org>, "dispatch-chairs@ietf.org" <dispatch-chairs@ietf.org>
Message-Id: <8FF28A00-F936-44F4-BC16-CBF1E43827C8@iii.ca>
References: <8B4A804A-102E-4877-8C21-BF667B19BAFA@cisco.com> <085E1A7A-5EDE-4666-BE01-574DDBC9049E@cisco.com> <4434118C-216F-4462-81EB-D9187F8E2477@nostrum.com> <DFFF269F-DFF4-4FCB-B3C3-A51916E845A1@nostrum.com> <AM0PR07MB3987F4A6F92302E1776D477C933E0@AM0PR07MB3987.eurprd07.prod.outlook.com>
To: Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/Cva5p7QXKydeG47zv-8mhrIMdok>
Subject: Re: [dispatch] PROPOSED CHARTER FOR ASAP (Automatic SIP trunking And Peering)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2020 23:30:32 -0000


> On Jan 8, 2020, at 4:08 PM, Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org> wrote:
> 
> Hi,
> 
> Shouldn't the charter also mention why existing feature- and extension indication mechanisms would not work? The way the text is written now one could think that SIP does not providing mechanisms for indicating support of features and extensions...
> 
> Regards,
> 
> Christer

Thoughts on how to clear up this text? As sip does provide indication of support of some types of things, we should certainly not say it does not. This should meet the truth in advertising.  I think there are some types of configuration that is pretty hard to do in SIP. For example, where to send the SIP message too.

v2.23.0 | Report a Bug | By Email