< draft-ietf-martini-gin-09.txt		draft-ietf-martini-gin-10.txt >
	MARTINI WG A. B. Roach		MARTINI WG A. B. Roach
	Internet-Draft Tekelec		Internet-Draft Tekelec
	Updates: 3680 (if approved) September 28, 2010		Updates: 3680 (if approved) October 18, 2010
	Intended status: Standards Track		Intended status: Standards Track
	Expires: April 1, 2011		Expires: April 21, 2011
	Registration for Multiple Phone Numbers in the Session Initiation		Registration for Multiple Phone Numbers in the Session Initiation
	Protocol (SIP)		Protocol (SIP)
	draft-ietf-martini-gin-09		draft-ietf-martini-gin-10
	Abstract		Abstract
	This document defines a mechanism by which a SIP server acting as a		This document defines a mechanism by which a SIP server acting as a
	traditional Private Branch Exchange (SIP-PBX) can register with a SIP		traditional Private Branch Exchange (SIP-PBX) can register with a SIP
	Service Provider (SSP) to receive phone calls for UAs designated by		Service Provider (SSP) to receive phone calls for UAs designated by
	phone numbers. In order to function properly, this mechanism relies		phone numbers. In order to function properly, this mechanism relies
	on the fact that the phone numbers are fully qualified and globally		on the fact that the phone numbers are fully qualified and globally
	unique.		unique.
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	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 http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 April 1, 2011.		This Internet-Draft will expire on April 21, 2011.
	Copyright Notice		Copyright Notice
	Copyright (c) 2010 IETF Trust and the persons identified as the		Copyright (c) 2010 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		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 9, line 24 ¶		skipping to change at page 9, line 24 ¶
	7.1. Globally Routable User-Agent URIs (GRUU)		7.1. Globally Routable User-Agent URIs (GRUU)
	To enable advanced services to work with UAs behind a SIP-PBX, it is		To enable advanced services to work with UAs behind a SIP-PBX, it is
	important that the GRUU mechanism defined by RFC 5627 [17] work		important that the GRUU mechanism defined by RFC 5627 [17] work
	correctly with the mechanism defined by this document -- that is,		correctly with the mechanism defined by this document -- that is,
	that User Agents served by the SIP-PBX can acquire and use GRUUs for		that User Agents served by the SIP-PBX can acquire and use GRUUs for
	their own use.		their own use.
	7.1.1. Public GRUUs		7.1.1. Public GRUUs
	Open Issue: This section needs to call out the level of support		Support of public GRUUs is optional in SSPs and SIP-PBXes.
	required of GIN systems with regards to public GRUUs. This issue is
	being resolved on the MARTINI mailing list.
	When a SIP-PBX registers a Bulk Number Contact (a Contact with a		When a SIP-PBX registers a Bulk Number Contact (a Contact with a
	"bnc" parameter), and also invokes GRUU procedures for that Contact		"bnc" parameter), and also invokes GRUU procedures for that Contact
	during registration, then the SSP will assign a public GRUU to the		during registration, then the SSP will assign a public GRUU to the
	SIP-PBX in the normal fashion. Because the URI being registered		SIP-PBX in the normal fashion. Because the URI being registered
	contains a "bnc" parameter, the GRUU will also contain a "bnc"		contains a "bnc" parameter, the GRUU will also contain a "bnc"
	parameter. In particular, this means that the GRUU will not contain		parameter. In particular, this means that the GRUU will not contain
	a user portion.		a user portion.
	When a UA registers a contact with the SIP-PBX using GRUU procedures,		When a UA registers a contact with the SIP-PBX using GRUU procedures,
End of changes. 5 change blocks.
	7 lines changed or deleted		5 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/