draft-ietf-asap-sip-auto-peer-04.txt		draft-ietf-asap-sip-auto-peer-05.txt
	ASAP K. Inamdar		ASAP K. Inamdar
	Internet-Draft Unaffiliated		Internet-Draft Unaffiliated
	Intended status: Standards Track S. Narayanan		Intended status: Standards Track S. Narayanan
	Expires: 27 April 2022 C. Jennings		Expires: 23 October 2022 C. Jennings
	Cisco Systems		Cisco Systems
	24 October 2021		21 April 2022
	Automatic Peering for SIP Trunks		Automatic Peering for SIP Trunks
	draft-ietf-asap-sip-auto-peer-04		draft-ietf-asap-sip-auto-peer-05
	Abstract		Abstract
	This draft specifies a configuration workflow to enable enterprise		This draft specifies a configuration workflow to enable enterprise
	Session Initiation Protocol (SIP) networks to solicit the capability		Session Initiation Protocol (SIP) networks to solicit the capability
	set of a SIP service provider network. The capability set can		set of a SIP service provider network. The capability set can
	subsequently be used to configure features and services on the		subsequently be used to configure features and services on the
	enterprise edge element, such as a Session Border Controller (SBC),		enterprise edge element, such as a Session Border Controller (SBC),
	to ensure smooth peering between enterprise and service provider		to ensure smooth peering between enterprise and service provider
	networks.		networks.
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on 27 April 2022.		This Internet-Draft will expire on 23 October 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2022 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	and restrictions with respect to this document. Code Components		and restrictions with respect to this document. Code Components
	extracted from this document must include Simplified BSD License text		extracted from this document must include Revised BSD License text as
	as described in Section 4.e of the Trust Legal Provisions and are		described in Section 4.e of the Trust Legal Provisions and are
	provided without warranty as described in the Simplified BSD License.		provided without warranty as described in the Revised BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Overview of Operations . . . . . . . . . . . . . . . . . . . 3		2. Overview of Operations . . . . . . . . . . . . . . . . . . . 3
	2.1. Reference Architecture . . . . . . . . . . . . . . . . . 3		2.1. Reference Architecture . . . . . . . . . . . . . . . . . 3
	2.2. Configuration Workflow . . . . . . . . . . . . . . . . . 5		2.2. Configuration Workflow . . . . . . . . . . . . . . . . . 5
	2.3. Transport . . . . . . . . . . . . . . . . . . . . . . . . 6		2.3. Transport . . . . . . . . . . . . . . . . . . . . . . . . 6
	3. Conventions and Terminology . . . . . . . . . . . . . . . . . 8		3. Conventions and Terminology . . . . . . . . . . . . . . . . . 8
	4. HTTP Transport . . . . . . . . . . . . . . . . . . . . . . . 8		4. HTTP Transport . . . . . . . . . . . . . . . . . . . . . . . 8
	skipping to change at page 11, line 43 ¶		skipping to change at page 11, line 43 ¶
	2. Discovery using the Webfinger Protocol		2. Discovery using the Webfinger Protocol
	The complete HTTPS URLs to be used when authenticating the enterprise		The complete HTTPS URLs to be used when authenticating the enterprise
	edge element (optional) and obtaining the SIP service provider		edge element (optional) and obtaining the SIP service provider
	capability set can be obtained from the SIP service provider		capability set can be obtained from the SIP service provider
	beforehand and entered into the edge element manually via some		beforehand and entered into the edge element manually via some
	interface - for example, a CLI or GUI.		interface - for example, a CLI or GUI.
	However, if the resource URL is unknown to the administrator (and by		However, if the resource URL is unknown to the administrator (and by
	extension of that to the edge element), the WebFinger protocol		extension of that to the edge element), the WebFinger protocol
	[RFC7033] may be leveraged.		[RFC7033] and the 'sipTrunkingCapability' [sipTrunkCapability] link
			relation type may be leveraged.
	If an enterprise edge element attempts to discover the URL of the		If an enterprise edge element attempts to discover the URL of the
	endpoints hosted in the ssp1.example.com domain, it issues the		endpoints hosted in the ssp1.example.com domain, it issues the
	following request (line wraps are for display purposes only).		following request (line wraps are for display purposes only).
	GET /.well-known/webfinger?		GET /.well-known/webfinger?
	resource=http%3A%2F%2Fssp1.example.com		resource=http%3A%2F%2Fssp1.example.com
	rel=capabilitySet		rel=sipTrunkingCapability
	HTTP/1.1		HTTP/1.1
	Host: ssp1.example.com		Host: ssp1.example.com
	HTTP/1.1 200 OK		HTTP/1.1 200 OK
	Access-Control-Allow-Origin: *		Access-Control-Allow-Origin: *
	Content-Type: application/jrd+json		Content-Type: application/jrd+json
	{		{
	"subject" : "http://ssp1.example.com",		"subject" : "http://ssp1.example.com",
	"links" :		"links" :
	[		[
	{		{
	"rel" : "capabilitySet",		"rel" : "sipTrunkingCapability",
	"href" :		"href" :
	"https://capserver.ssp1.com/capserver/capdoc.json"		"https://capserver.ssp1.com/capserver/capdoc.json"
	},		},
	]		]
	}		}
	Once the target URI is obtained by an enterprise telephony network,		Once the target URI is obtained by an enterprise telephony network,
	the URI may be dereferenced to obtain a unique capability set		the URI may be dereferenced to obtain a unique capability set
	document that is specific to that given enterprise telephony network.		document that is specific to that given enterprise telephony network.
	The ITSP may use credentials to determine the identity of the		The ITSP may use credentials to determine the identity of the
	skipping to change at page 39, line 10 ¶		skipping to change at page 39, line 10 ¶
	[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol		[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
	Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,		Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
	<https://www.rfc-editor.org/info/rfc8446>.		<https://www.rfc-editor.org/info/rfc8446>.
	[SIP-Connect-TR]		[SIP-Connect-TR]
	"SIP Connect Technical Recommendation",		"SIP Connect Technical Recommendation",
	<https://www.sipforum.org/download/sipconnect-technical-		<https://www.sipforum.org/download/sipconnect-technical-
	recommendation-version-2-0/?wpdmdl=2818>.		recommendation-version-2-0/?wpdmdl=2818>.
			[sipTrunkCapability]
			"The 'sipTrunkingCapability' Link Relation Type",
			<https://datatracker.ietf.org/doc/html/draft-engi-
			siptrunkingcapability-link>.
	Authors' Addresses		Authors' Addresses
	Kaustubh Inamdar		Kaustubh Inamdar
	Unaffiliated		Unaffiliated
	Email: kaustubh.ietf@gmail.com		Email: kaustubh.ietf@gmail.com
	Sreekanth Narayanan		Sreekanth Narayanan
	Cisco Systems		Cisco Systems
	Email: sreenara@cisco.com		Email: sreenara@cisco.com
	Cullen Jennings		Cullen Jennings
	Cisco Systems		Cisco Systems
	Email: fluffy@iii.ca		Email: fluffy@iii.ca
End of changes. 13 change blocks.
	14 lines changed or deleted		17 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/