[martini] FW: GIN: 'reg' event package proposal
Martien Huysmans <martien.huysmans@ericsson.com> Mon, 28 June 2010 13:03 UTC
Return-Path: <martien.huysmans@ericsson.com>
X-Original-To: martini@core3.amsl.com
Delivered-To: martini@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 926D83A6A36 for <martini@core3.amsl.com>; Mon, 28 Jun 2010 06:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level:
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id THV2qgWzuaPf for <martini@core3.amsl.com>; Mon, 28 Jun 2010 06:03:54 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id D068628C138 for <martini@ietf.org>; Mon, 28 Jun 2010 06:03:28 -0700 (PDT)
X-AuditID: c1b4fb3d-b7b90ae00000278d-ea-4c289da968c3
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id A9.40.10125.9AD982C4; Mon, 28 Jun 2010 15:03:37 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.240]) by esessmw0247.eemea.ericsson.se ([10.2.3.116]) with mapi; Mon, 28 Jun 2010 15:03:37 +0200
From: Martien Huysmans <martien.huysmans@ericsson.com>
To: "martini@ietf.org" <martini@ietf.org>
Date: Mon, 28 Jun 2010 15:03:35 +0200
Thread-Topic: [martini] GIN: 'reg' event package proposal
Thread-Index: AcsPOmT7shBY3JQhT/yjxSbEz+djZwHhAgaAAADy/FA=
Message-ID: <B5CE2B521539624E8364D395B6F76B5C23D403A73A@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [martini] FW: GIN: 'reg' event package proposal
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of en-mass SIP PBX registration mechanisms <martini.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/martini>, <mailto:martini-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/martini>
List-Post: <mailto:martini@ietf.org>
List-Help: <mailto:martini-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/martini>, <mailto:martini-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jun 2010 13:03:55 -0000
Forgot to include martini@ietf.org in the To. -----Original Message----- From: Martien Huysmans Sent: Monday, June 28, 2010 2:46 PM To: 'Adam Roach' Subject: RE: [martini] GIN: 'reg' event package proposal Adam Assume that the pbx has a user, say sip:user1@pbx.com with corresponding SSP identity: sip:+12145550102@ssp.example.com. Then I guess that it's is upto the SIP-PBX to include both, if both are publicly-visible? Would the procedure below imply that a SIP-PBX could provide a different replies to a SUBSCRIBE for regvent depending on the RURI: - SUBSCRIBE sip:+12145550102@ssp.example.com as described below - SUBSCRIBE sip:user1@pbx.com with all AOR's included ? Do you see a similar rule for the Contact's included in the registration document? Regards Martien -----Original Message----- From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf Of Adam Roach Sent: Saturday, June 19, 2010 1:03 AM To: martini@ietf.org Subject: [martini] GIN: 'reg' event package proposal After giving things some thought and reading through the 'reg' event package RFC, I think things will only really work if the SIP-PBX puts the public (i.e. SSP) AOR into the registration document. I propose the following text (which will appear in the next version of GIN unless there is a constructive counter-proposal): When a SIP-PBX receives a registration event subscription addressed to an AOR that has been registered using the bulk registration mechanism described in this document, then the resulting registration information documents SHOULD contain an 'aor' attribute in its <registration/> element that corresponds to the AOR at the SSP. For example, consider a SIP-PBX that has registered with an SSP that has a domain of "ssp.example.com" The SIP-PBX used a contact of "sip:198.51.100.3:5060;bnc". After such registration is complete, a registration event subscription arriving at the SSP with a Request-URI of "sip:+12145550102@ssp.example.com" will be re-targeted to the SIP-PBX, with a Request-URI of "sip:+12145550102@198.51.100.3:5060". The resulting registration document created by the SIP-PBX would contain a <registration/> element with an "aor" attribute of "sip:+12145550102@ssp.example.com". This behavior ensures that subscribers external to the system (and unaware of GIN procedures) will be able to find the relevant information in the registration document (since they will be looking for the publicly-visible AOR, not the address used for sending information from the SSP to the SIP-PBX). Also, based on Paul's comments during Interim V regarding the potential ability for SSPs to form back-end subscriptions to SIP-PBXes for registration state, I propose loosening up the normative requirement about passing through reg event SUBSCRIBEs; everything after the word "unless" is new: If the SSP receives a SUBSCRIBE request for the registration event package with a Request-URI that indicates a contact registered via the "Bulk Number Contact" mechanism defined in this document, then the SSP MUST proxy that SUBSCRIBE to the SIP-PBX in the same way that is would proxy an INVITE bound for that AOR, unless the SSP has and can maintain a copy of complete, accurate, and up-to-date information from the SIP-PBX (e.g., through an active back-end subscription). Again, this text will appear in the next version of GIN unless there is a constructive counter-proposal. /a _______________________________________________ martini mailing list martini@ietf.org https://www.ietf.org/mailman/listinfo/martini
- [martini] GIN: 'reg' event package proposal Adam Roach
- [martini] FW: GIN: 'reg' event package proposal Martien Huysmans
- Re: [martini] FW: GIN: 'reg' event package propos… Martien Huysmans
- Re: [martini] FW: GIN: 'reg' event package propos… Adam Roach