Re: [martini] draft-ietf-martini-reqs-06.txt: req 4: "on behalf of AOR".

Paul Kyzivat <pkyzivat@cisco.com> Tue, 11 May 2010 14:17 UTC

Return-Path: <pkyzivat@cisco.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 D96DB3A6D11 for <martini@core3.amsl.com>; Tue, 11 May 2010 07:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.392
X-Spam-Level:
X-Spam-Status: No, score=-9.392 tagged_above=-999 required=5 tests=[AWL=-0.509, BAYES_05=-1.11, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227]
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 oSDnnY35fb+W for <martini@core3.amsl.com>; Tue, 11 May 2010 07:17:01 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id E6E623A68A0 for <martini@ietf.org>; Tue, 11 May 2010 07:14:50 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMsC6UtAZnwN/2dsb2JhbACeK3GhUZleglqCNgQ
X-IronPort-AV: E=Sophos;i="4.53,207,1272844800"; d="scan'208";a="110038542"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 11 May 2010 14:14:39 +0000
Received: from [161.44.174.156] (dhcp-161-44-174-156.cisco.com [161.44.174.156]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o4BEEdCm008244; Tue, 11 May 2010 14:14:39 GMT
Message-ID: <4BE96650.9010001@cisco.com>
Date: Tue, 11 May 2010 10:14:40 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Martien Huysmans <martien.huysmans@ericsson.com>
References: <B5CE2B521539624E8364D395B6F76B5C1DCF16D6AC@ESESSCMS0356.eemea.ericsson.se> <A444A0F8084434499206E78C106220CAE34B47CF@MCHP058A.global-ad.net> <B5CE2B521539624E8364D395B6F76B5C1DCF16E1CE@ESESSCMS0356.eemea.ericsson.se> <4BE82159.5020303@cisco.com> <B5CE2B521539624E8364D395B6F76B5C1DCF1E5EBF@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <B5CE2B521539624E8364D395B6F76B5C1DCF1E5EBF@ESESSCMS0356.eemea.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] draft-ietf-martini-reqs-06.txt: req 4: "on behalf of AOR".
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: Tue, 11 May 2010 14:17:04 -0000

Martin,

I'm happy with what you and John worked out.

But just in the interest of closing this discussion on behalf of 
"behalf" - 3261 section 10.2 says:

    REGISTER requests add, remove, and query bindings.  A REGISTER
    request can add a new binding between an address-of-record and one or
    more contact addresses.  Registration on behalf of a particular
    address-of-record can be performed by a suitably authorized third
    party.  A client can also remove previous bindings or query to
    determine which bindings are currently in place for an address-of-
    record.

The use of "on behalf" in that paragraph may be unfortunate, but it 
seems clear to be that the "on behalf" is referring to the AOR that is 
the target of registration, and not to the identity of the party that is 
doing the registration. Consider the following variations that might 
have been said:

1) Registration on behalf of a particular
    address-of-record can be performed by a suitably authorized third
    party.

2) Registration (for/with/to) a particular
    address-of-record can be performed on behalf of a suitably
    authorized third party.

3) Registration on behalf of a particular
    address-of-record can be performed by a user agent representing
    that address-of-record.

Of those, (1) is the as-written case, talking about third party 
registration. (2) shifts the use of "on behalf of" to refer to the third 
party. I expect this is they way you have been interpreting it. Its 
also, IMO, a more natural way of using "on behalf of". (3) is applying 
the original phrasing to first party registration. It still "works".

I had to go back and study this in 3261 to be certain of this. But I 
presume it was this usage that John was copying in REQ 4. Because of the 
precedent I did not have an issue with it. But phrasing that doesn't use 
"on behalf of" will probably help prevent confusion.

I've personally always had difficulty deciding how to phrase this. And 
I've indicated that in (2) by showing the alternatives to/with/for. None 
of them seem ideal, though I usually use "to".

	Thanks,
	Paul

