[sipcore] Fwd: WG Action: Formed Automatic SIP trunking And Peering (asap)
"Murray S. Kucherawy" <superuser@gmail.com> Sun, 26 July 2020 18:42 UTC
Return-Path: <superuser@gmail.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 754553A13A8 for <sipcore@ietfa.amsl.com>; Sun, 26 Jul 2020 11:42:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 fBj9RuAYhqOu for <sipcore@ietfa.amsl.com>; Sun, 26 Jul 2020 11:42:01 -0700 (PDT)
Received: from mail-vk1-xa2c.google.com (mail-vk1-xa2c.google.com [IPv6:2607:f8b0:4864:20::a2c]) (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 0D08D3A13A7 for <sipcore@ietf.org>; Sun, 26 Jul 2020 11:42:01 -0700 (PDT)
Received: by mail-vk1-xa2c.google.com with SMTP id g22so3294882vke.9 for <sipcore@ietf.org>; Sun, 26 Jul 2020 11:42:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=HdmojTqa0/hUznyjlr1GWXCeOcxn+t/VbdtobjvcBRM=; b=YLT1dzuxdswJ0kCThDTYjTPJQsQJciwLzeu0ZBLu74YbQ4x6csiu5Fia8hjiHa1bCd cc3SeJ0swqdR41uPyilEc4/fQEHEmm24KU8dir107lVFXLdngYBzMwZZFd9ojqBA7INZ K/1OSFqxbD9txgRC2M3odJe6yTADVgCY/TWnBrxAhJPuaYI8tguSoKu8YU7aDrb79kNH /ZfqJKmJFXdQJgCYmguqbB6Jn+5Xt5oXLoTreyVwBfCwQczRYBrnREmp9lEISA3w2oRP lJgs5fKEeqmTCnumNi9mc5AufuOdWWt7arBSIYur4Qkh2qr5ZMe7hNd9cyL+ttFTp45w MLew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=HdmojTqa0/hUznyjlr1GWXCeOcxn+t/VbdtobjvcBRM=; b=AR1p5pvvYjTdJXSMbLfWM2cAUzYI32I/YZonOEsmOlTMr0jGCsDImzllkS+8mKtswz HYqBfIwfJdDkCeK89ZTf/DAsppT2RyJPieF7BjktP4P/Lo7Fo504SBLxL8tXsoSTQayM LrN5u/wZwbzQNSXZrKfR+1NnuVqbJOax49OeKvvtkwjaehh2WO83EbqWCZZ3EY2HZtvw 7K1JtavspYzfxvvOwmFRlCvUN/U07+G+/PTERle1gN2gYFUOI9zAh+tw/b5lZ5zmBgEe M4rooGsxWZaMDbW1f2xizU6U9FP2oG1/VNSUBjn4m03G17LIjAxDumufI9IltvU936qd X9dg==
X-Gm-Message-State: AOAM532UbcSwvbYHXkPSXeB+6GHR7usF6g5MwocpiJk3s/z+iV0Xvdlo odKWcCdDoLCNZPcWDjk4V46L+Sw3sf/oh6HgsfXB/g==
X-Google-Smtp-Source: ABdhPJw7eBCVlDAZm1Fg6WhDGBva2sajp6HQ038/L4rANzF8Xk9xLa8RzYLobDTpntFtgwyqFpboWc1k543oRAQQX9Y=
X-Received: by 2002:a1f:9a85:: with SMTP id c127mr14391123vke.8.1595788919658; Sun, 26 Jul 2020 11:41:59 -0700 (PDT)
MIME-Version: 1.0
References: <159562615817.8487.8157656164577705814@ietfa.amsl.com>
In-Reply-To: <159562615817.8487.8157656164577705814@ietfa.amsl.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Sun, 26 Jul 2020 11:41:49 -0700
Message-ID: <CAL0qLwbLMfJuCD8_SmLWqhZTDRWwhD7YfGRAM0Zr=kksDxhb4A@mail.gmail.com>
To: sipcore@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b15d1705ab5c8f13"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/qt0oeFjslRy6Sq4EdcrftyHveZk>
Subject: [sipcore] Fwd: WG Action: Formed Automatic SIP trunking And Peering (asap)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jul 2020 18:42:04 -0000
Of possible interest to this community. -MSK ---------- Forwarded message --------- From: The IESG <iesg-secretary@ietf.org> Date: Fri, Jul 24, 2020 at 2:29 PM Subject: WG Action: Formed Automatic SIP trunking And Peering (asap) To: IETF-Announce <ietf-announce@ietf.org> Cc: <asap-chairs@ietf.org>, <asap@ietf.org>, The IESG <iesg@ietf.org>, < dispatch-chairs@ietf.org> A new IETF WG has been formed in the Applications and Real-Time Area. For additional information, please contact the Area Directors or the WG Chairs. Automatic SIP trunking And Peering (asap) ----------------------------------------------------------------------- Current status: Active WG Chairs: Adam Roach <adam@nostrum.com> Gonzalo Salgueiro <gsalguei@cisco.com> Assigned Area Director: Murray Kucherawy <superuser@gmail.com> Applications and Real-Time Area Directors: Barry Leiba <barryleiba@computer.org> Murray Kucherawy <superuser@gmail.com> Mailing list: Address: asap@ietf.org To subscribe: https://www.ietf.org/mailman/listinfo/asap Archive: https://mailarchive.ietf.org/arch/browse/asap/ Group page: https://datatracker.ietf.org/group/asap/ Charter: https://datatracker.ietf.org/doc/charter-ietf-asap/ The deployment of a Session Initiation Protocol (SIP)-based infrastructure in enterprise and service provider communication networks has been gradually increasing over the last few years. Consequently, direct IP peering between enterprise and service provider networks is replacing traditional methods of interconnection between these networks, such as analog lines and time-division multiplexing (TDM)-based digital circuits. Currently published standards provide a strong foundation over which direct IP peering can be realized. However, given the sheer number of these standards, it is often unclear which behavioural subsets, extensions to baseline protocols and operating principles ought to be configured by the enterprise network administrator to ensure successful IP peering with a SIP service provider network. This lack of context often leads to interoperability issues between enterprise and service provider SIP networks. As a result, a significant amount of time is spent by enterprise network administrators in troubleshooting these interoperability issues individually or with enterprise equipment manufacturer and service provider support teams. Consequently, there is an increase in the time taken to deploy SIP trunking between enterprise and service provider networks. The ASAP working group will define a descriptive capability set, which is populated by a SIP service provider, and which, when communicated to an enterprise network, encapsulates sufficient information to set up SIP trunking with the service provider network. In addition to defining a descriptive capability set, the ASAP working group will define a data model for the capability set, a service discovery mechanism and a transport mechanism for the capability set. The aforementioned deliverables of the ASAP working group are collectively referred to as “SIP Auto Peer”. The scope of the ASAP working group is: * A capability set that encapsulates sufficient information to ensure smooth IP peering between enterprise and service provider SIP networks. * A data model for the capability set. * An HTTPS-based transport mechanism for the capability set. * A mechanism to discover the server(s) in the SIP service provider network that hosts the capability set. * A mechanism to extend the data model to allow the encoding of proprietary parameters. The following are out of scope: * Extensions to SIP that enable an enterprise network to solicit and obtain a descriptive capability set from a SIP service provider. * A workflow/mechanism that allows service providers to directly configure devices in the enterprise network. The group will produce: * Specification for SIP Auto Peer This group will co-ordinate with the SIPCORE working group and the SIPConnect efforts carried out by the SIP Forum. Milestones: Jun 2021 - SIP Automatic Peering specification submitted for publication to the IESG.
- [sipcore] Fwd: WG Action: Formed Automatic SIP tr… Murray S. Kucherawy