Martien Huysmans wrote:
> Paul
> 
> RFC3261, section 10.2 mentions the on-behalf-of registration or third-party registration.
> I think that in case, the From-URI is different, not the To-URI.
> 
> RFC3261, section 10.2 states:
> 
>       From: The From header field contains the address-of-record of the
>            person responsible for the registration.  The value is the
>            same as the To header field unless the request is a third-
>            party registration.
> 
> You propose to change the wording of REQ 4.
> For me the discussion started with trying to understand WHY the "on behalf of" 
> was included in the first place.
> 
> I think you text is probably equivelant to what I an John discussed in another email.
> But following the style of the requirement document, I rather use AOR, then talk about
> a specific parameter in the REGISTER.
> 
> /Martien
> 
> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> Sent: Monday, May 10, 2010 5:08 PM
> To: Martien Huysmans
> Cc: Elwell, John; martini@ietf.org
> Subject: Re: [martini] draft-ietf-martini-reqs-06.txt: req 4: "on behalf of AOR".
> 
> Maybe I'm missing something, because I don't understand the issue.
> AFAIK the use of "on behalf of X" in this requirement is just another way of saying "the To-URI of the REGISTER will be X". IOW, its equivalent to the following rewording:
> 
>     REQ4 - The mechanism MUST NOT prevent UAs attached to a SIP-PBX
>     registering with the SIP-PBX using a To-URI based on assigned
>     telephone numbers in order to receive requests targeted at those
>     telephone numbers, without needing to involve the SSP in the
>     registration process.
> 
> Section 10.2 of 3261 uses "on behalf of" in this same way.
> 
> 	Thanks,
> 	Paul
> 
> 
> Martien Huysmans wrote:
>> John
>>
>> The "problem" is trying to understand why the text includes "on behalf of".
>> This document is input for the other martini document and it should 
>> make sense to me or anybody else.
>>
>> I looked at RFC3261 on the usage of "on behalf of".
>> Section 10.2: 
>>    Registration on behalf of a particular address-of-record can be performed 
>>    by a suitably authorized third party. 
>> I have the impression that your text is not talking about "3rd party registration".
>> But I may be wrong.
>>
>> You asked for a proposition. Here is an attempt.
>>
>> 1) remove the sentence in section 1.
>>    Rationale: The information feels superluous compared to the 
>>    sentences before this sentence.
>>
>> 2) Update REQ4 to:
>>    The mechanism MUST allow an UA to register with a SIP-PBX 
>>    without needing to involve the SSP in the registration process,
>>    in order to receive requests targeted at assigned telephone numbers.
>>
>>    Rationale:
>>    - it uses MUST instead of "MUST NOT".
>>    - 3rd party registration is a "basic mechanims" according RFC3261. So
>>      no need to repeat that.
>>
>> /Martien
>>
>> -----Original Message-----
>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>> Sent: Friday, May 07, 2010 3:02 PM
>> To: Martien Huysmans; martini@ietf.org
>> Subject: RE: draft-ietf-martini-reqs-06.txt: req 4: "on behalf of AOR".
>>
>> Each UA that has credentials for a particular AOR can register a contact URI on behalf of that AOR. What is the problem with that? What preposition would you prefer?
>>
>> John
>>
>>> -----Original Message-----
>>> From: martini-bounces@ietf.org
>>> [mailto:martini-bounces@ietf.org] On Behalf Of Martien Huysmans
>>> Sent: 07 May 2010 07:54
>>> To: martini@ietf.org
>>> Subject: [martini] draft-ietf-martini-reqs-06.txt: req 4: "on behalf 
>>> of AOR".
>>>
>>> Question on draft-ietf-martini-reqs-06.txt. 
>>>  
>>> The text talks twice about "UAs register with the SIP-PBX on behalf 
>>> of the AORs concerned".
>>> What does this mean?
>>> How does an UA register with an SIP-PBX "on behalf of" an AOR?
>>>  
>>> /Martien
>>>  
>>>
>> _______________________________________________
>> martini mailing list
>> martini@ietf.org
>> https://www.ietf.org/mailman/listinfo/martini
>>
>