
From trac@tools.ietf.org  Mon Mar  1 05:41:42 2010
Return-Path: <trac@tools.ietf.org>
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 920B43A8B1B for <martini@core3.amsl.com>; Mon,  1 Mar 2010 05:41:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 kvRzwhfdq3r2 for <martini@core3.amsl.com>; Mon,  1 Mar 2010 05:41:41 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) by core3.amsl.com (Postfix) with ESMTP id 0136B3A8B6D for <martini@ietf.org>; Mon,  1 Mar 2010 05:41:34 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nm5sM-00056H-19; Mon, 01 Mar 2010 05:41:34 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Mon, 01 Mar 2010 13:41:33 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/3#comment:1
Message-ID: <085.e75e6880bba727d2ff8bc34b0943691c@tools.ietf.org>
References: <076.528e2a835ae2d9054533d1ea46b03e16@tools.ietf.org>
X-Trac-Ticket-ID: 3
In-Reply-To: <076.528e2a835ae2d9054533d1ea46b03e16@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #3: Requirement for identity assertions
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 01 Mar 2010 13:41:42 -0000

#3: Requirement for identity assertions
------------------------------------------------+---------------------------
 Reporter:  john.elwell@…                       |       Owner:  john.elwell@…                     
     Type:  enhancement                         |      Status:  new                               
 Priority:  major                               |   Milestone:  milestone1                        
Component:  reqs                                |     Version:  1.0                               
 Severity:  In WG Last Call                     |    Keywords:                                    
------------------------------------------------+---------------------------
Changes (by john.elwell@…):

  * owner:  john.elwell@… => john.elwell@…


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/3#comment:1>
martini <http://tools.ietf.org/martini/>


From john.elwell@siemens-enterprise.com  Mon Mar  1 06:15:25 2010
Return-Path: <john.elwell@siemens-enterprise.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 D42363A8B6D for <martini@core3.amsl.com>; Mon,  1 Mar 2010 06:15:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_31=0.6]
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 xvdAVVHIPLqd for <martini@core3.amsl.com>; Mon,  1 Mar 2010 06:15:24 -0800 (PST)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 2AC8C3A8B72 for <martini@ietf.org>; Mon,  1 Mar 2010 06:15:15 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1048497; Mon, 1 Mar 2010 15:15:14 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id B69ED1EB82BC; Mon,  1 Mar 2010 15:15:14 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.57]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 1 Mar 2010 15:15:14 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Brian Lindsay <blindsay@nortel.com>, Tyler Parkin <tyler@foxfam.com>, Adam Roach <adam@nostrum.com>, Spencer Dawkins <spencer@wonderhamster.org>
Date: Mon, 1 Mar 2010 15:15:13 +0100
Thread-Topic: [martini] Middlebox needs - admitting inbound requests
Thread-Index: Acq3DhVedCe9ueLhSy6la+jrT0lQfwBp1v2wACTueKA=
Message-ID: <A444A0F8084434499206E78C106220CABBBA59EF@MCHP058A.global-ad.net>
References: <C7AC4291.14C39%adam@nostrum.com><99BF4620352B4F9C9E090F9004C31924@china.huawei.com><4B86F875.6070902@nostrum.com><00b101cab66c$3ce34150$430510ac@CORPORATE.VOX.NET><09B7DBFE70A9E24BBB21689DAD3A06141CB0F52A@zcarhxm1.corp.nortel.com> <00ca01cab67a$7fd21460$430510ac@CORPORATE.VOX.NET> <A444A0F8084434499206E78C106220CABBB22E97@MCHP058A.global-ad.net> <000901cab6f5$968a9df0$010c030a@CORPORATE.VOX.NET> <A444A0F8084434499206E78C106220CABBB232D7@MCHP058A.global-ad.net> <008201cab70e$0d82c6e0$010c030a@CORPORATE.VOX.NET> <09B7DBFE70A9E24BBB21689DAD3A06141CB5DF53@zcarhxm1.corp.nortel.com>
In-Reply-To: <09B7DBFE70A9E24BBB21689DAD3A06141CB5DF53@zcarhxm1.corp.nortel.com>
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
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, MARTINI <martini@ietf.org>
Subject: Re: [martini] Middlebox needs - admitting inbound requests
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, 01 Mar 2010 14:15:25 -0000

Yes, I would have expected a middlebox providing this NAT function on messa=
ge contents should be sufficiently stateful to allow the opposite to happen=
 in the reverse direction. I still have a hard time understanding why the m=
iddlebox needs explicit knowledge of registered AORs (user parts) in order =
accomplish this type of functionality.

John
=20

> -----Original Message-----
> From: Brian Lindsay [mailto:blindsay@nortel.com]=20
> Sent: 28 February 2010 20:52
> To: Tyler Parkin; Elwell, John; Adam Roach; Spencer Dawkins
> Cc: Bernard Aboba; MARTINI
> Subject: RE: [martini] Middlebox needs - admitting inbound requests
>=20
> Hi Tyler,
>=20
>   I believe some SBCs that "NAT" as you describe would (or=20
> could) use a
> unique port on the northbound side per registered entity. So the SBC
> would be able to maintain a mapping from the client-side=20
> contact/routing
> info to a unique northbound address/port that it would=20
> receive requests
> on (for requests towards the SIP PBX). In this case, there=20
> shouldn't be
> any problems routing the request.
>=20
>   Also, I think the MARTINI-Shaken approach wouldn't have a problem in
> this case either, since the domain portion of the request uri=20
> (from the
> "SSP") contains a domain name representing the enterprise/PBX, rather
> than an IP address derived from the contact.
>=20
>   Thanks
>      Brian
>=20
> -----Original Message-----
> From: Tyler Parkin [mailto:tyler@foxfam.com]=20
> Sent: Friday, February 26, 2010 1:04 PM
> To: Elwell, John; Lindsay, Brian (CAR:AR00); Adam Roach;=20
> Spencer Dawkins
> Cc: Bernard Aboba; MARTINI
> Subject: Re: [martini] Middlebox needs - admitting inbound requests
>=20
>=20
> > ----- Original Message -----
> > From: "Elwell, John" <john.elwell@siemens-enterprise.com>
> > To: "Tyler Parkin" <tyler@foxfam.com>; "Brian Lindsay"
> > <blindsay@nortel.com>; "Adam Roach" <adam@nostrum.com>; "Spencer=20
> > Dawkins"
> > <spencer@wonderhamster.org>
> > Cc: "Bernard Aboba" <bernard_aboba@hotmail.com>; "MARTINI"
> > <martini@ietf.org>
> > Sent: Friday, February 26, 2010 5:34 AM
> > Subject: RE: [martini] Middlebox needs - admitting inbound requests
> >
> >
> > Tyler,
> >
> > I found this thread a little mixed up between outbound=20
> requests from=20
> > the PBX and inbound requests  to the PBX, so I am not sure I=20
> > understood everything.
> > [tyler] sorry for the confusion, I think we're looking at it in=20
> > different directions... inbound to me is inbound to the=20
> SSP, where to=20
> > you inbound is to the PBX.  I guess we'll stick w/ inbound =3D to the=20
> > PBX
> >
> > As far as inbound request are concerned, I think with gin-01 the=20
> > problems you raise should be solvable, but it perhaps=20
> requires use of=20
> > Proxy-Require, as already discussed. The middlebox does not need to=20
> > know exactly which E.164s are implicitly registered, but=20
> when it gets=20
> > a request to the PBX's IP address (presumably with Route indicating=20
> > the IP address of the middlebox) it should assume the E.164 in the=20
> > user part is indeed a registered AOR.
> > [tyler] my point is that the middlebox doesn't get a request to the=20
> > PBX's IP address.
> [JRE] Why not? If the Contact URI contains the IP address (as in
> gin-01), this will be registered at the registrar and will be returned
> as the target of an inbound request to the PBX.
>=20
> > The softswitch/registrar generating the call doesn't know=20
> the PBX's IP
>=20
> > because it was masked during the initial registration.
> [JRE] Why would it be masked? I understand that the registrar=20
> would not
> see the IP address at the transport level from which the REGISTER
> request arrived at the middlebox, but it would see the IP=20
> address in the
> Contact URI.
> [Tyler] In most scenarios where a middlebox (aka SBC) exists, the SBC
> performs two-way NAT functions, and NAT's the headers/URI's=20
> for inbound
> and outbound messaging.  Therefore, a request received on the public
> side from user@PBXIP is sent to the registrar as=20
> user@SBCPRIVATEIP.  The
> oposite direction (SSP -> PBX) is received by the SBC as=20
> user@SSPIP and
> NAT'd to user@SBCPUBLICIP.
>=20
> > Any
> > requests from from the registrar/softswitch to the=20
> middlebox (destined
>=20
> > for the PBX) will only have user@middlebox, perhaps w/ a cookie.
> > The middelbox
> > needs to map user@middlebox to whatever IP/host originally=20
> registered.
> > Today, the middlebox keeps a cache where the initial (individual)=20
> > registration might be user@1.1.1.1, and the registration=20
> forwarded to=20
> > the registrar is user@2.2.2.2.  That way when the registrar sends a=20
> > request to the middlebox for user@2.2.2.2 it maps it to=20
> user@1.1.1.1=20
> > and all is good.
> > If the middelbox doesn't have knowledge of the user (because of=20
> > implicit),
> [JRE] Are you suggesting that each user behind the PBX would register
> with a different IP address, so you need to know whether it=20
> is user1 or
> user2 in order to send requests to 11.11.11.11 or 22.22.22.22? If so,
> that is not the scenario that MARTINI is addressing. MARTINI is
> addressing the case where requests to user1, user2 etc. on a given PBX
> all need to be routed to the PBX's IP address. So as long as the
> middlebox knows the request needs to go to the PBX, it doesn't need to
> know that particular user.
> [Tyler] Agreed, I shouldn't have used the term user.  The middlebox in
> this scenario wouldn't care about individual users, it's point of
> contact is the PBX.  All PBX's send register requests to the middlebox
> from different IP's/domains, granted.  After NAT, however, all the
> requests from the SBC to the registrar appear to come from=20
> the same IP.
> We NAT in both directions, which is pretty standard, so we=20
> don't expose
> core equipment to the public, and we don't expose end user IP's to
> peers.  Plus it allows virtual route tables internally and=20
> resolves any
> issues with overlapping address space.
>=20
> > it can't make the mapping unless it has something else to=20
> associate to
>=20
> > the original implicit reg (like a cookie, or knowledge of the=20
> > extensions).
> >
> > Now concerning outbound requests (this was what my earlier=20
> message was
>=20
> > about, although somewhere further back that got brought=20
> across to this
>=20
> > thread rather than the thread concerning outbound requests, so the=20
> > thread title was wrong). Assuming an entity has knowledge of=20
> > registered E.164 numbers, it is not clear to me how it=20
> would deal with
>=20
> > a request where the From/PAI in the request from the PBX is=20
> not one of
>=20
> > the implicitly registered ones. This can arise, for example, if the=20
> > request originates elsewhere in the enterprise and "breaks=20
> out" to the
>=20
> > SSP via this particular PBX. Or if the call originated=20
> elsewhere and=20
> > was forwarded by the PBX to the SSP. I appreciate that there may be=20
> > some arrangements between PBX and SSP where this is forbidden by=20
> > policy, but in the general case I would expect it to work,=20
> so that the
>=20
> > callee has a correct AOR to which it can make a return call.
> > [tyler] methods dealing with this situation today (A calls B, B=20
> > forwards the call to C) would use from=3DA and PAI=3DB, where B is a=20
> > registered endpoint (and billable by the SSP).  Not sure if that's=20
> > what you're asking?
> [JRE] Yes, that was what I was asking, and I know that it sometimes
> works the way you describe, but this is bad because PAI=3DB is=20
> wrong - it
> is not compliant with RFC 3325, since it is not the source of the
> request. If the callee used that to make a return call, the=20
> return call
> would arrive at the wrong place. For example, if a customer=20
> calls me on
> my office number and the PBX forwards it to my home via the SSP, if my
> phone stores the PAI as the caller's number and I try to make a return
> call, the return call goes to my office phone, not to my customer.
> [Tyler] The source of the forward leg of the call is B, not=20
> A.  Calling
> area requirements and n11 need to be based on B.  Why would the callee
> use PAI to return a call?  That would be in violation of 3325 as well
> since it would obviate any callerid blocking/suppression requirements.
> I guess whether the PBX should strip PAI before sending it to=20
> your phone
> is arguable.  Agreed, using PAI to assert a different ID than From
> (where from isn't private) might not strictly adhere to 3325, but I
> think alternate ID's vs suppressed ID's is splitting hairs a little.
>=20
> John=20
>=20
> =

From tyler@foxfam.com  Mon Mar  1 10:03:48 2010
Return-Path: <tyler@foxfam.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 1BE5728C3C6 for <martini@core3.amsl.com>; Mon,  1 Mar 2010 10:03:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_31=0.6, STOX_REPLY_TYPE=0.001]
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 9+777CuZ0idt for <martini@core3.amsl.com>; Mon,  1 Mar 2010 10:03:46 -0800 (PST)
Received: from smtp02.atlngahp.sys.nuvox.net (smtp-out2.atlngahp.sys.nuvox.net [70.43.63.19]) by core3.amsl.com (Postfix) with ESMTP id 98AF428C496 for <martini@ietf.org>; Mon,  1 Mar 2010 10:03:46 -0800 (PST)
Received: from LT6KW7CD1 (fw.newsouth.com [209.177.200.190]) by smtp02.atlngahp.sys.nuvox.net (8.13.1/8.13.1) with SMTP id o21I3efX007729; Mon, 1 Mar 2010 13:03:40 -0500
Message-ID: <000e01cab969$87ee3380$370510ac@CORPORATE.VOX.NET>
From: "Tyler Parkin" <tyler@foxfam.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Brian Lindsay" <blindsay@nortel.com>, "Adam Roach" <adam@nostrum.com>,  "Spencer Dawkins" <spencer@wonderhamster.org>
References: <C7AC4291.14C39%adam@nostrum.com><99BF4620352B4F9C9E090F9004C31924@china.huawei.com><4B86F875.6070902@nostrum.com><00b101cab66c$3ce34150$430510ac@CORPORATE.VOX.NET><09B7DBFE70A9E24BBB21689DAD3A06141CB0F52A@zcarhxm1.corp.nortel.com> <00ca01cab67a$7fd21460$430510ac@CORPORATE.VOX.NET> <A444A0F8084434499206E78C106220CABBB22E97@MCHP058A.global-ad.net> <000901cab6f5$968a9df0$010c030a@CORPORATE.VOX.NET> <A444A0F8084434499206E78C106220CABBB232D7@MCHP058A.global-ad.net> <008201cab70e$0d82c6e0$010c030a@CORPORATE.VOX.NET> <09B7DBFE70A9E24BBB21689DAD3A06141CB5DF53@zcarhxm1.corp.nortel.com> <A444A0F8084434499206E78C106220CABBBA59EF@MCHP058A.global-ad.net>
Date: Mon, 1 Mar 2010 13:03:40 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, MARTINI <martini@ietf.org>
Subject: Re: [martini] Middlebox needs - admitting inbound requests
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, 01 Mar 2010 18:03:48 -0000

All I asked is that the behavior of network elements beyond the PBX also be 
described in the draft.  Even within this forum we've had two different 
suggestions on how a middlebox *could* behave to support then GIN 
proposal... one involved different ports on the private side of the 
middlebox and the other included the use of a cookie.  I didn't say explicit 
knowledge of the extensions is the only method, only that the mechanism used 
between the middlebox(es) and the registrars should be defined in this 
document so that the implimentation is standardized.  IMO, without 
describing that behavior, this draft won't be widely (or at least quickly 
adopted) due to interop issues between other vendors in the call flow.

Regards,

Tyler


----- Original Message ----- 
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Brian Lindsay" <blindsay@nortel.com>; "Tyler Parkin" 
<tyler@foxfam.com>; "Adam Roach" <adam@nostrum.com>; "Spencer Dawkins" 
<spencer@wonderhamster.org>
Cc: "Bernard Aboba" <bernard_aboba@hotmail.com>; "MARTINI" 
<martini@ietf.org>
Sent: Monday, March 01, 2010 9:15 AM
Subject: RE: [martini] Middlebox needs - admitting inbound requests


Yes, I would have expected a middlebox providing this NAT function on 
message contents should be sufficiently stateful to allow the opposite to 
happen in the reverse direction. I still have a hard time understanding why 
the middlebox needs explicit knowledge of registered AORs (user parts) in 
order accomplish this type of functionality.

John


> -----Original Message-----
> From: Brian Lindsay [mailto:blindsay@nortel.com]
> Sent: 28 February 2010 20:52
> To: Tyler Parkin; Elwell, John; Adam Roach; Spencer Dawkins
> Cc: Bernard Aboba; MARTINI
> Subject: RE: [martini] Middlebox needs - admitting inbound requests
>
> Hi Tyler,
>
>   I believe some SBCs that "NAT" as you describe would (or
> could) use a
> unique port on the northbound side per registered entity. So the SBC
> would be able to maintain a mapping from the client-side
> contact/routing
> info to a unique northbound address/port that it would
> receive requests
> on (for requests towards the SIP PBX). In this case, there
> shouldn't be
> any problems routing the request.
>
>   Also, I think the MARTINI-Shaken approach wouldn't have a problem in
> this case either, since the domain portion of the request uri
> (from the
> "SSP") contains a domain name representing the enterprise/PBX, rather
> than an IP address derived from the contact.
>
>   Thanks
>      Brian
>
> -----Original Message-----
> From: Tyler Parkin [mailto:tyler@foxfam.com]
> Sent: Friday, February 26, 2010 1:04 PM
> To: Elwell, John; Lindsay, Brian (CAR:AR00); Adam Roach;
> Spencer Dawkins
> Cc: Bernard Aboba; MARTINI
> Subject: Re: [martini] Middlebox needs - admitting inbound requests
>
>
> > ----- Original Message -----
> > From: "Elwell, John" <john.elwell@siemens-enterprise.com>
> > To: "Tyler Parkin" <tyler@foxfam.com>; "Brian Lindsay"
> > <blindsay@nortel.com>; "Adam Roach" <adam@nostrum.com>; "Spencer
> > Dawkins"
> > <spencer@wonderhamster.org>
> > Cc: "Bernard Aboba" <bernard_aboba@hotmail.com>; "MARTINI"
> > <martini@ietf.org>
> > Sent: Friday, February 26, 2010 5:34 AM
> > Subject: RE: [martini] Middlebox needs - admitting inbound requests
> >
> >
> > Tyler,
> >
> > I found this thread a little mixed up between outbound
> requests from
> > the PBX and inbound requests  to the PBX, so I am not sure I
> > understood everything.
> > [tyler] sorry for the confusion, I think we're looking at it in
> > different directions... inbound to me is inbound to the
> SSP, where to
> > you inbound is to the PBX.  I guess we'll stick w/ inbound = to the
> > PBX
> >
> > As far as inbound request are concerned, I think with gin-01 the
> > problems you raise should be solvable, but it perhaps
> requires use of
> > Proxy-Require, as already discussed. The middlebox does not need to
> > know exactly which E.164s are implicitly registered, but
> when it gets
> > a request to the PBX's IP address (presumably with Route indicating
> > the IP address of the middlebox) it should assume the E.164 in the
> > user part is indeed a registered AOR.
> > [tyler] my point is that the middlebox doesn't get a request to the
> > PBX's IP address.
> [JRE] Why not? If the Contact URI contains the IP address (as in
> gin-01), this will be registered at the registrar and will be returned
> as the target of an inbound request to the PBX.
>
> > The softswitch/registrar generating the call doesn't know
> the PBX's IP
>
> > because it was masked during the initial registration.
> [JRE] Why would it be masked? I understand that the registrar
> would not
> see the IP address at the transport level from which the REGISTER
> request arrived at the middlebox, but it would see the IP
> address in the
> Contact URI.
> [Tyler] In most scenarios where a middlebox (aka SBC) exists, the SBC
> performs two-way NAT functions, and NAT's the headers/URI's
> for inbound
> and outbound messaging.  Therefore, a request received on the public
> side from user@PBXIP is sent to the registrar as
> user@SBCPRIVATEIP.  The
> oposite direction (SSP -> PBX) is received by the SBC as
> user@SSPIP and
> NAT'd to user@SBCPUBLICIP.
>
> > Any
> > requests from from the registrar/softswitch to the
> middlebox (destined
>
> > for the PBX) will only have user@middlebox, perhaps w/ a cookie.
> > The middelbox
> > needs to map user@middlebox to whatever IP/host originally
> registered.
> > Today, the middlebox keeps a cache where the initial (individual)
> > registration might be user@1.1.1.1, and the registration
> forwarded to
> > the registrar is user@2.2.2.2.  That way when the registrar sends a
> > request to the middlebox for user@2.2.2.2 it maps it to
> user@1.1.1.1
> > and all is good.
> > If the middelbox doesn't have knowledge of the user (because of
> > implicit),
> [JRE] Are you suggesting that each user behind the PBX would register
> with a different IP address, so you need to know whether it
> is user1 or
> user2 in order to send requests to 11.11.11.11 or 22.22.22.22? If so,
> that is not the scenario that MARTINI is addressing. MARTINI is
> addressing the case where requests to user1, user2 etc. on a given PBX
> all need to be routed to the PBX's IP address. So as long as the
> middlebox knows the request needs to go to the PBX, it doesn't need to
> know that particular user.
> [Tyler] Agreed, I shouldn't have used the term user.  The middlebox in
> this scenario wouldn't care about individual users, it's point of
> contact is the PBX.  All PBX's send register requests to the middlebox
> from different IP's/domains, granted.  After NAT, however, all the
> requests from the SBC to the registrar appear to come from
> the same IP.
> We NAT in both directions, which is pretty standard, so we
> don't expose
> core equipment to the public, and we don't expose end user IP's to
> peers.  Plus it allows virtual route tables internally and
> resolves any
> issues with overlapping address space.
>
> > it can't make the mapping unless it has something else to
> associate to
>
> > the original implicit reg (like a cookie, or knowledge of the
> > extensions).
> >
> > Now concerning outbound requests (this was what my earlier
> message was
>
> > about, although somewhere further back that got brought
> across to this
>
> > thread rather than the thread concerning outbound requests, so the
> > thread title was wrong). Assuming an entity has knowledge of
> > registered E.164 numbers, it is not clear to me how it
> would deal with
>
> > a request where the From/PAI in the request from the PBX is
> not one of
>
> > the implicitly registered ones. This can arise, for example, if the
> > request originates elsewhere in the enterprise and "breaks
> out" to the
>
> > SSP via this particular PBX. Or if the call originated
> elsewhere and
> > was forwarded by the PBX to the SSP. I appreciate that there may be
> > some arrangements between PBX and SSP where this is forbidden by
> > policy, but in the general case I would expect it to work,
> so that the
>
> > callee has a correct AOR to which it can make a return call.
> > [tyler] methods dealing with this situation today (A calls B, B
> > forwards the call to C) would use from=A and PAI=B, where B is a
> > registered endpoint (and billable by the SSP).  Not sure if that's
> > what you're asking?
> [JRE] Yes, that was what I was asking, and I know that it sometimes
> works the way you describe, but this is bad because PAI=B is
> wrong - it
> is not compliant with RFC 3325, since it is not the source of the
> request. If the callee used that to make a return call, the
> return call
> would arrive at the wrong place. For example, if a customer
> calls me on
> my office number and the PBX forwards it to my home via the SSP, if my
> phone stores the PAI as the caller's number and I try to make a return
> call, the return call goes to my office phone, not to my customer.
> [Tyler] The source of the forward leg of the call is B, not
> A.  Calling
> area requirements and n11 need to be based on B.  Why would the callee
> use PAI to return a call?  That would be in violation of 3325 as well
> since it would obviate any callerid blocking/suppression requirements.
> I guess whether the PBX should strip PAI before sending it to
> your phone
> is arguable.  Agreed, using PAI to assert a different ID than From
> (where from isn't private) might not strictly adhere to 3325, but I
> think alternate ID's vs suppressed ID's is splitting hairs a little.
>
> John
>
> = 


From john.elwell@siemens-enterprise.com  Mon Mar  1 12:44:00 2010
Return-Path: <john.elwell@siemens-enterprise.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 27F543A8AFC for <martini@core3.amsl.com>; Mon,  1 Mar 2010 12:44:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_31=0.6]
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 O6TYD3Sx5bYu for <martini@core3.amsl.com>; Mon,  1 Mar 2010 12:43:58 -0800 (PST)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 18A0C3A8AEF for <martini@ietf.org>; Mon,  1 Mar 2010 12:43:57 -0800 (PST)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1053716; Mon, 1 Mar 2010 21:43:57 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id 081B223F02AE; Mon,  1 Mar 2010 21:43:57 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.57]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Mon, 1 Mar 2010 21:43:57 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Tyler Parkin <tyler@foxfam.com>, Brian Lindsay <blindsay@nortel.com>, Adam Roach <adam@nostrum.com>, Spencer Dawkins <spencer@wonderhamster.org>
Date: Mon, 1 Mar 2010 21:43:55 +0100
Thread-Topic: [martini] Middlebox needs - admitting inbound requests
Thread-Index: Acq5abU80xuq8SZFRZiKs6iXrkwFfgAFd7fw
Message-ID: <A444A0F8084434499206E78C106220CABBBA5CBB@MCHP058A.global-ad.net>
References: <C7AC4291.14C39%adam@nostrum.com><99BF4620352B4F9C9E090F9004C31924@china.huawei.com><4B86F875.6070902@nostrum.com><00b101cab66c$3ce34150$430510ac@CORPORATE.VOX.NET><09B7DBFE70A9E24BBB21689DAD3A06141CB0F52A@zcarhxm1.corp.nortel.com> <00ca01cab67a$7fd21460$430510ac@CORPORATE.VOX.NET> <A444A0F8084434499206E78C106220CABBB22E97@MCHP058A.global-ad.net> <000901cab6f5$968a9df0$010c030a@CORPORATE.VOX.NET> <A444A0F8084434499206E78C106220CABBB232D7@MCHP058A.global-ad.net> <008201cab70e$0d82c6e0$010c030a@CORPORATE.VOX.NET> <09B7DBFE70A9E24BBB21689DAD3A06141CB5DF53@zcarhxm1.corp.nortel.com> <A444A0F8084434499206E78C106220CABBBA59EF@MCHP058A.global-ad.net> <000e01cab969$87ee3380$370510ac@CORPORATE.VOX.NET>
In-Reply-To: <000e01cab969$87ee3380$370510ac@CORPORATE.VOX.NET>
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
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, MARTINI <martini@ietf.org>
Subject: Re: [martini] Middlebox needs - admitting inbound requests
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, 01 Mar 2010 20:44:00 -0000

Tyler,

Thanks for the clarification. So there is no impact on the Requirements dra=
ft. I will leave it to others to comment on whether they believe the interf=
ace between a middlebox and a registrar should be specified as part of MART=
INI.

John
=20

> -----Original Message-----
> From: Tyler Parkin [mailto:tyler@foxfam.com]=20
> Sent: 01 March 2010 18:04
> To: Elwell, John; Brian Lindsay; Adam Roach; Spencer Dawkins
> Cc: Bernard Aboba; MARTINI
> Subject: Re: [martini] Middlebox needs - admitting inbound requests
>=20
> All I asked is that the behavior of network elements beyond=20
> the PBX also be=20
> described in the draft.  Even within this forum we've had two=20
> different=20
> suggestions on how a middlebox *could* behave to support then GIN=20
> proposal... one involved different ports on the private side of the=20
> middlebox and the other included the use of a cookie.  I=20
> didn't say explicit=20
> knowledge of the extensions is the only method, only that the=20
> mechanism used=20
> between the middlebox(es) and the registrars should be=20
> defined in this=20
> document so that the implimentation is standardized.  IMO, without=20
> describing that behavior, this draft won't be widely (or at=20
> least quickly=20
> adopted) due to interop issues between other vendors in the call flow.
>=20
> Regards,
>=20
> Tyler
>=20
>=20
> ----- Original Message -----=20
> From: "Elwell, John" <john.elwell@siemens-enterprise.com>
> To: "Brian Lindsay" <blindsay@nortel.com>; "Tyler Parkin"=20
> <tyler@foxfam.com>; "Adam Roach" <adam@nostrum.com>; "Spencer=20
> Dawkins"=20
> <spencer@wonderhamster.org>
> Cc: "Bernard Aboba" <bernard_aboba@hotmail.com>; "MARTINI"=20
> <martini@ietf.org>
> Sent: Monday, March 01, 2010 9:15 AM
> Subject: RE: [martini] Middlebox needs - admitting inbound requests
>=20
>=20
> Yes, I would have expected a middlebox providing this NAT function on=20
> message contents should be sufficiently stateful to allow the=20
> opposite to=20
> happen in the reverse direction. I still have a hard time=20
> understanding why=20
> the middlebox needs explicit knowledge of registered AORs=20
> (user parts) in=20
> order accomplish this type of functionality.
>=20
> John
>=20
>=20
> > -----Original Message-----
> > From: Brian Lindsay [mailto:blindsay@nortel.com]
> > Sent: 28 February 2010 20:52
> > To: Tyler Parkin; Elwell, John; Adam Roach; Spencer Dawkins
> > Cc: Bernard Aboba; MARTINI
> > Subject: RE: [martini] Middlebox needs - admitting inbound requests
> >
> > Hi Tyler,
> >
> >   I believe some SBCs that "NAT" as you describe would (or
> > could) use a
> > unique port on the northbound side per registered entity. So the SBC
> > would be able to maintain a mapping from the client-side
> > contact/routing
> > info to a unique northbound address/port that it would
> > receive requests
> > on (for requests towards the SIP PBX). In this case, there
> > shouldn't be
> > any problems routing the request.
> >
> >   Also, I think the MARTINI-Shaken approach wouldn't have a=20
> problem in
> > this case either, since the domain portion of the request uri
> > (from the
> > "SSP") contains a domain name representing the=20
> enterprise/PBX, rather
> > than an IP address derived from the contact.
> >
> >   Thanks
> >      Brian
> >
> > -----Original Message-----
> > From: Tyler Parkin [mailto:tyler@foxfam.com]
> > Sent: Friday, February 26, 2010 1:04 PM
> > To: Elwell, John; Lindsay, Brian (CAR:AR00); Adam Roach;
> > Spencer Dawkins
> > Cc: Bernard Aboba; MARTINI
> > Subject: Re: [martini] Middlebox needs - admitting inbound requests
> >
> >
> > > ----- Original Message -----
> > > From: "Elwell, John" <john.elwell@siemens-enterprise.com>
> > > To: "Tyler Parkin" <tyler@foxfam.com>; "Brian Lindsay"
> > > <blindsay@nortel.com>; "Adam Roach" <adam@nostrum.com>; "Spencer
> > > Dawkins"
> > > <spencer@wonderhamster.org>
> > > Cc: "Bernard Aboba" <bernard_aboba@hotmail.com>; "MARTINI"
> > > <martini@ietf.org>
> > > Sent: Friday, February 26, 2010 5:34 AM
> > > Subject: RE: [martini] Middlebox needs - admitting=20
> inbound requests
> > >
> > >
> > > Tyler,
> > >
> > > I found this thread a little mixed up between outbound
> > requests from
> > > the PBX and inbound requests  to the PBX, so I am not sure I
> > > understood everything.
> > > [tyler] sorry for the confusion, I think we're looking at it in
> > > different directions... inbound to me is inbound to the
> > SSP, where to
> > > you inbound is to the PBX.  I guess we'll stick w/=20
> inbound =3D to the
> > > PBX
> > >
> > > As far as inbound request are concerned, I think with gin-01 the
> > > problems you raise should be solvable, but it perhaps
> > requires use of
> > > Proxy-Require, as already discussed. The middlebox does=20
> not need to
> > > know exactly which E.164s are implicitly registered, but
> > when it gets
> > > a request to the PBX's IP address (presumably with Route=20
> indicating
> > > the IP address of the middlebox) it should assume the E.164 in the
> > > user part is indeed a registered AOR.
> > > [tyler] my point is that the middlebox doesn't get a=20
> request to the
> > > PBX's IP address.
> > [JRE] Why not? If the Contact URI contains the IP address (as in
> > gin-01), this will be registered at the registrar and will=20
> be returned
> > as the target of an inbound request to the PBX.
> >
> > > The softswitch/registrar generating the call doesn't know
> > the PBX's IP
> >
> > > because it was masked during the initial registration.
> > [JRE] Why would it be masked? I understand that the registrar
> > would not
> > see the IP address at the transport level from which the REGISTER
> > request arrived at the middlebox, but it would see the IP
> > address in the
> > Contact URI.
> > [Tyler] In most scenarios where a middlebox (aka SBC)=20
> exists, the SBC
> > performs two-way NAT functions, and NAT's the headers/URI's
> > for inbound
> > and outbound messaging.  Therefore, a request received on the public
> > side from user@PBXIP is sent to the registrar as
> > user@SBCPRIVATEIP.  The
> > oposite direction (SSP -> PBX) is received by the SBC as
> > user@SSPIP and
> > NAT'd to user@SBCPUBLICIP.
> >
> > > Any
> > > requests from from the registrar/softswitch to the
> > middlebox (destined
> >
> > > for the PBX) will only have user@middlebox, perhaps w/ a cookie.
> > > The middelbox
> > > needs to map user@middlebox to whatever IP/host originally
> > registered.
> > > Today, the middlebox keeps a cache where the initial (individual)
> > > registration might be user@1.1.1.1, and the registration
> > forwarded to
> > > the registrar is user@2.2.2.2.  That way when the=20
> registrar sends a
> > > request to the middlebox for user@2.2.2.2 it maps it to
> > user@1.1.1.1
> > > and all is good.
> > > If the middelbox doesn't have knowledge of the user (because of
> > > implicit),
> > [JRE] Are you suggesting that each user behind the PBX=20
> would register
> > with a different IP address, so you need to know whether it
> > is user1 or
> > user2 in order to send requests to 11.11.11.11 or=20
> 22.22.22.22? If so,
> > that is not the scenario that MARTINI is addressing. MARTINI is
> > addressing the case where requests to user1, user2 etc. on=20
> a given PBX
> > all need to be routed to the PBX's IP address. So as long as the
> > middlebox knows the request needs to go to the PBX, it=20
> doesn't need to
> > know that particular user.
> > [Tyler] Agreed, I shouldn't have used the term user.  The=20
> middlebox in
> > this scenario wouldn't care about individual users, it's point of
> > contact is the PBX.  All PBX's send register requests to=20
> the middlebox
> > from different IP's/domains, granted.  After NAT, however, all the
> > requests from the SBC to the registrar appear to come from
> > the same IP.
> > We NAT in both directions, which is pretty standard, so we
> > don't expose
> > core equipment to the public, and we don't expose end user IP's to
> > peers.  Plus it allows virtual route tables internally and
> > resolves any
> > issues with overlapping address space.
> >
> > > it can't make the mapping unless it has something else to
> > associate to
> >
> > > the original implicit reg (like a cookie, or knowledge of the
> > > extensions).
> > >
> > > Now concerning outbound requests (this was what my earlier
> > message was
> >
> > > about, although somewhere further back that got brought
> > across to this
> >
> > > thread rather than the thread concerning outbound requests, so the
> > > thread title was wrong). Assuming an entity has knowledge of
> > > registered E.164 numbers, it is not clear to me how it
> > would deal with
> >
> > > a request where the From/PAI in the request from the PBX is
> > not one of
> >
> > > the implicitly registered ones. This can arise, for=20
> example, if the
> > > request originates elsewhere in the enterprise and "breaks
> > out" to the
> >
> > > SSP via this particular PBX. Or if the call originated
> > elsewhere and
> > > was forwarded by the PBX to the SSP. I appreciate that=20
> there may be
> > > some arrangements between PBX and SSP where this is forbidden by
> > > policy, but in the general case I would expect it to work,
> > so that the
> >
> > > callee has a correct AOR to which it can make a return call.
> > > [tyler] methods dealing with this situation today (A calls B, B
> > > forwards the call to C) would use from=3DA and PAI=3DB, where B is a
> > > registered endpoint (and billable by the SSP).  Not sure if that's
> > > what you're asking?
> > [JRE] Yes, that was what I was asking, and I know that it sometimes
> > works the way you describe, but this is bad because PAI=3DB is
> > wrong - it
> > is not compliant with RFC 3325, since it is not the source of the
> > request. If the callee used that to make a return call, the
> > return call
> > would arrive at the wrong place. For example, if a customer
> > calls me on
> > my office number and the PBX forwards it to my home via the=20
> SSP, if my
> > phone stores the PAI as the caller's number and I try to=20
> make a return
> > call, the return call goes to my office phone, not to my customer.
> > [Tyler] The source of the forward leg of the call is B, not
> > A.  Calling
> > area requirements and n11 need to be based on B.  Why would=20
> the callee
> > use PAI to return a call?  That would be in violation of=20
> 3325 as well
> > since it would obviate any callerid blocking/suppression=20
> requirements.
> > I guess whether the PBX should strip PAI before sending it to
> > your phone
> > is arguable.  Agreed, using PAI to assert a different ID than From
> > (where from isn't private) might not strictly adhere to 3325, but I
> > think alternate ID's vs suppressed ID's is splitting hairs a little.
> >
> > John
> >
> > =3D=20
>=20
> =

From adam@nostrum.com  Mon Mar  1 16:04:05 2010
Return-Path: <adam@nostrum.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 BB8D53A888B for <martini@core3.amsl.com>; Mon,  1 Mar 2010 16:04:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
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 XeTsnezOq1+3 for <martini@core3.amsl.com>; Mon,  1 Mar 2010 16:04:05 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 662E93A886D for <martini@ietf.org>; Mon,  1 Mar 2010 16:04:04 -0800 (PST)
Received: from hydra-3.local (ppp-70-249-147-216.dsl.rcsntx.swbell.net [70.249.147.216]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o22041iA038597 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <martini@ietf.org>; Mon, 1 Mar 2010 18:04:01 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4B8C55F0.9050205@nostrum.com>
Date: Mon, 01 Mar 2010 18:04:01 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: martini@ietf.org
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org>	<A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net>	<877ACFA2914F4A5B9336B80718E233D0@china.huawei.com> <A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 70.249.147.216 is authenticated by a trusted mechanism)
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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, 02 Mar 2010 00:04:05 -0000

On 2/22/10 11:35, Feb 22, Elwell, John wrote:
> From: Spencer Dawkins [mailto:spencer@wonderhamster.org]
>> (c) isn't likely to give us "several thousand AoRs". Dean did
>> helpful math
>> which was more scientific than my back-of-the-envelope (see
>> http://www.ietf.org/mail-archive/web/martini/current/msg00833.
>> html), and
>> came up with 70. That's more than an order of magnitude less than the
>> requirement requires, and (unfortunately) it may be
>> optimistic outside North
>> America, where AoRs can be longer than 10 digits.
>>      
> [JRE] I don't think that we can have a solution that limits you to 70 (or less outside NA) AORs. This is true whether or not we have an explicit requirement for a higher number.
>    

To be clear, it's not 70 DIDs. It's 70 discrete _ranges_ of DIDs. 
Depending on level of fragmentation, that could be anywhere from 70 
individual DIDs (if no two numbers are consecutive) to several hundred 
million DIDs.

So I *could* argue that the proposed scheme actually exceeds the 
specified requirement by five orders of magnitude.

But both extremes are ridiculous on their face, and I think portraying 
either extreme as the basis of an argument is a bit disingenuous.

Is the fragmentation issue so profound that we're really going to see 
PBXes with more than 70 contiguous *RANGES* of DIDs? That seems edging 
into the "implausible" area of these two extremes.

/a

From spencer@wonderhamster.org  Mon Mar  1 16:51:04 2010
Return-Path: <spencer@wonderhamster.org>
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 B84C03A8BFE for <martini@core3.amsl.com>; Mon,  1 Mar 2010 16:51:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.999, BAYES_00=-2.599]
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 ZCTLT6os2Y7Z for <martini@core3.amsl.com>; Mon,  1 Mar 2010 16:51:03 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 8F8CC28C21A for <martini@ietf.org>; Mon,  1 Mar 2010 16:51:03 -0800 (PST)
Received: from S73602b (w147.z209031239.sjc-ca.dsl.cnc.net [209.31.239.147]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0M85w9-1NZQNB3xWz-00verg; Mon, 01 Mar 2010 19:50:55 -0500
Message-ID: <778143AFD0DA4150AF03ED2F702B81F0@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Adam Roach" <adam@nostrum.com>, <martini@ietf.org>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org>	<A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net>	<877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net> <4B8C55F0.9050205@nostrum.com>
Date: Mon, 1 Mar 2010 18:50:45 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX19vKfCOk3WuPillJ3VyA72ga/H+KOTBd7P4Fwn wm2frThe4p/YKFkvrvJOSA+bR8A2K2c5U1W0kEt5Z4UKpAZdYl SlYFG0mAAIIY4hdrJk6N7Y5VaZu3UEl2rYS3sc6YWk=
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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, 02 Mar 2010 00:51:04 -0000

Hi, Adam,

I agree that what we're talking about is "ranges".

What I'm most concerned about is the situation where an enterprise ends up 
with an R.164 space that's just a little more segmented today than it was 
yesterday, and things stop working ("oh, NOW you need to start using RFC 
3263, since your REGISTER just failed").

My understanding from people like Richard Shockey is that we're just at the 
beginning of local number portability for Europe in a serious way, for 
example.

I don't know when 70 segments might become a commonly-encountered 
limitation, but I'm thinking that the chances that this will happen get 
greater every year.

The way I was reading the original requirement, all you'd have to do is send 
70 people from corporate headquarters to home offices (so their E.164s 
aren't routed to the PBX any more).  If we're insisting that we support 
support "several thousand" AoRs, I can imagine that happening (I have a 
vivid imagination, but I'm not sure I'm hallucinating yet). I'm pretty sure 
Nortel sent at least that many people to home offices in the Richardson 
campus during the late 1990s (actually, I'm fairly sure it was several 
hundred, out of a site population of several thousand).

But maybe it will never happen ("you could very well be right").

I THINK where we are is that we decided that we're not going to worry about 
this (if you worry about stuff like this, either manage your number ranges 
carefully or start planning your RFC 3263 migration) - Bernard, is that the 
way you're seeing it?

Thanks,

Spencer

>>> (c) isn't likely to give us "several thousand AoRs". Dean did
>>> helpful math
>>> which was more scientific than my back-of-the-envelope (see
>>> http://www.ietf.org/mail-archive/web/martini/current/msg00833.
>>> html), and
>>> came up with 70. That's more than an order of magnitude less than the
>>> requirement requires, and (unfortunately) it may be
>>> optimistic outside North
>>> America, where AoRs can be longer than 10 digits.
>>>
>> [JRE] I don't think that we can have a solution that limits you to 70 (or 
>> less outside NA) AORs. This is true whether or not we have an explicit 
>> requirement for a higher number.
>>
>
> To be clear, it's not 70 DIDs. It's 70 discrete _ranges_ of DIDs. 
> Depending on level of fragmentation, that could be anywhere from 70 
> individual DIDs (if no two numbers are consecutive) to several hundred 
> million DIDs.
>
> So I *could* argue that the proposed scheme actually exceeds the specified 
> requirement by five orders of magnitude.
>
> But both extremes are ridiculous on their face, and I think portraying 
> either extreme as the basis of an argument is a bit disingenuous.
>
> Is the fragmentation issue so profound that we're really going to see 
> PBXes with more than 70 contiguous *RANGES* of DIDs? That seems edging 
> into the "implausible" area of these two extremes.
>
> /a
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini 


From adam@nostrum.com  Mon Mar  1 19:37:47 2010
Return-Path: <adam@nostrum.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 5432C3A8A32 for <martini@core3.amsl.com>; Mon,  1 Mar 2010 19:37:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, SPF_PASS=-0.001]
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 OShGdh0+U9UD for <martini@core3.amsl.com>; Mon,  1 Mar 2010 19:37:45 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 292123A88BA for <martini@ietf.org>; Mon,  1 Mar 2010 19:37:44 -0800 (PST)
Received: from hydra-3.local (ppp-70-249-147-216.dsl.rcsntx.swbell.net [70.249.147.216]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o223bhU3054040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 Mar 2010 21:37:43 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4B8C8807.3040407@nostrum.com>
Date: Mon, 01 Mar 2010 21:37:43 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Spencer Dawkins <spencer@wonderhamster.org>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org>	<A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net>	<877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net> <4B8C55F0.9050205@nostrum.com> <778143AFD0DA4150AF03ED2F702B81F0@china.huawei.com>
In-Reply-To: <778143AFD0DA4150AF03ED2F702B81F0@china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 70.249.147.216 is authenticated by a trusted mechanism)
Cc: martini@ietf.org
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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, 02 Mar 2010 03:37:47 -0000

On 3/1/10 18:50, Mar 1, Spencer Dawkins wrote:
> What I'm most concerned about is the situation where an enterprise 
> ends up with an R.164 space that's just a little more segmented today 
> than it was yesterday, and things stop working ("oh, NOW you need to 
> start using RFC 3263, since your REGISTER just failed").

I was actually looking more towards RFC 793.

Before people start howling that the vast majority of implementations 
fully ignore the normative requirement to implement TCP, I'll point out 
that none of the "UDP only" (i.e., "we read 3261 except that part") 
implementations that I've ever seen bother counting bytes. Which means 
that they'll happily cobble together a 64 kbyte message and stuff it 
into a UDP packet. And IP takes care of the fragmentation. So it goes 
across the wire in 50-some-odd IP packets. And, for most modern 
networks, that'll work. Maybe not the first time, but it'll work within 
SIP's retransmission window just fine.

Great network design? No, not really. But they ignored some very 
important normative language in RFC 3261. Their bad, their problem. But 
"just failed?" No. That won't happen.

Let's re-run Dean's analysis with this actual reality in mind.

Using Dean's number of about 700 bytes (or so) consumed by a modern 
REGISTER message, that leaves about 64,835 bytes of UDP packet available 
for DIDs. Or approximately 6,483 ranges before things actually "stop 
working."

Which is probably enough.

/a

From spencer@wonderhamster.org  Mon Mar  1 23:56:43 2010
Return-Path: <spencer@wonderhamster.org>
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 3EF463A871B for <martini@core3.amsl.com>; Mon,  1 Mar 2010 23:56:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 uxQgFEq4QZqj for <martini@core3.amsl.com>; Mon,  1 Mar 2010 23:56:42 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 6DC2D3A77D0 for <martini@ietf.org>; Mon,  1 Mar 2010 23:56:42 -0800 (PST)
Received: from S73602b ([67.99.198.4]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0Md2qI-1O4S4s0Oeo-00IPbU; Tue, 02 Mar 2010 02:56:14 -0500
Message-ID: <509AD0EB30FF462E946BF4CA0722829B@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Adam Roach" <adam@nostrum.com>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org>	<A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net>	<877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net> <4B8C55F0.9050205@nostrum.com> <778143AFD0DA4150AF03ED2F702B81F0@china.huawei.com> <4B8C8807.3040407@nostrum.com>
Date: Tue, 2 Mar 2010 01:56:04 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX19NBJnfg7PI78kUslPoNR3PUWWc9WrzbXDH+Mn WYl5hXLXmT8wC+mvjuc6OA5nEi7/LpruaVHPIXx98qbe+8pWbG IhB196+bi3YiAFYIFQ8cBPKc/dlU16hxQGZ+pyf+X8=
Cc: martini@ietf.org
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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, 02 Mar 2010 07:56:43 -0000

Hi, Adam,

That would be the right order of magnitude for the requirement we have been 
discussing, so I will check this one off my list of stuff to worry about in 
MARTINI and go on to the next one :D

Thanks,

Spencer


> On 3/1/10 18:50, Mar 1, Spencer Dawkins wrote:
>> What I'm most concerned about is the situation where an enterprise ends 
>> up with an R.164 space that's just a little more segmented today than it 
>> was yesterday, and things stop working ("oh, NOW you need to start using 
>> RFC 3263, since your REGISTER just failed").
>
> I was actually looking more towards RFC 793.
>
> Before people start howling that the vast majority of implementations 
> fully ignore the normative requirement to implement TCP, I'll point out 
> that none of the "UDP only" (i.e., "we read 3261 except that part") 
> implementations that I've ever seen bother counting bytes. Which means 
> that they'll happily cobble together a 64 kbyte message and stuff it into 
> a UDP packet. And IP takes care of the fragmentation. So it goes across 
> the wire in 50-some-odd IP packets. And, for most modern networks, that'll 
> work. Maybe not the first time, but it'll work within SIP's retransmission 
> window just fine.
>
> Great network design? No, not really. But they ignored some very important 
> normative language in RFC 3261. Their bad, their problem. But "just 
> failed?" No. That won't happen.
>
> Let's re-run Dean's analysis with this actual reality in mind.
>
> Using Dean's number of about 700 bytes (or so) consumed by a modern 
> REGISTER message, that leaves about 64,835 bytes of UDP packet available 
> for DIDs. Or approximately 6,483 ranges before things actually "stop 
> working."
>
> Which is probably enough.
>
> /a 


From trac@tools.ietf.org  Tue Mar  2 00:27:50 2010
Return-Path: <trac@tools.ietf.org>
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 529463A888B for <martini@core3.amsl.com>; Tue,  2 Mar 2010 00:27:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 45dyFE5BsUX8 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 00:27:49 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) by core3.amsl.com (Postfix) with ESMTP id 1BA933A89A6 for <martini@ietf.org>; Tue,  2 Mar 2010 00:27:49 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NmNSF-00032e-Aj; Tue, 02 Mar 2010 00:27:47 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com, bruno.chatras@orange-ftgroup.com
X-Trac-Project: martini
Date: Tue, 02 Mar 2010 08:27:47 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/4
Message-ID: <074.31859e42adde33dceae499b167210f4e@tools.ietf.org>
X-Trac-Ticket-ID: 4
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, bruno.chatras@orange-ftgroup.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #4: PAI/PPI mismatches issue
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 02 Mar 2010 08:27:50 -0000

#4: PAI/PPI mismatches issue
----------------------------------------------+-----------------------------
 Reporter:  bruno.chatras@…                   |       Owner:  john.elwell@…                     
     Type:  defect                            |      Status:  new                               
 Priority:  minor                             |   Milestone:  milestone1                        
Component:  reqs                              |     Version:  1.0                               
 Severity:  In WG Last Call                   |    Keywords:                                    
----------------------------------------------+-----------------------------
 Clause 3.3.1 should indicate that if no match is found, the request is
 rejected or the PAI is created or overwritten with a value selected by
 the SSP.

 Clause 3.3.2 should indicate that mismatch "triggers requestrejection or
 PAI creation or overwritting with a value selected by the SSP.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/4>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Tue Mar  2 00:41:25 2010
Return-Path: <trac@tools.ietf.org>
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 85A1C3A89F0 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 00:41:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 1RNTklor5Q8M for <martini@core3.amsl.com>; Tue,  2 Mar 2010 00:41:24 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) by core3.amsl.com (Postfix) with ESMTP id A8BB43A8626 for <martini@ietf.org>; Tue,  2 Mar 2010 00:41:24 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NmNfP-00018X-Jq; Tue, 02 Mar 2010 00:41:23 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com, bruno.chatras@orange-ftgroup.com
X-Trac-Project: martini
Date: Tue, 02 Mar 2010 08:41:23 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/5
Message-ID: <074.378cdeefb4071f2108092872d74eadac@tools.ietf.org>
X-Trac-Ticket-ID: 5
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, bruno.chatras@orange-ftgroup.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #5: AORs other than telephone numbers
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 02 Mar 2010 08:41:25 -0000

#5: AORs other than telephone numbers
----------------------------------------------+-----------------------------
 Reporter:  bruno.chatras@…                   |       Owner:  john.elwell@…                     
     Type:  defect                            |      Status:  new                               
 Priority:  critical                          |   Milestone:  milestone1                        
Component:  gin                               |     Version:  1.0                               
 Severity:  In WG Last Call                   |    Keywords:                                    
----------------------------------------------+-----------------------------
 A new desirable requirement should be added:

 "DES5: The mechanism SHOULD allow a SIP-PBX to enter into a trunking
 arrangement with an SSP whereby the two parties have agreed on a set of
 SIP URIs deemed to have been assigned to a SIP-PBX.

    As the 3GPP/ETSI solution supports both Telephone Numbers and
    email-style SIP URIs, a mechanism supporting Telephone Numbers
    only may not be widely adopted by the market.
 "

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/5>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Tue Mar  2 00:42:01 2010
Return-Path: <trac@tools.ietf.org>
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 3052F3A8626 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 00:42:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 YDEdmSsbUh-B for <martini@core3.amsl.com>; Tue,  2 Mar 2010 00:42:00 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) by core3.amsl.com (Postfix) with ESMTP id 7EF043A70E2 for <martini@ietf.org>; Tue,  2 Mar 2010 00:42:00 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NmNg0-0001rR-Bk; Tue, 02 Mar 2010 00:42:00 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com, bruno.chatras@orange-ftgroup.com
X-Trac-Project: martini
Date: Tue, 02 Mar 2010 08:42:00 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/6
Message-ID: <074.00f38bdd51aa79f0265b2a39a5ed89f0@tools.ietf.org>
X-Trac-Ticket-ID: 6
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, bruno.chatras@orange-ftgroup.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #6: AORs other than telephone numbers
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 02 Mar 2010 08:42:01 -0000

#6: AORs other than telephone numbers
----------------------------------------------+-----------------------------
 Reporter:  bruno.chatras@…                   |       Owner:  john.elwell@…                     
     Type:  defect                            |      Status:  new                               
 Priority:  critical                          |   Milestone:  milestone1                        
Component:  reqs                              |     Version:  1.0                               
 Severity:  In WG Last Call                   |    Keywords:                                    
----------------------------------------------+-----------------------------
 A new desirable requirement should be added:

 "DES5: The mechanism SHOULD allow a SIP-PBX to enter into a trunking
 arrangement with an SSP whereby the two parties have agreed on a set of
 SIP URIs deemed to have been assigned to a SIP-PBX.

    As the 3GPP/ETSI solution supports both Telephone Numbers and
    email-style SIP URIs, a mechanism supporting Telephone Numbers
    only may not be widely adopted by the market.
 "

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/6>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Tue Mar  2 01:56:33 2010
Return-Path: <trac@tools.ietf.org>
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 DB4F53A87F0 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 01:56:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 kn+XeVfiqARj for <martini@core3.amsl.com>; Tue,  2 Mar 2010 01:56:33 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) by core3.amsl.com (Postfix) with ESMTP id 039D43A8766 for <martini@ietf.org>; Tue,  2 Mar 2010 01:56:33 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NmOq9-0005Jh-2j; Tue, 02 Mar 2010 01:56:33 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Tue, 02 Mar 2010 09:56:32 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/4#comment:1
Message-ID: <083.a7431db1fbb90f793468e735dfd62d75@tools.ietf.org>
References: <074.31859e42adde33dceae499b167210f4e@tools.ietf.org>
X-Trac-Ticket-ID: 4
In-Reply-To: <074.31859e42adde33dceae499b167210f4e@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #4: PAI/PPI mismatches issue
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 02 Mar 2010 09:56:34 -0000

#4: PAI/PPI mismatches issue
----------------------------------------------+-----------------------------
 Reporter:  bruno.chatras@…                   |        Owner:  john.elwell@…                     
     Type:  defect                            |       Status:  closed                            
 Priority:  minor                             |    Milestone:  milestone1                        
Component:  reqs                              |      Version:  1.0                               
 Severity:  In WG Last Call                   |   Resolution:  fixed                             
 Keywords:                                    |  
----------------------------------------------+-----------------------------
Changes (by john.elwell@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Replying to [ticket:4 bruno.chatras@…]:
 > Clause 3.3.1 should indicate that if no match is found, the request is
 rejected or the PAI is created or overwritten with a value selected by
 the SSP.
 >
 [JRE] OK - I will reword slightly and move the existing sentence about
 rejection to the end of the paragraph, where I think it will make more
 sense. It will say "This can cause an SSP to fail to find an AOR
 corresponding to the Contact URI for non-REGISTER requests, resulting in
 the SSP rejecting such requests or asserting its own PAI value, rather
 than asserting a value based on received header fields."

 > Clause 3.3.2 should indicate that mismatch "triggers requestrejection or
 PAI creation or overwritting with a value selected by the SSP.
 [JRE] The first paragraph of 3.3.2 effectively says that already, but the
 second paragraph fails to. I will make it clear that the statement refers
 to both and reword as "In either case, this can result in the SSP
 rejecting requests with values that do not match or asserting its own PAI
 value."

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/4#comment:1>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Tue Mar  2 02:09:14 2010
Return-Path: <trac@tools.ietf.org>
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 5A5A728C0D6 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 02:09:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 KOG2mPXkeWLy for <martini@core3.amsl.com>; Tue,  2 Mar 2010 02:09:13 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) by core3.amsl.com (Postfix) with ESMTP id A4C9128C0D0 for <martini@ietf.org>; Tue,  2 Mar 2010 02:09:13 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NmP2O-0000NN-Qx; Tue, 02 Mar 2010 02:09:12 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com, john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Tue, 02 Mar 2010 10:09:12 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/5#comment:1
Message-ID: <083.58c489f811b9f88844c3cf2d5c325d26@tools.ietf.org>
References: <074.378cdeefb4071f2108092872d74eadac@tools.ietf.org>
X-Trac-Ticket-ID: 5
In-Reply-To: <074.378cdeefb4071f2108092872d74eadac@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, john.elwell@siemens-enterprise.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #5: AORs other than telephone numbers
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 02 Mar 2010 10:09:14 -0000

#5: AORs other than telephone numbers
----------------------------------------------+-----------------------------
 Reporter:  bruno.chatras@…                   |       Owner:  adam@…          
     Type:  defect                            |      Status:  new             
 Priority:  critical                          |   Milestone:  milestone1      
Component:  gin                               |     Version:  1.0             
 Severity:  In WG Last Call                   |    Keywords:                  
----------------------------------------------+-----------------------------
Changes (by john.elwell@…):

  * owner:  john.elwell@… => adam@…


Comment:

 [JRE] I am reassigning to the gin document author, but my own opinion is
 that we already achieved consensus in the past to support only E.164
 numbers in our first deliverables. However, I notice the proposal is only
 for a Desirable, so what do people think?

 John

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/5#comment:1>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Tue Mar  2 02:13:06 2010
Return-Path: <trac@tools.ietf.org>
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 DE6BF28C10E for <martini@core3.amsl.com>; Tue,  2 Mar 2010 02:13:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 PlpFpsubZMwP for <martini@core3.amsl.com>; Tue,  2 Mar 2010 02:13:05 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) by core3.amsl.com (Postfix) with ESMTP id 0CD5028C11E for <martini@ietf.org>; Tue,  2 Mar 2010 02:13:05 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NmP6A-0003EU-68; Tue, 02 Mar 2010 02:13:06 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Tue, 02 Mar 2010 10:13:06 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/6#comment:1
Message-ID: <083.8d1f1e237e6a33ff6de5ecbf9434a306@tools.ietf.org>
References: <074.00f38bdd51aa79f0265b2a39a5ed89f0@tools.ietf.org>
X-Trac-Ticket-ID: 6
In-Reply-To: <074.00f38bdd51aa79f0265b2a39a5ed89f0@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #6: AORs other than telephone numbers
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 02 Mar 2010 10:13:06 -0000

#6: AORs other than telephone numbers
----------------------------------------------+-----------------------------
 Reporter:  bruno.chatras@…                   |       Owner:  john.elwell@…                     
     Type:  defect                            |      Status:  assigned                          
 Priority:  critical                          |   Milestone:  milestone1                        
Component:  reqs                              |     Version:  1.0                               
 Severity:  In WG Last Call                   |    Keywords:                                    
----------------------------------------------+-----------------------------
Changes (by john.elwell@…):

  * status:  new => assigned


Comment:

 [JRE] We already achieved consensus in the past to support only E.164
 numbers in our first deliverables. However, I notice the proposal is only
 for a Desirable, so what do people think?

 John

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/6#comment:1>
martini <http://tools.ietf.org/martini/>


From john.elwell@siemens-enterprise.com  Tue Mar  2 02:36:49 2010
Return-Path: <john.elwell@siemens-enterprise.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 1E8CB3A8383 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 02:36:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599]
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 Dzh-hlZqBzh9 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 02:36:47 -0800 (PST)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 7840C3A816C for <martini@ietf.org>; Tue,  2 Mar 2010 02:36:47 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1060512; Tue, 2 Mar 2010 11:36:46 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id C27E71EB82AE; Tue,  2 Mar 2010 11:36:46 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.57]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Tue, 2 Mar 2010 11:36:46 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Adam Roach <adam@nostrum.com>, "martini@ietf.org" <martini@ietf.org>
Date: Tue, 2 Mar 2010 11:36:45 +0100
Thread-Topic: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
Thread-Index: Acq5m+IoZrRB2mpaSYqpjpYDRl/L+QAVkdoA
Message-ID: <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org> <A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net> <877ACFA2914F4A5B9336B80718E233D0@china.huawei.com> <A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net> <4B8C55F0.9050205@nostrum.com>
In-Reply-To: <4B8C55F0.9050205@nostrum.com>
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
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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, 02 Mar 2010 10:36:49 -0000

=20

> -----Original Message-----
> From: martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] On Behalf Of Adam Roach
> Sent: 02 March 2010 00:04
> To: martini@ietf.org
> Subject: Re: [martini] #2: Scaling to Several Thousand=20
> Assigned Telephone Numbers
>=20
> On 2/22/10 11:35, Feb 22, Elwell, John wrote:
> > From: Spencer Dawkins [mailto:spencer@wonderhamster.org]
> >> (c) isn't likely to give us "several thousand AoRs". Dean did
> >> helpful math
> >> which was more scientific than my back-of-the-envelope (see
> >> http://www.ietf.org/mail-archive/web/martini/current/msg00833.
> >> html), and
> >> came up with 70. That's more than an order of magnitude=20
> less than the
> >> requirement requires, and (unfortunately) it may be
> >> optimistic outside North
> >> America, where AoRs can be longer than 10 digits.
> >>     =20
> > [JRE] I don't think that we can have a solution that limits=20
> you to 70 (or less outside NA) AORs. This is true whether or=20
> not we have an explicit requirement for a higher number.
> >   =20
>=20
> To be clear, it's not 70 DIDs. It's 70 discrete _ranges_ of DIDs.=20
> Depending on level of fragmentation, that could be anywhere from 70=20
> individual DIDs (if no two numbers are consecutive) to=20
> several hundred=20
> million DIDs.
>=20
> So I *could* argue that the proposed scheme actually exceeds the=20
> specified requirement by five orders of magnitude.
>=20
> But both extremes are ridiculous on their face, and I think=20
> portraying=20
> either extreme as the basis of an argument is a bit disingenuous.
>=20
> Is the fragmentation issue so profound that we're really going to see=20
> PBXes with more than 70 contiguous *RANGES* of DIDs? That=20
> seems edging=20
> into the "implausible" area of these two extremes.
[JRE] I agree we are talking about ranges. My only concern is that people a=
re saying that fragmentation will be a lot more severe in future, as number=
 portability gets going, so in the worst case you could be limited to 70 nu=
mbers. Personally I don't mind if MARTINI is restricted to quite small PBXs=
, and we use RFC 3263 for anything bigger, but I don't think the SSPs want =
to place the cut-off point as low as 70.

So if we can agree that 70 ranges is sufficient and 70 dicrete numbers is a=
n extreme that we are unlikely to meet in practice, or in the rare case we =
do we rely on it working through fragmentation or by switching to TCP, that=
 would be OK with me.

So are we moving to a consensus that we should delete DES2, on the basis th=
at it is unrealistic. Or do we need an alternative requirement expressed in=
 number of ranges?

John

>=20
> /a
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
> =

From bruno.chatras@orange-ftgroup.com  Tue Mar  2 04:58:53 2010
Return-Path: <bruno.chatras@orange-ftgroup.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 B85743A8191 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 04:58:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 pd2T4NAFkXpV for <martini@core3.amsl.com>; Tue,  2 Mar 2010 04:58:53 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id B20F73A873B for <martini@ietf.org>; Tue,  2 Mar 2010 04:58:52 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 50C678B8005; Tue,  2 Mar 2010 13:57:53 +0000 (UTC)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id 48CE18B8004; Tue,  2 Mar 2010 13:57:53 +0000 (UTC)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 2 Mar 2010 13:58:51 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 2 Mar 2010 13:58:51 +0100
Message-ID: <9ECCF01B52E7AB408A7EB853526421410128F7A2@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <083.58c489f811b9f88844c3cf2d5c325d26@tools.ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] #5: AORs other than telephone numbers
Thread-Index: Acq58G8vTpDcA87jSoC32YzZ0r+VXwAF5RoQ
References: <074.378cdeefb4071f2108092872d74eadac@tools.ietf.org> <083.58c489f811b9f88844c3cf2d5c325d26@tools.ietf.org>
From: <bruno.chatras@orange-ftgroup.com>
To: <trac@localhost.amsl.com>, <adam@nostrum.com>, <john.elwell@siemens-enterprise.com>
X-OriginalArrivalTime: 02 Mar 2010 12:58:51.0530 (UTC) FILETIME=[1B6096A0:01CABA08]
Cc: martini@ietf.org
Subject: Re: [martini] #5: AORs other than telephone numbers
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, 02 Mar 2010 12:58:53 -0000

This was not intended to be a comment on the Gin document but on the =
Requirements document. I m ade a mistake when filling the form. =20

> -----Message d'origine-----
> De : martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] De la part de martini issue tracker
> Envoy=E9 : mardi 2 mars 2010 11:09
> =C0 : adam@nostrum.com; john.elwell@siemens-enterprise.com
> Cc : martini@ietf.org
> Objet : Re: [martini] #5: AORs other than telephone numbers
>=20
> #5: AORs other than telephone numbers
> ----------------------------------------------+---------------
> ----------
> ----------------------------------------------+----
>  Reporter:  bruno.chatras@...                   |       Owner: =20
> adam@...         =20
>      Type:  defect                            |      Status: =20
> new            =20
>  Priority:  critical                          |   Milestone: =20
> milestone1     =20
> Component:  gin                               |     Version: =20
> 1.0            =20
>  Severity:  In WG Last Call                   |    Keywords: =20
>                =20
> ----------------------------------------------+---------------
> ----------
> ----------------------------------------------+----
> Changes (by john.elwell@...):
>=20
>   * owner:  john.elwell@... =3D> adam@...
>=20
>=20
> Comment:
>=20
>  [JRE] I am reassigning to the gin document author, but my=20
> own opinion is  that we already achieved consensus in the=20
> past to support only E.164  numbers in our first=20
> deliverables. However, I notice the proposal is only  for a=20
> Desirable, so what do people think?
>=20
>  John
>=20
> --
> Ticket URL:=20
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/5#comment:1>
> martini <http://tools.ietf.org/martini/>
>=20
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>=20

From trac@tools.ietf.org  Tue Mar  2 05:44:38 2010
Return-Path: <trac@tools.ietf.org>
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 B4E863A8A1B for <martini@core3.amsl.com>; Tue,  2 Mar 2010 05:44:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 gr70YtyKPiSL for <martini@core3.amsl.com>; Tue,  2 Mar 2010 05:44:38 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) by core3.amsl.com (Postfix) with ESMTP id 181173A8A08 for <martini@ietf.org>; Tue,  2 Mar 2010 05:44:38 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NmSOq-00038H-TU; Tue, 02 Mar 2010 05:44:36 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com, bernard_aboba@hotmail.com, john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Tue, 02 Mar 2010 13:44:36 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/5#comment:2
Message-ID: <083.1fbff5a15389deba432c3c267765b0c1@tools.ietf.org>
References: <074.378cdeefb4071f2108092872d74eadac@tools.ietf.org>
X-Trac-Ticket-ID: 5
In-Reply-To: <074.378cdeefb4071f2108092872d74eadac@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, bernard_aboba@hotmail.com, john.elwell@siemens-enterprise.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #5: AORs other than telephone numbers
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 02 Mar 2010 13:44:38 -0000

#5: AORs other than telephone numbers
----------------------------------------------+-----------------------------
 Reporter:  bruno.chatras@…                   |        Owner:  adam@…          
     Type:  defect                            |       Status:  closed          
 Priority:  critical                          |    Milestone:  milestone1      
Component:  gin                               |      Version:  1.0             
 Severity:  In WG Last Call                   |   Resolution:  duplicate       
 Keywords:                                    |  
----------------------------------------------+-----------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => duplicate


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/5#comment:2>
martini <http://tools.ietf.org/martini/>


From adam@nostrum.com  Tue Mar  2 06:19:11 2010
Return-Path: <adam@nostrum.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 B36FF3A8A3B for <martini@core3.amsl.com>; Tue,  2 Mar 2010 06:19:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, SPF_PASS=-0.001]
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 F1UNjjcTKHI7 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 06:19:11 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 100573A878A for <martini@ietf.org>; Tue,  2 Mar 2010 06:19:08 -0800 (PST)
Received: from hydra-3.local (ppp-70-249-147-216.dsl.rcsntx.swbell.net [70.249.147.216]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o22EJ7Ci006220 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Mar 2010 08:19:08 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4B8D1E5C.8020001@nostrum.com>
Date: Tue, 02 Mar 2010 08:19:08 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: trac@localhost.amsl.com
References: <074.00f38bdd51aa79f0265b2a39a5ed89f0@tools.ietf.org> <083.8d1f1e237e6a33ff6de5ecbf9434a306@tools.ietf.org>
In-Reply-To: <083.8d1f1e237e6a33ff6de5ecbf9434a306@tools.ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Received-SPF: pass (nostrum.com: 70.249.147.216 is authenticated by a trusted mechanism)
Cc: martini issue tracker <trac@tools.ietf.org>, martini@ietf.org
Subject: Re: [martini] #6: AORs other than telephone numbers
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, 02 Mar 2010 14:19:11 -0000

On 3/2/10 04:13, Mar 2, martini issue tracker wrote:
> #6: AORs other than telephone numbers
> ----------------------------------------------+-----------------------------
>   Reporter:  bruno.chatras@…                   |       Owner:  john.elwell@…
>       Type:  defect                            |      Status:  assigned
>   Priority:  critical                          |   Milestone:  milestone1
> Component:  reqs                              |     Version:  1.0
>   Severity:  In WG Last Call                   |    Keywords:
> ----------------------------------------------+-----------------------------
> Changes (by john.elwell@…):
>
>    * status:  new =>  assigned
>
>
> Comment:
>
>   [JRE] We already achieved consensus in the past to support only E.164
>   numbers in our first deliverables. However, I notice the proposal is only
>   for a Desirable, so what do people think?
>    

I thought we had pretty well closed this issue as well. My understanding 
is that the current document -- the one in WGLC -- is relevant only to 
this first goal for E.164 numbers. It would be a bit silly to add 
requirements -- even at a "desirable" level -- that we have no intention 
of attempting to accommodate.

/a

From spencer@wonderhamster.org  Tue Mar  2 08:49:07 2010
Return-Path: <spencer@wonderhamster.org>
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 1934928C14E for <martini@core3.amsl.com>; Tue,  2 Mar 2010 08:49:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.265
X-Spam-Level: 
X-Spam-Status: No, score=-3.265 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 jcrt8t2lY1it for <martini@core3.amsl.com>; Tue,  2 Mar 2010 08:49:06 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 4127C28C0D8 for <martini@ietf.org>; Tue,  2 Mar 2010 08:49:06 -0800 (PST)
Received: from S73602b (w147.z209031239.sjc-ca.dsl.cnc.net [209.31.239.147]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0LeNJV-1NN8Cd49FN-00q2Aw; Tue, 02 Mar 2010 11:49:03 -0500
Message-ID: <3F3263654C6C45E3A766175063D0538C@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Adam Roach" <adam@nostrum.com>, <martini@ietf.org>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com> <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net>
Date: Tue, 2 Mar 2010 10:48:51 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1+sMUKtt/NAegrAsTz8V5XBexjO04m7UD5kba3 0wy6g3p4HByugbd/pVUeCKz9ZSMRfLtgXsRNH4xEGKVded2TAq 4I4MhHtbRaUweSYU/9XocdwreCV17QWdEpjblUkFUg=
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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, 02 Mar 2010 16:49:07 -0000

Hi, John,

>> Is the fragmentation issue so profound that we're really going to see
>> PBXes with more than 70 contiguous *RANGES* of DIDs? That
>> seems edging
>> into the "implausible" area of these two extremes.
> [JRE] I agree we are talking about ranges. My only concern is that people 
> are saying that fragmentation will be a lot more severe in future, as 
> number portability gets going, so in the worst case you could be limited 
> to 70 numbers. Personally I don't mind if MARTINI is restricted to quite 
> small PBXs, and we use RFC 3263 for anything bigger, but I don't think the 
> SSPs want to place the cut-off point as low as 70.
>
> So if we can agree that 70 ranges is sufficient and 70 dicrete numbers is 
> an extreme that we are unlikely to meet in practice, or in the rare case 
> we do we rely on it working through fragmentation or by switching to TCP, 
> that would be OK with me.
>
> So are we moving to a consensus that we should delete DES2, on the basis 
> that it is unrealistic. Or do we need an alternative requirement expressed 
> in number of ranges?

I understood Adam's note as saying that

- the right answer is to use TCP (as a fallback, at minimum), so we don't 
need to specify a limit.

- if people don't use TCP (at least as a fallback), a larger number of AoR 
(ranges) will probably still work just based on IP fragmentation.

- if this doesn't work (because you punted TCP AND decided to enforce the 
UDP MTU limit), that's your problem to solve, and the suggested answer would 
be to either stop punting TCP or start using RFC 3263.

I think Adam and I broadly agree here, and that no change to the document is 
required.

Does anyone (especially Adam, because I think I'm agreeing with him :-) 
disagree?

Spencer 


From bruno.chatras@orange-ftgroup.com  Tue Mar  2 09:34:52 2010
Return-Path: <bruno.chatras@orange-ftgroup.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 840493A8AA0 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 09:34:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 8doS+t+dlM7m for <martini@core3.amsl.com>; Tue,  2 Mar 2010 09:34:51 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 147103A8BC4 for <martini@ietf.org>; Tue,  2 Mar 2010 09:34:51 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 430E08B8005; Tue,  2 Mar 2010 18:33:52 +0000 (UTC)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id 3C39D8B8009; Tue,  2 Mar 2010 18:33:51 +0000 (UTC)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 2 Mar 2010 18:34:43 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 2 Mar 2010 18:34:42 +0100
Message-ID: <9ECCF01B52E7AB408A7EB853526421410128FC1B@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <4B8D1E5C.8020001@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] #6: AORs other than telephone numbers
Thread-Index: Acq6E2mTrpbs/gKFRKeP7dvbuuRmKgAAZGBA
References: <074.00f38bdd51aa79f0265b2a39a5ed89f0@tools.ietf.org><083.8d1f1e237e6a33ff6de5ecbf9434a306@tools.ietf.org> <4B8D1E5C.8020001@nostrum.com>
From: <bruno.chatras@orange-ftgroup.com>
To: <adam@nostrum.com>, <trac@localhost.amsl.com>
X-OriginalArrivalTime: 02 Mar 2010 17:34:43.0523 (UTC) FILETIME=[A5224930:01CABA2E]
Cc: trac@tools.ietf.org, martini@ietf.org
Subject: Re: [martini] #6: AORs other than telephone numbers
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, 02 Mar 2010 17:34:52 -0000

This is desirable from the point of view of some operators at least. The =
fact that most people in the MARTINI group have no intention to =
accomodate this requirement does not make it irrelevant.=20

If this is not included as a desired requirement, more text is needed in =
this document to explain why this was seen as a non requirement by the =
MARTINI WG. Otherwise anyone reading this RFC later without having been =
involved in MARTINI's  discussions will not understand why this was =
discarded.

BC

> -----Message d'origine-----
> De : martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] De la part de Adam Roach
> Envoy=E9 : mardi 2 mars 2010 15:19
> =C0 : trac@localhost.amsl.com
> Cc : martini issue tracker; martini@ietf.org
> Objet : Re: [martini] #6: AORs other than telephone numbers
>=20
> On 3/2/10 04:13, Mar 2, martini issue tracker wrote:
> > #6: AORs other than telephone numbers
> >=20
> ----------------------------------------------+-----------------------
> > ----------------------------------------------+------
> >   Reporter:  bruno.chatras@...                   |      =20
> Owner:  john.elwell@...
> >       Type:  defect                            |     =20
> Status:  assigned
> >   Priority:  critical                          |  =20
> Milestone:  milestone1
> > Component:  reqs                              |     Version:  1.0
> >   Severity:  In WG Last Call                   |    Keywords:
> >=20
> ----------------------------------------------+-----------------------
> > ----------------------------------------------+------
> > Changes (by john.elwell@...):
> >
> >    * status:  new =3D>  assigned
> >
> >
> > Comment:
> >
> >   [JRE] We already achieved consensus in the past to=20
> support only E.164
> >   numbers in our first deliverables. However, I notice the=20
> proposal is only
> >   for a Desirable, so what do people think?
> >   =20
>=20
> I thought we had pretty well closed this issue as well. My=20
> understanding is that the current document -- the one in WGLC=20
> -- is relevant only to this first goal for E.164 numbers. It=20
> would be a bit silly to add requirements -- even at a=20
> "desirable" level -- that we have no intention of attempting=20
> to accommodate.
>=20
> /a
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>=20

From dean.willis@softarmor.com  Tue Mar  2 09:51:43 2010
Return-Path: <dean.willis@softarmor.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 2C81828C203 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 09:51:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Ndyj+0LecIH4 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 09:51:42 -0800 (PST)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 662003A8BE7 for <martini@ietf.org>; Tue,  2 Mar 2010 09:51:42 -0800 (PST)
Received: from [192.168.2.102] (cpe-66-25-30-183.tx.res.rr.com [66.25.30.183]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id o22Hpfep025577 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 2 Mar 2010 11:51:42 -0600
Message-Id: <BC8FD4F6-5657-4AA4-BE31-837443E0F5AB@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Adam Roach <adam@nostrum.com>
In-Reply-To: <4B8D1E5C.8020001@nostrum.com>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 2 Mar 2010 11:51:35 -0600
References: <074.00f38bdd51aa79f0265b2a39a5ed89f0@tools.ietf.org> <083.8d1f1e237e6a33ff6de5ecbf9434a306@tools.ietf.org> <4B8D1E5C.8020001@nostrum.com>
X-Mailer: Apple Mail (2.936)
Cc: martini issue tracker <trac@tools.ietf.org>, trac@localhost.amsl.com, martini@ietf.org
Subject: Re: [martini] #6: AORs other than telephone numbers
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, 02 Mar 2010 17:51:43 -0000

On Mar 2, 2010, at 8:19 AM, Adam Roach wrote:

> On 3/2/10 04:13, Mar 2, martini issue tracker wrote:
>> #6: AORs other than telephone numbers
>> ----------------------------------------------=20
>> +-----------------------------
>>  Reporter:  bruno.chatras@=85                   |       Owner:  =20
>> john.elwell@=85
>>      Type:  defect                            |      Status:  =20
>> assigned
>>  Priority:  critical                          |   Milestone:  =20
>> milestone1
>> Component:  reqs                              |     Version:  1.0
>>  Severity:  In WG Last Call                   |    Keywords:
>> ----------------------------------------------=20
>> +-----------------------------
>> Changes (by john.elwell@=85):
>>
>>   * status:  new =3D>  assigned
>>
>>
>> Comment:
>>
>>  [JRE] We already achieved consensus in the past to support only E.=20=

>> 164
>>  numbers in our first deliverables. However, I notice the proposal =20=

>> is only
>>  for a Desirable, so what do people think?
>>
>
> I thought we had pretty well closed this issue as well. My =20
> understanding is that the current document -- the one in WGLC -- is =20=

> relevant only to this first goal for E.164 numbers. It would be a =20
> bit silly to add requirements -- even at a "desirable" level -- that =20=

> we have no intention of attempting to accommodate.

This suggests something like a separate "Phase 2" requirements document.

--
Dean


From dean.willis@softarmor.com  Tue Mar  2 09:56:37 2010
Return-Path: <dean.willis@softarmor.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 53D8028C1D6 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 09:56:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 ecxwIGy6Xfhx for <martini@core3.amsl.com>; Tue,  2 Mar 2010 09:56:36 -0800 (PST)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 5EECF28C13B for <martini@ietf.org>; Tue,  2 Mar 2010 09:56:36 -0800 (PST)
Received: from [192.168.2.102] (cpe-66-25-30-183.tx.res.rr.com [66.25.30.183]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id o22HuZKp025639 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 2 Mar 2010 11:56:36 -0600
Message-Id: <4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "Spencer Dawkins" <spencer@wonderhamster.org>
In-Reply-To: <3F3263654C6C45E3A766175063D0538C@china.huawei.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-21--664902150
Mime-Version: 1.0 (Apple Message framework v936)
X-Priority: 3
Date: Tue, 2 Mar 2010 11:56:30 -0600
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com> <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net> <3F3263654C6C45E3A766175063D0538C@china.huawei.com>
X-Mailer: Apple Mail (2.936)
Cc: martini@ietf.org
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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, 02 Mar 2010 17:56:37 -0000

--Apple-Mail-21--664902150
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit


On Mar 2, 2010, at 10:48 AM, Spencer Dawkins wrote:
>
> I understood Adam's note as saying that
>
> - the right answer is to use TCP (as a fallback, at minimum), so we  
> don't need to specify a limit.
>
> - if people don't use TCP (at least as a fallback), a larger number  
> of AoR (ranges) will probably still work just based on IP  
> fragmentation.
>
> - if this doesn't work (because you punted TCP AND decided to  
> enforce the UDP MTU limit), that's your problem to solve, and the  
> suggested answer would be to either stop punting TCP or start using  
> RFC 3263.
>
> I think Adam and I broadly agree here, and that no change to the  
> document is required.
>
> Does anyone (especially Adam, because I think I'm agreeing with  
> him :-) disagree?
>

I agree with this set of statements.

However, I will warn us that the "transport police" will probably take  
exception. Congestion-induced retransmission of 64k UDP packets is  
pretty much a text-book example of what they think "harms the Internet".

 From a standards perspective, it would arguably be better to say that  
large registrations MUST be entirely processed over TCP, even though  
we know full well that nobody is going to bother, and that they're  
going to continue with fragmented UDP right until the world's ice caps  
melt from the global warming caused by the excess router-CPU needed to  
process all those retransmitted fragments.

I feel dirty.

--
Dean
--Apple-Mail-21--664902150
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On Mar 2, 2010, =
at 10:48 AM, Spencer Dawkins wrote:</div><blockquote =
type=3D"cite"><div><font class=3D"Apple-style-span" =
color=3D"#000000"><br></font>I understood Adam's note as saying =
that<br><br>- the right answer is to use TCP (as a fallback, at =
minimum), so we don't need to specify a limit.<br><br>- if people don't =
use TCP (at least as a fallback), a larger number of AoR (ranges) will =
probably still work just based on IP fragmentation.<br><br>- if this =
doesn't work (because you punted TCP AND decided to enforce the UDP MTU =
limit), that's your problem to solve, and the suggested answer would be =
to either stop punting TCP or start using RFC 3263.<br><br>I think Adam =
and I broadly agree here, and that no change to the document is =
required.<br><br>Does anyone (especially Adam, because I think I'm =
agreeing with him :-) =
disagree?<br><br></div></blockquote></div><br><div>I agree with this set =
of statements.&nbsp;</div><div><br></div><div>However, I will warn us =
that the "transport police" will probably take exception. =
Congestion-induced retransmission of 64k UDP packets is pretty much a =
text-book example of what they think "harms the =
Internet".</div><div><br></div><div>=46rom a standards perspective, it =
would arguably be better to say that large registrations MUST be =
entirely processed over TCP, even though we know full well that nobody =
is going to bother, and that they're going to continue with fragmented =
UDP right until the world's ice caps melt from the global warming caused =
by the excess router-CPU needed to process all those retransmitted =
fragments.</div><div><br></div><div>I feel =
dirty.</div><div><br></div><div>--</div><div>Dean</div></body></html>=

--Apple-Mail-21--664902150--

From spencer@wonderhamster.org  Tue Mar  2 10:11:24 2010
Return-Path: <spencer@wonderhamster.org>
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 5B62328C225 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 10:11:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.098
X-Spam-Level: 
X-Spam-Status: No, score=-3.098 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 A8vF-nnUT4tj for <martini@core3.amsl.com>; Tue,  2 Mar 2010 10:11:21 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 1E61528C1DD for <martini@ietf.org>; Tue,  2 Mar 2010 10:11:21 -0800 (PST)
Received: from S73602b (w147.z209031239.sjc-ca.dsl.cnc.net [209.31.239.147]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MSLTP-1OAyWM26QN-00TeKH; Tue, 02 Mar 2010 13:11:14 -0500
Message-ID: <BFC410373E034190957204A7FEDEC217@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Dean Willis" <dean.willis@softarmor.com>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com> <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net> <3F3263654C6C45E3A766175063D0538C@china.huawei.com> <4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com>
Date: Tue, 2 Mar 2010 12:10:59 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0C65_01CABA01.6BC3D410"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1+WrJyyAUChrSHrM+85tyL1BBCekwl5y5+uroE hqX6uxd9dUoHBk2KKt28ClI3zNGp3G0wHvonfTaa2E0ZVUyheF Dx4agkQk/rvOgzWj0EXsJvhZWAyI8tjrPt6m48PHLs=
Cc: martini@ietf.org
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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, 02 Mar 2010 18:11:24 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0C65_01CABA01.6BC3D410
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I'm sitting in a room with all three TSV ADs now, so I should be able to =
avoid blindsiding them at IETF Last Call time... but until then - my =
understanding is that this text in RFC 3261 is overarching:

18.1.1 Sending Requests
   The client side of the transport layer is responsible for sending the
   request and receiving responses.  The user of the transport layer
   passes the client transport the request, an IP address, port,
   transport, and possibly TTL for multicast destinations.

   If a request is within 200 bytes of the path MTU, or if it is larger
   than 1300 bytes and the path MTU is unknown, the request MUST be sent
   using an RFC 2914 [43] congestion controlled transport protocol, such
   as TCP. If this causes a change in the transport protocol from the
   one indicated in the top Via, the value in the top Via MUST be
   changed.  This prevents fragmentation of messages over UDP and
   provides congestion control for larger messages.  However,
   implementations MUST be able to handle messages up to the maximum
   datagram packet size.  For UDP, this size is 65,535 bytes, including
   IP and UDP headers.
If I'm right about that, any conformant implementation will work, and =
I'm not sure that saying "we really, really mean what RFC 3261 says" is =
going to change anything that will affect non-conforming =
implementations.

So, speaking as an individual, I'd say "no change to our document =
required". Bernard, want to call this one as chair?

Spencer
  ----- Original Message -----=20
  From: Dean Willis=20
  To: Spencer Dawkins=20
  Cc: Elwell, John ; Adam Roach ; martini@ietf.org=20
  Sent: Tuesday, March 02, 2010 11:56 AM
  Subject: Re: [martini] #2: Scaling to Several Thousand Assigned =
Telephone Numbers




  On Mar 2, 2010, at 10:48 AM, Spencer Dawkins wrote:

    I understood Adam's note as saying that

    - the right answer is to use TCP (as a fallback, at minimum), so we =
don't need to specify a limit.

    - if people don't use TCP (at least as a fallback), a larger number =
of AoR (ranges) will probably still work just based on IP fragmentation.

    - if this doesn't work (because you punted TCP AND decided to =
enforce the UDP MTU limit), that's your problem to solve, and the =
suggested answer would be to either stop punting TCP or start using RFC =
3263.

    I think Adam and I broadly agree here, and that no change to the =
document is required.

    Does anyone (especially Adam, because I think I'm agreeing with him =
:-) disagree?




  I agree with this set of statements.=20


  However, I will warn us that the "transport police" will probably take =
exception. Congestion-induced retransmission of 64k UDP packets is =
pretty much a text-book example of what they think "harms the Internet".


  From a standards perspective, it would arguably be better to say that =
large registrations MUST be entirely processed over TCP, even though we =
know full well that nobody is going to bother, and that they're going to =
continue with fragmented UDP right until the world's ice caps melt from =
the global warming caused by the excess router-CPU needed to process all =
those retransmitted fragments.


  I feel dirty.


  --
  Dean
------=_NextPart_000_0C65_01CABA01.6BC3D410
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18876">
<STYLE></STYLE>
</HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space"=20
bgColor=3D#ffffff>
<DIV><FONT size=3D2>I'm sitting in a room with all three TSV ADs now, so =
I should=20
be able to avoid blindsiding them at IETF Last Call time... but until =
then -=20
m</FONT><FONT size=3D2>y understanding is that this text in RFC 3261 is=20
overarching:</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><SPAN=20
style=3D"WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; =
BORDER-COLLAPSE: separate; FONT: medium 'Times New Roman'; WHITE-SPACE: =
normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); =
WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px"=20
class=3DApple-style-span><SPAN style=3D"FONT-SIZE: 40px" =
class=3DApple-style-span><PRE style=3D"PAGE-BREAK-BEFORE: always; =
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; FONT-SIZE: 1em" =
class=3Dnewpage><SPAN style=3D"LINE-HEIGHT: 0pt; DISPLAY: inline; =
FONT-FAMILY: monospace; WHITE-SPACE: pre; FONT-SIZE: 1em; FONT-WEIGHT: =
bold" class=3Dh4><H4 style=3D"LINE-HEIGHT: 0pt; DISPLAY: inline; =
FONT-FAMILY: monospace; WHITE-SPACE: pre; FONT-SIZE: 1em; FONT-WEIGHT: =
bold"><A name=3Dsection-18.1.1><FONT size=3D3>18.1.1</FONT></A><FONT =
size=3D3> Sending Requests</FONT></H4></SPAN>
<FONT size=3D3></FONT></PRE><PRE style=3D"PAGE-BREAK-BEFORE: always; =
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; FONT-SIZE: 1em" =
class=3Dnewpage><FONT size=3D3>   The client side of the transport layer =
is responsible for sending the
   request and receiving responses.  The user of the transport layer
   passes the client transport the request, an IP address, port,
   transport, and possibly TTL for multicast destinations.

<FONT color=3D#0000ff>   If a request is within 200 bytes of the path =
MTU, or if it is larger
   than 1300 bytes and the path MTU is unknown, the request MUST be sent
   using an </FONT></FONT><A href=3D"./rfc2914"><FONT size=3D3>RFC =
2914</FONT></A><FONT color=3D#0000ff size=3D3> [</FONT><A =
title=3D'"Congestion Control Principles"' =
href=3D"mhtml:mid://00003169/#ref-43"><FONT size=3D3>43</FONT></A><FONT =
size=3D3><FONT color=3D#0000ff>] congestion controlled transport =
protocol, such
   as TCP.</FONT> If this causes a change in the transport protocol from =
the
   one indicated in the top Via, the value in the top Via MUST be
   changed.  This prevents fragmentation of messages over UDP and
   provides congestion control for larger messages.  <FONT =
color=3D#0000ff>However,
   implementations MUST be able to handle messages up to the maximum
   datagram packet size.  For UDP, this size is 65,535 bytes, including
   IP and UDP headers.</FONT></FONT></PRE></SPAN></SPAN></FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>If I'm right about that, any conformant =
implementation will=20
work, and I'm not sure that saying "we really, really mean what RFC 3261 =
says"=20
is going to change anything that will affect non-conforming=20
implementations.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>So, speaking as an individual, I'd say "no change to =
our=20
document required". Bernard, want to call this one as =
chair?</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Spencer</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; =
PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"=20
dir=3Dltr>
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: =
black"><B>From:</B>=20
  <A title=3Ddean.willis@softarmor.com=20
  href=3D"mailto:dean.willis@softarmor.com">Dean Willis</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dspencer@wonderhamster.org=20
  href=3D"mailto:spencer@wonderhamster.org">Spencer Dawkins</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A=20
  title=3Djohn.elwell@siemens-enterprise.com=20
  href=3D"mailto:john.elwell@siemens-enterprise.com">Elwell, John</A> ; =
<A=20
  title=3Dadam@nostrum.com href=3D"mailto:adam@nostrum.com">Adam =
Roach</A> ; <A=20
  title=3Dmartini@ietf.org =
href=3D"mailto:martini@ietf.org">martini@ietf.org</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, March 02, 2010 =
11:56=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [martini] #2: =
Scaling to=20
  Several Thousand Assigned Telephone Numbers</DIV>
  <DIV><BR></DIV><BR>
  <DIV>
  <DIV>On Mar 2, 2010, at 10:48 AM, Spencer Dawkins wrote:</DIV>
  <BLOCKQUOTE type=3D"cite">
    <DIV><FONT class=3DApple-style-span color=3D#000000><BR></FONT>I =
understood=20
    Adam's note as saying that<BR><BR>- the right answer is to use TCP =
(as a=20
    fallback, at minimum), so we don't need to specify a limit.<BR><BR>- =
if=20
    people don't use TCP (at least as a fallback), a larger number of =
AoR=20
    (ranges) will probably still work just based on IP =
fragmentation.<BR><BR>-=20
    if this doesn't work (because you punted TCP AND decided to enforce =
the UDP=20
    MTU limit), that's your problem to solve, and the suggested answer =
would be=20
    to either stop punting TCP or start using RFC 3263.<BR><BR>I think =
Adam and=20
    I broadly agree here, and that no change to the document is=20
    required.<BR><BR>Does anyone (especially Adam, because I think I'm =
agreeing=20
    with him :-) disagree?<BR><BR></DIV></BLOCKQUOTE></DIV><BR>
  <DIV>I agree with this set of statements.&nbsp;</DIV>
  <DIV><BR></DIV>
  <DIV>However, I will warn us that the "transport police" will probably =
take=20
  exception. Congestion-induced retransmission of 64k UDP packets is =
pretty much=20
  a text-book example of what they think "harms the Internet".</DIV>
  <DIV><BR></DIV>
  <DIV>From a standards perspective, it would arguably be better to say =
that=20
  large registrations MUST be entirely processed over TCP, even though =
we know=20
  full well that nobody is going to bother, and that they're going to =
continue=20
  with fragmented UDP right until the world's ice caps melt from the =
global=20
  warming caused by the excess router-CPU needed to process all those=20
  retransmitted fragments.</DIV>
  <DIV><BR></DIV>
  <DIV>I feel dirty.</DIV>
  <DIV><BR></DIV>
  <DIV>--</DIV>
  <DIV>Dean</DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0C65_01CABA01.6BC3D410--


From bruno.chatras@orange-ftgroup.com  Tue Mar  2 10:24:57 2010
Return-Path: <bruno.chatras@orange-ftgroup.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 209FF28C257 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 10:24:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 nVg1tF6b0U3q for <martini@core3.amsl.com>; Tue,  2 Mar 2010 10:24:54 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id E58B928C233 for <martini@ietf.org>; Tue,  2 Mar 2010 10:24:53 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 05EC98B8078; Tue,  2 Mar 2010 19:21:34 +0000 (UTC)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id 42FA38B8084; Tue,  2 Mar 2010 19:17:17 +0000 (UTC)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 2 Mar 2010 19:17:59 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 2 Mar 2010 19:17:57 +0100
Message-ID: <9ECCF01B52E7AB408A7EB853526421410128FC5F@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <BC8FD4F6-5657-4AA4-BE31-837443E0F5AB@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] #6: AORs other than telephone numbers
Thread-Index: Acq6MTRKzaApDL8dS6S8gZZn9rTVawAA0G0A
References: <074.00f38bdd51aa79f0265b2a39a5ed89f0@tools.ietf.org><083.8d1f1e237e6a33ff6de5ecbf9434a306@tools.ietf.org><4B8D1E5C.8020001@nostrum.com> <BC8FD4F6-5657-4AA4-BE31-837443E0F5AB@softarmor.com>
From: <bruno.chatras@orange-ftgroup.com>
To: <dean.willis@softarmor.com>, <adam@nostrum.com>
X-OriginalArrivalTime: 02 Mar 2010 18:17:59.0433 (UTC) FILETIME=[B06AB790:01CABA34]
Cc: trac@localhost.amsl.com, trac@tools.ietf.org, martini@ietf.org
Subject: Re: [martini] #6: AORs other than telephone numbers
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, 02 Mar 2010 18:24:57 -0000

The problem I see with a separate phase 2 document is the risk to come =
with 2 totally different solutions for a PBX to support simultaneously =
when both types of URIs are used.

> -----Message d'origine-----
> De : martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] De la part de Dean Willis
> Envoy=E9 : mardi 2 mars 2010 18:52
> =C0 : Adam Roach
> Cc : martini issue tracker; trac@localhost.amsl.com; martini@ietf.org
> Objet : Re: [martini] #6: AORs other than telephone numbers
>=20
>=20
> On Mar 2, 2010, at 8:19 AM, Adam Roach wrote:
>=20
> > On 3/2/10 04:13, Mar 2, martini issue tracker wrote:
> >> #6: AORs other than telephone numbers
> >> ----------------------------------------------
> >> +-----------------------------
> >>  Reporter:  bruno.chatras@...                   |       Owner:  =20
> >> john.elwell@...
> >>      Type:  defect                            |      Status:  =20
> >> assigned
> >>  Priority:  critical                          |   Milestone:  =20
> >> milestone1
> >> Component:  reqs                              |     Version:  1.0
> >>  Severity:  In WG Last Call                   |    Keywords:
> >> ----------------------------------------------
> >> +-----------------------------
> >> Changes (by john.elwell@...):
> >>
> >>   * status:  new =3D>  assigned
> >>
> >>
> >> Comment:
> >>
> >>  [JRE] We already achieved consensus in the past to=20
> support only E.=20
> >> 164
> >>  numbers in our first deliverables. However, I notice the=20
> proposal is=20
> >> only  for a Desirable, so what do people think?
> >>
> >
> > I thought we had pretty well closed this issue as well. My=20
> > understanding is that the current document -- the one in WGLC -- is=20
> > relevant only to this first goal for E.164 numbers. It=20
> would be a bit=20
> > silly to add requirements -- even at a "desirable" level -- that we=20
> > have no intention of attempting to accommodate.
>=20
> This suggests something like a separate "Phase 2"=20
> requirements document.
>=20
> --
> Dean
>=20
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>=20

From spencer@wonderhamster.org  Tue Mar  2 11:08:54 2010
Return-Path: <spencer@wonderhamster.org>
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 247D73A8C64 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 11:08:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.998
X-Spam-Level: 
X-Spam-Status: No, score=-2.998 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 mGW0DJ+B5mTP for <martini@core3.amsl.com>; Tue,  2 Mar 2010 11:08:52 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id A59A23A8C61 for <martini@ietf.org>; Tue,  2 Mar 2010 11:08:52 -0800 (PST)
Received: from S73602b (w147.z209031239.sjc-ca.dsl.cnc.net [209.31.239.147]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0LtZUK-1Ncg7j1PQy-011Fy5; Tue, 02 Mar 2010 14:08:52 -0500
Message-ID: <88169CA4B5904BFF924E79B2A89E43A4@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: <martini@ietf.org>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com><A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net><3F3263654C6C45E3A766175063D0538C@china.huawei.com><4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com> <BFC410373E034190957204A7FEDEC217@china.huawei.com>
Date: Tue, 2 Mar 2010 13:08:43 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0C8C_01CABA09.7C16A010"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX19Zarx3l6UKAWQNguxU47CyGDJ5QUDxUtNj3lR ALAD1BxcWc/vsUI5rXv9QROTajElkukJma0VAL7VvvEji6D+py OJaeSjLSzrs9WM2vC/6kSIxizAL6R43K+1nKdAFwMY=
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned TelephoneNumbers
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, 02 Mar 2010 19:08:54 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0C8C_01CABA09.7C16A010
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Following up on my own post...

I chatted with Lars and with David Harrington (incoming TSV AD, who will =
be seated before the IESG ballots the requirements draft).

Here's the guidance I got:

- No need to mention this in requirements,

- No need to pick a number of AoR ranges to support,

- Does need to be mentioned in a protocol draft,

- Would be sufficient to point the issue out and say something like =
"implementations that already violate the "MUST use a =
congestion-controlled transport such as TCP when sending a request that =
is large enough to be IP-fragmented" in 3261 may have problems =
traversing NATs and losing fragmented IP packets when the network is =
congested; the solution is to use TCP as already required in 3261".

Adam, could you add this to your list for GIN? I can propose more formal =
text if that's helpful.

Thanks,

Spencer
  ----- Original Message ----- =20
  From: Spencer Dawkins=20
  To: Dean Willis=20
  Cc: martini@ietf.org=20
  Sent: Tuesday, March 02, 2010 12:10 PM
  Subject: Re: [martini] #2: Scaling to Several Thousand Assigned =
TelephoneNumbers


  I'm sitting in a room with all three TSV ADs now, so I should be able =
to avoid blindsiding them at IETF Last Call time... but until then - my =
understanding is that this text in RFC 3261 is overarching:

18.1.1 Sending Requests
   The client side of the transport layer is responsible for sending the
   request and receiving responses.  The user of the transport layer
   passes the client transport the request, an IP address, port,
   transport, and possibly TTL for multicast destinations.

   If a request is within 200 bytes of the path MTU, or if it is larger
   than 1300 bytes and the path MTU is unknown, the request MUST be sent
   using an RFC 2914 [43] congestion controlled transport protocol, such
   as TCP. If this causes a change in the transport protocol from the
   one indicated in the top Via, the value in the top Via MUST be
   changed.  This prevents fragmentation of messages over UDP and
   provides congestion control for larger messages.  However,
   implementations MUST be able to handle messages up to the maximum
   datagram packet size.  For UDP, this size is 65,535 bytes, including
   IP and UDP headers.
  If I'm right about that, any conformant implementation will work, and =
I'm not sure that saying "we really, really mean what RFC 3261 says" is =
going to change anything that will affect non-conforming =
implementations.

  So, speaking as an individual, I'd say "no change to our document =
required". Bernard, want to call this one as chair?

  Spencer
    ----- Original Message -----=20
    From: Dean Willis=20
    To: Spencer Dawkins=20
    Cc: Elwell, John ; Adam Roach ; martini@ietf.org=20
    Sent: Tuesday, March 02, 2010 11:56 AM
    Subject: Re: [martini] #2: Scaling to Several Thousand Assigned =
Telephone Numbers




    On Mar 2, 2010, at 10:48 AM, Spencer Dawkins wrote:

      I understood Adam's note as saying that

      - the right answer is to use TCP (as a fallback, at minimum), so =
we don't need to specify a limit.

      - if people don't use TCP (at least as a fallback), a larger =
number of AoR (ranges) will probably still work just based on IP =
fragmentation.

      - if this doesn't work (because you punted TCP AND decided to =
enforce the UDP MTU limit), that's your problem to solve, and the =
suggested answer would be to either stop punting TCP or start using RFC =
3263.

      I think Adam and I broadly agree here, and that no change to the =
document is required.

      Does anyone (especially Adam, because I think I'm agreeing with =
him :-) disagree?




    I agree with this set of statements.=20


    However, I will warn us that the "transport police" will probably =
take exception. Congestion-induced retransmission of 64k UDP packets is =
pretty much a text-book example of what they think "harms the Internet".


    From a standards perspective, it would arguably be better to say =
that large registrations MUST be entirely processed over TCP, even =
though we know full well that nobody is going to bother, and that =
they're going to continue with fragmented UDP right until the world's =
ice caps melt from the global warming caused by the excess router-CPU =
needed to process all those retransmitted fragments.


    I feel dirty.


    --
    Dean


-------------------------------------------------------------------------=
-----


  _______________________________________________
  martini mailing list
  martini@ietf.org
  https://www.ietf.org/mailman/listinfo/martini

------=_NextPart_000_0C8C_01CABA09.7C16A010
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18876">
<STYLE></STYLE>
</HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space"=20
bgColor=3D#ffffff>
<DIV><FONT size=3D2>Following up on my own post...</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>I chatted with Lars and with David Harrington =
(incoming TSV=20
AD, who will be seated before the IESG ballots the requirements=20
draft).</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Here's the guidance I got:</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>- No need to mention this in =
requirements,</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>- No need to pick a number of AoR ranges to=20
support,</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>- Does need to be mentioned in a protocol =
draft,</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>- Would be sufficient to point the issue out and say =
something=20
like "implementations that already violate the "MUST use=20
a&nbsp;congestion-controlled transport such as TCP when sending a =
request that=20
is large enough to be IP-fragmented" in 3261 may have problems =
traversing NATs=20
and losing fragmented IP packets when the network is congested; the =
solution is=20
to use TCP as already required in 3261".</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Adam, could you add this to your list for GIN? I can =
propose=20
more formal text if that's helpful.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Thanks,</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Spencer</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; =
PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message -----&nbsp; =
</DIV>
  <DIV=20
  style=3D"FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: =
black"><B>From:</B>=20
  <A title=3Dspencer@wonderhamster.org=20
  href=3D"mailto:spencer@wonderhamster.org">Spencer Dawkins</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Ddean.willis@softarmor.com=20
  href=3D"mailto:dean.willis@softarmor.com">Dean Willis</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A title=3Dmartini@ietf.org =

  href=3D"mailto:martini@ietf.org">martini@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, March 02, 2010 =
12:10=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [martini] #2: =
Scaling to=20
  Several Thousand Assigned TelephoneNumbers</DIV>
  <DIV><BR></DIV>
  <DIV><FONT size=3D2>I'm sitting in a room with all three TSV ADs now, =
so I=20
  should be able to avoid blindsiding them at IETF Last Call time... but =
until=20
  then - m</FONT><FONT size=3D2>y understanding is that this text in RFC =
3261 is=20
  overarching:</FONT></DIV>
  <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2><SPAN=20
  style=3D"WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; =
BORDER-COLLAPSE: separate; FONT: medium 'Times New Roman'; WHITE-SPACE: =
normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); =
WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px"=20
  class=3DApple-style-span><SPAN style=3D"FONT-SIZE: 40px" =
class=3DApple-style-span><PRE style=3D"PAGE-BREAK-BEFORE: always; =
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; FONT-SIZE: 1em" =
class=3Dnewpage><SPAN style=3D"LINE-HEIGHT: 0pt; DISPLAY: inline; =
FONT-FAMILY: monospace; WHITE-SPACE: pre; FONT-SIZE: 1em; FONT-WEIGHT: =
bold" class=3Dh4><H4 style=3D"LINE-HEIGHT: 0pt; DISPLAY: inline; =
FONT-FAMILY: monospace; WHITE-SPACE: pre; FONT-SIZE: 1em; FONT-WEIGHT: =
bold"><A name=3Dsection-18.1.1><FONT size=3D3>18.1.1</FONT></A><FONT =
size=3D3> Sending Requests</FONT></H4></SPAN>
<FONT size=3D3></FONT></PRE><PRE style=3D"PAGE-BREAK-BEFORE: always; =
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; FONT-SIZE: 1em" =
class=3Dnewpage><FONT size=3D3>   The client side of the transport layer =
is responsible for sending the
   request and receiving responses.  The user of the transport layer
   passes the client transport the request, an IP address, port,
   transport, and possibly TTL for multicast destinations.

<FONT color=3D#0000ff>   If a request is within 200 bytes of the path =
MTU, or if it is larger
   than 1300 bytes and the path MTU is unknown, the request MUST be sent
   using an </FONT></FONT><A href=3D"./rfc2914"><FONT size=3D3>RFC =
2914</FONT></A><FONT color=3D#0000ff size=3D3> [</FONT><A =
title=3D'"Congestion Control Principles"' =
href=3D"mhtml:mid://00003169/#ref-43"><FONT size=3D3>43</FONT></A><FONT =
size=3D3><FONT color=3D#0000ff>] congestion controlled transport =
protocol, such
   as TCP.</FONT> If this causes a change in the transport protocol from =
the
   one indicated in the top Via, the value in the top Via MUST be
   changed.  This prevents fragmentation of messages over UDP and
   provides congestion control for larger messages.  <FONT =
color=3D#0000ff>However,
   implementations MUST be able to handle messages up to the maximum
   datagram packet size.  For UDP, this size is 65,535 bytes, including
   IP and UDP headers.</FONT></FONT></PRE></SPAN></SPAN></FONT></DIV>
  <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2>If I'm right about that, any conformant =
implementation will=20
  work, and I'm not sure that saying "we really, really mean what RFC =
3261 says"=20
  is going to change anything that will affect non-conforming=20
  implementations.</FONT></DIV>
  <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2>So, speaking as an individual, I'd say "no change =
to our=20
  document required". Bernard, want to call this one as =
chair?</FONT></DIV>
  <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2>Spencer</FONT></DIV>
  <BLOCKQUOTE=20
  style=3D"BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; =
PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"=20
  dir=3Dltr>
    <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV=20
    style=3D"FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: =
black"><B>From:</B>=20
    <A title=3Ddean.willis@softarmor.com=20
    href=3D"mailto:dean.willis@softarmor.com">Dean Willis</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dspencer@wonderhamster.org=20
    href=3D"mailto:spencer@wonderhamster.org">Spencer Dawkins</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A=20
    title=3Djohn.elwell@siemens-enterprise.com=20
    href=3D"mailto:john.elwell@siemens-enterprise.com">Elwell, John</A> =
; <A=20
    title=3Dadam@nostrum.com href=3D"mailto:adam@nostrum.com">Adam =
Roach</A> ; <A=20
    title=3Dmartini@ietf.org =
href=3D"mailto:martini@ietf.org">martini@ietf.org</A>=20
    </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, March 02, 2010 =
11:56=20
    AM</DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [martini] #2: =
Scaling to=20
    Several Thousand Assigned Telephone Numbers</DIV>
    <DIV><BR></DIV><BR>
    <DIV>
    <DIV>On Mar 2, 2010, at 10:48 AM, Spencer Dawkins wrote:</DIV>
    <BLOCKQUOTE type=3D"cite">
      <DIV><FONT class=3DApple-style-span color=3D#000000><BR></FONT>I =
understood=20
      Adam's note as saying that<BR><BR>- the right answer is to use TCP =
(as a=20
      fallback, at minimum), so we don't need to specify a =
limit.<BR><BR>- if=20
      people don't use TCP (at least as a fallback), a larger number of =
AoR=20
      (ranges) will probably still work just based on IP =
fragmentation.<BR><BR>-=20
      if this doesn't work (because you punted TCP AND decided to =
enforce the=20
      UDP MTU limit), that's your problem to solve, and the suggested =
answer=20
      would be to either stop punting TCP or start using RFC =
3263.<BR><BR>I=20
      think Adam and I broadly agree here, and that no change to the =
document is=20
      required.<BR><BR>Does anyone (especially Adam, because I think I'm =

      agreeing with him :-) =
disagree?<BR><BR></DIV></BLOCKQUOTE></DIV><BR>
    <DIV>I agree with this set of statements.&nbsp;</DIV>
    <DIV><BR></DIV>
    <DIV>However, I will warn us that the "transport police" will =
probably take=20
    exception. Congestion-induced retransmission of 64k UDP packets is =
pretty=20
    much a text-book example of what they think "harms the =
Internet".</DIV>
    <DIV><BR></DIV>
    <DIV>From a standards perspective, it would arguably be better to =
say that=20
    large registrations MUST be entirely processed over TCP, even though =
we know=20
    full well that nobody is going to bother, and that they're going to =
continue=20
    with fragmented UDP right until the world's ice caps melt from the =
global=20
    warming caused by the excess router-CPU needed to process all those=20
    retransmitted fragments.</DIV>
    <DIV><BR></DIV>
    <DIV>I feel dirty.</DIV>
    <DIV><BR></DIV>
    <DIV>--</DIV>
    <DIV>Dean</DIV></BLOCKQUOTE>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>martini =
mailing=20
  =
list<BR>martini@ietf.org<BR>https://www.ietf.org/mailman/listinfo/martini=
<BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0C8C_01CABA09.7C16A010--


From adam@nostrum.com  Tue Mar  2 11:13:03 2010
Return-Path: <adam@nostrum.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 3CB463A8C6C for <martini@core3.amsl.com>; Tue,  2 Mar 2010 11:13:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001]
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 i+7c3uvH0JkK for <martini@core3.amsl.com>; Tue,  2 Mar 2010 11:13:00 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id DFB053A8C68 for <martini@ietf.org>; Tue,  2 Mar 2010 11:12:59 -0800 (PST)
Received: from hydra-3.local (ppp-70-249-147-216.dsl.rcsntx.swbell.net [70.249.147.216]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o22JCwEN028680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Mar 2010 13:12:58 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4B8D633A.7050301@nostrum.com>
Date: Tue, 02 Mar 2010 13:12:58 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com> <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net> <3F3263654C6C45E3A766175063D0538C@china.huawei.com> <4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com>
In-Reply-To: <4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com>
Content-Type: multipart/alternative; boundary="------------030109090609010702060301"
Received-SPF: pass (nostrum.com: 70.249.147.216 is authenticated by a trusted mechanism)
Cc: martini@ietf.org
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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, 02 Mar 2010 19:13:03 -0000

This is a multi-part message in MIME format.
--------------030109090609010702060301
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 3/2/10 11:56, Mar 2, Dean Willis wrote:
>
> On Mar 2, 2010, at 10:48 AM, Spencer Dawkins wrote:
>>
>> I understood Adam's note as saying that
>>
>> - the right answer is to use TCP (as a fallback, at minimum), so we 
>> don't need to specify a limit.
>>
>> - if people don't use TCP (at least as a fallback), a larger number 
>> of AoR (ranges) will probably still work just based on IP fragmentation.
>>
>> - if this doesn't work (because you punted TCP AND decided to enforce 
>> the UDP MTU limit), that's your problem to solve, and the suggested 
>> answer would be to either stop punting TCP or start using RFC 3263.
>>
>> I think Adam and I broadly agree here, and that no change to the 
>> document is required.
>>
>> Does anyone (especially Adam, because I think I'm agreeing with him 
>> :-) disagree?
>>
>
> I agree with this set of statements.
>
> However, I will warn us that the "transport police" will probably take 
> exception. Congestion-induced retransmission of 64k UDP packets is 
> pretty much a text-book example of what they think "harms the Internet".

We're not telling people to do this. There are MUST-strength normative 
statements that tell people *not* to do this, in fact.

But the brain-dead implementations that don't do TCP won't "just break" 
-- as was implied -- when UDP packets start exceeding the MTU. That was 
my point.

/a

--------------030109090609010702060301
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 3/2/10 11:56, Mar 2, Dean Willis wrote:
<blockquote
 cite="mid:4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com"
 type="cite"><br>
  <div>
  <div>On Mar 2, 2010, at 10:48 AM, Spencer Dawkins wrote:</div>
  <blockquote type="cite">
    <div><font class="Apple-style-span" color="#000000"><br>
    </font>I understood Adam's note as saying that<br>
    <br>
- the right answer is to use TCP (as a fallback, at minimum), so we
don't need to specify a limit.<br>
    <br>
- if people don't use TCP (at least as a fallback), a larger number of
AoR (ranges) will probably still work just based on IP fragmentation.<br>
    <br>
- if this doesn't work (because you punted TCP AND decided to enforce
the UDP MTU limit), that's your problem to solve, and the suggested
answer would be to either stop punting TCP or start using RFC 3263.<br>
    <br>
I think Adam and I broadly agree here, and that no change to the
document is required.<br>
    <br>
Does anyone (especially Adam, because I think I'm agreeing with him :-)
disagree?<br>
    <br>
    </div>
  </blockquote>
  </div>
  <br>
  <div>I agree with this set of statements.&nbsp;</div>
  <div><br>
  </div>
  <div>However, I will warn us that the "transport police" will
probably take exception. Congestion-induced retransmission of 64k UDP
packets is pretty much a text-book example of what they think "harms
the Internet".</div>
</blockquote>
<br>
We're not telling people to do this. There are MUST-strength normative
statements that tell people *not* to do this, in fact.<br>
<br>
But the brain-dead implementations that don't do TCP won't "just break"
-- as was implied -- when UDP packets start exceeding the MTU. That was
my point.<br>
<br>
/a<br>
</body>
</html>

--------------030109090609010702060301--

From john.elwell@siemens-enterprise.com  Tue Mar  2 11:56:49 2010
Return-Path: <john.elwell@siemens-enterprise.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 3CBEF28C164 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 11:56:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599]
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 TA7S2JijdBe0 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 11:56:48 -0800 (PST)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 1C1993A8C87 for <martini@ietf.org>; Tue,  2 Mar 2010 11:56:47 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1069687; Tue, 2 Mar 2010 20:56:48 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 06E921EB82C9; Tue,  2 Mar 2010 20:56:48 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.57]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Tue, 2 Mar 2010 20:56:48 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Adam Roach <adam@nostrum.com>, Dean Willis <dean.willis@softarmor.com>
Date: Tue, 2 Mar 2010 20:56:47 +0100
Thread-Topic: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
Thread-Index: Acq6PGHobq8imrGhT02B3n+n/3mgrwABbtog
Message-ID: <A444A0F8084434499206E78C106220CABBBA63CB@MCHP058A.global-ad.net>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com> <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net> <3F3263654C6C45E3A766175063D0538C@china.huawei.com> <4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com> <4B8D633A.7050301@nostrum.com>
In-Reply-To: <4B8D633A.7050301@nostrum.com>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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, 02 Mar 2010 19:56:49 -0000

So can we close Ticket#2 as "won't fix", i.e., no change to document, scala=
bility desirable remains (and is achievable)? I will do so if no objection =
today.

John=20

> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com]=20
> Sent: 02 March 2010 19:13
> To: Dean Willis
> Cc: Spencer Dawkins; Elwell, John; martini@ietf.org
> Subject: Re: [martini] #2: Scaling to Several Thousand=20
> Assigned Telephone Numbers
>=20
> On 3/2/10 11:56, Mar 2, Dean Willis wrote:=20
>=20
>=20
> 	On Mar 2, 2010, at 10:48 AM, Spencer Dawkins wrote:
>=20
> 	=09
> 		I understood Adam's note as saying that
> 	=09
> 		- the right answer is to use TCP (as a=20
> fallback, at minimum), so we don't need to specify a limit.
> 	=09
> 		- if people don't use TCP (at least as a=20
> fallback), a larger number of AoR (ranges) will probably=20
> still work just based on IP fragmentation.
> 	=09
> 		- if this doesn't work (because you punted TCP=20
> AND decided to enforce the UDP MTU limit), that's your=20
> problem to solve, and the suggested answer would be to either=20
> stop punting TCP or start using RFC 3263.
> 	=09
> 		I think Adam and I broadly agree here, and that=20
> no change to the document is required.
> 	=09
> 		Does anyone (especially Adam, because I think=20
> I'm agreeing with him :-) disagree?
> 	=09
> 	=09
>=20
>=20
> 	I agree with this set of statements.=20
>=20
> 	However, I will warn us that the "transport police"=20
> will probably take exception. Congestion-induced=20
> retransmission of 64k UDP packets is pretty much a text-book=20
> example of what they think "harms the Internet".
>=20
>=20
> We're not telling people to do this. There are MUST-strength=20
> normative statements that tell people *not* to do this, in fact.
>=20
> But the brain-dead implementations that don't do TCP won't=20
> "just break" -- as was implied -- when UDP packets start=20
> exceeding the MTU. That was my point.
>=20
> /a
>=20
> =

From spencer@wonderhamster.org  Tue Mar  2 12:02:34 2010
Return-Path: <spencer@wonderhamster.org>
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 1BB3028C230 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 12:02:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.931
X-Spam-Level: 
X-Spam-Status: No, score=-2.931 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 imqtC0CgLfQx for <martini@core3.amsl.com>; Tue,  2 Mar 2010 12:02:33 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 8224728C241 for <martini@ietf.org>; Tue,  2 Mar 2010 12:02:19 -0800 (PST)
Received: from S73602b (w147.z209031239.sjc-ca.dsl.cnc.net [209.31.239.147]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0M5Lyp-1NWOpE09Rn-00yjcn; Tue, 02 Mar 2010 15:02:20 -0500
Message-ID: <E03CBA9F2B5F4C9CA653BB81FF816A4D@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Adam Roach" <adam@nostrum.com>, "Dean Willis" <dean.willis@softarmor.com>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com> <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net> <3F3263654C6C45E3A766175063D0538C@china.huawei.com> <4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com> <4B8D633A.7050301@nostrum.com> <A444A0F8084434499206E78C106220CABBBA63CB@MCHP058A.global-ad.net>
Date: Tue, 2 Mar 2010 14:02:06 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX18chgFoPQNbSC7VpgY2pAC6m2tjNAzUXklb95e A+ROTk0qACB40sPhc76ekRt2JiBwAjI8rpUqL9EO/r/SgoZEYh uqV9Yyg85rbevoa7h4SjgaQPAlW+6Y+0ZJdexmtoII=
Cc: martini@ietf.org
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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, 02 Mar 2010 20:02:34 -0000

Hi, John,

Yes, I agree.

Spencer, as co-chair.

----- Original Message ----- 
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Adam Roach" <adam@nostrum.com>; "Dean Willis" 
<dean.willis@softarmor.com>
Cc: "Spencer Dawkins" <spencer@wonderhamster.org>; <martini@ietf.org>
Sent: Tuesday, March 02, 2010 1:56 PM
Subject: RE: [martini] #2: Scaling to Several Thousand Assigned Telephone 
Numbers


So can we close Ticket#2 as "won't fix", i.e., no change to document, 
scalability desirable remains (and is achievable)? I will do so if no 
objection today.

John

> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com]
> Sent: 02 March 2010 19:13
> To: Dean Willis
> Cc: Spencer Dawkins; Elwell, John; martini@ietf.org
> Subject: Re: [martini] #2: Scaling to Several Thousand
> Assigned Telephone Numbers
>
> On 3/2/10 11:56, Mar 2, Dean Willis wrote:
>
>
> On Mar 2, 2010, at 10:48 AM, Spencer Dawkins wrote:
>
>
> I understood Adam's note as saying that
>
> - the right answer is to use TCP (as a
> fallback, at minimum), so we don't need to specify a limit.
>
> - if people don't use TCP (at least as a
> fallback), a larger number of AoR (ranges) will probably
> still work just based on IP fragmentation.
>
> - if this doesn't work (because you punted TCP
> AND decided to enforce the UDP MTU limit), that's your
> problem to solve, and the suggested answer would be to either
> stop punting TCP or start using RFC 3263.
>
> I think Adam and I broadly agree here, and that
> no change to the document is required.
>
> Does anyone (especially Adam, because I think
> I'm agreeing with him :-) disagree?
>
>
>
>
> I agree with this set of statements.
>
> However, I will warn us that the "transport police"
> will probably take exception. Congestion-induced
> retransmission of 64k UDP packets is pretty much a text-book
> example of what they think "harms the Internet".
>
>
> We're not telling people to do this. There are MUST-strength
> normative statements that tell people *not* to do this, in fact.
>
> But the brain-dead implementations that don't do TCP won't
> "just break" -- as was implied -- when UDP packets start
> exceeding the MTU. That was my point.
>
> /a
>
> = 


From dean.willis@softarmor.com  Tue Mar  2 14:26:58 2010
Return-Path: <dean.willis@softarmor.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 BCFFF28C285 for <martini@core3.amsl.com>; Tue,  2 Mar 2010 14:26:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 x4B5utCseiMi for <martini@core3.amsl.com>; Tue,  2 Mar 2010 14:26:57 -0800 (PST)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id CDC8328C27F for <martini@ietf.org>; Tue,  2 Mar 2010 14:26:57 -0800 (PST)
Received: from [192.168.2.102] (cpe-66-25-30-183.tx.res.rr.com [66.25.30.183]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id o22MQnZ9027574 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 2 Mar 2010 16:26:58 -0600
Message-Id: <ED967586-4B47-49C9-A021-FB7C53F481A7@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Adam Roach <adam@nostrum.com>
In-Reply-To: <4B8D633A.7050301@nostrum.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 2 Mar 2010 16:26:44 -0600
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com> <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net> <3F3263654C6C45E3A766175063D0538C@china.huawei.com> <4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com> <4B8D633A.7050301@nostrum.com>
X-Mailer: Apple Mail (2.936)
Cc: martini@ietf.org
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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, 02 Mar 2010 22:26:58 -0000

On Mar 2, 2010, at 1:12 PM, Adam Roach wrote:

>
>>
>> However, I will warn us that the "transport police" will probably  
>> take exception. Congestion-induced retransmission of 64k UDP  
>> packets is pretty much a text-book example of what they think  
>> "harms the Internet".
>
> We're not telling people to do this. There are MUST-strength  
> normative statements that tell people *not* to do this, in fact.
>
> But the brain-dead implementations that don't do TCP won't "just  
> break" -- as was implied -- when UDP packets start exceeding the  
> MTU. That was my point.
>

Ok, I'm convinced.

--
Dean


From trac@tools.ietf.org  Wed Mar  3 00:14:08 2010
Return-Path: <trac@tools.ietf.org>
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 A95D528C2D8 for <martini@core3.amsl.com>; Wed,  3 Mar 2010 00:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, NORMAL_HTTP_TO_IP=0.001, USER_IN_WHITELIST=-100]
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 c1LDH7gol94l for <martini@core3.amsl.com>; Wed,  3 Mar 2010 00:14:04 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) by core3.amsl.com (Postfix) with ESMTP id 2ECB328C2CD for <martini@ietf.org>; Wed,  3 Mar 2010 00:14:02 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NmjiU-0004QM-Uq; Wed, 03 Mar 2010 00:14:02 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Wed, 03 Mar 2010 08:14:02 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://64.170.98.42/wg/martini/trac/ticket/2#comment:1
Message-ID: <076.de2b74cf1a55fdf7cdf84d24c414225f@tools.ietf.org>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org>
X-Trac-Ticket-ID: 2
In-Reply-To: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Wed, 03 Mar 2010 08:14:08 -0000

#2: Scaling to Several Thousand Assigned Telephone Numbers
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:  john.elwell@…                     
     Type:  defect                     |       Status:  closed                            
 Priority:  major                      |    Milestone:  milestone1                        
Component:  reqs                       |      Version:  1.0                               
 Severity:  In WG Last Call            |   Resolution:  wontfix                           
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by john.elwell@…):

  * status:  new => closed
  * resolution:  => wontfix


Comment:

 It is believed that solutions under consideration can achieve this
 scalability. In particular, any need to enumerate the registered AORs in a
 REGISTER request can scale by making use of number ranges or ensuring that
 TCP is used for messages exceeding the maximum MTU size. Therefore this
 "desirable" can remain.

-- 
Ticket URL: <http://64.170.98.42/wg/martini/trac/ticket/2#comment:1>
martini <http://tools.ietf.org/martini/>


From keith.drage@alcatel-lucent.com  Wed Mar  3 03:58:45 2010
Return-Path: <keith.drage@alcatel-lucent.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 BAB9328C340 for <martini@core3.amsl.com>; Wed,  3 Mar 2010 03:58:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.048
X-Spam-Level: 
X-Spam-Status: No, score=-2.048 tagged_above=-999 required=5 tests=[AWL=0.201,  BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
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 sZfoldNspTn7 for <martini@core3.amsl.com>; Wed,  3 Mar 2010 03:58:44 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 276A53A8D91 for <martini@ietf.org>; Wed,  3 Mar 2010 03:58:43 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o23Bw6Yv005744 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 3 Mar 2010 12:58:41 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Wed, 3 Mar 2010 12:58:23 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Spencer Dawkins <spencer@wonderhamster.org>, Dean Willis <dean.willis@softarmor.com>
Date: Wed, 3 Mar 2010 12:58:22 +0100
Thread-Topic: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
Thread-Index: Acq6M+wzfkHwTDjwSzCIpwU06BK8eQAlFz4Q
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE20C19DD2B@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com> <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net> <3F3263654C6C45E3A766175063D0538C@china.huawei.com> <4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com> <BFC410373E034190957204A7FEDEC217@china.huawei.com>
In-Reply-To: <BFC410373E034190957204A7FEDEC217@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_EDC0A1AE77C57744B664A310A0B23AE20C19DD2BFRMRSSXCHMBSC3d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone	Numbers
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: Wed, 03 Mar 2010 11:58:45 -0000

--_000_EDC0A1AE77C57744B664A310A0B23AE20C19DD2BFRMRSSXCHMBSC3d_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The situation that 18.1.1 does not cover is where the request conforms to t=
he rules specified in 18.1.1, and for some reason is less that the 1300 byt=
es, or whatever, and where the response grows beyond that. The response fol=
lows the transport mechanism of the request. We have not progressed at leas=
t one internet draft because of that problem.

So if someone wants a solution which for example puts a range of numbers in=
 a request, and enumerate all those numbers in the response, then the requi=
rements of 18.1.1 will not solve the issue.

regards

Keith



________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Spencer Dawkins
Sent: Tuesday, March 02, 2010 6:11 PM
To: Dean Willis
Cc: martini@ietf.org
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone N=
umbers

I'm sitting in a room with all three TSV ADs now, so I should be able to av=
oid blindsiding them at IETF Last Call time... but until then - my understa=
nding is that this text in RFC 3261 is overarching:


18.1.1 Sending Requests



   The client side of the transport layer is responsible for sending the
   request and receiving responses.  The user of the transport layer
   passes the client transport the request, an IP address, port,
   transport, and possibly TTL for multicast destinations.

   If a request is within 200 bytes of the path MTU, or if it is larger
   than 1300 bytes and the path MTU is unknown, the request MUST be sent
   using an RFC 2914<./rfc2914> [43<mhtml:mid://00003169/#ref-43>] congesti=
on controlled transport protocol, such
   as TCP. If this causes a change in the transport protocol from the
   one indicated in the top Via, the value in the top Via MUST be
   changed.  This prevents fragmentation of messages over UDP and
   provides congestion control for larger messages.  However,
   implementations MUST be able to handle messages up to the maximum
   datagram packet size.  For UDP, this size is 65,535 bytes, including
   IP and UDP headers.


If I'm right about that, any conformant implementation will work, and I'm n=
ot sure that saying "we really, really mean what RFC 3261 says" is going to=
 change anything that will affect non-conforming implementations.

So, speaking as an individual, I'd say "no change to our document required"=
. Bernard, want to call this one as chair?

Spencer
----- Original Message -----
From: Dean Willis<mailto:dean.willis@softarmor.com>
To: Spencer Dawkins<mailto:spencer@wonderhamster.org>
Cc: Elwell, John<mailto:john.elwell@siemens-enterprise.com> ; Adam Roach<ma=
ilto:adam@nostrum.com> ; martini@ietf.org<mailto:martini@ietf.org>
Sent: Tuesday, March 02, 2010 11:56 AM
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone N=
umbers


On Mar 2, 2010, at 10:48 AM, Spencer Dawkins wrote:

I understood Adam's note as saying that

- the right answer is to use TCP (as a fallback, at minimum), so we don't n=
eed to specify a limit.

- if people don't use TCP (at least as a fallback), a larger number of AoR =
(ranges) will probably still work just based on IP fragmentation.

- if this doesn't work (because you punted TCP AND decided to enforce the U=
DP MTU limit), that's your problem to solve, and the suggested answer would=
 be to either stop punting TCP or start using RFC 3263.

I think Adam and I broadly agree here, and that no change to the document i=
s required.

Does anyone (especially Adam, because I think I'm agreeing with him :-) dis=
agree?


I agree with this set of statements.

However, I will warn us that the "transport police" will probably take exce=
ption. Congestion-induced retransmission of 64k UDP packets is pretty much =
a text-book example of what they think "harms the Internet".

>From a standards perspective, it would arguably be better to say that large=
 registrations MUST be entirely processed over TCP, even though we know ful=
l well that nobody is going to bother, and that they're going to continue w=
ith fragmented UDP right until the world's ice caps melt from the global wa=
rming caused by the excess router-CPU needed to process all those retransmi=
tted fragments.

I feel dirty.

--
Dean

--_000_EDC0A1AE77C57744B664A310A0B23AE20C19DD2BFRMRSSXCHMBSC3d_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; webkit-line-break:=
 after-white-space"=20
bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D774315411-03032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>The situation that 18.1.1 does not cover is where =
the=20
request conforms to the rules specified in 18.1.1, and for some reason is l=
ess=20
that the 1300 bytes, or whatever, and where the response grows beyond that.=
 The=20
response follows the transport mechanism of the request. We have not progre=
ssed=20
at least one internet draft because of that problem.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D774315411-03032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D774315411-03032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>So if someone wants a solution which for example p=
uts a=20
range of numbers in a request, and enumerate all those numbers in the respo=
nse,=20
then the requirements of 18.1.1 will not solve the issue.</FONT></SPAN></DI=
V>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D774315411-03032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D774315411-03032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>regards</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D774315411-03032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D774315411-03032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Keith</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D774315411-03032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D774315411-03032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> martini-bounces@ietf.org=20
  [mailto:martini-bounces@ietf.org] <B>On Behalf Of </B>Spencer=20
  Dawkins<BR><B>Sent:</B> Tuesday, March 02, 2010 6:11 PM<BR><B>To:</B> Dea=
n=20
  Willis<BR><B>Cc:</B> martini@ietf.org<BR><B>Subject:</B> Re: [martini] #2=
:=20
  Scaling to Several Thousand Assigned Telephone Numbers<BR></FONT><BR></DI=
V>
  <DIV></DIV>
  <DIV><FONT size=3D2>I'm sitting in a room with all three TSV ADs now, so =
I=20
  should be able to avoid blindsiding them at IETF Last Call time... but un=
til=20
  then - m</FONT><FONT size=3D2>y understanding is that this text in RFC 32=
61 is=20
  overarching:</FONT></DIV>
  <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2><SPAN class=3DApple-style-span=20
  style=3D"WORD-SPACING: 0px; FONT: medium 'Times New Roman'; TEXT-TRANSFOR=
M: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-S=
PACING: normal; BORDER-COLLAPSE: separate; WIDOWS: 2; ORPHANS: 2; webkit-bo=
rder-horizontal-spacing: 0px; webkit-border-vertical-spacing: 0px; webkit-t=
ext-decorations-in-effect: none; webkit-text-size-adjust: auto; webkit-text=
-stroke-width: 0px"><SPAN=20
  class=3DApple-style-span style=3D"FONT-SIZE: 40px"><PRE class=3Dnewpage s=
tyle=3D"MARGIN-TOP: 0px; FONT-SIZE: 1em; MARGIN-BOTTOM: 0px; PAGE-BREAK-BEF=
ORE: always"><SPAN class=3Dh4 style=3D"DISPLAY: inline; FONT-WEIGHT: bold; =
FONT-SIZE: 1em; LINE-HEIGHT: 0pt; FONT-FAMILY: monospace; WHITE-SPACE: pre"=
><H4 style=3D"DISPLAY: inline; FONT-WEIGHT: bold; FONT-SIZE: 1em; LINE-HEIG=
HT: 0pt; FONT-FAMILY: monospace; WHITE-SPACE: pre"><A name=3Dsection-18.1.1=
><FONT size=3D3>18.1.1</FONT></A><FONT size=3D3> Sending Requests</FONT></H=
4></SPAN>
<FONT size=3D3></FONT></PRE><PRE class=3Dnewpage style=3D"MARGIN-TOP: 0px; =
FONT-SIZE: 1em; MARGIN-BOTTOM: 0px; PAGE-BREAK-BEFORE: always"><FONT size=
=3D3>   The client side of the transport layer is responsible for sending t=
he
   request and receiving responses.  The user of the transport layer
   passes the client transport the request, an IP address, port,
   transport, and possibly TTL for multicast destinations.

<FONT color=3D#0000ff>   If a request is within 200 bytes of the path MTU, =
or if it is larger
   than 1300 bytes and the path MTU is unknown, the request MUST be sent
   using an </FONT></FONT><A href=3D"./rfc2914"><FONT size=3D3>RFC 2914</FO=
NT></A><FONT color=3D#0000ff size=3D3> [</FONT><A title=3D'"Congestion Cont=
rol Principles"' href=3D"mhtml:mid://00003169/#ref-43"><FONT size=3D3>43</F=
ONT></A><FONT size=3D3><FONT color=3D#0000ff>] congestion controlled transp=
ort protocol, such
   as TCP.</FONT> If this causes a change in the transport protocol from th=
e
   one indicated in the top Via, the value in the top Via MUST be
   changed.  This prevents fragmentation of messages over UDP and
   provides congestion control for larger messages.  <FONT color=3D#0000ff>=
However,
   implementations MUST be able to handle messages up to the maximum
   datagram packet size.  For UDP, this size is 65,535 bytes, including
   IP and UDP headers.</FONT></FONT></PRE></SPAN></SPAN></FONT></DIV>
  <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2>If I'm right about that, any conformant implementatio=
n will=20
  work, and I'm not sure that saying "we really, really mean what RFC 3261 =
says"=20
  is going to change anything that will affect non-conforming=20
  implementations.</FONT></DIV>
  <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2>So, speaking as an individual, I'd say "no change to =
our=20
  document required". Bernard, want to call this one as chair?</FONT></DIV>
  <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2>Spencer</FONT></DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-=
LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV=20
    style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>F=
rom:</B>=20
    <A title=3Ddean.willis@softarmor.com=20
    href=3D"mailto:dean.willis@softarmor.com">Dean Willis</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Dspencer@wonderham=
ster.org=20
    href=3D"mailto:spencer@wonderhamster.org">Spencer Dawkins</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A=20
    title=3Djohn.elwell@siemens-enterprise.com=20
    href=3D"mailto:john.elwell@siemens-enterprise.com">Elwell, John</A> ; <=
A=20
    title=3Dadam@nostrum.com href=3D"mailto:adam@nostrum.com">Adam Roach</A=
> ; <A=20
    title=3Dmartini@ietf.org href=3D"mailto:martini@ietf.org">martini@ietf.=
org</A>=20
    </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, March 02, 2010 11=
:56=20
    AM</DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [martini] #2: Scali=
ng to=20
    Several Thousand Assigned Telephone Numbers</DIV>
    <DIV><BR></DIV><BR>
    <DIV>
    <DIV>On Mar 2, 2010, at 10:48 AM, Spencer Dawkins wrote:</DIV>
    <BLOCKQUOTE type=3D"cite">
      <DIV><FONT class=3DApple-style-span color=3D#000000><BR></FONT>I unde=
rstood=20
      Adam's note as saying that<BR><BR>- the right answer is to use TCP (a=
s a=20
      fallback, at minimum), so we don't need to specify a limit.<BR><BR>- =
if=20
      people don't use TCP (at least as a fallback), a larger number of AoR=
=20
      (ranges) will probably still work just based on IP fragmentation.<BR>=
<BR>-=20
      if this doesn't work (because you punted TCP AND decided to enforce t=
he=20
      UDP MTU limit), that's your problem to solve, and the suggested answe=
r=20
      would be to either stop punting TCP or start using RFC 3263.<BR><BR>I=
=20
      think Adam and I broadly agree here, and that no change to the docume=
nt is=20
      required.<BR><BR>Does anyone (especially Adam, because I think I'm=20
      agreeing with him :-) disagree?<BR><BR></DIV></BLOCKQUOTE></DIV><BR>
    <DIV>I agree with this set of statements.&nbsp;</DIV>
    <DIV><BR></DIV>
    <DIV>However, I will warn us that the "transport police" will probably =
take=20
    exception. Congestion-induced retransmission of 64k UDP packets is pret=
ty=20
    much a text-book example of what they think "harms the Internet".</DIV>
    <DIV><BR></DIV>
    <DIV>From a standards perspective, it would arguably be better to say t=
hat=20
    large registrations MUST be entirely processed over TCP, even though we=
 know=20
    full well that nobody is going to bother, and that they're going to con=
tinue=20
    with fragmented UDP right until the world's ice caps melt from the glob=
al=20
    warming caused by the excess router-CPU needed to process all those=20
    retransmitted fragments.</DIV>
    <DIV><BR></DIV>
    <DIV>I feel dirty.</DIV>
    <DIV><BR></DIV>
    <DIV>--</DIV>
    <DIV>Dean</DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--_000_EDC0A1AE77C57744B664A310A0B23AE20C19DD2BFRMRSSXCHMBSC3d_--

From bernard_aboba@hotmail.com  Wed Mar  3 08:04:16 2010
Return-Path: <bernard_aboba@hotmail.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 B6D633A8A92 for <martini@core3.amsl.com>; Wed,  3 Mar 2010 08:04:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.861
X-Spam-Level: 
X-Spam-Status: No, score=-1.861 tagged_above=-999 required=5 tests=[AWL=0.738,  BAYES_00=-2.599]
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 LCWJBTOxufdt for <martini@core3.amsl.com>; Wed,  3 Mar 2010 08:04:15 -0800 (PST)
Received: from blu0-omc2-s8.blu0.hotmail.com (blu0-omc2-s8.blu0.hotmail.com [65.55.111.83]) by core3.amsl.com (Postfix) with ESMTP id C305E3A8A8F for <martini@ietf.org>; Wed,  3 Mar 2010 08:04:15 -0800 (PST)
Received: from BLU137-DS1 ([65.55.111.71]) by blu0-omc2-s8.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 3 Mar 2010 08:04:17 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS13589682DA6CAEE35CF2D933A0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'MARTINI'" <martini@ietf.org>
Date: Wed, 3 Mar 2010 08:05:05 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acq650fmu0Ab3RaWRcOQVzGSApBxJAAA9gJQ
Content-Language: en-us
X-OriginalArrivalTime: 03 Mar 2010 16:04:17.0183 (UTC) FILETIME=[2D3242F0:01CABAEB]
Subject: [martini] Request for help in developing a tool that may be helpful to WG chairs (fwd)
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: Wed, 03 Mar 2010 16:04:16 -0000

-----Original Message-----
From: Scott O. Bradner
Sent: Wednesday, March 03, 2010 7:36 AM
To: wgchairs@ietf.org
Subject: Request for help in developing a tool that may be helpful to WG
chairs

IETF working group chairs;

We are developing an open-source tool for monitoring the status and
progress of conflicts in on-line working groups (WG).  The tool works by
analyzing the WG mailing list.  When developed, this tool should be
helpful to WG chairs trying to understand the status of WG discussions
(how close to consensus is the WG, what is the distribution of
participation, etc).

As part of the development process we have been using a prototype tool
to analyze IETF WG mailing list archives to determine the amount of
conflict and how effective this conflict is being (has been) resolved.
As the first step, we need to understand the relationship between the
conflicts in a working group and the structure of the communication
network in that group. While having conflicts is not necessarily a bad
thing for a working group effort, some conflicts can escalate into
disasters. We are interested in finding the communication patterns
related to the evolution of group conflicts. Results from this study
will provide the base for the development of the tool that helps working
group chairs to decide when to intervene with an internal conflict
before it becomes irreversibly negative as well as being a tool that may
help determine where there is consensus on a particular topic.

We would like your help in understanding the level of conflicts within
your working groups and how the conflicts affect productivity and group
members' perception on the working group. It will be greatly appreciated
if you could ask your WG members to anonymously fill a short survey at 

https://spreadsheets.google.com/viewform?hl=en&formkey=dExTbEU5QmRncnhFbjhQU
VR4bzBGMEE6MA

Thank you!

Best Regards, 

Bin Zhu, Mark Gaynor, Scott Bradner, and Jialun Qin



From dean.willis@softarmor.com  Wed Mar  3 11:13:30 2010
Return-Path: <dean.willis@softarmor.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 7232C28C255 for <martini@core3.amsl.com>; Wed,  3 Mar 2010 11:13:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 QQ20vuGYatt6 for <martini@core3.amsl.com>; Wed,  3 Mar 2010 11:13:29 -0800 (PST)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 17BEC28B797 for <martini@ietf.org>; Wed,  3 Mar 2010 11:13:29 -0800 (PST)
Received: from [192.168.2.106] (cpe-66-25-30-183.tx.res.rr.com [66.25.30.183]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id o23JDRb8004634 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 3 Mar 2010 13:13:29 -0600
Message-Id: <5156E67E-45E2-4D3F-A007-BDFA7A757E87@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE20C19DD2B@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-1--573890671
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 3 Mar 2010 13:13:21 -0600
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com> <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net> <3F3263654C6C45E3A766175063D0538C@china.huawei.com> <4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com> <BFC410373E034190957204A7FEDEC217@china.huawei.com> <EDC0A1AE77C57744B664A310A0B23AE20C19DD2B@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
X-Mailer: Apple Mail (2.936)
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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: Wed, 03 Mar 2010 19:13:30 -0000

--Apple-Mail-1--573890671
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit


On Mar 3, 2010, at 5:58 AM, DRAGE, Keith (Keith) wrote:

> The situation that 18.1.1 does not cover is where the request  
> conforms to the rules specified in 18.1.1, and for some reason is  
> less that the 1300 bytes, or whatever, and where the response grows  
> beyond that. The response follows the transport mechanism of the  
> request. We have not progressed at least one internet draft because  
> of that problem.
>
> So if someone wants a solution which for example puts a range of  
> numbers in a request, and enumerate all those numbers in the  
> response, then the requirements of 18.1.1 will not solve the issue.
>

This is unfortunately a real problem with REGISTER today, I can send a  
first REGISTER request with one contact and get back a response with  
one contact. Repeat with another REGISTER containing a new single  
contact, and the response has two contacts. Repeat a thousand more  
times, and while the requests stay the same size, the responses keep  
getting bigger -- and any 200 OK response with 1,000 contacts listed  
is going to be bigger than a single UDP packet on any common transport.

Have I mentioned lately that REGISTER is really not a great tool for  
systems with large numbers of routes? A scalable dynamic routing  
mechanism would be a much better solution for MARTINI. Doing it with  
REGISTER is just a temporary hack (arguably, a REASONABLE temporary  
hack) to get the PBX-world working until we build a real dynamic  
routing mechanism in SIP. This same lack of a dynamic routing  
mechanism is also showing up back in DISPATCH, with the proposal for  
using local private ENUM as the mechanism for informing nodes about  
routes (which I don't like much either). But at least it's a proposal  
for approaching the problem, and that's a good thing because it means  
somebody has seen another tip of the SIP "routing iceberg", and the  
more of it we can see, the better of a chance we have of navigating  
around the whole mass.

--
Dean
--Apple-Mail-1--573890671
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On Mar 3, 2010, =
at 5:58 AM, DRAGE, Keith (Keith) wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div bgcolor=3D"#ffffff" =
style=3D"word-wrap: break-word; "><div dir=3D"ltr" align=3D"left"><span =
class=3D"774315411-03032010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">The situation that 18.1.1 does not cover is where the request =
conforms to the rules specified in 18.1.1, and for some reason is less =
that the 1300 bytes, or whatever, and where the response grows beyond =
that. The response follows the transport mechanism of the request. We =
have not progressed at least one internet draft because of that =
problem.</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"774315411-03032010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"774315411-03032010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">So if someone wants a solution which for example puts a range =
of numbers in a request, and enumerate all those numbers in the =
response, then the requirements of 18.1.1 will not solve the =
issue.</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"774315411-03032010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div></div></span></blockquote></div><br><=
div>This is unfortunately a real problem with REGISTER today, I can send =
a first REGISTER request with one contact and get back a response with =
one contact. Repeat with another REGISTER containing a new single =
contact, and the response has two contacts. Repeat a thousand more =
times, and while the requests stay the same size, the responses keep =
getting bigger -- and any 200 OK response with 1,000 contacts listed is =
going to be bigger than a single UDP packet on any common =
transport.</div><div><br></div><div>Have I mentioned lately that =
REGISTER is really not a great tool for systems with large numbers of =
routes? A scalable dynamic routing mechanism would be a much better =
solution for MARTINI. Doing it with REGISTER is just a temporary hack =
(arguably, a REASONABLE temporary hack) to get the PBX-world working =
until we build a real dynamic routing mechanism in SIP. This same lack =
of a dynamic routing mechanism is also showing up back in DISPATCH, with =
the proposal for using local private ENUM as the mechanism for informing =
nodes about routes (which I don't like much either). But at least it's a =
proposal for approaching the problem, and that's a good thing because it =
means somebody has seen another tip of the SIP "routing iceberg", and =
the more of it we can see, the better of a chance we have of navigating =
around the whole =
mass.</div><div><br></div><div>--</div><div>Dean</div></body></html>=

--Apple-Mail-1--573890671--

From christer.holmberg@ericsson.com  Wed Mar  3 11:24:03 2010
Return-Path: <christer.holmberg@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 C89A23A8DFC for <martini@core3.amsl.com>; Wed,  3 Mar 2010 11:24:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 kpqMImA2Sbh1 for <martini@core3.amsl.com>; Wed,  3 Mar 2010 11:24:01 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id AE2063A8E04 for <martini@ietf.org>; Wed,  3 Mar 2010 11:23:55 -0800 (PST)
X-AuditID: c1b4fb3d-b7c72ae00000040e-ad-4b8eb749608d
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 1D.32.01038.947BE8B4; Wed,  3 Mar 2010 20:23:54 +0100 (CET)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.1.216]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Wed, 3 Mar 2010 20:23:53 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Dean Willis <dean.willis@softarmor.com>, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Date: Wed, 3 Mar 2010 20:22:40 +0100
Thread-Topic: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
Thread-Index: Acq7BZ9ya3tfxOowSxeC5Yi88dRk1AAAUUOi
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC745C10EE4159@ESESSCMS0354.eemea.ericsson.se>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com> <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net> <3F3263654C6C45E3A766175063D0538C@china.huawei.com> <4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com> <BFC410373E034190957204A7FEDEC217@china.huawei.com> <EDC0A1AE77C57744B664A310A0B23AE20C19DD2B@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>, <5156E67E-45E2-4D3F-A007-BDFA7A757E87@softarmor.com>
In-Reply-To: <5156E67E-45E2-4D3F-A007-BDFA7A757E87@softarmor.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone	Numbers
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: Wed, 03 Mar 2010 19:24:04 -0000

Hi,

This can be solved using wildcarded AOR, assuming the numbers are assigned =
in a way so they "fit" into a wildcard.

Regards,

Christer

________________________________
From: martini-bounces@ietf.org [martini-bounces@ietf.org] On Behalf Of Dean=
 Willis [dean.willis@softarmor.com]
Sent: Wednesday, March 03, 2010 9:13 PM
To: DRAGE, Keith (Keith)
Cc: martini@ietf.org
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone N=
umbers


On Mar 3, 2010, at 5:58 AM, DRAGE, Keith (Keith) wrote:

The situation that 18.1.1 does not cover is where the request conforms to t=
he rules specified in 18.1.1, and for some reason is less that the 1300 byt=
es, or whatever, and where the response grows beyond that. The response fol=
lows the transport mechanism of the request. We have not progressed at leas=
t one internet draft because of that problem.

So if someone wants a solution which for example puts a range of numbers in=
 a request, and enumerate all those numbers in the response, then the requi=
rements of 18.1.1 will not solve the issue.


This is unfortunately a real problem with REGISTER today, I can send a firs=
t REGISTER request with one contact and get back a response with one contac=
t. Repeat with another REGISTER containing a new single contact, and the re=
sponse has two contacts. Repeat a thousand more times, and while the reques=
ts stay the same size, the responses keep getting bigger -- and any 200 OK =
response with 1,000 contacts listed is going to be bigger than a single UDP=
 packet on any common transport.

Have I mentioned lately that REGISTER is really not a great tool for system=
s with large numbers of routes? A scalable dynamic routing mechanism would =
be a much better solution for MARTINI. Doing it with REGISTER is just a tem=
porary hack (arguably, a REASONABLE temporary hack) to get the PBX-world wo=
rking until we build a real dynamic routing mechanism in SIP. This same lac=
k of a dynamic routing mechanism is also showing up back in DISPATCH, with =
the proposal for using local private ENUM as the mechanism for informing no=
des about routes (which I don't like much either). But at least it's a prop=
osal for approaching the problem, and that's a good thing because it means =
somebody has seen another tip of the SIP "routing iceberg", and the more of=
 it we can see, the better of a chance we have of navigating around the who=
le mass.

--
Dean

From dean.willis@softarmor.com  Wed Mar  3 11:33:24 2010
Return-Path: <dean.willis@softarmor.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 D129728C139 for <martini@core3.amsl.com>; Wed,  3 Mar 2010 11:33:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 hFiFr1I2-Qa2 for <martini@core3.amsl.com>; Wed,  3 Mar 2010 11:33:23 -0800 (PST)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 89EB73A8E0C for <martini@ietf.org>; Wed,  3 Mar 2010 11:33:23 -0800 (PST)
Received: from [192.168.2.106] (cpe-66-25-30-183.tx.res.rr.com [66.25.30.183]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id o23JXIM5004799 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 3 Mar 2010 13:33:20 -0600
Message-Id: <7A944418-BFBD-4FBF-8898-7D0749DE2E69@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <FF84A09F50A6DC48ACB6714F4666CC745C10EE4159@ESESSCMS0354.eemea.ericsson.se>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 3 Mar 2010 13:33:13 -0600
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com> <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net> <3F3263654C6C45E3A766175063D0538C@china.huawei.com> <4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com> <BFC410373E034190957204A7FEDEC217@china.huawei.com> <EDC0A1AE77C57744B664A310A0B23AE20C19DD2B@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>, <5156E67E-45E2-4D3F-A007-BDFA7A757E87@softarmor.com> <FF84A09F50A6DC48ACB6714F4666CC745C10EE4159@ESESSCMS0354.eemea.ericsson.se>
X-Mailer: Apple Mail (2.936)
Cc: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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: Wed, 03 Mar 2010 19:33:25 -0000

On Mar 3, 2010, at 1:22 PM, Christer Holmberg wrote:

>
> Hi,
>
> This can be solved using wildcarded AOR, assuming the numbers are  
> assigned in a way so they "fit" into a wildcard.


It further requires a usage guideline that says:

Don't have a bazillion REGISTER messages with different numbers and  
ranges; register no more than you can fit into a single request.  
Otherwise, the REGISTER response may be larger than the REGISTER  
request, and this leads to unpredictable results.

--
Dean


From christer.holmberg@ericsson.com  Wed Mar  3 11:41:32 2010
Return-Path: <christer.holmberg@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 587EE28C445 for <martini@core3.amsl.com>; Wed,  3 Mar 2010 11:41:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 q0fCQD31U3HX for <martini@core3.amsl.com>; Wed,  3 Mar 2010 11:41:31 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 417CA28C131 for <martini@ietf.org>; Wed,  3 Mar 2010 11:41:31 -0800 (PST)
X-AuditID: c1b4fb39-b7c2dae000007b99-c9-4b8ebb6ba692
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 97.1A.31641.B6BBE8B4; Wed,  3 Mar 2010 20:41:31 +0100 (CET)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.1.216]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Wed, 3 Mar 2010 20:41:31 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Dean Willis <dean.willis@softarmor.com>
Date: Wed, 3 Mar 2010 20:39:24 +0100
Thread-Topic: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
Thread-Index: Acq7CHUx9TDnXLLIQ920QtC2XqYWdAAAMU7v
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC745C10EE415C@ESESSCMS0354.eemea.ericsson.se>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com> <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net> <3F3263654C6C45E3A766175063D0538C@china.huawei.com> <4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com> <BFC410373E034190957204A7FEDEC217@china.huawei.com> <EDC0A1AE77C57744B664A310A0B23AE20C19DD2B@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>, <5156E67E-45E2-4D3F-A007-BDFA7A757E87@softarmor.com> <FF84A09F50A6DC48ACB6714F4666CC745C10EE4159@ESESSCMS0354.eemea.ericsson.se>, <7A944418-BFBD-4FBF-8898-7D0749DE2E69@softarmor.com>
In-Reply-To: <7A944418-BFBD-4FBF-8898-7D0749DE2E69@softarmor.com>
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==
Cc: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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: Wed, 03 Mar 2010 19:41:32 -0000

Hi,

>> This can be solved using wildcarded AOR, assuming the numbers are
>> assigned in a way so they "fit" into a wildcard.
>
>
>It further requires a usage guideline that says:
>
>Don't have a bazillion REGISTER messages with different numbers and
>ranges; register no more than you can fit into a single request.
>Otherwise, the REGISTER response may be larger than the REGISTER
>request, and this leads to unpredictable results.

Yes. I think such text is much more useful than talking about exact numbers=
.

Maybe such text could start with: "Unless it can be ensured that TCP is use=
d all the way between the PBX and its registrar, blah blah blah..."

Regards,

Christer=

From spencer@wonderhamster.org  Wed Mar  3 12:59:25 2010
Return-Path: <spencer@wonderhamster.org>
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 5811828C1F1 for <martini@core3.amsl.com>; Wed,  3 Mar 2010 12:59:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 jOS+CJYo7u7z for <martini@core3.amsl.com>; Wed,  3 Mar 2010 12:59:24 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 020863A8795 for <martini@ietf.org>; Wed,  3 Mar 2010 12:59:24 -0800 (PST)
Received: from S73602b (cpe-76-182-230-135.tx.res.rr.com [76.182.230.135]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0Mar7C-1O1hee29sY-00KYyT; Wed, 03 Mar 2010 15:59:07 -0500
Message-ID: <21050529DB8E41A9B7FC6B18CDBA25D0@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>, "Dean Willis" <dean.willis@softarmor.com>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com><A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net><3F3263654C6C45E3A766175063D0538C@china.huawei.com><4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com><BFC410373E034190957204A7FEDEC217@china.huawei.com><EDC0A1AE77C57744B664A310A0B23AE20C19DD2B@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>, <5156E67E-45E2-4D3F-A007-BDFA7A757E87@softarmor.com><FF84A09F50A6DC48ACB6714F4666CC745C10EE4159@ESESSCMS0354.eemea.ericsson.se>, <7A944418-BFBD-4FBF-8898-7D0749DE2E69@softarmor.com> <FF84A09F50A6DC48ACB6714F4666CC745C10EE415C@ESESSCMS0354.eemea.ericsson.se>
Date: Wed, 3 Mar 2010 14:58:54 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1/rmtrp1ly+X89m0Lk1t/5OFxUEBk0IX1XAeht z/40/BiqfiCpRuXF9lO6PzshqVzYsUIjDI3RA8JxpLJOancXVn ycvllQAw3oVhSmSjae6IMQnkgf1VVCzlAHcnekFtag=
Cc: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, martini@ietf.org
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
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: Wed, 03 Mar 2010 20:59:25 -0000

Apparently great minds think alike :-)

I spoke with Lars and David Harrington yesterday (these will be the TSV ADs 
when MARTINI is balloted), and they said they would go for, roughly, what 
you guys said below.

Detailed report of the conversation at 
http://www.ietf.org/mail-archive/web/martini/current/msg00900.html.

Lars is expecting text along these lines to be in the protocol 
specification, saw no need for the requirements draft to address this, and 
saw no need for us to name an exact number - appropriate cautions (along the 
lines of "implementations that already violate the 'MUST use a 
congestion-controlled transport such as TCP when sending a request that is 
large enough to be IP-fragmented' in 3261 may have problems traversing NATs 
and losing fragmented IP packets when the network is congested; the solution 
is to use TCP as already required in 3261") seemed appropriate for him.

I asked John to close the issue for the requirements draft, and asked Adam 
if he needed a specific text proposal. So I think we're mostly done on this 
(important) point.

Thanks,

Spencer


> Hi,
>
>>> This can be solved using wildcarded AOR, assuming the numbers are
>>> assigned in a way so they "fit" into a wildcard.
>>
>>
>>It further requires a usage guideline that says:
>>
>>Don't have a bazillion REGISTER messages with different numbers and
>>ranges; register no more than you can fit into a single request.
>>Otherwise, the REGISTER response may be larger than the REGISTER
>>request, and this leads to unpredictable results.
>
> Yes. I think such text is much more useful than talking about exact 
> numbers.
>
> Maybe such text could start with: "Unless it can be ensured that TCP is 
> used all the way between the PBX and its registrar, blah blah blah..."
>
> Regards,
>
> Christer
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini 


From keith.drage@alcatel-lucent.com  Thu Mar  4 03:00:02 2010
Return-Path: <keith.drage@alcatel-lucent.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 D62CF3A888B for <martini@core3.amsl.com>; Thu,  4 Mar 2010 03:00:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.115
X-Spam-Level: 
X-Spam-Status: No, score=-2.115 tagged_above=-999 required=5 tests=[AWL=0.134,  BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 h7KFHWKfiheG for <martini@core3.amsl.com>; Thu,  4 Mar 2010 03:00:01 -0800 (PST)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id 81B473A879A for <martini@ietf.org>; Thu,  4 Mar 2010 02:59:58 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o24AxtOj009307 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 4 Mar 2010 11:59:56 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Thu, 4 Mar 2010 11:59:30 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Dean Willis <dean.willis@softarmor.com>
Date: Thu, 4 Mar 2010 11:59:28 +0100
Thread-Topic: [martini] #2: Scaling to Several Thousand Assigned Telephone Numbers
Thread-Index: Acq7BZ9ya3tfxOowSxeC5Yi88dRk1AAAUUOiACCTUTA=
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE20C19DFF5@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com> <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net> <3F3263654C6C45E3A766175063D0538C@china.huawei.com> <4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com> <BFC410373E034190957204A7FEDEC217@china.huawei.com> <EDC0A1AE77C57744B664A310A0B23AE20C19DD2B@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>, <5156E67E-45E2-4D3F-A007-BDFA7A757E87@softarmor.com> <FF84A09F50A6DC48ACB6714F4666CC745C10EE4159@ESESSCMS0354.eemea.ericsson.se>
In-Reply-To: <FF84A09F50A6DC48ACB6714F4666CC745C10EE4159@ESESSCMS0354.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.84
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned Telephone	Numbers
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: Thu, 04 Mar 2010 11:00:02 -0000

That is addressing a solution, not a requirement.

The point on the requirement issue is that it was being closed on the assum=
ption that conformance to RFC 3261 solves all the problems. It doesn't. You=
 need extra words to say that the solution must not encompass responses tha=
t are significantly larger than the requests, unless the solution always us=
es a reliable transport mechanism. That margin is the 300 or so bytes menti=
oned in RFC 3261 18.1.1.

This is a generic requirement for all SIP mechanisms, not just MARTINI.

regards

Keith

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]=20
> Sent: Wednesday, March 03, 2010 7:23 PM
> To: Dean Willis; DRAGE, Keith (Keith)
> Cc: martini@ietf.org
> Subject: RE: [martini] #2: Scaling to Several Thousand=20
> Assigned Telephone Numbers
>=20
>=20
> Hi,
>=20
> This can be solved using wildcarded AOR, assuming the numbers=20
> are assigned in a way so they "fit" into a wildcard.
>=20
> Regards,
>=20
> Christer
>=20
> ________________________________
> From: martini-bounces@ietf.org [martini-bounces@ietf.org] On=20
> Behalf Of Dean Willis [dean.willis@softarmor.com]
> Sent: Wednesday, March 03, 2010 9:13 PM
> To: DRAGE, Keith (Keith)
> Cc: martini@ietf.org
> Subject: Re: [martini] #2: Scaling to Several Thousand=20
> Assigned Telephone Numbers
>=20
>=20
> On Mar 3, 2010, at 5:58 AM, DRAGE, Keith (Keith) wrote:
>=20
> The situation that 18.1.1 does not cover is where the request=20
> conforms to the rules specified in 18.1.1, and for some=20
> reason is less that the 1300 bytes, or whatever, and where=20
> the response grows beyond that. The response follows the=20
> transport mechanism of the request. We have not progressed at=20
> least one internet draft because of that problem.
>=20
> So if someone wants a solution which for example puts a range=20
> of numbers in a request, and enumerate all those numbers in=20
> the response, then the requirements of 18.1.1 will not solve=20
> the issue.
>=20
>=20
> This is unfortunately a real problem with REGISTER today, I=20
> can send a first REGISTER request with one contact and get=20
> back a response with one contact. Repeat with another=20
> REGISTER containing a new single contact, and the response=20
> has two contacts. Repeat a thousand more times, and while the=20
> requests stay the same size, the responses keep getting=20
> bigger -- and any 200 OK response with 1,000 contacts listed=20
> is going to be bigger than a single UDP packet on any common=20
> transport.
>=20
> Have I mentioned lately that REGISTER is really not a great=20
> tool for systems with large numbers of routes? A scalable=20
> dynamic routing mechanism would be a much better solution for=20
> MARTINI. Doing it with REGISTER is just a temporary hack=20
> (arguably, a REASONABLE temporary hack) to get the PBX-world=20
> working until we build a real dynamic routing mechanism in=20
> SIP. This same lack of a dynamic routing mechanism is also=20
> showing up back in DISPATCH, with the proposal for using=20
> local private ENUM as the mechanism for informing nodes about=20
> routes (which I don't like much either). But at least it's a=20
> proposal for approaching the problem, and that's a good thing=20
> because it means somebody has seen another tip of the SIP=20
> "routing iceberg", and the more of it we can see, the better=20
> of a chance we have of navigating around the whole mass.
>=20
> --
> Dean
> =

From john.elwell@siemens-enterprise.com  Thu Mar  4 03:28:06 2010
Return-Path: <john.elwell@siemens-enterprise.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 45CD63A8148 for <martini@core3.amsl.com>; Thu,  4 Mar 2010 03:28:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
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 HI2z1TCXcT4o for <martini@core3.amsl.com>; Thu,  4 Mar 2010 03:28:05 -0800 (PST)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id BD63E3A70E2 for <martini@ietf.org>; Thu,  4 Mar 2010 03:28:04 -0800 (PST)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1093179; Thu, 4 Mar 2010 12:28:05 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id 8803723F028E; Thu,  4 Mar 2010 12:28:05 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.57]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Thu, 4 Mar 2010 12:28:05 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, Christer Holmberg <christer.holmberg@ericsson.com>, Dean Willis <dean.willis@softarmor.com>
Date: Thu, 4 Mar 2010 12:28:04 +0100
Thread-Topic: [martini] #2: Scaling to Several Thousand Assigned	Telephone Numbers
Thread-Index: Acq7BZ9ya3tfxOowSxeC5Yi88dRk1AAAUUOiACCTUTAAAREy0A==
Message-ID: <A444A0F8084434499206E78C106220CABBC012F9@MCHP058A.global-ad.net>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com> <A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net> <3F3263654C6C45E3A766175063D0538C@china.huawei.com> <4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com> <BFC410373E034190957204A7FEDEC217@china.huawei.com> <EDC0A1AE77C57744B664A310A0B23AE20C19DD2B@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>, <5156E67E-45E2-4D3F-A007-BDFA7A757E87@softarmor.com> <FF84A09F50A6DC48ACB6714F4666CC745C10EE4159@ESESSCMS0354.eemea.ericsson.se> <EDC0A1AE77C57744B664A310A0B23AE20C19DFF5@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE20C19DFF5@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #2: Scaling to Several Thousand Assigned	Telephone	Numbers
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: Thu, 04 Mar 2010 11:28:06 -0000

The existing requirement on scalability is sufficient. Measures needed to e=
nsure that the requirement can be met should be addressed as part of the so=
lution.

John=20

> -----Original Message-----
> From: martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] On Behalf Of DRAGE, Keith (Keith)
> Sent: 04 March 2010 10:59
> To: Christer Holmberg; Dean Willis
> Cc: martini@ietf.org
> Subject: Re: [martini] #2: Scaling to Several Thousand=20
> Assigned Telephone Numbers
>=20
> That is addressing a solution, not a requirement.
>=20
> The point on the requirement issue is that it was being=20
> closed on the assumption that conformance to RFC 3261 solves=20
> all the problems. It doesn't. You need extra words to say=20
> that the solution must not encompass responses that are=20
> significantly larger than the requests, unless the solution=20
> always uses a reliable transport mechanism. That margin is=20
> the 300 or so bytes mentioned in RFC 3261 18.1.1.
>=20
> This is a generic requirement for all SIP mechanisms, not=20
> just MARTINI.
>=20
> regards
>=20
> Keith
>=20
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]=20
> > Sent: Wednesday, March 03, 2010 7:23 PM
> > To: Dean Willis; DRAGE, Keith (Keith)
> > Cc: martini@ietf.org
> > Subject: RE: [martini] #2: Scaling to Several Thousand=20
> > Assigned Telephone Numbers
> >=20
> >=20
> > Hi,
> >=20
> > This can be solved using wildcarded AOR, assuming the numbers=20
> > are assigned in a way so they "fit" into a wildcard.
> >=20
> > Regards,
> >=20
> > Christer
> >=20
> > ________________________________
> > From: martini-bounces@ietf.org [martini-bounces@ietf.org] On=20
> > Behalf Of Dean Willis [dean.willis@softarmor.com]
> > Sent: Wednesday, March 03, 2010 9:13 PM
> > To: DRAGE, Keith (Keith)
> > Cc: martini@ietf.org
> > Subject: Re: [martini] #2: Scaling to Several Thousand=20
> > Assigned Telephone Numbers
> >=20
> >=20
> > On Mar 3, 2010, at 5:58 AM, DRAGE, Keith (Keith) wrote:
> >=20
> > The situation that 18.1.1 does not cover is where the request=20
> > conforms to the rules specified in 18.1.1, and for some=20
> > reason is less that the 1300 bytes, or whatever, and where=20
> > the response grows beyond that. The response follows the=20
> > transport mechanism of the request. We have not progressed at=20
> > least one internet draft because of that problem.
> >=20
> > So if someone wants a solution which for example puts a range=20
> > of numbers in a request, and enumerate all those numbers in=20
> > the response, then the requirements of 18.1.1 will not solve=20
> > the issue.
> >=20
> >=20
> > This is unfortunately a real problem with REGISTER today, I=20
> > can send a first REGISTER request with one contact and get=20
> > back a response with one contact. Repeat with another=20
> > REGISTER containing a new single contact, and the response=20
> > has two contacts. Repeat a thousand more times, and while the=20
> > requests stay the same size, the responses keep getting=20
> > bigger -- and any 200 OK response with 1,000 contacts listed=20
> > is going to be bigger than a single UDP packet on any common=20
> > transport.
> >=20
> > Have I mentioned lately that REGISTER is really not a great=20
> > tool for systems with large numbers of routes? A scalable=20
> > dynamic routing mechanism would be a much better solution for=20
> > MARTINI. Doing it with REGISTER is just a temporary hack=20
> > (arguably, a REASONABLE temporary hack) to get the PBX-world=20
> > working until we build a real dynamic routing mechanism in=20
> > SIP. This same lack of a dynamic routing mechanism is also=20
> > showing up back in DISPATCH, with the proposal for using=20
> > local private ENUM as the mechanism for informing nodes about=20
> > routes (which I don't like much either). But at least it's a=20
> > proposal for approaching the problem, and that's a good thing=20
> > because it means somebody has seen another tip of the SIP=20
> > "routing iceberg", and the more of it we can see, the better=20
> > of a chance we have of navigating around the whole mass.
> >=20
> > --
> > Dean
> >=20
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
> =

From spencer@wonderhamster.org  Thu Mar  4 06:31:40 2010
Return-Path: <spencer@wonderhamster.org>
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 9F77228C13D for <martini@core3.amsl.com>; Thu,  4 Mar 2010 06:31:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 2vXRYTD2SdRo for <martini@core3.amsl.com>; Thu,  4 Mar 2010 06:31:39 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 5131628C13C for <martini@ietf.org>; Thu,  4 Mar 2010 06:31:39 -0800 (PST)
Received: from S73602b (pool-71-96-150-125.dfw.dsl-w.verizon.net [71.96.150.125]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0Lmrky-1NEyqn0LcK-00gvSh; Thu, 04 Mar 2010 09:30:54 -0500
Message-ID: <57F1A67A888747F88B5A59333F6D68EE@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, "Christer Holmberg" <christer.holmberg@ericsson.com>, "Dean Willis" <dean.willis@softarmor.com>
References: <067.e23bbafa45eb4b09f274936404f0f091@tools.ietf.org><A444A0F8084434499206E78C106220CAB93E0FAC@MCHP058A.global-ad.net><877ACFA2914F4A5B9336B80718E233D0@china.huawei.com><A444A0F8084434499206E78C106220CAB93E1502@MCHP058A.global-ad.net><4B8C55F0.9050205@nostrum.com><A444A0F8084434499206E78C106220CABBBA5F3F@MCHP058A.global-ad.net><3F3263654C6C45E3A766175063D0538C@china.huawei.com><4F3FC4F7-1088-4B7C-BC2A-85617704AA25@softarmor.com><BFC410373E034190957204A7FEDEC217@china.huawei.com><EDC0A1AE77C57744B664A310A0B23AE20C19DD2B@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>, <5156E67E-45E2-4D3F-A007-BDFA7A757E87@softarmor.com><FF84A09F50A6DC48ACB6714F4666CC745C10EE4159@ESESSCMS0354.eemea.ericsson.se><EDC0A1AE77C57744B664A310A0B23AE20C19DFF5@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <A444A0F8084434499206E78C106220CABBC012F9@MCHP058A.global-ad.net>
Date: Thu, 4 Mar 2010 08:30:27 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1+tpvnRjNCBZz0iJvnkeLRqsJAghbYSwzYIOid HecNfACMfA+ARwWseZy5oXje7oEMK2FuRnDrTksK4t4QW7TVXe DKnr/YZrG7Vc9aBwPtmyeVTpqmSE4M8qh8gMyf7JbY=
Cc: martini@ietf.org
Subject: Re: [martini] #2: Scaling to Several ThousandAssigned	Telephone	Numbers
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: Thu, 04 Mar 2010 14:31:40 -0000

Keith,

I'm agreeing with John here, but I am hearing what you're saying. Please 
don't think I'm blowing you off; I took your concerns seriously enough to 
chase down the TSV guys immediately when I saw your note.

Speaking as co-chair, my concern is that, as pointed out a few times in this 
thread, the concern is a generic RFC 3261 concern, and I'd prefer not to 
spend MARTINI time on this - it's much like the MEDIACTRL discussion of SIP 
INFO, that needed to move to SIP because that's where the responsibility is, 
and anything we said needed to go through SIP anyway.

I think we're in the same situation now - only the working group name has 
been changed to SIPCORE (to protect the innocent?). We're saying "gotta be 
scalable" in MARTINI, but this specific concern, that could affect 
scalability, is a generic SIPCORE concern.

Bernard - if I'm off-base here, please say so. That's why we have co-chairs.

Cullen - if I'm off-base here, please say so. That's why we have ADs.

Thanks,

Spencer


> The existing requirement on scalability is sufficient. Measures needed to 
> ensure that the requirement can be met should be addressed as part of the 
> solution.
>
> John
>
>> -----Original Message-----
>> From: martini-bounces@ietf.org
>> [mailto:martini-bounces@ietf.org] On Behalf Of DRAGE, Keith (Keith)
>> Sent: 04 March 2010 10:59
>> To: Christer Holmberg; Dean Willis
>> Cc: martini@ietf.org
>> Subject: Re: [martini] #2: Scaling to Several Thousand
>> Assigned Telephone Numbers
>>
>> That is addressing a solution, not a requirement.
>>
>> The point on the requirement issue is that it was being
>> closed on the assumption that conformance to RFC 3261 solves
>> all the problems. It doesn't. You need extra words to say
>> that the solution must not encompass responses that are
>> significantly larger than the requests, unless the solution
>> always uses a reliable transport mechanism. That margin is
>> the 300 or so bytes mentioned in RFC 3261 18.1.1.
>>
>> This is a generic requirement for all SIP mechanisms, not
>> just MARTINI.
>>
>> regards
>>
>> Keith
>>
>> > -----Original Message-----
>> > From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
>> > Sent: Wednesday, March 03, 2010 7:23 PM
>> > To: Dean Willis; DRAGE, Keith (Keith)
>> > Cc: martini@ietf.org
>> > Subject: RE: [martini] #2: Scaling to Several Thousand
>> > Assigned Telephone Numbers
>> >
>> >
>> > Hi,
>> >
>> > This can be solved using wildcarded AOR, assuming the numbers
>> > are assigned in a way so they "fit" into a wildcard.
>> >
>> > Regards,
>> >
>> > Christer
>> >
>> > ________________________________
>> > From: martini-bounces@ietf.org [martini-bounces@ietf.org] On
>> > Behalf Of Dean Willis [dean.willis@softarmor.com]
>> > Sent: Wednesday, March 03, 2010 9:13 PM
>> > To: DRAGE, Keith (Keith)
>> > Cc: martini@ietf.org
>> > Subject: Re: [martini] #2: Scaling to Several Thousand
>> > Assigned Telephone Numbers
>> >
>> >
>> > On Mar 3, 2010, at 5:58 AM, DRAGE, Keith (Keith) wrote:
>> >
>> > The situation that 18.1.1 does not cover is where the request
>> > conforms to the rules specified in 18.1.1, and for some
>> > reason is less that the 1300 bytes, or whatever, and where
>> > the response grows beyond that. The response follows the
>> > transport mechanism of the request. We have not progressed at
>> > least one internet draft because of that problem.
>> >
>> > So if someone wants a solution which for example puts a range
>> > of numbers in a request, and enumerate all those numbers in
>> > the response, then the requirements of 18.1.1 will not solve
>> > the issue.
>> >
>> >
>> > This is unfortunately a real problem with REGISTER today, I
>> > can send a first REGISTER request with one contact and get
>> > back a response with one contact. Repeat with another
>> > REGISTER containing a new single contact, and the response
>> > has two contacts. Repeat a thousand more times, and while the
>> > requests stay the same size, the responses keep getting
>> > bigger -- and any 200 OK response with 1,000 contacts listed
>> > is going to be bigger than a single UDP packet on any common
>> > transport.
>> >
>> > Have I mentioned lately that REGISTER is really not a great
>> > tool for systems with large numbers of routes? A scalable
>> > dynamic routing mechanism would be a much better solution for
>> > MARTINI. Doing it with REGISTER is just a temporary hack
>> > (arguably, a REASONABLE temporary hack) to get the PBX-world
>> > working until we build a real dynamic routing mechanism in
>> > SIP. This same lack of a dynamic routing mechanism is also
>> > showing up back in DISPATCH, with the proposal for using
>> > local private ENUM as the mechanism for informing nodes about
>> > routes (which I don't like much either). But at least it's a
>> > proposal for approaching the problem, and that's a good thing
>> > because it means somebody has seen another tip of the SIP
>> > "routing iceberg", and the more of it we can see, the better
>> > of a chance we have of navigating around the whole mass.
>> >
>> > --
>> > Dean
>> >
>> _______________________________________________
>> martini mailing list
>> martini@ietf.org
>> https://www.ietf.org/mailman/listinfo/martini
>>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini 


From bernard_aboba@hotmail.com  Thu Mar  4 14:02:30 2010
Return-Path: <bernard_aboba@hotmail.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 4143C28C0E8 for <martini@core3.amsl.com>; Thu,  4 Mar 2010 14:02:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[AWL=0.709,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 qUrJsfKYRPQJ for <martini@core3.amsl.com>; Thu,  4 Mar 2010 14:02:22 -0800 (PST)
Received: from blu0-omc2-s18.blu0.hotmail.com (blu0-omc2-s18.blu0.hotmail.com [65.55.111.93]) by core3.amsl.com (Postfix) with ESMTP id A522028C0E1 for <martini@ietf.org>; Thu,  4 Mar 2010 14:02:22 -0800 (PST)
Received: from BLU137-DS10 ([65.55.111.72]) by blu0-omc2-s18.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 4 Mar 2010 14:02:24 -0800
X-Originating-IP: [131.107.0.104]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'MARTINI'" <martini@ietf.org>
Date: Thu, 4 Mar 2010 14:02:20 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0086_01CABBA3.4F0BFED0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acq75lzynCu/RB4MSc6T2IL3e5RvlA==
Content-Language: en-us
X-OriginalArrivalTime: 04 Mar 2010 22:02:24.0660 (UTC) FILETIME=[5F24CD40:01CABBE6]
Subject: [martini] Call for Adoption of "Registration for Multiple Phone Numbers in the SIP"
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: Thu, 04 Mar 2010 22:02:30 -0000

------=_NextPart_000_0086_01CABBA3.4F0BFED0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

This is a MARTINI WG Call for Adoption of "Registration for Multiple Phone
Numbers in the SIP" as a MARTINI WG work item, corresponding to the
"Multiple AoR Registration specification" Charter deliverable.  The document
is available for inspection here: 

http://tools.ietf.org/html/draft-roach-martini-gin-01.txt

The MARTINI WG Call for Adoption will last until Friday, March 19, 2010.

Please respond to this WG Call for Adoption, whether you are in favor of
adopting the document as a MARTINI WG work item or not.  If you have no
comments, please reply to this message and indicate in the body of your
message whether you think the document is ready for adoption as a MARTINI WG
work item or not.   Based on the response, the MARTINI WG chairs will
attempt to determine whether WG consensus exists to adopt the document or
not. 

If you have comments, please provide them to the WG in one of the following
ways: 

1.      The preferred choice is to open an issue in the MARTINI Issue
tracking database (TRAC), which is available here:
<http://trac.tools.ietf.org/wg/martini/trac/newticket>
http://trac.tools.ietf.org/wg/martini/trac/newticket  Information on how to
use TRAC is provided below.  Note that if you submit an issue in TRAC, it
will automatically also be posted to the MARTINI WG mailing list.  When
submitting issues in TRAC for this "call for adoption", please enter "gin"
for the Component: and "Candidate WG Document" for Severity.  

 2. If you can't figure out how to use TRAC, please post your Issue to the
MARTINI WG mailing list (martini at ietf.org) in the following format: 

To:  martini at ietf.org

Subject: GIN-Issue: <title of your issue>

Priority: blocker, critical, major, minor or trivial

<Explanation of your issue, including a proposal for specific text changes
to resolve the issue>

The MARTINI WG uses the TRAC database to keep track of issues relating to
work in progress, including working group work items and individual
submissions undergoing review.    This document provides some basic
information on how MARTINI WG participants can use TRAC to submit or edit
issues.  

Documentation relating to the TRAC Issue Tracking database is available
here:

http://trac.tools.ietf.org/wg/martini/trac/wiki

Since this documentation is somewhat lengthy (and mostly relevant to
Admins), here is a pithy synopsis. 

1.       To submit an issue in the MARTINI Issues database (known as TRAC),
you first need to login to the MARTINI WG site on the tools server
(http://tools.ietf.org/wg/martini/trac/login ) 

2.       If you don't already have a login ID, you can obtain one by
navigating to this site:   http://trac.tools.ietf.org/newlogin

3.       Once you have obtained an account, you can log in by clicking on
the "login" entry at the top of the page.  Once you have logged in, you can
file an issue by navigating to the  ticket entry form:
<http://trac.tools.ietf.org/wg/martini/trac/newticket>
http://trac.tools.ietf.org/wg/martini/trac/newticket

4     When opening an issue: 

a.       The Type: field should be set to "defect" for an issue with the
current document text, or "enhancement" for a proposed addition of
functionality (such as an additional requirement). 

b.      The Priority: field is set based on the severity of the Issue.   For
example, editorial issues are typically "minor" or "trivial". 

c.       The Milestone: field should be set to milestone1 (useless, I know).


d.      The Component: field should be set to the document you are filing
the issue on.  In responding to the GIN Call for Adoption, "gin" is the
appropriate choice.

e.      The Version: field should be set to "1.0". 

f.        The Severity: field should be set to based on the status of the
document (e.g. "Candidate WG Document" in this case)

g.        The Keywords: and CC: fields can be left blank unless inspiration
seizes you. 

h.      The Assign To: field is generally filled in with the email address
of the editor. 

5.       Typically it won't be necessary to enclose a file with the ticket,
but if you need to, select "I have files to attach to this ticket". 

6.       If you want to preview your Issue, click on the "Preview" button.
When you're ready to submit the issue, click on the "Create Ticket" button. 

That's it!  

If you have an problems in dealing with TRAC, send email to me and I'll try
to figure out what's going on. 

Happy TRACing,

Bernard

 


------=_NextPart_000_0086_01CABBA3.4F0BFED0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>This
is a MARTINI WG Call for Adoption of &#8220;Registration for Multiple =
Phone
Numbers in the SIP&#8221; as a MARTINI WG work item, corresponding to =
the &#8220;Multiple
AoR Registration specification&#8221; Charter deliverable. &nbsp;The =
document
is available for inspection here: <o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
href=3D"http://tools.ietf.org/html/draft-roach-martini-gin-01.txt">http:/=
/tools.ietf.org/html/draft-roach-martini-gin-01.txt</a><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The
MARTINI WG Call for Adoption will last until Friday, March 19, =
2010.<o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Please
respond to this WG Call for Adoption, whether you are in favor of =
adopting the
document as a MARTINI WG work item or not. &nbsp;If you have no =
comments,
please reply to this message and indicate in the body of your message =
whether
you think the document is ready for adoption as a MARTINI WG work item =
or not. &nbsp;&nbsp;Based
on the response, the MARTINI WG chairs will attempt to determine whether =
WG
consensus exists to adopt the document or not. <o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>If
you have comments, please provide them to the WG in one of the following =
ways: <o:p></o:p></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:21.0pt;text-indent:-.25in'><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The preferred choice is to open an issue in the MARTINI Issue tracking =
database
(TRAC), which is available here: <a
href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><span
style=3D'color:black'>http://trac.tools.ietf.org/wg/martini/trac/newticke=
t</span></a>
&nbsp;Information on how to use TRAC is provided below.&nbsp; Note that =
if you
submit an issue in TRAC, it will automatically also be posted to the =
MARTINI WG
mailing list. &nbsp;When submitting issues in TRAC for this &#8220;call =
for
adoption&#8221;, please enter &#8220;gin&#8221; for the Component: and
&#8220;Candidate WG Document&#8221; for Severity.&nbsp; =
<o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'color:black'>&nbsp;2. If you can&#8217;t figure out how to use =
TRAC,
please post your Issue to the MARTINI WG mailing list (martini at =
ietf.org) in
the following format: <o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'font-family:"Courier New"'>To:&nbsp; martini at =
ietf.org</span><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'font-family:"Courier New"'>Subject: GIN-Issue: &lt;title of =
your
issue&gt;</span><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'font-family:"Courier New"'>Priority: blocker, critical, major, =
minor or
trivial</span><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'font-family:"Courier New"'>&lt;Explanation of your issue, =
including a
proposal for specific text changes to resolve the =
issue&gt;</span><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'color:black'>The MARTINI WG uses the TRAC database to keep =
track of
issues relating to work in progress, including working group work items =
and
individual submissions undergoing review. &nbsp;&nbsp;&nbsp;This =
document
provides some basic information on how MARTINI WG participants can use =
TRAC to
submit or edit issues.&nbsp; </span><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Documentatio=
n
relating to the TRAC Issue Tracking database is available =
here:<o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
href=3D"http://trac.tools.ietf.org/wg/martini/trac/wiki">http://trac.tool=
s.ietf.org/wg/martini/trac/wiki</a><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Since
this documentation is somewhat lengthy (and mostly relevant to Admins), =
here is
a pithy synopsis. <o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>1.&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
To submit an issue in the MARTINI Issues database (known as TRAC), you =
first
need to login to the MARTINI WG site on the tools server (<a
href=3D"http://tools.ietf.org/wg/martini/trac/login">http://tools.ietf.or=
g/wg/martini/trac/login</a>
) <o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>2.&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
If you don&#8217;t already have a login ID, you can obtain one by =
navigating to
this site: &nbsp;&nbsp;<a =
href=3D"http://trac.tools.ietf.org/newlogin">http://trac.tools.ietf.org/n=
ewlogin</a><o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>3<span =
style=3D'color:black'>.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Once you have obtained an account, you can log in by clicking on the
&#8220;login&#8221; entry at the top of the page.&nbsp; Once you have =
logged
in, you can file an issue by navigating to the &nbsp;ticket entry form: =
<a
href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><span
style=3D'color:black'>http://trac.tools.ietf.org/wg/martini/trac/newticke=
t</span></a><o:p></o:p></span></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>4<span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;
</span>&nbsp;When opening an issue:&nbsp;<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>a.&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
The Type: field should be set to &#8220;defect&#8221; for an issue with =
the
current document text, or &#8220;enhancement&#8221; for a proposed =
addition of
functionality (such as an additional requirement). =
<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>b.&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; The
Priority: field is set based on the severity of the Issue.&nbsp;&nbsp; =
For
example, editorial issues are typically &#8220;minor&#8221; or
&#8220;trivial&#8221;. <o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>c<span =
style=3D'color:black'>.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The Milestone: field should be set to milestone1 (useless, I know). =
<o:p></o:p></span></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif";color:black'>d.&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
The Component: field should be set to the document you are filing the =
issue on.&nbsp;
In responding to the GIN Call for Adoption, &#8220;gin&#8221; is the
appropriate choice.<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif";color:black'>e.&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
The Version: field should be set to &#8220;1.0&#8221;. =
<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif";color:black'>f.&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;
The Severity: field should be set to based on the status of the document =
(e.g.
&#8220;Candidate WG Document&#8221; in this case)<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif";color:black'>g.&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
&nbsp;The Keywords: and CC: fields can be left blank unless inspiration =
seizes
you. <o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif";color:black'>h.&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
The Assign To: field is generally filled in with the email address of =
the editor.
<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>5.&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
Typically it won&#8217;t be necessary to enclose a file with the ticket, =
but if
you need to, select &#8220;I have files to attach to this ticket&#8221;. =
<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>6.&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
If you want to preview your Issue, click on the &#8220;Preview&#8221;
button.&nbsp; When you&#8217;re ready to submit the issue, click on the
&#8220;Create Ticket&#8221; button. <o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>That&#8217;s=

it!&nbsp; <span style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>If
you have an problems in dealing with TRAC, send email to me and =
I&#8217;ll try
to figure out what&#8217;s going on. <span =
style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Happy
TRACing,<span style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal>Bernard<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0086_01CABBA3.4F0BFED0--

From bernard_aboba@hotmail.com  Thu Mar  4 14:37:22 2010
Return-Path: <bernard_aboba@hotmail.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 016263A743D for <martini@core3.amsl.com>; Thu,  4 Mar 2010 14:37:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[AWL=0.665,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 ekR+RKS0oAcv for <martini@core3.amsl.com>; Thu,  4 Mar 2010 14:37:18 -0800 (PST)
Received: from blu0-omc2-s22.blu0.hotmail.com (blu0-omc2-s22.blu0.hotmail.com [65.55.111.97]) by core3.amsl.com (Postfix) with ESMTP id 5AB5828C13C for <martini@ietf.org>; Thu,  4 Mar 2010 14:37:18 -0800 (PST)
Received: from BLU137-DS17 ([65.55.111.71]) by blu0-omc2-s22.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 4 Mar 2010 14:37:20 -0800
X-Originating-IP: [131.107.0.104]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS178E0CB85E57CDC877D7AD93390@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'MARTINI'" <martini@ietf.org>
Date: Thu, 4 Mar 2010 14:37:16 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A9_01CABBA8.300A4640"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acq76z3zccNfIv1mQ0mEgm4UBsJpVA==
Content-Language: en-us
X-OriginalArrivalTime: 04 Mar 2010 22:37:20.0219 (UTC) FILETIME=[4031BAB0:01CABBEB]
Subject: [martini] IETF 77  Agenda - Take One
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: Thu, 04 Mar 2010 22:37:22 -0000

------=_NextPart_000_00A9_01CABBA8.300A4640
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

MARTINI WG Meeting Slot I

Monday, March 22, 2010

1 PM - 3 PM Pacific Time

Palos Verdes Room

 

Jabber room:  martini at jabber.ietf.org (Please join)

Question:  Do we have any remote presenters who need WebEx?

 

Agenda

 

1 PM - 1:10 PM:  Preliminaries

     Blue Sheets

     Note Takers

     Note Well

     Agenda bash

 

Requirements (20 minutes)

 

1:10 PM - 1:30 PM, MARTINI Requirements Last Call Update, John Elwell (20
minutes)

http://tools.ietf.org/html/draft-elwell-martini-reqs

 

Solution Updates (30 minutes)

 

1:30 PM - 1:50 PM, MARTINI with Globally Identifiable Numbers, Adam Roach
(20 minutes)

http://tools.ietf.org/html/draft-roach-martini-gin

 

1:50 PM - 2:00 PM, MARTINI Shaken  Update, Hadriel Kaplan (10 minutes)

http://tools.ietf.org/html/draft-kaplan-martini-shaken-implicit-registration
s

 

Discussion (30 minutes)

 

2:00 PM - 2:30 PM Discussion:  Participants (30 minutes)

 

Wrap-up (30 minutes)

 

2:30 PM - 2:45 PM  Hums:  WG Chairs (15 minutes)

2:45 PM - 3:00 PM  Next Steps:  WG Chairs & ADs (15 minutes)

 

MARTINI WG Meeting Slot II

Friday, March 26, 2010

1415 - 1515 Pacific Time

California D

 

Nothing scheduled at the moment (will cancel if time slot is not needed)


------=_NextPart_000_00A9_01CABBA8.300A4640
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>MARTINI
WG Meeting Slot I<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Monday,
March 22, 2010<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>1
PM &#8211; 3 PM Pacific Time<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Palos
Verdes Room<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Jabber
room:&nbsp; martini at jabber.ietf.org (Please =
join)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Question:&nbsp;
Do we have any remote presenters who need WebEx?<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Agenda<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>1 PM
&#8211; 1:10 PM:&nbsp; Preliminaries<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;
Blue Sheets<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;
Note Takers<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;
Note Well<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;
Agenda bash<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Requirements
(20 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>1:10
PM &#8211; 1:30 PM, MARTINI Requirements Last Call Update, John Elwell =
(20
minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>http://tools.ietf.org/html/draft-elwell-martini-reqs<o:p></o:p></sp=
an></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Solution
Updates (30 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>1:30
PM &#8211; 1:50 PM, MARTINI with Globally Identifiable Numbers, Adam =
Roach (20
minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>http://tools.ietf.org/html/draft-roach-martini-gin<o:p></o:p></span=
></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>1:50
PM - 2:00 PM, MARTINI Shaken&nbsp; Update, Hadriel Kaplan (10 =
minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>http://tools.ietf.org/html/draft-kaplan-martini-shaken-implicit-reg=
istrations<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Discussion
(30 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>2:00
PM &#8211; 2:30 PM Discussion:&nbsp; Participants (30 =
minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Wrap-up
(30 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>2:30
PM &#8211; 2:45 PM&nbsp; Hums:&nbsp; WG Chairs (15 =
minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>2:45
PM &#8211; 3:00 PM &nbsp;Next Steps:&nbsp; WG Chairs &amp; ADs (15 =
minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>MARTINI
WG Meeting Slot II<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Friday,
March 26, 2010<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>1415
- 1515 Pacific Time<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>California
D<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Nothing
scheduled at the moment (will cancel if time slot is not =
needed)</span><o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_00A9_01CABBA8.300A4640--

From keith.drage@alcatel-lucent.com  Thu Mar  4 15:13:18 2010
Return-Path: <keith.drage@alcatel-lucent.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 B621228C0E4 for <martini@core3.amsl.com>; Thu,  4 Mar 2010 15:13:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.168
X-Spam-Level: 
X-Spam-Status: No, score=-4.168 tagged_above=-999 required=5 tests=[AWL=2.080,  BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=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 sU1-OzQkAla9 for <martini@core3.amsl.com>; Thu,  4 Mar 2010 15:13:08 -0800 (PST)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 70E283A8839 for <martini@ietf.org>; Thu,  4 Mar 2010 15:13:04 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o24ND2j6010379 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 5 Mar 2010 00:13:02 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Fri, 5 Mar 2010 00:13:02 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>, "'MARTINI'" <martini@ietf.org>
Date: Fri, 5 Mar 2010 00:13:00 +0100
Thread-Topic: [martini] Call for Adoption of "Registration for Multiple Phone	Numbers in the SIP"
Thread-Index: Acq75lzynCu/RB4MSc6T2IL3e5RvlAACWpAQ
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE20C19E15F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
In-Reply-To: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_EDC0A1AE77C57744B664A310A0B23AE20C19E15FFRMRSSXCHMBSC3d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.13
Subject: Re: [martini] Call for Adoption of "Registration for Multiple Phone	Numbers in the SIP"
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: Thu, 04 Mar 2010 23:13:21 -0000

--_000_EDC0A1AE77C57744B664A310A0B23AE20C19E15FFRMRSSXCHMBSC3d_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

While you may be wanting to keep to the MARTINI timescales - I for one am s=
truggling to keep up with this.

You have the WGLC for requirements in the middle of a major 3GPP meeting (a=
 draft I still need to review and comment on), and now you are doing the ad=
option for GIN in the run up to the Anaheim, when I know there are still is=
sues to address here as well - as to whether this even bears commonality fo=
r where we need to get to.

So my view is NO, because it is too early. Doing this now ensures that MART=
INI goes a different way to the rest of the world and you end up with yet a=
nother interdace to support.

Keith

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Bernard Aboba
Sent: Thursday, March 04, 2010 10:02 PM
To: 'MARTINI'
Subject: [martini] Call for Adoption of "Registration for Multiple Phone Nu=
mbers in the SIP"

This is a MARTINI WG Call for Adoption of =93Registration for Multiple Phon=
e Numbers in the SIP=94 as a MARTINI WG work item, corresponding to the =93=
Multiple AoR Registration specification=94 Charter deliverable.  The docume=
nt is available for inspection here:
http://tools.ietf.org/html/draft-roach-martini-gin-01.txt
The MARTINI WG Call for Adoption will last until Friday, March 19, 2010.
Please respond to this WG Call for Adoption, whether you are in favor of ad=
opting the document as a MARTINI WG work item or not.  If you have no comme=
nts, please reply to this message and indicate in the body of your message =
whether you think the document is ready for adoption as a MARTINI WG work i=
tem or not.   Based on the response, the MARTINI WG chairs will attempt to =
determine whether WG consensus exists to adopt the document or not.
If you have comments, please provide them to the WG in one of the following=
 ways:

1.      The preferred choice is to open an issue in the MARTINI Issue track=
ing database (TRAC), which is available here: http://trac.tools.ietf.org/wg=
/martini/trac/newticket  Information on how to use TRAC is provided below. =
 Note that if you submit an issue in TRAC, it will automatically also be po=
sted to the MARTINI WG mailing list.  When submitting issues in TRAC for th=
is =93call for adoption=94, please enter =93gin=94 for the Component: and =
=93Candidate WG Document=94 for Severity.
 2. If you can=92t figure out how to use TRAC, please post your Issue to th=
e MARTINI WG mailing list (martini at ietf.org) in the following format:
To:  martini at ietf.org
Subject: GIN-Issue: <title of your issue>
Priority: blocker, critical, major, minor or trivial
<Explanation of your issue, including a proposal for specific text changes =
to resolve the issue>
The MARTINI WG uses the TRAC database to keep track of issues relating to w=
ork in progress, including working group work items and individual submissi=
ons undergoing review.    This document provides some basic information on =
how MARTINI WG participants can use TRAC to submit or edit issues.
Documentation relating to the TRAC Issue Tracking database is available her=
e:
http://trac.tools.ietf.org/wg/martini/trac/wiki
Since this documentation is somewhat lengthy (and mostly relevant to Admins=
), here is a pithy synopsis.

1.       To submit an issue in the MARTINI Issues database (known as TRAC),=
 you first need to login to the MARTINI WG site on the tools server (http:/=
/tools.ietf.org/wg/martini/trac/login )

2.       If you don=92t already have a login ID, you can obtain one by navi=
gating to this site:   http://trac.tools.ietf.org/newlogin

3.       Once you have obtained an account, you can log in by clicking on t=
he =93login=94 entry at the top of the page.  Once you have logged in, you =
can file an issue by navigating to the  ticket entry form: http://trac.tool=
s.ietf.org/wg/martini/trac/newticket

4     When opening an issue:

a.       The Type: field should be set to =93defect=94 for an issue with th=
e current document text, or =93enhancement=94 for a proposed addition of fu=
nctionality (such as an additional requirement).

b.      The Priority: field is set based on the severity of the Issue.   Fo=
r example, editorial issues are typically =93minor=94 or =93trivial=94.

c.       The Milestone: field should be set to milestone1 (useless, I know)=
.

d.      The Component: field should be set to the document you are filing t=
he issue on.  In responding to the GIN Call for Adoption, =93gin=94 is the =
appropriate choice.

e.      The Version: field should be set to =931.0=94.

f.        The Severity: field should be set to based on the status of the d=
ocument (e.g. =93Candidate WG Document=94 in this case)

g.        The Keywords: and CC: fields can be left blank unless inspiration=
 seizes you.

h.      The Assign To: field is generally filled in with the email address =
of the editor.

5.       Typically it won=92t be necessary to enclose a file with the ticke=
t, but if you need to, select =93I have files to attach to this ticket=94.

6.       If you want to preview your Issue, click on the =93Preview=94 butt=
on.  When you=92re ready to submit the issue, click on the =93Create Ticket=
=94 button.
That=92s it!
If you have an problems in dealing with TRAC, send email to me and I=92ll t=
ry to figure out what=92s going on.
Happy TRACing,
Bernard


--_000_EDC0A1AE77C57744B664A310A0B23AE20C19E15FFRMRSSXCHMBSC3d_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DWindows-125=
2">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoListParagraph {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times =
New Roman","serif"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; =
mso-style-priority: 34
}
LI.MsoListParagraph {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times =
New Roman","serif"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; =
mso-style-priority: 34
}
DIV.MsoListParagraph {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times =
New Roman","serif"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; =
mso-style-priority: 34
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: pe=
rsonal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D771440923-04032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>While you may be wanting to keep to the MARTINI ti=
mescales=20
- I for one am struggling to keep up with this.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D771440923-04032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D771440923-04032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>You have the WGLC for requirements in the middle o=
f a major=20
3GPP meeting (a draft I still need to review and comment on), and now you a=
re=20
doing the adoption for GIN in the run up to the Anaheim, when I know there =
are=20
still issues to address here as well - as to whether this even bears common=
ality=20
for where we need to get to.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D771440923-04032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D771440923-04032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>So my view is NO, because it is too early. Doing t=
his now=20
ensures that MARTINI goes a different way to the rest of the world and you =
end=20
up with yet another interdace to support.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D771440923-04032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D771440923-04032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Keith</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> martini-bounces@ietf.org=20
  [mailto:martini-bounces@ietf.org] <B>On Behalf Of </B>Bernard=20
  Aboba<BR><B>Sent:</B> Thursday, March 04, 2010 10:02 PM<BR><B>To:</B>=20
  'MARTINI'<BR><B>Subject:</B> [martini] Call for Adoption of "Registration=
 for=20
  Multiple Phone Numbers in the SIP"<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">This is a=
=20
  MARTINI WG Call for Adoption of =93Registration for Multiple Phone Number=
s in=20
  the SIP=94 as a MARTINI WG work item, corresponding to the =93Multiple Ao=
R=20
  Registration specification=94 Charter deliverable. &nbsp;The document is=
=20
  available for inspection here: <o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><A=20
  href=3D"http://tools.ietf.org/html/draft-roach-martini-gin-01.txt">http:/=
/tools.ietf.org/html/draft-roach-martini-gin-01.txt</A><o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">The MARTI=
NI WG=20
  Call for Adoption will last until Friday, March 19, 2010.<o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Please re=
spond=20
  to this WG Call for Adoption, whether you are in favor of adopting the=20
  document as a MARTINI WG work item or not. &nbsp;If you have no comments,=
=20
  please reply to this message and indicate in the body of your message whe=
ther=20
  you think the document is ready for adoption as a MARTINI WG work item or=
 not.=20
  &nbsp;&nbsp;Based on the response, the MARTINI WG chairs will attempt to=
=20
  determine whether WG consensus exists to adopt the document or not.=20
  <o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">If you ha=
ve=20
  comments, please provide them to the WG in one of the following ways:=20
  <o:p></o:p></P>
  <P class=3DMsoListParagraph=20
  style=3D"MARGIN-LEFT: 21pt; TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-seri=
f'">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The preferred choice is to open an issue in the MARTINI Issue tracking=20
  database (TRAC), which is available here: <A=20
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><SPAN=20
  style=3D"COLOR: black">http://trac.tools.ietf.org/wg/martini/trac/newtick=
et</SPAN></A>=20
  &nbsp;Information on how to use TRAC is provided below.&nbsp; Note that i=
f you=20
  submit an issue in TRAC, it will automatically also be posted to the MART=
INI=20
  WG mailing list. &nbsp;When submitting issues in TRAC for this =93call fo=
r=20
  adoption=94, please enter =93gin=94 for the Component: and =93Candidate W=
G Document=94=20
  for Severity.&nbsp; <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
  style=3D"COLOR: black">&nbsp;2. If you can=92t figure out how to use TRAC=
, please=20
  post your Issue to the MARTINI WG mailing list (martini at ietf.org) in t=
he=20
  following format: <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'">To:&nbsp; martini at=20
  ietf.org</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'">Subject: GIN-Issue: &lt;title of you=
r=20
  issue&gt;</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'">Priority: blocker, critical, major, =
minor=20
  or trivial</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'">&lt;Explanation of your issue, inclu=
ding a=20
  proposal for specific text changes to resolve the=20
  issue&gt;</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
  style=3D"COLOR: black">The MARTINI WG uses the TRAC database to keep trac=
k of=20
  issues relating to work in progress, including working group work items a=
nd=20
  individual submissions undergoing review. &nbsp;&nbsp;&nbsp;This document=
=20
  provides some basic information on how MARTINI WG participants can use TR=
AC to=20
  submit or edit issues.&nbsp; </SPAN><o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Documenta=
tion=20
  relating to the TRAC Issue Tracking database is available here:<o:p></o:p=
></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><A=20
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/wiki">http://trac.tool=
s.ietf.org/wg/martini/trac/wiki</A><o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Since thi=
s=20
  documentation is somewhat lengthy (and mostly relevant to Admins), here i=
s a=20
  pithy synopsis. <o:p></o:p></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">1.&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  To submit an issue in the MARTINI Issues database (known as TRAC), you fi=
rst=20
  need to login to the MARTINI WG site on the tools server (<A=20
  href=3D"http://tools.ietf.org/wg/martini/trac/login">http://tools.ietf.or=
g/wg/martini/trac/login</A>=20
  ) <o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">2.&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  If you don=92t already have a login ID, you can obtain one by navigating =
to this=20
  site: &nbsp;&nbsp;<A=20
  href=3D"http://trac.tools.ietf.org/newlogin">http://trac.tools.ietf.org/n=
ewlogin</A><o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">3<SPAN=20
  style=3D"COLOR: black">.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Once you hav=
e=20
  obtained an account, you can log in by clicking on the =93login=94 entry =
at the=20
  top of the page.&nbsp; Once you have logged in, you can file an issue by=
=20
  navigating to the &nbsp;ticket entry form: <A=20
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><SPAN=20
  style=3D"COLOR: black">http://trac.tools.ietf.org/wg/martini/trac/newtick=
et</SPAN></A><o:p></o:p></SPAN></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">4<SPAN=20
  style=3D"COLOR: #1f497d">&nbsp;&nbsp;&nbsp; </SPAN>&nbsp;When opening an=
=20
  issue:&nbsp;<o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">a.&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The Type: field should be set to =93defect=94 for an issue with the curre=
nt=20
  document text, or =93enhancement=94 for a proposed addition of functional=
ity (such=20
  as an additional requirement). <o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">b.&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;=20
  The Priority: field is set based on the severity of the Issue.&nbsp;&nbsp=
; For=20
  example, editorial issues are typically =93minor=94 or =93trivial=94.=20
  <o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">c<SPAN=20
  style=3D"COLOR: black">.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Mileston=
e:=20
  field should be set to milestone1 (useless, I know).=20
  <o:p></o:p></SPAN></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-seri=
f'">d.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The Component: field should be set to the document you are filing the iss=
ue=20
  on.&nbsp; In responding to the GIN Call for Adoption, =93gin=94 is the ap=
propriate=20
  choice.<o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-seri=
f'">e.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The Version: field should be set to =931.0=94. <o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-seri=
f'">f.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The Severity: field should be set to based on the status of the document =
(e.g.=20
  =93Candidate WG Document=94 in this case)<o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-seri=
f'">g.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &nbsp;The Keywords: and CC: fields can be left blank unless inspiration s=
eizes=20
  you. <o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-seri=
f'">h.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The Assign To: field is generally filled in with the email address of the=
=20
  editor. <o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">5.&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Typically it won=92t be necessary to enclose a file with the ticket, but =
if you=20
  need to, select =93I have files to attach to this ticket=94.=20
<o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">6.&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  If you want to preview your Issue, click on the =93Preview=94 button.&nbs=
p; When=20
  you=92re ready to submit the issue, click on the =93Create Ticket=94 butt=
on.=20
  <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">That=92s =
it!&nbsp;=20
  <SPAN style=3D"COLOR: #1f497d"><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">If you ha=
ve an=20
  problems in dealing with TRAC, send email to me and I=92ll try to figure =
out=20
  what=92s going on. <SPAN style=3D"COLOR: #1f497d"><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Happy=20
  TRACing,<SPAN style=3D"COLOR: #1f497d"><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal>Bernard<o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P></DIV></BLOCKQUOTE></BODY></HTM=
L>

--_000_EDC0A1AE77C57744B664A310A0B23AE20C19E15FFRMRSSXCHMBSC3d_--

From john.elwell@siemens-enterprise.com  Thu Mar  4 23:54:49 2010
Return-Path: <john.elwell@siemens-enterprise.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 A8E7A28C15D for <martini@core3.amsl.com>; Thu,  4 Mar 2010 23:54:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.462
X-Spam-Level: 
X-Spam-Status: No, score=-2.462 tagged_above=-999 required=5 tests=[AWL=0.136,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 7k09-d9oIoF2 for <martini@core3.amsl.com>; Thu,  4 Mar 2010 23:54:42 -0800 (PST)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 6AC3C28C11C for <martini@ietf.org>; Thu,  4 Mar 2010 23:54:41 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1104139; Fri, 5 Mar 2010 08:54:42 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 3C99F1EB82AB; Fri,  5 Mar 2010 08:54:42 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.57]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Fri, 5 Mar 2010 08:54:42 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>, "martini@ietf.org" <martini@ietf.org>
Date: Fri, 5 Mar 2010 08:54:41 +0100
Thread-Topic: [martini] Call for Adoption of "Registration for Multiple Phone	Numbers in the SIP"
Thread-Index: Acq75lzynCu/RB4MSc6T2IL3e5RvlAAUqgQQ
Message-ID: <A444A0F8084434499206E78C106220CABBC018D1@MCHP058A.global-ad.net>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
In-Reply-To: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A444A0F8084434499206E78C106220CABBC018D1MCHP058Aglobala_"
MIME-Version: 1.0
Subject: Re: [martini] Call for Adoption of "Registration for Multiple Phone	Numbers in the SIP"
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: Fri, 05 Mar 2010 07:54:49 -0000

--_000_A444A0F8084434499206E78C106220CABBC018D1MCHP058Aglobala_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I'm in favour.

John

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Bernard Aboba
Sent: 04 March 2010 22:02
To: 'MARTINI'
Subject: [martini] Call for Adoption of "Registration for Multiple Phone Nu=
mbers in the SIP"

This is a MARTINI WG Call for Adoption of "Registration for Multiple Phone =
Numbers in the SIP" as a MARTINI WG work item, corresponding to the "Multip=
le AoR Registration specification" Charter deliverable.  The document is av=
ailable for inspection here:
http://tools.ietf.org/html/draft-roach-martini-gin-01.txt
The MARTINI WG Call for Adoption will last until Friday, March 19, 2010.
Please respond to this WG Call for Adoption, whether you are in favor of ad=
opting the document as a MARTINI WG work item or not.  If you have no comme=
nts, please reply to this message and indicate in the body of your message =
whether you think the document is ready for adoption as a MARTINI WG work i=
tem or not.   Based on the response, the MARTINI WG chairs will attempt to =
determine whether WG consensus exists to adopt the document or not.
If you have comments, please provide them to the WG in one of the following=
 ways:

1.      The preferred choice is to open an issue in the MARTINI Issue track=
ing database (TRAC), which is available here: http://trac.tools.ietf.org/wg=
/martini/trac/newticket  Information on how to use TRAC is provided below. =
 Note that if you submit an issue in TRAC, it will automatically also be po=
sted to the MARTINI WG mailing list.  When submitting issues in TRAC for th=
is "call for adoption", please enter "gin" for the Component: and "Candidat=
e WG Document" for Severity.
 2. If you can't figure out how to use TRAC, please post your Issue to the =
MARTINI WG mailing list (martini at ietf.org) in the following format:
To:  martini at ietf.org
Subject: GIN-Issue: <title of your issue>
Priority: blocker, critical, major, minor or trivial
<Explanation of your issue, including a proposal for specific text changes =
to resolve the issue>
The MARTINI WG uses the TRAC database to keep track of issues relating to w=
ork in progress, including working group work items and individual submissi=
ons undergoing review.    This document provides some basic information on =
how MARTINI WG participants can use TRAC to submit or edit issues.
Documentation relating to the TRAC Issue Tracking database is available her=
e:
http://trac.tools.ietf.org/wg/martini/trac/wiki
Since this documentation is somewhat lengthy (and mostly relevant to Admins=
), here is a pithy synopsis.

1.       To submit an issue in the MARTINI Issues database (known as TRAC),=
 you first need to login to the MARTINI WG site on the tools server (http:/=
/tools.ietf.org/wg/martini/trac/login )

2.       If you don't already have a login ID, you can obtain one by naviga=
ting to this site:   http://trac.tools.ietf.org/newlogin

3.       Once you have obtained an account, you can log in by clicking on t=
he "login" entry at the top of the page.  Once you have logged in, you can =
file an issue by navigating to the  ticket entry form: http://trac.tools.ie=
tf.org/wg/martini/trac/newticket

4     When opening an issue:

a.       The Type: field should be set to "defect" for an issue with the cu=
rrent document text, or "enhancement" for a proposed addition of functional=
ity (such as an additional requirement).

b.      The Priority: field is set based on the severity of the Issue.   Fo=
r example, editorial issues are typically "minor" or "trivial".

c.       The Milestone: field should be set to milestone1 (useless, I know)=
.

d.      The Component: field should be set to the document you are filing t=
he issue on.  In responding to the GIN Call for Adoption, "gin" is the appr=
opriate choice.

e.      The Version: field should be set to "1.0".

f.        The Severity: field should be set to based on the status of the d=
ocument (e.g. "Candidate WG Document" in this case)

g.        The Keywords: and CC: fields can be left blank unless inspiration=
 seizes you.

h.      The Assign To: field is generally filled in with the email address =
of the editor.

5.       Typically it won't be necessary to enclose a file with the ticket,=
 but if you need to, select "I have files to attach to this ticket".

6.       If you want to preview your Issue, click on the "Preview" button. =
 When you're ready to submit the issue, click on the "Create Ticket" button=
.
That's it!
If you have an problems in dealing with TRAC, send email to me and I'll try=
 to figure out what's going on.
Happy TRACing,
Bernard


--_000_A444A0F8084434499206E78C106220CABBC018D1MCHP058Aglobala_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.5921" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoListParagraph {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times =
New Roman","serif"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; =
mso-style-priority: 34
}
LI.MsoListParagraph {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times =
New Roman","serif"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; =
mso-style-priority: 34
}
DIV.MsoListParagraph {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times =
New Roman","serif"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; =
mso-style-priority: 34
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: pe=
rsonal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D687015407-05032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I'm in favour.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D687015407-05032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D687015407-05032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>John</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> martini-bounces@ietf.org=20
  [mailto:martini-bounces@ietf.org] <B>On Behalf Of </B>Bernard=20
  Aboba<BR><B>Sent:</B> 04 March 2010 22:02<BR><B>To:</B>=20
  'MARTINI'<BR><B>Subject:</B> [martini] Call for Adoption of "Registration=
 for=20
  Multiple Phone Numbers in the SIP"<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">This is a=
=20
  MARTINI WG Call for Adoption of &#8220;Registration for Multiple Phone Nu=
mbers in=20
  the SIP&#8221; as a MARTINI WG work item, corresponding to the &#8220;Mul=
tiple AoR=20
  Registration specification&#8221; Charter deliverable. &nbsp;The document=
 is=20
  available for inspection here: <o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><A=20
  href=3D"http://tools.ietf.org/html/draft-roach-martini-gin-01.txt">http:/=
/tools.ietf.org/html/draft-roach-martini-gin-01.txt</A><o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">The MARTI=
NI WG=20
  Call for Adoption will last until Friday, March 19, 2010.<o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Please re=
spond=20
  to this WG Call for Adoption, whether you are in favor of adopting the=20
  document as a MARTINI WG work item or not. &nbsp;If you have no comments,=
=20
  please reply to this message and indicate in the body of your message whe=
ther=20
  you think the document is ready for adoption as a MARTINI WG work item or=
 not.=20
  &nbsp;&nbsp;Based on the response, the MARTINI WG chairs will attempt to=
=20
  determine whether WG consensus exists to adopt the document or not.=20
  <o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">If you ha=
ve=20
  comments, please provide them to the WG in one of the following ways:=20
  <o:p></o:p></P>
  <P class=3DMsoListParagraph=20
  style=3D"MARGIN-LEFT: 21pt; TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-seri=
f'">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The preferred choice is to open an issue in the MARTINI Issue tracking=20
  database (TRAC), which is available here: <A=20
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><SPAN=20
  style=3D"COLOR: black">http://trac.tools.ietf.org/wg/martini/trac/newtick=
et</SPAN></A>=20
  &nbsp;Information on how to use TRAC is provided below.&nbsp; Note that i=
f you=20
  submit an issue in TRAC, it will automatically also be posted to the MART=
INI=20
  WG mailing list. &nbsp;When submitting issues in TRAC for this &#8220;cal=
l for=20
  adoption&#8221;, please enter &#8220;gin&#8221; for the Component: and &#=
8220;Candidate WG Document&#8221;=20
  for Severity.&nbsp; <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
  style=3D"COLOR: black">&nbsp;2. If you can&#8217;t figure out how to use =
TRAC, please=20
  post your Issue to the MARTINI WG mailing list (martini at ietf.org) in t=
he=20
  following format: <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'">To:&nbsp; martini at=20
  ietf.org</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'">Subject: GIN-Issue: &lt;title of you=
r=20
  issue&gt;</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'">Priority: blocker, critical, major, =
minor=20
  or trivial</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'">&lt;Explanation of your issue, inclu=
ding a=20
  proposal for specific text changes to resolve the=20
  issue&gt;</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
  style=3D"COLOR: black">The MARTINI WG uses the TRAC database to keep trac=
k of=20
  issues relating to work in progress, including working group work items a=
nd=20
  individual submissions undergoing review. &nbsp;&nbsp;&nbsp;This document=
=20
  provides some basic information on how MARTINI WG participants can use TR=
AC to=20
  submit or edit issues.&nbsp; </SPAN><o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Documenta=
tion=20
  relating to the TRAC Issue Tracking database is available here:<o:p></o:p=
></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><A=20
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/wiki">http://trac.tool=
s.ietf.org/wg/martini/trac/wiki</A><o:p></o:p></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Since thi=
s=20
  documentation is somewhat lengthy (and mostly relevant to Admins), here i=
s a=20
  pithy synopsis. <o:p></o:p></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">1.&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  To submit an issue in the MARTINI Issues database (known as TRAC), you fi=
rst=20
  need to login to the MARTINI WG site on the tools server (<A=20
  href=3D"http://tools.ietf.org/wg/martini/trac/login">http://tools.ietf.or=
g/wg/martini/trac/login</A>=20
  ) <o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">2.&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  If you don&#8217;t already have a login ID, you can obtain one by navigat=
ing to this=20
  site: &nbsp;&nbsp;<A=20
  href=3D"http://trac.tools.ietf.org/newlogin">http://trac.tools.ietf.org/n=
ewlogin</A><o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">3<SPAN=20
  style=3D"COLOR: black">.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Once you hav=
e=20
  obtained an account, you can log in by clicking on the &#8220;login&#8221=
; entry at the=20
  top of the page.&nbsp; Once you have logged in, you can file an issue by=
=20
  navigating to the &nbsp;ticket entry form: <A=20
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><SPAN=20
  style=3D"COLOR: black">http://trac.tools.ietf.org/wg/martini/trac/newtick=
et</SPAN></A><o:p></o:p></SPAN></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">4<SPAN=20
  style=3D"COLOR: #1f497d">&nbsp;&nbsp;&nbsp; </SPAN>&nbsp;When opening an=
=20
  issue:&nbsp;<o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">a.&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The Type: field should be set to &#8220;defect&#8221; for an issue with t=
he current=20
  document text, or &#8220;enhancement&#8221; for a proposed addition of fu=
nctionality (such=20
  as an additional requirement). <o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">b.&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;=20
  The Priority: field is set based on the severity of the Issue.&nbsp;&nbsp=
; For=20
  example, editorial issues are typically &#8220;minor&#8221; or &#8220;tri=
vial&#8221;.=20
  <o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">c<SPAN=20
  style=3D"COLOR: black">.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Mileston=
e:=20
  field should be set to milestone1 (useless, I know).=20
  <o:p></o:p></SPAN></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-seri=
f'">d.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The Component: field should be set to the document you are filing the iss=
ue=20
  on.&nbsp; In responding to the GIN Call for Adoption, &#8220;gin&#8221; i=
s the appropriate=20
  choice.<o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-seri=
f'">e.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The Version: field should be set to &#8220;1.0&#8221;. <o:p></o:p></SPAN>=
</P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-seri=
f'">f.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The Severity: field should be set to based on the status of the document =
(e.g.=20
  &#8220;Candidate WG Document&#8221; in this case)<o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-seri=
f'">g.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &nbsp;The Keywords: and CC: fields can be left blank unless inspiration s=
eizes=20
  you. <o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-seri=
f'">h.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The Assign To: field is generally filled in with the email address of the=
=20
  editor. <o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">5.&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Typically it won&#8217;t be necessary to enclose a file with the ticket, =
but if you=20
  need to, select &#8220;I have files to attach to this ticket&#8221;.=20
<o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
  style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">6.&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  If you want to preview your Issue, click on the &#8220;Preview&#8221; but=
ton.&nbsp; When=20
  you&#8217;re ready to submit the issue, click on the &#8220;Create Ticket=
&#8221; button.=20
  <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">That&#821=
7;s it!&nbsp;=20
  <SPAN style=3D"COLOR: #1f497d"><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">If you ha=
ve an=20
  problems in dealing with TRAC, send email to me and I&#8217;ll try to fig=
ure out=20
  what&#8217;s going on. <SPAN style=3D"COLOR: #1f497d"><o:p></o:p></SPAN><=
/P>
  <P class=3DMsoNormal=20
  style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Happy=20
  TRACing,<SPAN style=3D"COLOR: #1f497d"><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal>Bernard<o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P></DIV></BLOCKQUOTE></BODY></HTM=
L>

--_000_A444A0F8084434499206E78C106220CABBC018D1MCHP058Aglobala_--

From alan.b.johnston@gmail.com  Fri Mar  5 08:10:37 2010
Return-Path: <alan.b.johnston@gmail.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 154F128C123 for <martini@core3.amsl.com>; Fri,  5 Mar 2010 08:10:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 mSvsMk8XPYXy for <martini@core3.amsl.com>; Fri,  5 Mar 2010 08:10:35 -0800 (PST)
Received: from mail-bw0-f222.google.com (mail-bw0-f222.google.com [209.85.218.222]) by core3.amsl.com (Postfix) with ESMTP id E9A9D28C142 for <martini@ietf.org>; Fri,  5 Mar 2010 08:10:31 -0800 (PST)
Received: by bwz22 with SMTP id 22so746416bwz.28 for <martini@ietf.org>; Fri, 05 Mar 2010 08:10:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=zvz0w993PYLOZZ1YcMzagKdTsk5ZXNgVEvuAygQIExY=; b=MGVj9ajRLmbF+PX8hTQs6fu2+XYQj3Kl1mcFwXaIh4ePnKA4ycIDFxKavNAflNEaeb UXpoz8l1ifcxueZuEHcgf4BfhsdaV+kdqgWrLRDszqU7Er2FudQuXmAZzQXsvN/ggikg qZEY1+/xqmlSpizjKRgcs/9vOLD45UdnwWIPQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=juXLMkAO1h/pnBNHC5wzoe55z/+dEkoPiQqj2JQgIWmUD17KmKs49IHXTZzof3FMMZ W0GdAWakjnyHNxWSrTRsGUUWmnc9iTAIKhF++B+gzfMJQheJV+Fsd6YYNWwd7WaW0bUQ DI8fsSQmCNNT6xbBNsOAQcZrSHQtegrsPt79Q=
Received: by 10.204.34.3 with SMTP id j3mr229183bkd.23.1267805429948; Fri, 05 Mar 2010 08:10:29 -0800 (PST)
Received: from Alans-PowerBook-G4-17.local (24-107-197-239.dhcp.stls.mo.charter.com [24.107.197.239]) by mx.google.com with ESMTPS id 13sm1277373bwz.3.2010.03.05.08.10.28 (version=SSLv3 cipher=RC4-MD5); Fri, 05 Mar 2010 08:10:28 -0800 (PST)
Message-ID: <4B912CF2.6050606@gmail.com>
Date: Fri, 05 Mar 2010 10:10:26 -0600
From: Alan Johnston <alan.b.johnston@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: martini@ietf.org
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
In-Reply-To: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [martini] Call for Adoption of "Registration for Multiple Phone Numbers in the SIP"
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: Fri, 05 Mar 2010 16:10:37 -0000

I would support this.

- Alan -

On 3/4/10 4:02 PM, Bernard Aboba wrote:
> This is a MARTINI WG Call for Adoption of "Registration for Multiple Phone
> Numbers in the SIP" as a MARTINI WG work item, corresponding to the
> "Multiple AoR Registration specification" Charter deliverable.  The document
> is available for inspection here: 
> 
> http://tools.ietf.org/html/draft-roach-martini-gin-01.txt
> 
> The MARTINI WG Call for Adoption will last until Friday, March 19, 2010.
> 
> Please respond to this WG Call for Adoption, whether you are in favor of
> adopting the document as a MARTINI WG work item or not.  If you have no
> comments, please reply to this message and indicate in the body of your
> message whether you think the document is ready for adoption as a MARTINI WG
> work item or not.   Based on the response, the MARTINI WG chairs will
> attempt to determine whether WG consensus exists to adopt the document or
> not. 
> 
> If you have comments, please provide them to the WG in one of the following
> ways: 
> 
> 1.      The preferred choice is to open an issue in the MARTINI Issue
> tracking database (TRAC), which is available here:
> <http://trac.tools.ietf.org/wg/martini/trac/newticket>
> http://trac.tools.ietf.org/wg/martini/trac/newticket  Information on how to
> use TRAC is provided below.  Note that if you submit an issue in TRAC, it
> will automatically also be posted to the MARTINI WG mailing list.  When
> submitting issues in TRAC for this "call for adoption", please enter "gin"
> for the Component: and "Candidate WG Document" for Severity.  
> 
>  2. If you can't figure out how to use TRAC, please post your Issue to the
> MARTINI WG mailing list (martini at ietf.org) in the following format: 
> 
> To:  martini at ietf.org
> 
> Subject: GIN-Issue: <title of your issue>
> 
> Priority: blocker, critical, major, minor or trivial
> 
> <Explanation of your issue, including a proposal for specific text changes
> to resolve the issue>
> 
> The MARTINI WG uses the TRAC database to keep track of issues relating to
> work in progress, including working group work items and individual
> submissions undergoing review.    This document provides some basic
> information on how MARTINI WG participants can use TRAC to submit or edit
> issues.  
> 
> Documentation relating to the TRAC Issue Tracking database is available
> here:
> 
> http://trac.tools.ietf.org/wg/martini/trac/wiki
> 
> Since this documentation is somewhat lengthy (and mostly relevant to
> Admins), here is a pithy synopsis. 
> 
> 1.       To submit an issue in the MARTINI Issues database (known as TRAC),
> you first need to login to the MARTINI WG site on the tools server
> (http://tools.ietf.org/wg/martini/trac/login ) 
> 
> 2.       If you don't already have a login ID, you can obtain one by
> navigating to this site:   http://trac.tools.ietf.org/newlogin
> 
> 3.       Once you have obtained an account, you can log in by clicking on
> the "login" entry at the top of the page.  Once you have logged in, you can
> file an issue by navigating to the  ticket entry form:
> <http://trac.tools.ietf.org/wg/martini/trac/newticket>
> http://trac.tools.ietf.org/wg/martini/trac/newticket
> 
> 4     When opening an issue: 
> 
> a.       The Type: field should be set to "defect" for an issue with the
> current document text, or "enhancement" for a proposed addition of
> functionality (such as an additional requirement). 
> 
> b.      The Priority: field is set based on the severity of the Issue.   For
> example, editorial issues are typically "minor" or "trivial". 
> 
> c.       The Milestone: field should be set to milestone1 (useless, I know).
> 
> 
> d.      The Component: field should be set to the document you are filing
> the issue on.  In responding to the GIN Call for Adoption, "gin" is the
> appropriate choice.
> 
> e.      The Version: field should be set to "1.0". 
> 
> f.        The Severity: field should be set to based on the status of the
> document (e.g. "Candidate WG Document" in this case)
> 
> g.        The Keywords: and CC: fields can be left blank unless inspiration
> seizes you. 
> 
> h.      The Assign To: field is generally filled in with the email address
> of the editor. 
> 
> 5.       Typically it won't be necessary to enclose a file with the ticket,
> but if you need to, select "I have files to attach to this ticket". 
> 
> 6.       If you want to preview your Issue, click on the "Preview" button.
> When you're ready to submit the issue, click on the "Create Ticket" button. 
> 
> That's it!  
> 
> If you have an problems in dealing with TRAC, send email to me and I'll try
> to figure out what's going on. 
> 
> Happy TRACing,
> 
> Bernard
> 
>  
> 
> 
> 
> 
> 
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini

From HKaplan@acmepacket.com  Fri Mar  5 08:11:31 2010
Return-Path: <HKaplan@acmepacket.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 79B603A8FEA for <martini@core3.amsl.com>; Fri,  5 Mar 2010 08:11:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 yM4Z5NIoG8-V for <martini@core3.amsl.com>; Fri,  5 Mar 2010 08:11:17 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 2AC4028C142 for <martini@ietf.org>; Fri,  5 Mar 2010 08:11:16 -0800 (PST)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 5 Mar 2010 11:11:17 -0500
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Fri, 5 Mar 2010 11:11:17 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>, 'MARTINI' <martini@ietf.org>
Date: Fri, 5 Mar 2010 11:11:15 -0500
Thread-Topic: [martini] Call for Adoption of "Registration for Multiple Phone	Numbers in the SIP"
Thread-Index: Acq75lzynCu/RB4MSc6T2IL3e5RvlAAl/rAw
Message-ID: <430FC6BDED356B4C8498F634416644A91952C0BF2E@mail>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
In-Reply-To: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_430FC6BDED356B4C8498F634416644A91952C0BF2Email_"
MIME-Version: 1.0
Subject: Re: [martini] Call for Adoption of "Registration for Multiple Phone	Numbers in the SIP"
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: Fri, 05 Mar 2010 16:11:32 -0000

--_000_430FC6BDED356B4C8498F634416644A91952C0BF2Email_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I'm in favor of it - we need to move forward, and GIN is close enough to Sh=
aken that I think we might was well just go forward with GIN and get this d=
one.
-hadriel

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Bernard Aboba
Sent: Thursday, March 04, 2010 5:02 PM
To: 'MARTINI'
Subject: [martini] Call for Adoption of "Registration for Multiple Phone Nu=
mbers in the SIP"

This is a MARTINI WG Call for Adoption of "Registration for Multiple Phone =
Numbers in the SIP" as a MARTINI WG work item, corresponding to the "Multip=
le AoR Registration specification" Charter deliverable.  The document is av=
ailable for inspection here:
http://tools.ietf.org/html/draft-roach-martini-gin-01.txt
The MARTINI WG Call for Adoption will last until Friday, March 19, 2010.
Please respond to this WG Call for Adoption, whether you are in favor of ad=
opting the document as a MARTINI WG work item or not.  If you have no comme=
nts, please reply to this message and indicate in the body of your message =
whether you think the document is ready for adoption as a MARTINI WG work i=
tem or not.   Based on the response, the MARTINI WG chairs will attempt to =
determine whether WG consensus exists to adopt the document or not.
If you have comments, please provide them to the WG in one of the following=
 ways:

1.      The preferred choice is to open an issue in the MARTINI Issue track=
ing database (TRAC), which is available here: http://trac.tools.ietf.org/wg=
/martini/trac/newticket  Information on how to use TRAC is provided below. =
 Note that if you submit an issue in TRAC, it will automatically also be po=
sted to the MARTINI WG mailing list.  When submitting issues in TRAC for th=
is "call for adoption", please enter "gin" for the Component: and "Candidat=
e WG Document" for Severity.
 2. If you can't figure out how to use TRAC, please post your Issue to the =
MARTINI WG mailing list (martini at ietf.org) in the following format:
To:  martini at ietf.org
Subject: GIN-Issue: <title of your issue>
Priority: blocker, critical, major, minor or trivial
<Explanation of your issue, including a proposal for specific text changes =
to resolve the issue>
The MARTINI WG uses the TRAC database to keep track of issues relating to w=
ork in progress, including working group work items and individual submissi=
ons undergoing review.    This document provides some basic information on =
how MARTINI WG participants can use TRAC to submit or edit issues.
Documentation relating to the TRAC Issue Tracking database is available her=
e:
http://trac.tools.ietf.org/wg/martini/trac/wiki
Since this documentation is somewhat lengthy (and mostly relevant to Admins=
), here is a pithy synopsis.

1.       To submit an issue in the MARTINI Issues database (known as TRAC),=
 you first need to login to the MARTINI WG site on the tools server (http:/=
/tools.ietf.org/wg/martini/trac/login )

2.       If you don't already have a login ID, you can obtain one by naviga=
ting to this site:   http://trac.tools.ietf.org/newlogin

3.       Once you have obtained an account, you can log in by clicking on t=
he "login" entry at the top of the page.  Once you have logged in, you can =
file an issue by navigating to the  ticket entry form: http://trac.tools.ie=
tf.org/wg/martini/trac/newticket

4     When opening an issue:

a.       The Type: field should be set to "defect" for an issue with the cu=
rrent document text, or "enhancement" for a proposed addition of functional=
ity (such as an additional requirement).

b.      The Priority: field is set based on the severity of the Issue.   Fo=
r example, editorial issues are typically "minor" or "trivial".

c.       The Milestone: field should be set to milestone1 (useless, I know)=
.

d.      The Component: field should be set to the document you are filing t=
he issue on.  In responding to the GIN Call for Adoption, "gin" is the appr=
opriate choice.

e.      The Version: field should be set to "1.0".

f.        The Severity: field should be set to based on the status of the d=
ocument (e.g. "Candidate WG Document" in this case)

g.        The Keywords: and CC: fields can be left blank unless inspiration=
 seizes you.

h.      The Assign To: field is generally filled in with the email address =
of the editor.

5.       Typically it won't be necessary to enclose a file with the ticket,=
 but if you need to, select "I have files to attach to this ticket".

6.       If you want to preview your Issue, click on the "Preview" button. =
 When you're ready to submit the issue, click on the "Create Ticket" button=
.
That's it!
If you have an problems in dealing with TRAC, send email to me and I'll try=
 to figure out what's going on.
Happy TRACing,
Bernard


--_000_430FC6BDED356B4C8498F634416644A91952C0BF2Email_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40"
xmlns:ns5=3D"http://schemas.microsoft.com/office/2004/12/omml">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"Person=
Name"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}
p.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
li.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
div.MSOLISTPARAGRAPH
	{mso-style-priority:34;}

 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.msolistparagraph, li.msolistparagraph, div.msolistparagraph
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Calibri;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I&#8217;m in favor of it &#8211; we ne=
ed to move
forward, and GIN is close enough to Shaken that I think we might was well j=
ust
go forward with GIN and get this done.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>-hadriel<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;font-family:"Times=
 New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> martini-=
bounces@ietf.org
[mailto:martini-bounces@ietf.org] <b><span style=3D'font-weight:bold'>On Be=
half
Of </span></b><st1:PersonName w:st=3D"on">Bernard Aboba</st1:PersonName><br=
>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, March 04, 20=
10
5:02 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'MARTINI'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [martini] Call for
Adoption of &quot;Registration for Multiple Phone Numbers in the SIP&quot;<=
/span></font><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt;font-fami=
ly:"Times New Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'>This is a MARTINI =
WG Call
for Adoption of &#8220;Registration for Multiple Phone Numbers in the SIP&#=
8221; as a
MARTINI WG work item, corresponding to the &#8220;Multiple AoR Registration
specification&#8221; Charter deliverable. &nbsp;The document is available f=
or
inspection here: <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'><a
href=3D"http://tools.ietf.org/html/draft-roach-martini-gin-01.txt">http://t=
ools.ietf.org/html/draft-roach-martini-gin-01.txt</a><o:p></o:p></span></fo=
nt></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'>The MARTINI WG Cal=
l for
Adoption will last until Friday, March 19, 2010.<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'>Please respond to =
this WG
Call for Adoption, whether you are in favor of adopting the document as a
MARTINI WG work item or not. &nbsp;If you have no comments, please reply to
this message and indicate in the body of your message whether you think the
document is ready for adoption as a MARTINI WG work item or not.
&nbsp;&nbsp;Based on the response, the MARTINI WG chairs will attempt to
determine whether WG consensus exists to adopt the document or not. <o:p></=
o:p></span></font></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'>If you have commen=
ts, please
provide them to the WG in one of the following ways: <o:p></o:p></span></fo=
nt></p>

<p class=3Dmsolistparagraph style=3D'margin-left:21.0pt;text-indent:-.25in'=
><font
size=3D2 color=3Dblack face=3DCalibri><span style=3D'font-size:11.0pt;font-=
family:Calibri;
color:black'>1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The preferred choice is to op=
en
an issue in the MARTINI Issue tracking database (TRAC), which is available
here: <a href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><fon=
t
color=3Dblack><span style=3D'color:black'>http://trac.tools.ietf.org/wg/mar=
tini/trac/newticket</span></font></a>
&nbsp;Information on how to use TRAC is provided below.&nbsp; Note that if =
you
submit an issue in TRAC, it will automatically also be posted to the MARTIN=
I WG
mailing list. &nbsp;When submitting issues in TRAC for this &#8220;call for
adoption&#8221;, please enter &#8220;gin&#8221; for the Component: and &#82=
20;Candidate WG Document&#8221;
for Severity.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 color=3Dblack face=3DCalibri><span style=3D'font-size:11.0pt;color=
:black'>&nbsp;2.
If you can&#8217;t figure out how to use TRAC, please post your Issue to th=
e MARTINI
WG mailing list (martini at ietf.org) in the following format: <o:p></o:p><=
/span></font></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:11.0pt;font-family:"=
Courier New"'>To:&nbsp;
martini at ietf.org</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:11.0pt;font-family:"=
Courier New"'>Subject:
GIN-Issue: &lt;title of your issue&gt;</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:11.0pt;font-family:"=
Courier New"'>Priority:
blocker, critical, major, minor or trivial</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:11.0pt;font-family:"=
Courier New"'>&lt;Explanation
of your issue, including a proposal for specific text changes to resolve th=
e
issue&gt;</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 color=3Dblack face=3DCalibri><span style=3D'font-size:11.0pt;color=
:black'>The
MARTINI WG uses the TRAC database to keep track of issues relating to work =
in
progress, including working group work items and individual submissions
undergoing review. &nbsp;&nbsp;&nbsp;This document provides some basic
information on how MARTINI WG participants can use TRAC to submit or edit
issues.&nbsp; </span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'>Documentation rela=
ting to
the TRAC Issue Tracking database is available here:<o:p></o:p></span></font=
></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'><a
href=3D"http://trac.tools.ietf.org/wg/martini/trac/wiki">http://trac.tools.=
ietf.org/wg/martini/trac/wiki</a><o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'>Since this documen=
tation is somewhat
lengthy (and mostly relevant to Admins), here is a pithy synopsis. <o:p></o=
:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in'><font size=3D2 fac=
e=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri'>1.&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
To submit an issue in the MARTINI Issues database (known as TRAC), you firs=
t
need to login to the MARTINI WG site on the tools server (<a
href=3D"http://tools.ietf.org/wg/martini/trac/login">http://tools.ietf.org/=
wg/martini/trac/login</a>
) <o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in'><font size=3D2 fac=
e=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri'>2.&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
If you don&#8217;t already have a login ID, you can obtain one by navigatin=
g to this
site: &nbsp;&nbsp;<a href=3D"http://trac.tools.ietf.org/newlogin">http://tr=
ac.tools.ietf.org/newlogin</a><o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in'><font size=3D2 fac=
e=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri'>3<font color=3Dblack><span
style=3D'color:black'>.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Once you have
obtained an account, you can log in by clicking on the &#8220;login&#8221; =
entry at the top
of the page.&nbsp; Once you have logged in, you can file an issue by naviga=
ting
to the &nbsp;ticket entry form: <a
href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><font color=
=3Dblack><span
style=3D'color:black'>http://trac.tools.ietf.org/wg/martini/trac/newticket<=
/span></font></a><o:p></o:p></span></font></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in'><font size=3D2 fac=
e=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri'>4<font color=3D"#1f497d"><sp=
an
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp; </span></font>&nbsp;When opening=
 an
issue:&nbsp;<o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in'><font size=3D2 fac=
e=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri'>a.&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
The Type: field should be set to &#8220;defect&#8221; for an issue with the=
 current
document text, or &#8220;enhancement&#8221; for a proposed addition of func=
tionality (such
as an additional requirement). <o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in'><font size=3D2 fac=
e=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri'>b.&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;
The Priority: field is set based on the severity of the Issue.&nbsp;&nbsp; =
For
example, editorial issues are typically &#8220;minor&#8221; or &#8220;trivi=
al&#8221;. <o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in'><font size=3D2 fac=
e=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri'>c<font color=3Dblack><span
style=3D'color:black'>.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Milestone: =
field
should be set to milestone1 (useless, I know). <o:p></o:p></span></font></s=
pan></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in'><font size=3D2 col=
or=3Dblack
face=3DCalibri><span style=3D'font-size:11.0pt;font-family:Calibri;color:bl=
ack'>d.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The Component: field should be set to the document you are filing the issue
on.&nbsp; In responding to the GIN Call for Adoption, &#8220;gin&#8221; is =
the appropriate
choice.<o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in'><font size=3D2 col=
or=3Dblack
face=3DCalibri><span style=3D'font-size:11.0pt;font-family:Calibri;color:bl=
ack'>e.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The Version: field should be set to &#8220;1.0&#8221;. <o:p></o:p></span></=
font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in'><font size=3D2 col=
or=3Dblack
face=3DCalibri><span style=3D'font-size:11.0pt;font-family:Calibri;color:bl=
ack'>f.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The Severity: field should be set to based on the status of the document (e=
.g.
&#8220;Candidate WG Document&#8221; in this case)<o:p></o:p></span></font><=
/p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in'><font size=3D2 col=
or=3Dblack
face=3DCalibri><span style=3D'font-size:11.0pt;font-family:Calibri;color:bl=
ack'>g.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;The Keywords: and CC: fields can be left blank unless inspiration sei=
zes
you. <o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in'><font size=3D2 col=
or=3Dblack
face=3DCalibri><span style=3D'font-size:11.0pt;font-family:Calibri;color:bl=
ack'>h.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The Assign To: field is generally filled in with the email address of the
editor. <o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in'><font size=3D2 fac=
e=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri'>5.&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
Typically it won&#8217;t be necessary to enclose a file with the ticket, bu=
t if you
need to, select &#8220;I have files to attach to this ticket&#8221;. <o:p><=
/o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in'><font size=3D2 fac=
e=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri'>6.&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
If you want to preview your Issue, click on the &#8220;Preview&#8221; butto=
n.&nbsp; When
you&#8217;re ready to submit the issue, click on the &#8220;Create Ticket&#=
8221; button. <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'>That&#8217;s it!&n=
bsp; <font
color=3D"#1f497d"><span style=3D'color:#1F497D'><o:p></o:p></span></font></=
span></font></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'>If you have an pro=
blems in
dealing with TRAC, send email to me and I&#8217;ll try to figure out what&#=
8217;s going on.
<font color=3D"#1f497d"><span style=3D'color:#1F497D'><o:p></o:p></span></f=
ont></span></font></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'>Happy TRACing,<fon=
t
color=3D"#1f497d"><span style=3D'color:#1F497D'><o:p></o:p></span></font></=
span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'>Bernard<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>

</body>

</html>

--_000_430FC6BDED356B4C8498F634416644A91952C0BF2Email_--

From bernard_aboba@hotmail.com  Fri Mar  5 08:38:55 2010
Return-Path: <bernard_aboba@hotmail.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 B8BB328C1F6 for <martini@core3.amsl.com>; Fri,  5 Mar 2010 08:38:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.983
X-Spam-Level: 
X-Spam-Status: No, score=-1.983 tagged_above=-999 required=5 tests=[AWL=0.615,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 HRN3XeP3Dg2t for <martini@core3.amsl.com>; Fri,  5 Mar 2010 08:38:47 -0800 (PST)
Received: from blu0-omc2-s25.blu0.hotmail.com (blu0-omc2-s25.blu0.hotmail.com [65.55.111.100]) by core3.amsl.com (Postfix) with ESMTP id 616A83A774E for <martini@ietf.org>; Fri,  5 Mar 2010 08:38:47 -0800 (PST)
Received: from BLU137-DS10 ([65.55.111.71]) by blu0-omc2-s25.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 5 Mar 2010 08:38:49 -0800
X-Originating-IP: [131.107.0.102]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS1062BD9518A4D7B629EF4793380@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'MARTINI'" <martini@ietf.org>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl> <430FC6BDED356B4C8498F634416644A91952C0BF2E@mail>
In-Reply-To: <430FC6BDED356B4C8498F634416644A91952C0BF2E@mail>
Date: Fri, 5 Mar 2010 08:38:50 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0092_01CABC3F.47FCC5B0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH5qMo/QP7i6yqnAZERxQ3cnPcK2wHlikUfkXaGtFA=
Content-Language: en-us
X-OriginalArrivalTime: 05 Mar 2010 16:38:49.0713 (UTC) FILETIME=[5558BE10:01CABC82]
Subject: Re: [martini] Call for Adoption of "Registration for Multiple Phone	Numbers in the SIP"
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: Fri, 05 Mar 2010 16:38:55 -0000

------=_NextPart_000_0092_01CABC3F.47FCC5B0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

+1. 

 

From: Hadriel Kaplan [mailto:HKaplan@acmepacket.com] 
Sent: Friday, March 05, 2010 8:11 AM
To: Bernard Aboba; 'MARTINI'
Subject: RE: [martini] Call for Adoption of "Registration for Multiple Phone
Numbers in the SIP"

 

I'm in favor of it - we need to move forward, and GIN is close enough to
Shaken that I think we might was well just go forward with GIN and get this
done.

-hadriel

 

  _____  

From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf
Of Bernard Aboba
Sent: Thursday, March 04, 2010 5:02 PM
To: 'MARTINI'
Subject: [martini] Call for Adoption of "Registration for Multiple Phone
Numbers in the SIP"

 

This is a MARTINI WG Call for Adoption of "Registration for Multiple Phone
Numbers in the SIP" as a MARTINI WG work item, corresponding to the
"Multiple AoR Registration specification" Charter deliverable.  The document
is available for inspection here: 

http://tools.ietf.org/html/draft-roach-martini-gin-01.txt

The MARTINI WG Call for Adoption will last until Friday, March 19, 2010.

Please respond to this WG Call for Adoption, whether you are in favor of
adopting the document as a MARTINI WG work item or not.  If you have no
comments, please reply to this message and indicate in the body of your
message whether you think the document is ready for adoption as a MARTINI WG
work item or not.   Based on the response, the MARTINI WG chairs will
attempt to determine whether WG consensus exists to adopt the document or
not. 

If you have comments, please provide them to the WG in one of the following
ways: 

1.      The preferred choice is to open an issue in the MARTINI Issue
tracking database (TRAC), which is available here:
<http://trac.tools.ietf.org/wg/martini/trac/newticket>
http://trac.tools.ietf.org/wg/martini/trac/newticket  Information on how to
use TRAC is provided below.  Note that if you submit an issue in TRAC, it
will automatically also be posted to the MARTINI WG mailing list.  When
submitting issues in TRAC for this "call for adoption", please enter "gin"
for the Component: and "Candidate WG Document" for Severity.  

 2. If you can't figure out how to use TRAC, please post your Issue to the
MARTINI WG mailing list (martini at ietf.org) in the following format: 

To:  martini at ietf.org

Subject: GIN-Issue: <title of your issue>

Priority: blocker, critical, major, minor or trivial

<Explanation of your issue, including a proposal for specific text changes
to resolve the issue>

The MARTINI WG uses the TRAC database to keep track of issues relating to
work in progress, including working group work items and individual
submissions undergoing review.    This document provides some basic
information on how MARTINI WG participants can use TRAC to submit or edit
issues.  

Documentation relating to the TRAC Issue Tracking database is available
here:

http://trac.tools.ietf.org/wg/martini/trac/wiki

Since this documentation is somewhat lengthy (and mostly relevant to
Admins), here is a pithy synopsis. 

1.       To submit an issue in the MARTINI Issues database (known as TRAC),
you first need to login to the MARTINI WG site on the tools server
(http://tools.ietf.org/wg/martini/trac/login ) 

2.       If you don't already have a login ID, you can obtain one by
navigating to this site:   http://trac.tools.ietf.org/newlogin

3.       Once you have obtained an account, you can log in by clicking on
the "login" entry at the top of the page.  Once you have logged in, you can
file an issue by navigating to the  ticket entry form:
<http://trac.tools.ietf.org/wg/martini/trac/newticket>
http://trac.tools.ietf.org/wg/martini/trac/newticket

4     When opening an issue: 

a.       The Type: field should be set to "defect" for an issue with the
current document text, or "enhancement" for a proposed addition of
functionality (such as an additional requirement). 

b.      The Priority: field is set based on the severity of the Issue.   For
example, editorial issues are typically "minor" or "trivial". 

c.       The Milestone: field should be set to milestone1 (useless, I know).


d.      The Component: field should be set to the document you are filing
the issue on.  In responding to the GIN Call for Adoption, "gin" is the
appropriate choice.

e.      The Version: field should be set to "1.0". 

f.        The Severity: field should be set to based on the status of the
document (e.g. "Candidate WG Document" in this case)

g.        The Keywords: and CC: fields can be left blank unless inspiration
seizes you. 

h.      The Assign To: field is generally filled in with the email address
of the editor. 

5.       Typically it won't be necessary to enclose a file with the ticket,
but if you need to, select "I have files to attach to this ticket". 

6.       If you want to preview your Issue, click on the "Preview" button.
When you're ready to submit the issue, click on the "Create Ticket" button. 

That's it!  

If you have an problems in dealing with TRAC, send email to me and I'll try
to figure out what's going on. 

Happy TRACing,

Bernard

 


------=_NextPart_000_0092_01CABC3F.47FCC5B0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><!--[if !mso]><style>v\:* =
{behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:navy;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>+1. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Hadriel Kaplan [mailto:HKaplan@acmepacket.com] <br><b>Sent:</b> Friday, =
March 05, 2010 8:11 AM<br><b>To:</b> Bernard Aboba; =
'MARTINI'<br><b>Subject:</b> RE: [martini] Call for Adoption of =
&quot;Registration for Multiple Phone Numbers in the =
SIP&quot;<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>I&=
#8217;m in favor of it &#8211; we need to move forward, and GIN is close =
enough to Shaken that I think we might was well just go forward with GIN =
and get this done.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>-h=
adriel<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'><o=
:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-left:solid =
blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><hr =
size=3D2 width=3D"100%" align=3Dcenter></span></div><p =
class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <b>On Behalf =
Of </b>Bernard Aboba<br><b>Sent:</b> Thursday, March 04, 2010 5:02 =
PM<br><b>To:</b> 'MARTINI'<br><b>Subject:</b> [martini] Call for =
Adoption of &quot;Registration for Multiple Phone Numbers in the =
SIP&quot;</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>This is a =
MARTINI WG Call for Adoption of &#8220;Registration for Multiple Phone =
Numbers in the SIP&#8221; as a MARTINI WG work item, corresponding to =
the &#8220;Multiple AoR Registration specification&#8221; Charter =
deliverable. &nbsp;The document is available for inspection here: =
<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a =
href=3D"http://tools.ietf.org/html/draft-roach-martini-gin-01.txt">http:/=
/tools.ietf.org/html/draft-roach-martini-gin-01.txt</a><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The MARTINI =
WG Call for Adoption will last until Friday, March 19, =
2010.<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Please =
respond to this WG Call for Adoption, whether you are in favor of =
adopting the document as a MARTINI WG work item or not. &nbsp;If you =
have no comments, please reply to this message and indicate in the body =
of your message whether you think the document is ready for adoption as =
a MARTINI WG work item or not. &nbsp;&nbsp;Based on the response, the =
MARTINI WG chairs will attempt to determine whether WG consensus exists =
to adopt the document or not. <o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>If you have =
comments, please provide them to the WG in one of the following ways: =
<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:21.0pt;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The preferred choice is to open an =
issue in the MARTINI Issue tracking database (TRAC), which is available =
here: <a =
href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><span =
style=3D'color:black'>http://trac.tools.ietf.org/wg/martini/trac/newticke=
t</span></a> &nbsp;Information on how to use TRAC is provided =
below.&nbsp; Note that if you submit an issue in TRAC, it will =
automatically also be posted to the MARTINI WG mailing list. &nbsp;When =
submitting issues in TRAC for this &#8220;call for adoption&#8221;, =
please enter &#8220;gin&#8221; for the Component: and &#8220;Candidate =
WG Document&#8221; for Severity.&nbsp; <o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:black'>&nbsp;2. If you can&#8217;t figure out how to use =
TRAC, please post your Issue to the MARTINI WG mailing list (martini at =
ietf.org) in the following format: <o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-family:"Courier New"'>To:&nbsp; martini at =
ietf.org</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-family:"Courier New"'>Subject: GIN-Issue: &lt;title of =
your issue&gt;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-family:"Courier New"'>Priority: blocker, critical, major, =
minor or trivial</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-family:"Courier New"'>&lt;Explanation of your issue, =
including a proposal for specific text changes to resolve the =
issue&gt;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:black'>The MARTINI WG uses the TRAC database to keep =
track of issues relating to work in progress, including working group =
work items and individual submissions undergoing review. =
&nbsp;&nbsp;&nbsp;This document provides some basic information on how =
MARTINI WG participants can use TRAC to submit or edit issues.&nbsp; =
</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Documentatio=
n relating to the TRAC Issue Tracking database is available =
here:<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a =
href=3D"http://trac.tools.ietf.org/wg/martini/trac/wiki">http://trac.tool=
s.ietf.org/wg/martini/trac/wiki</a><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Since this =
documentation is somewhat lengthy (and mostly relevant to Admins), here =
is a pithy synopsis. <o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>1.&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; To submit an issue in the MARTINI Issues =
database (known as TRAC), you first need to login to the MARTINI WG site =
on the tools server (<a =
href=3D"http://tools.ietf.org/wg/martini/trac/login">http://tools.ietf.or=
g/wg/martini/trac/login</a> ) <o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>2.&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; If you don&#8217;t already have a login ID, =
you can obtain one by navigating to this site: &nbsp;&nbsp;<a =
href=3D"http://trac.tools.ietf.org/newlogin">http://trac.tools.ietf.org/n=
ewlogin</a><o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>3<span =
style=3D'color:black'>.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Once you =
have obtained an account, you can log in by clicking on the =
&#8220;login&#8221; entry at the top of the page.&nbsp; Once you have =
logged in, you can file an issue by navigating to the &nbsp;ticket entry =
form: <a =
href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><span =
style=3D'color:black'>http://trac.tools.ietf.org/wg/martini/trac/newticke=
t</span></a><o:p></o:p></span></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>4<span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp; </span>&nbsp;When opening an =
issue:&nbsp;<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>a.&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; The Type: field should be set to =
&#8220;defect&#8221; for an issue with the current document text, or =
&#8220;enhancement&#8221; for a proposed addition of functionality (such =
as an additional requirement). <o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>b.&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; The Priority: field is set based on the severity =
of the Issue.&nbsp;&nbsp; For example, editorial issues are typically =
&#8220;minor&#8221; or &#8220;trivial&#8221;. <o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>c<span =
style=3D'color:black'>.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The =
Milestone: field should be set to milestone1 (useless, I know). =
<o:p></o:p></span></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>d.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Component: field should be set to =
the document you are filing the issue on.&nbsp; In responding to the GIN =
Call for Adoption, &#8220;gin&#8221; is the appropriate =
choice.<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>e.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Version: field should be set to =
&#8220;1.0&#8221;. <o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>f.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Severity: field should =
be set to based on the status of the document (e.g. &#8220;Candidate WG =
Document&#8221; in this case)<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>g.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;The Keywords: and CC: =
fields can be left blank unless inspiration seizes you. =
<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>h.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Assign To: field is generally =
filled in with the email address of the editor. <o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>5.&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; Typically it won&#8217;t be necessary to =
enclose a file with the ticket, but if you need to, select &#8220;I have =
files to attach to this ticket&#8221;. <o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>6.&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; If you want to preview your Issue, click on =
the &#8220;Preview&#8221; button.&nbsp; When you&#8217;re ready to =
submit the issue, click on the &#8220;Create Ticket&#8221; button. =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>That&#8217;s=
 it!&nbsp; <span style=3D'color:#1F497D'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>If you have =
an problems in dealing with TRAC, send email to me and I&#8217;ll try to =
figure out what&#8217;s going on. <span =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Happy =
TRACing,<span style=3D'color:#1F497D'><o:p></o:p></span></p><p =
class=3DMsoNormal>Bernard<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_0092_01CABC3F.47FCC5B0--

From richard@shockey.us  Fri Mar  5 09:15:23 2010
Return-Path: <richard@shockey.us>
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 2813B28C2C1 for <martini@core3.amsl.com>; Fri,  5 Mar 2010 09:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 4fIPYxw1hOnn for <martini@core3.amsl.com>; Fri,  5 Mar 2010 09:15:14 -0800 (PST)
Received: from outbound-mail-360.bluehost.com (outbound-mail-360.bluehost.com [66.147.249.254]) by core3.amsl.com (Postfix) with SMTP id 4CEAC28C1E3 for <martini@ietf.org>; Fri,  5 Mar 2010 09:15:13 -0800 (PST)
Received: (qmail 14139 invoked by uid 0); 5 Mar 2010 17:15:15 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy2.bluehost.com with SMTP; 5 Mar 2010 17:15:15 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=WkLhU9HMZuyJmgVjAQnH7duJkHQNlm2Sv1KwDcJUpQxyHEzB94ADpPWeYtBwmd99FBAoPhZXsatx/x5yvHe50prZ3ivLhNECEdOzDfgQYmyx+XoZoOMxfq1+HTFKfcjG;
Received: from pool-173-66-69-79.washdc.fios.verizon.net ([173.66.69.79] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from <richard@shockey.us>) id 1Nnb7L-0001gb-2Q; Fri, 05 Mar 2010 10:15:15 -0700
From: "Richard Shockey" <richard@shockey.us>
To: "'Bernard Aboba'" <bernard_aboba@hotmail.com>, "'MARTINI'" <martini@ietf.org>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl> <430FC6BDED356B4C8498F634416644A91952C0BF2E@mail>
In-Reply-To: <430FC6BDED356B4C8498F634416644A91952C0BF2E@mail>
Date: Fri, 5 Mar 2010 12:15:12 -0500
Message-ID: <016101cabc87$6b17a900$4146fb00$@us>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0162_01CABC5D.82441200"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acq75lzynCu/RB4MSc6T2IL3e5RvlAAl/rAwAAIjwJA=
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.66.69.79 authed with richard@shockey.us}
Subject: Re: [martini] Call for Adoption of "Registration for Multiple	Phone	Numbers in the SIP"
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: Fri, 05 Mar 2010 17:15:23 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0162_01CABC5D.82441200
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

+1 as well.

 

 I totally concur. Hadriel ..I know you can work with Adam on incorporating
any issues you can have into Gin  and I certainly think you deserve
significant recognition for all of your hard work in shaken.

 

We all owe Hadriel a Bombay Sapphire Gin Martini in Anaheim.

 

From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf
Of Hadriel Kaplan
Sent: Friday, March 05, 2010 11:11 AM
To: Bernard Aboba; 'MARTINI'
Subject: Re: [martini] Call for Adoption of "Registration for Multiple Phone
Numbers in the SIP"

 

I'm in favor of it - we need to move forward, and GIN is close enough to
Shaken that I think we might was well just go forward with GIN and get this
done.

-hadriel

 

  _____  

From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf
Of Bernard Aboba
Sent: Thursday, March 04, 2010 5:02 PM
To: 'MARTINI'
Subject: [martini] Call for Adoption of "Registration for Multiple Phone
Numbers in the SIP"

 

This is a MARTINI WG Call for Adoption of "Registration for Multiple Phone
Numbers in the SIP" as a MARTINI WG work item, corresponding to the
"Multiple AoR Registration specification" Charter deliverable.  The document
is available for inspection here: 

http://tools.ietf.org/html/draft-roach-martini-gin-01.txt

The MARTINI WG Call for Adoption will last until Friday, March 19, 2010.

Please respond to this WG Call for Adoption, whether you are in favor of
adopting the document as a MARTINI WG work item or not.  If you have no
comments, please reply to this message and indicate in the body of your
message whether you think the document is ready for adoption as a MARTINI WG
work item or not.   Based on the response, the MARTINI WG chairs will
attempt to determine whether WG consensus exists to adopt the document or
not. 

If you have comments, please provide them to the WG in one of the following
ways: 

1.      The preferred choice is to open an issue in the MARTINI Issue
tracking database (TRAC), which is available here:
<http://trac.tools.ietf.org/wg/martini/trac/newticket>
http://trac.tools.ietf.org/wg/martini/trac/newticket  Information on how to
use TRAC is provided below.  Note that if you submit an issue in TRAC, it
will automatically also be posted to the MARTINI WG mailing list.  When
submitting issues in TRAC for this "call for adoption", please enter "gin"
for the Component: and "Candidate WG Document" for Severity.  

 2. If you can't figure out how to use TRAC, please post your Issue to the
MARTINI WG mailing list (martini at ietf.org) in the following format: 

To:  martini at ietf.org

Subject: GIN-Issue: <title of your issue>

Priority: blocker, critical, major, minor or trivial

<Explanation of your issue, including a proposal for specific text changes
to resolve the issue>

The MARTINI WG uses the TRAC database to keep track of issues relating to
work in progress, including working group work items and individual
submissions undergoing review.    This document provides some basic
information on how MARTINI WG participants can use TRAC to submit or edit
issues.  

Documentation relating to the TRAC Issue Tracking database is available
here:

http://trac.tools.ietf.org/wg/martini/trac/wiki

Since this documentation is somewhat lengthy (and mostly relevant to
Admins), here is a pithy synopsis. 

1.       To submit an issue in the MARTINI Issues database (known as TRAC),
you first need to login to the MARTINI WG site on the tools server
(http://tools.ietf.org/wg/martini/trac/login ) 

2.       If you don't already have a login ID, you can obtain one by
navigating to this site:   http://trac.tools.ietf.org/newlogin

3.       Once you have obtained an account, you can log in by clicking on
the "login" entry at the top of the page.  Once you have logged in, you can
file an issue by navigating to the  ticket entry form:
<http://trac.tools.ietf.org/wg/martini/trac/newticket>
http://trac.tools.ietf.org/wg/martini/trac/newticket

4     When opening an issue: 

a.       The Type: field should be set to "defect" for an issue with the
current document text, or "enhancement" for a proposed addition of
functionality (such as an additional requirement). 

b.      The Priority: field is set based on the severity of the Issue.   For
example, editorial issues are typically "minor" or "trivial". 

c.       The Milestone: field should be set to milestone1 (useless, I know).


d.      The Component: field should be set to the document you are filing
the issue on.  In responding to the GIN Call for Adoption, "gin" is the
appropriate choice.

e.      The Version: field should be set to "1.0". 

f.        The Severity: field should be set to based on the status of the
document (e.g. "Candidate WG Document" in this case)

g.        The Keywords: and CC: fields can be left blank unless inspiration
seizes you. 

h.      The Assign To: field is generally filled in with the email address
of the editor. 

5.       Typically it won't be necessary to enclose a file with the ticket,
but if you need to, select "I have files to attach to this ticket". 

6.       If you want to preview your Issue, click on the "Preview" button.
When you're ready to submit the issue, click on the "Create Ticket" button. 

That's it!  

If you have an problems in dealing with TRAC, send email to me and I'll try
to figure out what's going on. 

Happy TRACing,

Bernard

 


------=_NextPart_000_0162_01CABC5D.82441200
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:navy;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>+1 as =
well.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>&nbsp;I totally =
concur. Hadriel ..I
know you can work with Adam on incorporating any issues you can have =
into Gin &nbsp;and
I certainly think you deserve significant recognition for all of your =
hard work
in shaken.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>We all owe Hadriel a =
Bombay Sapphire
Gin Martini in Anaheim.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <b>On Behalf =
Of </b>Hadriel
Kaplan<br>
<b>Sent:</b> Friday, March 05, 2010 11:11 AM<br>
<b>To:</b> Bernard Aboba; 'MARTINI'<br>
<b>Subject:</b> Re: [martini] Call for Adoption of &quot;Registration =
for
Multiple Phone Numbers in the SIP&quot;<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>I&#8217;m in favor of it &#8211; we need to move forward, =
and GIN is close
enough to Shaken that I think we might was well just go forward with GIN =
and
get this done.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>-hadriel<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <b>On Behalf =
Of </b>Bernard
Aboba<br>
<b>Sent:</b> Thursday, March 04, 2010 5:02 PM<br>
<b>To:</b> 'MARTINI'<br>
<b>Subject:</b> [martini] Call for Adoption of &quot;Registration for =
Multiple
Phone Numbers in the SIP&quot;</span><span =
style=3D'font-size:12.0pt;font-family:
"Times New Roman","serif"'><o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>This
is a MARTINI WG Call for Adoption of &#8220;Registration for Multiple =
Phone Numbers
in the SIP&#8221; as a MARTINI WG work item, corresponding to the =
&#8220;Multiple AoR
Registration specification&#8221; Charter deliverable. &nbsp;The =
document is
available for inspection here: <o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
href=3D"http://tools.ietf.org/html/draft-roach-martini-gin-01.txt">http:/=
/tools.ietf.org/html/draft-roach-martini-gin-01.txt</a><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The
MARTINI WG Call for Adoption will last until Friday, March 19, =
2010.<o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Please
respond to this WG Call for Adoption, whether you are in favor of =
adopting the
document as a MARTINI WG work item or not. &nbsp;If you have no =
comments,
please reply to this message and indicate in the body of your message =
whether
you think the document is ready for adoption as a MARTINI WG work item =
or not.
&nbsp;&nbsp;Based on the response, the MARTINI WG chairs will attempt to
determine whether WG consensus exists to adopt the document or not. =
<o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>If
you have comments, please provide them to the WG in one of the following =
ways: <o:p></o:p></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:21.0pt;text-indent:-.25in'><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The preferred choice is to open an issue in the MARTINI Issue tracking =
database
(TRAC), which is available here: <a
href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><span
style=3D'color:black'>http://trac.tools.ietf.org/wg/martini/trac/newticke=
t</span></a>
&nbsp;Information on how to use TRAC is provided below.&nbsp; Note that =
if you
submit an issue in TRAC, it will automatically also be posted to the =
MARTINI WG
mailing list. &nbsp;When submitting issues in TRAC for this &#8220;call =
for
adoption&#8221;, please enter &#8220;gin&#8221; for the Component: and =
&#8220;Candidate WG Document&#8221;
for Severity.&nbsp; <o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'color:black'>&nbsp;2. If you can&#8217;t figure out how to use =
TRAC, please
post your Issue to the MARTINI WG mailing list (martini at ietf.org) in =
the
following format: <o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'font-family:"Courier New"'>To:&nbsp; martini at =
ietf.org</span><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'font-family:"Courier New"'>Subject: GIN-Issue: &lt;title of =
your
issue&gt;</span><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'font-family:"Courier New"'>Priority: blocker, critical, major, =
minor or
trivial</span><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'font-family:"Courier New"'>&lt;Explanation of your issue, =
including a
proposal for specific text changes to resolve the =
issue&gt;</span><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'color:black'>The MARTINI WG uses the TRAC database to keep =
track of
issues relating to work in progress, including working group work items =
and
individual submissions undergoing review. &nbsp;&nbsp;&nbsp;This =
document
provides some basic information on how MARTINI WG participants can use =
TRAC to
submit or edit issues.&nbsp; </span><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Documentatio=
n
relating to the TRAC Issue Tracking database is available =
here:<o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
href=3D"http://trac.tools.ietf.org/wg/martini/trac/wiki">http://trac.tool=
s.ietf.org/wg/martini/trac/wiki</a><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Since
this documentation is somewhat lengthy (and mostly relevant to Admins), =
here is
a pithy synopsis. <o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>1.&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
To submit an issue in the MARTINI Issues database (known as TRAC), you =
first
need to login to the MARTINI WG site on the tools server (<a
href=3D"http://tools.ietf.org/wg/martini/trac/login">http://tools.ietf.or=
g/wg/martini/trac/login</a>
) <o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>2.&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
If you don&#8217;t already have a login ID, you can obtain one by =
navigating to this
site: &nbsp;&nbsp;<a =
href=3D"http://trac.tools.ietf.org/newlogin">http://trac.tools.ietf.org/n=
ewlogin</a><o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>3<span =
style=3D'color:black'>.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Once you have obtained an account, you can log in by clicking on the =
&#8220;login&#8221;
entry at the top of the page.&nbsp; Once you have logged in, you can =
file an
issue by navigating to the &nbsp;ticket entry form: <a
href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><span
style=3D'color:black'>http://trac.tools.ietf.org/wg/martini/trac/newticke=
t</span></a><o:p></o:p></span></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>4<span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;
</span>&nbsp;When opening an issue:&nbsp;<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>a.&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
The Type: field should be set to &#8220;defect&#8221; for an issue with =
the current
document text, or &#8220;enhancement&#8221; for a proposed addition of =
functionality (such
as an additional requirement). <o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>b.&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; The
Priority: field is set based on the severity of the Issue.&nbsp;&nbsp; =
For
example, editorial issues are typically &#8220;minor&#8221; or =
&#8220;trivial&#8221;. <o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>c<span =
style=3D'color:black'>.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The Milestone: field should be set to milestone1 (useless, I know). =
<o:p></o:p></span></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif";color:black'>d.&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
The Component: field should be set to the document you are filing the =
issue
on.&nbsp; In responding to the GIN Call for Adoption, &#8220;gin&#8221; =
is the appropriate
choice.<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif";color:black'>e.&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
The Version: field should be set to &#8220;1.0&#8221;. =
<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif";color:black'>f.&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;
The Severity: field should be set to based on the status of the document =
(e.g.
&#8220;Candidate WG Document&#8221; in this case)<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif";color:black'>g.&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
&nbsp;The Keywords: and CC: fields can be left blank unless inspiration =
seizes
you. <o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif";color:black'>h.&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
The Assign To: field is generally filled in with the email address of =
the
editor. <o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>5.&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
Typically it won&#8217;t be necessary to enclose a file with the ticket, =
but if you
need to, select &#8220;I have files to attach to this ticket&#8221;. =
<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>6.&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
If you want to preview your Issue, click on the &#8220;Preview&#8221; =
button.&nbsp; When
you&#8217;re ready to submit the issue, click on the &#8220;Create =
Ticket&#8221; button. <o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>That&#8217;s=

it!&nbsp; <span style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>If
you have an problems in dealing with TRAC, send email to me and =
I&#8217;ll try to
figure out what&#8217;s going on. <span =
style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Happy
TRACing,<span style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal>Bernard<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_0162_01CABC5D.82441200--


From victor.pascual.avila@gmail.com  Fri Mar  5 09:29:10 2010
Return-Path: <victor.pascual.avila@gmail.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 4F15D28C2D8 for <martini@core3.amsl.com>; Fri,  5 Mar 2010 09:29:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 DwUfVK-Bj-w9 for <martini@core3.amsl.com>; Fri,  5 Mar 2010 09:29:09 -0800 (PST)
Received: from mail-bw0-f222.google.com (mail-bw0-f222.google.com [209.85.218.222]) by core3.amsl.com (Postfix) with ESMTP id 9BDD63A8D81 for <martini@ietf.org>; Fri,  5 Mar 2010 09:29:08 -0800 (PST)
Received: by bwz22 with SMTP id 22so840698bwz.28 for <martini@ietf.org>; Fri, 05 Mar 2010 09:29:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Pj3+XJ7hPufwAwxacRs3A7Ajq3zCq3YZZUtOKI1NzcY=; b=RR/WBX7U2Srbq/Dg2Ht4qRA+JhVu0ALBUVUd6Rya/nWYKrdRolH5ZHPrTB+JWBoDr8 qVG6Vae+1YHisv0z+Gs5sK6ed2iencsIJwgK2SXzjwRiimNUj1MTGCwv7UHJrt6eWZz+ bfTq2rYoEs+nppU7Zfnph2oaapxuPqAGjmaQQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=KcksFQqO5Bbk53rUwLnbk0xZ1jHWV5LbizGOcoglE2HYplZSDe1Gd3jPGPYpNS76ep TdK5TQMhmv2+XDI2PKs6XqQEisKqBaO1AEgmj8mV69iRx6Rb3hi4ss2GH9zNqlYVChtF X9WvtF5TER7HqnsMc0q3q1hOS/cGIbRIlmkzk=
MIME-Version: 1.0
Received: by 10.204.30.212 with SMTP id v20mr338401bkc.99.1267810145405; Fri,  05 Mar 2010 09:29:05 -0800 (PST)
In-Reply-To: <016101cabc87$6b17a900$4146fb00$@us>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl> <430FC6BDED356B4C8498F634416644A91952C0BF2E@mail> <016101cabc87$6b17a900$4146fb00$@us>
Date: Fri, 5 Mar 2010 18:29:05 +0100
Message-ID: <618e24241003050929r6250cdd9u9c8c9a3fed0244dc@mail.gmail.com>
From: Victor Pascual Avila <victor.pascual.avila@gmail.com>
To: Richard Shockey <richard@shockey.us>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, MARTINI <martini@ietf.org>
Subject: Re: [martini] Call for Adoption of "Registration for Multiple Phone Numbers in the SIP"
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: Fri, 05 Mar 2010 17:29:10 -0000

+1

On Fri, Mar 5, 2010 at 6:15 PM, Richard Shockey <richard@shockey.us> wrote:
> +1 as well.
>
>
>
> =C2=A0I totally concur. Hadriel ..I know you can work with Adam on incorp=
orating
> any issues you can have into Gin =C2=A0and I certainly think you deserve
> significant recognition for all of your hard work in shaken.
>
>
>
> We all owe Hadriel a Bombay Sapphire Gin Martini in Anaheim.
>
>
>
> From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behal=
f
> Of Hadriel Kaplan
> Sent: Friday, March 05, 2010 11:11 AM
> To: Bernard Aboba; 'MARTINI'
> Subject: Re: [martini] Call for Adoption of "Registration for Multiple Ph=
one
> Numbers in the SIP"
>
>
>
> I=E2=80=99m in favor of it =E2=80=93 we need to move forward, and GIN is =
close enough to
> Shaken that I think we might was well just go forward with GIN and get th=
is
> done.
>
> -hadriel
>
>
>
> ________________________________
>
> From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behal=
f
> Of Bernard Aboba
> Sent: Thursday, March 04, 2010 5:02 PM
> To: 'MARTINI'
> Subject: [martini] Call for Adoption of "Registration for Multiple Phone
> Numbers in the SIP"
>
>
>
> This is a MARTINI WG Call for Adoption of =E2=80=9CRegistration for Multi=
ple Phone
> Numbers in the SIP=E2=80=9D as a MARTINI WG work item, corresponding to t=
he
> =E2=80=9CMultiple AoR Registration specification=E2=80=9D Charter deliver=
able. =C2=A0The document
> is available for inspection here:
>
> http://tools.ietf.org/html/draft-roach-martini-gin-01.txt
>
> The MARTINI WG Call for Adoption will last until Friday, March 19, 2010.
>
> Please respond to this WG Call for Adoption, whether you are in favor of
> adopting the document as a MARTINI WG work item or not. =C2=A0If you have=
 no
> comments, please reply to this message and indicate in the body of your
> message whether you think the document is ready for adoption as a MARTINI=
 WG
> work item or not. =C2=A0=C2=A0Based on the response, the MARTINI WG chair=
s will
> attempt to determine whether WG consensus exists to adopt the document or
> not.
>
> If you have comments, please provide them to the WG in one of the followi=
ng
> ways:
>
> 1.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The preferred choice is to open an issue=
 in the MARTINI Issue
> tracking database (TRAC), which is available here:
> http://trac.tools.ietf.org/wg/martini/trac/newticket =C2=A0Information on=
 how to
> use TRAC is provided below.=C2=A0 Note that if you submit an issue in TRA=
C, it
> will automatically also be posted to the MARTINI WG mailing list. =C2=A0W=
hen
> submitting issues in TRAC for this =E2=80=9Ccall for adoption=E2=80=9D, p=
lease enter =E2=80=9Cgin=E2=80=9D
> for the Component: and =E2=80=9CCandidate WG Document=E2=80=9D for Severi=
ty.
>
> =C2=A02. If you can=E2=80=99t figure out how to use TRAC, please post you=
r Issue to the
> MARTINI WG mailing list (martini at ietf.org) in the following format:
>
> To:=C2=A0 martini at ietf.org
>
> Subject: GIN-Issue: <title of your issue>
>
> Priority: blocker, critical, major, minor or trivial
>
> <Explanation of your issue, including a proposal for specific text change=
s
> to resolve the issue>
>
> The MARTINI WG uses the TRAC database to keep track of issues relating to
> work in progress, including working group work items and individual
> submissions undergoing review. =C2=A0=C2=A0=C2=A0This document provides s=
ome basic
> information on how MARTINI WG participants can use TRAC to submit or edit
> issues.
>
> Documentation relating to the TRAC Issue Tracking database is available
> here:
>
> http://trac.tools.ietf.org/wg/martini/trac/wiki
>
> Since this documentation is somewhat lengthy (and mostly relevant to
> Admins), here is a pithy synopsis.
>
> 1.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 To submit an issue in the MARTINI =
Issues database (known as TRAC),
> you first need to login to the MARTINI WG site on the tools server
> (http://tools.ietf.org/wg/martini/trac/login )
>
> 2.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 If you don=E2=80=99t already have =
a login ID, you can obtain one by
> navigating to this site: =C2=A0=C2=A0http://trac.tools.ietf.org/newlogin
>
> 3.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Once you have obtained an account,=
 you can log in by clicking on
> the =E2=80=9Clogin=E2=80=9D entry at the top of the page.=C2=A0 Once you =
have logged in, you can
> file an issue by navigating to the =C2=A0ticket entry form:
> http://trac.tools.ietf.org/wg/martini/trac/newticket
>
> 4=C2=A0=C2=A0=C2=A0 =C2=A0When opening an issue:
>
> a.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Type: field should be set to =
=E2=80=9Cdefect=E2=80=9D for an issue with the
> current document text, or =E2=80=9Cenhancement=E2=80=9D for a proposed ad=
dition of
> functionality (such as an additional requirement).
>
> b.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Priority: field is set based on the =
severity of the Issue.=C2=A0=C2=A0 For
> example, editorial issues are typically =E2=80=9Cminor=E2=80=9D or =E2=80=
=9Ctrivial=E2=80=9D.
>
> c.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Milestone: field should be set=
 to milestone1 (useless, I know).
>
> d.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Component: field should be set to th=
e document you are filing
> the issue on.=C2=A0 In responding to the GIN Call for Adoption, =E2=80=9C=
gin=E2=80=9D is the
> appropriate choice.
>
> e.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Version: field should be set to =E2=
=80=9C1.0=E2=80=9D.
>
> f.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Severity: field should b=
e set to based on the status of the
> document (e.g. =E2=80=9CCandidate WG Document=E2=80=9D in this case)
>
> g.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0The Keywords: and CC: fields=
 can be left blank unless inspiration
> seizes you.
>
> h.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Assign To: field is generally filled=
 in with the email address
> of the editor.
>
> 5.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Typically it won=E2=80=99t be nece=
ssary to enclose a file with the ticket,
> but if you need to, select =E2=80=9CI have files to attach to this ticket=
=E2=80=9D.
>
> 6.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 If you want to preview your Issue,=
 click on the =E2=80=9CPreview=E2=80=9D button.
> When you=E2=80=99re ready to submit the issue, click on the =E2=80=9CCrea=
te Ticket=E2=80=9D button.
>
> That=E2=80=99s it!
>
> If you have an problems in dealing with TRAC, send email to me and I=E2=
=80=99ll try
> to figure out what=E2=80=99s going on.
>
> Happy TRACing,
>
> Bernard
>
>
>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>
>



--=20
Victor Pascual =C3=81vila

From dean.willis@softarmor.com  Fri Mar  5 10:12:11 2010
Return-Path: <dean.willis@softarmor.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 3904E3A8D05 for <martini@core3.amsl.com>; Fri,  5 Mar 2010 10:12:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.558
X-Spam-Level: 
X-Spam-Status: No, score=-2.558 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 3DAcTveWoPpt for <martini@core3.amsl.com>; Fri,  5 Mar 2010 10:12:09 -0800 (PST)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 38E5E3A8B75 for <martini@ietf.org>; Fri,  5 Mar 2010 10:12:09 -0800 (PST)
Received: from [192.168.2.106] (cpe-66-25-30-183.tx.res.rr.com [66.25.30.183]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id o25IBc2X025222 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 5 Mar 2010 12:11:39 -0600
Message-Id: <AFB74521-1DBC-4750-AF59-F88B43352302@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE20C19E15F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-3--404799354
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 5 Mar 2010 12:11:32 -0600
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl> <EDC0A1AE77C57744B664A310A0B23AE20C19E15F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
X-Mailer: Apple Mail (2.936)
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, 'MARTINI' <martini@ietf.org>
Subject: Re: [martini] Call for Adoption of "Registration for Multiple Phone	Numbers in the SIP"
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: Fri, 05 Mar 2010 18:12:11 -0000

--Apple-Mail-3--404799354
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit


On Mar 4, 2010, at 5:13 PM, DRAGE, Keith (Keith) wrote:

> While you may be wanting to keep to the MARTINI timescales - I for  
> one am struggling to keep up with this.
>
> You have the WGLC for requirements in the middle of a major 3GPP  
> meeting (a draft I still need to review and comment on), and now you  
> are doing the adoption for GIN in the run up to the Anaheim, when I  
> know there are still issues to address here as well - as to whether  
> this even bears commonality for where we need to get to.
>
> So my view is NO, because it is too early. Doing this now ensures  
> that MARTINI goes a different way to the rest of the world and you  
> end up with yet another interdace to support.

It's true that we've been moving very quickly on this work. I'm  
astounded at the level of energy and enthusiasm expressed. This is  
exactly the sort of response I was hoping for when I pushed for  
smaller, task-focused, and short-lived working groups as opposed to  
the eternal lumbering behemoths of SIP and SIPPING.

Working on "Internet time" is at odds with the longer review/work  
cycle of other SDOs like 3GPP. This can make for some painful  
adjustments and rethinking of the way we do things. I'm sorry that  
this is making it hard for some of our folks who are concurrently  
working in multiple organizational temporalities. But I think it is  
absolutely critical that we keep our momentum going and not slip back  
into a trimester hibernation cycle. Hibernation might be great for  
ground hogs, but it doesn't lead to particularly good weather  
forecasting or the rapid development of community consensus.

I'd also like to point out that adoption of a draft is not conclusion  
of the work; we still expect to see a large amount of review, and may  
see some substantive changes,  That is, after all, the IETF's work  
process.

On the comment of "yet another interface to support": The goal of  
doing MARTINI registration as I understand it has been merely to clean  
up and standardize an existing broadly (but diversely) deployed  
interface. It's not the final answer to the problem, and I think it's  
OK that IMS has a slightly different answer to a slightly different  
problem. I fully expect to go on from here towards solving the more  
general dynamic route-binding problem (another fact of which we are  
currently seeing in DISPATCH).

So at this time, I'd like to endorse the adoption of "gin" as a  
standardized component of the proper MARTINI. I'll leave it to Hadriel  
and Adam to lead the conversation as to whether we want our gin  
shaken, stirred, or possibly blended into the final confection. And  
hopefully Keith can look up from his 3GPP work long enough to partake  
of a few SIPs along the way.

--
Dean


--Apple-Mail-3--404799354
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On Mar 4, 2010, =
at 5:13 PM, DRAGE, Keith (Keith) wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div lang=3D"EN-US" =
vlink=3D"purple" link=3D"blue"><div dir=3D"ltr" align=3D"left"><span =
class=3D"771440923-04032010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">While you may be wanting to keep to the MARTINI timescales - =
I for one am struggling to keep up with this.</font></span></div><div =
dir=3D"ltr" align=3D"left"><span class=3D"771440923-04032010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div=
 dir=3D"ltr" align=3D"left"><span class=3D"771440923-04032010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">You have the WGLC for =
requirements in the middle of a major 3GPP meeting (a draft I still need =
to review and comment on), and now you are doing the adoption for GIN in =
the run up to the Anaheim, when I know there are still issues to address =
here as well - as to whether this even bears commonality for where we =
need to get to.</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"771440923-04032010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"771440923-04032010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">So my view is NO, because it is too early. Doing this now =
ensures that MARTINI goes a different way to the rest of the world and =
you end up with yet another interdace to =
support.</font></span></div></div></span></blockquote></div><br><div>It's =
true that we've been moving very quickly on this work. I'm astounded at =
the level of energy and enthusiasm expressed. This is exactly the sort =
of response I was hoping for when I pushed for smaller, task-focused, =
and short-lived working groups as opposed to the eternal lumbering =
behemoths of SIP and SIPPING.</div><div><br></div><div>Working on =
"Internet time" is at odds with the longer review/work cycle of other =
SDOs like 3GPP. This can make for some painful adjustments and =
rethinking of the way we do things. I'm sorry that this is making it =
hard for some of our folks who are concurrently working in multiple =
organizational temporalities. But I think it is absolutely critical that =
we keep our momentum going and not slip back into a trimester =
hibernation cycle. Hibernation might be great for ground hogs, but it =
doesn't lead to particularly good weather forecasting or the rapid =
development of community consensus.</div><div><br></div><div>I'd also =
like to point out that adoption of a draft is not conclusion of the =
work; we still expect to see a large amount of review, and may see some =
substantive changes, &nbsp;That is, after all, the IETF's work =
process.</div><div><br></div><div>On the comment of "yet another =
interface to support": The goal of doing MARTINI registration as I =
understand it has been merely to clean up and standardize an existing =
broadly (but diversely) deployed interface. It's not the final answer to =
the problem, and I think it's OK that IMS has a slightly different =
answer to a slightly different problem. I fully expect to go on from =
here towards solving the more general dynamic route-binding problem =
(another fact of which we are currently seeing in =
DISPATCH).</div><div><br></div><div>So at this time, I'd like to endorse =
the adoption of "gin" as a standardized component of the proper MARTINI. =
I'll leave it to Hadriel and Adam to lead the conversation as to whether =
we want our gin shaken, stirred, or possibly blended into the final =
confection. And hopefully Keith can look up from his 3GPP work long =
enough to partake of a few SIPs along the =
way.</div><div><br></div><div>--</div><div>Dean</div><div><br></div></body=
></html>=

--Apple-Mail-3--404799354--

From jsburton@cablevision.com  Sat Mar  6 13:14:34 2010
Return-Path: <jsburton@cablevision.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 9B8973A8BBF for <martini@core3.amsl.com>; Sat,  6 Mar 2010 13:14:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.938
X-Spam-Level: *
X-Spam-Status: No, score=1.938 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, J_CHICKENPOX_31=0.6, J_CHICKENPOX_32=0.6, J_CHICKENPOX_41=0.6]
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 wjeFdxJKSgfZ for <martini@core3.amsl.com>; Sat,  6 Mar 2010 13:14:33 -0800 (PST)
Received: from cscpsmout01.cablevision.com (cscpsmout01.cablevision.com [167.206.119.144]) by core3.amsl.com (Postfix) with ESMTP id BFE153A8982 for <martini@ietf.org>; Sat,  6 Mar 2010 13:14:31 -0800 (PST)
Received: from c3gwiaoutvs.cablevision.com (c3gwiaoutvs.cablevision.com [10.128.36.189]) by cscpsmout01.cablevision.com (Sentrion-MTA-4.0.2/Sentrion-MTA-4.0.2) with ESMTP id o26LEYCL026153 for <martini@ietf.org>; Sat, 6 Mar 2010 16:14:34 -0500
X-DKIM: Sendmail DKIM Filter v2.5.6 cscpsmout01.cablevision.com o26LEYCL026153
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cablevision.com; s=cscprod; t=1267910074; bh=q6njXlChsUOOwd0CDshR56bBxSdUVG/0UDfocUA Vqq4=; h=Message-Id:Date:From:To:Subject:References:In-Reply-To: Mime-Version:Content-Type; b=ap8JzmIZ1GRa2mwqd2Pu+vMB3eCQu4R3EolGT T30SzaLu9O4L1X1Rl8bwuw0DYZ8VnRKWoP5m/ZfInFiwyFeQb/iBM2D8daZYPukTIKR ZcuAY1Ok5khpMAxmBXB06swAa6ouj+oYK8vaJRwPLw8rwbzshZbGHbcgfTkW6swSXLM =
Received: from C3GWIAOUTDOM-MTA by c3gwiaoutvs.cablevision.com with Novell_GroupWise; Sat, 06 Mar 2010 16:14:34 -0500
Message-Id: <4B927F66.6D98.00CB.0@cablevision.com>
X-Mailer: Novell GroupWise Internet Agent 7.0.3 
Date: Sat, 06 Mar 2010 16:14:23 -0500
From: "Jack Burton" <jsburton@cablevision.com>
To: <martini@ietf.org>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
In-Reply-To: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartCBE11FBF.0__="
X-Auth-Type: Internal IP
Subject: Re: [martini] Call for Adoption of "Registration for Multiple	PhoneNumbers in the SIP"
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: Sat, 06 Mar 2010 21:14:34 -0000

--=__PartCBE11FBF.0__=
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

In Favor.
 
-Jack
 
 
Jack Burton
Dir. Systems Engineering
Cablevision
jsburton@cablevision.com 
516-803-9733 

>>> "Bernard Aboba" <bernard_aboba@hotmail.com> 3/4/2010 17:02 >>>

This is a MARTINI WG Call for Adoption of *Registration for Multiple
Phone Numbers in the SIP* as a MARTINI WG work item, corresponding to
the *Multiple AoR Registration specification* Charter deliverable.  The
document is available for inspection here: 
http://tools.ietf.org/html/draft-roach-martini-gin-01.txt 
The MARTINI WG Call for Adoption will last until Friday, March 19,
2010.
Please respond to this WG Call for Adoption, whether you are in favor
of adopting the document as a MARTINI WG work item or not.  If you have
no comments, please reply to this message and indicate in the body of
your message whether you think the document is ready for adoption as a
MARTINI WG work item or not.   Based on the response, the MARTINI WG
chairs will attempt to determine whether WG consensus exists to adopt
the document or not. 
If you have comments, please provide them to the WG in one of the
following ways: 
1.      The preferred choice is to open an issue in the MARTINI Issue
tracking database (TRAC), which is available here:
http://trac.tools.ietf.org/wg/martini/trac/newticket  Information on
how to use TRAC is provided below.  Note that if you submit an issue in
TRAC, it will automatically also be posted to the MARTINI WG mailing
list.  When submitting issues in TRAC for this *call for adoption*,
please enter *gin* for the Component: and *Candidate WG Document* for
Severity.  
 2. If you can*t figure out how to use TRAC, please post your Issue to
the MARTINI WG mailing list (martini at ietf.org) in the following
format: 
To:  martini at ietf.org
Subject: GIN-Issue: <title of your issue>
Priority: blocker, critical, major, minor or trivial
<Explanation of your issue, including a proposal for specific text
changes to resolve the issue>
The MARTINI WG uses the TRAC database to keep track of issues relating
to work in progress, including working group work items and individual
submissions undergoing review.    This document provides some basic
information on how MARTINI WG participants can use TRAC to submit or
edit issues.  
Documentation relating to the TRAC Issue Tracking database is available
here:
http://trac.tools.ietf.org/wg/martini/trac/wiki 
Since this documentation is somewhat lengthy (and mostly relevant to
Admins), here is a pithy synopsis. 
1.       To submit an issue in the MARTINI Issues database (known as
TRAC), you first need to login to the MARTINI WG site on the tools
server (http://tools.ietf.org/wg/martini/trac/login ) 
2.       If you don*t already have a login ID, you can obtain one by
navigating to this site:   http://trac.tools.ietf.org/newlogin 
3.       Once you have obtained an account, you can log in by clicking
on the *login* entry at the top of the page.  Once you have logged in,
you can file an issue by navigating to the  ticket entry form:
http://trac.tools.ietf.org/wg/martini/trac/newticket
4     When opening an issue: 
a.       The Type: field should be set to *defect* for an issue with
the current document text, or *enhancement* for a proposed addition of
functionality (such as an additional requirement). 
b.      The Priority: field is set based on the severity of the Issue. 
 For example, editorial issues are typically *minor* or *trivial*. 
c.       The Milestone: field should be set to milestone1 (useless, I
know). 
d.      The Component: field should be set to the document you are
filing the issue on.  In responding to the GIN Call for Adoption, *gin*
is the appropriate choice.
e.      The Version: field should be set to *1.0*. 
f.        The Severity: field should be set to based on the status of
the document (e.g. *Candidate WG Document* in this case)
g.        The Keywords: and CC: fields can be left blank unless
inspiration seizes you. 
h.      The Assign To: field is generally filled in with the email
address of the editor. 
5.       Typically it won*t be necessary to enclose a file with the
ticket, but if you need to, select *I have files to attach to this
ticket*. 
6.       If you want to preview your Issue, click on the *Preview*
button.  When you*re ready to submit the issue, click on the *Create
Ticket* button. 
That*s it!  
If you have an problems in dealing with TRAC, send email to me and I*ll
try to figure out what*s going on. 
Happy TRACing,
Bernard
 

-------------------------------------------------------- 
The information transmitted in this email and any of its attachments is intended only for the person or entity to which it is addressed and may contain information concerning Cablevision and/or its affiliates and subsidiaries that is proprietary, privileged, confidential and/or subject to copyright.   Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited and may be unlawful.  If you received this in error, please contact the sender immediately and delete and destroy the communication and all of the attachments you have received and all copies thereof.
--------------------------------------------------------
--=__PartCBE11FBF.0__=
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Content-Description: HTML

<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v = "urn:schemas-microsoft-com:vml" xmlns:o = "urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word" xmlns:m = "http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
<META content="MSHTML 6.00.6000.16981" name=GENERATOR>
<STYLE>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=EN-US style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma" vLink=purple link=blue>
<DIV>In Favor.</DIV>
<DIV>&nbsp;</DIV>
<DIV>-Jack</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Tahoma color=#000080 size=2>Jack Burton<BR>Dir. Systems Engineering<BR>Cablevision<BR>jsburton@cablevision.com<BR>516-803-9733</FONT> <BR><BR>&gt;&gt;&gt; "Bernard Aboba" &lt;bernard_aboba@hotmail.com&gt; 3/4/2010 17:02 &gt;&gt;&gt;<BR></DIV>
<DIV class=Section1>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">This is a MARTINI WG Call for Adoption of "Registration for Multiple Phone Numbers in the SIP" as a MARTINI WG work item, corresponding to the "Multiple AoR Registration specification" Charter deliverable. &nbsp;The document is available for inspection here: <o:p></o:p></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><A href="http://tools.ietf.org/html/draft-roach-martini-gin-01.txt">http://tools.ietf.org/html/draft-roach-martini-gin-01.txt</A><o:p></o:p></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">The MARTINI WG Call for Adoption will last until Friday, March 19, 2010.<o:p></o:p></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Please respond to this WG Call for Adoption, whether you are in favor of adopting the document as a MARTINI WG work item or not. &nbsp;If you have no comments, please reply to this message and indicate in the body of your message whether you think the document is ready for adoption as a MARTINI WG work item or not. &nbsp;&nbsp;Based on the response, the MARTINI WG chairs will attempt to determine whether WG consensus exists to adopt the document or not. <o:p></o:p></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">If you have comments, please provide them to the WG in one of the following ways: <o:p></o:p></P>
<P class=MsoListParagraph style="MARGIN-LEFT: 21pt; TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The preferred choice is to open an issue in the MARTINI Issue tracking database (TRAC), which is available here: <A href="http://trac.tools.ietf.org/wg/martini/trac/newticket"><SPAN style="COLOR: black">http://trac.tools.ietf.org/wg/martini/trac/newticket</SPAN></A> &nbsp;Information on how to use TRAC is provided below.&nbsp; Note that if you submit an issue in TRAC, it will automatically also be posted to the MARTINI WG mailing list. &nbsp;When submitting issues in TRAC for this "call for adoption", please enter "gin" for the Component: and "Candidate WG Document" for Severity.&nbsp; <o:p></o:p></SPAN></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN style="COLOR: black">&nbsp;2. If you can't figure out how to use TRAC, please post your Issue to the MARTINI WG mailing list (martini at ietf.org) in the following format: <o:p></o:p></SPAN></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN style="FONT-FAMILY: 'Courier New'">To:&nbsp; martini at ietf.org</SPAN><o:p></o:p></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN style="FONT-FAMILY: 'Courier New'">Subject: GIN-Issue: &lt;title of your issue&gt;</SPAN><o:p></o:p></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN style="FONT-FAMILY: 'Courier New'">Priority: blocker, critical, major, minor or trivial</SPAN><o:p></o:p></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN style="FONT-FAMILY: 'Courier New'">&lt;Explanation of your issue, including a proposal for specific text changes to resolve the issue&gt;</SPAN><o:p></o:p></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN style="COLOR: black">The MARTINI WG uses the TRAC database to keep track of issues relating to work in progress, including working group work items and individual submissions undergoing review. &nbsp;&nbsp;&nbsp;This document provides some basic information on how MARTINI WG participants can use TRAC to submit or edit issues.&nbsp; </SPAN><o:p></o:p></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Documentation relating to the TRAC Issue Tracking database is available here:<o:p></o:p></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><A href="http://trac.tools.ietf.org/wg/martini/trac/wiki">http://trac.tools.ietf.org/wg/martini/trac/wiki</A><o:p></o:p></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Since this documentation is somewhat lengthy (and mostly relevant to Admins), here is a pithy synopsis. <o:p></o:p></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To submit an issue in the MARTINI Issues database (known as TRAC), you first need to login to the MARTINI WG site on the tools server (<A href="http://tools.ietf.org/wg/martini/trac/login">http://tools.ietf.org/wg/martini/trac/login</A> ) <o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If you don't already have a login ID, you can obtain one by navigating to this site: &nbsp;&nbsp;<A href="http://trac.tools.ietf.org/newlogin">http://trac.tools.ietf.org/newlogin</A><o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">3<SPAN style="COLOR: black">.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Once you have obtained an account, you can log in by clicking on the "login" entry at the top of the page.&nbsp; Once you have logged in, you can file an issue by navigating to the &nbsp;ticket entry form: <A href="http://trac.tools.ietf.org/wg/martini/trac/newticket"><SPAN style="COLOR: black">http://trac.tools.ietf.org/wg/martini/trac/newticket</SPAN></A><o:p></o:p></SPAN></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">4<SPAN style="COLOR: #1f497d">&nbsp;&nbsp;&nbsp; </SPAN>&nbsp;When opening an issue:&nbsp;<o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">a.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Type: field should be set to "defect" for an issue with the current document text, or "enhancement" for a proposed addition of functionality (such as an additional requirement). <o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">b.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Priority: field is set based on the severity of the Issue.&nbsp;&nbsp; For example, editorial issues are typically "minor" or "trivial". <o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">c<SPAN style="COLOR: black">.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Milestone: field should be set to milestone1 (useless, I know). <o:p></o:p></SPAN></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">d.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Component: field should be set to the document you are filing the issue on.&nbsp; In responding to the GIN Call for Adoption, "gin" is the appropriate choice.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">e.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Version: field should be set to "1.0". <o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">f.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Severity: field should be set to based on the status of the document (e.g. "Candidate WG Document" in this case)<o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">g.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;The Keywords: and CC: fields can be left blank unless inspiration seizes you. <o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">h.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Assign To: field is generally filled in with the email address of the editor. <o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">5.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Typically it won't be necessary to enclose a file with the ticket, but if you need to, select "I have files to attach to this ticket". <o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">6.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If you want to preview your Issue, click on the "Preview" button.&nbsp; When you're ready to submit the issue, click on the "Create Ticket" button. <o:p></o:p></SPAN></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">That's it!&nbsp; <SPAN style="COLOR: #1f497d"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">If you have an problems in dealing with TRAC, send email to me and I'll try to figure out what's going on. <SPAN style="COLOR: #1f497d"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Happy TRACing,<SPAN style="COLOR: #1f497d"><o:p></o:p></SPAN></P>
<P class=MsoNormal>Bernard<o:p></o:p></P>
<P class=MsoNormal><o:p>&nbsp;</o:p></P></DIV></BODY></HTML>
<br>
-------------------------------------------------------- <br>
The information transmitted in this email and any of its attachments is intended only for the person or entity to which it is addressed and may contain information concerning Cablevision and/or its affiliates and subsidiaries that is proprietary, privileged, confidential and/or subject to copyright.   Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited and may be unlawful.  If you received this in error, please contact the sender immediately and delete and destroy the communication and all of the attachments you have received and all copies thereof.<br>
--------------------------------------------------------
--=__PartCBE11FBF.0__=--

From bernard_aboba@hotmail.com  Sat Mar  6 19:35:58 2010
Return-Path: <bernard_aboba@hotmail.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 C8A8E28B797 for <martini@core3.amsl.com>; Sat,  6 Mar 2010 19:35:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.758
X-Spam-Level: 
X-Spam-Status: No, score=-0.758 tagged_above=-999 required=5 tests=[AWL=-0.574, BAYES_40=-0.185, HTML_MESSAGE=0.001]
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 c5c-p-UNl8rJ for <martini@core3.amsl.com>; Sat,  6 Mar 2010 19:35:54 -0800 (PST)
Received: from blu0-omc2-s36.blu0.hotmail.com (blu0-omc2-s36.blu0.hotmail.com [65.55.111.111]) by core3.amsl.com (Postfix) with ESMTP id 7ABCA3A887E for <martini@ietf.org>; Sat,  6 Mar 2010 19:35:54 -0800 (PST)
Received: from BLU137-DS4 ([65.55.111.73]) by blu0-omc2-s36.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Sat, 6 Mar 2010 19:35:57 -0800
X-Originating-IP: [72.11.69.66]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS423A4ED594DFDFD1147FE93360@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <martini@ietf.org>
Date: Sat, 6 Mar 2010 19:35:56 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000C_01CABD64.3E086FC0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acq76z3zccNfIv1mQ0mEgm4UBsJpVABu0HPA
Content-Language: en-us
X-OriginalArrivalTime: 07 Mar 2010 03:35:57.0683 (UTC) FILETIME=[4CA94430:01CABDA7]
Subject: [martini] IETF 77  Agenda - Take Two
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: Sun, 07 Mar 2010 03:35:59 -0000

------=_NextPart_000_000C_01CABD64.3E086FC0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

MARTINI WG Meeting Slot I

Monday, March 22, 2010

1 PM - 3 PM Pacific Time

Palos Verdes Room

 

Jabber room:  martini at jabber.ietf.org (Please join)

 

Agenda

 

1 PM - 1:10 PM:  Preliminaries

     Blue Sheets

     Note Takers

     Note Well

     Agenda bash

     Document Status

 

Requirements (40 minutes)

 

1:10 PM - 1:50 PM, MARTINI Requirements, John Elwell (40 minutes)

http://tools.ietf.org/html/draft-elwell-martini-reqs

 

Solution Updates (30 minutes)

 

1:50 PM - 2:20 PM, MARTINI with Globally Identifiable Numbers, Adam Roach
(30 minutes)

http://tools.ietf.org/html/draft-roach-martini-gin

 

Discussion (20 minutes)

 

2:20 PM - 2:40 PM Discussion:  Participants (30 minutes)

 

Wrap-up (20 minutes)

 

2:40 PM - 2:50 PM  Hums:  WG Chairs (10 minutes)

2:50 PM - 3:00 PM  Next Steps:  WG Chairs & ADs (10 minutes)

 

MARTINI WG Meeting Slot II

Friday, March 26, 2010

1415 - 1515 Pacific Time

California D

 

Nothing scheduled at the moment (will cancel if time slot is not needed)


------=_NextPart_000_000C_01CABD64.3E086FC0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>MARTINI WG Meeting Slot I<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>Monday, March 22, 2010<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>1 PM &#8211; 3 PM Pacific Time<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>Palos Verdes Room<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>Jabber room:&nbsp; martini at jabber.ietf.org (Please =
join)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>Agenda<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>1 PM &#8211; 1:10 PM:&nbsp; =
Preliminaries<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;&nbsp;&nbsp;&nbsp; Blue Sheets<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;&nbsp;&nbsp;&nbsp; Note Takers<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;&nbsp;&nbsp;&nbsp; Note Well<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;&nbsp;&nbsp;&nbsp; Agenda bash<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;&nbsp;&nbsp;&nbsp; Document =
Status<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>Requirements (40 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>1:10 PM &#8211; 1:50 PM, MARTINI Requirements, John Elwell =
(</span><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:#1F497D'>4</span><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>0 =
minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>http://tools.ietf.org/html/draft-elwell-martini-reqs<o:p></o=
:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>Solution Updates (30 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>1:50 PM &#8211; 2:20 PM, MARTINI with Globally Identifiable
Numbers, Adam Roach (30 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>http://tools.ietf.org/html/draft-roach-martini-gin<o:p></o:p=
></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>Discussion (20 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>2:20 PM &#8211; 2:40 PM Discussion:&nbsp; Participants (30
minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>Wrap-up (20 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>2:40 PM &#8211; 2:50 PM&nbsp; Hums:&nbsp; WG Chairs (10 =
minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>2:50 PM &#8211; 3:00 PM &nbsp;Next Steps:&nbsp; WG Chairs =
&amp;
ADs (10 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>MARTINI WG Meeting Slot II<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>Friday, March 26, 2010<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>1415 - 1515 Pacific Time<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>California D<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:black'>Nothing scheduled at the moment (will cancel if time slot =
is not
needed)</span><span style=3D'color:black'><o:p></o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_000C_01CABD64.3E086FC0--

From trac@tools.ietf.org  Mon Mar  8 00:22:12 2010
Return-Path: <trac@tools.ietf.org>
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 A9A4F3A67A8 for <martini@core3.amsl.com>; Mon,  8 Mar 2010 00:22:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.441
X-Spam-Level: 
X-Spam-Status: No, score=-102.441 tagged_above=-999 required=5 tests=[AWL=0.159, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 i0zRj0g-jsgA for <martini@core3.amsl.com>; Mon,  8 Mar 2010 00:22:11 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id B46543A6781 for <martini@ietf.org>; Mon,  8 Mar 2010 00:22:11 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NoYEB-0003hE-FH; Mon, 08 Mar 2010 00:22:15 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Mon, 08 Mar 2010 08:22:15 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/6#comment:2
Message-ID: <083.ecefb3f14f5fbde8428a484765ed0491@tools.ietf.org>
References: <074.00f38bdd51aa79f0265b2a39a5ed89f0@tools.ietf.org>
X-Trac-Ticket-ID: 6
In-Reply-To: <074.00f38bdd51aa79f0265b2a39a5ed89f0@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #6: AORs other than telephone numbers
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 08 Mar 2010 08:22:12 -0000

#6: AORs other than telephone numbers
----------------------------------------------+-----------------------------
 Reporter:  bruno.chatras@…                   |        Owner:  john.elwell@…                     
     Type:  defect                            |       Status:  closed                            
 Priority:  critical                          |    Milestone:  milestone1                        
Component:  reqs                              |      Version:  1.0                               
 Severity:  In WG Last Call                   |   Resolution:  wontfix                           
 Keywords:                                    |  
----------------------------------------------+-----------------------------
Changes (by john.elwell@…):

  * status:  assigned => closed
  * resolution:  => wontfix


Comment:

 I have not seen any support for this (other than from the originator) and
 a couple of people spoke against it. Therefore I am closing it as 'won't
 fix'. However, the following text is added to section 1: "AORs based on
 E.164 numbers represent an overwhelming proportion of the current market
 for small/medium SIP-PBXs, and it is for sector that an urgent solution is
 required. This does not preclude future work on solutions for AORs that
 are not based on numbers or are based on non-E.164 numbers (private
 numbers)."

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/6#comment:2>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Mon Mar  8 00:30:23 2010
Return-Path: <trac@tools.ietf.org>
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 29E9C3A67E7 for <martini@core3.amsl.com>; Mon,  8 Mar 2010 00:30:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.451
X-Spam-Level: 
X-Spam-Status: No, score=-102.451 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 Zvk9Uytv6wVI for <martini@core3.amsl.com>; Mon,  8 Mar 2010 00:30:18 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id F11043A67EF for <martini@ietf.org>; Mon,  8 Mar 2010 00:30:17 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NoYM1-0002iR-7s; Mon, 08 Mar 2010 00:30:21 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Mon, 08 Mar 2010 08:30:21 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/3#comment:2
Message-ID: <085.13e523860cd79dabbe012427633dc170@tools.ietf.org>
References: <076.528e2a835ae2d9054533d1ea46b03e16@tools.ietf.org>
X-Trac-Ticket-ID: 3
In-Reply-To: <076.528e2a835ae2d9054533d1ea46b03e16@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #3: Requirement for identity assertions
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 08 Mar 2010 08:30:28 -0000

#3: Requirement for identity assertions
------------------------------------------------+---------------------------
 Reporter:  john.elwell@…                       |        Owner:  john.elwell@…                     
     Type:  enhancement                         |       Status:  closed                            
 Priority:  major                               |    Milestone:  milestone1                        
Component:  reqs                                |      Version:  1.0                               
 Severity:  In WG Last Call                     |   Resolution:  wontfix                           
 Keywords:                                      |  
------------------------------------------------+---------------------------
Changes (by john.elwell@…):

  * status:  new => closed
  * resolution:  => wontfix


Comment:

 I saw no responses to this question that favoured making any changes. I
 will therefore close the issue without making any change.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/3#comment:2>
martini <http://tools.ietf.org/martini/>


From root@core3.amsl.com  Mon Mar  8 01:00:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: martini@ietf.org
Delivered-To: martini@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 886863A67A8; Mon,  8 Mar 2010 01:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100308090001.886863A67A8@core3.amsl.com>
Date: Mon,  8 Mar 2010 01:00:01 -0800 (PST)
Cc: martini@ietf.org
Subject: [martini] I-D Action:draft-ietf-martini-reqs-02.txt
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, 08 Mar 2010 09:00:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiple AoR reachabiliTy InformatioN Indication Working Group of the IETF.


	Title           : Requirements for multiple address of record (AOR) reachability information in the Session Initiation Protocol (SIP)
	Author(s)       : J. Elwell, H. Kaplan
	Filename        : draft-ietf-martini-reqs-02.txt
	Pages           : 12
	Date            : 2010-03-08

This document states requirements for a standardized SIP registration
mechanism for multiple addresses of record, the mechanism being
suitable for deployment by SIP service providers on a large scale in
support of small to medium sized PBXs.  The requirements are for a
solution that can, as a minimum, support AORs based on E.164 numbers.

This work is being discussed on the martini@ietf.org mailing list.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-martini-reqs-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-martini-reqs-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-03-08004757.I-D@ietf.org>


--NextPart--

From john.elwell@siemens-enterprise.com  Mon Mar  8 03:29:55 2010
Return-Path: <john.elwell@siemens-enterprise.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 9BA353A6917 for <martini@core3.amsl.com>; Mon,  8 Mar 2010 03:29:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.385
X-Spam-Level: 
X-Spam-Status: No, score=-2.385 tagged_above=-999 required=5 tests=[AWL=-0.013, BAYES_00=-2.599, 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 wAuvmlJgetRM for <martini@core3.amsl.com>; Mon,  8 Mar 2010 03:29:54 -0800 (PST)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 5D2F43A68C1 for <martini@ietf.org>; Mon,  8 Mar 2010 03:29:54 -0800 (PST)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1127070 for martini@ietf.org; Mon, 8 Mar 2010 12:29:57 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id E8FA523F0278 for <martini@ietf.org>; Mon,  8 Mar 2010 12:29:57 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.57]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 8 Mar 2010 12:29:58 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "martini@ietf.org" <martini@ietf.org>
Date: Mon, 8 Mar 2010 12:29:56 +0100
Thread-Topic: draft-ietf-martini-reqs-02 available
Thread-Index: Acq+sq3KLqjGy64hScKVpiJIvGy0kw==
Message-ID: <A444A0F8084434499206E78C106220CABBC49F24@MCHP058A.global-ad.net>
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
Subject: [martini] draft-ietf-martini-reqs-02 available
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, 08 Mar 2010 11:29:55 -0000

http://www.ietf.org/id/draft-ietf-martini-reqs-02.txt

Although no announcement has appeared yet, 02 is now available. I have atte=
mpted to address all issues raised before or during WGLC (see closed issues=
 in tracker). The particular changes from 01 are:
- Addition of text at end of section 1 concerning AORs not based on E.164 n=
umbers.
- Addition of reference to 3GPP TS 23.003
- Some text changes in 3.3.1 and 3.3.2 for clarification.
- A small number of editorial changes.

John=

From bruno.chatras@orange-ftgroup.com  Tue Mar  9 01:11:12 2010
Return-Path: <bruno.chatras@orange-ftgroup.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 AFB033A67B2 for <martini@core3.amsl.com>; Tue,  9 Mar 2010 01:11:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.247
X-Spam-Level: 
X-Spam-Status: No, score=-2.247 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001]
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 mtOZu7zU-aOf for <martini@core3.amsl.com>; Tue,  9 Mar 2010 01:11:10 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by core3.amsl.com (Postfix) with ESMTP id 7E19B3A6781 for <martini@ietf.org>; Tue,  9 Mar 2010 01:11:08 -0800 (PST)
Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda14.si.francetelecom.fr (ESMTP service) with ESMTP id 586592AD388; Tue,  9 Mar 2010 10:11:11 +0100 (CET)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id CFF5A15807F; Tue,  9 Mar 2010 10:11:10 +0100 (CET)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 9 Mar 2010 10:09:30 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CABF68.39FF7083"
Date: Tue, 9 Mar 2010 10:08:46 +0100
Message-ID: <951_1268125870_4B9610AE_951_114651_3_9ECCF01B52E7AB408A7EB85352642141012FD45D@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <AFB74521-1DBC-4750-AF59-F88B43352302@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] Call for Adoption of "Registration for MultiplePhone	Numbers in the SIP"
Thread-Index: Acq8j2O+TPHRRmshSh+XU9dlDat8cgCDusig
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl><EDC0A1AE77C57744B664A310A0B23AE20C19E15F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AFB74521-1DBC-4750-AF59-F88B43352302@softarmor.com>
From: <bruno.chatras@orange-ftgroup.com>
To: <dean.willis@softarmor.com>, <keith.drage@alcatel-lucent.com>
X-OriginalArrivalTime: 09 Mar 2010 09:09:30.0917 (UTC) FILETIME=[3A4DED50:01CABF68]
X-PMX-Version: 5.5.7.378829, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.3.9.82126
Cc: bernard_aboba@hotmail.com, martini@ietf.org
Subject: Re: [martini] Call for Adoption of "Registration for MultiplePhone	Numbers in the SIP"
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, 09 Mar 2010 09:11:12 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CABF68.39FF7083
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

=20


________________________________

	De : martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] De la part=
 de Dean Willis
	Envoy=E9 : vendredi 5 mars 2010 19:12
	=C0 : DRAGE, Keith (Keith)
	Cc : Bernard Aboba; 'MARTINI'
	Objet : Re: [martini] Call for Adoption of "Registration for MultiplePhone=
 Numbers in the SIP"
=09
=09

	On Mar 4, 2010, at 5:13 PM, DRAGE, Keith (Keith) wrote:


=09=09
		While you may be wanting to keep to the MARTINI timescales - I for one am=
 struggling to keep up with this.
=09=09=20
		You have the WGLC for requirements in the middle of a major 3GPP meeting =
(a draft I still need to review and comment on), and now you are doing the =
adoption for GIN in the run up to the Anaheim, when I know there are still =
issues to address here as well - as to whether this even bears commonality =
for where we need to get to.
=09=09=20
		So my view is NO, because it is too early. Doing this now ensures that MA=
RTINI goes a different way to the rest of the world and you end up with yet=
 another interdace to support.


	It's true that we've been moving very quickly on this work. I'm astounded =
at the level of energy and enthusiasm expressed. This is exactly the sort o=
f response I was hoping for when I pushed for smaller, task-focused, and sh=
ort-lived working groups as opposed to the eternal lumbering behemoths of S=
IP and SIPPING.

	Working on "Internet time" is at odds with the longer review/work cycle of=
 other SDOs like 3GPP. This can make for some painful adjustments and rethi=
nking of the way we do things. I'm sorry that this is making it hard for so=
me of our folks who are concurrently working in multiple organizational tem=
poralities. But I think it is absolutely critical that we keep our momentum=
 going and not slip back into a trimester hibernation cycle. Hibernation mi=
ght be great for ground hogs, but it doesn't lead to particularly good weat=
her forecasting or the rapid development of community consensus.

	I'd also like to point out that adoption of a draft is not conclusion of t=
he work; we still expect to see a large amount of review, and may see some =
substantive changes,  That is, after all, the IETF's work process.

	On the comment of "yet another interface to support": The goal of doing MA=
RTINI registration as I understand it has been merely to clean up and stand=
ardize an existing broadly (but diversely) deployed interface. It's not the=
 final answer to the problem, and I think it's OK that IMS has a slightly d=
ifferent answer to a slightly different problem. I fully expect to go on fr=
om here towards solving the more general dynamic route-binding problem (ano=
ther fact of which we are currently seeing in DISPATCH).
=09
	[=3D=3D>BC:] I think the situation is even worse than what Keith has descr=
ibed. As It's not only "yet another interface to support" but probably TWO =
other interfaces as it seems that a different solution will be required at =
a later stage for supporting other forms of URIs. I also think it's too ear=
ly to go for WGLC.

	So at this time, I'd like to endorse the adoption of "gin" as a standardiz=
ed component of the proper MARTINI. I'll leave it to Hadriel and Adam to le=
ad the conversation as to whether we want our gin shaken, stirred, or possi=
bly blended into the final confection. And hopefully Keith can look up from=
 his 3GPP work long enough to partake of a few SIPs along the way.

	--
	Dean



*********************************
This message and any attachments (the "message") are confidential and inten=
ded solely for the addressees.=20
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.=20
France Telecom Group shall not be liable for the message if altered, change=
d or falsified.
If you are not the intended addressee of this message, please cancel it imm=
ediately and inform the sender.
********************************


------_=_NextPart_001_01CABF68.39FF7083
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; webkit-line-break:=
 after-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D162070409-08032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Dfr dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>De&nbsp;:</B> martini-bounces@ietf.org=20
  [mailto:martini-bounces@ietf.org] <B>De la part de</B> Dean=20
  Willis<BR><B>Envoy=E9&nbsp;:</B> vendredi 5 mars 2010 19:12<BR><B>=C0&nbs=
p;:</B>=20
  DRAGE, Keith (Keith)<BR><B>Cc&nbsp;:</B> Bernard Aboba;=20
  'MARTINI'<BR><B>Objet&nbsp;:</B> Re: [martini] Call for Adoption of=20
  "Registration for MultiplePhone Numbers in the SIP"<BR></FONT><BR></DIV>
  <DIV></DIV><BR>
  <DIV>
  <DIV>On Mar 4, 2010, at 5:13 PM, DRAGE, Keith (Keith) wrote:</DIV><BR=20
  class=3DApple-interchange-newline>
  <BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-style-span=20
    style=3D"WORD-SPACING: 0px; FONT: medium Helvetica; TEXT-TRANSFORM: non=
e; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING=
: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: 2; webkit-border-h=
orizontal-spacing: 0px; webkit-border-vertical-spacing: 0px; webkit-text-de=
corations-in-effect: none; webkit-text-size-adjust: auto; webkit-text-strok=
e-width: 0px">
    <DIV lang=3DEN-US vlink=3D"purple" link=3D"blue">
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D771440923-04032010><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>While you may be wanting to keep to the MARTIN=
I=20
    timescales - I for one am struggling to keep up with=20
    this.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D771440923-04032010><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D771440923-04032010><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>You have the WGLC for requirements in the midd=
le of a=20
    major 3GPP meeting (a draft I still need to review and comment on), and=
 now=20
    you are doing the adoption for GIN in the run up to the Anaheim, when I=
 know=20
    there are still issues to address here as well - as to whether this eve=
n=20
    bears commonality for where we need to get to.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D771440923-04032010><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D771440923-04032010><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>So my view is NO, because it is too early. Doi=
ng this=20
    now ensures that MARTINI goes a different way to the rest of the world =
and=20
    you end up with yet another interdace to=20
    support.</FONT></SPAN></DIV></DIV></SPAN></BLOCKQUOTE></DIV><BR>
  <DIV>It's true that we've been moving very quickly on this work. I'm asto=
unded=20
  at the level of energy and enthusiasm expressed. This is exactly the sort=
 of=20
  response I was hoping for when I pushed for smaller, task-focused, and=20
  short-lived working groups as opposed to the eternal lumbering behemoths =
of=20
  SIP and SIPPING.</DIV>
  <DIV><BR></DIV>
  <DIV>Working on "Internet time" is at odds with the longer review/work cy=
cle=20
  of other SDOs like 3GPP. This can make for some painful adjustments and=
=20
  rethinking of the way we do things. I'm sorry that this is making it hard=
 for=20
  some of our folks who are concurrently working in multiple organizational=
=20
  temporalities. But I think it is absolutely critical that we keep our mom=
entum=20
  going and not slip back into a trimester hibernation cycle. Hibernation m=
ight=20
  be great for ground hogs, but it doesn't lead to particularly good weathe=
r=20
  forecasting or the rapid development of community consensus.</DIV>
  <DIV><BR></DIV>
  <DIV>I'd also like to point out that adoption of a draft is not conclusio=
n of=20
  the work; we still expect to see a large amount of review, and may see so=
me=20
  substantive changes, &nbsp;That is, after all, the IETF's work process.</=
DIV>
  <DIV><BR></DIV>
  <DIV>On the comment of "yet another interface to support": The goal of do=
ing=20
  MARTINI registration as I understand it has been merely to clean up and=
=20
  standardize an existing broadly (but diversely) deployed interface. It's =
not=20
  the final answer to the problem, and I think it's OK that IMS has a sligh=
tly=20
  different answer to a slightly different problem. I fully expect to go on=
 from=20
  here towards solving the more general dynamic route-binding problem (anot=
her=20
  fact of which we are currently seeing in DISPATCH).<BR><SPAN=20
  class=3D162070409-08032010><FONT face=3DArial size=3D2></FONT></SPAN></DI=
V>
  <DIV><SPAN class=3D162070409-08032010><FONT face=3DArial=20
  size=3D2><STRONG>[=3D=3D&gt;BC:]&nbsp;<SPAN class=3D162070409-08032010><F=
ONT=20
  face=3DArial color=3D#0000ff size=3D2><FONT color=3D#000000>I think the s=
ituation is=20
  even worse than what Keith has described. As It's not only "yet another=
=20
  interface to support" but probably TWO&nbsp;other interfaces as it seems =
that=20
  a different solution will be required at a later stage for supporting oth=
er=20
  forms of URIs. I also think it's too early to go for=20
  WGLC.</FONT></FONT></SPAN></STRONG></FONT></SPAN><SPAN=20
  class=3D162070409-08032010></SPAN><SPAN class=3D162070409-08032010></SPAN=
><SPAN=20
  class=3D162070409-08032010><FONT face=3DArial color=3D#0000ff=20
  size=3D2></FONT></SPAN></DIV>
  <DIV><BR></DIV>
  <DIV>So at this time, I'd like to endorse the adoption of "gin" as a=20
  standardized component of the proper MARTINI. I'll leave it to Hadriel an=
d=20
  Adam to lead the conversation as to whether we want our gin shaken, stirr=
ed,=20
  or possibly blended into the final confection. And hopefully Keith can lo=
ok up=20
  from his 3GPP work long enough to partake of a few SIPs along the way.</D=
IV>
  <DIV><BR></DIV>
  <DIV>--</DIV>
  <DIV>Dean</DIV>
  <DIV><BR></DIV></BLOCKQUOTE><PRE>*********************************
This message and any attachments (the "message") are confidential and inten=
ded solely for the addressees.=20
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.=20
France Telecom Group shall not be liable for the message if altered, change=
d or falsified.
If you are not the intended addressee of this message, please cancel it imm=
ediately and inform the sender.
********************************
</PRE></BODY></HTML>

------_=_NextPart_001_01CABF68.39FF7083--

From spencer@wonderhamster.org  Tue Mar  9 09:55:52 2010
Return-Path: <spencer@wonderhamster.org>
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 6EA533A6915 for <martini@core3.amsl.com>; Tue,  9 Mar 2010 09:55:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.184
X-Spam-Level: 
X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, STOX_REPLY_TYPE=0.001]
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 9WoRqBXXz5mr for <martini@core3.amsl.com>; Tue,  9 Mar 2010 09:55:50 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 665C93A6968 for <martini@ietf.org>; Tue,  9 Mar 2010 09:55:50 -0800 (PST)
Received: from S73602b ([12.172.14.11]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MIdsG-1NrFVx2zTU-0030eF; Tue, 09 Mar 2010 12:55:54 -0500
Message-ID: <BF420A61348C4BF9BDA6FE0B081C33D3@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: <martini@ietf.org>
Date: Tue, 9 Mar 2010 11:55:52 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX19TwQ7oGC8SOREmHiaLYSvWdalimK8N47sMGs0 8/bnJTWOmUKJSriI0WDpDWWnd25PFYum5BlJDMp216OTXd9RGG gnFEpAqeQIBlmJJNhYsHnU9OGU4UJi13x58LMSfGUU=
Subject: [martini] IETF 77 MARTINI Participation Doodle Poll
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, 09 Mar 2010 17:55:52 -0000

MARTINI is currently scheduled to meet at IETF 77. It would be very helpful 
for Bernard and I to know who to expect in our meeting.

Please visit http://www.doodle.com/xb2wn5hr69hds4yn and let us know if 
you're coming.

Thanks,

Spencer and Bernard, as co-chairs 


From dean.willis@softarmor.com  Tue Mar  9 09:56:31 2010
Return-Path: <dean.willis@softarmor.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 213943A6915 for <martini@core3.amsl.com>; Tue,  9 Mar 2010 09:56:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599]
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 DZOVN1bKUdaO for <martini@core3.amsl.com>; Tue,  9 Mar 2010 09:56:30 -0800 (PST)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 21BEB3A6904 for <martini@ietf.org>; Tue,  9 Mar 2010 09:56:30 -0800 (PST)
Received: from [192.168.2.108] (cpe-66-25-30-183.tx.res.rr.com [66.25.30.183]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id o29HuU6L032728 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 9 Mar 2010 11:56:32 -0600
Message-Id: <2BE087AB-0DD5-4024-A837-9DA6597AEDFF@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "<bruno.chatras@orange-ftgroup.com>" <bruno.chatras@orange-ftgroup.com>
In-Reply-To: <951_1268125870_4B9610AE_951_114651_3_9ECCF01B52E7AB408A7EB85352642141012FD45D@ftrdmel0.rd.francetelecom.fr>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 9 Mar 2010 11:56:25 -0600
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl><EDC0A1AE77C57744B664A310A0B23AE20C19E15F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AFB74521-1DBC-4750-AF59-F88B43352302@softarmor.com> <951_1268125870_4B9610AE_951_114651_3_9ECCF01B52E7AB408A7EB85352642141012FD45D@ftrdmel0.rd.francetelecom.fr>
X-Mailer: Apple Mail (2.936)
Cc: Keith Drage <keith.drage@alcatel-lucent.com>, MARTINI <martini@ietf.org>
Subject: Re: [martini] Call for Adoption of "Registration for MultiplePhone	Numbers in the SIP"
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, 09 Mar 2010 17:56:31 -0000

On Mar 9, 2010, at 3:08 AM, <bruno.chatras@orange-ftgroup.com> <bruno.chatras@orange-ftgroup.com 
 > wrote:

> I think the situation is even worse than what Keith has described.  
> As It's not only "yet another interface to support" but probably TWO  
> other interfaces as it seems that a different solution will be  
> required at a later stage for supporting other forms of URIs. I also  
> think it's too early to go for WGLC.

I prefer to think of what GIN is currently doing as simply clarifying  
and standardizing what can be done with RFC 3261's REGISTER method for  
single-request registration of multiple phone numbers. This is a  
matter of converging multiple common implementations into a single  
standardized approach. It's not a "new" interface, but a cleanup of an  
underspecified one that already exists.

It's true that we aren't proposing (in this document) to standardize  
registration of multiple domain-style AORs with a single request.  
We're not agreed that REGISTER is even a reasonable general solution  
to that problem, nor are we likely to so agree at any time in the near  
future. Nor are we proposing to solve at this time the fundamental  
intra-domain or inter-domain routing problems (see current thread in  
DISPATCH).

A second "interface", as you and Keith describe it, is probably  
required because REGISTER itself is fundamentally unsuited to solving  
the general routing problem. All we're doing in this document (gin) is  
the part of the problem that REGISTER can reasonably solve when the  
target identities are expressed as phone numbers.

I'd argue that REGISTER could also be reasonably used for handling  
registration of multiple domain-style URIs (AORs) when those AOR-URIs  
are all scoped to the same authentication domain AND the right-hand- 
side of the contact-URI is identical across all contact-URI's being  
registered within a single request AND there is a one-to-one mapping  
between AOR-URI and contact-URI produced in the registrar as a result  
of the request. This might well be within the scope of MARTINI, and is  
a completely separable problem. It could be documented in the same  
RFC, or documented in a second RFC, should we choose to pursue that  
line of work. I would argue that such an approach would not constitute  
a separate interface in either case (same or different documents).  
Each would be a documentation of the REGISTER interface for  
registering multiple contacts within a single request -- one for  
multiple domain-style URIs, one for multiple phone numbers within a  
domain.


So, are you saying that:

1) You don't like the GIN mechanism and we shouldn't work from it for  
solving the multiple phone-number-registration problem.

2) You like the GIN mechanism but don't want to settle on it until we  
also have a proposal for dealing with the subset of the "registering  
multiple domain-style URIs in a single request" problem that can be  
dealt with using REGISTER.

2a) As 2, and you want the proposal for dealing with the subset of the  
"registering multiple domain-style URIs in a single request" problem  
that can be dealt with using REGISTER to be incorporated into the same  
document as the current gin solution before it is adopted as baseline  
text by the WG.

2b) As 2, and you want the proposal for dealing with the subset of the  
"registering multiple domain-style URIs in a single request" problem  
that can be dealt with using REGISTER to be presented in a separate  
document so that we can adopt them both concurrently.

3) You believe that REGISTER is the "universal hammer" for all SIP  
routing exchange problems, and are going to  block any partial  
solution until we all accept that approach and have a written proposal  
for solving all route-exchange problems using REGISTER.

4) Something entirely different (please specify).


And who said anything about WGLC of the solution? We're talking WGLC  
of the requirements draft, and adoption of the -gin- draft as a  
baseline text that we will then hammer on until we're ready for WGLC.

--
Dean

From bernard_aboba@hotmail.com  Tue Mar  9 10:41:03 2010
Return-Path: <bernard_aboba@hotmail.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 3C0B13A6963 for <martini@core3.amsl.com>; Tue,  9 Mar 2010 10:41:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.958
X-Spam-Level: 
X-Spam-Status: No, score=-0.958 tagged_above=-999 required=5 tests=[AWL=-0.219, BAYES_20=-0.74, HTML_MESSAGE=0.001]
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 qNc+n3RczCTm for <martini@core3.amsl.com>; Tue,  9 Mar 2010 10:41:00 -0800 (PST)
Received: from blu0-omc2-s25.blu0.hotmail.com (blu0-omc2-s25.blu0.hotmail.com [65.55.111.100]) by core3.amsl.com (Postfix) with ESMTP id F0CF43A6A10 for <martini@ietf.org>; Tue,  9 Mar 2010 10:40:59 -0800 (PST)
Received: from BLU137-DS15 ([65.55.111.72]) by blu0-omc2-s25.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 9 Mar 2010 10:41:04 -0800
X-Originating-IP: [131.107.0.104]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS152527D5E75E6306FFB40F93340@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <bruno.chatras@orange-ftgroup.com>, <dean.willis@softarmor.com>, <keith.drage@alcatel-lucent.com>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl><EDC0A1AE77C57744B664A310A0B23AE20C19E15F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AFB74521-1DBC-4750-AF59-F88B43352302@softarmor.com> <951_1268125870_4B9610AE_951_114651_3_9ECCF01B52E7AB408A7EB85352642141012FD45D@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <951_1268125870_4B9610AE_951_114651_3_9ECCF01B52E7AB408A7EB85352642141012FD45D@ftrdmel0.rd.francetelecom.fr>
Date: Tue, 9 Mar 2010 10:41:00 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_03AD_01CABF75.0297EBB0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acq8j2O+TPHRRmshSh+XU9dlDat8cgCDusigAEZgUbA=
Content-Language: en-us
X-OriginalArrivalTime: 09 Mar 2010 18:41:04.0414 (UTC) FILETIME=[12D24BE0:01CABFB8]
Cc: martini@ietf.org
Subject: Re: [martini] Call for Adoption of "Registration for MultiplePhone	Numbers in the SIP"
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, 09 Mar 2010 18:41:03 -0000

------=_NextPart_000_03AD_01CABF75.0297EBB0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

 [==>BC:] I think the situation is even worse than what Keith has described.
As It's not only "yet another interface to support" but probably TWO other
interfaces as it seems that a different solution will be required at a later
stage for supporting other forms of URIs. I also think it's too early to go
for WGLC.

 
[BA] To clarify -- this isn't a MARTINI WG last call, since GIN isn't a
MARTINI WG work item yet.  It's a "Call for Adoption" of GIN as a MARTINI WG
work item.   

------=_NextPart_000_03AD_01CABF75.0297EBB0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple style=3D'WORD-WRAP: =
break-word;
webkit-nbsp-mode: space;webkit-line-break: after-white-space'>

<div class=3DSection1>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<div>

<p class=3DMsoNormal><strong><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;[=3D=3D=
&gt;BC:]&nbsp;<span
style=3D'color:black'>I think the situation is even worse than what =
Keith has
described. As It's not only &quot;yet another interface to support&quot; =
but
probably TWO&nbsp;other interfaces as it seems that a different solution =
will
be required at a later stage for supporting other forms of URIs. I also =
think
it's too early to go for WGLC.</span></span></strong><o:p></o:p></p>

</div>

</blockquote>

<pre><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></pre><pre><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[BA] To clarify -- this isn&#8217;t a MARTINI WG last call, since GIN =
isn&#8217;t a MARTINI WG work item yet.&nbsp; It&#8217;s a &#8220;Call =
for Adoption&#8221; of GIN as a MARTINI WG work item. =
&nbsp;&nbsp;<o:p></o:p></span></pre></div>

</body>

</html>

------=_NextPart_000_03AD_01CABF75.0297EBB0--

From bruno.chatras@orange-ftgroup.com  Tue Mar  9 11:01:42 2010
Return-Path: <bruno.chatras@orange-ftgroup.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 CEEE33A6A63 for <martini@core3.amsl.com>; Tue,  9 Mar 2010 11:01:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 GHvr+VXhWHqc for <martini@core3.amsl.com>; Tue,  9 Mar 2010 11:01:41 -0800 (PST)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id 4D04A3A6A6C for <martini@ietf.org>; Tue,  9 Mar 2010 11:01:40 -0800 (PST)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 668B96FCC25; Tue,  9 Mar 2010 20:05:34 +0000 (UTC)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id 5DCD96FCC24; Tue,  9 Mar 2010 20:05:34 +0000 (UTC)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 9 Mar 2010 20:01:37 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 9 Mar 2010 20:01:37 +0100
Message-ID: <9ECCF01B52E7AB408A7EB8535264214101329FB6@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <2BE087AB-0DD5-4024-A837-9DA6597AEDFF@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] Call for Adoption of "Registration for MultiplePhone	Numbers in the SIP"
Thread-Index: Acq/sgFyBj+6vq8sRGmeIyEQM13qIwAAKV3Q
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl><EDC0A1AE77C57744B664A310A0B23AE20C19E15F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AFB74521-1DBC-4750-AF59-F88B43352302@softarmor.com> <951_1268125870_4B9610AE_951_114651_3_9ECCF01B52E7AB408A7EB85352642141012FD45D@ftrdmel0.rd.francetelecom.fr> <2BE087AB-0DD5-4024-A837-9DA6597AEDFF@softarmor.com>
From: <bruno.chatras@orange-ftgroup.com>
To: <dean.willis@softarmor.com>
X-OriginalArrivalTime: 09 Mar 2010 19:01:37.0918 (UTC) FILETIME=[F20C11E0:01CABFBA]
Cc: keith.drage@alcatel-lucent.com, martini@ietf.org
Subject: Re: [martini] Call for Adoption of "Registration for MultiplePhone	Numbers in the SIP"
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, 09 Mar 2010 19:01:42 -0000

Strictly speaking it's not a new interface but in practice it means that =
a PBX will find different things in the Request URI of inbound requests =
depending on whether it is connected  to an IMS or a GIN-based network. =
In the first case, the R-URI will contain the original target identity =
while in the second case it will contain this special contact address =
built as described in the GIN draft.=20

For the rest of my message, there was a typo in it! I intended to write =
that it was too early to accept this document as a WG Work Item but =
wrote WGLC...=20

If I try to map what I meant to your 4 options, I believe I meant Option =
1: I don't like the GIN mechanism in its present form as it does not =
preserve the original target identity in the R-URI and is restricted to =
E.164 numbers. However, what you have described as Option 2a is worth =
discussing. The definition of the <subset of the "registering multiple =
domain-style URIs in a single request" problem that can be dealt with =
using REGISTER> would also deserve further discussions. If it turns out =
that the gin draft can be extended to support a reasonable subset of the =
problem then it might become a better candidate for a WG Work Item. This =
does not solve the R-URI issue however.

/BC


> -----Message d'origine-----
> De : Dean Willis [mailto:dean.willis@softarmor.com]=20
> Envoy=E9 : mardi 9 mars 2010 18:56
> =C0 : CHATRAS Bruno RD-CORE-ISS
> Cc : Keith Drage; MARTINI
> Objet : Re: [martini] Call for Adoption of "Registration for=20
> MultiplePhone Numbers in the SIP"
>=20
>=20
> On Mar 9, 2010, at 3:08 AM,=20
> <bruno.chatras@orange-ftgroup.com>=20
> <bruno.chatras@orange-ftgroup.com  > wrote:
>=20
> > I think the situation is even worse than what Keith has described. =20
> > As It's not only "yet another interface to support" but=20
> probably TWO=20
> > other interfaces as it seems that a different solution will be=20
> > required at a later stage for supporting other forms of=20
> URIs. I also=20
> > think it's too early to go for WGLC.
>=20
> I prefer to think of what GIN is currently doing as simply=20
> clarifying and standardizing what can be done with RFC 3261's=20
> REGISTER method for single-request registration of multiple=20
> phone numbers. This is a matter of converging multiple common=20
> implementations into a single standardized approach. It's not=20
> a "new" interface, but a cleanup of an underspecified one=20
> that already exists.
>=20
> It's true that we aren't proposing (in this document) to=20
> standardize registration of multiple domain-style AORs with a=20
> single request. =20
> We're not agreed that REGISTER is even a reasonable general=20
> solution to that problem, nor are we likely to so agree at=20
> any time in the near future. Nor are we proposing to solve at=20
> this time the fundamental intra-domain or inter-domain=20
> routing problems (see current thread in DISPATCH).
>=20
> A second "interface", as you and Keith describe it, is=20
> probably required because REGISTER itself is fundamentally=20
> unsuited to solving the general routing problem. All we're=20
> doing in this document (gin) is the part of the problem that=20
> REGISTER can reasonably solve when the target identities are=20
> expressed as phone numbers.
>=20
> I'd argue that REGISTER could also be reasonably used for=20
> handling registration of multiple domain-style URIs (AORs)=20
> when those AOR-URIs are all scoped to the same authentication=20
> domain AND the right-hand- side of the contact-URI is=20
> identical across all contact-URI's being registered within a=20
> single request AND there is a one-to-one mapping between=20
> AOR-URI and contact-URI produced in the registrar as a result=20
> of the request. This might well be within the scope of=20
> MARTINI, and is a completely separable problem. It could be=20
> documented in the same RFC, or documented in a second RFC,=20
> should we choose to pursue that line of work. I would argue=20
> that such an approach would not constitute a separate=20
> interface in either case (same or different documents). =20
> Each would be a documentation of the REGISTER interface for=20
> registering multiple contacts within a single request -- one=20
> for multiple domain-style URIs, one for multiple phone=20
> numbers within a domain.
>=20
>=20
> So, are you saying that:
>=20
> 1) You don't like the GIN mechanism and we shouldn't work=20
> from it for solving the multiple phone-number-registration problem.
>=20
> 2) You like the GIN mechanism but don't want to settle on it=20
> until we also have a proposal for dealing with the subset of=20
> the "registering multiple domain-style URIs in a single=20
> request" problem that can be dealt with using REGISTER.
>=20
> 2a) As 2, and you want the proposal for dealing with the=20
> subset of the "registering multiple domain-style URIs in a=20
> single request" problem that can be dealt with using REGISTER=20
> to be incorporated into the same document as the current gin=20
> solution before it is adopted as baseline text by the WG.
>=20
> 2b) As 2, and you want the proposal for dealing with the=20
> subset of the "registering multiple domain-style URIs in a=20
> single request" problem that can be dealt with using REGISTER=20
> to be presented in a separate document so that we can adopt=20
> them both concurrently.
>=20
> 3) You believe that REGISTER is the "universal hammer" for=20
> all SIP routing exchange problems, and are going to  block=20
> any partial solution until we all accept that approach and=20
> have a written proposal for solving all route-exchange=20
> problems using REGISTER.
>=20
> 4) Something entirely different (please specify).
>=20
>=20
> And who said anything about WGLC of the solution? We're=20
> talking WGLC of the requirements draft, and adoption of the=20
> -gin- draft as a baseline text that we will then hammer on=20
> until we're ready for WGLC.
>=20
> --
> Dean
>=20

From richard@shockey.us  Tue Mar  9 17:50:05 2010
Return-Path: <richard@shockey.us>
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 0C8023A6AE9 for <martini@core3.amsl.com>; Tue,  9 Mar 2010 17:50:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.17
X-Spam-Level: 
X-Spam-Status: No, score=-1.17 tagged_above=-999 required=5 tests=[AWL=-1.172,  BAYES_50=0.001, HTML_MESSAGE=0.001]
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 C-JKJjnQgHQf for <martini@core3.amsl.com>; Tue,  9 Mar 2010 17:50:04 -0800 (PST)
Received: from outbound-mail-360.bluehost.com (outbound-mail-360.bluehost.com [66.147.249.254]) by core3.amsl.com (Postfix) with SMTP id F103D3A6AE1 for <martini@ietf.org>; Tue,  9 Mar 2010 17:50:03 -0800 (PST)
Received: (qmail 22409 invoked by uid 0); 10 Mar 2010 01:43:28 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy2.bluehost.com with SMTP; 10 Mar 2010 01:43:28 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=TMIvnGFTYSC4Z1sIj03DmxyWwWErZrKXmtIh2T1wdCnGjRWTF2V8UEqC4vOmyizGhVEPbgDhHcZ2r2BPtZ65E6/R/9OIGJh2JBpFfOsLhKbNG6WtA/CUZmk/XB/HQ2tI;
Received: from pool-173-66-69-79.washdc.fios.verizon.net ([173.66.69.79] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from <richard@shockey.us>) id 1NpAxM-0002WA-Ag; Tue, 09 Mar 2010 18:43:28 -0700
From: "Richard Shockey" <richard@shockey.us>
To: <dispatch@ietf.org>, <sipcore@ietf.org>, "'MARTINI'" <martini@ietf.org>
Date: Tue, 9 Mar 2010 20:43:25 -0500
Message-ID: <028201cabff3$13cc1360$3b643a20$@us>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0283_01CABFC9.2AF60B60"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acq/uZOrLwXMolSnQeyPKU4g86oIkg==
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.66.69.79 authed with richard@shockey.us}
Subject: [martini] SIP Forum Luncheon at IETF 77 Monday 11:30 13:00
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: Wed, 10 Mar 2010 01:50:05 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0283_01CABFC9.2AF60B60
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 

The SIP Forum is going to hold a open meeting for the RAI community during
IETF 77. The purpose of this meeting is remind the SIP community of what the
SIP Forum is doing and discuss relevant technical issues that relate to IETF
WG's. The agenda for this luncheon will be to review current activities in
the SIP Forum and seek additional technical input from the RAI community on
mutual concerns.

 

As many of you know the SIP Forum is the principal sponsor of the SIPit
interoperability events and currently has 4 Task groups operating. 

 

BTW registration for SIPit 26 will be open soon.

 

Our principal technical initiatives are:

 

1.      SIP Connect 1.1 which is developing an enhanced  profile of IETF
Standards for PBX to SSP interoperability. As part of that work the IETF
MARTINI WG was formed to redefine the so called Implicit registration
procedure in SIP.

2.      FAX over SIP is investigating the interoperability of SIP in T.38
networks with a goal of possible recommendations to the relevant SDO's on
how fax can work better.

3.      Client User Agent Configuration which has a pending Recommendation
on how CUA devices could auto streamline the locating, retrieving and
maintaining of configuration-related information for SIP User Agents

4.      SIP in the SmartGrid. This is a Special Interest Group that is
evaluating the appropriateness of using SIP as a protocol for a number of
Smart Grid areas, including the Home Area Network (HAN), Utilities'
Operational Network, and PEV (Plug-In Vehicle) deployments.

 

Information on the SIP Forum is available at 

 

http//www.sipforum.org

 

If you are interested in attending this event we have set up a Doodle Poll
to indicate your interest. Seating is somewhat limited ( 150 Maximum) lunch
will be provided.

 

Location .. Monday 11:30 13:00 the Laguna room and its located on the 4th
floor of the Anaheim Hilton

The link to the poll is: 

http://www.doodle.com/hde57nbpcdykzqfz 

 

Richard Shockey
Shockey Consulting
Chairman of the Board of Directors SIP Forum
PSTN Mobile: +1 703.593.2683
<mailto:richard(at)shockey.us>
skype: rshockey101
LinkedIn : http://www.linkedin.com/in/rshockey101



 


------=_NextPart_000_0283_01CABFC9.2AF60B60
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1758674576;
	mso-list-type:hybrid;
	mso-list-template-ids:-1492463448 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>The SIP Forum is going to hold a open meeting for =
the RAI
community during IETF 77. The purpose of this meeting is remind the SIP
community of what the SIP Forum is doing and discuss relevant technical =
issues
that relate to IETF WG&#8217;s. The agenda for this luncheon will be to =
review
current activities in the SIP Forum and seek additional technical input =
from
the RAI community on mutual concerns.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>As many of you know the SIP Forum is the principal =
sponsor
of the SIPit interoperability events and currently has 4 Task groups =
operating.
<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>BTW registration for SIPit 26 will be open =
soon.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Our principal technical initiatives =
are:<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>SIP Connect 1.1 which is developing an enhanced
&nbsp;profile of IETF Standards for PBX to SSP interoperability. As part =
of
that work the IETF MARTINI WG was formed to redefine the so called =
Implicit
registration procedure in SIP.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>FAX over SIP is investigating the =
interoperability of
SIP in T.38 networks with a goal of possible recommendations to the =
relevant
SDO&#8217;s on how fax can work better.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Client User Agent Configuration which has a =
pending
Recommendation on how CUA devices could auto streamline the locating,
retrieving and maintaining of configuration-related information for SIP =
User
Agents<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'mso-list:Ignore'>4.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>SIP in the SmartGrid. This is a Special Interest =
Group
that is evaluating the appropriateness of using SIP as a protocol for a =
number
of Smart Grid areas, including the Home Area Network (HAN), Utilities'
Operational Network, and PEV (Plug-In Vehicle) =
deployments.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Information on the SIP Forum is available at =
<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Times =
New Roman","serif"'>http//www.sipforum.org</span><o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>If you are interested in attending this event we =
have set up
a Doodle Poll to indicate your interest. Seating is somewhat limited ( =
150
Maximum) lunch will be provided.<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
background:yellow;mso-highlight:yellow'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
background:yellow;mso-highlight:yellow'>Location .. </span><span
style=3D'font-size:10.0pt'>Monday 11:30 13:00 </span><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif";color:blue'>the Laguna room and its =
located on
the 4th floor of the Anaheim Hilton</span><span =
style=3D'font-size:10.0pt;
background:yellow;mso-highlight:yellow'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
background:yellow;mso-highlight:yellow'>The link to the poll =
is:</span><span
style=3D'font-size:10.0pt'> <br>
<br>
<a href=3D"http://www.doodle.com/hde57nbpcdykzqfz" =
target=3D"_blank">http://www.doodle.com/hde57nbpcdykzqfz</a>
</span><o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
style=3D'font-size:10.0pt;font-family:"Times New Roman","serif"'>Richard =
Shockey<br>
Shockey Consulting<br>
Chairman of the Board of Directors SIP Forum<br>
PSTN Mobile: +1 703.593.2683<br>
&lt;<a =
href=3D"mailto:richard(at)shockey.us">mailto:richard(at)shockey.us</a>&gt=
;<br>
skype: rshockey101<br>
LinkedIn : <a =
href=3D"http://www.linkedin.com/in/rshockey101">http://www.linkedin.com/i=
n/rshockey101</a><br>
<br>
</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0283_01CABFC9.2AF60B60--


From dean.willis@softarmor.com  Tue Mar  9 20:06:22 2010
Return-Path: <dean.willis@softarmor.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 736903A6B33 for <martini@core3.amsl.com>; Tue,  9 Mar 2010 20:06:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.031,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 J8p57L9TFy0c for <martini@core3.amsl.com>; Tue,  9 Mar 2010 20:06:21 -0800 (PST)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 5839A3A6B32 for <martini@ietf.org>; Tue,  9 Mar 2010 20:06:21 -0800 (PST)
Received: from [192.168.2.108] (cpe-66-25-30-183.tx.res.rr.com [66.25.30.183]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id o2A46NHO004364 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 9 Mar 2010 22:06:24 -0600
Message-Id: <1FA4E089-8790-454F-9046-C67F13E411CA@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "<bruno.chatras@orange-ftgroup.com>" <bruno.chatras@orange-ftgroup.com>
In-Reply-To: <9ECCF01B52E7AB408A7EB8535264214101329FB6@ftrdmel0.rd.francetelecom.fr>
Content-Type: multipart/alternative; boundary=Apple-Mail-24--23514505
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 9 Mar 2010 22:06:17 -0600
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl><EDC0A1AE77C57744B664A310A0B23AE20C19E15F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AFB74521-1DBC-4750-AF59-F88B43352302@softarmor.com> <951_1268125870_4B9610AE_951_114651_3_9ECCF01B52E7AB408A7EB85352642141012FD45D@ftrdmel0.rd.francetelecom.fr> <2BE087AB-0DD5-4024-A837-9DA6597AEDFF@softarmor.com> <9ECCF01B52E7AB408A7EB8535264214101329FB6@ftrdmel0.rd.francetelecom.fr>
X-Mailer: Apple Mail (2.936)
Cc: keith.drage@alcatel-lucent.com, martini@ietf.org
Subject: Re: [martini] Call for Adoption of "Registration for MultiplePhone	Numbers in the SIP"
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: Wed, 10 Mar 2010 04:06:22 -0000

--Apple-Mail-24--23514505
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit


On Mar 9, 2010, at 1:01 PM, <bruno.chatras@orange-ftgroup.com> <bruno.chatras@orange-ftgroup.com 
 > wrote:
>
> If I try to map what I meant to your 4 options, I believe I meant  
> Option 1: I don't like the GIN mechanism in its present form as it  
> does not preserve the original target identity in the R-URI

REGISTER under RFC 3261 does not preserve the target identity in the R- 
URI. Rather, it places the identity being registered in the To: header  
field.

Or are you saying you don't like contact-routing as described in RFC  
3261, because contact routing doesn't preserve the R-URI as seen by  
the home proxy; rather, the R-URI is replaced by the registered Contact.

If do, I don't like it either. But we can't do much about it without  
rather fundamental changes to RFC 3261, and I don't think that MARTINI  
is chartered to completely re-write the registration and contact- 
routing of RFC 3261, despite the fact that it desperately needs doing.


> and is restricted to E.164 numbers. However, what you have described  
> as Option 2a is worth discussing. The definition of the <subset of  
> the "registering multiple domain-style URIs in a single request"  
> problem that can be dealt with using REGISTER> would also deserve  
> further discussions. If it turns out that the gin draft can be  
> extended to support a reasonable subset of the problem then it might  
> become a better candidate for a WG Work Item.

Ok, let's start a separate thread for that topic.

> This does not solve the R-URI issue however.


Nor does it solve world peace, global climate change, or the  
inadequacy of socialized medicine to meet the very real demands of an  
aging population of baby boomers who are starting to get Even Sicker.  
We have about the same likely hood of solving those in MARTINI as we  
have of solving the "preservation of request-URI across contact  
routing" problem.

--
Dean





--Apple-Mail-24--23514505
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On Mar 9, 2010, =
at 1:01 PM, &lt;<a =
href=3D"mailto:bruno.chatras@orange-ftgroup.com">bruno.chatras@orange-ftgr=
oup.com</a>&gt; &lt;<a =
href=3D"mailto:bruno.chatras@orange-ftgroup.com">bruno.chatras@orange-ftgr=
oup.com</a>&gt; wrote:</div><blockquote type=3D"cite"><div><font =
class=3D"Apple-style-span" color=3D"#000000"><br></font>If I try to map =
what I meant to your 4 options, I believe I meant Option 1: I don't like =
the GIN mechanism in its present form as it does not preserve the =
original target identity in the R-URI =
</div></blockquote><div><br></div><div>REGISTER under RFC 3261 does not =
preserve the target identity in the R-URI. Rather, it places the =
identity being registered in the To: header =
field.</div><div><br></div><div>Or are you saying you don't like =
contact-routing as described in RFC 3261, because contact routing =
doesn't preserve the R-URI as seen by the home proxy; rather, the R-URI =
is replaced by the registered Contact.</div><div><br></div><div>If do, I =
don't like it either. But we can't do much about it without rather =
fundamental changes to RFC 3261, and I don't think that MARTINI is =
chartered to completely re-write the registration and contact-routing of =
RFC 3261, despite the fact that it desperately needs =
doing.</div><div><br></div><br><blockquote type=3D"cite"><div>and is =
restricted to E.164 numbers. However, what you have described as Option =
2a is worth discussing. The definition of the &lt;subset of the =
"registering multiple domain-style URIs in a single request" problem =
that can be dealt with using REGISTER&gt; would also deserve further =
discussions. If it turns out that the gin draft can be extended to =
support a reasonable subset of the problem then it might become a better =
candidate for a WG Work Item. </div></blockquote><div><br></div><div>Ok, =
let's start a separate thread for that topic.</div><br><blockquote =
type=3D"cite"><div>This does not solve the R-URI issue =
however.<br></div></blockquote></div><div><br></div>Nor does it solve =
world peace, global climate change, or the inadequacy of socialized =
medicine to meet the very real demands of an aging population of baby =
boomers who are starting to get Even Sicker. We have about the same =
likely hood of solving those in MARTINI as we have of solving the =
"preservation of request-URI across contact routing" =
problem.<div><br></div><div>--</div><div>Dean<br><div><br></div><div><br><=
div><br></div><div><br></div></div></div></body></html>=

--Apple-Mail-24--23514505--

From john.elwell@siemens-enterprise.com  Wed Mar 10 00:45:34 2010
Return-Path: <john.elwell@siemens-enterprise.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 563213A65A6 for <martini@core3.amsl.com>; Wed, 10 Mar 2010 00:45:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.498
X-Spam-Level: 
X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[AWL=0.101,  BAYES_00=-2.599]
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 h-g--lcImi0F for <martini@core3.amsl.com>; Wed, 10 Mar 2010 00:45:33 -0800 (PST)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 319063A676A for <martini@ietf.org>; Wed, 10 Mar 2010 00:45:32 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1156508; Wed, 10 Mar 2010 09:45:36 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id D87941EB82BD; Wed, 10 Mar 2010 09:45:36 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.57]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Wed, 10 Mar 2010 09:45:37 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Dean Willis <dean.willis@softarmor.com>, "<bruno.chatras@orange-ftgroup.com>" <bruno.chatras@orange-ftgroup.com>
Date: Wed, 10 Mar 2010 09:45:35 +0100
Thread-Topic: [martini] Call for Adoption of "Registration for	MultiplePhone Numbers in the SIP"
Thread-Index: AcrABxA9MWze69iRQd6HP+MV5GLgPwAJe+eA
Message-ID: <A444A0F8084434499206E78C106220CABBC9C70B@MCHP058A.global-ad.net>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl><EDC0A1AE77C57744B664A310A0B23AE20C19E15F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AFB74521-1DBC-4750-AF59-F88B43352302@softarmor.com> <951_1268125870_4B9610AE_951_114651_3_9ECCF01B52E7AB408A7EB85352642141012FD45D@ftrdmel0.rd.francetelecom.fr> <2BE087AB-0DD5-4024-A837-9DA6597AEDFF@softarmor.com> <9ECCF01B52E7AB408A7EB8535264214101329FB6@ftrdmel0.rd.francetelecom.fr> <1FA4E089-8790-454F-9046-C67F13E411CA@softarmor.com>
In-Reply-To: <1FA4E089-8790-454F-9046-C67F13E411CA@softarmor.com>
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
Cc: "keith.drage@alcatel-lucent.com" <keith.drage@alcatel-lucent.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Call for Adoption of "Registration for	MultiplePhone	Numbers in the SIP"
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: Wed, 10 Mar 2010 08:45:34 -0000

Bruno,

I recall from the TISPAN business trunking discussions a couple of years ag=
o that we tried to preserve the contents of the Request-URI, based on princ=
iples proposed in the Rosenberg loose route draft, which was under consider=
ation at the IETF at the time and which we thought had a strong possibility=
 of being adopted. Unfortunately (I can't recall the precise reasons, but b=
ackwards compatibility played a large part), the IETF decided not to go in =
that direction. Therefore it would be an uphill struggle to get the IETF to=
 agree to adopt a similar principle now, in the context of the MARTINI work=
.

John

> -----Original Message-----
> From: martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] On Behalf Of Dean Willis
> Sent: 10 March 2010 04:06
> To: <bruno.chatras@orange-ftgroup.com>
> Cc: keith.drage@alcatel-lucent.com; martini@ietf.org
> Subject: Re: [martini] Call for Adoption of "Registration for=20
> MultiplePhone Numbers in the SIP"
>=20
>=20
> On Mar 9, 2010, at 1:01 PM,=20
> <bruno.chatras@orange-ftgroup.com>=20
> <bruno.chatras@orange-ftgroup.com> wrote:
>=20
> =09
> 	If I try to map what I meant to your 4 options, I=20
> believe I meant Option 1: I don't like the GIN mechanism in=20
> its present form as it does not preserve the original target=20
> identity in the R-URI=20
>=20
>=20
> REGISTER under RFC 3261 does not preserve the target identity=20
> in the R-URI. Rather, it places the identity being registered=20
> in the To: header field.
>=20
> Or are you saying you don't like contact-routing as described=20
> in RFC 3261, because contact routing doesn't preserve the=20
> R-URI as seen by the home proxy; rather, the R-URI is=20
> replaced by the registered Contact.
>=20
> If do, I don't like it either. But we can't do much about it=20
> without rather fundamental changes to RFC 3261, and I don't=20
> think that MARTINI is chartered to completely re-write the=20
> registration and contact-routing of RFC 3261, despite the=20
> fact that it desperately needs doing.
>=20
>=20
>=20
> 	and is restricted to E.164 numbers. However, what you=20
> have described as Option 2a is worth discussing. The=20
> definition of the <subset of the "registering multiple=20
> domain-style URIs in a single request" problem that can be=20
> dealt with using REGISTER> would also deserve further=20
> discussions. If it turns out that the gin draft can be=20
> extended to support a reasonable subset of the problem then=20
> it might become a better candidate for a WG Work Item.=20
>=20
>=20
> Ok, let's start a separate thread for that topic.
>=20
>=20
> 	This does not solve the R-URI issue however.
> =09
>=20
>=20
> Nor does it solve world peace, global climate change, or the=20
> inadequacy of socialized medicine to meet the very real=20
> demands of an aging population of baby boomers who are=20
> starting to get Even Sicker. We have about the same likely=20
> hood of solving those in MARTINI as we have of solving the=20
> "preservation of request-URI across contact routing" problem.=20
>=20
> --
> Dean
>=20
>=20
>=20
>=20
>=20
> =

From ietf.hanserik@gmail.com  Wed Mar 10 00:51:58 2010
Return-Path: <ietf.hanserik@gmail.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 4E1193A6765 for <martini@core3.amsl.com>; Wed, 10 Mar 2010 00:51:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 oGCWXSNwewL8 for <martini@core3.amsl.com>; Wed, 10 Mar 2010 00:51:57 -0800 (PST)
Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216]) by core3.amsl.com (Postfix) with ESMTP id B4CDF3A65A6 for <martini@ietf.org>; Wed, 10 Mar 2010 00:51:56 -0800 (PST)
Received: by ewy8 with SMTP id 8so1173680ewy.28 for <martini@ietf.org>; Wed, 10 Mar 2010 00:51:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=VlUHtynRWLdWnU0pMJyF6vmGtlnIXpao8FvRADDh+28=; b=VVXdoEOnLW95/Jdzs1er9mHmMA5Osfu2bWQGnyQibgGxqOtgJ/BxRbcxhT8EduwCuk p794p5U/7bohn46t4EQKTDTPHyv068PhYZ4uOX3q83BYL3mXKaG0bFwqeNe/vqcjkz2m Z7Y6JvpvNWZ4pl2vAGLm9WmuCxwkpnN+JkqGU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ZEs7yo5wPe9jB+lvdaSgbm9fv56gkd0KhmBaFSeV1jvtMWyy1bVqSpVwlt54npZ7EO 5hybEyiygl4u90otzC1tiGUr0xIdtwvWy51vNdSBcu6txYxISgk4RHx/PpU+ocIF4MUP XsSwyBNnTfWYFjFeXBugQuv00HkD+KiAfzZPc=
MIME-Version: 1.0
Received: by 10.213.1.19 with SMTP id 19mr706270ebd.21.1268211117894; Wed, 10  Mar 2010 00:51:57 -0800 (PST)
In-Reply-To: <A444A0F8084434499206E78C106220CABBC9C70B@MCHP058A.global-ad.net>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl> <EDC0A1AE77C57744B664A310A0B23AE20C19E15F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AFB74521-1DBC-4750-AF59-F88B43352302@softarmor.com> <951_1268125870_4B9610AE_951_114651_3_9ECCF01B52E7AB408A7EB85352642141012FD45D@ftrdmel0.rd.francetelecom.fr> <2BE087AB-0DD5-4024-A837-9DA6597AEDFF@softarmor.com> <9ECCF01B52E7AB408A7EB8535264214101329FB6@ftrdmel0.rd.francetelecom.fr> <1FA4E089-8790-454F-9046-C67F13E411CA@softarmor.com> <A444A0F8084434499206E78C106220CABBC9C70B@MCHP058A.global-ad.net>
Date: Wed, 10 Mar 2010 09:51:57 +0100
Message-ID: <9ae56b1e1003100051w43d14119y2f691cb9a4c368b7@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Content-Type: multipart/alternative; boundary=000e0cdff8b42eae3204816e697c
Cc: "keith.drage@alcatel-lucent.com" <keith.drage@alcatel-lucent.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Call for Adoption of "Registration for MultiplePhone Numbers in the SIP"
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: Wed, 10 Mar 2010 08:51:58 -0000

--000e0cdff8b42eae3204816e697c
Content-Type: text/plain; charset=ISO-8859-1

John,

While the solution has some optical similarities we did NOT adopt the UA
loose route draft solution in TISPAN. We used the loose route mechanism as
provided by RFC3261. For trunking subscriptions the home proxy would just
execute a slightly different routing policy then for normal UE's.

Best Regards,
/Hans Erik van Elburg


On Wed, Mar 10, 2010 at 9:45 AM, Elwell, John <
john.elwell@siemens-enterprise.com> wrote:

> Bruno,
>
> I recall from the TISPAN business trunking discussions a couple of years
> ago that we tried to preserve the contents of the Request-URI, based on
> principles proposed in the Rosenberg loose route draft, which was under
> consideration at the IETF at the time and which we thought had a strong
> possibility of being adopted. Unfortunately (I can't recall the precise
> reasons, but backwards compatibility played a large part), the IETF decided
> not to go in that direction. Therefore it would be an uphill struggle to get
> the IETF to agree to adopt a similar principle now, in the context of the
> MARTINI work.
>
> John
>
> > -----Original Message-----
> > From: martini-bounces@ietf.org
> > [mailto:martini-bounces@ietf.org] On Behalf Of Dean Willis
> > Sent: 10 March 2010 04:06
> > To: <bruno.chatras@orange-ftgroup.com>
> > Cc: keith.drage@alcatel-lucent.com; martini@ietf.org
> > Subject: Re: [martini] Call for Adoption of "Registration for
> > MultiplePhone Numbers in the SIP"
> >
> >
> > On Mar 9, 2010, at 1:01 PM,
> > <bruno.chatras@orange-ftgroup.com>
> > <bruno.chatras@orange-ftgroup.com> wrote:
> >
> >
> >       If I try to map what I meant to your 4 options, I
> > believe I meant Option 1: I don't like the GIN mechanism in
> > its present form as it does not preserve the original target
> > identity in the R-URI
> >
> >
> > REGISTER under RFC 3261 does not preserve the target identity
> > in the R-URI. Rather, it places the identity being registered
> > in the To: header field.
> >
> > Or are you saying you don't like contact-routing as described
> > in RFC 3261, because contact routing doesn't preserve the
> > R-URI as seen by the home proxy; rather, the R-URI is
> > replaced by the registered Contact.
> >
> > If do, I don't like it either. But we can't do much about it
> > without rather fundamental changes to RFC 3261, and I don't
> > think that MARTINI is chartered to completely re-write the
> > registration and contact-routing of RFC 3261, despite the
> > fact that it desperately needs doing.
> >
> >
> >
> >       and is restricted to E.164 numbers. However, what you
> > have described as Option 2a is worth discussing. The
> > definition of the <subset of the "registering multiple
> > domain-style URIs in a single request" problem that can be
> > dealt with using REGISTER> would also deserve further
> > discussions. If it turns out that the gin draft can be
> > extended to support a reasonable subset of the problem then
> > it might become a better candidate for a WG Work Item.
> >
> >
> > Ok, let's start a separate thread for that topic.
> >
> >
> >       This does not solve the R-URI issue however.
> >
> >
> >
> > Nor does it solve world peace, global climate change, or the
> > inadequacy of socialized medicine to meet the very real
> > demands of an aging population of baby boomers who are
> > starting to get Even Sicker. We have about the same likely
> > hood of solving those in MARTINI as we have of solving the
> > "preservation of request-URI across contact routing" problem.
> >
> > --
> > Dean
> >
> >
> >
> >
> >
> >
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>

--000e0cdff8b42eae3204816e697c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

John,<br><br>While the solution has some optical similarities we did NOT ad=
opt the UA loose route draft solution in TISPAN. We used the loose route me=
chanism as provided by RFC3261. For trunking subscriptions the home proxy w=
ould just execute a slightly different routing policy then for normal UE&#3=
9;s.<br>
<br>Best Regards,<br clear=3D"all">/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Wed, Mar 10, 2010 at 9:45 AM, Elwell,=
 John <span dir=3D"ltr">&lt;<a href=3D"mailto:john.elwell@siemens-enterpris=
e.com">john.elwell@siemens-enterprise.com</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204=
); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Bruno,<br>
<br>
I recall from the TISPAN business trunking discussions a couple of years ag=
o that we tried to preserve the contents of the Request-URI, based on princ=
iples proposed in the Rosenberg loose route draft, which was under consider=
ation at the IETF at the time and which we thought had a strong possibility=
 of being adopted. Unfortunately (I can&#39;t recall the precise reasons, b=
ut backwards compatibility played a large part), the IETF decided not to go=
 in that direction. Therefore it would be an uphill struggle to get the IET=
F to agree to adopt a similar principle now, in the context of the MARTINI =
work.<br>

<font color=3D"#888888"><br>
John<br>
</font><div class=3D"im"><br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:martini-bounces@ietf.org">martini-bounces@ietf=
.org</a><br>
&gt; [mailto:<a href=3D"mailto:martini-bounces@ietf.org">martini-bounces@ie=
tf.org</a>] On Behalf Of Dean Willis<br>
&gt; Sent: 10 March 2010 04:06<br>
&gt; To: &lt;<a href=3D"mailto:bruno.chatras@orange-ftgroup.com">bruno.chat=
ras@orange-ftgroup.com</a>&gt;<br>
&gt; Cc: <a href=3D"mailto:keith.drage@alcatel-lucent.com">keith.drage@alca=
tel-lucent.com</a>; <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a=
><br>
&gt; Subject: Re: [martini] Call for Adoption of &quot;Registration for<br>
&gt; MultiplePhone Numbers in the SIP&quot;<br>
&gt;<br>
&gt;<br>
</div><div><div></div><div class=3D"h5">&gt; On Mar 9, 2010, at 1:01 PM,<br=
>
&gt; &lt;<a href=3D"mailto:bruno.chatras@orange-ftgroup.com">bruno.chatras@=
orange-ftgroup.com</a>&gt;<br>
&gt; &lt;<a href=3D"mailto:bruno.chatras@orange-ftgroup.com">bruno.chatras@=
orange-ftgroup.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 If I try to map what I meant to your 4 options, I<br>
&gt; believe I meant Option 1: I don&#39;t like the GIN mechanism in<br>
&gt; its present form as it does not preserve the original target<br>
&gt; identity in the R-URI<br>
&gt;<br>
&gt;<br>
&gt; REGISTER under RFC 3261 does not preserve the target identity<br>
&gt; in the R-URI. Rather, it places the identity being registered<br>
&gt; in the To: header field.<br>
&gt;<br>
&gt; Or are you saying you don&#39;t like contact-routing as described<br>
&gt; in RFC 3261, because contact routing doesn&#39;t preserve the<br>
&gt; R-URI as seen by the home proxy; rather, the R-URI is<br>
&gt; replaced by the registered Contact.<br>
&gt;<br>
&gt; If do, I don&#39;t like it either. But we can&#39;t do much about it<b=
r>
&gt; without rather fundamental changes to RFC 3261, and I don&#39;t<br>
&gt; think that MARTINI is chartered to completely re-write the<br>
&gt; registration and contact-routing of RFC 3261, despite the<br>
&gt; fact that it desperately needs doing.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 and is restricted to E.164 numbers. However, what you<br>
&gt; have described as Option 2a is worth discussing. The<br>
&gt; definition of the &lt;subset of the &quot;registering multiple<br>
&gt; domain-style URIs in a single request&quot; problem that can be<br>
&gt; dealt with using REGISTER&gt; would also deserve further<br>
&gt; discussions. If it turns out that the gin draft can be<br>
&gt; extended to support a reasonable subset of the problem then<br>
&gt; it might become a better candidate for a WG Work Item.<br>
&gt;<br>
&gt;<br>
&gt; Ok, let&#39;s start a separate thread for that topic.<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 This does not solve the R-URI issue however.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Nor does it solve world peace, global climate change, or the<br>
&gt; inadequacy of socialized medicine to meet the very real<br>
&gt; demands of an aging population of baby boomers who are<br>
&gt; starting to get Even Sicker. We have about the same likely<br>
&gt; hood of solving those in MARTINI as we have of solving the<br>
&gt; &quot;preservation of request-URI across contact routing&quot; problem=
.<br>
&gt;<br>
&gt; --<br>
&gt; Dean<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
</div></div><div><div></div><div class=3D"h5">_____________________________=
__________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
</div></div></blockquote></div><br>

--000e0cdff8b42eae3204816e697c--

From ietf.hanserik@gmail.com  Wed Mar 10 01:21:38 2010
Return-Path: <ietf.hanserik@gmail.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 8186F3A676A for <martini@core3.amsl.com>; Wed, 10 Mar 2010 01:21:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 1ei9D30NPJ0h for <martini@core3.amsl.com>; Wed, 10 Mar 2010 01:21:32 -0800 (PST)
Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216]) by core3.amsl.com (Postfix) with ESMTP id 2D3C93A65A6 for <martini@ietf.org>; Wed, 10 Mar 2010 01:21:27 -0800 (PST)
Received: by ewy8 with SMTP id 8so1184301ewy.28 for <martini@ietf.org>; Wed, 10 Mar 2010 01:21:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=J5T9hBpZlO2O2kFPuVBTYuqCTx8e5elg09u6vHVJW/A=; b=mQI0pzTEU5COJamyYJJ0gTCd/V8bio7hFAwMtaCsCcoP2KsJeML9lQqMFMp8x/OGa8 BJm0G5IO0yMIJrLd1MbjfkqTSAUYcxegl0CaVd2oX/jwz367x7C5xmCuJ7jJG5Pnbnks EBx12AOvUu5kaM/JKcEMa5I5HhQKRz0Ff6mIc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=R/PjNtUzjGov+g7KsZyfEZOU5QVBMQQsdjo4Z8AcVkaOXEt6L3O4iRMDpAZGc+So5S VNbeL5GfgnRaCrpm3JDtLSkybb01naWHAN/oPurKncREqozu882Rm+jADCa9BCXZzFNW mjdzl7cA5CEKs1m2Z4kXBSeD/2MR51LNA91hE=
MIME-Version: 1.0
Received: by 10.213.104.19 with SMTP id m19mr710877ebo.40.1268212888004; Wed,  10 Mar 2010 01:21:28 -0800 (PST)
In-Reply-To: <9ECCF01B52E7AB408A7EB8535264214101329FB6@ftrdmel0.rd.francetelecom.fr>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl> <EDC0A1AE77C57744B664A310A0B23AE20C19E15F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AFB74521-1DBC-4750-AF59-F88B43352302@softarmor.com> <951_1268125870_4B9610AE_951_114651_3_9ECCF01B52E7AB408A7EB85352642141012FD45D@ftrdmel0.rd.francetelecom.fr> <2BE087AB-0DD5-4024-A837-9DA6597AEDFF@softarmor.com> <9ECCF01B52E7AB408A7EB8535264214101329FB6@ftrdmel0.rd.francetelecom.fr>
Date: Wed, 10 Mar 2010 10:21:27 +0100
Message-ID: <9ae56b1e1003100121v37c83dds727805d1fb5fe92@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: martini@ietf.org
Content-Type: multipart/alternative; boundary=00504502d2d6b0698604816ed297
Subject: Re: [martini] Call for Adoption of "Registration for MultiplePhone Numbers in the SIP"
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: Wed, 10 Mar 2010 09:21:38 -0000

--00504502d2d6b0698604816ed297
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Given the ambitionlevel to only provide a solution for the specific E.164
cases,  why is this drafts intended status "Standards Track"?

Being first made aware of this work group yesterday, surprised to see that =
a
new solution is developed, whereas there exists a standardised solution for
over a year now supporting any target SIP URI (not limited to E.164) alone
and that can easily be modified/adapted/rephrased to work in a more
generalised internet setting.

BR,
/Hans Erik van Elburg

On Tue, Mar 9, 2010 at 8:01 PM, <bruno.chatras@orange-ftgroup.com> wrote:

> Strictly speaking it's not a new interface but in practice it means that =
a
> PBX will find different things in the Request URI of inbound requests
> depending on whether it is connected  to an IMS or a GIN-based network. I=
n
> the first case, the R-URI will contain the original target identity while=
 in
> the second case it will contain this special contact address built as
> described in the GIN draft.
>
> For the rest of my message, there was a typo in it! I intended to write
> that it was too early to accept this document as a WG Work Item but wrote
> WGLC...
>
> If I try to map what I meant to your 4 options, I believe I meant Option =
1:
> I don't like the GIN mechanism in its present form as it does not preserv=
e
> the original target identity in the R-URI and is restricted to E.164
> numbers. However, what you have described as Option 2a is worth discussin=
g.
> The definition of the <subset of the "registering multiple domain-style U=
RIs
> in a single request" problem that can be dealt with using REGISTER> would
> also deserve further discussions. If it turns out that the gin draft can =
be
> extended to support a reasonable subset of the problem then it might beco=
me
> a better candidate for a WG Work Item. This does not solve the R-URI issu=
e
> however.
>
> /BC
>
>
> > -----Message d'origine-----
> > De : Dean Willis [mailto:dean.willis@softarmor.com]
> > Envoy=E9 : mardi 9 mars 2010 18:56
> > =C0 : CHATRAS Bruno RD-CORE-ISS
> > Cc : Keith Drage; MARTINI
> > Objet : Re: [martini] Call for Adoption of "Registration for
> > MultiplePhone Numbers in the SIP"
> >
> >
> > On Mar 9, 2010, at 3:08 AM,
> > <bruno.chatras@orange-ftgroup.com>
> > <bruno.chatras@orange-ftgroup.com  > wrote:
> >
> > > I think the situation is even worse than what Keith has described.
> > > As It's not only "yet another interface to support" but
> > probably TWO
> > > other interfaces as it seems that a different solution will be
> > > required at a later stage for supporting other forms of
> > URIs. I also
> > > think it's too early to go for WGLC.
> >
> > I prefer to think of what GIN is currently doing as simply
> > clarifying and standardizing what can be done with RFC 3261's
> > REGISTER method for single-request registration of multiple
> > phone numbers. This is a matter of converging multiple common
> > implementations into a single standardized approach. It's not
> > a "new" interface, but a cleanup of an underspecified one
> > that already exists.
> >
> > It's true that we aren't proposing (in this document) to
> > standardize registration of multiple domain-style AORs with a
> > single request.
> > We're not agreed that REGISTER is even a reasonable general
> > solution to that problem, nor are we likely to so agree at
> > any time in the near future. Nor are we proposing to solve at
> > this time the fundamental intra-domain or inter-domain
> > routing problems (see current thread in DISPATCH).
> >
> > A second "interface", as you and Keith describe it, is
> > probably required because REGISTER itself is fundamentally
> > unsuited to solving the general routing problem. All we're
> > doing in this document (gin) is the part of the problem that
> > REGISTER can reasonably solve when the target identities are
> > expressed as phone numbers.
> >
> > I'd argue that REGISTER could also be reasonably used for
> > handling registration of multiple domain-style URIs (AORs)
> > when those AOR-URIs are all scoped to the same authentication
> > domain AND the right-hand- side of the contact-URI is
> > identical across all contact-URI's being registered within a
> > single request AND there is a one-to-one mapping between
> > AOR-URI and contact-URI produced in the registrar as a result
> > of the request. This might well be within the scope of
> > MARTINI, and is a completely separable problem. It could be
> > documented in the same RFC, or documented in a second RFC,
> > should we choose to pursue that line of work. I would argue
> > that such an approach would not constitute a separate
> > interface in either case (same or different documents).
> > Each would be a documentation of the REGISTER interface for
> > registering multiple contacts within a single request -- one
> > for multiple domain-style URIs, one for multiple phone
> > numbers within a domain.
> >
> >
> > So, are you saying that:
> >
> > 1) You don't like the GIN mechanism and we shouldn't work
> > from it for solving the multiple phone-number-registration problem.
> >
> > 2) You like the GIN mechanism but don't want to settle on it
> > until we also have a proposal for dealing with the subset of
> > the "registering multiple domain-style URIs in a single
> > request" problem that can be dealt with using REGISTER.
> >
> > 2a) As 2, and you want the proposal for dealing with the
> > subset of the "registering multiple domain-style URIs in a
> > single request" problem that can be dealt with using REGISTER
> > to be incorporated into the same document as the current gin
> > solution before it is adopted as baseline text by the WG.
> >
> > 2b) As 2, and you want the proposal for dealing with the
> > subset of the "registering multiple domain-style URIs in a
> > single request" problem that can be dealt with using REGISTER
> > to be presented in a separate document so that we can adopt
> > them both concurrently.
> >
> > 3) You believe that REGISTER is the "universal hammer" for
> > all SIP routing exchange problems, and are going to  block
> > any partial solution until we all accept that approach and
> > have a written proposal for solving all route-exchange
> > problems using REGISTER.
> >
> > 4) Something entirely different (please specify).
> >
> >
> > And who said anything about WGLC of the solution? We're
> > talking WGLC of the requirements draft, and adoption of the
> > -gin- draft as a baseline text that we will then hammer on
> > until we're ready for WGLC.
> >
> > --
> > Dean
> >
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>

--00504502d2d6b0698604816ed297
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Given the ambitionlevel to only provide a solution for the specific E.164 c=
ases,=A0 why is this drafts intended status &quot;Standards Track&quot;?<br=
><br>Being first made aware of this work group yesterday, surprised to see =
that a new solution is developed, whereas there exists a standardised solut=
ion for over a year now supporting any target SIP URI (not limited to E.164=
) alone and that can easily be modified/adapted/rephrased to work in a more=
 generalised internet setting.<br>
<br>BR,<br clear=3D"all">/Hans Erik van Elburg<br>


<br><div class=3D"gmail_quote">On Tue, Mar 9, 2010 at 8:01 PM,  <span dir=
=3D"ltr">&lt;<a href=3D"mailto:bruno.chatras@orange-ftgroup.com" target=3D"=
_blank">bruno.chatras@orange-ftgroup.com</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204)=
; margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">



Strictly speaking it&#39;s not a new interface but in practice it means tha=
t a PBX will find different things in the Request URI of inbound requests d=
epending on whether it is connected =A0to an IMS or a GIN-based network. In=
 the first case, the R-URI will contain the original target identity while =
in the second case it will contain this special contact address built as de=
scribed in the GIN draft.<br>




<br>
For the rest of my message, there was a typo in it! I intended to write tha=
t it was too early to accept this document as a WG Work Item but wrote WGLC=
...<br>
<br>
If I try to map what I meant to your 4 options, I believe I meant Option 1:=
 I don&#39;t like the GIN mechanism in its present form as it does not pres=
erve the original target identity in the R-URI and is restricted to E.164 n=
umbers. However, what you have described as Option 2a is worth discussing. =
The definition of the &lt;subset of the &quot;registering multiple domain-s=
tyle URIs in a single request&quot; problem that can be dealt with using RE=
GISTER&gt; would also deserve further discussions. If it turns out that the=
 gin draft can be extended to support a reasonable subset of the problem th=
en it might become a better candidate for a WG Work Item. This does not sol=
ve the R-URI issue however.<br>




<br>
/BC<br>
<br>
<br>
&gt; -----Message d&#39;origine-----<br>
&gt; De : Dean Willis [mailto:<a href=3D"mailto:dean.willis@softarmor.com" =
target=3D"_blank">dean.willis@softarmor.com</a>]<br>
&gt; Envoy=E9 : mardi 9 mars 2010 18:56<br>
&gt; =C0 : CHATRAS Bruno RD-CORE-ISS<br>
&gt; Cc : Keith Drage; MARTINI<br>
&gt; Objet : Re: [martini] Call for Adoption of &quot;Registration for<br>
&gt; MultiplePhone Numbers in the SIP&quot;<br>
<div><div></div><div>&gt;<br>
&gt;<br>
&gt; On Mar 9, 2010, at 3:08 AM,<br>
&gt; &lt;<a href=3D"mailto:bruno.chatras@orange-ftgroup.com" target=3D"_bla=
nk">bruno.chatras@orange-ftgroup.com</a>&gt;<br>
&gt; &lt;<a href=3D"mailto:bruno.chatras@orange-ftgroup.com" target=3D"_bla=
nk">bruno.chatras@orange-ftgroup.com</a> =A0&gt; wrote:<br>
&gt;<br>
&gt; &gt; I think the situation is even worse than what Keith has described=
.<br>
&gt; &gt; As It&#39;s not only &quot;yet another interface to support&quot;=
 but<br>
&gt; probably TWO<br>
&gt; &gt; other interfaces as it seems that a different solution will be<br=
>
&gt; &gt; required at a later stage for supporting other forms of<br>
&gt; URIs. I also<br>
&gt; &gt; think it&#39;s too early to go for WGLC.<br>
&gt;<br>
&gt; I prefer to think of what GIN is currently doing as simply<br>
&gt; clarifying and standardizing what can be done with RFC 3261&#39;s<br>
&gt; REGISTER method for single-request registration of multiple<br>
&gt; phone numbers. This is a matter of converging multiple common<br>
&gt; implementations into a single standardized approach. It&#39;s not<br>
&gt; a &quot;new&quot; interface, but a cleanup of an underspecified one<br=
>
&gt; that already exists.<br>
&gt;<br>
&gt; It&#39;s true that we aren&#39;t proposing (in this document) to<br>
&gt; standardize registration of multiple domain-style AORs with a<br>
&gt; single request.<br>
&gt; We&#39;re not agreed that REGISTER is even a reasonable general<br>
&gt; solution to that problem, nor are we likely to so agree at<br>
&gt; any time in the near future. Nor are we proposing to solve at<br>
&gt; this time the fundamental intra-domain or inter-domain<br>
&gt; routing problems (see current thread in DISPATCH).<br>
&gt;<br>
&gt; A second &quot;interface&quot;, as you and Keith describe it, is<br>
&gt; probably required because REGISTER itself is fundamentally<br>
&gt; unsuited to solving the general routing problem. All we&#39;re<br>
&gt; doing in this document (gin) is the part of the problem that<br>
&gt; REGISTER can reasonably solve when the target identities are<br>
&gt; expressed as phone numbers.<br>
&gt;<br>
&gt; I&#39;d argue that REGISTER could also be reasonably used for<br>
&gt; handling registration of multiple domain-style URIs (AORs)<br>
&gt; when those AOR-URIs are all scoped to the same authentication<br>
&gt; domain AND the right-hand- side of the contact-URI is<br>
&gt; identical across all contact-URI&#39;s being registered within a<br>
&gt; single request AND there is a one-to-one mapping between<br>
&gt; AOR-URI and contact-URI produced in the registrar as a result<br>
&gt; of the request. This might well be within the scope of<br>
&gt; MARTINI, and is a completely separable problem. It could be<br>
&gt; documented in the same RFC, or documented in a second RFC,<br>
&gt; should we choose to pursue that line of work. I would argue<br>
&gt; that such an approach would not constitute a separate<br>
&gt; interface in either case (same or different documents).<br>
&gt; Each would be a documentation of the REGISTER interface for<br>
&gt; registering multiple contacts within a single request -- one<br>
&gt; for multiple domain-style URIs, one for multiple phone<br>
&gt; numbers within a domain.<br>
&gt;<br>
&gt;<br>
&gt; So, are you saying that:<br>
&gt;<br>
&gt; 1) You don&#39;t like the GIN mechanism and we shouldn&#39;t work<br>
&gt; from it for solving the multiple phone-number-registration problem.<br=
>
&gt;<br>
&gt; 2) You like the GIN mechanism but don&#39;t want to settle on it<br>
&gt; until we also have a proposal for dealing with the subset of<br>
&gt; the &quot;registering multiple domain-style URIs in a single<br>
&gt; request&quot; problem that can be dealt with using REGISTER.<br>
&gt;<br>
&gt; 2a) As 2, and you want the proposal for dealing with the<br>
&gt; subset of the &quot;registering multiple domain-style URIs in a<br>
&gt; single request&quot; problem that can be dealt with using REGISTER<br>
&gt; to be incorporated into the same document as the current gin<br>
&gt; solution before it is adopted as baseline text by the WG.<br>
&gt;<br>
&gt; 2b) As 2, and you want the proposal for dealing with the<br>
&gt; subset of the &quot;registering multiple domain-style URIs in a<br>
&gt; single request&quot; problem that can be dealt with using REGISTER<br>
&gt; to be presented in a separate document so that we can adopt<br>
&gt; them both concurrently.<br>
&gt;<br>
&gt; 3) You believe that REGISTER is the &quot;universal hammer&quot; for<b=
r>
&gt; all SIP routing exchange problems, and are going to =A0block<br>
&gt; any partial solution until we all accept that approach and<br>
&gt; have a written proposal for solving all route-exchange<br>
&gt; problems using REGISTER.<br>
&gt;<br>
&gt; 4) Something entirely different (please specify).<br>
&gt;<br>
&gt;<br>
&gt; And who said anything about WGLC of the solution? We&#39;re<br>
&gt; talking WGLC of the requirements draft, and adoption of the<br>
&gt; -gin- draft as a baseline text that we will then hammer on<br>
&gt; until we&#39;re ready for WGLC.<br>
&gt;<br>
&gt; --<br>
&gt; Dean<br>
&gt;<br>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
</div></div></blockquote></div><br>

--00504502d2d6b0698604816ed297--

From adam@nostrum.com  Wed Mar 10 09:11:10 2010
Return-Path: <adam@nostrum.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 7147C3A6BFC for <martini@core3.amsl.com>; Wed, 10 Mar 2010 09:11:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, SPF_PASS=-0.001]
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 WnM1UWliTWoo for <martini@core3.amsl.com>; Wed, 10 Mar 2010 09:11:08 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 6DA143A6967 for <martini@ietf.org>; Wed, 10 Mar 2010 09:10:56 -0800 (PST)
Received: from [172.16.3.231] (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o2AHAvNq098157 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Mar 2010 11:10:57 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4B97D2A1.3070403@nostrum.com>
Date: Wed, 10 Mar 2010 11:10:57 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>	<EDC0A1AE77C57744B664A310A0B23AE20C19E15F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	<AFB74521-1DBC-4750-AF59-F88B43352302@softarmor.com>	<951_1268125870_4B9610AE_951_114651_3_9ECCF01B52E7AB408A7EB85352642141012FD45D@ftrdmel0.rd.francetelecom.fr>	<2BE087AB-0DD5-4024-A837-9DA6597AEDFF@softarmor.com>	<9ECCF01B52E7AB408A7EB8535264214101329FB6@ftrdmel0.rd.francetelecom.fr> <9ae56b1e1003100121v37c83dds727805d1fb5fe92@mail.gmail.com>
In-Reply-To: <9ae56b1e1003100121v37c83dds727805d1fb5fe92@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: martini@ietf.org
Subject: Re: [martini] Call for Adoption of "Registration for MultiplePhone Numbers in the SIP"
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: Wed, 10 Mar 2010 17:11:10 -0000

On 3/10/10 3:21 AM, Hans Erik van Elburg wrote:
> Being first made aware of this work group yesterday, surprised to see 
> that a new solution is developed, whereas there exists a standardised 
> solution for over a year now supporting any target SIP URI (not 
> limited to E.164) alone and that can easily be 
> modified/adapted/rephrased to work in a more generalised internet setting.

There has been quite a bit of discussion on the MARTINI mailing list 
since the beginning of the year. Most of it focused on what many of us 
believe are fundamental flaws in the existing approaches. If you really 
want to understand how we got where we are, I suggest you familiarize 
yourself with the discussion to date:

http://www.ietf.org/mail-archive/web/martini/current/mail2.html

The minutes of the three interim meetings we've had this year are also 
good background for the state of things:

http://aboba.drizzlehosting.com/MARTINI/

I don't think any of us are particularly eager to go back to arguing 
over the problems inherent in the currently deployed solutions: many 
participants would like to have something in front of the IESG in the 
first half of 2010, not sometime in late 2013.

/a

From bernard_aboba@hotmail.com  Wed Mar 10 20:22:24 2010
Return-Path: <bernard_aboba@hotmail.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 DFEA63A6AD1 for <martini@core3.amsl.com>; Wed, 10 Mar 2010 20:22:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.902
X-Spam-Level: 
X-Spam-Status: No, score=-0.902 tagged_above=-999 required=5 tests=[AWL=-0.163, BAYES_20=-0.74, HTML_MESSAGE=0.001]
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 DjsbRWAy7YYN for <martini@core3.amsl.com>; Wed, 10 Mar 2010 20:22:21 -0800 (PST)
Received: from blu0-omc2-s9.blu0.hotmail.com (blu0-omc2-s9.blu0.hotmail.com [65.55.111.84]) by core3.amsl.com (Postfix) with ESMTP id CF3493A6A35 for <martini@ietf.org>; Wed, 10 Mar 2010 20:22:20 -0800 (PST)
Received: from BLU137-DS15 ([65.55.111.71]) by blu0-omc2-s9.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 10 Mar 2010 20:22:26 -0800
X-Originating-IP: [32.177.200.106]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS152FACD79E78C9460523D593320@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <martini@ietf.org>
Date: Wed, 10 Mar 2010 20:22:24 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_005E_01CAC08F.65C13E60"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcrA0nOh6uKvC/BfTwaofzWH1iL4sg==
Content-Language: en-us
X-OriginalArrivalTime: 11 Mar 2010 04:22:26.0100 (UTC) FILETIME=[7456EF40:01CAC0D2]
Subject: [martini] REMINDER: Call for Adoption of "Registration for Multiple Phone Numbers in the SIP"
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: Thu, 11 Mar 2010 04:22:25 -0000

------=_NextPart_000_005E_01CAC08F.65C13E60
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

This is a reminder that the IETF MARTINI WG is currently holding a Call for
Adoption of "Registration for Multiple Phone Numbers in the SIP" as a
MARTINI WG work item.  The MARTINI WG Call for Adoption will last until
Friday, March 19, 2010.

More information on the Call for Adoption is available here:

http://www.ietf.org/mail-archive/web/martini/current/msg00916.html

 

Note that the Call for Adoption not only requests WG participants to state
their opinions on whether the GIN document is ready for adoption,   but also
solicits in depth reviews of the draft.   Every comment from editorial NITs
to technical issues is fair game, regardless of how minor (or major) the
issue might be. 

 


------=_NextPart_000_005E_01CAC08F.65C13E60
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>This
is a reminder that the IETF MARTINI WG is currently holding a Call for =
Adoption
of &#8220;Registration for Multiple Phone Numbers in the SIP&#8221; as a
MARTINI WG work item. &nbsp;The MARTINI WG Call for Adoption will last =
until Friday,
March 19, 2010.<o:p></o:p></p>

<p class=3DMsoNormal>More information on the Call for Adoption is =
available here:<o:p></o:p></p>

<p class=3DMsoNormal><a
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00916.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00916.html</a>=
<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Note that the Call for Adoption not only requests =
WG
participants to state their opinions on whether the GIN document is =
ready for
adoption,&nbsp; &nbsp;but also solicits in depth reviews of the =
draft.&nbsp; &nbsp;Every comment
from editorial NITs to technical issues is fair game, regardless of how =
minor
(or major) the issue might be. <o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

------=_NextPart_000_005E_01CAC08F.65C13E60--

From trac@tools.ietf.org  Wed Mar 10 20:29:46 2010
Return-Path: <trac@tools.ietf.org>
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 EC6F73A6816 for <martini@core3.amsl.com>; Wed, 10 Mar 2010 20:29:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.493
X-Spam-Level: 
X-Spam-Status: No, score=-102.493 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 SciR7bkESUvN for <martini@core3.amsl.com>; Wed, 10 Mar 2010 20:29:46 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 382E23A6A4B for <martini@ietf.org>; Wed, 10 Mar 2010 20:29:46 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Npa1u-0005IR-SN; Wed, 10 Mar 2010 20:29:50 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com, bernard_aboba@hotmail.com
X-Trac-Project: martini
Date: Thu, 11 Mar 2010 04:29:50 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/7
Message-ID: <067.5ec62977838b8c119ef7c4f9e3e654c6@tools.ietf.org>
X-Trac-Ticket-ID: 7
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, bernard_aboba@hotmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #7: GIN idnits
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 11 Mar 2010 04:29:47 -0000

#7: GIN idnits
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  adam@…          
     Type:  defect                     |      Status:  new             
 Priority:  minor                      |   Milestone:  milestone1      
Component:  gin                        |     Version:  1.0             
 Severity:  Candidate WG Document      |    Keywords:                  
---------------------------------------+------------------------------------
 idnits output when run on GIN-01:

 idnits 2.12.01

 tmp/draft-roach-martini-gin-01.txt:

   Checking boilerplate required by RFC 5378 and the IETF Trust (see
   http://trustee.ietf.org/license-info):
 ----------------------------------------------------------------------------

   == You're using the IETF Trust Provisions' Section 6.b License Notice
 from
      12 Sep 2009 rather than the newer Notice from 28 Dec 2009.  (See
      http://trustee.ietf.org/license-info/)


   Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt:
 ----------------------------------------------------------------------------

      No issues found here.

   Checking nits according to http://www.ietf.org/id-info/checklist :
 ----------------------------------------------------------------------------

   ** The document seems to lack a Security Considerations section.

   ** The document seems to lack a both a reference to RFC 2119 and the
      recommended RFC 2119 boilerplate, even if it appears to use RFC 2119
      keywords.

      RFC 2119, paragraph 2:
      "The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
       "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
       this document are to be interpreted as described in RFC 2119."

      RFC 2119 keyword, line 187: '...   parameter MUST NOT contain a user
 p...'
      RFC 2119 keyword, line 228: '...REGISTER message MUST be copied to
 the...'
      RFC 2119 keyword, line 318: '...ered bulk number contact, the SSP
 MUST...'
      RFC 2119 keyword, line 421: '...   MUST proxy that SUBSCRIBE to the
 PB...'

   Miscellaneous warnings:
 ----------------------------------------------------------------------------

      No issues found here.

   Checking references for intended status: Proposed Standard
 ----------------------------------------------------------------------------

      (See RFCs 3967 and 4897 for information about using normative
 references
      to lower-maturity documents in RFCs)

      No issues found here.

      Summary: 2 errors (**), 1 warning (==), 0 comments (--).

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/7>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Wed Mar 10 20:55:41 2010
Return-Path: <trac@tools.ietf.org>
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 B54EA3A6A4B for <martini@core3.amsl.com>; Wed, 10 Mar 2010 20:55:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.496
X-Spam-Level: 
X-Spam-Status: No, score=-102.496 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 TYVMfWFxrsu1 for <martini@core3.amsl.com>; Wed, 10 Mar 2010 20:55:40 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id E81273A682B for <martini@ietf.org>; Wed, 10 Mar 2010 20:55:40 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NpaR0-0003ds-7F; Wed, 10 Mar 2010 20:55:46 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com, bernard_aboba@hotmail.com
X-Trac-Project: martini
Date: Thu, 11 Mar 2010 04:55:46 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/8
Message-ID: <067.b839f4a9e00d234c0d2b7572017d3dc0@tools.ietf.org>
X-Trac-Ticket-ID: 8
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, bernard_aboba@hotmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #8: GIN editorial issues
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 11 Mar 2010 04:55:41 -0000

#8: GIN editorial issues
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  adam@…          
     Type:  defect                     |      Status:  new             
 Priority:  trivial                    |   Milestone:  milestone1      
Component:  gin                        |     Version:  1.0             
 Severity:  Candidate WG Document      |    Keywords:                  
---------------------------------------+------------------------------------
 Section 1

  The users registered individual reachability information with the this
 authority, which would then route incoming requests accordingly.

 s/with the this/with this/

 The document "SIP IP-PBX Registration Problems" [3] describes several
 deployed IP PBX registration techniques, along with a number of problems
 that arise from the approaches that have been implemented to date.

 [BA] The reference should probably be to the requirements document.

 Section 2

    These are being defined in
    the MARTINI requirements document.  In terms of impact to the
    solution at hand, the following two constraints have the most
    profound effect: (1) The PBX cannot be assumed to be assigned a
    static IP address; and (2) No DNS entry can be relied upon to
    consistently resolve to the IP address of the PBX.

 [BA] Reference needed.

 Section 3

    This document uses the terms defined in section 2 of "SIP IP-PBX
    Registration Problems" [3].

 [BA] Suggest reference to the Requirements document instead.

 Section 4

 Finally, we non-normatively demonstrate that existing procedures that can
 be used to generate temporary GRUUs for terminals behind the PBX.

 [BA] Suggest "We demonstrate how existing procedures can be used..."

 Section 6

 s/based in such mapping/based on the mapping/

 section 16.6 of RFC 3261.

 [BA] Reference needed.

 Section 7.1.1

    So, for example, when the PBX registers the with the following
    contact header field:

 s/the with/with/

 possibly the URN itself; possible some other identifier

 suggest: "possibly the URN itself or some other identifier"

 This resulting Contact => The resulting Contact

 as defined in section 4.3 of RFC 5627

 [BA] Reference needed

 stable over long => stable over a long

    For example, using the same setup as in the "Public GRUU" section
    above, an extensions registering with the PBX might obtain a temp
    gruu by receiving a Contact header field that looks like:

 [BA] Example needed (section ends abruptly).

 Section 8

 The current sections represents

 s/represents/represent/

 Section 8.1

 s/Wumpus/Usage Scenario/g

 Section 9

 The document "SIP IP-PBX Registration Problems" [3] describes a

 [BA] Change reference to Requirements document.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/8>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Wed Mar 10 20:57:00 2010
Return-Path: <trac@tools.ietf.org>
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 174C73A6A4B for <martini@core3.amsl.com>; Wed, 10 Mar 2010 20:57:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 HCnGTkku7gPP for <martini@core3.amsl.com>; Wed, 10 Mar 2010 20:56:59 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 791A23A682B for <martini@ietf.org>; Wed, 10 Mar 2010 20:56:59 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NpaSG-0003yD-M9; Wed, 10 Mar 2010 20:57:04 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com, bernard_aboba@hotmail.com
X-Trac-Project: martini
Date: Thu, 11 Mar 2010 04:57:04 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/9
Message-ID: <067.b617480425ee58bf2cf3e04cd7c88604@tools.ietf.org>
X-Trac-Ticket-ID: 9
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, bernard_aboba@hotmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #9: IANA considerations
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 11 Mar 2010 04:57:00 -0000

#9: IANA considerations
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  adam@…          
     Type:  defect                     |      Status:  new             
 Priority:  major                      |   Milestone:  milestone1      
Component:  gin                        |     Version:  1.0             
 Severity:  Candidate WG Document      |    Keywords:                  
---------------------------------------+------------------------------------
 10.  IANA Considerations

  This isn't even close to finished.  It's here to remind me that there
  are IANA impacts.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/9>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Wed Mar 10 20:59:00 2010
Return-Path: <trac@tools.ietf.org>
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 44A1D3A6B02 for <martini@core3.amsl.com>; Wed, 10 Mar 2010 20:59:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.502
X-Spam-Level: 
X-Spam-Status: No, score=-102.502 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 UUOL7RR5plDD for <martini@core3.amsl.com>; Wed, 10 Mar 2010 20:58:59 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id AB1FA3A6AC9 for <martini@ietf.org>; Wed, 10 Mar 2010 20:58:59 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NpaUD-00041m-2J; Wed, 10 Mar 2010 20:59:05 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com, bernard_aboba@hotmail.com
X-Trac-Project: martini
Date: Thu, 11 Mar 2010 04:59:05 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/10
Message-ID: <067.2a49b7034245fef91ad2ddf7b60f2826@tools.ietf.org>
X-Trac-Ticket-ID: 10
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, bernard_aboba@hotmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #10: Section 9: Issues Solved
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 11 Mar 2010 04:59:00 -0000

#10: Section 9: Issues Solved
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  adam@…          
     Type:  defect                     |      Status:  new             
 Priority:  major                      |   Milestone:  milestone1      
Component:  gin                        |     Version:  1.0             
 Severity:  Candidate WG Document      |    Keywords:                  
---------------------------------------+------------------------------------
 Going forward, this section should probably evaluate GIN against the
 requirements in the Requirements document.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/10>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Wed Mar 10 21:00:07 2010
Return-Path: <trac@tools.ietf.org>
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 D07C13A688C for <martini@core3.amsl.com>; Wed, 10 Mar 2010 21:00:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.505
X-Spam-Level: 
X-Spam-Status: No, score=-102.505 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 ZlHr-PveTbmO for <martini@core3.amsl.com>; Wed, 10 Mar 2010 21:00:07 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 3FD7F3A659A for <martini@ietf.org>; Wed, 10 Mar 2010 21:00:07 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NpaVH-00045j-R1; Wed, 10 Mar 2010 21:00:11 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com, bernard_aboba@hotmail.com
X-Trac-Project: martini
Date: Thu, 11 Mar 2010 05:00:11 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/11
Message-ID: <067.1dc0363dbc71855d1326f8975eb439ff@tools.ietf.org>
X-Trac-Ticket-ID: 11
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, bernard_aboba@hotmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #11: Section 7.3: Outbound Analysis
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 11 Mar 2010 05:00:07 -0000

#11: Section 7.3: Outbound Analysis
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  adam@…          
     Type:  defect                     |      Status:  new             
 Priority:  major                      |   Milestone:  milestone1      
Component:  gin                        |     Version:  1.0             
 Severity:  Candidate WG Document      |    Keywords:                  
---------------------------------------+------------------------------------
 7.3.  Client-Initiated (Outbound) Connections

    RFC 5626 [7] -- needs analysis.  Some people think it might "just
    work."

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/11>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Wed Mar 10 21:00:52 2010
Return-Path: <trac@tools.ietf.org>
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 53AFA3A688C for <martini@core3.amsl.com>; Wed, 10 Mar 2010 21:00:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.507
X-Spam-Level: 
X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 y2vHsMMyrMPS for <martini@core3.amsl.com>; Wed, 10 Mar 2010 21:00:51 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id B186E3A659A for <martini@ietf.org>; Wed, 10 Mar 2010 21:00:51 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NpaW1-00049g-58; Wed, 10 Mar 2010 21:00:57 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com, bernard_aboba@hotmail.com
X-Trac-Project: martini
Date: Thu, 11 Mar 2010 05:00:57 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/12
Message-ID: <067.324dd7e58954de0f0f6b28cbec329648@tools.ietf.org>
X-Trac-Ticket-ID: 12
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, bernard_aboba@hotmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #12: Section 7.4:  Path
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 11 Mar 2010 05:00:52 -0000

#12: Section 7.4:  Path
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  adam@…          
     Type:  defect                     |      Status:  new             
 Priority:  major                      |   Milestone:  milestone1      
Component:  gin                        |     Version:  1.0             
 Severity:  Candidate WG Document      |    Keywords:                  
---------------------------------------+------------------------------------
 7.4.  Non-Adjacent Contact Registration (Path)

    RFC 3327 [4] -- needs analysis.  Some people think it might "just
    work."

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/12>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Wed Mar 10 21:01:44 2010
Return-Path: <trac@tools.ietf.org>
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 8AF9A3A6AC9 for <martini@core3.amsl.com>; Wed, 10 Mar 2010 21:01:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.51
X-Spam-Level: 
X-Spam-Status: No, score=-102.51 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 LwmQP8bwtpSD for <martini@core3.amsl.com>; Wed, 10 Mar 2010 21:01:43 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id F10233A6A62 for <martini@ietf.org>; Wed, 10 Mar 2010 21:01:43 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NpaWr-0004AR-Cn; Wed, 10 Mar 2010 21:01:49 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com, bernard_aboba@hotmail.com
X-Trac-Project: martini
Date: Thu, 11 Mar 2010 05:01:49 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/13
Message-ID: <067.2daab1a0eeaadd6fa805c57ed66f0b7e@tools.ietf.org>
X-Trac-Ticket-ID: 13
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, bernard_aboba@hotmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #13: Section 7.5:  Service Route
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 11 Mar 2010 05:01:44 -0000

#13: Section 7.5:  Service Route
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  adam@…          
     Type:  defect                     |      Status:  new             
 Priority:  major                      |   Milestone:  milestone1      
Component:  gin                        |     Version:  1.0             
 Severity:  Candidate WG Document      |    Keywords:                  
---------------------------------------+------------------------------------
 7.5.  Service Route Discovery

    RFC 3608 [5] -- needs analysis.  Some people think it might "just
    work."

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/13>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Wed Mar 10 21:24:49 2010
Return-Path: <trac@tools.ietf.org>
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 4B2BC3A6A4C for <martini@core3.amsl.com>; Wed, 10 Mar 2010 21:24:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.512
X-Spam-Level: 
X-Spam-Status: No, score=-102.512 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 nf1DVRjRMmml for <martini@core3.amsl.com>; Wed, 10 Mar 2010 21:24:48 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 8FFE73A6A62 for <martini@ietf.org>; Wed, 10 Mar 2010 21:24:47 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Npat9-0008MG-LP; Wed, 10 Mar 2010 21:24:51 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com, bernard_aboba@hotmail.com
X-Trac-Project: martini
Date: Thu, 11 Mar 2010 05:24:51 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/14
Message-ID: <067.1bb7d53ea30d51340c8bb804b8a8feb9@tools.ietf.org>
X-Trac-Ticket-ID: 14
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, bernard_aboba@hotmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #14: Section 8: Examples
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 11 Mar 2010 05:24:49 -0000

#14: Section 8: Examples
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  adam@…          
     Type:  defect                     |      Status:  new             
 Priority:  minor                      |   Milestone:  milestone1      
Component:  gin                        |     Version:                  
 Severity:  Candidate WG Document      |    Keywords:                  
---------------------------------------+------------------------------------
 These will be fleshed out more in later versions of the draft, with
 explanations of the processing performed at each step.  For the time
 being, they just show the basic syntax described above.

 [BA] Do we really need detailed explanations of the processing at each
 step?

 Section 8.1

    REGISTER sip:ssp.example.com SIP/2.0
    Via: SIP/2.0/UDP 198.51.100.3:5060;branch=z9hG4bKnashds7
    Max-Forwards: 70
    To: <sip:pbx@ssp.example.com>
    From: <sip:pbx@ssp.example.com>;tag=a23589
    Call-ID: 843817637684230@998sdasdh09
    CSeq: 1826 REGISTER
    Require: bulk-number-contact
    Contact: <sip:198.51.100.3:5060;user=phone;bnc>
    Expires: 7200
    Content-Length: 0

 [BA] Do we need a Proxy-Require: header in the examples as well?

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/14>
martini <http://tools.ietf.org/martini/>


From kpfleming@digium.com  Thu Mar 11 08:11:27 2010
Return-Path: <kpfleming@digium.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 330F93A6BAE for <martini@core3.amsl.com>; Thu, 11 Mar 2010 08:11:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 4GLR8MXp8zWe for <martini@core3.amsl.com>; Thu, 11 Mar 2010 08:11:25 -0800 (PST)
Received: from mail.digium.com (mail.digium.com [216.207.245.2]) by core3.amsl.com (Postfix) with ESMTP id 6EC003A6977 for <martini@ietf.org>; Thu, 11 Mar 2010 08:10:31 -0800 (PST)
Received: from zimbra.digium.internal ([10.24.55.203] helo=zimbra.hsv.digium.com) by mail.digium.com with esmtp (Exim 4.69) (envelope-from <kpfleming@digium.com>) id 1Npky4-0001gN-6W; Thu, 11 Mar 2010 10:10:36 -0600
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.hsv.digium.com (Postfix) with ESMTP id 23AA9D8004; Thu, 11 Mar 2010 10:10:36 -0600 (CST)
Received: from zimbra.hsv.digium.com ([127.0.0.1]) by localhost (zimbra.hsv.digium.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EDNXPv0wdzzs; Thu, 11 Mar 2010 10:10:35 -0600 (CST)
Received: from [10.24.250.46] (unknown [10.24.250.46]) by zimbra.hsv.digium.com (Postfix) with ESMTPSA id D2779D8003; Thu, 11 Mar 2010 10:10:35 -0600 (CST)
Message-ID: <4B9915FB.3020405@digium.com>
Date: Thu, 11 Mar 2010 10:10:35 -0600
From: "Kevin P. Fleming" <kpfleming@digium.com>
Organization: Digium, Inc.
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
In-Reply-To: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
X-Enigmail-Version: 0.95.7
OpenPGP: id=05FB8DB2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 'MARTINI' <martini@ietf.org>
Subject: Re: [martini] Call for Adoption of "Registration for Multiple Phone Numbers in the SIP"
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: Thu, 11 Mar 2010 16:11:27 -0000

Bernard Aboba wrote:

> Please respond to this WG Call for Adoption, whether you are in favor of
> adopting the document as a MARTINI WG work item or not.  If you have no
> comments, please reply to this message and indicate in the body of your
> message whether you think the document is ready for adoption as a
> MARTINI WG work item or not.   Based on the response, the MARTINI WG
> chairs will attempt to determine whether WG consensus exists to adopt
> the document or not.

I am in favor of this document being adopted as a WG item as-is.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kfleming@digium.com
Check us out at www.digium.com & www.asterisk.org

From spencer@wonderhamster.org  Fri Mar 12 14:56:46 2010
Return-Path: <spencer@wonderhamster.org>
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 DC0303A686E for <martini@core3.amsl.com>; Fri, 12 Mar 2010 14:56:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.296
X-Spam-Level: 
X-Spam-Status: No, score=-2.296 tagged_above=-999 required=5 tests=[AWL=0.302,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 I4E7y03R2kbm for <martini@core3.amsl.com>; Fri, 12 Mar 2010 14:56:46 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 254BF3A6868 for <martini@ietf.org>; Fri, 12 Mar 2010 14:56:41 -0800 (PST)
Received: from S73602b ([12.172.14.11]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0ML6Fd-1NqUtm204P-000Vic; Fri, 12 Mar 2010 17:56:46 -0500
Message-ID: <D5BAF166177346FE89DD96B4496AC580@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Bernard Aboba" <bernard_aboba@hotmail.com>, <martini@ietf.org>
References: <BLU137-DS423A4ED594DFDFD1147FE93360@phx.gbl>
Date: Fri, 12 Mar 2010 16:56:41 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_128E_01CAC204.FD12B5C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1/uUqX897DJPSxXpm+zFX6lwyDe8SI+BRkFsD5 XIXpjv4hQ9KnTNFHb8Tmzx0L3/I5p3amKWPcXX7DYJO9HVCRhZ yfKQD+PQGvMmqsrI4kpbiHFNeBJFno3pBrnMWePodo=
Subject: Re: [martini] IETF 77  Agenda - Take Two
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: Fri, 12 Mar 2010 22:56:46 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_128E_01CAC204.FD12B5C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I have posted an HTML version of this agenda (reformatted but unchanged) =
at http://www.ietf.org/proceedings/10mar/agenda/martini.html...

Spencer
  ----- Original Message -----=20
  From: Bernard Aboba=20
  To: martini@ietf.org=20
  Sent: Saturday, March 06, 2010 9:35 PM
  Subject: [martini] IETF 77 Agenda - Take Two


  MARTINI WG Meeting Slot I

  Monday, March 22, 2010

  1 PM - 3 PM Pacific Time

  Palos Verdes Room

  =20

  Jabber room:  martini at jabber.ietf.org (Please join)

  =20

  Agenda

  =20

  1 PM - 1:10 PM:  Preliminaries

       Blue Sheets

       Note Takers

       Note Well

       Agenda bash

       Document Status

  =20

  Requirements (40 minutes)

  =20

  1:10 PM - 1:50 PM, MARTINI Requirements, John Elwell (40 minutes)

  http://tools.ietf.org/html/draft-elwell-martini-reqs

  =20

  Solution Updates (30 minutes)

  =20

  1:50 PM - 2:20 PM, MARTINI with Globally Identifiable Numbers, Adam =
Roach (30 minutes)

  http://tools.ietf.org/html/draft-roach-martini-gin

  =20

  Discussion (20 minutes)

  =20

  2:20 PM - 2:40 PM Discussion:  Participants (30 minutes)

  =20

  Wrap-up (20 minutes)

  =20

  2:40 PM - 2:50 PM  Hums:  WG Chairs (10 minutes)

  2:50 PM - 3:00 PM  Next Steps:  WG Chairs & ADs (10 minutes)

  =20

  MARTINI WG Meeting Slot II

  Friday, March 26, 2010

  1415 - 1515 Pacific Time

  California D

  =20

  Nothing scheduled at the moment (will cancel if time slot is not =
needed)



-------------------------------------------------------------------------=
-----


  _______________________________________________
  martini mailing list
  martini@ietf.org
  https://www.ietf.org/mailman/listinfo/martini

------=_NextPart_000_128E_01CAC204.FD12B5C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18876">
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: =
11pt
}
LI.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: =
11pt
}
DIV.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: =
11pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
PRE {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"; FONT-SIZE: 10pt; =
mso-style-priority: 99; mso-style-link: "HTML Preformatted Char"
}
SPAN.HTMLPreformattedChar {
	FONT-FAMILY: "Courier New"; mso-style-priority: 99; mso-style-link: =
"HTML Preformatted"; mso-style-name: "HTML Preformatted Char"
}
SPAN.EmailStyle19 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: =
personal
}
SPAN.EmailStyle20 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: =
personal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US link=3Dblue bgColor=3D#ffffff vLink=3Dpurple>
<DIV><FONT size=3D2>I have posted an HTML version of this agenda =
(reformatted but=20
unchanged) at <A=20
href=3D"http://www.ietf.org/proceedings/10mar/agenda/martini.html"><FONT =

size=3D3>http://www.ietf.org/proceedings/10mar/agenda/martini.html</FONT>=
</A>...</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Spencer</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; =
PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: =
black"><B>From:</B>=20
  <A title=3Dbernard_aboba@hotmail.com=20
  href=3D"mailto:bernard_aboba@hotmail.com">Bernard Aboba</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Dmartini@ietf.org =

  href=3D"mailto:martini@ietf.org">martini@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Saturday, March 06, 2010 =
9:35=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [martini] IETF 77 =
Agenda - Take=20
  Two</DIV>
  <DIV><BR></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">MARTINI WG=20
  Meeting Slot I<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">Monday,=20
  March 22, 2010<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: 10pt">1 =
PM =96 3 PM=20
  Pacific Time<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">Palos Verdes=20
  Room<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">Jabber=20
  room:&nbsp; martini at jabber.ietf.org (Please =
join)<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">Agenda<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: 10pt">1 =
PM =96 1:10=20
  PM:&nbsp; Preliminaries<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">&nbsp;&nbsp;&nbsp;&nbsp;=20
  Blue Sheets<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">&nbsp;&nbsp;&nbsp;&nbsp;=20
  Note Takers<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">&nbsp;&nbsp;&nbsp;&nbsp;=20
  Note Well<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">&nbsp;&nbsp;&nbsp;&nbsp;=20
  Agenda bash<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">&nbsp;&nbsp;&nbsp;&nbsp;=20
  Document Status<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">Requirements=20
  (40 minutes)<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">1:10 PM =96=20
  1:50 PM, MARTINI Requirements, John Elwell (</SPAN><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: #1f497d; FONT-SIZE: =
10pt">4</SPAN><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: 10pt">0=20
  minutes)<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">http://tools.ietf.org/html/draft-elwell-martini-reqs<o:p></o:p></SP=
AN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">Solution=20
  Updates (30 minutes)<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">1:50 PM =96=20
  2:20 PM, MARTINI with Globally Identifiable Numbers, Adam Roach (30=20
  minutes)<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">http://tools.ietf.org/html/draft-roach-martini-gin<o:p></o:p></SPAN=
></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">Discussion=20
  (20 minutes)<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">2:20 PM =96=20
  2:40 PM Discussion:&nbsp; Participants (30 =
minutes)<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">Wrap-up (20=20
  minutes)<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">2:40 PM =96=20
  2:50 PM&nbsp; Hums:&nbsp; WG Chairs (10 minutes)<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">2:50 PM =96=20
  3:00 PM &nbsp;Next Steps:&nbsp; WG Chairs &amp; ADs (10=20
  minutes)<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: =
black"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">MARTINI WG=20
  Meeting Slot II<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">Friday,=20
  March 26, 2010<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">1415 - 1515=20
  Pacific Time<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">California=20
  D<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: =
10pt">Nothing=20
  scheduled at the moment (will cancel if time slot is not =
needed)</SPAN><SPAN=20
  style=3D"COLOR: black"><o:p></o:p></SPAN></P></DIV>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>martini =
mailing=20
  =
list<BR>martini@ietf.org<BR>https://www.ietf.org/mailman/listinfo/martini=
<BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_128E_01CAC204.FD12B5C0--


From BLINDSAY@nortel.com  Wed Mar 17 06:51:30 2010
Return-Path: <BLINDSAY@nortel.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 A1CD63A682B for <martini@core3.amsl.com>; Wed, 17 Mar 2010 06:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.504
X-Spam-Level: 
X-Spam-Status: No, score=-3.504 tagged_above=-999 required=5 tests=[AWL=-0.636, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=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 SOaSiCYbRuUg for <martini@core3.amsl.com>; Wed, 17 Mar 2010 06:51:23 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id ED5433A69A6 for <martini@ietf.org>; Wed, 17 Mar 2010 06:51:16 -0700 (PDT)
Received: from zcarhxm1.corp.nortel.com (zcarhxm1.corp.nortel.com [47.129.230.97]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id o2HDpLf12572; Wed, 17 Mar 2010 13:51:21 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAC5D8.EC4C640C"
Date: Wed, 17 Mar 2010 09:51:19 -0400
Message-ID: <09B7DBFE70A9E24BBB21689DAD3A06141CF400B7@zcarhxm1.corp.nortel.com>
In-Reply-To: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] Call for Adoption of "Registration for Multiple PhoneNumbers in the SIP"
Thread-Index: Acq75lzynCu/RB4MSc6T2IL3e5RvlAJ8JC4Q
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
From: "Brian Lindsay" <blindsay@nortel.com>
To: "Bernard Aboba" <bernard_aboba@hotmail.com>, "MARTINI" <martini@ietf.org>
Subject: Re: [martini] Call for Adoption of "Registration for Multiple PhoneNumbers in the SIP"
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: Wed, 17 Mar 2010 13:51:30 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CAC5D8.EC4C640C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Bernard,
=20
   I think the gin draft could form the basis of a solution, but at as
couple of other folks have noted there already is a solution
standardized by TIPAN/3GPP which uses a different approach for request
routing for SIP PBXs. It would be ideal if we had one common approach in
the industry, otherwise we are going to see some carriers require one
solution and other carriers the other solution and vendors on both the
enterprise and carrier side will need to implement and support both.
=20
   The shaken draft is closer to the TISPAN/3GPP approach and is
essentially adding some incremental improvements. I'd be more inclined
to go with the shaken appoach at this time given it's alignment with the
existing standardized TISPAN/3GPP solution.
=20
   I haven't heard too many other responses on the call for adoption
from SSP vendors so I'm curious on that front what others are thinking.
=20
   Thanks
       Brian

________________________________

From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On
Behalf Of Bernard Aboba
Sent: Thursday, March 04, 2010 5:02 PM
To: 'MARTINI'
Subject: [martini] Call for Adoption of "Registration for Multiple
PhoneNumbers in the SIP"



This is a MARTINI WG Call for Adoption of "Registration for Multiple
Phone Numbers in the SIP" as a MARTINI WG work item, corresponding to
the "Multiple AoR Registration specification" Charter deliverable.  The
document is available for inspection here:=20

http://tools.ietf.org/html/draft-roach-martini-gin-01.txt

The MARTINI WG Call for Adoption will last until Friday, March 19, 2010.

Please respond to this WG Call for Adoption, whether you are in favor of
adopting the document as a MARTINI WG work item or not.  If you have no
comments, please reply to this message and indicate in the body of your
message whether you think the document is ready for adoption as a
MARTINI WG work item or not.   Based on the response, the MARTINI WG
chairs will attempt to determine whether WG consensus exists to adopt
the document or not.=20

If you have comments, please provide them to the WG in one of the
following ways:=20

1.      The preferred choice is to open an issue in the MARTINI Issue
tracking database (TRAC), which is available here:
http://trac.tools.ietf.org/wg/martini/trac/newticket
<http://trac.tools.ietf.org/wg/martini/trac/newticket>   Information on
how to use TRAC is provided below.  Note that if you submit an issue in
TRAC, it will automatically also be posted to the MARTINI WG mailing
list.  When submitting issues in TRAC for this "call for adoption",
please enter "gin" for the Component: and "Candidate WG Document" for
Severity. =20

 2. If you can't figure out how to use TRAC, please post your Issue to
the MARTINI WG mailing list (martini at ietf.org) in the following
format:=20

To:  martini at ietf.org

Subject: GIN-Issue: <title of your issue>

Priority: blocker, critical, major, minor or trivial

<Explanation of your issue, including a proposal for specific text
changes to resolve the issue>

The MARTINI WG uses the TRAC database to keep track of issues relating
to work in progress, including working group work items and individual
submissions undergoing review.    This document provides some basic
information on how MARTINI WG participants can use TRAC to submit or
edit issues. =20

Documentation relating to the TRAC Issue Tracking database is available
here:

http://trac.tools.ietf.org/wg/martini/trac/wiki

Since this documentation is somewhat lengthy (and mostly relevant to
Admins), here is a pithy synopsis.=20

1.       To submit an issue in the MARTINI Issues database (known as
TRAC), you first need to login to the MARTINI WG site on the tools
server (http://tools.ietf.org/wg/martini/trac/login )=20

2.       If you don't already have a login ID, you can obtain one by
navigating to this site:   http://trac.tools.ietf.org/newlogin

3.       Once you have obtained an account, you can log in by clicking
on the "login" entry at the top of the page.  Once you have logged in,
you can file an issue by navigating to the  ticket entry form:
http://trac.tools.ietf.org/wg/martini/trac/newticket
<http://trac.tools.ietf.org/wg/martini/trac/newticket>=20

4     When opening an issue:=20

a.       The Type: field should be set to "defect" for an issue with the
current document text, or "enhancement" for a proposed addition of
functionality (such as an additional requirement).=20

b.      The Priority: field is set based on the severity of the Issue.
For example, editorial issues are typically "minor" or "trivial".=20

c.       The Milestone: field should be set to milestone1 (useless, I
know).=20

d.      The Component: field should be set to the document you are
filing the issue on.  In responding to the GIN Call for Adoption, "gin"
is the appropriate choice.

e.      The Version: field should be set to "1.0".=20

f.        The Severity: field should be set to based on the status of
the document (e.g. "Candidate WG Document" in this case)

g.        The Keywords: and CC: fields can be left blank unless
inspiration seizes you.=20

h.      The Assign To: field is generally filled in with the email
address of the editor.=20

5.       Typically it won't be necessary to enclose a file with the
ticket, but if you need to, select "I have files to attach to this
ticket".=20

6.       If you want to preview your Issue, click on the "Preview"
button.  When you're ready to submit the issue, click on the "Create
Ticket" button.=20

That's it! =20

If you have an problems in dealing with TRAC, send email to me and I'll
try to figure out what's going on.=20

Happy TRACing,

Bernard

=20


------_=_NextPart_001_01CAC5D8.EC4C640C
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoListParagraph {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman","serif"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-style-priority: 34
}
LI.MsoListParagraph {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman","serif"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-style-priority: 34
}
DIV.MsoListParagraph {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman","serif"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-style-priority: 34
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D531033713-17032010>Hi=20
Bernard,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D531033713-17032010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D531033713-17032010>&nbsp;&nbsp; I think the gin draft could form =
the basis=20
of a solution, but at as couple of other folks have noted there already =
is a=20
solution standardized by TIPAN/3GPP which uses a different approach for =
request=20
routing for SIP PBXs. It would be ideal if we had one common approach in =
the=20
industry, otherwise we are going to see some carriers require one =
solution and=20
other carriers the other solution and vendors on both the enterprise and =
carrier=20
side will need to&nbsp;implement and support both.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D531033713-17032010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D531033713-17032010>&nbsp;&nbsp; The shaken draft is closer to =
the=20
TISPAN/3GPP approach and is essentially adding some incremental =
improvements.=20
I'd be more inclined to go with the shaken appoach at this time given =
it's=20
alignment with the existing standardized TISPAN/3GPP=20
solution.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D531033713-17032010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D531033713-17032010>&nbsp;&nbsp; I haven't heard too many other =
responses=20
on the call for adoption&nbsp;from SSP vendors so I'm curious on that =
front what=20
others are thinking.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D531033713-17032010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D531033713-17032010>&nbsp;&nbsp; Thanks</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D531033713-17032010>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Brian</SPAN></FONT></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> martini-bounces@ietf.org=20
[mailto:martini-bounces@ietf.org] <B>On Behalf Of </B>Bernard=20
Aboba<BR><B>Sent:</B> Thursday, March 04, 2010 5:02 PM<BR><B>To:</B>=20
'MARTINI'<BR><B>Subject:</B> [martini] Call for Adoption of =
"Registration for=20
Multiple PhoneNumbers in the SIP"<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">This is =
a MARTINI=20
WG Call for Adoption of &#8220;Registration for Multiple Phone Numbers =
in the SIP&#8221; as=20
a MARTINI WG work item, corresponding to the &#8220;Multiple AoR =
Registration=20
specification&#8221; Charter deliverable. &nbsp;The document is =
available for=20
inspection here: <o:p></o:p></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><A=20
href=3D"http://tools.ietf.org/html/draft-roach-martini-gin-01.txt">http:/=
/tools.ietf.org/html/draft-roach-martini-gin-01.txt</A><o:p></o:p></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">The =
MARTINI WG=20
Call for Adoption will last until Friday, March 19, 2010.<o:p></o:p></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Please =
respond to=20
this WG Call for Adoption, whether you are in favor of adopting the =
document as=20
a MARTINI WG work item or not. &nbsp;If you have no comments, please =
reply to=20
this message and indicate in the body of your message whether you think =
the=20
document is ready for adoption as a MARTINI WG work item or not.=20
&nbsp;&nbsp;Based on the response, the MARTINI WG chairs will attempt to =

determine whether WG consensus exists to adopt the document or not.=20
<o:p></o:p></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">If you =
have=20
comments, please provide them to the WG in one of the following ways:=20
<o:p></o:p></P>
<P class=3DMsoListParagraph style=3D"MARGIN-LEFT: 21pt; TEXT-INDENT: =
-0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: =
'Calibri','sans-serif'">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The preferred choice is to open an issue in the MARTINI Issue tracking =
database=20
(TRAC), which is available here: <A=20
href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><SPAN=20
style=3D"COLOR: =
black">http://trac.tools.ietf.org/wg/martini/trac/newticket</SPAN></A>=20
&nbsp;Information on how to use TRAC is provided below.&nbsp; Note that =
if you=20
submit an issue in TRAC, it will automatically also be posted to the =
MARTINI WG=20
mailing list. &nbsp;When submitting issues in TRAC for this &#8220;call =
for adoption&#8221;,=20
please enter &#8220;gin&#8221; for the Component: and &#8220;Candidate =
WG Document&#8221; for=20
Severity.&nbsp; <o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
style=3D"COLOR: black">&nbsp;2. If you can&#8217;t figure out how to use =
TRAC, please=20
post your Issue to the MARTINI WG mailing list (martini at ietf.org) in =
the=20
following format: <o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'">To:&nbsp; martini at=20
ietf.org</SPAN><o:p></o:p></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'">Subject: GIN-Issue: &lt;title of =
your=20
issue&gt;</SPAN><o:p></o:p></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'">Priority: blocker, critical, major, =
minor or=20
trivial</SPAN><o:p></o:p></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'">&lt;Explanation of your issue, =
including a=20
proposal for specific text changes to resolve the=20
issue&gt;</SPAN><o:p></o:p></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=20
style=3D"COLOR: black">The MARTINI WG uses the TRAC database to keep =
track of=20
issues relating to work in progress, including working group work items =
and=20
individual submissions undergoing review. &nbsp;&nbsp;&nbsp;This =
document=20
provides some basic information on how MARTINI WG participants can use =
TRAC to=20
submit or edit issues.&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: =
auto">Documentation=20
relating to the TRAC Issue Tracking database is available =
here:<o:p></o:p></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><A=20
href=3D"http://trac.tools.ietf.org/wg/martini/trac/wiki">http://trac.tool=
s.ietf.org/wg/martini/trac/wiki</A><o:p></o:p></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Since =
this=20
documentation is somewhat lengthy (and mostly relevant to Admins), here =
is a=20
pithy synopsis. <o:p></o:p></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; FONT-FAMILY: =
'Calibri','sans-serif'">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
To submit an issue in the MARTINI Issues database (known as TRAC), you =
first=20
need to login to the MARTINI WG site on the tools server (<A=20
href=3D"http://tools.ietf.org/wg/martini/trac/login">http://tools.ietf.or=
g/wg/martini/trac/login</A>=20
) <o:p></o:p></SPAN></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; FONT-FAMILY: =
'Calibri','sans-serif'">2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
If you don&#8217;t already have a login ID, you can obtain one by =
navigating to this=20
site: &nbsp;&nbsp;<A=20
href=3D"http://trac.tools.ietf.org/newlogin">http://trac.tools.ietf.org/n=
ewlogin</A><o:p></o:p></SPAN></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">3<SPAN=20
style=3D"COLOR: black">.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Once you =
have=20
obtained an account, you can log in by clicking on the =
&#8220;login&#8221; entry at the top=20
of the page.&nbsp; Once you have logged in, you can file an issue by =
navigating=20
to the &nbsp;ticket entry form: <A=20
href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><SPAN=20
style=3D"COLOR: =
black">http://trac.tools.ietf.org/wg/martini/trac/newticket</SPAN></A><o:=
p></o:p></SPAN></SPAN></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">4<SPAN=20
style=3D"COLOR: #1f497d">&nbsp;&nbsp;&nbsp; </SPAN>&nbsp;When opening an =

issue:&nbsp;<o:p></o:p></SPAN></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; FONT-FAMILY: =
'Calibri','sans-serif'">a.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The Type: field should be set to &#8220;defect&#8221; for an issue with =
the current document=20
text, or &#8220;enhancement&#8221; for a proposed addition of =
functionality (such as an=20
additional requirement). <o:p></o:p></SPAN></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; FONT-FAMILY: =
'Calibri','sans-serif'">b.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The Priority: field is set based on the severity of the =
Issue.&nbsp;&nbsp; For=20
example, editorial issues are typically &#8220;minor&#8221; or =
&#8220;trivial&#8221;.=20
<o:p></o:p></SPAN></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">c<SPAN=20
style=3D"COLOR: black">.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The =
Milestone: field=20
should be set to milestone1 (useless, I know). =
<o:p></o:p></SPAN></SPAN></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: =
'Calibri','sans-serif'">d.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The Component: field should be set to the document you are filing the =
issue=20
on.&nbsp; In responding to the GIN Call for Adoption, &#8220;gin&#8221; =
is the appropriate=20
choice.<o:p></o:p></SPAN></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: =
'Calibri','sans-serif'">e.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The Version: field should be set to &#8220;1.0&#8221;. =
<o:p></o:p></SPAN></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: =
'Calibri','sans-serif'">f.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The Severity: field should be set to based on the status of the document =
(e.g.=20
&#8220;Candidate WG Document&#8221; in this case)<o:p></o:p></SPAN></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: =
'Calibri','sans-serif'">g.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;The Keywords: and CC: fields can be left blank unless inspiration =
seizes=20
you. <o:p></o:p></SPAN></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: =
'Calibri','sans-serif'">h.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The Assign To: field is generally filled in with the email address of =
the=20
editor. <o:p></o:p></SPAN></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; FONT-FAMILY: =
'Calibri','sans-serif'">5.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Typically it won&#8217;t be necessary to enclose a file with the ticket, =
but if you=20
need to, select &#8220;I have files to attach to this ticket&#8221;. =
<o:p></o:p></SPAN></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -0.25in"><SPAN=20
style=3D"FONT-SIZE: 11pt; FONT-FAMILY: =
'Calibri','sans-serif'">6.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
If you want to preview your Issue, click on the &#8220;Preview&#8221; =
button.&nbsp; When=20
you&#8217;re ready to submit the issue, click on the &#8220;Create =
Ticket&#8221; button.=20
<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: =
auto">That&#8217;s it!&nbsp;=20
<SPAN style=3D"COLOR: #1f497d"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">If you =
have an=20
problems in dealing with TRAC, send email to me and I&#8217;ll try to =
figure out=20
what&#8217;s going on. <SPAN style=3D"COLOR: =
#1f497d"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">Happy=20
TRACing,<SPAN style=3D"COLOR: #1f497d"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal>Bernard<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P></DIV></BODY></HTML>

------_=_NextPart_001_01CAC5D8.EC4C640C--

From bernard_aboba@hotmail.com  Wed Mar 17 07:23:57 2010
Return-Path: <bernard_aboba@hotmail.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 D83CA3A6967 for <martini@core3.amsl.com>; Wed, 17 Mar 2010 07:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.035
X-Spam-Level: 
X-Spam-Status: No, score=0.035 tagged_above=-999 required=5 tests=[AWL=-1.097,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 kSg4-UxQiCuL for <martini@core3.amsl.com>; Wed, 17 Mar 2010 07:23:56 -0700 (PDT)
Received: from blu0-omc2-s3.blu0.hotmail.com (blu0-omc2-s3.blu0.hotmail.com [65.55.111.78]) by core3.amsl.com (Postfix) with ESMTP id 39A4628C167 for <martini@ietf.org>; Wed, 17 Mar 2010 07:12:51 -0700 (PDT)
Received: from BLU137-W18 ([65.55.111.72]) by blu0-omc2-s3.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 17 Mar 2010 07:13:01 -0700
Message-ID: <BLU137-W1824D141F59B4CABCD016F932C0@phx.gbl>
Content-Type: multipart/alternative; boundary="_12e803c3-de98-431f-b9c4-8a399ac837d1_"
X-Originating-IP: [67.201.119.8]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <martini@ietf.org>
Date: Wed, 17 Mar 2010 07:13:01 -0700
Importance: Normal
In-Reply-To: <006201cac0d2$758758f0$60960ad0$@com>
References: <006201cac0d2$758758f0$60960ad0$@com>
MIME-Version: 1.0
X-OriginalArrivalTime: 17 Mar 2010 14:13:01.0098 (UTC) FILETIME=[F3B908A0:01CAC5DB]
Subject: [martini] REMINDER:  MARTINI WG Call for Adoption
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: Wed, 17 Mar 2010 14:23:58 -0000

--_12e803c3-de98-431f-b9c4-8a399ac837d1_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable







This
is a reminder that the IETF MARTINI WG is currently holding a Call for Adop=
tion
of =93Registration for Multiple Phone Numbers in the SIP=94 as a
MARTINI WG work item.  The MARTINI WG Call for Adoption will last until
Friday=2C March 19=2C 2010.

More information on the Call for Adoption is available here:

http://www.ietf.org/mail-archive/web/martini/current/msg00916.html

=20

Note that the Call for Adoption not only requests WG
participants to state their opinions on whether the GIN document is ready f=
or
adoption=2C   but also solicits in depth reviews of the draft.   Every
comment from editorial NITs to technical issues is fair game=2C regardless =
of how
minor (or major) the issue might be.=20

 		 	   		  =

--_12e803c3-de98-431f-b9c4-8a399ac837d1_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
<br>



<style>
.ExternalClass .ecxhmmessage P
{padding:0px=3B}
.ExternalClass body.ecxhmmessage
{font-size:10pt=3Bfont-family:Verdana=3B}</style>This
is a reminder that the IETF MARTINI WG is currently holding a Call for Adop=
tion
of =93Registration for Multiple Phone Numbers in the SIP=94 as a
MARTINI WG work item. &nbsp=3BThe MARTINI WG Call for Adoption will last un=
til
Friday=2C March 19=2C 2010.<div class=3D"ecxecxSection1">

<p class=3D"ecxecxMsoNormal">More information on the Call for Adoption is a=
vailable here:</p>

<p class=3D"ecxecxMsoNormal"><a href=3D"http://www.ietf.org/mail-archive/we=
b/martini/current/msg00916.html">http://www.ietf.org/mail-archive/web/marti=
ni/current/msg00916.html</a></p>

<p class=3D"ecxecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxecxMsoNormal">Note that the Call for Adoption not only reque=
sts WG
participants to state their opinions on whether the GIN document is ready f=
or
adoption=2C&nbsp=3B &nbsp=3Bbut also solicits in depth reviews of the draft=
.&nbsp=3B &nbsp=3BEvery
comment from editorial NITs to technical issues is fair game=2C regardless =
of how
minor (or major) the issue might be. </p>

</div> 		 	   		  </body>
</html>=

--_12e803c3-de98-431f-b9c4-8a399ac837d1_--

From ben@nostrum.com  Wed Mar 17 15:01:56 2010
Return-Path: <ben@nostrum.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 406E73A68A6 for <martini@core3.amsl.com>; Wed, 17 Mar 2010 15:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.034
X-Spam-Level: 
X-Spam-Status: No, score=-2.034 tagged_above=-999 required=5 tests=[AWL=-0.565, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, SPF_PASS=-0.001]
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 Ac90xb505tnn for <martini@core3.amsl.com>; Wed, 17 Mar 2010 15:01:54 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 30EF23A6855 for <martini@ietf.org>; Wed, 17 Mar 2010 15:01:53 -0700 (PDT)
Received: from dn3-174.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o2HM22cT087222 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 17 Mar 2010 17:02:02 -0500 (CDT) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: multipart/alternative; boundary=Apple-Mail-4-645829594
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
Date: Wed, 17 Mar 2010 17:02:01 -0500
Message-Id: <FE1A8148-4670-4BB4-B4C2-3CE38E787233@nostrum.com>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl>
To: Bernard Aboba <bernard_aboba@hotmail.com>
X-Mailer: Apple Mail (2.1077)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: 'MARTINI' <martini@ietf.org>
Subject: Re: [martini] Call for Adoption of "Registration for Multiple Phone Numbers in the SIP"
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: Wed, 17 Mar 2010 22:01:56 -0000

--Apple-Mail-4-645829594
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252



On Mar 4, 2010, at 4:02 PM, Bernard Aboba wrote:

> This is a MARTINI WG Call for Adoption of =93Registration for Multiple =
Phone Numbers in the SIP=94 as a MARTINI WG work item, corresponding to =
the =93Multiple AoR Registration specification=94 Charter deliverable.  =
The document is available for inspection here:
> http://tools.ietf.org/html/draft-roach-martini-gin-01.txt
> The MARTINI WG Call for Adoption will last until Friday, March 19, =
2010.
>=20

I'm in favor of adoption.=

--Apple-Mail-4-645829594
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><br></div><br><div><div>On Mar 4, 2010, at 4:02 PM, Bernard Aboba =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; ">This is a MARTINI WG Call for =
Adoption of =93Registration for Multiple Phone Numbers in the SIP=94 as =
a MARTINI WG work item, corresponding to the =93Multiple AoR =
Registration specification=94 Charter deliverable. &nbsp;The document is =
available for inspection here:<o:p></o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif; "><a =
href=3D"http://tools.ietf.org/html/draft-roach-martini-gin-01.txt" =
style=3D"color: blue; text-decoration: underline; =
">http://tools.ietf.org/html/draft-roach-martini-gin-01.txt</a><o:p></o:p>=
</div><div style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: =
0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif; ">The MARTINI WG Call for Adoption will last until Friday, =
March 19, 2010.<o:p></o:p></div></span><br =
class=3D"Apple-interchange-newline"></blockquote></div><br><div>I'm in =
favor of adoption.</div></body></html>=

--Apple-Mail-4-645829594--

From jan.van.geel@belgacom.be  Thu Mar 18 01:07:54 2010
Return-Path: <jan.van.geel@belgacom.be>
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 7CCD83A6ACE for <martini@core3.amsl.com>; Thu, 18 Mar 2010 01:07:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.883
X-Spam-Level: *
X-Spam-Status: No, score=1.883 tagged_above=-999 required=5 tests=[AWL=0.937,  BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 D4os6mLTQ9Sy for <martini@core3.amsl.com>; Thu, 18 Mar 2010 01:07:46 -0700 (PDT)
Received: from inmxcar02.belgacom.be (inmxcar02.belgacom.be [195.13.11.185]) by core3.amsl.com (Postfix) with ESMTP id 716023A68FC for <martini@ietf.org>; Thu, 18 Mar 2010 01:06:16 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.51,265,1267398000"; d="scan'208,217";a="48888344"
Received: from unknown (HELO A03008.BGC.NET) ([10.121.129.162]) by outmxcar02.belgacom.be with ESMTP; 18 Mar 2010 09:06:22 +0100
X-TM-IMSS-Message-ID: <029800020000333b@belgacom.be>
Received: from AE7212.BGC.NET ([45.223.1.31]) by belgacom.be ([10.121.129.162]) with ESMTP (TREND IMSS SMTP Service 7.0; TLS: TLSv1/SSLv3,128bits,RC4-MD5) id 029800020000333b ; Thu, 18 Mar 2010 09:06:21 +0100
Received: from CMS03.BGC.NET ([10.120.128.133]) by AE7212.BGC.NET ([45.223.1.31]) with mapi; Thu, 18 Mar 2010 09:06:21 +0100
From: <jan.van.geel@belgacom.be>
To: <blindsay@nortel.com>, <bernard_aboba@hotmail.com>, <martini@ietf.org>
Date: Thu, 18 Mar 2010 09:06:20 +0100
Thread-Topic: [martini] Call for Adoption of "Registration for Multiple PhoneNumbers in the SIP"
Thread-Index: Acq75lzynCu/RB4MSc6T2IL3e5RvlAJ8JC4QACa1dFA=
Message-ID: <208EAE1DFA28FC419529619ABB8622441616E6C19B@CMS03.BGC.NET>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl> <09B7DBFE70A9E24BBB21689DAD3A06141CF400B7@zcarhxm1.corp.nortel.com>
In-Reply-To: <09B7DBFE70A9E24BBB21689DAD3A06141CF400B7@zcarhxm1.corp.nortel.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
x-tm-as-product-ver: SMEX-8.0.0.1285-6.000.1038-17258.003
x-tm-as-result: No--58.659200-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_208EAE1DFA28FC419529619ABB8622441616E6C19BCMS03BGCNET_"
MIME-Version: 1.0
Subject: Re: [martini] Call for Adoption of "Registration for Multiple	PhoneNumbers in the SIP"
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: Thu, 18 Mar 2010 08:07:54 -0000

--_000_208EAE1DFA28FC419529619ABB8622441616E6C19BCMS03BGCNET_
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

As=20service=20provider=20I=20completely=20agree=20with=20the=20statement=
=20that=20a=20common=20approach=20is=20beneficial=20for=20the=20industry.=
=20Therefore=20I=20would=20prefer=20that=20alignment=20with=20existing=20=
specifications=20of=203GPP/ETSI=20is=20sought=20as=20much=20as=20possible=
.

Kind=20regards


Jan=20Van=20Geel
IT=20and=20Network=20Development=20Specialist
Belgacom=20SDE/SDV/PSE/NST/NCP
Tel:=20+32=202=20202=201035
Tel:=20+32=202=20207=204442
Tel:=20+32=202=20207=209032
Email=20:=20jan.van.geel@belgacom.be
www.cyberwezz.tk


From:=20martini-bounces@ietf.org=20[mailto:martini-bounces@ietf.org]=20On=
=20Behalf=20Of=20Brian=20Lindsay
Sent:=2017=20March=202010=2014:51
To:=20Bernard=20Aboba;=20MARTINI
Subject:=20Re:=20[martini]=20Call=20for=20Adoption=20of=20"Registration=
=20for=20Multiple=20PhoneNumbers=20in=20the=20SIP"

Hi=20Bernard,

=20=20=20I=20think=20the=20gin=20draft=20could=20form=20the=20basis=20of=
=20a=20solution,=20but=20at=20as=20couple=20of=20other=20folks=20have=20n=
oted=20there=20already=20is=20a=20solution=20standardized=20by=20TIPAN/3G=
PP=20which=20uses=20a=20different=20approach=20for=20request=20routing=20=
for=20SIP=20PBXs.=20It=20would=20be=20ideal=20if=20we=20had=20one=20commo=
n=20approach=20in=20the=20industry,=20otherwise=20we=20are=20going=20to=
=20see=20some=20carriers=20require=20one=20solution=20and=20other=20carri=
ers=20the=20other=20solution=20and=20vendors=20on=20both=20the=20enterpri=
se=20and=20carrier=20side=20will=20need=20to=20implement=20and=20support=
=20both.

=20=20=20The=20shaken=20draft=20is=20closer=20to=20the=20TISPAN/3GPP=20ap=
proach=20and=20is=20essentially=20adding=20some=20incremental=20improveme=
nts.=20I'd=20be=20more=20inclined=20to=20go=20with=20the=20shaken=20appoa=
ch=20at=20this=20time=20given=20it's=20alignment=20with=20the=20existing=
=20standardized=20TISPAN/3GPP=20solution.

=20=20=20I=20haven't=20heard=20too=20many=20other=20responses=20on=20the=
=20call=20for=20adoption=20from=20SSP=20vendors=20so=20I'm=20curious=20on=
=20that=20front=20what=20others=20are=20thinking.

=20=20=20Thanks
=20=20=20=20=20=20=20Brian

________________________________
From:=20martini-bounces@ietf.org=20[mailto:martini-bounces@ietf.org]=20On=
=20Behalf=20Of=20Bernard=20Aboba
Sent:=20Thursday,=20March=2004,=202010=205:02=20PM
To:=20'MARTINI'
Subject:=20[martini]=20Call=20for=20Adoption=20of=20"Registration=20for=
=20Multiple=20PhoneNumbers=20in=20the=20SIP"
This=20is=20a=20MARTINI=20WG=20Call=20for=20Adoption=20of=20"Registration=
=20for=20Multiple=20Phone=20Numbers=20in=20the=20SIP"=20as=20a=20MARTINI=
=20WG=20work=20item,=20corresponding=20to=20the=20"Multiple=20AoR=20Regis=
tration=20specification"=20Charter=20deliverable.=20=20The=20document=20i=
s=20available=20for=20inspection=20here:
http://tools.ietf.org/html/draft-roach-martini-gin-01.txt
The=20MARTINI=20WG=20Call=20for=20Adoption=20will=20last=20until=20Friday=
,=20March=2019,=202010.
Please=20respond=20to=20this=20WG=20Call=20for=20Adoption,=20whether=20yo=
u=20are=20in=20favor=20of=20adopting=20the=20document=20as=20a=20MARTINI=
=20WG=20work=20item=20or=20not.=20=20If=20you=20have=20no=20comments,=20p=
lease=20reply=20to=20this=20message=20and=20indicate=20in=20the=20body=20=
of=20your=20message=20whether=20you=20think=20the=20document=20is=20ready=
=20for=20adoption=20as=20a=20MARTINI=20WG=20work=20item=20or=20not.=20=20=
=20Based=20on=20the=20response,=20the=20MARTINI=20WG=20chairs=20will=20at=
tempt=20to=20determine=20whether=20WG=20consensus=20exists=20to=20adopt=
=20the=20document=20or=20not.
If=20you=20have=20comments,=20please=20provide=20them=20to=20the=20WG=20i=
n=20one=20of=20the=20following=20ways:

1.=20=20=20=20=20=20The=20preferred=20choice=20is=20to=20open=20an=20issu=
e=20in=20the=20MARTINI=20Issue=20tracking=20database=20(TRAC),=20which=20=
is=20available=20here:=20http://trac.tools.ietf.org/wg/martini/trac/newti=
cket=20=20Information=20on=20how=20to=20use=20TRAC=20is=20provided=20belo=
w.=20=20Note=20that=20if=20you=20submit=20an=20issue=20in=20TRAC,=20it=20=
will=20automatically=20also=20be=20posted=20to=20the=20MARTINI=20WG=20mai=
ling=20list.=20=20When=20submitting=20issues=20in=20TRAC=20for=20this=20"=
call=20for=20adoption",=20please=20enter=20"gin"=20for=20the=20Component:=
=20and=20"Candidate=20WG=20Document"=20for=20Severity.
=202.=20If=20you=20can't=20figure=20out=20how=20to=20use=20TRAC,=20please=
=20post=20your=20Issue=20to=20the=20MARTINI=20WG=20mailing=20list=20(mart=
ini=20at=20ietf.org)=20in=20the=20following=20format:
To:=20=20martini=20at=20ietf.org
Subject:=20GIN-Issue:=20<title=20of=20your=20issue>
Priority:=20blocker,=20critical,=20major,=20minor=20or=20trivial
<Explanation=20of=20your=20issue,=20including=20a=20proposal=20for=20spec=
ific=20text=20changes=20to=20resolve=20the=20issue>
The=20MARTINI=20WG=20uses=20the=20TRAC=20database=20to=20keep=20track=20o=
f=20issues=20relating=20to=20work=20in=20progress,=20including=20working=
=20group=20work=20items=20and=20individual=20submissions=20undergoing=20r=
eview.=20=20=20=20This=20document=20provides=20some=20basic=20information=
=20on=20how=20MARTINI=20WG=20participants=20can=20use=20TRAC=20to=20submi=
t=20or=20edit=20issues.
Documentation=20relating=20to=20the=20TRAC=20Issue=20Tracking=20database=
=20is=20available=20here:
http://trac.tools.ietf.org/wg/martini/trac/wiki
Since=20this=20documentation=20is=20somewhat=20lengthy=20(and=20mostly=20=
relevant=20to=20Admins),=20here=20is=20a=20pithy=20synopsis.

1.=20=20=20=20=20=20=20To=20submit=20an=20issue=20in=20the=20MARTINI=20Is=
sues=20database=20(known=20as=20TRAC),=20you=20first=20need=20to=20login=
=20to=20the=20MARTINI=20WG=20site=20on=20the=20tools=20server=20(http://t=
ools.ietf.org/wg/martini/trac/login=20)

2.=20=20=20=20=20=20=20If=20you=20don't=20already=20have=20a=20login=20ID=
,=20you=20can=20obtain=20one=20by=20navigating=20to=20this=20site:=20=20=
=20http://trac.tools.ietf.org/newlogin

3.=20=20=20=20=20=20=20Once=20you=20have=20obtained=20an=20account,=20you=
=20can=20log=20in=20by=20clicking=20on=20the=20"login"=20entry=20at=20the=
=20top=20of=20the=20page.=20=20Once=20you=20have=20logged=20in,=20you=20c=
an=20file=20an=20issue=20by=20navigating=20to=20the=20=20ticket=20entry=
=20form:=20http://trac.tools.ietf.org/wg/martini/trac/newticket

4=20=20=20=20=20When=20opening=20an=20issue:

a.=20=20=20=20=20=20=20The=20Type:=20field=20should=20be=20set=20to=20"de=
fect"=20for=20an=20issue=20with=20the=20current=20document=20text,=20or=
=20"enhancement"=20for=20a=20proposed=20addition=20of=20functionality=20(=
such=20as=20an=20additional=20requirement).

b.=20=20=20=20=20=20The=20Priority:=20field=20is=20set=20based=20on=20the=
=20severity=20of=20the=20Issue.=20=20=20For=20example,=20editorial=20issu=
es=20are=20typically=20"minor"=20or=20"trivial".

c.=20=20=20=20=20=20=20The=20Milestone:=20field=20should=20be=20set=20to=
=20milestone1=20(useless,=20I=20know).

d.=20=20=20=20=20=20The=20Component:=20field=20should=20be=20set=20to=20t=
he=20document=20you=20are=20filing=20the=20issue=20on.=20=20In=20respondi=
ng=20to=20the=20GIN=20Call=20for=20Adoption,=20"gin"=20is=20the=20appropr=
iate=20choice.

e.=20=20=20=20=20=20The=20Version:=20field=20should=20be=20set=20to=20"1.=
0".

f.=20=20=20=20=20=20=20=20The=20Severity:=20field=20should=20be=20set=20t=
o=20based=20on=20the=20status=20of=20the=20document=20(e.g.=20"Candidate=
=20WG=20Document"=20in=20this=20case)

g.=20=20=20=20=20=20=20=20The=20Keywords:=20and=20CC:=20fields=20can=20be=
=20left=20blank=20unless=20inspiration=20seizes=20you.

h.=20=20=20=20=20=20The=20Assign=20To:=20field=20is=20generally=20filled=
=20in=20with=20the=20email=20address=20of=20the=20editor.

5.=20=20=20=20=20=20=20Typically=20it=20won't=20be=20necessary=20to=20enc=
lose=20a=20file=20with=20the=20ticket,=20but=20if=20you=20need=20to,=20se=
lect=20"I=20have=20files=20to=20attach=20to=20this=20ticket".

6.=20=20=20=20=20=20=20If=20you=20want=20to=20preview=20your=20Issue,=20c=
lick=20on=20the=20"Preview"=20button.=20=20When=20you're=20ready=20to=20s=
ubmit=20the=20issue,=20click=20on=20the=20"Create=20Ticket"=20button.
That's=20it!
If=20you=20have=20an=20problems=20in=20dealing=20with=20TRAC,=20send=20em=
ail=20to=20me=20and=20I'll=20try=20to=20figure=20out=20what's=20going=20o=
n.
Happy=20TRACing,
Bernard


****=20DISCLAIMER=20****
http://www.belgacom.be/maildisclaimer

--_000_208EAE1DFA28FC419529619ABB8622441616E6C19BCMS03BGCNET_
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html=20xmlns:v=3D"urn:schemas-microsoft-com:vml"=20xmlns:o=3D"urn:schema=
s-microsoft-com:office:office"=20xmlns:w=3D"urn:schemas-microsoft-com:off=
ice:word"=20xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"=
=20xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META=20HTTP-EQUIV=3D"Content-Type"=20CONTENT=3D"text/html;=20charset=3Du=
s-ascii">
<meta=20name=3DGenerator=20content=3D"Microsoft=20Word=2012=20(filtered=
=20medium)">
<!--[if=20!mso]>
<style>
v\:*=20{behavior:url(#default#VML);}
o\:*=20{behavior:url(#default#VML);}
w\:*=20{behavior:url(#default#VML);}
.shape=20{behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
=20/*=20Font=20Definitions=20*/
=20@font-face
=09{font-family:Calibri;
=09panose-1:2=2015=205=202=202=202=204=203=202=204;}
@font-face
=09{font-family:Tahoma;
=09panose-1:2=2011=206=204=203=205=204=204=202=204;}
@font-face
=09{font-family:Verdana;
=09panose-1:2=2011=206=204=203=205=204=204=202=204;}
=20/*=20Style=20Definitions=20*/
=20p.MsoNormal,=20li.MsoNormal,=20div.MsoNormal
=09{margin:0cm;
=09margin-bottom:.0001pt;
=09font-size:11.0pt;
=09font-family:"Calibri","sans-serif";}
a:link,=20span.MsoHyperlink
=09{mso-style-priority:99;
=09color:blue;
=09text-decoration:underline;}
a:visited,=20span.MsoHyperlinkFollowed
=09{mso-style-priority:99;
=09color:purple;
=09text-decoration:underline;}
p.MsoListParagraph,=20li.MsoListParagraph,=20div.MsoListParagraph
=09{mso-style-priority:34;
=09mso-margin-top-alt:auto;
=09margin-right:0cm;
=09mso-margin-bottom-alt:auto;
=09margin-left:0cm;
=09font-size:12.0pt;
=09font-family:"Times=20New=20Roman","serif";}
span.EmailStyle18
=09{mso-style-type:personal;
=09font-family:"Calibri","sans-serif";
=09color:windowtext;}
span.EmailStyle19
=09{mso-style-type:personal-reply;
=09font-family:"Verdana","sans-serif";
=09color:blue;
=09font-weight:normal;
=09font-style:normal;
=09text-decoration:none=20none;}
.MsoChpDefault
=09{mso-style-type:export-only;
=09font-size:10.0pt;}
@page=20WordSection1
=09{size:612.0pt=20792.0pt;
=09margin:72.0pt=2072.0pt=2072.0pt=2072.0pt;}
div.WordSection1
=09{page:WordSection1;}
-->
</style>
<!--[if=20gte=20mso=209]><xml>
=20<o:shapedefaults=20v:ext=3D"edit"=20spidmax=3D"1026"=20/>
</xml><![endif]--><!--[if=20gte=20mso=209]><xml>
=20<o:shapelayout=20v:ext=3D"edit">
=20=20<o:idmap=20v:ext=3D"edit"=20data=3D"1"=20/>
=20</o:shapelayout></xml><![endif]-->
</head>

<body=20lang=3DEN-GB=20link=3Dblue=20vlink=3Dpurple>

<div=20class=3DWordSection1>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'>Hi,<o:p></o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'>As=20service=20provider=20I=20completely=20agree=20with=20the=
=20statement=20that=20a
common=20approach=20is=20beneficial=20for=20the=20industry.=20Therefore=
=20I=20would=20prefer=20that
alignment=20with=20existing=20specifications=20of=203GPP/ETSI=20is=20soug=
ht=20as=20much=20as
possible.<o:p></o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'>Kind=20regards<o:p></o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

<p=20class=3DMsoNormal><b><span=20style=3D'font-size:12.0pt;font-family:"=
Arial","sans-serif";
color:blue'>Jan=20Van=20Geel</span></b><span=20style=3D'font-size:12.0pt;=
font-family:
"Times=20New=20Roman","serif";color:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"=
;
color:blue'>IT=20and=20Network=20Development=20Specialist</span><span=20s=
tyle=3D'font-size:
12.0pt;font-family:"Times=20New=20Roman","serif";color:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"=
;
color:blue'>Belgacom=20SDE/SDV/PSE/NST/NCP</span><span=20style=3D'font-si=
ze:12.0pt;
font-family:"Times=20New=20Roman","serif";color:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"=
;
color:blue'>Tel:=20+32=202=20202=201035</span><span=20style=3D'font-size:=
12.0pt;font-family:
"Times=20New=20Roman","serif";color:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"=
;
color:blue'>Tel:=20+32=202=20207=204442</span><span=20style=3D'font-size:=
12.0pt;font-family:
"Times=20New=20Roman","serif";color:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"=
;
color:blue'>Tel:=20+32=202=20207=209032</span><span=20style=3D'font-size:=
12.0pt;font-family:
"Times=20New=20Roman","serif";color:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"=
;
color:blue'>Email=20:=20jan.van.geel@belgacom.be</span><span=20style=3D'f=
ont-size:12.0pt;
font-family:"Times=20New=20Roman","serif";color:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"=
;
color:blue'>www.cyberwezz.tk</span><span=20style=3D'font-size:12.0pt;font=
-family:
"Times=20New=20Roman","serif";color:blue'>=20</span><span=20style=3D'font=
-size:9.0pt;
font-family:"Verdana","sans-serif";color:blue'><o:p></o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

<div>

<div=20style=3D'border:none;border-top:solid=20#B5C4DF=201.0pt;padding:3.=
0pt=200cm=200cm=200cm'>

<p=20class=3DMsoNormal><b><span=20lang=3DEN-US=20style=3D'font-size:10.0p=
t;font-family:
"Tahoma","sans-serif"'>From:</span></b><span=20lang=3DEN-US=20style=3D'fo=
nt-size:10.0pt;
font-family:"Tahoma","sans-serif"'>=20martini-bounces@ietf.org
[mailto:martini-bounces@ietf.org]=20<b>On=20Behalf=20Of=20</b>Brian=20Lin=
dsay<br>
<b>Sent:</b>=2017=20March=202010=2014:51<br>
<b>To:</b>=20Bernard=20Aboba;=20MARTINI<br>
<b>Subject:</b>=20Re:=20[martini]=20Call=20for=20Adoption=20of=20&quot;Re=
gistration=20for
Multiple=20PhoneNumbers=20in=20the=20SIP&quot;<o:p></o:p></span></p>

</div>

</div>

<p=20class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p=20class=3DMsoNormal><span=20lang=3DEN-US=20style=3D'font-size:10.0pt;f=
ont-family:"Arial","sans-serif";
color:blue'>Hi=20Bernard,</span><span=20lang=3DEN-US=20style=3D'font-size=
:12.0pt;
font-family:"Times=20New=20Roman","serif"'><o:p></o:p></span></p>

</div>

<div>

<p=20class=3DMsoNormal><span=20lang=3DEN-US=20style=3D'font-size:12.0pt;f=
ont-family:"Times=20New=20Roman","serif"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p=20class=3DMsoNormal><span=20lang=3DEN-US=20style=3D'font-size:10.0pt;f=
ont-family:"Arial","sans-serif";
color:blue'>&nbsp;&nbsp;=20I=20think=20the=20gin=20draft=20could=20form=
=20the=20basis=20of=20a
solution,=20but=20at=20as=20couple=20of=20other=20folks=20have=20noted=20=
there=20already=20is=20a
solution=20standardized=20by=20TIPAN/3GPP=20which=20uses=20a=20different=
=20approach=20for=20request
routing=20for=20SIP=20PBXs.=20It=20would=20be=20ideal=20if=20we=20had=20o=
ne=20common=20approach=20in=20the
industry,=20otherwise=20we=20are=20going=20to=20see=20some=20carriers=20r=
equire=20one=20solution=20and
other=20carriers=20the=20other=20solution=20and=20vendors=20on=20both=20t=
he=20enterprise=20and
carrier=20side=20will=20need=20to&nbsp;implement=20and=20support=20both.<=
/span><span
lang=3DEN-US=20style=3D'font-size:12.0pt;font-family:"Times=20New=20Roman=
","serif"'><o:p></o:p></span></p>

</div>

<div>

<p=20class=3DMsoNormal><span=20lang=3DEN-US=20style=3D'font-size:12.0pt;f=
ont-family:"Times=20New=20Roman","serif"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p=20class=3DMsoNormal><span=20lang=3DEN-US=20style=3D'font-size:10.0pt;f=
ont-family:"Arial","sans-serif";
color:blue'>&nbsp;&nbsp;=20The=20shaken=20draft=20is=20closer=20to=20the=
=20TISPAN/3GPP=20approach
and=20is=20essentially=20adding=20some=20incremental=20improvements.=20I'=
d=20be=20more=20inclined
to=20go=20with=20the=20shaken=20appoach=20at=20this=20time=20given=20it's=
=20alignment=20with=20the
existing=20standardized=20TISPAN/3GPP=20solution.</span><span=20lang=3DEN=
-US
style=3D'font-size:12.0pt;font-family:"Times=20New=20Roman","serif"'><o:p=
></o:p></span></p>

</div>

<div>

<p=20class=3DMsoNormal><span=20lang=3DEN-US=20style=3D'font-size:12.0pt;f=
ont-family:"Times=20New=20Roman","serif"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p=20class=3DMsoNormal><span=20lang=3DEN-US=20style=3D'font-size:10.0pt;f=
ont-family:"Arial","sans-serif";
color:blue'>&nbsp;&nbsp;=20I=20haven't=20heard=20too=20many=20other=20res=
ponses=20on=20the=20call
for=20adoption&nbsp;from=20SSP=20vendors=20so=20I'm=20curious=20on=20that=
=20front=20what=20others=20are
thinking.</span><span=20lang=3DEN-US=20style=3D'font-size:12.0pt;font-fam=
ily:"Times=20New=20Roman","serif"'><o:p></o:p></span></p>

</div>

<div>

<p=20class=3DMsoNormal><span=20lang=3DEN-US=20style=3D'font-size:12.0pt;f=
ont-family:"Times=20New=20Roman","serif"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p=20class=3DMsoNormal><span=20lang=3DEN-US=20style=3D'font-size:10.0pt;f=
ont-family:"Arial","sans-serif";
color:blue'>&nbsp;&nbsp;=20Thanks</span><span=20lang=3DEN-US=20style=3D'f=
ont-size:12.0pt;
font-family:"Times=20New=20Roman","serif"'><o:p></o:p></span></p>

</div>

<div>

<p=20class=3DMsoNormal><span=20lang=3DEN-US=20style=3D'font-size:10.0pt;f=
ont-family:"Arial","sans-serif";
color:blue'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20Brian</span><span=20la=
ng=3DEN-US
style=3D'font-size:12.0pt;font-family:"Times=20New=20Roman","serif"'><o:p=
></o:p></span></p>

</div>

<p=20class=3DMsoNormal><span=20lang=3DEN-US=20style=3D'font-size:12.0pt;f=
ont-family:"Times=20New=20Roman","serif"'><o:p>&nbsp;</o:p></span></p>

<div=20class=3DMsoNormal=20align=3Dcenter=20style=3D'text-align:center'><=
span=20lang=3DEN-US
style=3D'font-size:12.0pt;font-family:"Times=20New=20Roman","serif"'>

<hr=20size=3D2=20width=3D"100%"=20align=3Dcenter>

</span></div>

<p=20class=3DMsoNormal=20style=3D'margin-bottom:12.0pt'><b><span=20lang=
=3DEN-US
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
lang=3DEN-US=20style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif=
"'>
martini-bounces@ietf.org=20[mailto:martini-bounces@ietf.org]=20<b>On=20Be=
half=20Of=20</b>Bernard
Aboba<br>
<b>Sent:</b>=20Thursday,=20March=2004,=202010=205:02=20PM<br>
<b>To:</b>=20'MARTINI'<br>
<b>Subject:</b>=20[martini]=20Call=20for=20Adoption=20of=20&quot;Registra=
tion=20for=20Multiple
PhoneNumbers=20in=20the=20SIP&quot;</span><span=20lang=3DEN-US=20style=3D=
'font-size:12.0pt;
font-family:"Times=20New=20Roman","serif"'><o:p></o:p></span></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>This=20is=20a=20MARTINI=20WG=20Call=20for=20Adoption=20of=20=
&#8220;Registration=20for=20Multiple
Phone=20Numbers=20in=20the=20SIP&#8221;=20as=20a=20MARTINI=20WG=20work=20=
item,=20corresponding=20to=20the
&#8220;Multiple=20AoR=20Registration=20specification&#8221;=20Charter=20d=
eliverable.=20&nbsp;The
document=20is=20available=20for=20inspection=20here:=20<o:p></o:p></span>=
</p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US><a=20href=3D"http://tools.ietf.org/html/draft-roach-martini-=
gin-01.txt">http://tools.ietf.org/html/draft-roach-martini-gin-01.txt</a>=
<o:p></o:p></span></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>The=20MARTINI=20WG=20Call=20for=20Adoption=20will=20last=20u=
ntil=20Friday,=20March=2019,
2010.<o:p></o:p></span></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>Please=20respond=20to=20this=20WG=20Call=20for=20Adoption,=
=20whether=20you=20are=20in
favor=20of=20adopting=20the=20document=20as=20a=20MARTINI=20WG=20work=20i=
tem=20or=20not.=20&nbsp;If=20you
have=20no=20comments,=20please=20reply=20to=20this=20message=20and=20indi=
cate=20in=20the=20body=20of=20your
message=20whether=20you=20think=20the=20document=20is=20ready=20for=20ado=
ption=20as=20a=20MARTINI=20WG
work=20item=20or=20not.=20&nbsp;&nbsp;Based=20on=20the=20response,=20the=
=20MARTINI=20WG=20chairs=20will
attempt=20to=20determine=20whether=20WG=20consensus=20exists=20to=20adopt=
=20the=20document=20or=20not.=20<o:p></o:p></span></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>If=20you=20have=20comments,=20please=20provide=20them=20to=
=20the=20WG=20in=20one=20of=20the
following=20ways:=20<o:p></o:p></span></p>

<p=20class=3DMsoListParagraph=20style=3D'margin-left:21.0pt;text-indent:-=
18.0pt'><span
lang=3DEN-US=20style=3D'font-size:11.0pt;font-family:"Calibri","sans-seri=
f";
color:black'>1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20The=20preferred=20choice=
=20is=20to=20open
an=20issue=20in=20the=20MARTINI=20Issue=20tracking=20database=20(TRAC),=
=20which=20is=20available
here:=20<a=20href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket=
"><span
style=3D'color:black'>http://trac.tools.ietf.org/wg/martini/trac/newticke=
t</span></a>
&nbsp;Information=20on=20how=20to=20use=20TRAC=20is=20provided=20below.&n=
bsp;=20Note=20that=20if=20you
submit=20an=20issue=20in=20TRAC,=20it=20will=20automatically=20also=20be=
=20posted=20to=20the=20MARTINI=20WG
mailing=20list.=20&nbsp;When=20submitting=20issues=20in=20TRAC=20for=20th=
is=20&#8220;call=20for
adoption&#8221;,=20please=20enter=20&#8220;gin&#8221;=20for=20the=20Compo=
nent:=20and=20&#8220;Candidate=20WG=20Document&#8221;
for=20Severity.&nbsp;=20<o:p></o:p></span></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'color:black'>&nbsp;2.=20If=20you=20can&#8217;t=20=
figure=20out=20how=20to=20use
TRAC,=20please=20post=20your=20Issue=20to=20the=20MARTINI=20WG=20mailing=
=20list=20(martini=20at
ietf.org)=20in=20the=20following=20format:=20<o:p></o:p></span></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'font-family:"Courier=20New"'>To:&nbsp;=20martini=
=20at=20ietf.org</span><span
lang=3DEN-US><o:p></o:p></span></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'font-family:"Courier=20New"'>Subject:=20GIN-Issue=
:=20&lt;title=20of
your=20issue&gt;</span><span=20lang=3DEN-US><o:p></o:p></span></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'font-family:"Courier=20New"'>Priority:=20blocker,=
=20critical,
major,=20minor=20or=20trivial</span><span=20lang=3DEN-US><o:p></o:p></spa=
n></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'font-family:"Courier=20New"'>&lt;Explanation=20of=
=20your=20issue,
including=20a=20proposal=20for=20specific=20text=20changes=20to=20resolve=
=20the=20issue&gt;</span><span
lang=3DEN-US><o:p></o:p></span></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'color:black'>The=20MARTINI=20WG=20uses=20the=20TR=
AC=20database=20to=20keep
track=20of=20issues=20relating=20to=20work=20in=20progress,=20including=
=20working=20group=20work
items=20and=20individual=20submissions=20undergoing=20review.=20&nbsp;&nb=
sp;&nbsp;This
document=20provides=20some=20basic=20information=20on=20how=20MARTINI=20W=
G=20participants=20can=20use
TRAC=20to=20submit=20or=20edit=20issues.&nbsp;=20</span><span=20lang=3DEN=
-US><o:p></o:p></span></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>Documentation=20relating=20to=20the=20TRAC=20Issue=20Trackin=
g=20database=20is
available=20here:<o:p></o:p></span></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US><a=20href=3D"http://trac.tools.ietf.org/wg/martini/trac/wiki=
">http://trac.tools.ietf.org/wg/martini/trac/wiki</a><o:p></o:p></span></=
p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>Since=20this=20documentation=20is=20somewhat=20lengthy=20(an=
d=20mostly=20relevant=20to
Admins),=20here=20is=20a=20pithy=20synopsis.=20<o:p></o:p></span></p>

<p=20class=3DMsoListParagraph=20style=3D'text-indent:-18.0pt'><span=20lan=
g=3DEN-US
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>1.&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
To=20submit=20an=20issue=20in=20the=20MARTINI=20Issues=20database=20(know=
n=20as=20TRAC),=20you=20first
need=20to=20login=20to=20the=20MARTINI=20WG=20site=20on=20the=20tools=20s=
erver=20(<a
href=3D"http://tools.ietf.org/wg/martini/trac/login">http://tools.ietf.or=
g/wg/martini/trac/login</a>
)=20<o:p></o:p></span></p>

<p=20class=3DMsoListParagraph=20style=3D'text-indent:-18.0pt'><span=20lan=
g=3DEN-US
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>2.&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
If=20you=20don&#8217;t=20already=20have=20a=20login=20ID,=20you=20can=20o=
btain=20one=20by=20navigating=20to=20this
site:=20&nbsp;&nbsp;<a=20href=3D"http://trac.tools.ietf.org/newlogin">htt=
p://trac.tools.ietf.org/newlogin</a><o:p></o:p></span></p>

<p=20class=3DMsoListParagraph=20style=3D'text-indent:-18.0pt'><span=20lan=
g=3DEN-US
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>3<span
style=3D'color:black'>.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20Once=20you=
=20have
obtained=20an=20account,=20you=20can=20log=20in=20by=20clicking=20on=20th=
e=20&#8220;login&#8221;=20entry=20at=20the=20top
of=20the=20page.&nbsp;=20Once=20you=20have=20logged=20in,=20you=20can=20f=
ile=20an=20issue=20by=20navigating
to=20the=20&nbsp;ticket=20entry=20form:=20<a
href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"><span
style=3D'color:black'>http://trac.tools.ietf.org/wg/martini/trac/newticke=
t</span></a><o:p></o:p></span></span></p>

<p=20class=3DMsoListParagraph=20style=3D'text-indent:-18.0pt'><span=20lan=
g=3DEN-US
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>4<span
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;=20</span>&nbsp;When=20opening=
=20an
issue:&nbsp;<o:p></o:p></span></p>

<p=20class=3DMsoListParagraph=20style=3D'text-indent:-18.0pt'><span=20lan=
g=3DEN-US
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>a.&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
The=20Type:=20field=20should=20be=20set=20to=20&#8220;defect&#8221;=20for=
=20an=20issue=20with=20the=20current
document=20text,=20or=20&#8220;enhancement&#8221;=20for=20a=20proposed=20=
addition=20of=20functionality=20(such
as=20an=20additional=20requirement).=20<o:p></o:p></span></p>

<p=20class=3DMsoListParagraph=20style=3D'text-indent:-18.0pt'><span=20lan=
g=3DEN-US
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>b.&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
The=20Priority:=20field=20is=20set=20based=20on=20the=20severity=20of=20t=
he=20Issue.&nbsp;&nbsp;=20For
example,=20editorial=20issues=20are=20typically=20&#8220;minor&#8221;=20o=
r=20&#8220;trivial&#8221;.=20<o:p></o:p></span></p>

<p=20class=3DMsoListParagraph=20style=3D'text-indent:-18.0pt'><span=20lan=
g=3DEN-US
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>c<span
style=3D'color:black'>.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20The=20Miles=
tone:=20field
should=20be=20set=20to=20milestone1=20(useless,=20I=20know).=20<o:p></o:p=
></span></span></p>

<p=20class=3DMsoListParagraph=20style=3D'text-indent:-18.0pt'><span=20lan=
g=3DEN-US
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>d.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The=20Component:=20field=20should=20be=20set=20to=20the=20document=20you=
=20are=20filing=20the=20issue
on.&nbsp;=20In=20responding=20to=20the=20GIN=20Call=20for=20Adoption,=20&=
#8220;gin&#8221;=20is=20the=20appropriate
choice.<o:p></o:p></span></p>

<p=20class=3DMsoListParagraph=20style=3D'text-indent:-18.0pt'><span=20lan=
g=3DEN-US
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>e.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The=20Version:=20field=20should=20be=20set=20to=20&#8220;1.0&#8221;.=20<o=
:p></o:p></span></p>

<p=20class=3DMsoListParagraph=20style=3D'text-indent:-18.0pt'><span=20lan=
g=3DEN-US
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>f.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The=20Severity:=20field=20should=20be=20set=20to=20based=20on=20the=20sta=
tus=20of=20the=20document=20(e.g.
&#8220;Candidate=20WG=20Document&#8221;=20in=20this=20case)<o:p></o:p></s=
pan></p>

<p=20class=3DMsoListParagraph=20style=3D'text-indent:-18.0pt'><span=20lan=
g=3DEN-US
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>g.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;The=20Keywords:=20and=20CC:=20fields=20can=20be=20left=20blank=20un=
less=20inspiration=20seizes
you.=20<o:p></o:p></span></p>

<p=20class=3DMsoListParagraph=20style=3D'text-indent:-18.0pt'><span=20lan=
g=3DEN-US
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>h.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The=20Assign=20To:=20field=20is=20generally=20filled=20in=20with=20the=20=
email=20address=20of=20the
editor.=20<o:p></o:p></span></p>

<p=20class=3DMsoListParagraph=20style=3D'text-indent:-18.0pt'><span=20lan=
g=3DEN-US
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>5.&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
Typically=20it=20won&#8217;t=20be=20necessary=20to=20enclose=20a=20file=
=20with=20the=20ticket,=20but=20if=20you
need=20to,=20select=20&#8220;I=20have=20files=20to=20attach=20to=20this=
=20ticket&#8221;.=20<o:p></o:p></span></p>

<p=20class=3DMsoListParagraph=20style=3D'text-indent:-18.0pt'><span=20lan=
g=3DEN-US
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>6.&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
If=20you=20want=20to=20preview=20your=20Issue,=20click=20on=20the=20&#822=
0;Preview&#8221;=20button.&nbsp;=20When
you&#8217;re=20ready=20to=20submit=20the=20issue,=20click=20on=20the=20&#=
8220;Create=20Ticket&#8221;=20button.=20<o:p></o:p></span></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>That&#8217;s=20it!&nbsp;=20<span=20style=3D'color:#1F497D'><=
o:p></o:p></span></span></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>If=20you=20have=20an=20problems=20in=20dealing=20with=20TRAC=
,=20send=20email=20to=20me=20and
I&#8217;ll=20try=20to=20figure=20out=20what&#8217;s=20going=20on.=20<span=
=20style=3D'color:#1F497D'><o:p></o:p></span></span></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>Happy=20TRACing,<span=20style=3D'color:#1F497D'><o:p></o:p><=
/span></span></p>

<p=20class=3DMsoNormal><span=20lang=3DEN-US>Bernard<o:p></o:p></span></p>

<p=20class=3DMsoNormal><span=20lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

</div>

</body>

</html>

<table><tr><td=20bgcolor=3D#ffffff><font=20color=3D#000000><pre>****=20DI=
SCLAIMER=20****
http://www.belgacom.be/maildisclaimer</pre></font></td></tr></table>

--_000_208EAE1DFA28FC419529619ABB8622441616E6C19BCMS03BGCNET_--

From john.elwell@siemens-enterprise.com  Thu Mar 18 07:15:31 2010
Return-Path: <john.elwell@siemens-enterprise.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 CF6803A6BDD for <martini@core3.amsl.com>; Thu, 18 Mar 2010 07:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.239
X-Spam-Level: 
X-Spam-Status: No, score=-0.239 tagged_above=-999 required=5 tests=[AWL=-1.784, BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_45=0.6]
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 xnvgHoFiyurT for <martini@core3.amsl.com>; Thu, 18 Mar 2010 07:15:31 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 785623A6BB3 for <martini@ietf.org>; Thu, 18 Mar 2010 07:15:29 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1261882 for martini@ietf.org; Thu, 18 Mar 2010 15:15:39 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id 0AC8A23F0278 for <martini@ietf.org>; Thu, 18 Mar 2010 15:15:39 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Thu, 18 Mar 2010 15:15:39 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "martini@ietf.org" <martini@ietf.org>
Date: Thu, 18 Mar 2010 15:15:37 +0100
Thread-Topic: Use of user=phone in gin draft
Thread-Index: AcrGpXtYYgyKBSitThyeB2c7JzjAoA==
Message-ID: <A444A0F8084434499206E78C106220CABE9055B5@MCHP058A.global-ad.net>
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
Subject: [martini] Use of user=phone in gin draft
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: Thu, 18 Mar 2010 14:15:31 -0000

The examples in the gin draft include 'user=3Dphone' in the contact URI reg=
istered with the SSP, e.g.: <sip:198.51.100.3:5060;user=3Dphone;bnc>

I just wonder whether user=3Dphone is appropriate here. The parameter makes=
 a statement that the user part is a telephone subscriber number, which in =
this case, in the absence of a user part, is clearly not the case. However,=
 when expanded and used in an inbound request (e.g., <sip:+12145550102@198.=
51.100.3:5060;user=3Dphone>, it can be correct. In fact, because the draft =
is limited to fully-qualified E.164 numbers in the user part, the presence =
of user=3Dphone will always be correct.

So we would seem to have several choices:
1. Keep as is.
2. Omit from the REGISTER request but require the registrar to add it when =
constructing the complete contact URI.
3. Don't use user=3Dphone at all.

I don't have a strong opinion - just raising the question.

John


From kpfleming@digium.com  Thu Mar 18 07:55:56 2010
Return-Path: <kpfleming@digium.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 DB9F53A6C34 for <martini@core3.amsl.com>; Thu, 18 Mar 2010 07:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.415
X-Spam-Level: 
X-Spam-Status: No, score=-104.415 tagged_above=-999 required=5 tests=[AWL=-2.145, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 BXUAX0WvfeXH for <martini@core3.amsl.com>; Thu, 18 Mar 2010 07:55:55 -0700 (PDT)
Received: from mail.digium.com (mail.digium.com [216.207.245.2]) by core3.amsl.com (Postfix) with ESMTP id EEBBA3A6C2F for <martini@ietf.org>; Thu, 18 Mar 2010 07:55:53 -0700 (PDT)
Received: from zimbra.digium.internal ([10.24.55.203] helo=zimbra.hsv.digium.com) by mail.digium.com with esmtp (Exim 4.69) (envelope-from <kpfleming@digium.com>) id 1NsH8m-0005kZ-L5; Thu, 18 Mar 2010 09:56:04 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.hsv.digium.com (Postfix) with ESMTP id 92B22D8004; Thu, 18 Mar 2010 09:56:04 -0500 (CDT)
Received: from zimbra.hsv.digium.com ([127.0.0.1]) by localhost (zimbra.hsv.digium.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jtDK5MQ88r14; Thu, 18 Mar 2010 09:56:04 -0500 (CDT)
Received: from [172.19.1.105] (173-24-205-181.client.mchsi.com [173.24.205.181]) by zimbra.hsv.digium.com (Postfix) with ESMTPSA id 08FE2D8002; Thu, 18 Mar 2010 09:56:03 -0500 (CDT)
Message-ID: <4BA23F03.7030108@digium.com>
Date: Thu, 18 Mar 2010 09:56:03 -0500
From: "Kevin P. Fleming" <kpfleming@digium.com>
Organization: Digium, Inc.
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
References: <A444A0F8084434499206E78C106220CABE9055B5@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CABE9055B5@MCHP058A.global-ad.net>
X-Enigmail-Version: 0.95.7
OpenPGP: id=05FB8DB2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Use of user=phone in gin draft
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: Thu, 18 Mar 2010 14:55:56 -0000

Elwell, John wrote:
> The examples in the gin draft include 'user=phone' in the contact URI registered with the SSP, e.g.: <sip:198.51.100.3:5060;user=phone;bnc>
> 
> I just wonder whether user=phone is appropriate here. The parameter makes a statement that the user part is a telephone subscriber number, which in this case, in the absence of a user part, is clearly not the case. However, when expanded and used in an inbound request (e.g., <sip:+12145550102@198.51.100.3:5060;user=phone>, it can be correct. In fact, because the draft is limited to fully-qualified E.164 numbers in the user part, the presence of user=phone will always be correct.
> 
> So we would seem to have several choices:
> 1. Keep as is.
> 2. Omit from the REGISTER request but require the registrar to add it when constructing the complete contact URI.
> 3. Don't use user=phone at all.

I don't have a strong opinion either, but I went through the same logic
when reading the draft that you've listed above, and came to the same
conclusion... it's appropriate in the REGISTER URI because it will be
correct (and possibly even required) in the generated INVITE URI. So...
that's option #1.

The only thing that might be worth doing is modifying the draft to say
that "any URI parameters that are required to appear in the INVITE's
Request URI must be included in the REGISTER's Request URI, because the
registrar will never add them on its own. This could include
'user=phone' (and these examples do include it), or other URI parameters
that may be defined later to be used with E.164-type Request URIs".

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kfleming@digium.com
Check us out at www.digium.com & www.asterisk.org

From bernard_aboba@hotmail.com  Thu Mar 18 08:31:23 2010
Return-Path: <bernard_aboba@hotmail.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 4BB3C3A6B4C for <martini@core3.amsl.com>; Thu, 18 Mar 2010 08:31:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.057
X-Spam-Level: 
X-Spam-Status: No, score=0.057 tagged_above=-999 required=5 tests=[AWL=-1.075,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 kp9rEkgcAGyk for <martini@core3.amsl.com>; Thu, 18 Mar 2010 08:31:21 -0700 (PDT)
Received: from blu0-omc2-s9.blu0.hotmail.com (blu0-omc2-s9.blu0.hotmail.com [65.55.111.84]) by core3.amsl.com (Postfix) with ESMTP id F0E483A6AEC for <martini@ietf.org>; Thu, 18 Mar 2010 08:31:19 -0700 (PDT)
Received: from BLU137-W1 ([65.55.111.73]) by blu0-omc2-s9.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 18 Mar 2010 08:31:31 -0700
Message-ID: <BLU137-W1206413E35DB668DE4FFA932B0@phx.gbl>
Content-Type: multipart/alternative; boundary="_c21f4dd8-315e-42f1-aac4-a2c9560010c1_"
X-Originating-IP: [76.108.77.56]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <martini@ietf.org>
Date: Thu, 18 Mar 2010 08:31:31 -0700
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 18 Mar 2010 15:31:31.0628 (UTC) FILETIME=[15D49EC0:01CAC6B0]
Subject: [martini] Slide Request
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: Thu, 18 Mar 2010 15:31:23 -0000

--_c21f4dd8-315e-42f1-aac4-a2c9560010c1_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


The first MARTINI WG meeting at IETF 77 will be held on Monday=2C March 22=
=2C 2010 in the 1 - 3 PM slot.

That is only 4 days from now!

So if you are on the agenda=2C please send your slides to Spencer and mysel=
f ASAP.=20



 		 	   		  =

--_c21f4dd8-315e-42f1-aac4-a2c9560010c1_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
The first MARTINI WG meeting at IETF 77 will be held on Monday=2C March 22=
=2C 2010 in the 1 - 3 PM slot.<br><br>That is only 4 days from now!<br><br>=
So if you are on the agenda=2C please send your slides to Spencer and mysel=
f ASAP. <br><br><br><table style=3D"border-top: 1px solid black=3B font-wei=
ght: bold=3B font-family: 'Segoe UI'=2CTahoma=2Csan-serif=3B"><tbody><tr><t=
d><a href=3D"http://im.live.com/Messenger/IM/Home/?source=3DEML_WLHM_Greate=
rGood" style=3D"font-size: 9pt=3B color: rgb(1=2C 132=2C 203)=3B text-decor=
ation: none=3B"><span style=3D"padding: 0px 24px=3B font-size: 8pt=3B color=
: rgb(63=2C 181=2C 85)=3B text-decoration: underline=3B"></span></a><br></t=
d></tr></tbody></table> 		 	   		  </body>
</html>=

--_c21f4dd8-315e-42f1-aac4-a2c9560010c1_--

From ietf.hanserik@gmail.com  Thu Mar 18 10:42:19 2010
Return-Path: <ietf.hanserik@gmail.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 031BD3A698D for <martini@core3.amsl.com>; Thu, 18 Mar 2010 10:42:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.826
X-Spam-Level: 
X-Spam-Status: No, score=-0.826 tagged_above=-999 required=5 tests=[AWL=-1.772, BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 hmxwL5jyr77j for <martini@core3.amsl.com>; Thu, 18 Mar 2010 10:42:17 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by core3.amsl.com (Postfix) with ESMTP id 4A0213A69C9 for <martini@ietf.org>; Thu, 18 Mar 2010 10:42:14 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 4so219017eyf.51 for <martini@ietf.org>; Thu, 18 Mar 2010 10:42:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=xiRmkjFtm1gIagy7/mYCQ2G6jMmlyFqvEdyRNCG1MzA=; b=TLEqup85p/+zlyP8jCKRS7TAyEcWQm62NlQL1Q5cBx95hWOP+2LvwhH1z5wlkzKJBj LOjS16fWUSgoPlNR10bSr+VQrpBxEEnlUUvAcyrmApDeoofgDqcLt+dkfV7mg7u+mWZW nJP4TNmtY3mQsc3vL8Fr7iTbx8f+L8sdbyqFc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=PCFJ3p1/aq+slZmd9eMDgLfCDn8goFxaQ4RGOPeW8vd1sTKQ9kRsH8t1sE79wsW2cu GNMWKdfFX93Zd0J3DXFDCcwh9BIetBJ7EzRtV/Ik04FtnPS0+q1kSZVamJ+LKaO6NUr3 YKw2sjsK802BwzSs1SNNaVyH9LpLAYidwCDbw=
MIME-Version: 1.0
Received: by 10.213.109.149 with SMTP id j21mr1860086ebp.73.1268934141343;  Thu, 18 Mar 2010 10:42:21 -0700 (PDT)
In-Reply-To: <208EAE1DFA28FC419529619ABB8622441616E6C19B@CMS03.BGC.NET>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl> <09B7DBFE70A9E24BBB21689DAD3A06141CF400B7@zcarhxm1.corp.nortel.com> <208EAE1DFA28FC419529619ABB8622441616E6C19B@CMS03.BGC.NET>
Date: Thu, 18 Mar 2010 18:42:21 +0100
Message-ID: <9ae56b1e1003181042u3e21d1bax79124b1584e8e40d@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: jan.van.geel@belgacom.be
Content-Type: multipart/alternative; boundary=000e0cdfd720bcf6e2048216c0e1
Cc: bernard_aboba@hotmail.com, martini@ietf.org
Subject: Re: [martini] Call for Adoption of "Registration for Multiple PhoneNumbers in the SIP"
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: Thu, 18 Mar 2010 17:42:19 -0000

--000e0cdfd720bcf6e2048216c0e1
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

+1

Allowing both UC-3 and UC-6/9 scenarios could be a way forward, use cases o=
r
scenarios as depicted in:
http://aboba.drizzlehosting.com/MARTINI/Jan-Interim-III/IETF77_MARTINI_Feb9=
Interim_Use_models.pdf

PBX configurations that are fine with the limitations or limited themselves
can register and indicate they are expecting UC-3 style.
PBX configurations that need more advanced setups can register and indicate
they are expecting UC-6/9 style.

BR,
/Hans Erik van Elburg

On Thu, Mar 18, 2010 at 9:06 AM, <jan.van.geel@belgacom.be> wrote:

>  Hi,
>
>
>
> As service provider I completely agree with the statement that a common
> approach is beneficial for the industry. Therefore I would prefer that
> alignment with existing specifications of 3GPP/ETSI is sought as much as
> possible.
>
>
>
> Kind regards
>
>
>
>
>
> *Jan Van Geel*
> IT and Network Development Specialist
> Belgacom SDE/SDV/PSE/NST/NCP
> Tel: +32 2 202 1035
> Tel: +32 2 207 4442
> Tel: +32 2 207 9032
> Email : jan.van.geel@belgacom.be
> www.cyberwezz.tk
>
>
>
>
>
> *From:* martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] *On
> Behalf Of *Brian Lindsay
> *Sent:* 17 March 2010 14:51
> *To:* Bernard Aboba; MARTINI
> *Subject:* Re: [martini] Call for Adoption of "Registration for Multiple
> PhoneNumbers in the SIP"
>
>
>
> Hi Bernard,
>
>
>
>    I think the gin draft could form the basis of a solution, but at as
> couple of other folks have noted there already is a solution standardized=
 by
> TIPAN/3GPP which uses a different approach for request routing for SIP PB=
Xs.
> It would be ideal if we had one common approach in the industry, otherwis=
e
> we are going to see some carriers require one solution and other carriers
> the other solution and vendors on both the enterprise and carrier side wi=
ll
> need to implement and support both.
>
>
>
>    The shaken draft is closer to the TISPAN/3GPP approach and is
> essentially adding some incremental improvements. I'd be more inclined to=
 go
> with the shaken appoach at this time given it's alignment with the existi=
ng
> standardized TISPAN/3GPP solution.
>
>
>
>    I haven't heard too many other responses on the call for adoption from
> SSP vendors so I'm curious on that front what others are thinking.
>
>
>
>    Thanks
>
>        Brian
>
>
>  ------------------------------
>
> *From:* martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] *On
> Behalf Of *Bernard Aboba
> *Sent:* Thursday, March 04, 2010 5:02 PM
> *To:* 'MARTINI'
> *Subject:* [martini] Call for Adoption of "Registration for Multiple
> PhoneNumbers in the SIP"
>
> This is a MARTINI WG Call for Adoption of =93Registration for Multiple Ph=
one
> Numbers in the SIP=94 as a MARTINI WG work item, corresponding to the
> =93Multiple AoR Registration specification=94 Charter deliverable.  The d=
ocument
> is available for inspection here:
>
> http://tools.ietf.org/html/draft-roach-martini-gin-01.txt
>
> The MARTINI WG Call for Adoption will last until Friday, March 19, 2010.
>
> Please respond to this WG Call for Adoption, whether you are in favor of
> adopting the document as a MARTINI WG work item or not.  If you have no
> comments, please reply to this message and indicate in the body of your
> message whether you think the document is ready for adoption as a MARTINI=
 WG
> work item or not.   Based on the response, the MARTINI WG chairs will
> attempt to determine whether WG consensus exists to adopt the document or
> not.
>
> If you have comments, please provide them to the WG in one of the followi=
ng
> ways:
>
> 1.      The preferred choice is to open an issue in the MARTINI Issue
> tracking database (TRAC), which is available here:
> http://trac.tools.ietf.org/wg/martini/trac/newticket  Information on how
> to use TRAC is provided below.  Note that if you submit an issue in TRAC,=
 it
> will automatically also be posted to the MARTINI WG mailing list.  When
> submitting issues in TRAC for this =93call for adoption=94, please enter =
=93gin=94
> for the Component: and =93Candidate WG Document=94 for Severity.
>
>  2. If you can=92t figure out how to use TRAC, please post your Issue to =
the
> MARTINI WG mailing list (martini at ietf.org) in the following format:
>
> To:  martini at ietf.org
>
> Subject: GIN-Issue: <title of your issue>
>
> Priority: blocker, critical, major, minor or trivial
>
> <Explanation of your issue, including a proposal for specific text change=
s
> to resolve the issue>
>
> The MARTINI WG uses the TRAC database to keep track of issues relating to
> work in progress, including working group work items and individual
> submissions undergoing review.    This document provides some basic
> information on how MARTINI WG participants can use TRAC to submit or edit
> issues.
>
> Documentation relating to the TRAC Issue Tracking database is available
> here:
>
> http://trac.tools.ietf.org/wg/martini/trac/wiki
>
> Since this documentation is somewhat lengthy (and mostly relevant to
> Admins), here is a pithy synopsis.
>
> 1.       To submit an issue in the MARTINI Issues database (known as TRAC=
),
> you first need to login to the MARTINI WG site on the tools server (
> http://tools.ietf.org/wg/martini/trac/login )
>
> 2.       If you don=92t already have a login ID, you can obtain one by
> navigating to this site:   http://trac.tools.ietf.org/newlogin
>
> 3.       Once you have obtained an account, you can log in by clicking on
> the =93login=94 entry at the top of the page.  Once you have logged in, y=
ou can
> file an issue by navigating to the  ticket entry form:
> http://trac.tools.ietf.org/wg/martini/trac/newticket
>
> 4     When opening an issue:
>
> a.       The Type: field should be set to =93defect=94 for an issue with =
the
> current document text, or =93enhancement=94 for a proposed addition of
> functionality (such as an additional requirement).
>
> b.      The Priority: field is set based on the severity of the Issue.
> For example, editorial issues are typically =93minor=94 or =93trivial=94.
>
> c.       The Milestone: field should be set to milestone1 (useless, I
> know).
>
> d.      The Component: field should be set to the document you are filing
> the issue on.  In responding to the GIN Call for Adoption, =93gin=94 is t=
he
> appropriate choice.
>
> e.      The Version: field should be set to =931.0=94.
>
> f.        The Severity: field should be set to based on the status of the
> document (e.g. =93Candidate WG Document=94 in this case)
>
> g.        The Keywords: and CC: fields can be left blank unless inspirati=
on
> seizes you.
>
> h.      The Assign To: field is generally filled in with the email addres=
s
> of the editor.
>
> 5.       Typically it won=92t be necessary to enclose a file with the tic=
ket,
> but if you need to, select =93I have files to attach to this ticket=94.
>
> 6.       If you want to preview your Issue, click on the =93Preview=94 bu=
tton.
> When you=92re ready to submit the issue, click on the =93Create Ticket=94=
 button.
>
> That=92s it!
>
> If you have an problems in dealing with TRAC, send email to me and I=92ll=
 try
> to figure out what=92s going on.
>
> Happy TRACing,
>
> Bernard
>
>
>
> **** DISCLAIMER ****http://www.belgacom.be/maildisclaimer
>
>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>
>

--000e0cdfd720bcf6e2048216c0e1
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

+1<br><br>Allowing both UC-3 and UC-6/9 scenarios could be a way forward,=
=20
use cases or scenarios as depicted in:<br>
<a href=3D"http://aboba.drizzlehosting.com/MARTINI/Jan-Interim-III/IETF77_M=
ARTINI_Feb9Interim_Use_models.pdf" target=3D"_blank">http://aboba.drizzleho=
sting.com/MARTINI/Jan-Interim-III/IETF77_MARTINI_Feb9Interim_Use_models.pdf=
</a><br>

<br>
PBX configurations that are fine with the limitations or limited=20
themselves can register and indicate they are expecting UC-3 style.<br>
PBX configurations that need more advanced setups can register and=20
indicate they are expecting UC-6/9 style.<br>
<br>BR,<br clear=3D"all">/Hans Erik van Elburg<br>
<br><div class=3D"gmail_quote">On Thu, Mar 18, 2010 at 9:06 AM,  <span dir=
=3D"ltr">&lt;<a href=3D"mailto:jan.van.geel@belgacom.be">jan.van.geel@belga=
com.be</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); paddi=
ng-left: 1ex;">










<div link=3D"blue" vlink=3D"purple" lang=3D"EN-GB">

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">Hi,</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">As serv=
ice provider I completely agree with the statement that a
common approach is beneficial for the industry. Therefore I would prefer th=
at
alignment with existing specifications of 3GPP/ETSI is sought as much as
possible.</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">Kind re=
gards</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><b><span style=3D"font-size: 12pt; color: blue;">Jan=
 Van Geel</span></b><span style=3D"font-size: 12pt; font-family: &quot;Time=
s New Roman&quot;,&quot;serif&quot;; color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">IT and Network Develop=
ment Specialist</span><span style=3D"font-size: 12pt; font-family: &quot;Ti=
mes New Roman&quot;,&quot;serif&quot;; color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Belgacom SDE/SDV/PSE/N=
ST/NCP</span><span style=3D"font-size: 12pt; font-family: &quot;Times New R=
oman&quot;,&quot;serif&quot;; color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Tel: +32 2 202 1035</s=
pan><span style=3D"font-size: 12pt; font-family: &quot;Times New Roman&quot=
;,&quot;serif&quot;; color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Tel: +32 2 207 4442</s=
pan><span style=3D"font-size: 12pt; font-family: &quot;Times New Roman&quot=
;,&quot;serif&quot;; color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Tel: +32 2 207 9032</s=
pan><span style=3D"font-size: 12pt; font-family: &quot;Times New Roman&quot=
;,&quot;serif&quot;; color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Email : <a href=3D"mai=
lto:jan.van.geel@belgacom.be" target=3D"_blank">jan.van.geel@belgacom.be</a=
></span><span style=3D"font-size: 12pt; font-family: &quot;Times New Roman&=
quot;,&quot;serif&quot;; color: blue;"> <br>

</span><span style=3D"font-size: 10pt; color: blue;"><a href=3D"http://www.=
cyberwezz.tk" target=3D"_blank">www.cyberwezz.tk</a></span><span style=3D"f=
ont-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;=
 color: blue;"> </span><span style=3D"font-size: 9pt; color: blue;"></span>=
</p>


<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<div>

<div style=3D"border-width: 1pt medium medium; border-style: solid none non=
e; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color=
; padding: 3pt 0cm 0cm;">

<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt;" lang=3D"EN-US">F=
rom:</span></b><span style=3D"font-size: 10pt;" lang=3D"EN-US"> <a href=3D"=
mailto:martini-bounces@ietf.org" target=3D"_blank">martini-bounces@ietf.org=
</a>
[mailto:<a href=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">marti=
ni-bounces@ietf.org</a>] <b>On Behalf Of </b>Brian Lindsay<br>
<b>Sent:</b> 17 March 2010 14:51<br>
<b>To:</b> Bernard Aboba; MARTINI<br>
<b>Subject:</b> Re: [martini] Call for Adoption of &quot;Registration for
Multiple PhoneNumbers in the SIP&quot;</span></p>

</div>

</div><div><div></div><div class=3D"h5">

<p class=3D"MsoNormal">=A0</p>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;" lang=
=3D"EN-US">Hi Bernard,</span><span style=3D"font-size: 12pt; font-family: &=
quot;Times New Roman&quot;,&quot;serif&quot;;" lang=3D"EN-US"></span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 12pt; font-family: &quot;T=
imes New Roman&quot;,&quot;serif&quot;;" lang=3D"EN-US">=A0</span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;" lang=
=3D"EN-US">=A0=A0 I think the gin draft could form the basis of a
solution, but at as couple of other folks have noted there already is a
solution standardized by TIPAN/3GPP which uses a different approach for req=
uest
routing for SIP PBXs. It would be ideal if we had one common approach in th=
e
industry, otherwise we are going to see some carriers require one solution =
and
other carriers the other solution and vendors on both the enterprise and
carrier side will need to=A0implement and support both.</span><span style=
=3D"font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&q=
uot;;" lang=3D"EN-US"></span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 12pt; font-family: &quot;T=
imes New Roman&quot;,&quot;serif&quot;;" lang=3D"EN-US">=A0</span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;" lang=
=3D"EN-US">=A0=A0 The shaken draft is closer to the TISPAN/3GPP approach
and is essentially adding some incremental improvements. I&#39;d be more in=
clined
to go with the shaken appoach at this time given it&#39;s alignment with th=
e
existing standardized TISPAN/3GPP solution.</span><span style=3D"font-size:=
 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;" lang=3D=
"EN-US"></span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 12pt; font-family: &quot;T=
imes New Roman&quot;,&quot;serif&quot;;" lang=3D"EN-US">=A0</span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;" lang=
=3D"EN-US">=A0=A0 I haven&#39;t heard too many other responses on the call
for adoption=A0from SSP vendors so I&#39;m curious on that front what other=
s are
thinking.</span><span style=3D"font-size: 12pt; font-family: &quot;Times Ne=
w Roman&quot;,&quot;serif&quot;;" lang=3D"EN-US"></span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 12pt; font-family: &quot;T=
imes New Roman&quot;,&quot;serif&quot;;" lang=3D"EN-US">=A0</span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;" lang=
=3D"EN-US">=A0=A0 Thanks</span><span style=3D"font-size: 12pt; font-family:=
 &quot;Times New Roman&quot;,&quot;serif&quot;;" lang=3D"EN-US"></span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;" lang=
=3D"EN-US">=A0=A0=A0=A0=A0=A0 Brian</span><span style=3D"font-size: 12pt; f=
ont-family: &quot;Times New Roman&quot;,&quot;serif&quot;;" lang=3D"EN-US">=
</span></p>

</div>

<p class=3D"MsoNormal"><span style=3D"font-size: 12pt; font-family: &quot;T=
imes New Roman&quot;,&quot;serif&quot;;" lang=3D"EN-US">=A0</span></p>

<div class=3D"MsoNormal" style=3D"text-align: center;" align=3D"center"><sp=
an style=3D"font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot=
;serif&quot;;" lang=3D"EN-US">

<hr width=3D"100%" align=3D"center" size=3D"2">

</span></div>

<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;"><b><span style=3D"fon=
t-size: 10pt;" lang=3D"EN-US">From:</span></b><span style=3D"font-size: 10p=
t;" lang=3D"EN-US">
<a href=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">martini-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:martini-bounces@ietf.org" target=
=3D"_blank">martini-bounces@ietf.org</a>] <b>On Behalf Of </b>Bernard
Aboba<br>
<b>Sent:</b> Thursday, March 04, 2010 5:02 PM<br>
<b>To:</b> &#39;MARTINI&#39;<br>
<b>Subject:</b> [martini] Call for Adoption of &quot;Registration for Multi=
ple
PhoneNumbers in the SIP&quot;</span><span style=3D"font-size: 12pt; font-fa=
mily: &quot;Times New Roman&quot;,&quot;serif&quot;;" lang=3D"EN-US"></span=
></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">This is a MARTINI WG Call for A=
doption of =93Registration for Multiple
Phone Numbers in the SIP=94 as a MARTINI WG work item, corresponding to the
=93Multiple AoR Registration specification=94 Charter deliverable. =A0The
document is available for inspection here: </span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US"><a href=3D"http://tools.ietf.or=
g/html/draft-roach-martini-gin-01.txt" target=3D"_blank">http://tools.ietf.=
org/html/draft-roach-martini-gin-01.txt</a></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">The MARTINI WG Call for Adoptio=
n will last until Friday, March 19,
2010.</span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">Please respond to this WG Call =
for Adoption, whether you are in
favor of adopting the document as a MARTINI WG work item or not. =A0If you
have no comments, please reply to this message and indicate in the body of =
your
message whether you think the document is ready for adoption as a MARTINI W=
G
work item or not. =A0=A0Based on the response, the MARTINI WG chairs will
attempt to determine whether WG consensus exists to adopt the document or n=
ot. </span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">If you have comments, please pr=
ovide them to the WG in one of the
following ways: </span></p>

<p style=3D"margin-left: 21pt;"><span style=3D"font-size: 11pt; color: blac=
k;" lang=3D"EN-US">1.=A0=A0=A0=A0=A0 The preferred choice is to open
an issue in the MARTINI Issue tracking database (TRAC), which is available
here: <a href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket" targ=
et=3D"_blank"><span style=3D"color: black;">http://trac.tools.ietf.org/wg/m=
artini/trac/newticket</span></a>
=A0Information on how to use TRAC is provided below.=A0 Note that if you
submit an issue in TRAC, it will automatically also be posted to the MARTIN=
I WG
mailing list. =A0When submitting issues in TRAC for this =93call for
adoption=94, please enter =93gin=94 for the Component: and =93Candidate WG =
Document=94
for Severity.=A0 </span></p>

<p class=3D"MsoNormal"><span style=3D"color: black;" lang=3D"EN-US">=A02. I=
f you can=92t figure out how to use
TRAC, please post your Issue to the MARTINI WG mailing list (martini at
<a href=3D"http://ietf.org" target=3D"_blank">ietf.org</a>) in the followin=
g format: </span></p>

<p class=3D"MsoNormal"><span style=3D"font-family: &quot;Courier New&quot;;=
" lang=3D"EN-US">To:=A0 martini at <a href=3D"http://ietf.org" target=3D"_b=
lank">ietf.org</a></span><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span style=3D"font-family: &quot;Courier New&quot;;=
" lang=3D"EN-US">Subject: GIN-Issue: &lt;title of
your issue&gt;</span><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span style=3D"font-family: &quot;Courier New&quot;;=
" lang=3D"EN-US">Priority: blocker, critical,
major, minor or trivial</span><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span style=3D"font-family: &quot;Courier New&quot;;=
" lang=3D"EN-US">&lt;Explanation of your issue,
including a proposal for specific text changes to resolve the issue&gt;</sp=
an><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span style=3D"color: black;" lang=3D"EN-US">The MAR=
TINI WG uses the TRAC database to keep
track of issues relating to work in progress, including working group work
items and individual submissions undergoing review. =A0=A0=A0This
document provides some basic information on how MARTINI WG participants can=
 use
TRAC to submit or edit issues.=A0 </span><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">Documentation relating to the T=
RAC Issue Tracking database is
available here:</span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US"><a href=3D"http://trac.tools.ie=
tf.org/wg/martini/trac/wiki" target=3D"_blank">http://trac.tools.ietf.org/w=
g/martini/trac/wiki</a></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">Since this documentation is som=
ewhat lengthy (and mostly relevant to
Admins), here is a pithy synopsis. </span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">1.=A0=A0=A0=A0=A0=A0
To submit an issue in the MARTINI Issues database (known as TRAC), you firs=
t
need to login to the MARTINI WG site on the tools server (<a href=3D"http:/=
/tools.ietf.org/wg/martini/trac/login" target=3D"_blank">http://tools.ietf.=
org/wg/martini/trac/login</a>
) </span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">2.=A0=A0=A0=A0=A0=A0
If you don=92t already have a login ID, you can obtain one by navigating to=
 this
site: =A0=A0<a href=3D"http://trac.tools.ietf.org/newlogin" target=3D"_blan=
k">http://trac.tools.ietf.org/newlogin</a></span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">3<span style=3D"color: b=
lack;">.=A0=A0=A0=A0=A0=A0 Once you have
obtained an account, you can log in by clicking on the =93login=94 entry at=
 the top
of the page.=A0 Once you have logged in, you can file an issue by navigatin=
g
to the =A0ticket entry form: <a href=3D"http://trac.tools.ietf.org/wg/marti=
ni/trac/newticket" target=3D"_blank"><span style=3D"color: black;">http://t=
rac.tools.ietf.org/wg/martini/trac/newticket</span></a></span></span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">4<span style=3D"color: r=
gb(31, 73, 125);">=A0=A0=A0 </span>=A0When opening an
issue:=A0</span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">a.=A0=A0=A0=A0=A0=A0
The Type: field should be set to =93defect=94 for an issue with the current
document text, or =93enhancement=94 for a proposed addition of functionalit=
y (such
as an additional requirement). </span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">b.=A0=A0=A0=A0=A0
The Priority: field is set based on the severity of the Issue.=A0=A0 For
example, editorial issues are typically =93minor=94 or =93trivial=94. </spa=
n></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">c<span style=3D"color: b=
lack;">.=A0=A0=A0=A0=A0=A0 The Milestone: field
should be set to milestone1 (useless, I know). </span></span></p>

<p><span style=3D"font-size: 11pt; color: black;" lang=3D"EN-US">d.=A0=A0=
=A0=A0=A0
The Component: field should be set to the document you are filing the issue
on.=A0 In responding to the GIN Call for Adoption, =93gin=94 is the appropr=
iate
choice.</span></p>

<p><span style=3D"font-size: 11pt; color: black;" lang=3D"EN-US">e.=A0=A0=
=A0=A0=A0
The Version: field should be set to =931.0=94. </span></p>

<p><span style=3D"font-size: 11pt; color: black;" lang=3D"EN-US">f.=A0=A0=
=A0=A0=A0=A0=A0
The Severity: field should be set to based on the status of the document (e=
.g.
=93Candidate WG Document=94 in this case)</span></p>

<p><span style=3D"font-size: 11pt; color: black;" lang=3D"EN-US">g.=A0=A0=
=A0=A0=A0=A0
=A0The Keywords: and CC: fields can be left blank unless inspiration seizes
you. </span></p>

<p><span style=3D"font-size: 11pt; color: black;" lang=3D"EN-US">h.=A0=A0=
=A0=A0=A0
The Assign To: field is generally filled in with the email address of the
editor. </span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">5.=A0=A0=A0=A0=A0=A0
Typically it won=92t be necessary to enclose a file with the ticket, but if=
 you
need to, select =93I have files to attach to this ticket=94. </span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">6.=A0=A0=A0=A0=A0=A0
If you want to preview your Issue, click on the =93Preview=94 button.=A0 Wh=
en
you=92re ready to submit the issue, click on the =93Create Ticket=94 button=
. </span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">That=92s it!=A0 <span style=3D"=
color: rgb(31, 73, 125);"></span></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">If you have an problems in deal=
ing with TRAC, send email to me and
I=92ll try to figure out what=92s going on. <span style=3D"color: rgb(31, 7=
3, 125);"></span></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">Happy TRACing,<span style=3D"co=
lor: rgb(31, 73, 125);"></span></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">Bernard</span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">=A0</span></p>

</div></div></div>

</div>



<table><tbody><tr><td bgcolor=3D"#ffffff"><font color=3D"#000000"><pre>****=
 DISCLAIMER ****
<a href=3D"http://www.belgacom.be/maildisclaimer" target=3D"_blank">http://=
www.belgacom.be/maildisclaimer</a></pre></font></td></tr></tbody></table>
<br>_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
<br></blockquote></div><br>

--000e0cdfd720bcf6e2048216c0e1--

From brett@broadsoft.com  Thu Mar 18 12:48:37 2010
Return-Path: <brett@broadsoft.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 4185B3A686D for <martini@core3.amsl.com>; Thu, 18 Mar 2010 12:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.332
X-Spam-Level: 
X-Spam-Status: No, score=-1.332 tagged_above=-999 required=5 tests=[AWL=-0.462, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_45=0.6]
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 3CIzhmCzlPtm for <martini@core3.amsl.com>; Thu, 18 Mar 2010 12:48:36 -0700 (PDT)
Received: from smtp-out01.seaservers.net (smtp-out01.seaservers.net [72.37.232.66]) by core3.amsl.com (Postfix) with ESMTP id 794243A65A6 for <martini@ietf.org>; Thu, 18 Mar 2010 12:48:36 -0700 (PDT)
Received: from EXMBXCLUS01.citservers.local ([fe80:0000:0000:0000:a488:d1ec:167.6.58.109]) by casumhub01.citservers.local ([172.16.98.57]) with mapi; Thu, 18 Mar 2010 12:48:48 -0700
From: Brett Tate <brett@broadsoft.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "martini@ietf.org" <martini@ietf.org>
Date: Thu, 18 Mar 2010 12:48:06 -0700
Thread-Topic: Use of user=phone in gin draft
Thread-Index: AcrGpXtYYgyKBSitThyeB2c7JzjAoAALeB9Q
Message-ID: <747A6506A991724FB09B129B79D5FEB614808053C1@EXMBXCLUS01.citservers.local>
References: <A444A0F8084434499206E78C106220CABE9055B5@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CABE9055B5@MCHP058A.global-ad.net>
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
Subject: Re: [martini] Use of user=phone in gin draft
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: Thu, 18 Mar 2010 19:48:37 -0000

In case it helps, here is a link concerning user=3Dphone topic; it was rece=
ntly discussed on sipcore and sip-implementors.

http://www.ietf.org/mail-archive/web/sipcore/current/msg01784.html=20


> -----Original Message-----
> From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On
> Behalf Of Elwell, John
> Sent: Thursday, March 18, 2010 10:16 AM
> To: martini@ietf.org
> Subject: [martini] Use of user=3Dphone in gin draft
>=20
> The examples in the gin draft include 'user=3Dphone' in the contact URI
> registered with the SSP, e.g.: <sip:198.51.100.3:5060;user=3Dphone;bnc>
>=20
> I just wonder whether user=3Dphone is appropriate here. The parameter
> makes a statement that the user part is a telephone subscriber number,
> which in this case, in the absence of a user part, is clearly not the
> case. However, when expanded and used in an inbound request (e.g.,
> <sip:+12145550102@198.51.100.3:5060;user=3Dphone>, it can be correct. In
> fact, because the draft is limited to fully-qualified E.164 numbers in
> the user part, the presence of user=3Dphone will always be correct.
>=20
> So we would seem to have several choices:
> 1. Keep as is.
> 2. Omit from the REGISTER request but require the registrar to add it
> when constructing the complete contact URI.
> 3. Don't use user=3Dphone at all.
>=20
> I don't have a strong opinion - just raising the question.
>=20
> John
>=20
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini

From bernard_aboba@hotmail.com  Thu Mar 18 13:38:12 2010
Return-Path: <bernard_aboba@hotmail.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 274153A6BD6 for <martini@core3.amsl.com>; Thu, 18 Mar 2010 13:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.119
X-Spam-Level: 
X-Spam-Status: No, score=0.119 tagged_above=-999 required=5 tests=[AWL=-1.013,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 GdwN+ff7ygwl for <martini@core3.amsl.com>; Thu, 18 Mar 2010 13:38:10 -0700 (PDT)
Received: from blu0-omc2-s32.blu0.hotmail.com (blu0-omc2-s32.blu0.hotmail.com [65.55.111.107]) by core3.amsl.com (Postfix) with ESMTP id 93A083A6A74 for <martini@ietf.org>; Thu, 18 Mar 2010 13:38:02 -0700 (PDT)
Received: from BLU137-W12 ([65.55.111.72]) by blu0-omc2-s32.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 18 Mar 2010 13:38:13 -0700
Message-ID: <BLU137-W12F325386E9185C7104D61932B0@phx.gbl>
Content-Type: multipart/alternative; boundary="_89f026b3-d9de-4b71-a5ea-cd3a59b73965_"
X-Originating-IP: [76.108.77.56]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <martini@ietf.org>
Date: Thu, 18 Mar 2010 13:38:13 -0700
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 18 Mar 2010 20:38:13.0732 (UTC) FILETIME=[EE56DA40:01CAC6DA]
Subject: [martini] Conclusion of the MARTINI WG last call on the Requirements document
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: Thu, 18 Mar 2010 20:38:12 -0000

--_89f026b3-d9de-4b71-a5ea-cd3a59b73965_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


The MARTINI WG last call on the Requirements document concluded on March 5=
=2C 2010.=20

5 Issues were filed and were resolved as follows:


=20
=20
=20
=20
=20
=20
=20
=20
  Issue
  Description
  Document
  Status
  Resolution
  Severity
  Date Resolved
=20
=20
  #3  =20
  Requirement for identity assertions  =20
  reqs =20
  closed =20
  wontfix =20
  major =20
  3/8/2010
=20
=20
  #6=20
  AORs other than telephone numbers=20
  reqs=20
  closed=20
  wontfix=20
  critical=20
  3/8/2010
=20
=20
  #2=20
  Scaling to Several Thousand Assigned Telephone Numbers=20
  reqs=20
  closed=20
  wontfix=20
  major=20
  3/3/2010
=20
=20
  #5=20
  AORs other than telephone numbers=20
  gin=20
  closed=20
  duplicate=20
  critical=20
  3/2/2010
=20
=20
  #4=20
  PAI/PPI mismatches issue=20
  reqs=20
  closed=20
  fixed=20
  minor=20
  3/2/2010
=20
=20
  #1=20
  Editorial Issues=20
  reqs=20
  closed=20
  fixed=20
  trivial=20
  2/22/2010
=20


A revision of the requirements document including these resolves issues has=
 now been posted:
http://tools.ietf.org/html/draft-ietf-martini-reqs-02.txt

Next Steps
-----------

With the posting of -02=2C the MARTINI Requirements document

 		 	   		  =

--_89f026b3-d9de-4b71-a5ea-cd3a59b73965_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
The MARTINI WG last call on the Requirements document concluded on March 5=
=2C 2010. <br><br>5 Issues were filed and were resolved as follows:<br><br>
 <table style=3D"border-collapse: collapse=3B width: 648pt=3B" border=3D"0"=
 cellpadding=3D"0" cellspacing=3D"0" width=3D"863"><col style=3D"width: 49p=
t=3B" width=3D"65">
 <col style=3D"width: 285pt=3B" width=3D"380">
 <col style=3D"width: 62pt=3B" width=3D"83">
 <col style=3D"width: 58pt=3B" width=3D"77">
 <col style=3D"width: 65pt=3B" width=3D"87">
 <col style=3D"width: 56pt=3B" width=3D"74">
 <col style=3D"width: 73pt=3B" width=3D"97">
 <tbody><tr style=3D"height: 15pt=3B" height=3D"20">
  <td class=3D"xl66" style=3D"height: 15pt=3B width: 49pt=3B" width=3D"65" =
height=3D"20">Issue</td>
  <td class=3D"xl66" style=3D"width: 285pt=3B" width=3D"380">Description</t=
d>
  <td class=3D"xl66" style=3D"width: 62pt=3B" width=3D"83">Document</td>
  <td class=3D"xl66" style=3D"width: 58pt=3B" width=3D"77">Status</td>
  <td class=3D"xl66" style=3D"width: 65pt=3B" width=3D"87">Resolution</td>
  <td class=3D"xl66" style=3D"width: 56pt=3B" width=3D"74">Severity</td>
  <td class=3D"xl66" style=3D"width: 73pt=3B" width=3D"97">Date Resolved</t=
d>
 </tr>
 <tr style=3D"height: 15pt=3B" height=3D"20">
  <td style=3D"height: 15pt=3B" height=3D"20">#3<span style=3D"">&nbsp=3B&n=
bsp=3B&nbsp=3B</span></td>
  <td>Requirement for identity assertions<span style=3D"">&nbsp=3B&nbsp=3B&=
nbsp=3B</span></td>
  <td>reqs<span style=3D"">&nbsp=3B&nbsp=3B</span></td>
  <td>closed<span style=3D"">&nbsp=3B&nbsp=3B</span></td>
  <td>wontfix<span style=3D"">&nbsp=3B&nbsp=3B</span></td>
  <td>major<span style=3D"">&nbsp=3B&nbsp=3B</span></td>
  <td class=3D"xl65" align=3D"right">3/8/2010</td>
 </tr>
 <tr style=3D"height: 15pt=3B" height=3D"20">
  <td style=3D"height: 15pt=3B" height=3D"20">#6<span style=3D"">&nbsp=3B</=
span></td>
  <td>AORs other than telephone numbers<span style=3D"">&nbsp=3B</span></td=
>
  <td>reqs<span style=3D"">&nbsp=3B</span></td>
  <td>closed<span style=3D"">&nbsp=3B</span></td>
  <td>wontfix<span style=3D"">&nbsp=3B</span></td>
  <td>critical<span style=3D"">&nbsp=3B</span></td>
  <td class=3D"xl65" align=3D"right">3/8/2010</td>
 </tr>
 <tr style=3D"height: 15pt=3B" height=3D"20">
  <td style=3D"height: 15pt=3B" height=3D"20">#2<span style=3D"">&nbsp=3B</=
span></td>
  <td>Scaling to Several Thousand Assigned Telephone Numbers<span style=3D"=
">&nbsp=3B</span></td>
  <td>reqs<span style=3D"">&nbsp=3B</span></td>
  <td>closed<span style=3D"">&nbsp=3B</span></td>
  <td>wontfix<span style=3D"">&nbsp=3B</span></td>
  <td>major<span style=3D"">&nbsp=3B</span></td>
  <td class=3D"xl65" align=3D"right">3/3/2010</td>
 </tr>
 <tr style=3D"height: 15pt=3B" height=3D"20">
  <td style=3D"height: 15pt=3B" height=3D"20">#5<span style=3D"">&nbsp=3B</=
span></td>
  <td>AORs other than telephone numbers<span style=3D"">&nbsp=3B</span></td=
>
  <td>gin<span style=3D"">&nbsp=3B</span></td>
  <td>closed<span style=3D"">&nbsp=3B</span></td>
  <td>duplicate<span style=3D"">&nbsp=3B</span></td>
  <td>critical<span style=3D"">&nbsp=3B</span></td>
  <td class=3D"xl65" align=3D"right">3/2/2010</td>
 </tr>
 <tr style=3D"height: 15pt=3B" height=3D"20">
  <td style=3D"height: 15pt=3B" height=3D"20">#4<span style=3D"">&nbsp=3B</=
span></td>
  <td>PAI/PPI mismatches issue<span style=3D"">&nbsp=3B</span></td>
  <td>reqs<span style=3D"">&nbsp=3B</span></td>
  <td>closed<span style=3D"">&nbsp=3B</span></td>
  <td>fixed<span style=3D"">&nbsp=3B</span></td>
  <td>minor<span style=3D"">&nbsp=3B</span></td>
  <td class=3D"xl65" align=3D"right">3/2/2010</td>
 </tr>
 <tr style=3D"height: 15pt=3B" height=3D"20">
  <td style=3D"height: 15pt=3B" height=3D"20">#1<span style=3D"">&nbsp=3B</=
span></td>
  <td>Editorial Issues<span style=3D"">&nbsp=3B</span></td>
  <td>reqs<span style=3D"">&nbsp=3B</span></td>
  <td>closed<span style=3D"">&nbsp=3B</span></td>
  <td>fixed<span style=3D"">&nbsp=3B</span></td>
  <td>trivial<span style=3D"">&nbsp=3B</span></td>
  <td class=3D"xl65" align=3D"right">2/22/2010</td>
 </tr>
</tbody></table><br><br>A revision of the requirements document including t=
hese resolves issues has now been posted:<br>http://tools.ietf.org/html/dra=
ft-ietf-martini-reqs-02.txt<br><br>Next Steps<br>-----------<br><br>With th=
e posting of -02=2C the MARTINI Requirements document<br><table style=3D"bo=
rder-top: 1px solid black=3B font-weight: bold=3B font-family: 'Segoe UI'=
=2CTahoma=2Csan-serif=3B"><tbody><tr><td><a href=3D"http://im.live.com/Mess=
enger/IM/Home/?source=3DEML_WLHM_GreaterGood" style=3D"font-size: 9pt=3B co=
lor: rgb(1=2C 132=2C 203)=3B text-decoration: none=3B"><span style=3D"paddi=
ng: 0px 24px=3B font-size: 8pt=3B color: rgb(63=2C 181=2C 85)=3B text-decor=
ation: underline=3B"></span></a><br></td></tr></tbody></table> 		 	   		  <=
/body>
</html>=

--_89f026b3-d9de-4b71-a5ea-cd3a59b73965_--

From bernard_aboba@hotmail.com  Thu Mar 18 13:44:37 2010
Return-Path: <bernard_aboba@hotmail.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 8AFFF3A687F for <martini@core3.amsl.com>; Thu, 18 Mar 2010 13:44:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.138
X-Spam-Level: 
X-Spam-Status: No, score=0.138 tagged_above=-999 required=5 tests=[AWL=-0.994,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 ZOgFus2j2H6x for <martini@core3.amsl.com>; Thu, 18 Mar 2010 13:44:36 -0700 (PDT)
Received: from blu0-omc2-s4.blu0.hotmail.com (blu0-omc2-s4.blu0.hotmail.com [65.55.111.79]) by core3.amsl.com (Postfix) with ESMTP id 4A0923A69BE for <martini@ietf.org>; Thu, 18 Mar 2010 13:44:33 -0700 (PDT)
Received: from BLU137-DS17 ([65.55.111.72]) by blu0-omc2-s4.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 18 Mar 2010 13:44:44 -0700
X-Originating-IP: [76.108.77.56]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS178707B566969188B28F3B932B0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <martini@ietf.org>
Date: Thu, 18 Mar 2010 16:45:08 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_003D_01CAC6BA.5E9721A0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcrG2+VnWS7Pfl32S6akNZXrgj+3gQ==
Content-Language: en-us
X-OriginalArrivalTime: 18 Mar 2010 20:44:44.0411 (UTC) FILETIME=[D733BCB0:01CAC6DB]
Subject: [martini] Conclusion of MARTINI WG last call on the Requirements Document (untruncated version)
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: Thu, 18 Mar 2010 20:44:37 -0000

------=_NextPart_000_003D_01CAC6BA.5E9721A0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

The MARTINI WG last call on the Requirements document concluded on March 5,
2010. 

6 Issues were filed.  The issues were resolved as follows:


Issue

Description

Document

Status

Resolution

Severity

Date Resolved


#3   

Requirement for identity assertions   

reqs  

closed  

wontfix  

major  

3/8/2010


#6 

AORs other than telephone numbers 

reqs 

closed 

wontfix 

critical 

3/8/2010


#2 

Scaling to Several Thousand Assigned Telephone Numbers 

reqs 

closed 

wontfix 

major 

3/3/2010


#5 

AORs other than telephone numbers 

gin 

closed 

duplicate 

critical 

3/2/2010


#4 

PAI/PPI mismatches issue 

reqs 

closed 

fixed 

minor 

3/2/2010


#1 

Editorial Issues 

reqs 

closed 

fixed 

trivial 

2/22/2010



A revision of the requirements document including the resolutions has now
been posted:
http://tools.ietf.org/html/draft-ietf-martini-reqs-02.txt

Next Steps
-----------

With the posting of -02, the MARTINI Requirements document is now ready for
use in evaluating solution proposals. Utilizing the -02 requirements in
evaluating solutions is the next step, since this will both enhance our
confidence in the requirements as well as enabling further discussion and
refinement of the solution proposals.   


------=_NextPart_000_003D_01CAC6BA.5E9721A0
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:12.0pt;
font-family:"Times New Roman","serif"'>The MARTINI WG last call on the
Requirements document concluded on March 5, 2010. <br>
<br>
6 Issues were filed.&nbsp; The issues were resolved as =
follows:<o:p></o:p></span></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D864
 style=3D'width:9.0in;border-collapse:collapse'>
 <tr style=3D'height:15.0pt'>
  <td width=3D65 style=3D'width:49.0pt;padding:0in 0in 0in =
0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>Issue<o:p></o:p></span></p>
  </td>
  <td width=3D380 style=3D'width:285.0pt;padding:0in 0in 0in =
0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>Description<o:p></o:p></span></p>
  </td>
  <td width=3D83 style=3D'width:62.0pt;padding:0in 0in 0in =
0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>Document<o:p></o:p></span></p>
  </td>
  <td width=3D77 style=3D'width:58.0pt;padding:0in 0in 0in =
0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>Status<o:p></o:p></span></p>
  </td>
  <td width=3D87 style=3D'width:65.0pt;padding:0in 0in 0in =
0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>Resolution<o:p></o:p></span></p>
  </td>
  <td width=3D75 style=3D'width:56.0pt;padding:0in 0in 0in =
0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>Severity<o:p></o:p></span></p>
  </td>
  <td width=3D97 style=3D'width:73.0pt;padding:0in 0in 0in =
0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>Date
  Resolved<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>#3&nbsp;&nbsp;&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>Requirement
  for identity assertions&nbsp;&nbsp;&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>reqs&nbsp;&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>closed&nbsp;&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>wontfix&nbsp;&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>major&nbsp;&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>3/8/2010<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>#6&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>AORs
  other than telephone numbers&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>reqs&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>closed&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>wontfix&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>critical&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>3/8/2010<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>#2&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>Scaling
  to Several Thousand Assigned Telephone =
Numbers&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>reqs&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>closed&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>wontfix&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>major&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>3/3/2010<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>#5&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>AORs
  other than telephone numbers&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>gin&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>closed&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>duplicate&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>critical&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>3/2/2010<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>#4&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>PAI/PPI
  mismatches issue&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>reqs&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>closed&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>fixed&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>minor&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>3/2/2010<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>#1&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>Editorial
  Issues&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>reqs&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>closed&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>fixed&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>trivial&nbsp;<o:p></o:p></span></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in;height:15.0pt'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>2/22/2010<o:p></o:p></span></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif"'><br>
<br>
A revision of the requirements document including the resolutions has =
now been
posted:<br>
http://tools.ietf.org/html/draft-ietf-martini-reqs-02.txt<br>
<br>
Next Steps<br>
-----------<br>
<br>
With the posting of -02, the MARTINI Requirements document is now ready =
for use
in evaluating solution proposals. Utilizing the -02 requirements in =
evaluating
solutions is the next step, since this will both enhance our confidence =
in the
requirements as well as enabling further discussion and refinement of =
the
solution proposals.&nbsp; &nbsp;</span><o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_003D_01CAC6BA.5E9721A0--

From trac@tools.ietf.org  Thu Mar 18 15:02:28 2010
Return-Path: <trac@tools.ietf.org>
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 67A833A6BBF for <martini@core3.amsl.com>; Thu, 18 Mar 2010 15:02:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.909
X-Spam-Level: 
X-Spam-Status: No, score=-101.909 tagged_above=-999 required=5 tests=[AWL=-0.439, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 HpFZ9d6GGkpt for <martini@core3.amsl.com>; Thu, 18 Mar 2010 15:02:27 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id C81813A6BBC for <martini@ietf.org>; Thu, 18 Mar 2010 15:02:26 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NsNna-0000ro-U6; Thu, 18 Mar 2010 15:02:38 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: ietf.hanserik@gmail.com
X-Trac-Project: martini
Date: Thu, 18 Mar 2010 22:02:38 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/15
Message-ID: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org>
X-Trac-Ticket-ID: 15
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: ietf.hanserik@gmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #15: support for non E.164 numbers
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 18 Mar 2010 22:02:28 -0000

#15: support for non E.164 numbers
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |       Owner:            
     Type:  defect                   |      Status:  new       
 Priority:  critical                 |   Milestone:  milestone1
Component:  reqs                     |     Version:  1.0       
 Severity:  In WG Last Call          |    Keywords:            
-------------------------------------+--------------------------------------
 REQ19 - The mechanism MUST allow a set of assigned telephone numbers to
 comprise local numbers as specified in RFC3966, which can be in
 contiguous ranges, discrete, or in any combination of the two.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/15>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Thu Mar 18 15:12:12 2010
Return-Path: <trac@tools.ietf.org>
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 067693A6952 for <martini@core3.amsl.com>; Thu, 18 Mar 2010 15:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.898
X-Spam-Level: 
X-Spam-Status: No, score=-101.898 tagged_above=-999 required=5 tests=[AWL=-0.428, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 yCST68W0EUqj for <martini@core3.amsl.com>; Thu, 18 Mar 2010 15:12:11 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 6523F3A6872 for <martini@ietf.org>; Thu, 18 Mar 2010 15:12:11 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NsNx1-0003NX-J8; Thu, 18 Mar 2010 15:12:23 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: ietf.hanserik@gmail.com
X-Trac-Project: martini
Date: Thu, 18 Mar 2010 22:12:23 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/16
Message-ID: <065.111f925a59a8643c429a6e1e5e86d2da@tools.ietf.org>
X-Trac-Ticket-ID: 16
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: ietf.hanserik@gmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #16: Extensibility to support any AOR
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 18 Mar 2010 22:12:12 -0000

#16: Extensibility to support any AOR
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |       Owner:            
     Type:  enhancement              |      Status:  new       
 Priority:  critical                 |   Milestone:  milestone1
Component:  reqs                     |     Version:  1.0       
 Severity:  In WG Last Call          |    Keywords:            
-------------------------------------+--------------------------------------
 REQ20 - The mechanism MUST be extensible to allow a set of arbitrary
 assigned SIP URI's as specified in RFC3261, without requiring a complete
 change of mechanism as compared to that used for numbers.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/16>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Thu Mar 18 15:21:06 2010
Return-Path: <trac@tools.ietf.org>
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 C685F3A6944 for <martini@core3.amsl.com>; Thu, 18 Mar 2010 15:21:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.889
X-Spam-Level: 
X-Spam-Status: No, score=-101.889 tagged_above=-999 required=5 tests=[AWL=-0.419, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 eRiRaowOC5tK for <martini@core3.amsl.com>; Thu, 18 Mar 2010 15:21:06 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 3A7F23A6952 for <martini@ietf.org>; Thu, 18 Mar 2010 15:20:27 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NsO51-0007Fr-Io; Thu, 18 Mar 2010 15:20:39 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: ietf.hanserik@gmail.com
X-Trac-Project: martini
Date: Thu, 18 Mar 2010 22:20:39 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/17
Message-ID: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org>
X-Trac-Ticket-ID: 17
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: ietf.hanserik@gmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #17: Desirable to align with existing standards
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 18 Mar 2010 22:21:07 -0000

#17: Desirable to align with existing standards
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |       Owner:            
     Type:  enhancement              |      Status:  new       
 Priority:  major                    |   Milestone:  milestone1
Component:  reqs                     |     Version:  1.0       
 Severity:  In WG Last Call          |    Keywords:            
-------------------------------------+--------------------------------------
 DES5 - The mechanism SHOULD be aligned as much as possible with mechanisms
 already standardised in other SDO's like ETSI and 3GPP in order to
 prohibit a fragmentation of the market.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/17>
martini <http://tools.ietf.org/martini/>


From adam@nostrum.com  Thu Mar 18 15:53:10 2010
Return-Path: <adam@nostrum.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 18EC43A697D for <martini@core3.amsl.com>; Thu, 18 Mar 2010 15:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level: 
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[AWL=-0.435, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, SPF_PASS=-0.001]
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 qM4qB6W5Q4bu for <martini@core3.amsl.com>; Thu, 18 Mar 2010 15:53:09 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id D2C733A67D7 for <martini@ietf.org>; Thu, 18 Mar 2010 15:53:08 -0700 (PDT)
Received: from [172.16.3.231] (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o2IMr9AG099391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Mar 2010 17:53:10 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4BA2AED5.5040903@nostrum.com>
Date: Thu, 18 Mar 2010 17:53:09 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: trac@localhost.amsl.com
References: <065.111f925a59a8643c429a6e1e5e86d2da@tools.ietf.org>
In-Reply-To: <065.111f925a59a8643c429a6e1e5e86d2da@tools.ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: martini issue tracker <trac@tools.ietf.org>, martini@ietf.org
Subject: Re: [martini] #16: Extensibility to support any 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: Thu, 18 Mar 2010 22:53:10 -0000

Satisfying this requirement would require solving the general case 
before we can declare victory on the phone number case. I think we've 
already come to a pretty strong consensus that we're doing the phone 
number case first, for the sake of expediency.

I would also argue that opening trac bugs to request features that are 
intentionally duplicates (this one duplicates bugs #5 and #6) and 
contrary to apparent working group consensus is an abuse of the trac system.

This should be closed as a duplicate of #6.

/a

On 3/18/10 5:12 PM, martini issue tracker wrote:
> #16: Extensibility to support any AOR
> -------------------------------------+--------------------------------------
>   Reporter:  ietf.hanserik@…          |       Owner:
>       Type:  enhancement              |      Status:  new
>   Priority:  critical                 |   Milestone:  milestone1
> Component:  reqs                     |     Version:  1.0
>   Severity:  In WG Last Call          |    Keywords:
> -------------------------------------+--------------------------------------
>   REQ20 - The mechanism MUST be extensible to allow a set of arbitrary
>   assigned SIP URI's as specified in RFC3261, without requiring a complete
>   change of mechanism as compared to that used for numbers.
>
>    


From jan.van.geel@belgacom.be  Fri Mar 19 00:36:01 2010
Return-Path: <jan.van.geel@belgacom.be>
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 3A6FA3A68C3 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 00:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.132
X-Spam-Level: *
X-Spam-Status: No, score=1.132 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 oHNiiH7Tij-b for <martini@core3.amsl.com>; Fri, 19 Mar 2010 00:35:49 -0700 (PDT)
Received: from inmxcar01.belgacom.be (inmxcar01.belgacom.be [195.13.11.182]) by core3.amsl.com (Postfix) with ESMTP id 386173A6778 for <martini@ietf.org>; Fri, 19 Mar 2010 00:35:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.51,273,1267398000"; d="scan'208,217";a="79941719"
Received: from unknown (HELO A03007.BGC.NET) ([10.120.129.162]) by outmxcar01.belgacom.be with ESMTP; 19 Mar 2010 08:35:59 +0100
X-TM-IMSS-Message-ID: <0289ba3300002c00@belgacom.be>
Received: from AE7111.BGC.NET ([45.219.2.50]) by belgacom.be ([10.120.129.162]) with ESMTP (TREND IMSS SMTP Service 7.0; TLS: TLSv1/SSLv3,128bits,RC4-MD5) id 0289ba3300002c00 ; Fri, 19 Mar 2010 08:35:58 +0100
Received: from CMS03.BGC.NET ([10.120.128.133]) by AE7111.BGC.NET ([45.219.2.50]) with mapi; Fri, 19 Mar 2010 08:35:57 +0100
From: <jan.van.geel@belgacom.be>
To: <ietf.hanserik@gmail.com>
Date: Fri, 19 Mar 2010 08:35:56 +0100
Thread-Topic: [martini] Call for Adoption of "Registration for Multiple PhoneNumbers in the SIP"
Thread-Index: AcrGwl6otlrQVir5TLWH7AHOk2VzfQAc9NJQ
Message-ID: <208EAE1DFA28FC419529619ABB8622441617535005@CMS03.BGC.NET>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl> <09B7DBFE70A9E24BBB21689DAD3A06141CF400B7@zcarhxm1.corp.nortel.com> <208EAE1DFA28FC419529619ABB8622441616E6C19B@CMS03.BGC.NET> <9ae56b1e1003181042u3e21d1bax79124b1584e8e40d@mail.gmail.com>
In-Reply-To: <9ae56b1e1003181042u3e21d1bax79124b1584e8e40d@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
x-tm-as-product-ver: SMEX-8.0.0.1285-6.000.1038-17260.005
x-tm-as-result: No--65.924300-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_208EAE1DFA28FC419529619ABB8622441617535005CMS03BGCNET_"
MIME-Version: 1.0
Cc: bernard_aboba@hotmail.com, martini@ietf.org
Subject: Re: [martini] Call for Adoption of "Registration for Multiple PhoneNumbers in the SIP"
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: Fri, 19 Mar 2010 07:36:01 -0000

--_000_208EAE1DFA28FC419529619ABB8622441617535005CMS03BGCNET_
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hans=20Erik,=20all,

Maybe=20I=20misunderstand=20(some=20of)=20the=20use=20cases,=20but=20to=
=20me=20UC3=20looks=20like=20a=20PBX=20using=20a=20group=20REGISTER,=20as=
=20described=20in=203GPP/ETSI=20documents.=20The=20Conclusion=20of=20this=
=20discussion=20document=20seems=20to=20indicate=20that=20this=20is=20the=
=20solution=20with=20the=20lesser=20drawbacks,=20right=20?

Kind=20regards


Jan=20Van=20Geel
IT=20and=20Network=20Development=20Specialist
Belgacom=20SDE/SDV/PSE/NST/NCP
Tel:=20+32=202=20202=201035
Tel:=20+32=202=20207=204442
Tel:=20+32=202=20207=209032
Email=20:=20jan.van.geel@belgacom.be
www.cyberwezz.tk


From:=20Hans=20Erik=20van=20Elburg=20[mailto:ietf.hanserik@gmail.com]
Sent:=2018=20March=202010=2018:42
To:=20VAN=20GEEL=20Jan=20(ITN/NIS)
Cc:=20blindsay@nortel.com;=20bernard_aboba@hotmail.com;=20martini@ietf.or=
g
Subject:=20Re:=20[martini]=20Call=20for=20Adoption=20of=20"Registration=
=20for=20Multiple=20PhoneNumbers=20in=20the=20SIP"

+1

Allowing=20both=20UC-3=20and=20UC-6/9=20scenarios=20could=20be=20a=20way=
=20forward,=20use=20cases=20or=20scenarios=20as=20depicted=20in:
http://aboba.drizzlehosting.com/MARTINI/Jan-Interim-III/IETF77_MARTINI_Fe=
b9Interim_Use_models.pdf

PBX=20configurations=20that=20are=20fine=20with=20the=20limitations=20or=
=20limited=20themselves=20can=20register=20and=20indicate=20they=20are=20=
expecting=20UC-3=20style.
PBX=20configurations=20that=20need=20more=20advanced=20setups=20can=20reg=
ister=20and=20indicate=20they=20are=20expecting=20UC-6/9=20style.

BR,
/Hans=20Erik=20van=20Elburg
On=20Thu,=20Mar=2018,=202010=20at=209:06=20AM,=20<jan.van.geel@belgacom.b=
e<mailto:jan.van.geel@belgacom.be>>=20wrote:
Hi,

As=20service=20provider=20I=20completely=20agree=20with=20the=20statement=
=20that=20a=20common=20approach=20is=20beneficial=20for=20the=20industry.=
=20Therefore=20I=20would=20prefer=20that=20alignment=20with=20existing=20=
specifications=20of=203GPP/ETSI=20is=20sought=20as=20much=20as=20possible=
.

Kind=20regards


Jan=20Van=20Geel
IT=20and=20Network=20Development=20Specialist
Belgacom=20SDE/SDV/PSE/NST/NCP
Tel:=20+32=202=20202=201035
Tel:=20+32=202=20207=204442
Tel:=20+32=202=20207=209032
Email=20:=20jan.van.geel@belgacom.be<mailto:jan.van.geel@belgacom.be>
www.cyberwezz.tk<http://www.cyberwezz.tk>


From:=20martini-bounces@ietf.org<mailto:martini-bounces@ietf.org>=20[mail=
to:martini-bounces@ietf.org<mailto:martini-bounces@ietf.org>]=20On=20Beha=
lf=20Of=20Brian=20Lindsay
Sent:=2017=20March=202010=2014:51
To:=20Bernard=20Aboba;=20MARTINI
Subject:=20Re:=20[martini]=20Call=20for=20Adoption=20of=20"Registration=
=20for=20Multiple=20PhoneNumbers=20in=20the=20SIP"

Hi=20Bernard,

=20=20=20I=20think=20the=20gin=20draft=20could=20form=20the=20basis=20of=
=20a=20solution,=20but=20at=20as=20couple=20of=20other=20folks=20have=20n=
oted=20there=20already=20is=20a=20solution=20standardized=20by=20TIPAN/3G=
PP=20which=20uses=20a=20different=20approach=20for=20request=20routing=20=
for=20SIP=20PBXs.=20It=20would=20be=20ideal=20if=20we=20had=20one=20commo=
n=20approach=20in=20the=20industry,=20otherwise=20we=20are=20going=20to=
=20see=20some=20carriers=20require=20one=20solution=20and=20other=20carri=
ers=20the=20other=20solution=20and=20vendors=20on=20both=20the=20enterpri=
se=20and=20carrier=20side=20will=20need=20to=20implement=20and=20support=
=20both.

=20=20=20The=20shaken=20draft=20is=20closer=20to=20the=20TISPAN/3GPP=20ap=
proach=20and=20is=20essentially=20adding=20some=20incremental=20improveme=
nts.=20I'd=20be=20more=20inclined=20to=20go=20with=20the=20shaken=20appoa=
ch=20at=20this=20time=20given=20it's=20alignment=20with=20the=20existing=
=20standardized=20TISPAN/3GPP=20solution.

=20=20=20I=20haven't=20heard=20too=20many=20other=20responses=20on=20the=
=20call=20for=20adoption=20from=20SSP=20vendors=20so=20I'm=20curious=20on=
=20that=20front=20what=20others=20are=20thinking.

=20=20=20Thanks
=20=20=20=20=20=20=20Brian

________________________________
From:=20martini-bounces@ietf.org<mailto:martini-bounces@ietf.org>=20[mail=
to:martini-bounces@ietf.org<mailto:martini-bounces@ietf.org>]=20On=20Beha=
lf=20Of=20Bernard=20Aboba
Sent:=20Thursday,=20March=2004,=202010=205:02=20PM
To:=20'MARTINI'
Subject:=20[martini]=20Call=20for=20Adoption=20of=20"Registration=20for=
=20Multiple=20PhoneNumbers=20in=20the=20SIP"
This=20is=20a=20MARTINI=20WG=20Call=20for=20Adoption=20of=20"Registration=
=20for=20Multiple=20Phone=20Numbers=20in=20the=20SIP"=20as=20a=20MARTINI=
=20WG=20work=20item,=20corresponding=20to=20the=20"Multiple=20AoR=20Regis=
tration=20specification"=20Charter=20deliverable.=20=20The=20document=20i=
s=20available=20for=20inspection=20here:
http://tools.ietf.org/html/draft-roach-martini-gin-01.txt
The=20MARTINI=20WG=20Call=20for=20Adoption=20will=20last=20until=20Friday=
,=20March=2019,=202010.
Please=20respond=20to=20this=20WG=20Call=20for=20Adoption,=20whether=20yo=
u=20are=20in=20favor=20of=20adopting=20the=20document=20as=20a=20MARTINI=
=20WG=20work=20item=20or=20not.=20=20If=20you=20have=20no=20comments,=20p=
lease=20reply=20to=20this=20message=20and=20indicate=20in=20the=20body=20=
of=20your=20message=20whether=20you=20think=20the=20document=20is=20ready=
=20for=20adoption=20as=20a=20MARTINI=20WG=20work=20item=20or=20not.=20=20=
=20Based=20on=20the=20response,=20the=20MARTINI=20WG=20chairs=20will=20at=
tempt=20to=20determine=20whether=20WG=20consensus=20exists=20to=20adopt=
=20the=20document=20or=20not.
If=20you=20have=20comments,=20please=20provide=20them=20to=20the=20WG=20i=
n=20one=20of=20the=20following=20ways:

1.=20=20=20=20=20=20The=20preferred=20choice=20is=20to=20open=20an=20issu=
e=20in=20the=20MARTINI=20Issue=20tracking=20database=20(TRAC),=20which=20=
is=20available=20here:=20http://trac.tools.ietf.org/wg/martini/trac/newti=
cket=20=20Information=20on=20how=20to=20use=20TRAC=20is=20provided=20belo=
w.=20=20Note=20that=20if=20you=20submit=20an=20issue=20in=20TRAC,=20it=20=
will=20automatically=20also=20be=20posted=20to=20the=20MARTINI=20WG=20mai=
ling=20list.=20=20When=20submitting=20issues=20in=20TRAC=20for=20this=20"=
call=20for=20adoption",=20please=20enter=20"gin"=20for=20the=20Component:=
=20and=20"Candidate=20WG=20Document"=20for=20Severity.
=202.=20If=20you=20can't=20figure=20out=20how=20to=20use=20TRAC,=20please=
=20post=20your=20Issue=20to=20the=20MARTINI=20WG=20mailing=20list=20(mart=
ini=20at=20ietf.org<http://ietf.org>)=20in=20the=20following=20format:
To:=20=20martini=20at=20ietf.org<http://ietf.org>
Subject:=20GIN-Issue:=20<title=20of=20your=20issue>
Priority:=20blocker,=20critical,=20major,=20minor=20or=20trivial
<Explanation=20of=20your=20issue,=20including=20a=20proposal=20for=20spec=
ific=20text=20changes=20to=20resolve=20the=20issue>
The=20MARTINI=20WG=20uses=20the=20TRAC=20database=20to=20keep=20track=20o=
f=20issues=20relating=20to=20work=20in=20progress,=20including=20working=
=20group=20work=20items=20and=20individual=20submissions=20undergoing=20r=
eview.=20=20=20=20This=20document=20provides=20some=20basic=20information=
=20on=20how=20MARTINI=20WG=20participants=20can=20use=20TRAC=20to=20submi=
t=20or=20edit=20issues.
Documentation=20relating=20to=20the=20TRAC=20Issue=20Tracking=20database=
=20is=20available=20here:
http://trac.tools.ietf.org/wg/martini/trac/wiki
Since=20this=20documentation=20is=20somewhat=20lengthy=20(and=20mostly=20=
relevant=20to=20Admins),=20here=20is=20a=20pithy=20synopsis.

1.=20=20=20=20=20=20=20To=20submit=20an=20issue=20in=20the=20MARTINI=20Is=
sues=20database=20(known=20as=20TRAC),=20you=20first=20need=20to=20login=
=20to=20the=20MARTINI=20WG=20site=20on=20the=20tools=20server=20(http://t=
ools.ietf.org/wg/martini/trac/login=20)

2.=20=20=20=20=20=20=20If=20you=20don't=20already=20have=20a=20login=20ID=
,=20you=20can=20obtain=20one=20by=20navigating=20to=20this=20site:=20=20=
=20http://trac.tools.ietf.org/newlogin

3.=20=20=20=20=20=20=20Once=20you=20have=20obtained=20an=20account,=20you=
=20can=20log=20in=20by=20clicking=20on=20the=20"login"=20entry=20at=20the=
=20top=20of=20the=20page.=20=20Once=20you=20have=20logged=20in,=20you=20c=
an=20file=20an=20issue=20by=20navigating=20to=20the=20=20ticket=20entry=
=20form:=20http://trac.tools.ietf.org/wg/martini/trac/newticket

4=20=20=20=20=20When=20opening=20an=20issue:

a.=20=20=20=20=20=20=20The=20Type:=20field=20should=20be=20set=20to=20"de=
fect"=20for=20an=20issue=20with=20the=20current=20document=20text,=20or=
=20"enhancement"=20for=20a=20proposed=20addition=20of=20functionality=20(=
such=20as=20an=20additional=20requirement).

b.=20=20=20=20=20=20The=20Priority:=20field=20is=20set=20based=20on=20the=
=20severity=20of=20the=20Issue.=20=20=20For=20example,=20editorial=20issu=
es=20are=20typically=20"minor"=20or=20"trivial".

c.=20=20=20=20=20=20=20The=20Milestone:=20field=20should=20be=20set=20to=
=20milestone1=20(useless,=20I=20know).

d.=20=20=20=20=20=20The=20Component:=20field=20should=20be=20set=20to=20t=
he=20document=20you=20are=20filing=20the=20issue=20on.=20=20In=20respondi=
ng=20to=20the=20GIN=20Call=20for=20Adoption,=20"gin"=20is=20the=20appropr=
iate=20choice.

e.=20=20=20=20=20=20The=20Version:=20field=20should=20be=20set=20to=20"1.=
0".

f.=20=20=20=20=20=20=20=20The=20Severity:=20field=20should=20be=20set=20t=
o=20based=20on=20the=20status=20of=20the=20document=20(e.g.=20"Candidate=
=20WG=20Document"=20in=20this=20case)

g.=20=20=20=20=20=20=20=20The=20Keywords:=20and=20CC:=20fields=20can=20be=
=20left=20blank=20unless=20inspiration=20seizes=20you.

h.=20=20=20=20=20=20The=20Assign=20To:=20field=20is=20generally=20filled=
=20in=20with=20the=20email=20address=20of=20the=20editor.

5.=20=20=20=20=20=20=20Typically=20it=20won't=20be=20necessary=20to=20enc=
lose=20a=20file=20with=20the=20ticket,=20but=20if=20you=20need=20to,=20se=
lect=20"I=20have=20files=20to=20attach=20to=20this=20ticket".

6.=20=20=20=20=20=20=20If=20you=20want=20to=20preview=20your=20Issue,=20c=
lick=20on=20the=20"Preview"=20button.=20=20When=20you're=20ready=20to=20s=
ubmit=20the=20issue,=20click=20on=20the=20"Create=20Ticket"=20button.
That's=20it!
If=20you=20have=20an=20problems=20in=20dealing=20with=20TRAC,=20send=20em=
ail=20to=20me=20and=20I'll=20try=20to=20figure=20out=20what's=20going=20o=
n.
Happy=20TRACing,
Bernard


****=20DISCLAIMER=20****

http://www.belgacom.be/maildisclaimer


_______________________________________________
martini=20mailing=20list
martini@ietf.org<mailto:martini@ietf.org>
https://www.ietf.org/mailman/listinfo/martini


****=20DISCLAIMER=20****
http://www.belgacom.be/maildisclaimer

--_000_208EAE1DFA28FC419529619ABB8622441617535005CMS03BGCNET_
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html=20xmlns:v=3D"urn:schemas-microsoft-com:vml"=20xmlns:o=3D"urn:schema=
s-microsoft-com:office:office"=20xmlns:w=3D"urn:schemas-microsoft-com:off=
ice:word"=20xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"=
=20xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta=20http-equiv=3DContent-Type=20content=3D"text/html;=20charset=3Dus-=
ascii">
<meta=20name=3DGenerator=20content=3D"Microsoft=20Word=2012=20(filtered=
=20medium)">
<!--[if=20!mso]>
<style>
v\:*=20{behavior:url(#default#VML);}
o\:*=20{behavior:url(#default#VML);}
w\:*=20{behavior:url(#default#VML);}
.shape=20{behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
=20/*=20Font=20Definitions=20*/
=20@font-face
=09{font-family:Calibri;
=09panose-1:2=2015=205=202=202=202=204=203=202=204;}
@font-face
=09{font-family:Tahoma;
=09panose-1:2=2011=206=204=203=205=204=204=202=204;}
@font-face
=09{font-family:Verdana;
=09panose-1:2=2011=206=204=203=205=204=204=202=204;}
@font-face
=09{font-family:Consolas;
=09panose-1:2=2011=206=209=202=202=204=203=202=204;}
=20/*=20Style=20Definitions=20*/
=20p.MsoNormal,=20li.MsoNormal,=20div.MsoNormal
=09{margin:0cm;
=09margin-bottom:.0001pt;
=09font-size:12.0pt;
=09font-family:"Times=20New=20Roman","serif";}
a:link,=20span.MsoHyperlink
=09{mso-style-priority:99;
=09color:blue;
=09text-decoration:underline;}
a:visited,=20span.MsoHyperlinkFollowed
=09{mso-style-priority:99;
=09color:purple;
=09text-decoration:underline;}
p
=09{mso-style-priority:99;
=09mso-margin-top-alt:auto;
=09margin-right:0cm;
=09mso-margin-bottom-alt:auto;
=09margin-left:0cm;
=09font-size:12.0pt;
=09font-family:"Times=20New=20Roman","serif";}
pre
=09{mso-style-priority:99;
=09mso-style-link:"HTML=20Preformatted=20Char";
=09margin:0cm;
=09margin-bottom:.0001pt;
=09font-size:10.0pt;
=09font-family:"Courier=20New";}
span.HTMLPreformattedChar
=09{mso-style-name:"HTML=20Preformatted=20Char";
=09mso-style-priority:99;
=09mso-style-link:"HTML=20Preformatted";
=09font-family:"Consolas","serif";}
span.EmailStyle20
=09{mso-style-type:personal-reply;
=09font-family:"Verdana","sans-serif";
=09color:blue;
=09font-weight:normal;
=09font-style:normal;
=09text-decoration:none=20none;}
.MsoChpDefault
=09{mso-style-type:export-only;}
@page=20WordSection1
=09{size:612.0pt=20792.0pt;
=09margin:72.0pt=2072.0pt=2072.0pt=2072.0pt;}
div.WordSection1
=09{page:WordSection1;}
-->
</style>
<!--[if=20gte=20mso=209]><xml>
=20<o:shapedefaults=20v:ext=3D"edit"=20spidmax=3D"1026"=20/>
</xml><![endif]--><!--[if=20gte=20mso=209]><xml>
=20<o:shapelayout=20v:ext=3D"edit">
=20=20<o:idmap=20v:ext=3D"edit"=20data=3D"1"=20/>
=20</o:shapelayout></xml><![endif]-->
</head>

<body=20lang=3DEN-GB=20link=3Dblue=20vlink=3Dpurple>

<div=20class=3DWordSection1>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'>Hans=20Erik,=20all,<o:p></o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'>Maybe=20I=20misunderstand=20(some=20of)=20the=20use=20cases,=
=20but=20to=20me=20UC3=20looks
like=20a=20PBX=20using=20a=20group=20REGISTER,=20as=20described=20in=203G=
PP/ETSI=20documents.=20The
Conclusion=20of=20this=20discussion=20document=20seems=20to=20indicate=20=
that=20this=20is=20the
solution=20with=20the=20lesser=20drawbacks,=20right=20?<o:p></o:p></span>=
</p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'>Kind=20regards<o:p></o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

<p=20class=3DMsoNormal><b><span=20style=3D'font-family:"Arial","sans-seri=
f";color:blue'>Jan
Van=20Geel</span></b><span=20style=3D'color:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"=
;
color:blue'>IT=20and=20Network=20Development=20Specialist</span><span=20s=
tyle=3D'color:
blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"=
;
color:blue'>Belgacom=20SDE/SDV/PSE/NST/NCP</span><span=20style=3D'color:b=
lue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"=
;
color:blue'>Tel:=20+32=202=20202=201035</span><span=20style=3D'color:blue=
'>=20<br>
</span><span=20style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"=
;
color:blue'>Tel:=20+32=202=20207=204442</span><span=20style=3D'color:blue=
'>=20<br>
</span><span=20style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"=
;
color:blue'>Tel:=20+32=202=20207=209032</span><span=20style=3D'color:blue=
'>=20<br>
</span><span=20style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"=
;
color:blue'>Email=20:=20jan.van.geel@belgacom.be</span><span=20style=3D'c=
olor:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"=
;
color:blue'>www.cyberwezz.tk</span><span=20style=3D'color:blue'>=20</span=
><span
style=3D'font-size:9.0pt;font-family:"Verdana","sans-serif";color:blue'><=
o:p></o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

<p=20class=3DMsoNormal><span=20style=3D'font-size:9.0pt;font-family:"Verd=
ana","sans-serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

<div=20style=3D'border:none;border-top:solid=20#B5C4DF=201.0pt;padding:3.=
0pt=200cm=200cm=200cm'>

<p=20class=3DMsoNormal><b><span=20lang=3DEN-US=20style=3D'font-size:10.0p=
t;font-family:
"Tahoma","sans-serif"'>From:</span></b><span=20lang=3DEN-US=20style=3D'fo=
nt-size:10.0pt;
font-family:"Tahoma","sans-serif"'>=20Hans=20Erik=20van=20Elburg
[mailto:ietf.hanserik@gmail.com]=20<br>
<b>Sent:</b>=2018=20March=202010=2018:42<br>
<b>To:</b>=20VAN=20GEEL=20Jan=20(ITN/NIS)<br>
<b>Cc:</b>=20blindsay@nortel.com;=20bernard_aboba@hotmail.com;=20martini@=
ietf.org<br>
<b>Subject:</b>=20Re:=20[martini]=20Call=20for=20Adoption=20of=20&quot;Re=
gistration=20for
Multiple=20PhoneNumbers=20in=20the=20SIP&quot;<o:p></o:p></span></p>

</div>

<p=20class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p=20class=3DMsoNormal=20style=3D'margin-bottom:12.0pt'>+1<br>
<br>
Allowing=20both=20UC-3=20and=20UC-6/9=20scenarios=20could=20be=20a=20way=
=20forward,=20use=20cases=20or
scenarios=20as=20depicted=20in:<br>
<a
href=3D"http://aboba.drizzlehosting.com/MARTINI/Jan-Interim-III/IETF77_MA=
RTINI_Feb9Interim_Use_models.pdf"
target=3D"_blank">http://aboba.drizzlehosting.com/MARTINI/Jan-Interim-III=
/IETF77_MARTINI_Feb9Interim_Use_models.pdf</a><br>
<br>
PBX=20configurations=20that=20are=20fine=20with=20the=20limitations=20or=
=20limited=20themselves=20can
register=20and=20indicate=20they=20are=20expecting=20UC-3=20style.<br>
PBX=20configurations=20that=20need=20more=20advanced=20setups=20can=20reg=
ister=20and=20indicate
they=20are=20expecting=20UC-6/9=20style.<br>
<br>
BR,<br=20clear=3Dall>
/Hans=20Erik=20van=20Elburg<o:p></o:p></p>

<div>

<p=20class=3DMsoNormal>On=20Thu,=20Mar=2018,=202010=20at=209:06=20AM,=20&=
lt;<a
href=3D"mailto:jan.van.geel@belgacom.be">jan.van.geel@belgacom.be</a>&gt;=
=20wrote:<o:p></o:p></p>

<div>

<div>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
style=3D'font-size:9.0pt;color:blue'>Hi,</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
style=3D'font-size:9.0pt;color:blue'>&nbsp;</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
style=3D'font-size:9.0pt;color:blue'>As=20service=20provider=20I=20comple=
tely=20agree=20with
the=20statement=20that=20a=20common=20approach=20is=20beneficial=20for=20=
the=20industry.=20Therefore
I=20would=20prefer=20that=20alignment=20with=20existing=20specifications=
=20of=203GPP/ETSI=20is
sought=20as=20much=20as=20possible.</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
style=3D'font-size:9.0pt;color:blue'>&nbsp;</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
style=3D'font-size:9.0pt;color:blue'>Kind=20regards</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
style=3D'font-size:9.0pt;color:blue'>&nbsp;</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
style=3D'font-size:9.0pt;color:blue'>&nbsp;</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><b><span
style=3D'color:blue'>Jan=20Van=20Geel</span></b><span=20style=3D'color:bl=
ue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;color:blue'>IT=20and=20Network=
=20Development
Specialist</span><span=20style=3D'color:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;color:blue'>Belgacom=20SDE/SDV/P=
SE/NST/NCP</span><span
style=3D'color:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;color:blue'>Tel:=20+32=202=20202=
=201035</span><span
style=3D'color:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;color:blue'>Tel:=20+32=202=20207=
=204442</span><span
style=3D'color:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;color:blue'>Tel:=20+32=202=20207=
=209032</span><span
style=3D'color:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;color:blue'>Email=20:=20<a
href=3D"mailto:jan.van.geel@belgacom.be"=20target=3D"_blank">jan.van.geel=
@belgacom.be</a></span><span
style=3D'color:blue'>=20<br>
</span><span=20style=3D'font-size:10.0pt;color:blue'><a
href=3D"http://www.cyberwezz.tk"=20target=3D"_blank">www.cyberwezz.tk</a>=
</span><span
style=3D'color:blue'>=20</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
style=3D'font-size:9.0pt;color:blue'>&nbsp;</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
style=3D'font-size:9.0pt;color:blue'>&nbsp;</span><o:p></o:p></p>

<div>

<div=20style=3D'border:none;border-top:solid=20windowtext=201.0pt;padding=
:3.0pt=200cm=200cm=200cm;
border-color:-moz-use-text-color=20-moz-use-text-color'>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><b><span
lang=3DEN-US=20style=3D'font-size:10.0pt'>From:</span></b><span=20lang=3D=
EN-US
style=3D'font-size:10.0pt'>=20<a=20href=3D"mailto:martini-bounces@ietf.or=
g"
target=3D"_blank">martini-bounces@ietf.org</a>=20[mailto:<a
href=3D"mailto:martini-bounces@ietf.org"=20target=3D"_blank">martini-boun=
ces@ietf.org</a>]
<b>On=20Behalf=20Of=20</b>Brian=20Lindsay<br>
<b>Sent:</b>=2017=20March=202010=2014:51<br>
<b>To:</b>=20Bernard=20Aboba;=20MARTINI<br>
<b>Subject:</b>=20Re:=20[martini]=20Call=20for=20Adoption=20of=20&quot;Re=
gistration=20for
Multiple=20PhoneNumbers=20in=20the=20SIP&quot;</span><o:p></o:p></p>

</div>

</div>

<div>

<div>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'>&nbsp;<o:p></o:p></p>

<div>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'font-size:10.0pt;color:blue'>Hi=20Bernard,</span>=
<o:p></o:p></p>

</div>

<div>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>&nbsp;</span><o:p></o:p></p>

</div>

<div>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'font-size:10.0pt;color:blue'>&nbsp;&nbsp;=20I=20t=
hink=20the=20gin
draft=20could=20form=20the=20basis=20of=20a=20solution,=20but=20at=20as=
=20couple=20of=20other=20folks=20have
noted=20there=20already=20is=20a=20solution=20standardized=20by=20TIPAN/3=
GPP=20which=20uses=20a
different=20approach=20for=20request=20routing=20for=20SIP=20PBXs.=20It=
=20would=20be=20ideal=20if=20we
had=20one=20common=20approach=20in=20the=20industry,=20otherwise=20we=20a=
re=20going=20to=20see=20some
carriers=20require=20one=20solution=20and=20other=20carriers=20the=20othe=
r=20solution=20and=20vendors
on=20both=20the=20enterprise=20and=20carrier=20side=20will=20need=20to&nb=
sp;implement=20and=20support
both.</span><o:p></o:p></p>

</div>

<div>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>&nbsp;</span><o:p></o:p></p>

</div>

<div>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'font-size:10.0pt;color:blue'>&nbsp;&nbsp;=20The=
=20shaken=20draft=20is
closer=20to=20the=20TISPAN/3GPP=20approach=20and=20is=20essentially=20add=
ing=20some=20incremental
improvements.=20I'd=20be=20more=20inclined=20to=20go=20with=20the=20shake=
n=20appoach=20at=20this=20time
given=20it's=20alignment=20with=20the=20existing=20standardized=20TISPAN/=
3GPP=20solution.</span><o:p></o:p></p>

</div>

<div>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>&nbsp;</span><o:p></o:p></p>

</div>

<div>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'font-size:10.0pt;color:blue'>&nbsp;&nbsp;=20I=20h=
aven't=20heard=20too
many=20other=20responses=20on=20the=20call=20for=20adoption&nbsp;from=20S=
SP=20vendors=20so=20I'm
curious=20on=20that=20front=20what=20others=20are=20thinking.</span><o:p>=
</o:p></p>

</div>

<div>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>&nbsp;</span><o:p></o:p></p>

</div>

<div>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'font-size:10.0pt;color:blue'>&nbsp;&nbsp;=20Thank=
s</span><o:p></o:p></p>

</div>

<div>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'font-size:10.0pt;color:blue'>&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;
Brian</span><o:p></o:p></p>

</div>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>&nbsp;</span><o:p></o:p></p>

<div=20class=3DMsoNormal=20align=3Dcenter=20style=3D'text-align:center'><=
span=20lang=3DEN-US>

<hr=20size=3D2=20width=3D"100%"=20align=3Dcenter>

</span></div>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;margin-bottom:1=
2.0pt'><b><span
lang=3DEN-US=20style=3D'font-size:10.0pt'>From:</span></b><span=20lang=3D=
EN-US
style=3D'font-size:10.0pt'>=20<a=20href=3D"mailto:martini-bounces@ietf.or=
g"
target=3D"_blank">martini-bounces@ietf.org</a>=20[mailto:<a
href=3D"mailto:martini-bounces@ietf.org"=20target=3D"_blank">martini-boun=
ces@ietf.org</a>]
<b>On=20Behalf=20Of=20</b>Bernard=20Aboba<br>
<b>Sent:</b>=20Thursday,=20March=2004,=202010=205:02=20PM<br>
<b>To:</b>=20'MARTINI'<br>
<b>Subject:</b>=20[martini]=20Call=20for=20Adoption=20of=20&quot;Registra=
tion=20for=20Multiple
PhoneNumbers=20in=20the=20SIP&quot;</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>This=20is=20a=20MARTINI=20WG=20Call=20for=20Adoption=20of=20=
&#8220;Registration=20for
Multiple=20Phone=20Numbers=20in=20the=20SIP&#8221;=20as=20a=20MARTINI=20W=
G=20work=20item,
corresponding=20to=20the=20&#8220;Multiple=20AoR=20Registration=20specifi=
cation&#8221;
Charter=20deliverable.=20&nbsp;The=20document=20is=20available=20for=20in=
spection=20here:=20</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US><a=20href=3D"http://tools.ietf.org/html/draft-roach-martini-=
gin-01.txt"
target=3D"_blank">http://tools.ietf.org/html/draft-roach-martini-gin-01.t=
xt</a></span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>The=20MARTINI=20WG=20Call=20for=20Adoption=20will=20last=20u=
ntil=20Friday,=20March=2019,
2010.</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>Please=20respond=20to=20this=20WG=20Call=20for=20Adoption,=
=20whether=20you=20are=20in
favor=20of=20adopting=20the=20document=20as=20a=20MARTINI=20WG=20work=20i=
tem=20or=20not.=20&nbsp;If=20you
have=20no=20comments,=20please=20reply=20to=20this=20message=20and=20indi=
cate=20in=20the=20body=20of=20your
message=20whether=20you=20think=20the=20document=20is=20ready=20for=20ado=
ption=20as=20a=20MARTINI=20WG
work=20item=20or=20not.=20&nbsp;&nbsp;Based=20on=20the=20response,=20the=
=20MARTINI=20WG=20chairs=20will
attempt=20to=20determine=20whether=20WG=20consensus=20exists=20to=20adopt=
=20the=20document=20or=20not.=20</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>If=20you=20have=20comments,=20please=20provide=20them=20to=
=20the=20WG=20in=20one=20of=20the
following=20ways:=20</span><o:p></o:p></p>

<p=20style=3D'margin-left:21.0pt'><span=20lang=3DEN-US=20style=3D'font-si=
ze:11.0pt;
color:black'>1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20The=20preferred=20choice=
=20is=20to=20open
an=20issue=20in=20the=20MARTINI=20Issue=20tracking=20database=20(TRAC),=
=20which=20is=20available
here:=20<a=20href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket=
"
target=3D"_blank"><span=20style=3D'color:black'>http://trac.tools.ietf.or=
g/wg/martini/trac/newticket</span></a>
&nbsp;Information=20on=20how=20to=20use=20TRAC=20is=20provided=20below.&n=
bsp;=20Note=20that=20if=20you
submit=20an=20issue=20in=20TRAC,=20it=20will=20automatically=20also=20be=
=20posted=20to=20the=20MARTINI=20WG
mailing=20list.=20&nbsp;When=20submitting=20issues=20in=20TRAC=20for=20th=
is=20&#8220;call=20for
adoption&#8221;,=20please=20enter=20&#8220;gin&#8221;=20for=20the=20Compo=
nent:=20and
&#8220;Candidate=20WG=20Document&#8221;=20for=20Severity.&nbsp;=20</span>=
<o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'color:black'>&nbsp;2.=20If=20you=20can&#8217;t=20=
figure=20out=20how=20to
use=20TRAC,=20please=20post=20your=20Issue=20to=20the=20MARTINI=20WG=20ma=
iling=20list=20(martini=20at=20<a
href=3D"http://ietf.org"=20target=3D"_blank">ietf.org</a>)=20in=20the=20f=
ollowing=20format:=20</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'font-family:"Courier=20New"'>To:&nbsp;=20martini=
=20at=20<a
href=3D"http://ietf.org"=20target=3D"_blank">ietf.org</a></span><o:p></o:=
p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'font-family:"Courier=20New"'>Subject:=20GIN-Issue=
:=20&lt;title=20of
your=20issue&gt;</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'font-family:"Courier=20New"'>Priority:=20blocker,=
=20critical,
major,=20minor=20or=20trivial</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'font-family:"Courier=20New"'>&lt;Explanation=20of=
=20your=20issue,
including=20a=20proposal=20for=20specific=20text=20changes=20to=20resolve=
=20the=20issue&gt;</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US=20style=3D'color:black'>The=20MARTINI=20WG=20uses=20the=20TR=
AC=20database=20to=20keep
track=20of=20issues=20relating=20to=20work=20in=20progress,=20including=
=20working=20group=20work
items=20and=20individual=20submissions=20undergoing=20review.=20&nbsp;&nb=
sp;&nbsp;This
document=20provides=20some=20basic=20information=20on=20how=20MARTINI=20W=
G=20participants=20can=20use
TRAC=20to=20submit=20or=20edit=20issues.&nbsp;=20</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>Documentation=20relating=20to=20the=20TRAC=20Issue=20Trackin=
g=20database=20is
available=20here:</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US><a=20href=3D"http://trac.tools.ietf.org/wg/martini/trac/wiki=
"
target=3D"_blank">http://trac.tools.ietf.org/wg/martini/trac/wiki</a></sp=
an><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>Since=20this=20documentation=20is=20somewhat=20lengthy=20(an=
d=20mostly=20relevant=20to
Admins),=20here=20is=20a=20pithy=20synopsis.=20</span><o:p></o:p></p>

<p><span=20lang=3DEN-US=20style=3D'font-size:11.0pt'>1.&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
To=20submit=20an=20issue=20in=20the=20MARTINI=20Issues=20database=20(know=
n=20as=20TRAC),=20you=20first
need=20to=20login=20to=20the=20MARTINI=20WG=20site=20on=20the=20tools=20s=
erver=20(<a
href=3D"http://tools.ietf.org/wg/martini/trac/login"=20target=3D"_blank">=
http://tools.ietf.org/wg/martini/trac/login</a>
)=20</span><o:p></o:p></p>

<p><span=20lang=3DEN-US=20style=3D'font-size:11.0pt'>2.&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
If=20you=20don&#8217;t=20already=20have=20a=20login=20ID,=20you=20can=20o=
btain=20one=20by=20navigating=20to
this=20site:=20&nbsp;&nbsp;<a=20href=3D"http://trac.tools.ietf.org/newlog=
in"
target=3D"_blank">http://trac.tools.ietf.org/newlogin</a></span><o:p></o:=
p></p>

<p><span=20lang=3DEN-US=20style=3D'font-size:11.0pt'>3<span=20style=3D'co=
lor:black'>.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Once=20you=20have=20obtained=20an=20account,=20you=20can=20log=20in=20by=
=20clicking=20on=20the
&#8220;login&#8221;=20entry=20at=20the=20top=20of=20the=20page.&nbsp;=20O=
nce=20you=20have=20logged
in,=20you=20can=20file=20an=20issue=20by=20navigating=20to=20the=20&nbsp;=
ticket=20entry=20form:=20<a
href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket"=20target=3D=
"_blank"><span
style=3D'color:black'>http://trac.tools.ietf.org/wg/martini/trac/newticke=
t</span></a></span></span><o:p></o:p></p>

<p><span=20lang=3DEN-US=20style=3D'font-size:11.0pt'>4<span=20style=3D'co=
lor:#1F497D'>&nbsp;&nbsp;&nbsp;
</span>&nbsp;When=20opening=20an=20issue:&nbsp;</span><o:p></o:p></p>

<p><span=20lang=3DEN-US=20style=3D'font-size:11.0pt'>a.&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
The=20Type:=20field=20should=20be=20set=20to=20&#8220;defect&#8221;=20for=
=20an=20issue=20with=20the
current=20document=20text,=20or=20&#8220;enhancement&#8221;=20for=20a=20p=
roposed=20addition=20of
functionality=20(such=20as=20an=20additional=20requirement).=20</span><o:=
p></o:p></p>

<p><span=20lang=3DEN-US=20style=3D'font-size:11.0pt'>b.&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
The=20Priority:=20field=20is=20set=20based=20on=20the=20severity=20of=20t=
he=20Issue.&nbsp;&nbsp;=20For
example,=20editorial=20issues=20are=20typically=20&#8220;minor&#8221;=20o=
r
&#8220;trivial&#8221;.=20</span><o:p></o:p></p>

<p><span=20lang=3DEN-US=20style=3D'font-size:11.0pt'>c<span=20style=3D'co=
lor:black'>.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The=20Milestone:=20field=20should=20be=20set=20to=20milestone1=20(useless=
,=20I=20know).=20</span></span><o:p></o:p></p>

<p><span=20lang=3DEN-US=20style=3D'font-size:11.0pt;color:black'>d.&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;
The=20Component:=20field=20should=20be=20set=20to=20the=20document=20you=
=20are=20filing=20the=20issue
on.&nbsp;=20In=20responding=20to=20the=20GIN=20Call=20for=20Adoption,=20&=
#8220;gin&#8221;=20is=20the
appropriate=20choice.</span><o:p></o:p></p>

<p><span=20lang=3DEN-US=20style=3D'font-size:11.0pt;color:black'>e.&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;
The=20Version:=20field=20should=20be=20set=20to=20&#8220;1.0&#8221;.=20</=
span><o:p></o:p></p>

<p><span=20lang=3DEN-US=20style=3D'font-size:11.0pt;color:black'>f.&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The=20Severity:=20field=20should=20be=20set=20to=20based=20on=20the=20sta=
tus=20of=20the=20document=20(e.g.
&#8220;Candidate=20WG=20Document&#8221;=20in=20this=20case)</span><o:p></=
o:p></p>

<p><span=20lang=3DEN-US=20style=3D'font-size:11.0pt;color:black'>g.&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;The=20Keywords:=20and=20CC:=20fields=20can=20be=20left=20blank=20un=
less=20inspiration=20seizes
you.=20</span><o:p></o:p></p>

<p><span=20lang=3DEN-US=20style=3D'font-size:11.0pt;color:black'>h.&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;
The=20Assign=20To:=20field=20is=20generally=20filled=20in=20with=20the=20=
email=20address=20of=20the=20editor.
</span><o:p></o:p></p>

<p><span=20lang=3DEN-US=20style=3D'font-size:11.0pt'>5.&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
Typically=20it=20won&#8217;t=20be=20necessary=20to=20enclose=20a=20file=
=20with=20the=20ticket,=20but=20if
you=20need=20to,=20select=20&#8220;I=20have=20files=20to=20attach=20to=20=
this=20ticket&#8221;.=20</span><o:p></o:p></p>

<p><span=20lang=3DEN-US=20style=3D'font-size:11.0pt'>6.&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
If=20you=20want=20to=20preview=20your=20Issue,=20click=20on=20the=20&#822=
0;Preview&#8221;
button.&nbsp;=20When=20you&#8217;re=20ready=20to=20submit=20the=20issue,=
=20click=20on=20the
&#8220;Create=20Ticket&#8221;=20button.=20</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>That&#8217;s=20it!&nbsp;=20</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>If=20you=20have=20an=20problems=20in=20dealing=20with=20TRAC=
,=20send=20email=20to=20me=20and
I&#8217;ll=20try=20to=20figure=20out=20what&#8217;s=20going=20on.=20</spa=
n><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>Happy=20TRACing,</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>Bernard</span><o:p></o:p></p>

<p=20class=3DMsoNormal=20style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span
lang=3DEN-US>&nbsp;</span><o:p></o:p></p>

</div>

</div>

</div>

</div>

<table=20class=3DMsoNormalTable=20border=3D0=20cellpadding=3D0>
=20<tr>
=20=20<td=20style=3D'background:white;padding:.75pt=20.75pt=20.75pt=20.75=
pt'><pre><span
=20=20style=3D'color:black'>****=20DISCLAIMER=20****<o:p></o:p></span></p=
re><pre><span
=20=20style=3D'color:black'><a=20href=3D"http://www.belgacom.be/maildiscl=
aimer"
=20=20target=3D"_blank">http://www.belgacom.be/maildisclaimer</a><o:p></o=
:p></span></pre></td>
=20</tr>
</table>

<p=20class=3DMsoNormal=20style=3D'margin-bottom:12.0pt'><br>
_______________________________________________<br>
martini=20mailing=20list<br>
<a=20href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a=20href=3D"https://www.ietf.org/mailman/listinfo/martini"=20target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/martini</a><o:p></o:p></p>

</div>

<p=20class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

<table><tr><td=20bgcolor=3D#ffffff><font=20color=3D#000000><pre>****=20DI=
SCLAIMER=20****
http://www.belgacom.be/maildisclaimer</pre></font></td></tr></table>

--_000_208EAE1DFA28FC419529619ABB8622441617535005CMS03BGCNET_--

From ietf.hanserik@gmail.com  Fri Mar 19 01:39:41 2010
Return-Path: <ietf.hanserik@gmail.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 92FC03A685E for <martini@core3.amsl.com>; Fri, 19 Mar 2010 01:39:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.733
X-Spam-Level: 
X-Spam-Status: No, score=-0.733 tagged_above=-999 required=5 tests=[AWL=-1.865, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 9WavbXIgzsDg for <martini@core3.amsl.com>; Fri, 19 Mar 2010 01:39:39 -0700 (PDT)
Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216]) by core3.amsl.com (Postfix) with ESMTP id B363A3A685D for <martini@ietf.org>; Fri, 19 Mar 2010 01:39:38 -0700 (PDT)
Received: by ewy8 with SMTP id 8so1603525ewy.28 for <martini@ietf.org>; Fri, 19 Mar 2010 01:39:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=aDBfob/GIBF7lHtVuZpLHDyCNw9jmq1W8kIeC8tqUwg=; b=ToHgZZ9e9MrNPTKm+E9AEclc801VgOoUbjXTN/Hp3lHcHKZSeH6YO74iEWY9+ccoMw eOSHd1jHlu5EnINAnKEraZrZG2vn3dv9Q5lvAaXVJFmPEWWEmx1G39TjFL3GZOIYDQdD UwMcmppTjYPwQvv1l+dBQxkTXuDFIe8HJuPsY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=uTKIIa1qjZlSluA+boucyRqpiJnsWBJI/dqolftja0ANOV5v22X0IJ0Uocik22nAJm 2OBz4pGx95qgivCD2u87c55rLk6KNyO8HQQBOwcSH0LpUM6pMPK6OwtfGV6u8d1MmhwT zgnTn7vA4RcQJ1Xkl6wQrEWjNjW8xnA0nv25E=
MIME-Version: 1.0
Received: by 10.213.34.79 with HTTP; Fri, 19 Mar 2010 01:39:46 -0700 (PDT)
In-Reply-To: <208EAE1DFA28FC419529619ABB8622441617535005@CMS03.BGC.NET>
References: <BLU137-DS10BC28829B50482DC93D0A93390@phx.gbl> <09B7DBFE70A9E24BBB21689DAD3A06141CF400B7@zcarhxm1.corp.nortel.com> <208EAE1DFA28FC419529619ABB8622441616E6C19B@CMS03.BGC.NET> <9ae56b1e1003181042u3e21d1bax79124b1584e8e40d@mail.gmail.com> <208EAE1DFA28FC419529619ABB8622441617535005@CMS03.BGC.NET>
Date: Fri, 19 Mar 2010 09:39:46 +0100
Received: by 10.213.43.67 with SMTP id v3mr241442ebe.0.1268987986117; Fri, 19  Mar 2010 01:39:46 -0700 (PDT)
Message-ID: <9ae56b1e1003190139i75897d9dq93079efc0ca754e0@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: jan.van.geel@belgacom.be
Content-Type: multipart/alternative; boundary=00148530a3462304200482234a85
Cc: bernard_aboba@hotmail.com, martini@ietf.org
Subject: Re: [martini] Call for Adoption of "Registration for Multiple PhoneNumbers in the SIP"
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: Fri, 19 Mar 2010 08:39:41 -0000

--00148530a3462304200482234a85
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Yes these scenarios are based on implicit registration.

BR,
/Hans Erik van Elburg


On Fri, Mar 19, 2010 at 8:35 AM, <jan.van.geel@belgacom.be> wrote:

>  Hans Erik, all,
>
>
>
> Maybe I misunderstand (some of) the use cases, but to me UC3 looks like a
> PBX using a group REGISTER, as described in 3GPP/ETSI documents. The
> Conclusion of this discussion document seems to indicate that this is the
> solution with the lesser drawbacks, right ?
>
>
>
> Kind regards
>
>
>
>
>
> *Jan Van Geel*
> IT and Network Development Specialist
> Belgacom SDE/SDV/PSE/NST/NCP
> Tel: +32 2 202 1035
> Tel: +32 2 207 4442
> Tel: +32 2 207 9032
> Email : jan.van.geel@belgacom.be
> www.cyberwezz.tk
>
>
>
>
>
> *From:* Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
> *Sent:* 18 March 2010 18:42
> *To:* VAN GEEL Jan (ITN/NIS)
> *Cc:* blindsay@nortel.com; bernard_aboba@hotmail.com; martini@ietf.org
>
> *Subject:* Re: [martini] Call for Adoption of "Registration for Multiple
> PhoneNumbers in the SIP"
>
>
>
> +1
>
> Allowing both UC-3 and UC-6/9 scenarios could be a way forward, use cases
> or scenarios as depicted in:
>
> http://aboba.drizzlehosting.com/MARTINI/Jan-Interim-III/IETF77_MARTINI_Fe=
b9Interim_Use_models.pdf
>
> PBX configurations that are fine with the limitations or limited themselv=
es
> can register and indicate they are expecting UC-3 style.
> PBX configurations that need more advanced setups can register and indica=
te
> they are expecting UC-6/9 style.
>
> BR,
> /Hans Erik van Elburg
>
> On Thu, Mar 18, 2010 at 9:06 AM, <jan.van.geel@belgacom.be> wrote:
>
> Hi,
>
>
>
> As service provider I completely agree with the statement that a common
> approach is beneficial for the industry. Therefore I would prefer that
> alignment with existing specifications of 3GPP/ETSI is sought as much as
> possible.
>
>
>
> Kind regards
>
>
>
>
>
> *Jan Van Geel*
> IT and Network Development Specialist
> Belgacom SDE/SDV/PSE/NST/NCP
> Tel: +32 2 202 1035
> Tel: +32 2 207 4442
> Tel: +32 2 207 9032
> Email : jan.van.geel@belgacom.be
> www.cyberwezz.tk
>
>
>
>
>
> *From:* martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] *On
> Behalf Of *Brian Lindsay
> *Sent:* 17 March 2010 14:51
> *To:* Bernard Aboba; MARTINI
> *Subject:* Re: [martini] Call for Adoption of "Registration for Multiple
> PhoneNumbers in the SIP"
>
>
>
> Hi Bernard,
>
>
>
>    I think the gin draft could form the basis of a solution, but at as
> couple of other folks have noted there already is a solution standardized=
 by
> TIPAN/3GPP which uses a different approach for request routing for SIP PB=
Xs.
> It would be ideal if we had one common approach in the industry, otherwis=
e
> we are going to see some carriers require one solution and other carriers
> the other solution and vendors on both the enterprise and carrier side wi=
ll
> need to implement and support both.
>
>
>
>    The shaken draft is closer to the TISPAN/3GPP approach and is
> essentially adding some incremental improvements. I'd be more inclined to=
 go
> with the shaken appoach at this time given it's alignment with the existi=
ng
> standardized TISPAN/3GPP solution.
>
>
>
>    I haven't heard too many other responses on the call for adoption from
> SSP vendors so I'm curious on that front what others are thinking.
>
>
>
>    Thanks
>
>        Brian
>
>
>  ------------------------------
>
> *From:* martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] *On
> Behalf Of *Bernard Aboba
> *Sent:* Thursday, March 04, 2010 5:02 PM
> *To:* 'MARTINI'
> *Subject:* [martini] Call for Adoption of "Registration for Multiple
> PhoneNumbers in the SIP"
>
> This is a MARTINI WG Call for Adoption of =93Registration for Multiple Ph=
one
> Numbers in the SIP=94 as a MARTINI WG work item, corresponding to the
> =93Multiple AoR Registration specification=94 Charter deliverable.  The d=
ocument
> is available for inspection here:
>
> http://tools.ietf.org/html/draft-roach-martini-gin-01.txt
>
> The MARTINI WG Call for Adoption will last until Friday, March 19, 2010.
>
> Please respond to this WG Call for Adoption, whether you are in favor of
> adopting the document as a MARTINI WG work item or not.  If you have no
> comments, please reply to this message and indicate in the body of your
> message whether you think the document is ready for adoption as a MARTINI=
 WG
> work item or not.   Based on the response, the MARTINI WG chairs will
> attempt to determine whether WG consensus exists to adopt the document or
> not.
>
> If you have comments, please provide them to the WG in one of the followi=
ng
> ways:
>
> 1.      The preferred choice is to open an issue in the MARTINI Issue
> tracking database (TRAC), which is available here:
> http://trac.tools.ietf.org/wg/martini/trac/newticket  Information on how
> to use TRAC is provided below.  Note that if you submit an issue in TRAC,=
 it
> will automatically also be posted to the MARTINI WG mailing list.  When
> submitting issues in TRAC for this =93call for adoption=94, please enter =
=93gin=94
> for the Component: and =93Candidate WG Document=94 for Severity.
>
>  2. If you can=92t figure out how to use TRAC, please post your Issue to =
the
> MARTINI WG mailing list (martini at ietf.org) in the following format:
>
> To:  martini at ietf.org
>
> Subject: GIN-Issue: <title of your issue>
>
> Priority: blocker, critical, major, minor or trivial
>
> <Explanation of your issue, including a proposal for specific text change=
s
> to resolve the issue>
>
> The MARTINI WG uses the TRAC database to keep track of issues relating to
> work in progress, including working group work items and individual
> submissions undergoing review.    This document provides some basic
> information on how MARTINI WG participants can use TRAC to submit or edit
> issues.
>
> Documentation relating to the TRAC Issue Tracking database is available
> here:
>
> http://trac.tools.ietf.org/wg/martini/trac/wiki
>
> Since this documentation is somewhat lengthy (and mostly relevant to
> Admins), here is a pithy synopsis.
>
> 1.       To submit an issue in the MARTINI Issues database (known as TRAC=
),
> you first need to login to the MARTINI WG site on the tools server (
> http://tools.ietf.org/wg/martini/trac/login )
>
> 2.       If you don=92t already have a login ID, you can obtain one by
> navigating to this site:   http://trac.tools.ietf.org/newlogin
>
> 3.       Once you have obtained an account, you can log in by clicking on
> the =93login=94 entry at the top of the page.  Once you have logged in, y=
ou can
> file an issue by navigating to the  ticket entry form:
> http://trac.tools.ietf.org/wg/martini/trac/newticket
>
> 4     When opening an issue:
>
> a.       The Type: field should be set to =93defect=94 for an issue with =
the
> current document text, or =93enhancement=94 for a proposed addition of
> functionality (such as an additional requirement).
>
> b.      The Priority: field is set based on the severity of the Issue.
> For example, editorial issues are typically =93minor=94 or =93trivial=94.
>
> c.       The Milestone: field should be set to milestone1 (useless, I
> know).
>
> d.      The Component: field should be set to the document you are filing
> the issue on.  In responding to the GIN Call for Adoption, =93gin=94 is t=
he
> appropriate choice.
>
> e.      The Version: field should be set to =931.0=94.
>
> f.        The Severity: field should be set to based on the status of the
> document (e.g. =93Candidate WG Document=94 in this case)
>
> g.        The Keywords: and CC: fields can be left blank unless inspirati=
on
> seizes you.
>
> h.      The Assign To: field is generally filled in with the email addres=
s
> of the editor.
>
> 5.       Typically it won=92t be necessary to enclose a file with the tic=
ket,
> but if you need to, select =93I have files to attach to this ticket=94.
>
> 6.       If you want to preview your Issue, click on the =93Preview=94 bu=
tton.
> When you=92re ready to submit the issue, click on the =93Create Ticket=94=
 button.
>
> That=92s it!
>
> If you have an problems in dealing with TRAC, send email to me and I=92ll=
 try
> to figure out what=92s going on.
>
> Happy TRACing,
>
> Bernard
>
>
>
> **** DISCLAIMER ****
>
> http://www.belgacom.be/maildisclaimer
>
>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>
>
>
> **** DISCLAIMER ****http://www.belgacom.be/maildisclaimer
>
>

--00148530a3462304200482234a85
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Yes these scenarios are based on implicit registration.<br><br>BR,<br>/Hans=
 Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Fri, Mar 19, 2010 at 8:35 AM,  <span =
dir=3D"ltr">&lt;<a href=3D"mailto:jan.van.geel@belgacom.be">jan.van.geel@be=
lgacom.be</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); p=
adding-left: 1ex;">










<div link=3D"blue" vlink=3D"purple" lang=3D"EN-GB">

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">Hans Er=
ik, all,</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">Maybe I=
 misunderstand (some of) the use cases, but to me UC3 looks
like a PBX using a group REGISTER, as described in 3GPP/ETSI documents. The
Conclusion of this discussion document seems to indicate that this is the
solution with the lesser drawbacks, right ?</span></p><div class=3D"im">

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">Kind re=
gards</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><b><span style=3D"color: blue;">Jan
Van Geel</span></b><span style=3D"color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">IT and Network Develop=
ment Specialist</span><span style=3D"color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Belgacom SDE/SDV/PSE/N=
ST/NCP</span><span style=3D"color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Tel: +32 2 202 1035</s=
pan><span style=3D"color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Tel: +32 2 207 4442</s=
pan><span style=3D"color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Tel: +32 2 207 9032</s=
pan><span style=3D"color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Email : <a href=3D"mai=
lto:jan.van.geel@belgacom.be" target=3D"_blank">jan.van.geel@belgacom.be</a=
></span><span style=3D"color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;"><a href=3D"http://www.=
cyberwezz.tk" target=3D"_blank">www.cyberwezz.tk</a></span><span style=3D"c=
olor: blue;"> </span><span style=3D"font-size: 9pt; color: blue;"></span></=
p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

</div><div style=3D"border-width: 1pt medium medium; border-style: solid no=
ne none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text=
-color; padding: 3pt 0cm 0cm;">

<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt;" lang=3D"EN-US">F=
rom:</span></b><span style=3D"font-size: 10pt;" lang=3D"EN-US"> Hans Erik v=
an Elburg
[mailto:<a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">ietf.h=
anserik@gmail.com</a>] <br>
<b>Sent:</b> 18 March 2010 18:42<br>
<b>To:</b> VAN GEEL Jan (ITN/NIS)<br>
<b>Cc:</b> <a href=3D"mailto:blindsay@nortel.com" target=3D"_blank">blindsa=
y@nortel.com</a>; <a href=3D"mailto:bernard_aboba@hotmail.com" target=3D"_b=
lank">bernard_aboba@hotmail.com</a>; <a href=3D"mailto:martini@ietf.org" ta=
rget=3D"_blank">martini@ietf.org</a><div>
<div></div><div class=3D"h5"><br>
<b>Subject:</b> Re: [martini] Call for Adoption of &quot;Registration for
Multiple PhoneNumbers in the SIP&quot;</div></div></span></p>

</div><div><div></div><div class=3D"h5">

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;">+1<br>
<br>
Allowing both UC-3 and UC-6/9 scenarios could be a way forward, use cases o=
r
scenarios as depicted in:<br>
<a href=3D"http://aboba.drizzlehosting.com/MARTINI/Jan-Interim-III/IETF77_M=
ARTINI_Feb9Interim_Use_models.pdf" target=3D"_blank">http://aboba.drizzleho=
sting.com/MARTINI/Jan-Interim-III/IETF77_MARTINI_Feb9Interim_Use_models.pdf=
</a><br>

<br>
PBX configurations that are fine with the limitations or limited themselves=
 can
register and indicate they are expecting UC-3 style.<br>
PBX configurations that need more advanced setups can register and indicate
they are expecting UC-6/9 style.<br>
<br>
BR,<br clear=3D"all">
/Hans Erik van Elburg</p>

<div>

<p class=3D"MsoNormal">On Thu, Mar 18, 2010 at 9:06 AM, &lt;<a href=3D"mail=
to:jan.van.geel@belgacom.be" target=3D"_blank">jan.van.geel@belgacom.be</a>=
&gt; wrote:</p>

<div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">Hi,</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">As serv=
ice provider I completely agree with
the statement that a common approach is beneficial for the industry. Theref=
ore
I would prefer that alignment with existing specifications of 3GPP/ETSI is
sought as much as possible.</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">Kind re=
gards</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><b><span style=3D"color: blue;">Jan Van Geel</span><=
/b><span style=3D"color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">IT and Network Develop=
ment
Specialist</span><span style=3D"color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Belgacom SDE/SDV/PSE/N=
ST/NCP</span><span style=3D"color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Tel: +32 2 202 1035</s=
pan><span style=3D"color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Tel: +32 2 207 4442</s=
pan><span style=3D"color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Tel: +32 2 207 9032</s=
pan><span style=3D"color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;">Email : <a href=3D"mai=
lto:jan.van.geel@belgacom.be" target=3D"_blank">jan.van.geel@belgacom.be</a=
></span><span style=3D"color: blue;"> <br>
</span><span style=3D"font-size: 10pt; color: blue;"><a href=3D"http://www.=
cyberwezz.tk" target=3D"_blank">www.cyberwezz.tk</a></span><span style=3D"c=
olor: blue;"> </span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 9pt; color: blue;">=A0</sp=
an></p>

<div>

<div style=3D"border-width: 1pt medium medium; border-style: solid none non=
e; padding: 3pt 0cm 0cm; border-color: -moz-use-text-color;">

<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt;" lang=3D"EN-US">F=
rom:</span></b><span style=3D"font-size: 10pt;" lang=3D"EN-US"> <a href=3D"=
mailto:martini-bounces@ietf.org" target=3D"_blank">martini-bounces@ietf.org=
</a> [mailto:<a href=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">=
martini-bounces@ietf.org</a>]
<b>On Behalf Of </b>Brian Lindsay<br>
<b>Sent:</b> 17 March 2010 14:51<br>
<b>To:</b> Bernard Aboba; MARTINI<br>
<b>Subject:</b> Re: [martini] Call for Adoption of &quot;Registration for
Multiple PhoneNumbers in the SIP&quot;</span></p>

</div>

</div>

<div>

<div>

<p class=3D"MsoNormal">=A0</p>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;" lang=
=3D"EN-US">Hi Bernard,</span></p>

</div>

<div>

<p class=3D"MsoNormal"><span lang=3D"EN-US">=A0</span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;" lang=
=3D"EN-US">=A0=A0 I think the gin
draft could form the basis of a solution, but at as couple of other folks h=
ave
noted there already is a solution standardized by TIPAN/3GPP which uses a
different approach for request routing for SIP PBXs. It would be ideal if w=
e
had one common approach in the industry, otherwise we are going to see some
carriers require one solution and other carriers the other solution and ven=
dors
on both the enterprise and carrier side will need to=A0implement and suppor=
t
both.</span></p>

</div>

<div>

<p class=3D"MsoNormal"><span lang=3D"EN-US">=A0</span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;" lang=
=3D"EN-US">=A0=A0 The shaken draft is
closer to the TISPAN/3GPP approach and is essentially adding some increment=
al
improvements. I&#39;d be more inclined to go with the shaken appoach at thi=
s time
given it&#39;s alignment with the existing standardized TISPAN/3GPP solutio=
n.</span></p>

</div>

<div>

<p class=3D"MsoNormal"><span lang=3D"EN-US">=A0</span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;" lang=
=3D"EN-US">=A0=A0 I haven&#39;t heard too
many other responses on the call for adoption=A0from SSP vendors so I&#39;m
curious on that front what others are thinking.</span></p>

</div>

<div>

<p class=3D"MsoNormal"><span lang=3D"EN-US">=A0</span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;" lang=
=3D"EN-US">=A0=A0 Thanks</span></p>

</div>

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;" lang=
=3D"EN-US">=A0=A0=A0=A0=A0=A0
Brian</span></p>

</div>

<p class=3D"MsoNormal"><span lang=3D"EN-US">=A0</span></p>

<div class=3D"MsoNormal" style=3D"text-align: center;" align=3D"center"><sp=
an lang=3D"EN-US">

<hr width=3D"100%" align=3D"center" size=3D"2">

</span></div>

<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;"><b><span style=3D"fon=
t-size: 10pt;" lang=3D"EN-US">From:</span></b><span style=3D"font-size: 10p=
t;" lang=3D"EN-US"> <a href=3D"mailto:martini-bounces@ietf.org" target=3D"_=
blank">martini-bounces@ietf.org</a> [mailto:<a href=3D"mailto:martini-bounc=
es@ietf.org" target=3D"_blank">martini-bounces@ietf.org</a>]
<b>On Behalf Of </b>Bernard Aboba<br>
<b>Sent:</b> Thursday, March 04, 2010 5:02 PM<br>
<b>To:</b> &#39;MARTINI&#39;<br>
<b>Subject:</b> [martini] Call for Adoption of &quot;Registration for Multi=
ple
PhoneNumbers in the SIP&quot;</span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">This is a MARTINI WG Call for A=
doption of =93Registration for
Multiple Phone Numbers in the SIP=94 as a MARTINI WG work item,
corresponding to the =93Multiple AoR Registration specification=94
Charter deliverable. =A0The document is available for inspection here: </sp=
an></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US"><a href=3D"http://tools.ietf.or=
g/html/draft-roach-martini-gin-01.txt" target=3D"_blank">http://tools.ietf.=
org/html/draft-roach-martini-gin-01.txt</a></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">The MARTINI WG Call for Adoptio=
n will last until Friday, March 19,
2010.</span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">Please respond to this WG Call =
for Adoption, whether you are in
favor of adopting the document as a MARTINI WG work item or not. =A0If you
have no comments, please reply to this message and indicate in the body of =
your
message whether you think the document is ready for adoption as a MARTINI W=
G
work item or not. =A0=A0Based on the response, the MARTINI WG chairs will
attempt to determine whether WG consensus exists to adopt the document or n=
ot. </span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">If you have comments, please pr=
ovide them to the WG in one of the
following ways: </span></p>

<p style=3D"margin-left: 21pt;"><span style=3D"font-size: 11pt; color: blac=
k;" lang=3D"EN-US">1.=A0=A0=A0=A0=A0 The preferred choice is to open
an issue in the MARTINI Issue tracking database (TRAC), which is available
here: <a href=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket" targ=
et=3D"_blank"><span style=3D"color: black;">http://trac.tools.ietf.org/wg/m=
artini/trac/newticket</span></a>
=A0Information on how to use TRAC is provided below.=A0 Note that if you
submit an issue in TRAC, it will automatically also be posted to the MARTIN=
I WG
mailing list. =A0When submitting issues in TRAC for this =93call for
adoption=94, please enter =93gin=94 for the Component: and
=93Candidate WG Document=94 for Severity.=A0 </span></p>

<p class=3D"MsoNormal"><span style=3D"color: black;" lang=3D"EN-US">=A02. I=
f you can=92t figure out how to
use TRAC, please post your Issue to the MARTINI WG mailing list (martini at=
 <a href=3D"http://ietf.org" target=3D"_blank">ietf.org</a>) in the followi=
ng format: </span></p>

<p class=3D"MsoNormal"><span style=3D"font-family: &quot;Courier New&quot;;=
" lang=3D"EN-US">To:=A0 martini at <a href=3D"http://ietf.org" target=3D"_b=
lank">ietf.org</a></span></p>

<p class=3D"MsoNormal"><span style=3D"font-family: &quot;Courier New&quot;;=
" lang=3D"EN-US">Subject: GIN-Issue: &lt;title of
your issue&gt;</span></p>

<p class=3D"MsoNormal"><span style=3D"font-family: &quot;Courier New&quot;;=
" lang=3D"EN-US">Priority: blocker, critical,
major, minor or trivial</span></p>

<p class=3D"MsoNormal"><span style=3D"font-family: &quot;Courier New&quot;;=
" lang=3D"EN-US">&lt;Explanation of your issue,
including a proposal for specific text changes to resolve the issue&gt;</sp=
an></p>

<p class=3D"MsoNormal"><span style=3D"color: black;" lang=3D"EN-US">The MAR=
TINI WG uses the TRAC database to keep
track of issues relating to work in progress, including working group work
items and individual submissions undergoing review. =A0=A0=A0This
document provides some basic information on how MARTINI WG participants can=
 use
TRAC to submit or edit issues.=A0 </span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">Documentation relating to the T=
RAC Issue Tracking database is
available here:</span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US"><a href=3D"http://trac.tools.ie=
tf.org/wg/martini/trac/wiki" target=3D"_blank">http://trac.tools.ietf.org/w=
g/martini/trac/wiki</a></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">Since this documentation is som=
ewhat lengthy (and mostly relevant to
Admins), here is a pithy synopsis. </span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">1.=A0=A0=A0=A0=A0=A0
To submit an issue in the MARTINI Issues database (known as TRAC), you firs=
t
need to login to the MARTINI WG site on the tools server (<a href=3D"http:/=
/tools.ietf.org/wg/martini/trac/login" target=3D"_blank">http://tools.ietf.=
org/wg/martini/trac/login</a>
) </span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">2.=A0=A0=A0=A0=A0=A0
If you don=92t already have a login ID, you can obtain one by navigating to
this site: =A0=A0<a href=3D"http://trac.tools.ietf.org/newlogin" target=3D"=
_blank">http://trac.tools.ietf.org/newlogin</a></span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">3<span style=3D"color: b=
lack;">.=A0=A0=A0=A0=A0=A0
Once you have obtained an account, you can log in by clicking on the
=93login=94 entry at the top of the page.=A0 Once you have logged
in, you can file an issue by navigating to the =A0ticket entry form: <a hre=
f=3D"http://trac.tools.ietf.org/wg/martini/trac/newticket" target=3D"_blank=
"><span style=3D"color: black;">http://trac.tools.ietf.org/wg/martini/trac/=
newticket</span></a></span></span></p>


<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">4<span style=3D"color: r=
gb(31, 73, 125);">=A0=A0=A0
</span>=A0When opening an issue:=A0</span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">a.=A0=A0=A0=A0=A0=A0
The Type: field should be set to =93defect=94 for an issue with the
current document text, or =93enhancement=94 for a proposed addition of
functionality (such as an additional requirement). </span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">b.=A0=A0=A0=A0=A0
The Priority: field is set based on the severity of the Issue.=A0=A0 For
example, editorial issues are typically =93minor=94 or
=93trivial=94. </span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">c<span style=3D"color: b=
lack;">.=A0=A0=A0=A0=A0=A0
The Milestone: field should be set to milestone1 (useless, I know). </span>=
</span></p>

<p><span style=3D"font-size: 11pt; color: black;" lang=3D"EN-US">d.=A0=A0=
=A0=A0=A0
The Component: field should be set to the document you are filing the issue
on.=A0 In responding to the GIN Call for Adoption, =93gin=94 is the
appropriate choice.</span></p>

<p><span style=3D"font-size: 11pt; color: black;" lang=3D"EN-US">e.=A0=A0=
=A0=A0=A0
The Version: field should be set to =931.0=94. </span></p>

<p><span style=3D"font-size: 11pt; color: black;" lang=3D"EN-US">f.=A0=A0=
=A0=A0=A0=A0=A0
The Severity: field should be set to based on the status of the document (e=
.g.
=93Candidate WG Document=94 in this case)</span></p>

<p><span style=3D"font-size: 11pt; color: black;" lang=3D"EN-US">g.=A0=A0=
=A0=A0=A0=A0
=A0The Keywords: and CC: fields can be left blank unless inspiration seizes
you. </span></p>

<p><span style=3D"font-size: 11pt; color: black;" lang=3D"EN-US">h.=A0=A0=
=A0=A0=A0
The Assign To: field is generally filled in with the email address of the e=
ditor.
</span></p>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">5.=A0=A0=A0=A0=A0=A0
Typically it won=92t be necessary to enclose a file with the ticket, but if
you need to, select =93I have files to attach to this ticket=94. </span></p=
>

<p><span style=3D"font-size: 11pt;" lang=3D"EN-US">6.=A0=A0=A0=A0=A0=A0
If you want to preview your Issue, click on the =93Preview=94
button.=A0 When you=92re ready to submit the issue, click on the
=93Create Ticket=94 button. </span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">That=92s it!=A0 </span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">If you have an problems in deal=
ing with TRAC, send email to me and
I=92ll try to figure out what=92s going on. </span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">Happy TRACing,</span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">Bernard</span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">=A0</span></p>

</div>

</div>

</div>

</div>

<table border=3D"0" cellpadding=3D"0">
 <tbody><tr>
  <td style=3D"background: none repeat scroll 0% 0% white; padding: 0.75pt;=
"><pre><span style=3D"color: black;">**** DISCLAIMER ****</span></pre><pre>=
<span style=3D"color: black;"><a href=3D"http://www.belgacom.be/maildisclai=
mer" target=3D"_blank">http://www.belgacom.be/maildisclaimer</a></span></pr=
e>
</td>
 </tr>
</tbody></table>

<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;"><br>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a></p>

</div>

<p class=3D"MsoNormal">=A0</p>

</div></div></div>

</div><div><div></div><div class=3D"h5">



<table><tbody><tr><td bgcolor=3D"#ffffff"><font color=3D"#000000"><pre>****=
 DISCLAIMER ****
<a href=3D"http://www.belgacom.be/maildisclaimer" target=3D"_blank">http://=
www.belgacom.be/maildisclaimer</a></pre></font></td></tr></tbody></table>
</div></div></blockquote></div><br>

--00148530a3462304200482234a85--

From ietf.hanserik@gmail.com  Fri Mar 19 02:06:01 2010
Return-Path: <ietf.hanserik@gmail.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 AFC313A68D6 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 02:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.767
X-Spam-Level: 
X-Spam-Status: No, score=-1.767 tagged_above=-999 required=5 tests=[AWL=-0.299, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 dl19cUQDitfr for <martini@core3.amsl.com>; Fri, 19 Mar 2010 02:06:00 -0700 (PDT)
Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216]) by core3.amsl.com (Postfix) with ESMTP id 69B9A3A68BF for <martini@ietf.org>; Fri, 19 Mar 2010 02:06:00 -0700 (PDT)
Received: by ewy8 with SMTP id 8so1611365ewy.28 for <martini@ietf.org>; Fri, 19 Mar 2010 02:06:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=Id9AFCyANvCx9paAPFqCTNSIznYipXdv+8KhQTztnXE=; b=oBMUx6H0iwKTrdwtzyId1Sm950lO6QrjAS20pPd/vEQP6VrLEzxynIzjDRvXYvQc3D oeOADTj9QpayfHNi43pAVdpx9gnhgFk8u9NtBqN+xw+aIA2qgj/nBRFJLdbqDegKutoV nDG9Le16ihiA/oU/d+a3pQLtTEDu+hcyo1aC4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=CDivr5O74QTiqUsVupFwP24AKadTqx84MDpISR/Tuomh+v6DPvBlw1G/8A78Lvt9JO XSUnCkHXm75uwHGJaV5Q1RM3TEnqBJFWWuWqypL5/VrDN6SR111AVtPwupqXFDQmzbOu DoJkfmS4Gu7Rqt+bVHPhaMBdZJufcVN5/4GfQ=
MIME-Version: 1.0
Received: by 10.213.2.79 with SMTP id 15mr711573ebi.96.1268989569030; Fri, 19  Mar 2010 02:06:09 -0700 (PDT)
In-Reply-To: <4BA2AED5.5040903@nostrum.com>
References: <065.111f925a59a8643c429a6e1e5e86d2da@tools.ietf.org> <4BA2AED5.5040903@nostrum.com>
Date: Fri, 19 Mar 2010 10:06:09 +0100
Message-ID: <9ae56b1e1003190206if9c8851p1fc2b5fbc47cbca4@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: Adam Roach <adam@nostrum.com>
Content-Type: multipart/alternative; boundary=0015174768187c5e27048223a831
Cc: martini issue tracker <trac@tools.ietf.org>, trac@localhost.amsl.com, martini@ietf.org
Subject: Re: [martini] #16: Extensibility to support any 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: Fri, 19 Mar 2010 09:06:01 -0000

--0015174768187c5e27048223a831
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Adam,

I disagree, it is different in that it formulates a design goal that the
solution must not inhibit using the same mechanism for non number AOR's. Of
course if that is not clear we could rephrase.

I used TRAC as a guesture to the group where it was expressed to be the too=
l
of choice for such remarks.
Accusations of bad intent are totally inappropriate.

Best Regards,
/Hans Erik van Elburg

On Thu, Mar 18, 2010 at 11:53 PM, Adam Roach <adam@nostrum.com> wrote:

> Satisfying this requirement would require solving the general case before
> we can declare victory on the phone number case. I think we've already co=
me
> to a pretty strong consensus that we're doing the phone number case first=
,
> for the sake of expediency.
>
> I would also argue that opening trac bugs to request features that are
> intentionally duplicates (this one duplicates bugs #5 and #6) and contrar=
y
> to apparent working group consensus is an abuse of the trac system.
>
> This should be closed as a duplicate of #6.
>
> /a
>
>
> On 3/18/10 5:12 PM, martini issue tracker wrote:
>
>> #16: Extensibility to support any AOR
>>
>> -------------------------------------+----------------------------------=
----
>>  Reporter:  ietf.hanserik@=85          |       Owner:
>>      Type:  enhancement              |      Status:  new
>>  Priority:  critical                 |   Milestone:  milestone1
>> Component:  reqs                     |     Version:  1.0
>>  Severity:  In WG Last Call          |    Keywords:
>>
>> -------------------------------------+----------------------------------=
----
>>  REQ20 - The mechanism MUST be extensible to allow a set of arbitrary
>>  assigned SIP URI's as specified in RFC3261, without requiring a complet=
e
>>  change of mechanism as compared to that used for numbers.
>>
>>
>>
>
>

--0015174768187c5e27048223a831
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Adam,<br><br>I disagree, it is different in that it formulates a design goa=
l that the solution must not inhibit using the same mechanism for non numbe=
r AOR&#39;s. Of course if that is not clear we could rephrase.<br><br>I use=
d TRAC as a guesture to the group where it was expressed to be the tool of =
choice for such remarks. <br>
Accusations of=20
bad intent are totally inappropriate. <br><br>Best Regards,<br clear=3D"all=
">/Hans Erik van Elburg<br>
<br><div class=3D"gmail_quote">On Thu, Mar 18, 2010 at 11:53 PM, Adam Roach=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:adam@nostrum.com">adam@nostrum.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-lef=
t: 1ex;">
Satisfying this requirement would require solving the general case before w=
e can declare victory on the phone number case. I think we&#39;ve already c=
ome to a pretty strong consensus that we&#39;re doing the phone number case=
 first, for the sake of expediency.<br>

<br>
I would also argue that opening trac bugs to request features that are inte=
ntionally duplicates (this one duplicates bugs #5 and #6) and contrary to a=
pparent working group consensus is an abuse of the trac system.<br>
<br>
This should be closed as a duplicate of #6.<br><font color=3D"#888888">
<br>
/a</font><div><div></div><div class=3D"h5"><br>
<br>
On 3/18/10 5:12 PM, martini issue tracker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
#16: Extensibility to support any AOR<br>
-------------------------------------+-------------------------------------=
-<br>
 =A0Reporter: =A0ietf.hanserik@=85 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0 Owner:<=
br>
 =A0 =A0 =A0Type: =A0enhancement =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0St=
atus: =A0new<br>
 =A0Priority: =A0critical =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 Milestone: =
=A0milestone1<br>
Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 Versio=
n: =A01.0<br>
 =A0Severity: =A0In WG Last Call =A0 =A0 =A0 =A0 =A0| =A0 =A0Keywords:<br>
-------------------------------------+-------------------------------------=
-<br>
 =A0REQ20 - The mechanism MUST be extensible to allow a set of arbitrary<br=
>
 =A0assigned SIP URI&#39;s as specified in RFC3261, without requiring a com=
plete<br>
 =A0change of mechanism as compared to that used for numbers.<br>
<br>
 =A0 <br>
</blockquote>
<br>
</div></div></blockquote></div><br>

--0015174768187c5e27048223a831--

From john.elwell@siemens-enterprise.com  Fri Mar 19 03:54:54 2010
Return-Path: <john.elwell@siemens-enterprise.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 131703A6867 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 03:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.755
X-Spam-Level: 
X-Spam-Status: No, score=-0.755 tagged_above=-999 required=5 tests=[AWL=-1.145, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13]
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 MZAfc+oHzA8F for <martini@core3.amsl.com>; Fri, 19 Mar 2010 03:54:53 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id E2F873A6778 for <martini@ietf.org>; Fri, 19 Mar 2010 03:54:52 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1274606; Fri, 19 Mar 2010 11:55:00 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id 5666623F0278; Fri, 19 Mar 2010 11:55:00 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Fri, 19 Mar 2010 11:55:00 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>, Adam Roach <adam@nostrum.com>
Date: Fri, 19 Mar 2010 11:54:58 +0100
Thread-Topic: [martini] #16: Extensibility to support any AOR
Thread-Index: AcrHQ28NOA+fMslGS1uQTgbLp8NnVAAC+z+w
Message-ID: <A444A0F8084434499206E78C106220CABE982753@MCHP058A.global-ad.net>
References: <065.111f925a59a8643c429a6e1e5e86d2da@tools.ietf.org> <4BA2AED5.5040903@nostrum.com> <9ae56b1e1003190206if9c8851p1fc2b5fbc47cbca4@mail.gmail.com>
In-Reply-To: <9ae56b1e1003190206if9c8851p1fc2b5fbc47cbca4@mail.gmail.com>
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
Cc: "trac@localhost.amsl.com" <trac@localhost.amsl.com>, martini issue tracker <trac@tools.ietf.org>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #16: Extensibility to support any 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: Fri, 19 Mar 2010 10:54:54 -0000

As editor, I see #16 as being different from #6, so this is acceptable use =
of the issue tracker.

As individual, I have difficult accepting #16. The group consensus to work =
on an initial version that addresses the E.164 use case was made in the kno=
wledge that a more general solution would be harder, and probably would nee=
d to take a quite different direction (probably not based on REGISTER). In =
that case I doubt the proposed new requirement REQ20 is achievable without =
reversing our decision to focus initially on E.164 numbers. Stating require=
ments that are known to be unachievable will not move the work forward. The=
refore my proposal would be to reject this request.

John

> -----Original Message-----
> From: martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] On Behalf Of Hans Erik van Elburg
> Sent: 19 March 2010 09:06
> To: Adam Roach
> Cc: martini issue tracker; trac@localhost.amsl.com; martini@ietf.org
> Subject: Re: [martini] #16: Extensibility to support any AOR
>=20
> Adam,
>=20
> I disagree, it is different in that it formulates a design=20
> goal that the solution must not inhibit using the same=20
> mechanism for non number AOR's. Of course if that is not=20
> clear we could rephrase.
>=20
> I used TRAC as a guesture to the group where it was expressed=20
> to be the tool of choice for such remarks.=20
> Accusations of bad intent are totally inappropriate.=20
>=20
> Best Regards,
> /Hans Erik van Elburg
>=20
>=20
> On Thu, Mar 18, 2010 at 11:53 PM, Adam Roach <adam@nostrum.com> wrote:
>=20
>=20
> 	Satisfying this requirement would require solving the=20
> general case before we can declare victory on the phone=20
> number case. I think we've already come to a pretty strong=20
> consensus that we're doing the phone number case first, for=20
> the sake of expediency.
> =09
> 	I would also argue that opening trac bugs to request=20
> features that are intentionally duplicates (this one=20
> duplicates bugs #5 and #6) and contrary to apparent working=20
> group consensus is an abuse of the trac system.
> =09
> 	This should be closed as a duplicate of #6.
> =09
> 	/a=20
>=20
>=20
> 	On 3/18/10 5:12 PM, martini issue tracker wrote:
> =09
>=20
> 		#16: Extensibility to support any AOR
> 	=09
> -------------------------------------+------------------------
> --------------
> 		 Reporter:  ietf.hanserik@...          |       Owner:
> 		     Type:  enhancement              |      Status:  new
> 		 Priority:  critical                 |  =20
> Milestone:  milestone1
> 		Component:  reqs                     |     Version:  1.0
> 		 Severity:  In WG Last Call          |    Keywords:
> 	=09
> -------------------------------------+------------------------
> --------------
> 		 REQ20 - The mechanism MUST be extensible to=20
> allow a set of arbitrary
> 		 assigned SIP URI's as specified in RFC3261,=20
> without requiring a complete
> 		 change of mechanism as compared to that used=20
> for numbers.
> 	=09
> 		 =20
> 	=09
>=20
>=20
>=20
> =

From john.elwell@siemens-enterprise.com  Fri Mar 19 04:01:50 2010
Return-Path: <john.elwell@siemens-enterprise.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 7E0A63A6975 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 04:01:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level: 
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[AWL=-0.178, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 WxsaBI477o1d for <martini@core3.amsl.com>; Fri, 19 Mar 2010 04:01:49 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 1B85D3A69B5 for <martini@ietf.org>; Fri, 19 Mar 2010 04:01:48 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1273639; Fri, 19 Mar 2010 12:02:01 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 51F5E1EB82BB; Fri, 19 Mar 2010 12:02:01 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Fri, 19 Mar 2010 12:02:01 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "trac@localhost.amsl.com" <trac@localhost.amsl.com>, "ietf.hanserik@gmail.com" <ietf.hanserik@gmail.com>
Date: Fri, 19 Mar 2010 12:01:59 +0100
Thread-Topic: [martini]  #17: Desirable to align with existing standards
Thread-Index: AcrG6XIaCNf2ltHlS5uWdQHVxh1PdAAaXqSw
Message-ID: <A444A0F8084434499206E78C106220CABE982764@MCHP058A.global-ad.net>
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org>
In-Reply-To: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #17: Desirable to align with existing standards
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: Fri, 19 Mar 2010 11:01:50 -0000

As individual, I would remark that the market is already fragmented between=
 SIP and IMS-SIP, which makes things difficult.

As editor, I seek guidance from others on this one.

John

> -----Original Message-----
> From: martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] On Behalf Of martini issue tracker
> Sent: 18 March 2010 22:21
> To: ietf.hanserik@gmail.com
> Cc: martini@ietf.org
> Subject: [martini] #17: Desirable to align with existing standards
>=20
> #17: Desirable to align with existing standards
> -------------------------------------+------------------------
> --------------
>  Reporter:  ietf.hanserik@...          |       Owner:           =20
>      Type:  enhancement              |      Status:  new      =20
>  Priority:  major                    |   Milestone:  milestone1
> Component:  reqs                     |     Version:  1.0      =20
>  Severity:  In WG Last Call          |    Keywords:           =20
> -------------------------------------+------------------------
> --------------
>  DES5 - The mechanism SHOULD be aligned as much as possible=20
> with mechanisms
>  already standardised in other SDO's like ETSI and 3GPP in order to
>  prohibit a fragmentation of the market.
>=20
> --=20
> Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/17>
> martini <http://tools.ietf.org/martini/>
>=20
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
> =

From john.elwell@siemens-enterprise.com  Fri Mar 19 04:10:19 2010
Return-Path: <john.elwell@siemens-enterprise.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 EF26F3A68DE for <martini@core3.amsl.com>; Fri, 19 Mar 2010 04:10:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.641
X-Spam-Level: 
X-Spam-Status: No, score=-1.641 tagged_above=-999 required=5 tests=[AWL=-0.172, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 6sF7E7JnN0UO for <martini@core3.amsl.com>; Fri, 19 Mar 2010 04:10:16 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 0CEB83A68B6 for <martini@ietf.org>; Fri, 19 Mar 2010 04:10:08 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1274612; Fri, 19 Mar 2010 11:55:20 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 561241EB82BB; Fri, 19 Mar 2010 11:55:20 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Fri, 19 Mar 2010 11:55:20 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "trac@localhost.amsl.com" <trac@localhost.amsl.com>, "ietf.hanserik@gmail.com" <ietf.hanserik@gmail.com>
Date: Fri, 19 Mar 2010 11:55:18 +0100
Thread-Topic: [martini]  #15: support for non E.164 numbers
Thread-Index: AcrG5sLK8AdLEaxATGmDd7ZN6oXUSwAagbNg
Message-ID: <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net>
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org>
In-Reply-To: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #15: support for non E.164 numbers
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: Fri, 19 Mar 2010 11:10:19 -0000

As an individual, I don't see an urgent need to solve this in the initial p=
hase. Present deployments use fully-qualified E.164 numbers (or numbers tha=
t can be turned into fully-qualified E.164 numbers), and it is for these de=
ployments that we urgently need a standard on which to converge. Support fo=
r non-E.164-based (private numbers) might be nice to have, but not essentia=
l.=20

I guess an important point is whether these non-E.164 numbers are globally =
unique (as a result of a phone-context parameter), in which case they might=
 be easier to accommodate, but even then I am not sure. If I have a telepho=
ne number in the form tel:1234;phone-context=3Dpbx.com, how does this get r=
outed to ssp.com in order to get onward-routed to the PBX? It might work if=
 you start off with sip:1234;phone-context=3Dpbx.com@ssp.com;user=3Dphone, =
but how would the calling UA construct such a URI in the first place (unles=
s returning a received URI)?

It seems to me that considerations are similar to non-number-based SIP URIs=
, and therefore this should be treated in the same way as #16 (depending on=
 what we decide for that - see my recommendation in my previous email).

John


> -----Original Message-----
> From: martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] On Behalf Of martini issue tracker
> Sent: 18 March 2010 22:03
> To: ietf.hanserik@gmail.com
> Cc: martini@ietf.org
> Subject: [martini] #15: support for non E.164 numbers
>=20
> #15: support for non E.164 numbers
> -------------------------------------+------------------------
> --------------
>  Reporter:  ietf.hanserik@...          |       Owner:           =20
>      Type:  defect                   |      Status:  new      =20
>  Priority:  critical                 |   Milestone:  milestone1
> Component:  reqs                     |     Version:  1.0      =20
>  Severity:  In WG Last Call          |    Keywords:           =20
> -------------------------------------+------------------------
> --------------
>  REQ19 - The mechanism MUST allow a set of assigned telephone=20
> numbers to
>  comprise local numbers as specified in RFC3966, which can be in
>  contiguous ranges, discrete, or in any combination of the two.
>=20
> --=20
> Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/15>
> martini <http://tools.ietf.org/martini/>
>=20
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
> =

From ietf.hanserik@gmail.com  Fri Mar 19 04:20:59 2010
Return-Path: <ietf.hanserik@gmail.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 73D9B3A68F9 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 04:20:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.729
X-Spam-Level: 
X-Spam-Status: No, score=-1.729 tagged_above=-999 required=5 tests=[AWL=-0.261, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 NhBsX2SaScJ3 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 04:20:57 -0700 (PDT)
Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216]) by core3.amsl.com (Postfix) with ESMTP id 9A2CF3A68DE for <martini@ietf.org>; Fri, 19 Mar 2010 04:20:53 -0700 (PDT)
Received: by ewy8 with SMTP id 8so1652789ewy.28 for <martini@ietf.org>; Fri, 19 Mar 2010 04:21:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=/Sl43uiNbpsZH7l1K5RRyfh3MqNHMKOP9D0bgIa1Sec=; b=XOlLAvRcbvhIYhAAzRTpK41ePKiRBDLkl2DYdaHAmxiuvgQN+hxdVX2BN2UBT++P3a uHCSBZdUZrFwHPszn3Xv3LkBm7WOFloWmF63BIj3Xuu0MIAUWUv2HwvVrWkchTTCaLpd 2JiuHfJonDCBM0ZoWjusgavuZNZc3kZwR5p8o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=pqTROWJJK6CHZCMNBvpctFPzwvxSnQCBZBXMTetQcEoQqIF5ardP2hgbgH6p/4ZjnJ 7EBlR+P5HCK5GmurDTqP50WEqs7REtvByJ/+KUTJQKPz8hV1GBHuQxt8jGfjYEZ6BGN2 VcjCLKQX32HzlHcvDa3JG6RyqaWaJugl67EBE=
MIME-Version: 1.0
Received: by 10.213.34.79 with HTTP; Fri, 19 Mar 2010 04:21:02 -0700 (PDT)
In-Reply-To: <A444A0F8084434499206E78C106220CABE982764@MCHP058A.global-ad.net>
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982764@MCHP058A.global-ad.net>
Date: Fri, 19 Mar 2010 12:21:02 +0100
Received: by 10.213.54.147 with SMTP id q19mr361445ebg.12.1268997662984; Fri,  19 Mar 2010 04:21:02 -0700 (PDT)
Message-ID: <9ae56b1e1003190421r553a6197ke711efeddc65966@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Content-Type: multipart/alternative; boundary=00c09ffb588eec4b280482258a38
Cc: "trac@localhost.amsl.com" <trac@localhost.amsl.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #17: Desirable to align with existing standards
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: Fri, 19 Mar 2010 11:20:59 -0000

--00c09ffb588eec4b280482258a38
Content-Type: text/plain; charset=ISO-8859-1

SIP = SIP, regardless whether the service provider uses an IMS architecture
or not.

IMS provides a given SIP profile, in a non-IMS setting things are less clear
which is part of the problem we face today.

/Hans Erik van Elburg


On Fri, Mar 19, 2010 at 12:01 PM, Elwell, John <
john.elwell@siemens-enterprise.com> wrote:

> As individual, I would remark that the market is already fragmented between
> SIP and IMS-SIP, which makes things difficult.
>
> As editor, I seek guidance from others on this one.
>
> John
>
> > -----Original Message-----
> > From: martini-bounces@ietf.org
> > [mailto:martini-bounces@ietf.org] On Behalf Of martini issue tracker
> > Sent: 18 March 2010 22:21
> > To: ietf.hanserik@gmail.com
> > Cc: martini@ietf.org
> > Subject: [martini] #17: Desirable to align with existing standards
> >
> > #17: Desirable to align with existing standards
> > -------------------------------------+------------------------
> > --------------
> >  Reporter:  ietf.hanserik@...          |       Owner:
> >      Type:  enhancement              |      Status:  new
> >  Priority:  major                    |   Milestone:  milestone1
> > Component:  reqs                     |     Version:  1.0
> >  Severity:  In WG Last Call          |    Keywords:
> > -------------------------------------+------------------------
> > --------------
> >  DES5 - The mechanism SHOULD be aligned as much as possible
> > with mechanisms
> >  already standardised in other SDO's like ETSI and 3GPP in order to
> >  prohibit a fragmentation of the market.
> >
> > --
> > Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/17>
> > martini <http://tools.ietf.org/martini/>
> >
> > _______________________________________________
> > martini mailing list
> > martini@ietf.org
> > https://www.ietf.org/mailman/listinfo/martini
> >

--00c09ffb588eec4b280482258a38
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

SIP =3D SIP, regardless whether the service provider uses an IMS architectu=
re or not.<br><br>IMS provides a given SIP profile, in a non-IMS setting th=
ings are less clear which is part of the problem we face today.=A0 <br><br =
clear=3D"all">
/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Fri, Mar 19, 2010 at 12:01 PM, Elwell=
, John <span dir=3D"ltr">&lt;<a href=3D"mailto:john.elwell@siemens-enterpri=
se.com">john.elwell@siemens-enterprise.com</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left:=
 1px solid rgb(204, 204, 204); padding-left: 1ex;">
As individual, I would remark that the market is already fragmented between=
 SIP and IMS-SIP, which makes things difficult.<br>
<br>
As editor, I seek guidance from others on this one.<br>
<br>
John<br>
<div><div></div><div class=3D"h5"><br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:martini-bounces@ietf.org">martini-bounces@ietf=
.org</a><br>
&gt; [mailto:<a href=3D"mailto:martini-bounces@ietf.org">martini-bounces@ie=
tf.org</a>] On Behalf Of martini issue tracker<br>
&gt; Sent: 18 March 2010 22:21<br>
&gt; To: <a href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com=
</a><br>
&gt; Cc: <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; Subject: [martini] #17: Desirable to align with existing standards<br>
&gt;<br>
&gt; #17: Desirable to align with existing standards<br>
&gt; -------------------------------------+------------------------<br>
&gt; --------------<br>
&gt; =A0Reporter: =A0ietf.hanserik@... =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0 Own=
er:<br>
&gt; =A0 =A0 =A0Type: =A0enhancement =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =
=A0Status: =A0new<br>
&gt; =A0Priority: =A0major =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 Mil=
estone: =A0milestone1<br>
&gt; Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 V=
ersion: =A01.0<br>
&gt; =A0Severity: =A0In WG Last Call =A0 =A0 =A0 =A0 =A0| =A0 =A0Keywords:<=
br>
&gt; -------------------------------------+------------------------<br>
&gt; --------------<br>
&gt; =A0DES5 - The mechanism SHOULD be aligned as much as possible<br>
&gt; with mechanisms<br>
&gt; =A0already standardised in other SDO&#39;s like ETSI and 3GPP in order=
 to<br>
&gt; =A0prohibit a fragmentation of the market.<br>
&gt;<br>
&gt; --<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/trac/=
ticket/17" target=3D"_blank">http://trac.tools.ietf.org/wg/martini/trac/tic=
ket/17</a>&gt;<br>
&gt; martini &lt;<a href=3D"http://tools.ietf.org/martini/" target=3D"_blan=
k">http://tools.ietf.org/martini/</a>&gt;<br>
&gt;<br>
</div></div>&gt; _______________________________________________<br>
&gt; martini mailing list<br>
&gt; <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/martini</a><br>
&gt; </blockquote></div><br>

--00c09ffb588eec4b280482258a38--

From ietf.hanserik@gmail.com  Fri Mar 19 04:30:32 2010
Return-Path: <ietf.hanserik@gmail.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 1B0203A68F0 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 04:30:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[AWL=-0.232,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 UyU2-zu0heFb for <martini@core3.amsl.com>; Fri, 19 Mar 2010 04:30:31 -0700 (PDT)
Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216]) by core3.amsl.com (Postfix) with ESMTP id 5F57D3A68B6 for <martini@ietf.org>; Fri, 19 Mar 2010 04:30:30 -0700 (PDT)
Received: by ewy8 with SMTP id 8so1655578ewy.28 for <martini@ietf.org>; Fri, 19 Mar 2010 04:30:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=2CBDMKizS6x5dC2oIgu/a02jnBunVMGvNQGwJI6Irdc=; b=mFuQkpqrzXvaFfddm1SjLwyqo7qhHo7Nib+xCwlIAnr4NXs3UTuGyyU6A5uvWZhblV oD1sYCImVm2o/NJQ1azh2GTXdBpgtj5dRoFeU4Q7y4zrbZTogeQSJjxEuN/54ZvEe3oO cdgW74c+t3fY9Id/k5qp236fUiamJMrfmUaWg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=sWMd5HSKHRxUrJ0JKYPudC78mtGHzvm1ERx+TI/LF9z2pf+xZC3VJlwnvxm/N2GCEI IsnZyMF84zhaVS7EOFtXyOk1G6vliwjC2Bbm06z+c/WB8+CeiihIUB0Zat/cY9RA3zuz ln+WpIRaVXqVZxbHpflkVsxsJBlsEQdBbeBUg=
MIME-Version: 1.0
Received: by 10.213.39.14 with SMTP id d14mr2502843ebe.24.1268998238982; Fri,  19 Mar 2010 04:30:38 -0700 (PDT)
In-Reply-To: <A444A0F8084434499206E78C106220CABE982753@MCHP058A.global-ad.net>
References: <065.111f925a59a8643c429a6e1e5e86d2da@tools.ietf.org> <4BA2AED5.5040903@nostrum.com> <9ae56b1e1003190206if9c8851p1fc2b5fbc47cbca4@mail.gmail.com> <A444A0F8084434499206E78C106220CABE982753@MCHP058A.global-ad.net>
Date: Fri, 19 Mar 2010 12:30:38 +0100
Message-ID: <9ae56b1e1003190430l21c907des5faa11f02b1f3430@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Content-Type: multipart/alternative; boundary=00148531ab61415459048225ad97
Cc: martini issue tracker <trac@tools.ietf.org>, "trac@localhost.amsl.com" <trac@localhost.amsl.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #16: Extensibility to support any 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: Fri, 19 Mar 2010 11:30:32 -0000

--00148531ab61415459048225ad97
Content-Type: text/plain; charset=ISO-8859-1

It is not clear why implicit registration could be equally valid here.

The question is not how such requests reach the SSP, the question is how
given that such requests are handled by the SSP such can be delivered to an
IP-PBX to which they are assigned.

The point is that an SSP may have more complete enterprise offering that
would require calls to be delivered via the SSP cloud to enterprise private
numbers that do not have a DID E.164 number, but which are assigned to a
PBX. Such private numbers are completely under control of the enterprise and
do not require reservation of E.164 for no good reason.

The current solution should not prohibit such service offerings and I
haven't seen a good reason why this should not be covered.

/Hans Erik van Elburg


On Fri, Mar 19, 2010 at 11:54 AM, Elwell, John <
john.elwell@siemens-enterprise.com> wrote:

> As editor, I see #16 as being different from #6, so this is acceptable use
> of the issue tracker.
>
> As individual, I have difficult accepting #16. The group consensus to work
> on an initial version that addresses the E.164 use case was made in the
> knowledge that a more general solution would be harder, and probably would
> need to take a quite different direction (probably not based on REGISTER).
> In that case I doubt the proposed new requirement REQ20 is achievable
> without reversing our decision to focus initially on E.164 numbers. Stating
> requirements that are known to be unachievable will not move the work
> forward. Therefore my proposal would be to reject this request.
>
> John
>
> > -----Original Message-----
> > From: martini-bounces@ietf.org
> > [mailto:martini-bounces@ietf.org] On Behalf Of Hans Erik van Elburg
> > Sent: 19 March 2010 09:06
> > To: Adam Roach
> > Cc: martini issue tracker; trac@localhost.amsl.com; martini@ietf.org
> > Subject: Re: [martini] #16: Extensibility to support any AOR
> >
> > Adam,
> >
> > I disagree, it is different in that it formulates a design
> > goal that the solution must not inhibit using the same
> > mechanism for non number AOR's. Of course if that is not
> > clear we could rephrase.
> >
> > I used TRAC as a guesture to the group where it was expressed
> > to be the tool of choice for such remarks.
> > Accusations of bad intent are totally inappropriate.
> >
> > Best Regards,
> > /Hans Erik van Elburg
> >
> >
> > On Thu, Mar 18, 2010 at 11:53 PM, Adam Roach <adam@nostrum.com> wrote:
> >
> >
> >       Satisfying this requirement would require solving the
> > general case before we can declare victory on the phone
> > number case. I think we've already come to a pretty strong
> > consensus that we're doing the phone number case first, for
> > the sake of expediency.
> >
> >       I would also argue that opening trac bugs to request
> > features that are intentionally duplicates (this one
> > duplicates bugs #5 and #6) and contrary to apparent working
> > group consensus is an abuse of the trac system.
> >
> >       This should be closed as a duplicate of #6.
> >
> >       /a
> >
> >
> >       On 3/18/10 5:12 PM, martini issue tracker wrote:
> >
> >
> >               #16: Extensibility to support any AOR
> >
> > -------------------------------------+------------------------
> > --------------
> >                Reporter:  ietf.hanserik@...          |       Owner:
> >                    Type:  enhancement              |      Status:  new
> >                Priority:  critical                 |
> > Milestone:  milestone1
> >               Component:  reqs                     |     Version:  1.0
> >                Severity:  In WG Last Call          |    Keywords:
> >
> > -------------------------------------+------------------------
> > --------------
> >                REQ20 - The mechanism MUST be extensible to
> > allow a set of arbitrary
> >                assigned SIP URI's as specified in RFC3261,
> > without requiring a complete
> >                change of mechanism as compared to that used
> > for numbers.
> >
> >
> >
> >
> >
> >
> >
>

--00148531ab61415459048225ad97
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It is not clear why implicit registration could be equally valid here.<br><=
br>The question is not how such requests reach the SSP, the question is how=
 given that such requests are handled by the SSP such can be delivered to a=
n IP-PBX to which they are assigned.<br>
<br>The point is that an SSP may have more complete enterprise offering tha=
t would require calls to be delivered via the SSP cloud to enterprise priva=
te numbers that do not have a DID E.164 number, but which are assigned to a=
 PBX. Such private numbers are completely under control of the enterprise a=
nd do not require reservation of E.164 for no good reason.<br>
<br>The current solution should not prohibit such service offerings and I h=
aven&#39;t seen a good reason why this should not be covered.<br><br clear=
=3D"all">/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Fri, Mar 19, 2010 at 11:54 AM, Elwell=
, John <span dir=3D"ltr">&lt;<a href=3D"mailto:john.elwell@siemens-enterpri=
se.com">john.elwell@siemens-enterprise.com</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left:=
 1px solid rgb(204, 204, 204); padding-left: 1ex;">
As editor, I see #16 as being different from #6, so this is acceptable use =
of the issue tracker.<br>
<br>
As individual, I have difficult accepting #16. The group consensus to work =
on an initial version that addresses the E.164 use case was made in the kno=
wledge that a more general solution would be harder, and probably would nee=
d to take a quite different direction (probably not based on REGISTER). In =
that case I doubt the proposed new requirement REQ20 is achievable without =
reversing our decision to focus initially on E.164 numbers. Stating require=
ments that are known to be unachievable will not move the work forward. The=
refore my proposal would be to reject this request.<br>

<font color=3D"#888888"><br>
John<br>
</font><div><div></div><div class=3D"h5"><br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:martini-bounces@ietf.org">martini-bounces@ietf=
.org</a><br>
&gt; [mailto:<a href=3D"mailto:martini-bounces@ietf.org">martini-bounces@ie=
tf.org</a>] On Behalf Of Hans Erik van Elburg<br>
&gt; Sent: 19 March 2010 09:06<br>
&gt; To: Adam Roach<br>
&gt; Cc: martini issue tracker; <a href=3D"mailto:trac@localhost.amsl.com">=
trac@localhost.amsl.com</a>; <a href=3D"mailto:martini@ietf.org">martini@ie=
tf.org</a><br>
&gt; Subject: Re: [martini] #16: Extensibility to support any AOR<br>
&gt;<br>
&gt; Adam,<br>
&gt;<br>
&gt; I disagree, it is different in that it formulates a design<br>
&gt; goal that the solution must not inhibit using the same<br>
&gt; mechanism for non number AOR&#39;s. Of course if that is not<br>
&gt; clear we could rephrase.<br>
&gt;<br>
&gt; I used TRAC as a guesture to the group where it was expressed<br>
&gt; to be the tool of choice for such remarks.<br>
&gt; Accusations of bad intent are totally inappropriate.<br>
&gt;<br>
&gt; Best Regards,<br>
&gt; /Hans Erik van Elburg<br>
&gt;<br>
&gt;<br>
&gt; On Thu, Mar 18, 2010 at 11:53 PM, Adam Roach &lt;<a href=3D"mailto:ada=
m@nostrum.com">adam@nostrum.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 Satisfying this requirement would require solving the<br>
&gt; general case before we can declare victory on the phone<br>
&gt; number case. I think we&#39;ve already come to a pretty strong<br>
&gt; consensus that we&#39;re doing the phone number case first, for<br>
&gt; the sake of expediency.<br>
&gt;<br>
&gt; =A0 =A0 =A0 I would also argue that opening trac bugs to request<br>
&gt; features that are intentionally duplicates (this one<br>
&gt; duplicates bugs #5 and #6) and contrary to apparent working<br>
&gt; group consensus is an abuse of the trac system.<br>
&gt;<br>
&gt; =A0 =A0 =A0 This should be closed as a duplicate of #6.<br>
&gt;<br>
&gt; =A0 =A0 =A0 /a<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 On 3/18/10 5:12 PM, martini issue tracker wrote:<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 #16: Extensibility to support any AOR<br>
&gt;<br>
&gt; -------------------------------------+------------------------<br>
&gt; --------------<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Reporter: =A0ietf.hanserik@... =A0 =A0 =
=A0 =A0 =A0| =A0 =A0 =A0 Owner:<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Type: =A0enhancement =A0 =A0 =
=A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0Status: =A0new<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Priority: =A0critical =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 |<br>
&gt; Milestone: =A0milestone1<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 | =A0 =A0 Version: =A01.0<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Severity: =A0In WG Last Call =A0 =A0 =
=A0 =A0 =A0| =A0 =A0Keywords:<br>
&gt;<br>
&gt; -------------------------------------+------------------------<br>
&gt; --------------<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0REQ20 - The mechanism MUST be extensibl=
e to<br>
&gt; allow a set of arbitrary<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0assigned SIP URI&#39;s as specified in =
RFC3261,<br>
&gt; without requiring a complete<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0change of mechanism as compared to that=
 used<br>
&gt; for numbers.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; </div></div></blockquote></div><br>

--00148531ab61415459048225ad97--

From trac@tools.ietf.org  Fri Mar 19 04:35:06 2010
Return-Path: <trac@tools.ietf.org>
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 2C6C53A68B6 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 04:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.879
X-Spam-Level: 
X-Spam-Status: No, score=-101.879 tagged_above=-999 required=5 tests=[AWL=-0.409, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 eii-q1hF4-8a for <martini@core3.amsl.com>; Fri, 19 Mar 2010 04:35:05 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 8FE133A63C9 for <martini@ietf.org>; Fri, 19 Mar 2010 04:35:05 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NsaU2-00073m-Fx; Fri, 19 Mar 2010 04:35:18 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: martini
Date: Fri, 19 Mar 2010 11:35:18 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/16#comment:1
Message-ID: <074.736485b13c62b26346edf6d0c69d1361@tools.ietf.org>
References: <065.111f925a59a8643c429a6e1e5e86d2da@tools.ietf.org>
X-Trac-Ticket-ID: 16
In-Reply-To: <065.111f925a59a8643c429a6e1e5e86d2da@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #16: Extensibility to support any AOR
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Fri, 19 Mar 2010 11:35:06 -0000

#16: Extensibility to support any AOR
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |        Owner:            
     Type:  enhancement              |       Status:  closed    
 Priority:  critical                 |    Milestone:  milestone1
Component:  reqs                     |      Version:  1.0       
 Severity:  In WG Last Call          |   Resolution:  duplicate 
 Keywords:                           |  
-------------------------------------+--------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => duplicate


Comment:

 This is duplicate of Issue #6.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/16#comment:1>
martini <http://tools.ietf.org/martini/>


From ietf.hanserik@gmail.com  Fri Mar 19 04:50:10 2010
Return-Path: <ietf.hanserik@gmail.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 BAF1A3A6800 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 04:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level: 
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[AWL=-0.209, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 asH2kbpQgxab for <martini@core3.amsl.com>; Fri, 19 Mar 2010 04:50:10 -0700 (PDT)
Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216]) by core3.amsl.com (Postfix) with ESMTP id B57E83A6774 for <martini@ietf.org>; Fri, 19 Mar 2010 04:50:09 -0700 (PDT)
Received: by ewy8 with SMTP id 8so1661537ewy.28 for <martini@ietf.org>; Fri, 19 Mar 2010 04:50:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=mhv8U35js3HriexvGidX39chXRQ5+OfO+77n+fb0VeA=; b=D9cND1QSQg107QCTYfe2JW+fLLVMP9wSIMfQJSCCWdDUbpzBbdgiy1lSXaP42JvBrl 3IfC8YIvFwsmH89man1HWPNo3Nmzix6PfZ18HVnwjzQhcLpamZOEvOXYbS4Y8OVtQLRg J3aIIXZNFYASgxItCTPJsIhOsEZR23yRsN0Iw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TqnKqbeSC0ZUP0A9QTq9w5Bjoc2ZHO8Ln62JuQFfvKtBJK29qU95oyemQ8q5dtFFqV KHT3+U2KfyaO6Yd0Q1E/lqxLy7gQW9ZxlUcRcJy82xcd/7L8R2PK5dh2gGScxE4T+Ec6 sXBSArGCgcJdX5MF1M5vU400EB4GFx4DCmbwg=
MIME-Version: 1.0
Received: by 10.213.2.75 with SMTP id 11mr5993381ebi.14.1268999419533; Fri, 19  Mar 2010 04:50:19 -0700 (PDT)
In-Reply-To: <074.736485b13c62b26346edf6d0c69d1361@tools.ietf.org>
References: <065.111f925a59a8643c429a6e1e5e86d2da@tools.ietf.org> <074.736485b13c62b26346edf6d0c69d1361@tools.ietf.org>
Date: Fri, 19 Mar 2010 12:50:19 +0100
Message-ID: <9ae56b1e1003190450n2246bf5cm8bdbdbd49b5d986@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: bernard_aboba@hotmail.com
Content-Type: multipart/alternative; boundary=0015174762f09f193e048225f3b1
Cc: martini@ietf.org
Subject: Re: [martini] #16: Extensibility to support any 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: Fri, 19 Mar 2010 11:50:10 -0000

--0015174762f09f193e048225f3b1
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

This is not a duplicate. Please justify your action.

BR,
/Hans Erik van Elburg

On Fri, Mar 19, 2010 at 12:35 PM, martini issue tracker <trac@tools.ietf.or=
g
> wrote:

> #16: Extensibility to support any AOR
>
> -------------------------------------+-----------------------------------=
---
>  Reporter:  ietf.hanserik@=85          |        Owner:
>      Type:  enhancement              |       Status:  closed
>  Priority:  critical                 |    Milestone:  milestone1
> Component:  reqs                     |      Version:  1.0
>  Severity:  In WG Last Call          |   Resolution:  duplicate
>  Keywords:                           |
>
> -------------------------------------+-----------------------------------=
---
> Changes (by bernard_aboba@=85):
>
>  * status:  new =3D> closed
>  * resolution:  =3D> duplicate
>
>
> Comment:
>
>  This is duplicate of Issue #6.
>
> --
> Ticket URL: <
> http://trac.tools.ietf.org/wg/martini/trac/ticket/16#comment:1>
> martini <http://tools.ietf.org/martini/>
>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>

--0015174762f09f193e048225f3b1
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

This is not a duplicate. Please justify your action.<br><br>BR,<br clear=3D=
"all">/Hans Erik van Elburg<br><br><div class=3D"gmail_quote">On Fri, Mar 1=
9, 2010 at 12:35 PM, martini issue tracker <span dir=3D"ltr">&lt;<a href=3D=
"mailto:trac@tools.ietf.org">trac@tools.ietf.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class=3D"im"=
>#16: Extensibility to support any AOR<br>
-------------------------------------+-------------------------------------=
-<br>
=A0Reporter: =A0ietf.hanserik@=85 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0Owner=
:<br>
</div> =A0 =A0 Type: =A0enhancement =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =
=A0 Status: =A0closed<br>
<div class=3D"im">=A0Priority: =A0critical =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
| =A0 =A0Milestone: =A0milestone1<br>
Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 =A0Ver=
sion: =A01.0<br>
</div>=A0Severity: =A0In WG Last Call =A0 =A0 =A0 =A0 =A0| =A0 Resolution: =
=A0duplicate<br>
=A0Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
-------------------------------------+-------------------------------------=
-<br>
Changes (by bernard_aboba@=85):<br>
<br>
 =A0* status: =A0new =3D&gt; closed<br>
 =A0* resolution: =A0=3D&gt; duplicate<br>
<br>
<br>
Comment:<br>
<br>
=A0This is duplicate of Issue #6.<br>
<br>
--<br>
Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticke=
t/16#comment:1" target=3D"_blank">http://trac.tools.ietf.org/wg/martini/tra=
c/ticket/16#comment:1</a>&gt;<br>
<div class=3D"im">martini &lt;<a href=3D"http://tools.ietf.org/martini/" ta=
rget=3D"_blank">http://tools.ietf.org/martini/</a>&gt;<br>
<br>
</div>_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
</blockquote></div><br>

--0015174762f09f193e048225f3b1--

From trac@tools.ietf.org  Fri Mar 19 04:57:49 2010
Return-Path: <trac@tools.ietf.org>
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 B78003A67AF for <martini@core3.amsl.com>; Fri, 19 Mar 2010 04:57:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.126
X-Spam-Level: 
X-Spam-Status: No, score=-101.126 tagged_above=-999 required=5 tests=[AWL=-1.145, BAYES_05=-1.11, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 YFpg40YOqtGe for <martini@core3.amsl.com>; Fri, 19 Mar 2010 04:57:49 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 22DA43A63C9 for <martini@ietf.org>; Fri, 19 Mar 2010 04:57:49 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nsaq1-0000T9-V7; Fri, 19 Mar 2010 04:58:02 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: martini
Date: Fri, 19 Mar 2010 11:58:01 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/17#comment:1
Message-ID: <074.57293cfb84fbc56fdd2f994ae9c92237@tools.ietf.org>
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org>
X-Trac-Ticket-ID: 17
In-Reply-To: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #17: Desirable to align with existing standards
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Fri, 19 Mar 2010 11:57:49 -0000

#17: Desirable to align with existing standards
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |        Owner:            
     Type:  enhancement              |       Status:  closed    
 Priority:  major                    |    Milestone:  milestone1
Component:  reqs                     |      Version:  1.0       
 Severity:  In WG Last Call          |   Resolution:  invalid   
 Keywords:                           |  
-------------------------------------+--------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => invalid


Comment:

 The requirements document notes the issues with existing practices.  There
 are multiple mechanisms already deployed, and each mechanism has one or
 more issues.

 Since it is not possible to simultaneously adopt existing practices
 verbatim and to address the issues with them, the major question is about
 how MARTINI solutions will deviate from existing practice.

 Saying that the solution SHOULD be aligned with existing practice places
 no useful constraints on the solution.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/17#comment:1>
martini <http://tools.ietf.org/martini/>


From ietf.hanserik@gmail.com  Fri Mar 19 05:02:07 2010
Return-Path: <ietf.hanserik@gmail.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 0FE743A68D8 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 05:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level: 
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[AWL=-0.190, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 yo3gUUxYn4i7 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 05:02:03 -0700 (PDT)
Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216]) by core3.amsl.com (Postfix) with ESMTP id CB7443A6800 for <martini@ietf.org>; Fri, 19 Mar 2010 05:02:02 -0700 (PDT)
Received: by ewy8 with SMTP id 8so1665142ewy.28 for <martini@ietf.org>; Fri, 19 Mar 2010 05:02:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=leMQm9zkhCrgqk7QSEXwL7HKAvNKZlcaBI19je8Ebfc=; b=JZVP+5svuBPDTaAmGVtKAtlpMlNoAhydyXH7wt5sKq92vHzbyypF3n0l6UymI9iEcW nhuCPb+qHDilJ4WCFWnPAFIIGvT/w9p9H/dL5oOweB3+CF14kWHRxWyJgqpyoSr+//UT o/H+4JHqUy003GKtEtE0nA1RIehw7cGRXllEg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QDJFF2F4q1efAmBU/kudXeGr18ZoytgvZbAE2eMs1Trb9SI4U9z8RAAeMgpv8LH0vZ 7b61NnMeHYwbDTW3KSll/d9Ih5nr/y0tx7uC+AF6t4YBSKJqingrP4xcsppI0Sbl54cB AhZsQ0KkHxfhrDI4amUJT9kuJ8Hyf1MomPOBQ=
MIME-Version: 1.0
Received: by 10.213.2.79 with SMTP id 15mr834875ebi.96.1269000131618; Fri, 19  Mar 2010 05:02:11 -0700 (PDT)
In-Reply-To: <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net>
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net>
Date: Fri, 19 Mar 2010 13:02:11 +0100
Message-ID: <9ae56b1e1003190502r26359206rf5bcb481addd8d20@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Content-Type: multipart/alternative; boundary=00151747681810a75b0482261e5a
Cc: "trac@localhost.amsl.com" <trac@localhost.amsl.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #15: support for non E.164 numbers
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: Fri, 19 Mar 2010 12:02:07 -0000

--00151747681810a75b0482261e5a
Content-Type: text/plain; charset=ISO-8859-1

Again the question is not how such requests reach the SSP, the question is
how given that such requests are handled by the SSP such can be delivered to
an IP-PBX to which they are assigned.

The point is that an SSP may have more complete enterprise offering that
would require calls to be delivered via the SSP cloud to enterprise private
numbers that do not have a DID E.164 number, but which are assigned to a
PBX. Such private numbers are completely under control of the enterprise and
do not require reservation of E.164 for no good reason.

The current solution should not prohibit such service offerings and I
haven't seen a good reason why this should not be covered.

#16 is a different topic.

/Hans Erik van Elburg


On Fri, Mar 19, 2010 at 11:55 AM, Elwell, John <
john.elwell@siemens-enterprise.com> wrote:

> As an individual, I don't see an urgent need to solve this in the initial
> phase. Present deployments use fully-qualified E.164 numbers (or numbers
> that can be turned into fully-qualified E.164 numbers), and it is for these
> deployments that we urgently need a standard on which to converge. Support
> for non-E.164-based (private numbers) might be nice to have, but not
> essential.
>
> I guess an important point is whether these non-E.164 numbers are globally
> unique (as a result of a phone-context parameter), in which case they might
> be easier to accommodate, but even then I am not sure. If I have a telephone
> number in the form tel:1234;phone-context=pbx.com, how does this get
> routed to ssp.com in order to get onward-routed to the PBX? It might work
> if you start off with sip:1234;phone-context=pbx.com@ssp.com;user=phone,
> but how would the calling UA construct such a URI in the first place (unless
> returning a received URI)?
>
> It seems to me that considerations are similar to non-number-based SIP
> URIs, and therefore this should be treated in the same way as #16 (depending
> on what we decide for that - see my recommendation in my previous email).
>
> John
>
>
> > -----Original Message-----
> > From: martini-bounces@ietf.org
> > [mailto:martini-bounces@ietf.org] On Behalf Of martini issue tracker
> > Sent: 18 March 2010 22:03
> > To: ietf.hanserik@gmail.com
> > Cc: martini@ietf.org
> > Subject: [martini] #15: support for non E.164 numbers
> >
> > #15: support for non E.164 numbers
> > -------------------------------------+------------------------
> > --------------
> >  Reporter:  ietf.hanserik@...          |       Owner:
> >      Type:  defect                   |      Status:  new
> >  Priority:  critical                 |   Milestone:  milestone1
> > Component:  reqs                     |     Version:  1.0
> >  Severity:  In WG Last Call          |    Keywords:
> > -------------------------------------+------------------------
> > --------------
> >  REQ19 - The mechanism MUST allow a set of assigned telephone
> > numbers to
> >  comprise local numbers as specified in RFC3966, which can be in
> >  contiguous ranges, discrete, or in any combination of the two.
> >
> > --
> > Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/15>
> > martini <http://tools.ietf.org/martini/>
> >
> > _______________________________________________
> > martini mailing list
> > martini@ietf.org
> > https://www.ietf.org/mailman/listinfo/martini
> >

--00151747681810a75b0482261e5a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Again the question is not how such requests reach the SSP, the question is =
how given that such requests are handled by the SSP such can be delivered t=
o an IP-PBX to which they are assigned.<br><br>The point is that an SSP may=
 have more complete enterprise offering that would require calls to be deli=
vered via the SSP cloud to enterprise private numbers that do not have a DI=
D E.164 number, but which are assigned to a PBX. Such private numbers are c=
ompletely under control of the enterprise and do not require reservation of=
 E.164 for no good reason.<br>
<br>The current solution should not prohibit such service offerings and I h=
aven&#39;t seen a good reason why this should not be covered.<br><br>#16 is=
 a different topic. <br><br clear=3D"all">/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Fri, Mar 19, 2010 at 11:55 AM, Elwell=
, John <span dir=3D"ltr">&lt;<a href=3D"mailto:john.elwell@siemens-enterpri=
se.com">john.elwell@siemens-enterprise.com</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left:=
 1px solid rgb(204, 204, 204); padding-left: 1ex;">
As an individual, I don&#39;t see an urgent need to solve this in the initi=
al phase. Present deployments use fully-qualified E.164 numbers (or numbers=
 that can be turned into fully-qualified E.164 numbers), and it is for thes=
e deployments that we urgently need a standard on which to converge. Suppor=
t for non-E.164-based (private numbers) might be nice to have, but not esse=
ntial.<br>

<br>
I guess an important point is whether these non-E.164 numbers are globally =
unique (as a result of a phone-context parameter), in which case they might=
 be easier to accommodate, but even then I am not sure. If I have a telepho=
ne number in the form tel:1234;phone-context=3D<a href=3D"http://pbx.com" t=
arget=3D"_blank">pbx.com</a>, how does this get routed to <a href=3D"http:/=
/ssp.com" target=3D"_blank">ssp.com</a> in order to get onward-routed to th=
e PBX? It might work if you start off with sip:1234;phone-context=3D<a href=
=3D"http://pbx.com" target=3D"_blank">pbx.com</a>@<a href=3D"http://ssp.com=
" target=3D"_blank">ssp.com</a>;user=3Dphone, but how would the calling UA =
construct such a URI in the first place (unless returning a received URI)?<=
br>

<br>
It seems to me that considerations are similar to non-number-based SIP URIs=
, and therefore this should be treated in the same way as #16 (depending on=
 what we decide for that - see my recommendation in my previous email).<br>

<br>
John<br>
<div><div></div><div class=3D"h5"><br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:martini-bounces@ietf.org">martini-bounces@ietf=
.org</a><br>
&gt; [mailto:<a href=3D"mailto:martini-bounces@ietf.org">martini-bounces@ie=
tf.org</a>] On Behalf Of martini issue tracker<br>
&gt; Sent: 18 March 2010 22:03<br>
&gt; To: <a href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com=
</a><br>
&gt; Cc: <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; Subject: [martini] #15: support for non E.164 numbers<br>
&gt;<br>
&gt; #15: support for non E.164 numbers<br>
&gt; -------------------------------------+------------------------<br>
&gt; --------------<br>
&gt; =A0Reporter: =A0ietf.hanserik@... =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0 Own=
er:<br>
&gt; =A0 =A0 =A0Type: =A0defect =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =
=A0 =A0Status: =A0new<br>
&gt; =A0Priority: =A0critical =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 Milesto=
ne: =A0milestone1<br>
&gt; Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 V=
ersion: =A01.0<br>
&gt; =A0Severity: =A0In WG Last Call =A0 =A0 =A0 =A0 =A0| =A0 =A0Keywords:<=
br>
&gt; -------------------------------------+------------------------<br>
&gt; --------------<br>
&gt; =A0REQ19 - The mechanism MUST allow a set of assigned telephone<br>
&gt; numbers to<br>
&gt; =A0comprise local numbers as specified in RFC3966, which can be in<br>
&gt; =A0contiguous ranges, discrete, or in any combination of the two.<br>
&gt;<br>
&gt; --<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/trac/=
ticket/15" target=3D"_blank">http://trac.tools.ietf.org/wg/martini/trac/tic=
ket/15</a>&gt;<br>
&gt; martini &lt;<a href=3D"http://tools.ietf.org/martini/" target=3D"_blan=
k">http://tools.ietf.org/martini/</a>&gt;<br>
&gt;<br>
</div></div>&gt; _______________________________________________<br>
&gt; martini mailing list<br>
&gt; <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/martini</a><br>
&gt; </blockquote></div><br>

--00151747681810a75b0482261e5a--

From trac@tools.ietf.org  Fri Mar 19 05:06:03 2010
Return-Path: <trac@tools.ietf.org>
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 B161C3A68B6 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 05:06:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.917
X-Spam-Level: 
X-Spam-Status: No, score=-100.917 tagged_above=-999 required=5 tests=[AWL=-1.306, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 5znPvzSj2YgI for <martini@core3.amsl.com>; Fri, 19 Mar 2010 05:06:02 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 237BA3A67AF for <martini@ietf.org>; Fri, 19 Mar 2010 05:06:00 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nsaxx-0000nt-6a; Fri, 19 Mar 2010 05:06:13 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: martini
Date: Fri, 19 Mar 2010 12:06:13 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/16#comment:2
Message-ID: <074.0008df581ff44c897b7cb7909e0c3e7d@tools.ietf.org>
References: <065.111f925a59a8643c429a6e1e5e86d2da@tools.ietf.org>
X-Trac-Ticket-ID: 16
In-Reply-To: <065.111f925a59a8643c429a6e1e5e86d2da@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #16: Extensibility to support any AOR
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Fri, 19 Mar 2010 12:06:03 -0000

#16: Extensibility to support any AOR
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |        Owner:            
     Type:  enhancement              |       Status:  reopened  
 Priority:  critical                 |    Milestone:  milestone1
Component:  reqs                     |      Version:  1.0       
 Severity:  In WG Last Call          |   Resolution:            
 Keywords:                           |  
-------------------------------------+--------------------------------------
Changes (by bernard_aboba@…):

  * status:  closed => reopened
  * resolution:  duplicate =>


Comment:

 This issue is different from #6 in that it formulates a design goal that
 the solution must not inhibit using the same mechanism for non number
 AOR's.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/16#comment:2>
martini <http://tools.ietf.org/martini/>


From ietf.hanserik@gmail.com  Fri Mar 19 05:14:07 2010
Return-Path: <ietf.hanserik@gmail.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 991FA3A69E7 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 05:14:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.147
X-Spam-Level: 
X-Spam-Status: No, score=-1.147 tagged_above=-999 required=5 tests=[AWL=0.321,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 woAizaAMZ0j1 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 05:14:06 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by core3.amsl.com (Postfix) with ESMTP id C97563A6975 for <martini@ietf.org>; Fri, 19 Mar 2010 05:14:05 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 4so269395eyf.51 for <martini@ietf.org>; Fri, 19 Mar 2010 05:14:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=W2so0+5BrhkTuB6jrx301ZJAkfIfXOCNlyifVWU7o+c=; b=H5AkQnYbkzPTuzHrNO2xS6ZPiPXquV6IWXPduvSE4bk3fugdiu5AlEYBBiyuYRkpNl QpMVQSYrCntyFPO/u4U+W8a3NZfOUJnEVT3fPAGw7o6M6U4j5OZA0wHDZ6Szu852NuWu P15c1gFeIEH60jcW67dCTb/NHTIQv+6u+lKSU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=UFNAicPH2h0ir0fb1P+KEf3c4hvT1TWOx2TlVBriHtDiOcT3haXf85aS5pOJPoQGy7 53e7ucdDLquQQ/jmC3+7WF8iWXw1541cblE8YbEP+fgcGwoS6IVf/9PraYRfjfWd+faH J+LNx/ep4DLtm7rTErVMR4cZIrmLCG03Cs8ow=
MIME-Version: 1.0
Received: by 10.213.34.79 with HTTP; Fri, 19 Mar 2010 05:14:14 -0700 (PDT)
In-Reply-To: <074.57293cfb84fbc56fdd2f994ae9c92237@tools.ietf.org>
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org> <074.57293cfb84fbc56fdd2f994ae9c92237@tools.ietf.org>
Date: Fri, 19 Mar 2010 13:14:14 +0100
Received: by 10.213.54.147 with SMTP id q19mr403714ebg.12.1269000854065; Fri,  19 Mar 2010 05:14:14 -0700 (PDT)
Message-ID: <9ae56b1e1003190514h2c64c052g4137895172b0f6f1@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: trac@localhost.amsl.com
Content-Type: multipart/alternative; boundary=00c09ffb588e206acb0482264916
Cc: bernard_aboba@hotmail.com, martini@ietf.org
Subject: Re: [martini] #17: Desirable to align with existing standards
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: Fri, 19 Mar 2010 12:14:07 -0000

--00c09ffb588e206acb0482264916
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Understood. Still think that it would be good if the different fora talk to
eachother, for the good of industry. Aligning does not mean "adopt" it migh=
t
require some changes on both sides.

In that case: "DES4 - The mechanism SHOULD require relatively modest change=
s
to a substantial population of existing SSP and SIP-PBX implementations, in
order to encourage a fast market adoption of the standardized mechanism. "

Is equally or even more problematic as " require relatively modest changes
to a substantial population of existing SSP and SIP-PBX implementations"
can't be qualified and is highly problematic.  I can raise a TRAC issue to
remove that?

BR,
/Hans Erik van Elburg

On Fri, Mar 19, 2010 at 12:58 PM, martini issue tracker <trac@tools.ietf.or=
g
> wrote:

> #17: Desirable to align with existing standards
>
> -------------------------------------+-----------------------------------=
---
>  Reporter:  ietf.hanserik@=85          |        Owner:
>      Type:  enhancement              |       Status:  closed
>  Priority:  major                    |    Milestone:  milestone1
> Component:  reqs                     |      Version:  1.0
>  Severity:  In WG Last Call          |   Resolution:  invalid
>  Keywords:                           |
>
> -------------------------------------+-----------------------------------=
---
> Changes (by bernard_aboba@=85):
>
>  * status:  new =3D> closed
>  * resolution:  =3D> invalid
>
>
> Comment:
>
>  The requirements document notes the issues with existing practices.  The=
re
>  are multiple mechanisms already deployed, and each mechanism has one or
>  more issues.
>
>  Since it is not possible to simultaneously adopt existing practices
>  verbatim and to address the issues with them, the major question is abou=
t
>  how MARTINI solutions will deviate from existing practice.
>
>  Saying that the solution SHOULD be aligned with existing practice places
>  no useful constraints on the solution.
>
> --
> Ticket URL: <
> http://trac.tools.ietf.org/wg/martini/trac/ticket/17#comment:1>
> martini <http://tools.ietf.org/martini/>
>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>

--00c09ffb588e206acb0482264916
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Understood. Still think that it would be good if the different fora talk to=
 eachother, for the good of industry. Aligning does not mean &quot;adopt&qu=
ot; it might require some changes on both sides.<br><br>In that case: &quot=
;DES4 - The mechanism SHOULD require relatively modest changes to a    subs=
tantial population of existing SSP and SIP-PBX implementations, in order to=
 encourage a fast market adoption of the standardized mechanism. &quot;<br>
<br>Is equally or even more problematic as &quot; require relatively modest=
 changes to a    substantial population of=20
existing SSP and SIP-PBX implementations&quot; can&#39;t be qualified and i=
s highly problematic.=A0 I can raise a TRAC issue to remove that?<br><br>BR=
,<br clear=3D"all">/Hans Erik van Elburg<br>
<br><div class=3D"gmail_quote">On Fri, Mar 19, 2010 at 12:58 PM, martini is=
sue tracker <span dir=3D"ltr">&lt;<a href=3D"mailto:trac@tools.ietf.org">tr=
ac@tools.ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, =
204); padding-left: 1ex;">
<div class=3D"im">#17: Desirable to align with existing standards<br>
-------------------------------------+-------------------------------------=
-<br>
=A0Reporter: =A0ietf.hanserik@=85 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0Owner=
:<br>
</div> =A0 =A0 Type: =A0enhancement =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =
=A0 Status: =A0closed<br>
<div class=3D"im">=A0Priority: =A0major =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0| =A0 =A0Milestone: =A0milestone1<br>
Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 =A0Ver=
sion: =A01.0<br>
</div>=A0Severity: =A0In WG Last Call =A0 =A0 =A0 =A0 =A0| =A0 Resolution: =
=A0invalid<br>
=A0Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
-------------------------------------+-------------------------------------=
-<br>
Changes (by bernard_aboba@=85):<br>
<br>
 =A0* status: =A0new =3D&gt; closed<br>
 =A0* resolution: =A0=3D&gt; invalid<br>
<br>
<br>
Comment:<br>
<br>
=A0The requirements document notes the issues with existing practices. =A0T=
here<br>
=A0are multiple mechanisms already deployed, and each mechanism has one or<=
br>
=A0more issues.<br>
<br>
=A0Since it is not possible to simultaneously adopt existing practices<br>
=A0verbatim and to address the issues with them, the major question is abou=
t<br>
=A0how MARTINI solutions will deviate from existing practice.<br>
<br>
=A0Saying that the solution SHOULD be aligned with existing practice places=
<br>
=A0no useful constraints on the solution.<br>
<font color=3D"#888888"><br>
--<br>
Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticke=
t/17#comment:1" target=3D"_blank">http://trac.tools.ietf.org/wg/martini/tra=
c/ticket/17#comment:1</a>&gt;<br>
</font><div class=3D"im">martini &lt;<a href=3D"http://tools.ietf.org/marti=
ni/" target=3D"_blank">http://tools.ietf.org/martini/</a>&gt;<br>
<br>
</div><div><div></div><div class=3D"h5">___________________________________=
____________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
</div></div></blockquote></div><br>

--00c09ffb588e206acb0482264916--

From bernard_aboba@hotmail.com  Fri Mar 19 05:39:03 2010
Return-Path: <bernard_aboba@hotmail.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 055783A68FC for <martini@core3.amsl.com>; Fri, 19 Mar 2010 05:39:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.156
X-Spam-Level: 
X-Spam-Status: No, score=0.156 tagged_above=-999 required=5 tests=[AWL=-0.976,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 ho+spPovegBt for <martini@core3.amsl.com>; Fri, 19 Mar 2010 05:39:01 -0700 (PDT)
Received: from blu0-omc2-s6.blu0.hotmail.com (blu0-omc2-s6.blu0.hotmail.com [65.55.111.81]) by core3.amsl.com (Postfix) with ESMTP id B9FDF3A6906 for <martini@ietf.org>; Fri, 19 Mar 2010 05:39:01 -0700 (PDT)
Received: from BLU137-W19 ([65.55.111.73]) by blu0-omc2-s6.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 19 Mar 2010 05:39:14 -0700
Message-ID: <BLU137-W1914DD465AF564F5D1BA80932A0@phx.gbl>
Content-Type: multipart/alternative; boundary="_2676962d-12c0-43a6-a3f2-c8208c8d0485_"
X-Originating-IP: [76.108.77.56]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <ietf.hanserik@gmail.com>
Date: Fri, 19 Mar 2010 05:39:14 -0700
Importance: Normal
In-Reply-To: <9ae56b1e1003190514h2c64c052g4137895172b0f6f1@mail.gmail.com>
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org>, <074.57293cfb84fbc56fdd2f994ae9c92237@tools.ietf.org>, <9ae56b1e1003190514h2c64c052g4137895172b0f6f1@mail.gmail.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 19 Mar 2010 12:39:14.0281 (UTC) FILETIME=[2EB46590:01CAC761]
Cc: martini@ietf.org
Subject: Re: [martini] #17: Desirable to align with existing standards
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: Fri, 19 Mar 2010 12:39:03 -0000

--_2676962d-12c0-43a6-a3f2-c8208c8d0485_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


Ideally=2C requirements should be things that we can evaluate a solution ag=
ainst in a straightforward way.=20

Whether a solution would require modest or major changes to a given impleme=
ntation can vary based on the implementation=2C so determining whether a gi=
ven solution meets the "modest change" requirement could be difficult to do=
 in an objective way.

My suggestion is that we reformulate this to be more specific.  One way to =
do this would be to have further discussion about problems that would be co=
nsidered "deal breakers" for SSPs.  Issues that have already been brought u=
p are things like compatibility with path=2C outbound=2C etc.   These are e=
asier to evaluate (e.g. we can require a solution to demonstrate how it wou=
ld work with path).=20

Date: Fri=2C 19 Mar 2010 13:14:14 +0100
Subject: Re: [martini] #17: Desirable to align with existing standards
From: ietf.hanserik@gmail.com
To: trac@localhost.amsl.com
CC: bernard_aboba@hotmail.com=3B martini@ietf.org

Understood. Still think that it would be good if the different fora talk to=
 eachother=2C for the good of industry. Aligning does not mean "adopt" it m=
ight require some changes on both sides.

In that case: "DES4 - The mechanism SHOULD require relatively modest change=
s to a    substantial population of existing SSP and SIP-PBX implementation=
s=2C in order to encourage a fast market adoption of the standardized mecha=
nism. "


Is equally or even more problematic as " require relatively modest changes =
to a    substantial population of=20
existing SSP and SIP-PBX implementations" can't be qualified and is highly =
problematic.  I can raise a TRAC issue to remove that?

BR=2C/Hans Erik van Elburg


On Fri=2C Mar 19=2C 2010 at 12:58 PM=2C martini issue tracker <trac@tools.i=
etf.org> wrote:

#17: Desirable to align with existing standards

-------------------------------------+-------------------------------------=
-

 Reporter:  ietf.hanserik@=85          |        Owner:

     Type:  enhancement              |       Status:  closed

 Priority:  major                    |    Milestone:  milestone1

Component:  reqs                     |      Version:  1.0

 Severity:  In WG Last Call          |   Resolution:  invalid

 Keywords:                           |

-------------------------------------+-------------------------------------=
-

Changes (by bernard_aboba@=85):



  * status:  new =3D> closed

  * resolution:  =3D> invalid





Comment:



 The requirements document notes the issues with existing practices.  There

 are multiple mechanisms already deployed=2C and each mechanism has one or

 more issues.



 Since it is not possible to simultaneously adopt existing practices

 verbatim and to address the issues with them=2C the major question is abou=
t

 how MARTINI solutions will deviate from existing practice.



 Saying that the solution SHOULD be aligned with existing practice places

 no useful constraints on the solution.



--

Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/17#comment:1=
>

martini <http://tools.ietf.org/martini/>



_______________________________________________

martini mailing list

martini@ietf.org

https://www.ietf.org/mailman/listinfo/martini


 		 	   		  =

--_2676962d-12c0-43a6-a3f2-c8208c8d0485_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
Ideally=2C requirements should be things that we can evaluate a solution ag=
ainst in a straightforward way. <br><br>Whether a solution would require mo=
dest or major changes to a given implementation can vary based on the imple=
mentation=2C so determining whether a given solution meets the "modest chan=
ge" requirement could be difficult to do in an objective way.<br><br>My sug=
gestion is that we reformulate this to be more specific.&nbsp=3B One way to=
 do this would be to have further discussion about problems that would be c=
onsidered "deal breakers" for SSPs.&nbsp=3B Issues that have already been b=
rought up are things like compatibility with path=2C outbound=2C etc.&nbsp=
=3B&nbsp=3B These are easier to evaluate (e.g. we can require a solution to=
 demonstrate how it would work with path). <br><br><hr id=3D"stopSpelling">=
Date: Fri=2C 19 Mar 2010 13:14:14 +0100<br>Subject: Re: [martini] #17: Desi=
rable to align with existing standards<br>From: ietf.hanserik@gmail.com<br>=
To: trac@localhost.amsl.com<br>CC: bernard_aboba@hotmail.com=3B martini@iet=
f.org<br><br>Understood. Still think that it would be good if the different=
 fora talk to eachother=2C for the good of industry. Aligning does not mean=
 "adopt" it might require some changes on both sides.<br><br>In that case: =
"DES4 - The mechanism SHOULD require relatively modest changes to a    subs=
tantial population of existing SSP and SIP-PBX implementations=2C in order =
to encourage a fast market adoption of the standardized mechanism. "<br>
<br>Is equally or even more problematic as " require relatively modest chan=
ges to a    substantial population of=20
existing SSP and SIP-PBX implementations" can't be qualified and is highly =
problematic.&nbsp=3B I can raise a TRAC issue to remove that?<br><br>BR=2C<=
br clear=3D"all">/Hans Erik van Elburg<br>
<br><div class=3D"ecxgmail_quote">On Fri=2C Mar 19=2C 2010 at 12:58 PM=2C m=
artini issue tracker <span dir=3D"ltr">&lt=3B<a>trac@tools.ietf.org</a>&gt=
=3B</span> wrote:<br><blockquote class=3D"ecxgmail_quote" style=3D"padding-=
left: 1ex=3B">
<div class=3D"ecxim">#17: Desirable to align with existing standards<br>
-------------------------------------+-------------------------------------=
-<br>
&nbsp=3BReporter: &nbsp=3Bietf.hanserik@=85 &nbsp=3B &nbsp=3B &nbsp=3B &nbs=
p=3B &nbsp=3B| &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3BOwner:<br>
</div> &nbsp=3B &nbsp=3B Type: &nbsp=3Benhancement &nbsp=3B &nbsp=3B &nbsp=
=3B &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3B| &nbsp=3B &nbsp=3B &nbsp=3B Status:=
 &nbsp=3Bclosed<br>
<div class=3D"ecxim">&nbsp=3BPriority: &nbsp=3Bmajor &nbsp=3B &nbsp=3B &nbs=
p=3B &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3B| &nbsp=
=3B &nbsp=3BMilestone: &nbsp=3Bmilestone1<br>
Component: &nbsp=3Breqs &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=
=3B &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3B | &nbsp=3B &nbsp=3B &nbsp=3BVersion=
: &nbsp=3B1.0<br>
</div>&nbsp=3BSeverity: &nbsp=3BIn WG Last Call &nbsp=3B &nbsp=3B &nbsp=3B =
&nbsp=3B &nbsp=3B| &nbsp=3B Resolution: &nbsp=3Binvalid<br>
&nbsp=3BKeywords: &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3B &nb=
sp=3B &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3B &nbsp=3B |<br>
-------------------------------------+-------------------------------------=
-<br>
Changes (by bernard_aboba@=85):<br>
<br>
 &nbsp=3B* status: &nbsp=3Bnew =3D&gt=3B closed<br>
 &nbsp=3B* resolution: &nbsp=3B=3D&gt=3B invalid<br>
<br>
<br>
Comment:<br>
<br>
&nbsp=3BThe requirements document notes the issues with existing practices.=
 &nbsp=3BThere<br>
&nbsp=3Bare multiple mechanisms already deployed=2C and each mechanism has =
one or<br>
&nbsp=3Bmore issues.<br>
<br>
&nbsp=3BSince it is not possible to simultaneously adopt existing practices=
<br>
&nbsp=3Bverbatim and to address the issues with them=2C the major question =
is about<br>
&nbsp=3Bhow MARTINI solutions will deviate from existing practice.<br>
<br>
&nbsp=3BSaying that the solution SHOULD be aligned with existing practice p=
laces<br>
&nbsp=3Bno useful constraints on the solution.<br>
<font color=3D"#888888"><br>
--<br>
Ticket URL: &lt=3B<a>http://trac.tools.ietf.org/wg/martini/trac/ticket/17#c=
omment:1</a>&gt=3B<br>
</font><div class=3D"ecxim">martini &lt=3B<a>http://tools.ietf.org/martini/=
</a>&gt=3B<br>
<br>
</div><div><div></div><div class=3D"h5">___________________________________=
____________<br>
martini mailing list<br>
<a>martini@ietf.org</a><br>
<a>https://www.ietf.org/mailman/listinfo/martini</a><br>
</div></div></blockquote></div><br> 		 	   		  </body>
</html>=

--_2676962d-12c0-43a6-a3f2-c8208c8d0485_--

From ietf.hanserik@gmail.com  Fri Mar 19 05:51:50 2010
Return-Path: <ietf.hanserik@gmail.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 047683A6835 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 05:51:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.898
X-Spam-Level: 
X-Spam-Status: No, score=-0.898 tagged_above=-999 required=5 tests=[AWL=-0.919, BAYES_05=-1.11, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 qZptrEw2vuA0 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 05:51:49 -0700 (PDT)
Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216]) by core3.amsl.com (Postfix) with ESMTP id 84FC23A67A2 for <martini@ietf.org>; Fri, 19 Mar 2010 05:51:48 -0700 (PDT)
Received: by ewy8 with SMTP id 8so1680367ewy.28 for <martini@ietf.org>; Fri, 19 Mar 2010 05:51:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=KvwIFALB75eghinBARNMyxT4t1tZ2tBzshiw8O0+OmA=; b=c29KbXSY5tqNi3MO5HbBXQxNDj+9kBCUi2jXfgThTlgrbFoS/NSP3z6Ceckrtg3sR7 WLaG02ZvnanAeRJtwcKE4q0MQoLgx8LWEiCv+Y2gk6kRipg6cmS4vlV8YVcEeT2ubxxy eOgLl/rJvy01ZKfOqBUHm2OYmvQeJF+QwS8v8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=worymK6rW3EdqxHwt6aQXHZXbYtuQU/cKXOq2hT5LB6QcAlCTlF7hZwF7bOI6J3RJu h/Rt2byKykQFUD1+l8lDNua6bK0vootN9C+GJq5XX5FF1x97sEor0rV/4jCKRjsvt3Xj CBNA8v85PDNgGSmYsuyvnvBVpMe4x5vQMd1Co=
MIME-Version: 1.0
Received: by 10.213.103.146 with SMTP id k18mr1662122ebo.5.1269003117009; Fri,  19 Mar 2010 05:51:57 -0700 (PDT)
In-Reply-To: <BLU137-W1914DD465AF564F5D1BA80932A0@phx.gbl>
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org> <074.57293cfb84fbc56fdd2f994ae9c92237@tools.ietf.org> <9ae56b1e1003190514h2c64c052g4137895172b0f6f1@mail.gmail.com> <BLU137-W1914DD465AF564F5D1BA80932A0@phx.gbl>
Date: Fri, 19 Mar 2010 13:51:56 +0100
Message-ID: <9ae56b1e1003190551w236a056bt5aa709521bb74f5a@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Content-Type: multipart/alternative; boundary=00504502d139021f81048226d061
Cc: martini@ietf.org
Subject: Re: [martini] #17: Desirable to align with existing standards
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: Fri, 19 Mar 2010 12:51:50 -0000

--00504502d139021f81048226d061
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Looks like such reformulation would go more in the direction of actual
requirements. Analogous as the one for GRUU.

/Hans Erik van Elburg

On Fri, Mar 19, 2010 at 1:39 PM, Bernard Aboba <bernard_aboba@hotmail.com>w=
rote:

>  Ideally, requirements should be things that we can evaluate a solution
> against in a straightforward way.
>
> Whether a solution would require modest or major changes to a given
> implementation can vary based on the implementation, so determining wheth=
er
> a given solution meets the "modest change" requirement could be difficult=
 to
> do in an objective way.
>
> My suggestion is that we reformulate this to be more specific.  One way t=
o
> do this would be to have further discussion about problems that would be
> considered "deal breakers" for SSPs.  Issues that have already been broug=
ht
> up are things like compatibility with path, outbound, etc.   These are
> easier to evaluate (e.g. we can require a solution to demonstrate how it
> would work with path).
>
> ------------------------------
> Date: Fri, 19 Mar 2010 13:14:14 +0100
> Subject: Re: [martini] #17: Desirable to align with existing standards
> From: ietf.hanserik@gmail.com
> To: trac@localhost.amsl.com
> CC: bernard_aboba@hotmail.com; martini@ietf.org
>
>
> Understood. Still think that it would be good if the different fora talk =
to
> eachother, for the good of industry. Aligning does not mean "adopt" it mi=
ght
> require some changes on both sides.
>
> In that case: "DES4 - The mechanism SHOULD require relatively modest
> changes to a substantial population of existing SSP and SIP-PBX
> implementations, in order to encourage a fast market adoption of the
> standardized mechanism. "
>
> Is equally or even more problematic as " require relatively modest change=
s
> to a substantial population of existing SSP and SIP-PBX implementations"
> can't be qualified and is highly problematic.  I can raise a TRAC issue t=
o
> remove that?
>
> BR,
> /Hans Erik van Elburg
>
> On Fri, Mar 19, 2010 at 12:58 PM, martini issue tracker <
> trac@tools.ietf.org> wrote:
>
> #17: Desirable to align with existing standards
>
> -------------------------------------+-----------------------------------=
---
>  Reporter:  ietf.hanserik@=85          |        Owner:
>      Type:  enhancement              |       Status:  closed
>  Priority:  major                    |    Milestone:  milestone1
> Component:  reqs                     |      Version:  1.0
>  Severity:  In WG Last Call          |   Resolution:  invalid
>  Keywords:                           |
>
> -------------------------------------+-----------------------------------=
---
> Changes (by bernard_aboba@=85):
>
>  * status:  new =3D> closed
>  * resolution:  =3D> invalid
>
>
> Comment:
>
>  The requirements document notes the issues with existing practices.  The=
re
>  are multiple mechanisms already deployed, and each mechanism has one or
>  more issues.
>
>  Since it is not possible to simultaneously adopt existing practices
>  verbatim and to address the issues with them, the major question is abou=
t
>  how MARTINI solutions will deviate from existing practice.
>
>  Saying that the solution SHOULD be aligned with existing practice places
>  no useful constraints on the solution.
>
> --
> Ticket URL: <
> http://trac.tools.ietf.org/wg/martini/trac/ticket/17#comment:1>
> martini <http://tools.ietf.org/martini/>
>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>
>
>

--00504502d139021f81048226d061
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Looks like such reformulation would go more in the direction of actual requ=
irements. Analogous as the one for GRUU.<br><br clear=3D"all">/Hans Erik va=
n Elburg<br>
<br><div class=3D"gmail_quote">On Fri, Mar 19, 2010 at 1:39 PM, Bernard Abo=
ba <span dir=3D"ltr">&lt;<a href=3D"mailto:bernard_aboba@hotmail.com">berna=
rd_aboba@hotmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 20=
4, 204); padding-left: 1ex;">




<div>
Ideally, requirements should be things that we can evaluate a solution agai=
nst in a straightforward way. <br><br>Whether a solution would require mode=
st or major changes to a given implementation can vary based on the impleme=
ntation, so determining whether a given solution meets the &quot;modest cha=
nge&quot; requirement could be difficult to do in an objective way.<br>
<br>My suggestion is that we reformulate this to be more specific.=A0 One w=
ay to do this would be to have further discussion about problems that would=
 be considered &quot;deal breakers&quot; for SSPs.=A0 Issues that have alre=
ady been brought up are things like compatibility with path, outbound, etc.=
=A0=A0 These are easier to evaluate (e.g. we can require a solution to demo=
nstrate how it would work with path). <br>
<div class=3D"hm"><br><hr>Date: Fri, 19 Mar 2010 13:14:14 +0100<br>Subject:=
 Re: [martini] #17: Desirable to align with existing standards<br>From: <a =
href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">ietf.hanserik@gma=
il.com</a><br>
To: <a href=3D"mailto:trac@localhost.amsl.com" target=3D"_blank">trac@local=
host.amsl.com</a><br>CC: <a href=3D"mailto:bernard_aboba@hotmail.com" targe=
t=3D"_blank">bernard_aboba@hotmail.com</a>; <a href=3D"mailto:martini@ietf.=
org" target=3D"_blank">martini@ietf.org</a></div>
<div><div></div><div class=3D"h5"><br><br>Understood. Still think that it w=
ould be good if the different fora talk to eachother, for the good of indus=
try. Aligning does not mean &quot;adopt&quot; it might require some changes=
 on both sides.<br>
<br>In that case: &quot;DES4 - The mechanism SHOULD require relatively mode=
st changes to a    substantial population of existing SSP and SIP-PBX imple=
mentations, in order to encourage a fast market adoption of the standardize=
d mechanism. &quot;<br>

<br>Is equally or even more problematic as &quot; require relatively modest=
 changes to a    substantial population of=20
existing SSP and SIP-PBX implementations&quot; can&#39;t be qualified and i=
s highly problematic.=A0 I can raise a TRAC issue to remove that?<br><br>BR=
,<br clear=3D"all">/Hans Erik van Elburg<br>
<br><div>On Fri, Mar 19, 2010 at 12:58 PM, martini issue tracker <span dir=
=3D"ltr">&lt;<a>trac@tools.ietf.org</a>&gt;</span> wrote:<br><blockquote st=
yle=3D"padding-left: 1ex;">
<div>#17: Desirable to align with existing standards<br>
-------------------------------------+-------------------------------------=
-<br>
=A0Reporter: =A0ietf.hanserik@=85 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0Owner=
:<br>
</div> =A0 =A0 Type: =A0enhancement =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =
=A0 Status: =A0closed<br>
<div>=A0Priority: =A0major =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0=
Milestone: =A0milestone1<br>
Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 =A0Ver=
sion: =A01.0<br>
</div>=A0Severity: =A0In WG Last Call =A0 =A0 =A0 =A0 =A0| =A0 Resolution: =
=A0invalid<br>
=A0Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
-------------------------------------+-------------------------------------=
-<br>
Changes (by bernard_aboba@=85):<br>
<br>
 =A0* status: =A0new =3D&gt; closed<br>
 =A0* resolution: =A0=3D&gt; invalid<br>
<br>
<br>
Comment:<br>
<br>
=A0The requirements document notes the issues with existing practices. =A0T=
here<br>
=A0are multiple mechanisms already deployed, and each mechanism has one or<=
br>
=A0more issues.<br>
<br>
=A0Since it is not possible to simultaneously adopt existing practices<br>
=A0verbatim and to address the issues with them, the major question is abou=
t<br>
=A0how MARTINI solutions will deviate from existing practice.<br>
<br>
=A0Saying that the solution SHOULD be aligned with existing practice places=
<br>
=A0no useful constraints on the solution.<br>
<font color=3D"#888888"><br>
--<br>
Ticket URL: &lt;<a>http://trac.tools.ietf.org/wg/martini/trac/ticket/17#com=
ment:1</a>&gt;<br>
</font><div>martini &lt;<a>http://tools.ietf.org/martini/</a>&gt;<br>
<br>
</div><div><div></div><div>_______________________________________________<=
br>
martini mailing list<br>
<a>martini@ietf.org</a><br>
<a>https://www.ietf.org/mailman/listinfo/martini</a><br>
</div></div></blockquote></div><br> 		 	   		  </div></div></div>
</blockquote></div><br>

--00504502d139021f81048226d061--

From pkyzivat@cisco.com  Fri Mar 19 06:35:49 2010
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 2E1BC3A69AD for <martini@core3.amsl.com>; Fri, 19 Mar 2010 06:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.618
X-Spam-Level: 
X-Spam-Status: No, score=-9.618 tagged_above=-999 required=5 tests=[AWL=-0.149, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_HI=-8]
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 wUjBHdvNGRaG for <martini@core3.amsl.com>; Fri, 19 Mar 2010 06:35:47 -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 7FD263A68B4 for <martini@ietf.org>; Fri, 19 Mar 2010 06:35:47 -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: AvsEAK8ao0tAZnwM/2dsb2JhbACbPHOiApkNglgBgiEEjwk
X-IronPort-AV: E=Sophos;i="4.51,274,1267401600"; d="scan'208";a="94242443"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 19 Mar 2010 13:35:59 +0000
Received: from [161.44.174.156] (dhcp-161-44-174-156.cisco.com [161.44.174.156]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o2JDZxcA010199; Fri, 19 Mar 2010 13:35:59 GMT
Message-ID: <4BA37DBF.8060404@cisco.com>
Date: Fri, 19 Mar 2010 09:35:59 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "trac@localhost.amsl.com" <trac@localhost.amsl.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #15: support for non E.164 numbers
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: Fri, 19 Mar 2010 13:35:49 -0000

Jon,

I agree with you here.

Solving this in general will require coming up with an approach for 
routing local TEL URIs based on phone-context. I can think of various 
ways to do that, but fear there would be as much politics involved as 
there has been with ENUM.

	Thanks,
	Paul

Elwell, John wrote:
> As an individual, I don't see an urgent need to solve this in the initial phase. Present deployments use fully-qualified E.164 numbers (or numbers that can be turned into fully-qualified E.164 numbers), and it is for these deployments that we urgently need a standard on which to converge. Support for non-E.164-based (private numbers) might be nice to have, but not essential. 
> 
> I guess an important point is whether these non-E.164 numbers are globally unique (as a result of a phone-context parameter), in which case they might be easier to accommodate, but even then I am not sure. If I have a telephone number in the form tel:1234;phone-context=pbx.com, how does this get routed to ssp.com in order to get onward-routed to the PBX? It might work if you start off with sip:1234;phone-context=pbx.com@ssp.com;user=phone, but how would the calling UA construct such a URI in the first place (unless returning a received URI)?
> 
> It seems to me that considerations are similar to non-number-based SIP URIs, and therefore this should be treated in the same way as #16 (depending on what we decide for that - see my recommendation in my previous email).
> 
> John
> 
> 
>> -----Original Message-----
>> From: martini-bounces@ietf.org 
>> [mailto:martini-bounces@ietf.org] On Behalf Of martini issue tracker
>> Sent: 18 March 2010 22:03
>> To: ietf.hanserik@gmail.com
>> Cc: martini@ietf.org
>> Subject: [martini] #15: support for non E.164 numbers
>>
>> #15: support for non E.164 numbers
>> -------------------------------------+------------------------
>> --------------
>>  Reporter:  ietf.hanserik@...          |       Owner:            
>>      Type:  defect                   |      Status:  new       
>>  Priority:  critical                 |   Milestone:  milestone1
>> Component:  reqs                     |     Version:  1.0       
>>  Severity:  In WG Last Call          |    Keywords:            
>> -------------------------------------+------------------------
>> --------------
>>  REQ19 - The mechanism MUST allow a set of assigned telephone 
>> numbers to
>>  comprise local numbers as specified in RFC3966, which can be in
>>  contiguous ranges, discrete, or in any combination of the two.
>>
>> -- 
>> Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/15>
>> martini <http://tools.ietf.org/martini/>
>>
>> _______________________________________________
>> martini mailing list
>> martini@ietf.org
>> https://www.ietf.org/mailman/listinfo/martini
>>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
> 

From ietf.hanserik@gmail.com  Fri Mar 19 06:50:41 2010
Return-Path: <ietf.hanserik@gmail.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 A4E113A685A for <martini@core3.amsl.com>; Fri, 19 Mar 2010 06:50:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.572
X-Spam-Level: 
X-Spam-Status: No, score=-1.572 tagged_above=-999 required=5 tests=[AWL=-0.103, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 rYfmFkqdj6Rx for <martini@core3.amsl.com>; Fri, 19 Mar 2010 06:50:40 -0700 (PDT)
Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216]) by core3.amsl.com (Postfix) with ESMTP id E58FE3A6800 for <martini@ietf.org>; Fri, 19 Mar 2010 06:50:39 -0700 (PDT)
Received: by ewy8 with SMTP id 8so1699774ewy.28 for <martini@ietf.org>; Fri, 19 Mar 2010 06:50:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=6inXq9MKoYFKWxwD3hxNdPQ0JPE5LKQOPtd9v3BBe4Y=; b=uowACH1qWYj8D7hdQryg7O+ITy9TPslaZ9e6utY6Dnw5wxXsQQwiWuebMprE/0jeTu GTvXrcXbZS9TmrPrbc5z+kS9ODKdHPEs7cB7aIASemfy+fC1LIRknE8oILORjidImYAt Bm6DEvKNCSSHm8O3huttW3ZyywpYV7ZEj0AaY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=KFWjDNly0yy9SWwlV42Js7DbIEYQoS+fINEr7caxAmfvQGAYFUJP7tLj10vztDa60f X5l84WSmp0QXFOQlQ+V+FjoUtZzE9HrSPtzn09KRsc4x0mNkDhrnf/knzc/J0AMuRQKh J64rkUqi8ociKBK2mDtpVTzZlee14AjUpvqsU=
MIME-Version: 1.0
Received: by 10.213.80.65 with SMTP id s1mr577664ebk.64.1269006645421; Fri, 19  Mar 2010 06:50:45 -0700 (PDT)
In-Reply-To: <4BA37DBF.8060404@cisco.com>
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net> <4BA37DBF.8060404@cisco.com>
Date: Fri, 19 Mar 2010 14:50:45 +0100
Message-ID: <9ae56b1e1003190650s5c402e39g3aa840f31673e4c6@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Content-Type: multipart/alternative; boundary=00c09f8c1c8f516765048227a2cd
Cc: "trac@localhost.amsl.com" <trac@localhost.amsl.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #15: support for non E.164 numbers
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: Fri, 19 Mar 2010 13:50:41 -0000

--00c09f8c1c8f516765048227a2cd
Content-Type: text/plain; charset=ISO-8859-1

So the argument here goes: we don't know how local numbers would be routed
to the SSP therefore we will not allow local numbers to be delivered to
IP-PBX's by that SSP even if they only have significance within the SSP
domain and are understood by the PBX.

I can not really follow that logic. Seems like forced limitation of freedom
by design.

/Hans Erik van Elburg

On Fri, Mar 19, 2010 at 2:35 PM, Paul Kyzivat <pkyzivat@cisco.com> wrote:

> Jon,
>
> I agree with you here.
>
> Solving this in general will require coming up with an approach for routing
> local TEL URIs based on phone-context. I can think of various ways to do
> that, but fear there would be as much politics involved as there has been
> with ENUM.
>
>        Thanks,
>        Paul
>
>
> Elwell, John wrote:
>
>> As an individual, I don't see an urgent need to solve this in the initial
>> phase. Present deployments use fully-qualified E.164 numbers (or numbers
>> that can be turned into fully-qualified E.164 numbers), and it is for these
>> deployments that we urgently need a standard on which to converge. Support
>> for non-E.164-based (private numbers) might be nice to have, but not
>> essential.
>> I guess an important point is whether these non-E.164 numbers are globally
>> unique (as a result of a phone-context parameter), in which case they might
>> be easier to accommodate, but even then I am not sure. If I have a telephone
>> number in the form tel:1234;phone-context=pbx.com, how does this get
>> routed to ssp.com in order to get onward-routed to the PBX? It might work
>> if you start off with sip:1234;phone-context=pbx.com@ssp.com;user=phone,
>> but how would the calling UA construct such a URI in the first place (unless
>> returning a received URI)?
>>
>> It seems to me that considerations are similar to non-number-based SIP
>> URIs, and therefore this should be treated in the same way as #16 (depending
>> on what we decide for that - see my recommendation in my previous email).
>>
>> John
>>
>>
>>  -----Original Message-----
>>> From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On
>>> Behalf Of martini issue tracker
>>> Sent: 18 March 2010 22:03
>>> To: ietf.hanserik@gmail.com
>>> Cc: martini@ietf.org
>>> Subject: [martini] #15: support for non E.164 numbers
>>>
>>> #15: support for non E.164 numbers
>>> -------------------------------------+------------------------
>>> --------------
>>>  Reporter:  ietf.hanserik@...          |       Owner:
>>> Type:  defect                   |      Status:  new        Priority:
>>>  critical                 |   Milestone:  milestone1
>>> Component:  reqs                     |     Version:  1.0        Severity:
>>>  In WG Last Call          |    Keywords:
>>>  -------------------------------------+------------------------
>>> --------------
>>>  REQ19 - The mechanism MUST allow a set of assigned telephone numbers to
>>>  comprise local numbers as specified in RFC3966, which can be in
>>>  contiguous ranges, discrete, or in any combination of the two.
>>>
>>> --
>>> Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/15>
>>> martini <http://tools.ietf.org/martini/>
>>>
>>> _______________________________________________
>>> martini mailing list
>>> martini@ietf.org
>>> https://www.ietf.org/mailman/listinfo/martini
>>>
>>>  _______________________________________________
>> martini mailing list
>> martini@ietf.org
>> https://www.ietf.org/mailman/listinfo/martini
>>
>>

--00c09f8c1c8f516765048227a2cd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

So the argument here goes: we don&#39;t know how local numbers would be rou=
ted to the SSP therefore we will not allow local numbers to be delivered to=
 IP-PBX&#39;s by that SSP even if they only have significance within the SS=
P domain and are understood by the PBX.<br>
<br>I can not really follow that logic. Seems like forced limitation of fre=
edom by design.<br><br clear=3D"all">/Hans Erik van Elburg<br><br><div clas=
s=3D"gmail_quote">On Fri, Mar 19, 2010 at 2:35 PM, Paul Kyzivat <span dir=
=3D"ltr">&lt;<a href=3D"mailto:pkyzivat@cisco.com">pkyzivat@cisco.com</a>&g=
t;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Jon,<br>
<br>
I agree with you here.<br>
<br>
Solving this in general will require coming up with an approach for routing=
 local TEL URIs based on phone-context. I can think of various ways to do t=
hat, but fear there would be as much politics involved as there has been wi=
th ENUM.<br>

<br>
 =A0 =A0 =A0 =A0Thanks,<br><font color=3D"#888888">
 =A0 =A0 =A0 =A0Paul</font><div><div></div><div class=3D"h5"><br>
<br>
Elwell, John wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
As an individual, I don&#39;t see an urgent need to solve this in the initi=
al phase. Present deployments use fully-qualified E.164 numbers (or numbers=
 that can be turned into fully-qualified E.164 numbers), and it is for thes=
e deployments that we urgently need a standard on which to converge. Suppor=
t for non-E.164-based (private numbers) might be nice to have, but not esse=
ntial. <br>

I guess an important point is whether these non-E.164 numbers are globally =
unique (as a result of a phone-context parameter), in which case they might=
 be easier to accommodate, but even then I am not sure. If I have a telepho=
ne number in the form tel:1234;phone-context=3D<a href=3D"http://pbx.com" t=
arget=3D"_blank">pbx.com</a>, how does this get routed to <a href=3D"http:/=
/ssp.com" target=3D"_blank">ssp.com</a> in order to get onward-routed to th=
e PBX? It might work if you start off with sip:1234;phone-context=3D<a href=
=3D"http://pbx.com" target=3D"_blank">pbx.com</a>@<a href=3D"http://ssp.com=
" target=3D"_blank">ssp.com</a>;user=3Dphone, but how would the calling UA =
construct such a URI in the first place (unless returning a received URI)?<=
br>

<br>
It seems to me that considerations are similar to non-number-based SIP URIs=
, and therefore this should be treated in the same way as #16 (depending on=
 what we decide for that - see my recommendation in my previous email).<br>

<br>
John<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
-----Original Message-----<br>
From: <a href=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">martini=
-bounces@ietf.org</a> [mailto:<a href=3D"mailto:martini-bounces@ietf.org" t=
arget=3D"_blank">martini-bounces@ietf.org</a>] On Behalf Of martini issue t=
racker<br>

Sent: 18 March 2010 22:03<br>
To: <a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">ietf.hanse=
rik@gmail.com</a><br>
Cc: <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org<=
/a><br>
Subject: [martini] #15: support for non E.164 numbers<br>
<br>
#15: support for non E.164 numbers<br>
-------------------------------------+------------------------<br>
--------------<br>
=A0Reporter: =A0ietf.hanserik@... =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0 Owner: =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Type: =A0defect =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 | =A0 =A0 =A0Status: =A0new =A0 =A0 =A0 =A0Priority: =A0critical =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 Milestone: =A0milestone1<br>
Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 Versio=
n: =A01.0 =A0 =A0 =A0 =A0Severity: =A0In WG Last Call =A0 =A0 =A0 =A0 =A0| =
=A0 =A0Keywords: =A0 =A0 =A0 =A0 =A0 =A0-----------------------------------=
--+------------------------<br>
--------------<br>
=A0REQ19 - The mechanism MUST allow a set of assigned telephone numbers to<=
br>
=A0comprise local numbers as specified in RFC3966, which can be in<br>
=A0contiguous ranges, discrete, or in any combination of the two.<br>
<br>
-- <br>
Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticke=
t/15" target=3D"_blank">http://trac.tools.ietf.org/wg/martini/trac/ticket/1=
5</a>&gt;<br>
martini &lt;<a href=3D"http://tools.ietf.org/martini/" target=3D"_blank">ht=
tp://tools.ietf.org/martini/</a>&gt;<br>
<br>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
<br>
</blockquote>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
<br>
</blockquote>
</div></div></blockquote></div><br>

--00c09f8c1c8f516765048227a2cd--

From jan.van.geel@belgacom.be  Fri Mar 19 06:50:42 2010
Return-Path: <jan.van.geel@belgacom.be>
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 D43333A6800 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 06:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.576
X-Spam-Level: 
X-Spam-Status: No, score=0.576 tagged_above=-999 required=5 tests=[AWL=0.556,  BAYES_05=-1.11, DNS_FROM_OPENWHOIS=1.13]
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 RlXWHQZg3oE8 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 06:50:41 -0700 (PDT)
Received: from inmxcar01.belgacom.be (inmxcar01.belgacom.be [195.13.11.182]) by core3.amsl.com (Postfix) with ESMTP id 13A6A3A681A for <martini@ietf.org>; Fri, 19 Mar 2010 06:50:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.51,274,1267398000"; d="scan'208";a="80010326"
Received: from unknown (HELO A03007.BGC.NET) ([10.120.129.162]) by outmxcar01.belgacom.be with ESMTP; 19 Mar 2010 14:50:33 +0100
X-TM-IMSS-Message-ID: <03e0aa020000983d@belgacom.be>
Received: from AE7111.BGC.NET ([45.219.2.50]) by belgacom.be ([10.120.129.162]) with ESMTP (TREND IMSS SMTP Service 7.0; TLS: TLSv1/SSLv3,128bits,RC4-MD5) id 03e0aa020000983d ; Fri, 19 Mar 2010 14:50:32 +0100
Received: from CMS03.BGC.NET ([10.120.128.133]) by AE7111.BGC.NET ([45.219.2.50]) with mapi; Fri, 19 Mar 2010 14:50:32 +0100
From: <jan.van.geel@belgacom.be>
To: <pkyzivat@cisco.com>, <john.elwell@siemens-enterprise.com>
Date: Fri, 19 Mar 2010 14:50:31 +0100
Thread-Topic: [martini] #15: support for non E.164 numbers
Thread-Index: AcrHaTrEaEBHqJEOTaiWkHfEk0l5BAAAZ+Ew
Message-ID: <208EAE1DFA28FC419529619ABB862244161769242E@CMS03.BGC.NET>
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net> <4BA37DBF.8060404@cisco.com>
In-Reply-To: <4BA37DBF.8060404@cisco.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
x-tm-as-product-ver: SMEX-8.0.0.1285-6.000.1038-17260.006
x-tm-as-result: No--47.652000-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: trac@localhost.amsl.com, martini@ietf.org
Subject: Re: [martini] #15: support for non E.164 numbers
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: Fri, 19 Mar 2010 13:50:42 -0000

Hi,

My=20understanding=20is=20that=20the=20term=20non-E.164=20numbers=20is=20=
not=20only=20used=20for=20private=20numbering=20plans,=20but=20also=20for=
=20short=20numbers=20like=20911=20or=20112.
If=20that=20is=20the=20case,=20it=20would=20not=20categorise=20this=20as=
=20"non-essential"

Kind=20regards

Jan=20Van=20Geel=20
IT=20and=20Network=20Development=20Specialist=20
Belgacom=20SDE/SDV/PSE/NST/NCP=20
Tel:=20+32=202=20202=201035=20
Tel:=20+32=202=20207=209032=20
Email=20:=20jan.van.geel@belgacom.be=20
www.cyberwezz.tk=20


-----Original=20Message-----
From:=20martini-bounces@ietf.org=20[mailto:martini-bounces@ietf.org]=20On=
=20Behalf=20Of=20Paul=20Kyzivat
Sent:=2019=20March=202010=2014:36
To:=20Elwell,=20John
Cc:=20trac@localhost.amsl.com;=20martini@ietf.org
Subject:=20Re:=20[martini]=20#15:=20support=20for=20non=20E.164=20numbers

Jon,

I=20agree=20with=20you=20here.

Solving=20this=20in=20general=20will=20require=20coming=20up=20with=20an=
=20approach=20for=20
routing=20local=20TEL=20URIs=20based=20on=20phone-context.=20I=20can=20th=
ink=20of=20various=20
ways=20to=20do=20that,=20but=20fear=20there=20would=20be=20as=20much=20po=
litics=20involved=20as=20
there=20has=20been=20with=20ENUM.

=09Thanks,
=09Paul

Elwell,=20John=20wrote:
>=20As=20an=20individual,=20I=20don't=20see=20an=20urgent=20need=20to=20s=
olve=20this=20in=20the=20initial=20phase.=20Present=20deployments=20use=
=20fully-qualified=20E.164=20numbers=20(or=20numbers=20that=20can=20be=20=
turned=20into=20fully-qualified=20E.164=20numbers),=20and=20it=20is=20for=
=20these=20deployments=20that=20we=20urgently=20need=20a=20standard=20on=
=20which=20to=20converge.=20Support=20for=20non-E.164-based=20(private=20=
numbers)=20might=20be=20nice=20to=20have,=20but=20not=20essential.=20
>=20
>=20I=20guess=20an=20important=20point=20is=20whether=20these=20non-E.164=
=20numbers=20are=20globally=20unique=20(as=20a=20result=20of=20a=20phone-=
context=20parameter),=20in=20which=20case=20they=20might=20be=20easier=20=
to=20accommodate,=20but=20even=20then=20I=20am=20not=20sure.=20If=20I=20h=
ave=20a=20telephone=20number=20in=20the=20form=20tel:1234;phone-context=
=3Dpbx.com,=20how=20does=20this=20get=20routed=20to=20ssp.com=20in=20orde=
r=20to=20get=20onward-routed=20to=20the=20PBX?=20It=20might=20work=20if=
=20you=20start=20off=20with=20sip:1234;phone-context=3Dpbx.com@ssp.com;us=
er=3Dphone,=20but=20how=20would=20the=20calling=20UA=20construct=20such=
=20a=20URI=20in=20the=20first=20place=20(unless=20returning=20a=20receive=
d=20URI)?
>=20
>=20It=20seems=20to=20me=20that=20considerations=20are=20similar=20to=20n=
on-number-based=20SIP=20URIs,=20and=20therefore=20this=20should=20be=20tr=
eated=20in=20the=20same=20way=20as=20#16=20(depending=20on=20what=20we=20=
decide=20for=20that=20-=20see=20my=20recommendation=20in=20my=20previous=
=20email).
>=20
>=20John
>=20
>=20
>>=20-----Original=20Message-----
>>=20From:=20martini-bounces@ietf.org=20
>>=20[mailto:martini-bounces@ietf.org]=20On=20Behalf=20Of=20martini=20iss=
ue=20tracker
>>=20Sent:=2018=20March=202010=2022:03
>>=20To:=20ietf.hanserik@gmail.com
>>=20Cc:=20martini@ietf.org
>>=20Subject:=20[martini]=20#15:=20support=20for=20non=20E.164=20numbers
>>
>>=20#15:=20support=20for=20non=20E.164=20numbers
>>=20-------------------------------------+------------------------
>>=20--------------
>>=20=20Reporter:=20=20ietf.hanserik@...=20=20=20=20=20=20=20=20=20=20|=
=20=20=20=20=20=20=20Owner:=20=20=20=20=20=20=20=20=20=20=20=20
>>=20=20=20=20=20=20Type:=20=20defect=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20|=20=20=20=20=20=20Status:=20=20new=20=20=20=20=20=
=20=20
>>=20=20Priority:=20=20critical=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20|=20=20=20Milestone:=20=20milestone1
>>=20Component:=20=20reqs=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20|=20=20=20=20=20Version:=20=201.0=20=20=20=20=20=20=20
>>=20=20Severity:=20=20In=20WG=20Last=20Call=20=20=20=20=20=20=20=20=20=
=20|=20=20=20=20Keywords:=20=20=20=20=20=20=20=20=20=20=20=20
>>=20-------------------------------------+------------------------
>>=20--------------
>>=20=20REQ19=20-=20The=20mechanism=20MUST=20allow=20a=20set=20of=20assig=
ned=20telephone=20
>>=20numbers=20to
>>=20=20comprise=20local=20numbers=20as=20specified=20in=20RFC3966,=20whi=
ch=20can=20be=20in
>>=20=20contiguous=20ranges,=20discrete,=20or=20in=20any=20combination=20=
of=20the=20two.
>>
>>=20--=20
>>=20Ticket=20URL:=20<http://trac.tools.ietf.org/wg/martini/trac/ticket/1=
5>
>>=20martini=20<http://tools.ietf.org/martini/>
>>
>>=20_______________________________________________
>>=20martini=20mailing=20list
>>=20martini@ietf.org
>>=20https://www.ietf.org/mailman/listinfo/martini
>>
>=20_______________________________________________
>=20martini=20mailing=20list
>=20martini@ietf.org
>=20https://www.ietf.org/mailman/listinfo/martini
>=20
_______________________________________________
martini=20mailing=20list
martini@ietf.org
https://www.ietf.org/mailman/listinfo/martini

****=20DISCLAIMER=20****
http://www.belgacom.be/maildisclaimer

From pkyzivat@cisco.com  Fri Mar 19 07:05:36 2010
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 B4ADD3A6A57 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 07:05:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.613
X-Spam-Level: 
X-Spam-Status: No, score=-9.613 tagged_above=-999 required=5 tests=[AWL=-0.144, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_HI=-8]
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 mEN1pm9iFi49 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 07:05:35 -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 B55BE3A6A50 for <martini@ietf.org>; Fri, 19 Mar 2010 07:05:33 -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: AloVAKcho0tAZnwM/2dsb2JhbACIMgGTCXOhe5kMglgBgiEEjwk
X-IronPort-AV: E=Sophos;i="4.51,274,1267401600"; d="scan'208";a="94251090"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 19 Mar 2010 14:05:46 +0000
Received: from [161.44.174.156] (dhcp-161-44-174-156.cisco.com [161.44.174.156]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o2JE5kcF018558; Fri, 19 Mar 2010 14:05:46 GMT
Message-ID: <4BA384BA.8050001@cisco.com>
Date: Fri, 19 Mar 2010 10:05:46 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: jan.van.geel@belgacom.be
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org>	<A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net> <4BA37DBF.8060404@cisco.com> <208EAE1DFA28FC419529619ABB862244161769242E@CMS03.BGC.NET>
In-Reply-To: <208EAE1DFA28FC419529619ABB862244161769242E@CMS03.BGC.NET>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: trac@localhost.amsl.com, martini@ietf.org
Subject: Re: [martini] #15: support for non E.164 numbers
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: Fri, 19 Mar 2010 14:05:36 -0000

I think numbers like 911 and 112 are not an issue for martini *unless* 
we expect that there is a requirement that they be *terminated* on the 
pbx, and be routed to it via the SSP.

Is that kind of case in scope right now?

	Thanks,
	Paul

jan.van.geel@belgacom.be wrote:
> Hi,
> 
> My understanding is that the term non-E.164 numbers is not only used for private numbering plans, but also for short numbers like 911 or 112.
> If that is the case, it would not categorise this as "non-essential"
> 
> Kind regards
> 
> Jan Van Geel 
> IT and Network Development Specialist 
> Belgacom SDE/SDV/PSE/NST/NCP 
> Tel: +32 2 202 1035 
> Tel: +32 2 207 9032 
> Email : jan.van.geel@belgacom.be 
> www.cyberwezz.tk 
> 
> 
> -----Original Message-----
> From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: 19 March 2010 14:36
> To: Elwell, John
> Cc: trac@localhost.amsl.com; martini@ietf.org
> Subject: Re: [martini] #15: support for non E.164 numbers
> 
> Jon,
> 
> I agree with you here.
> 
> Solving this in general will require coming up with an approach for 
> routing local TEL URIs based on phone-context. I can think of various 
> ways to do that, but fear there would be as much politics involved as 
> there has been with ENUM.
> 
> 	Thanks,
> 	Paul
> 
> Elwell, John wrote:
>> As an individual, I don't see an urgent need to solve this in the initial phase. Present deployments use fully-qualified E.164 numbers (or numbers that can be turned into fully-qualified E.164 numbers), and it is for these deployments that we urgently need a standard on which to converge. Support for non-E.164-based (private numbers) might be nice to have, but not essential. 
>>
>> I guess an important point is whether these non-E.164 numbers are globally unique (as a result of a phone-context parameter), in which case they might be easier to accommodate, but even then I am not sure. If I have a telephone number in the form tel:1234;phone-context=pbx.com, how does this get routed to ssp.com in order to get onward-routed to the PBX? It might work if you start off with sip:1234;phone-context=pbx.com@ssp.com;user=phone, but how would the calling UA construct such a URI in the first place (unless returning a received URI)?
>>
>> It seems to me that considerations are similar to non-number-based SIP URIs, and therefore this should be treated in the same way as #16 (depending on what we decide for that - see my recommendation in my previous email).
>>
>> John
>>
>>
>>> -----Original Message-----
>>> From: martini-bounces@ietf.org 
>>> [mailto:martini-bounces@ietf.org] On Behalf Of martini issue tracker
>>> Sent: 18 March 2010 22:03
>>> To: ietf.hanserik@gmail.com
>>> Cc: martini@ietf.org
>>> Subject: [martini] #15: support for non E.164 numbers
>>>
>>> #15: support for non E.164 numbers
>>> -------------------------------------+------------------------
>>> --------------
>>>  Reporter:  ietf.hanserik@...          |       Owner:            
>>>      Type:  defect                   |      Status:  new       
>>>  Priority:  critical                 |   Milestone:  milestone1
>>> Component:  reqs                     |     Version:  1.0       
>>>  Severity:  In WG Last Call          |    Keywords:            
>>> -------------------------------------+------------------------
>>> --------------
>>>  REQ19 - The mechanism MUST allow a set of assigned telephone 
>>> numbers to
>>>  comprise local numbers as specified in RFC3966, which can be in
>>>  contiguous ranges, discrete, or in any combination of the two.
>>>
>>> -- 
>>> Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/15>
>>> martini <http://tools.ietf.org/martini/>
>>>
>>> _______________________________________________
>>> martini mailing list
>>> martini@ietf.org
>>> https://www.ietf.org/mailman/listinfo/martini
>>>
>> _______________________________________________
>> martini mailing list
>> martini@ietf.org
>> https://www.ietf.org/mailman/listinfo/martini
>>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
> 
> **** DISCLAIMER ****
> http://www.belgacom.be/maildisclaimer
> 

From john.elwell@siemens-enterprise.com  Fri Mar 19 07:15:57 2010
Return-Path: <john.elwell@siemens-enterprise.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 CAAAD3A6A71 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 07:15:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.636
X-Spam-Level: 
X-Spam-Status: No, score=-1.636 tagged_above=-999 required=5 tests=[AWL=-0.166, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 S+gFbMSB1i6M for <martini@core3.amsl.com>; Fri, 19 Mar 2010 07:15:55 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id C56903A6A82 for <martini@ietf.org>; Fri, 19 Mar 2010 07:15:48 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1278440; Fri, 19 Mar 2010 15:16:00 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 603CE1EB82B8; Fri, 19 Mar 2010 15:16:00 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Fri, 19 Mar 2010 15:16:00 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>
Date: Fri, 19 Mar 2010 15:15:59 +0100
Thread-Topic: [martini] #15: support for non E.164 numbers
Thread-Index: AcrHXAJSsC2G8mRlRUC201GjjKfoBQAEiR6w
Message-ID: <A444A0F8084434499206E78C106220CABE982931@MCHP058A.global-ad.net>
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net> <9ae56b1e1003190502r26359206rf5bcb481addd8d20@mail.gmail.com>
Keywords: MARTINI
In-Reply-To: <9ae56b1e1003190502r26359206rf5bcb481addd8d20@mail.gmail.com>
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
Cc: "trac@localhost.amsl.com" <trac@localhost.amsl.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #15: support for non E.164 numbers
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: Fri, 19 Mar 2010 14:15:57 -0000

=20

> -----Original Message-----
> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]=20
> Sent: 19 March 2010 12:02
> To: Elwell, John
> Cc: trac@localhost.amsl.com; martini@ietf.org
> Subject: Re: [martini] #15: support for non E.164 numbers
>=20
> Again the question is not how such requests reach the SSP,=20
> the question is how given that such requests are handled by=20
> the SSP such can be delivered to an IP-PBX to which they are assigned.
[JRE] I agree. But on the other hand, requiring we have a solution for rout=
ing such requests to the SIP-PBX when it is unclear how such requests might=
 arrive at the SSP in the first place seems pointless. We just need to be c=
lear whether this is a common enough situation that we need a solution for =
this on day one, and that there are indeed solutions in existence for getti=
ng requests to the SSP.

John

>=20
> The point is that an SSP may have more complete enterprise=20
> offering that would require calls to be delivered via the SSP=20
> cloud to enterprise private numbers that do not have a DID=20
> E.164 number, but which are assigned to a PBX. Such private=20
> numbers are completely under control of the enterprise and do=20
> not require reservation of E.164 for no good reason.
>=20
> The current solution should not prohibit such service=20
> offerings and I haven't seen a good reason why this should=20
> not be covered.
>=20
> #16 is a different topic.=20
>=20
> /Hans Erik van Elburg
>=20
>=20
>=20
> On Fri, Mar 19, 2010 at 11:55 AM, Elwell, John=20
> <john.elwell@siemens-enterprise.com> wrote:
>=20
>=20
> 	As an individual, I don't see an urgent need to solve=20
> this in the initial phase. Present deployments use=20
> fully-qualified E.164 numbers (or numbers that can be turned=20
> into fully-qualified E.164 numbers), and it is for these=20
> deployments that we urgently need a standard on which to=20
> converge. Support for non-E.164-based (private numbers) might=20
> be nice to have, but not essential.
> =09
> 	I guess an important point is whether these non-E.164=20
> numbers are globally unique (as a result of a phone-context=20
> parameter), in which case they might be easier to=20
> accommodate, but even then I am not sure. If I have a=20
> telephone number in the form tel:1234;phone-context=3Dpbx.com,=20
> how does this get routed to ssp.com in order to get=20
> onward-routed to the PBX? It might work if you start off with=20
> sip:1234;phone-context=3Dpbx.com@ssp.com;user=3Dphone, but how=20
> would the calling UA construct such a URI in the first place=20
> (unless returning a received URI)?
> =09
> 	It seems to me that considerations are similar to=20
> non-number-based SIP URIs, and therefore this should be=20
> treated in the same way as #16 (depending on what we decide=20
> for that - see my recommendation in my previous email).
> =09
> 	John
> =09
>=20
>=20
> 	> -----Original Message-----
> 	> From: martini-bounces@ietf.org
> 	> [mailto:martini-bounces@ietf.org] On Behalf Of=20
> martini issue tracker
> 	> Sent: 18 March 2010 22:03
> 	> To: ietf.hanserik@gmail.com
> 	> Cc: martini@ietf.org
> 	> Subject: [martini] #15: support for non E.164 numbers
> 	>
> 	> #15: support for non E.164 numbers
> 	> -------------------------------------+------------------------
> 	> --------------
> 	>  Reporter:  ietf.hanserik@...          |       Owner:
> 	>      Type:  defect                   |      Status:  new
> 	>  Priority:  critical                 |   Milestone: =20
> milestone1
> 	> Component:  reqs                     |     Version:  1.0
> 	>  Severity:  In WG Last Call          |    Keywords:
> 	> -------------------------------------+------------------------
> 	> --------------
> 	>  REQ19 - The mechanism MUST allow a set of assigned telephone
> 	> numbers to
> 	>  comprise local numbers as specified in RFC3966,=20
> which can be in
> 	>  contiguous ranges, discrete, or in any combination=20
> of the two.
> 	>
> 	> --
> 	> Ticket URL:=20
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/15>
> 	> martini <http://tools.ietf.org/martini/>
> 	>
> =09
> 	> _______________________________________________
> 	> martini mailing list
> 	> martini@ietf.org
> 	> https://www.ietf.org/mailman/listinfo/martini
> 	>=20
>=20
>=20
> =

From adam@nostrum.com  Fri Mar 19 07:18:51 2010
Return-Path: <adam@nostrum.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 637143A6A71 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 07:18:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.059
X-Spam-Level: 
X-Spam-Status: No, score=-1.059 tagged_above=-999 required=5 tests=[AWL=-1.448, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, SPF_PASS=-0.001]
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 S0CS+eaJcuoX for <martini@core3.amsl.com>; Fri, 19 Mar 2010 07:18:50 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 44E9B3A681A for <martini@ietf.org>; Fri, 19 Mar 2010 07:18:50 -0700 (PDT)
Received: from hydra-3.local (ppp-70-249-147-216.dsl.rcsntx.swbell.net [70.249.147.216]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o2JEIx8G069575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Mar 2010 09:18:59 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4BA387D3.9070704@nostrum.com>
Date: Fri, 19 Mar 2010 09:18:59 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.8) Gecko/20100216 Thunderbird/3.0.2
MIME-Version: 1.0
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org>	<A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net>	<4BA37DBF.8060404@cisco.com> <9ae56b1e1003190650s5c402e39g3aa840f31673e4c6@mail.gmail.com>
In-Reply-To: <9ae56b1e1003190650s5c402e39g3aa840f31673e4c6@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 70.249.147.216 is authenticated by a trusted mechanism)
Cc: "trac@localhost.amsl.com" <trac@localhost.amsl.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #15: support for non E.164 numbers
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: Fri, 19 Mar 2010 14:18:51 -0000

On 3/19/10 08:50, Mar 19, Hans Erik van Elburg wrote:
> So the argument here goes: we don't know how local numbers would be 
> routed to the SSP therefore we will not allow local numbers to be 
> delivered to IP-PBX's by that SSP even if they only have significance 
> within the SSP domain and are understood by the PBX.

The issue really comes down to global uniqueness. I don't think GIN 
currently forbids private numbers; it's just not something we're taking 
on as a design constraint. If an SSP and their customers can guarantee 
uniqueness of user portions among all PBXes, they would be free (within 
the current GIN framework) to try to make that work. And it probably will.

But we're explicitly in an unprecedented hurry here (when else has a WG 
had three interims in two months?), and taking on the additional 
analysis to ensure that private numbering works, and making adjustments 
to the protocol to accommodate it, don't fit into that mode of operation.

>
> I can not really follow that logic. Seems like forced limitation of 
> freedom by design.

Perhaps -- that might be the other side of the coin that I would 
characterize as "restricting the solution space for the sake of expediency."

Some projects are planned based on "how long would it take to design X 
so that it is perfect." Others are planned based on "we have X amount of 
time; what can you design in that timeframe?" In the IETF, we tend to 
deal with the former, and the answer is "3 to 5 years, unless someone 
disagrees with something, in which case it will take longer." For the 
first MARTINI deliverables, we're dealing with the latter, where the 
timeframe is "within 3 to 6 months."

/a

From pkyzivat@cisco.com  Fri Mar 19 07:23:14 2010
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 7A9193A685A for <martini@core3.amsl.com>; Fri, 19 Mar 2010 07:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.61
X-Spam-Level: 
X-Spam-Status: No, score=-9.61 tagged_above=-999 required=5 tests=[AWL=-0.141,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_HI=-8]
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 9otOUdHNn+9w for <martini@core3.amsl.com>; Fri, 19 Mar 2010 07:23:11 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 76A2B3A681A for <martini@ietf.org>; Fri, 19 Mar 2010 07:23:11 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACslo0tAZnwM/2dsb2JhbACbPHOhepkNglgBgiEEjwk
X-IronPort-AV: E=Sophos;i="4.51,274,1267401600"; d="scan'208";a="94393080"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 19 Mar 2010 14:23:24 +0000
Received: from [161.44.174.156] (dhcp-161-44-174-156.cisco.com [161.44.174.156]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o2JENNEL024072; Fri, 19 Mar 2010 14:23:23 GMT
Message-ID: <4BA388DC.1010109@cisco.com>
Date: Fri, 19 Mar 2010 10:23:24 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org>	 <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net>	 <4BA37DBF.8060404@cisco.com> <9ae56b1e1003190650s5c402e39g3aa840f31673e4c6@mail.gmail.com>
In-Reply-To: <9ae56b1e1003190650s5c402e39g3aa840f31673e4c6@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "trac@localhost.amsl.com" <trac@localhost.amsl.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #15: support for non E.164 numbers
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: Fri, 19 Mar 2010 14:23:15 -0000

Hans Erik van Elburg wrote:
> So the argument here goes: we don't know how local numbers would be 
> routed to the SSP therefore we will not allow local numbers to be 
> delivered to IP-PBX's by that SSP even if they only have significance 
> within the SSP domain and are understood by the PBX.
> 
> I can not really follow that logic. Seems like forced limitation of 
> freedom by design.

The issue is simply one of how to reduce scope to something manageable.
The way that has been proposed is to reduce the scope to E.164 numbers.

The value of doing so is that we then don't have to consider the issues 
that might arise for cases outside that scope.

IIUC you are proposing to change the scope to include something beyond 
E.164 numbers. (I don't know how much beyond.) Increasing the scope will 
at least require people to reconsider what new issues might arise with 
that expanded scope. Its certainly easier not to do that reevaluation.

Nevertheless, maybe it is an important thing to do. IMO the discussion 
of how such numbers might be needed is merely a way to get at the 
importance of expanding the scope. If we can't think of good reasons why 
this expansion is needed, then there is less motivation to consider it 
right now.

As an example of the implications of expanding the scope beyond E.164 
numbers:

When a request arrives for any of the implicitly registered numbers, its 
going to be mapped to a different URL with the same user part but a 
domain part belonging to the pbx. (At least that is the Gin proposal.)

The pbx needs to know which user parts are valid for such uses, and also 
which user parts will never arise from such mappings and which may be 
used for other internal purposes. With the scope limited to E.164 
numbers, the pbx knows that it should reserve user parts of form +digits 
for such use, and that any user part of another form is "safe" for other 
internal uses. Once we expand the scope that assumption must change.

	Thanks,
	Paul

> /Hans Erik van Elburg
> 
> On Fri, Mar 19, 2010 at 2:35 PM, Paul Kyzivat <pkyzivat@cisco.com 
> <mailto:pkyzivat@cisco.com>> wrote:
> 
>     Jon,
> 
>     I agree with you here.
> 
>     Solving this in general will require coming up with an approach for
>     routing local TEL URIs based on phone-context. I can think of
>     various ways to do that, but fear there would be as much politics
>     involved as there has been with ENUM.
> 
>            Thanks,
>            Paul
> 
> 
>     Elwell, John wrote:
> 
>         As an individual, I don't see an urgent need to solve this in
>         the initial phase. Present deployments use fully-qualified E.164
>         numbers (or numbers that can be turned into fully-qualified
>         E.164 numbers), and it is for these deployments that we urgently
>         need a standard on which to converge. Support for
>         non-E.164-based (private numbers) might be nice to have, but not
>         essential.
>         I guess an important point is whether these non-E.164 numbers
>         are globally unique (as a result of a phone-context parameter),
>         in which case they might be easier to accommodate, but even then
>         I am not sure. If I have a telephone number in the form
>         tel:1234;phone-context=pbx.com <http://pbx.com>, how does this
>         get routed to ssp.com <http://ssp.com> in order to get
>         onward-routed to the PBX? It might work if you start off with
>         sip:1234;phone-context=pbx.com <http://pbx.com>@ssp.com
>         <http://ssp.com>;user=phone, but how would the calling UA
>         construct such a URI in the first place (unless returning a
>         received URI)?
> 
>         It seems to me that considerations are similar to
>         non-number-based SIP URIs, and therefore this should be treated
>         in the same way as #16 (depending on what we decide for that -
>         see my recommendation in my previous email).
> 
>         John
> 
> 
>             -----Original Message-----
>             From: martini-bounces@ietf.org
>             <mailto:martini-bounces@ietf.org>
>             [mailto:martini-bounces@ietf.org
>             <mailto:martini-bounces@ietf.org>] On Behalf Of martini
>             issue tracker
>             Sent: 18 March 2010 22:03
>             To: ietf.hanserik@gmail.com <mailto:ietf.hanserik@gmail.com>
>             Cc: martini@ietf.org <mailto:martini@ietf.org>
>             Subject: [martini] #15: support for non E.164 numbers
> 
>             #15: support for non E.164 numbers
>             -------------------------------------+------------------------
>             --------------
>              Reporter:  ietf.hanserik@...          |       Owner:      
>                       Type:  defect                   |      Status:
>              new        Priority:  critical                 |  
>             Milestone:  milestone1
>             Component:  reqs                     |     Version:  1.0    
>                Severity:  In WG Last Call          |    Keywords:      
>                
>              -------------------------------------+------------------------
>             --------------
>              REQ19 - The mechanism MUST allow a set of assigned
>             telephone numbers to
>              comprise local numbers as specified in RFC3966, which can be in
>              contiguous ranges, discrete, or in any combination of the two.
> 
>             -- 
>             Ticket URL:
>             <http://trac.tools.ietf.org/wg/martini/trac/ticket/15>
>             martini <http://tools.ietf.org/martini/>
> 
>             _______________________________________________
>             martini mailing list
>             martini@ietf.org <mailto:martini@ietf.org>
>             https://www.ietf.org/mailman/listinfo/martini
> 
>         _______________________________________________
>         martini mailing list
>         martini@ietf.org <mailto:martini@ietf.org>
>         https://www.ietf.org/mailman/listinfo/martini
> 
> 

From jan.van.geel@belgacom.be  Fri Mar 19 07:25:14 2010
Return-Path: <jan.van.geel@belgacom.be>
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 EA34E3A6A41 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 07:25:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.414
X-Spam-Level: *
X-Spam-Status: No, score=1.414 tagged_above=-999 required=5 tests=[AWL=0.469,  BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13]
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 u4sHXNm11rEV for <martini@core3.amsl.com>; Fri, 19 Mar 2010 07:25:14 -0700 (PDT)
Received: from inmxmss01.belgacom.be (inmxmss01.belgacom.be [213.181.44.82]) by core3.amsl.com (Postfix) with ESMTP id 3C9273A6882 for <martini@ietf.org>; Fri, 19 Mar 2010 07:25:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.51,274,1267398000"; d="scan'208";a="77062000"
Received: from unknown (HELO A03007.BGC.NET) ([10.120.129.162]) by outmxmss01.belgacom.be with ESMTP; 19 Mar 2010 15:25:23 +0100
X-TM-IMSS-Message-ID: <0400918d0000a20d@belgacom.be>
Received: from AE7212.BGC.NET ([45.223.1.31]) by belgacom.be ([10.120.129.162]) with ESMTP (TREND IMSS SMTP Service 7.0; TLS: TLSv1/SSLv3,128bits,RC4-MD5) id 0400918d0000a20d ; Fri, 19 Mar 2010 15:25:23 +0100
Received: from CMS03.BGC.NET ([10.120.128.133]) by AE7212.BGC.NET ([45.223.1.31]) with mapi; Fri, 19 Mar 2010 15:25:23 +0100
From: <jan.van.geel@belgacom.be>
To: <adam@nostrum.com>, <ietf.hanserik@gmail.com>
Date: Fri, 19 Mar 2010 15:25:21 +0100
Thread-Topic: [martini] #15: support for non E.164 numbers
Thread-Index: AcrHbyXmJpkjpPWOTVGRFTk2e5FH2wAAKV/Q
Message-ID: <208EAE1DFA28FC419529619ABB862244161769256F@CMS03.BGC.NET>
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net> <4BA37DBF.8060404@cisco.com> <9ae56b1e1003190650s5c402e39g3aa840f31673e4c6@mail.gmail.com> <4BA387D3.9070704@nostrum.com>
In-Reply-To: <4BA387D3.9070704@nostrum.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
x-tm-as-product-ver: SMEX-8.0.0.1285-6.000.1038-17260.006
x-tm-as-result: No--44.413400-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: trac@localhost.amsl.com, martini@ietf.org
Subject: Re: [martini] #15: support for non E.164 numbers
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: Fri, 19 Mar 2010 14:25:15 -0000

It=20seems=20that=20you=20are=20in=20hurry=20to=20provide=20a=20solution=
=20to=20a=20problem,=20for=20which=20another=20forum=20already=20provided=
=20a=20solution.
In=20order=20to=20win=20time,=20why=20not=20envisaging=20adopting=20that=
=20solution=20and=20study=20possible=20enhancements.

Kind=20regards

Jan=20Van=20Geel=20
IT=20and=20Network=20Development=20Specialist=20
Belgacom=20SDE/SDV/PSE/NST/NCP=20
Tel:=20+32=202=20202=201035=20
Tel:=20+32=202=20207=209032=20
Email=20:=20jan.van.geel@belgacom.be=20
www.cyberwezz.tk=20


-----Original=20Message-----
From:=20martini-bounces@ietf.org=20[mailto:martini-bounces@ietf.org]=20On=
=20Behalf=20Of=20Adam=20Roach
Sent:=2019=20March=202010=2015:19
To:=20Hans=20Erik=20van=20Elburg
Cc:=20trac@localhost.amsl.com;=20martini@ietf.org
Subject:=20Re:=20[martini]=20#15:=20support=20for=20non=20E.164=20numbers


On=203/19/10=2008:50,=20Mar=2019,=20Hans=20Erik=20van=20Elburg=20wrote:
>=20So=20the=20argument=20here=20goes:=20we=20don't=20know=20how=20local=
=20numbers=20would=20be=20
>=20routed=20to=20the=20SSP=20therefore=20we=20will=20not=20allow=20local=
=20numbers=20to=20be=20
>=20delivered=20to=20IP-PBX's=20by=20that=20SSP=20even=20if=20they=20only=
=20have=20significance=20
>=20within=20the=20SSP=20domain=20and=20are=20understood=20by=20the=20PBX=
.

The=20issue=20really=20comes=20down=20to=20global=20uniqueness.=20I=20don=
't=20think=20GIN=20
currently=20forbids=20private=20numbers;=20it's=20just=20not=20something=
=20we're=20taking=20
on=20as=20a=20design=20constraint.=20If=20an=20SSP=20and=20their=20custom=
ers=20can=20guarantee=20
uniqueness=20of=20user=20portions=20among=20all=20PBXes,=20they=20would=
=20be=20free=20(within=20
the=20current=20GIN=20framework)=20to=20try=20to=20make=20that=20work.=20=
And=20it=20probably=20will.

But=20we're=20explicitly=20in=20an=20unprecedented=20hurry=20here=20(when=
=20else=20has=20a=20WG=20
had=20three=20interims=20in=20two=20months?),=20and=20taking=20on=20the=
=20additional=20
analysis=20to=20ensure=20that=20private=20numbering=20works,=20and=20maki=
ng=20adjustments=20
to=20the=20protocol=20to=20accommodate=20it,=20don't=20fit=20into=20that=
=20mode=20of=20operation.

>
>=20I=20can=20not=20really=20follow=20that=20logic.=20Seems=20like=20forc=
ed=20limitation=20of=20
>=20freedom=20by=20design.

Perhaps=20--=20that=20might=20be=20the=20other=20side=20of=20the=20coin=
=20that=20I=20would=20
characterize=20as=20"restricting=20the=20solution=20space=20for=20the=20s=
ake=20of=20expediency."

Some=20projects=20are=20planned=20based=20on=20"how=20long=20would=20it=
=20take=20to=20design=20X=20
so=20that=20it=20is=20perfect."=20Others=20are=20planned=20based=20on=20"=
we=20have=20X=20amount=20of=20
time;=20what=20can=20you=20design=20in=20that=20timeframe?"=20In=20the=20=
IETF,=20we=20tend=20to=20
deal=20with=20the=20former,=20and=20the=20answer=20is=20"3=20to=205=20yea=
rs,=20unless=20someone=20
disagrees=20with=20something,=20in=20which=20case=20it=20will=20take=20lo=
nger."=20For=20the=20
first=20MARTINI=20deliverables,=20we're=20dealing=20with=20the=20latter,=
=20where=20the=20
timeframe=20is=20"within=203=20to=206=20months."

/a
_______________________________________________
martini=20mailing=20list
martini@ietf.org
https://www.ietf.org/mailman/listinfo/martini

****=20DISCLAIMER=20****
http://www.belgacom.be/maildisclaimer

From adam@nostrum.com  Fri Mar 19 07:53:31 2010
Return-Path: <adam@nostrum.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 7ED903A6A9A for <martini@core3.amsl.com>; Fri, 19 Mar 2010 07:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[AWL=-0.465, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, SPF_PASS=-0.001]
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 hXMZamFN2qMh for <martini@core3.amsl.com>; Fri, 19 Mar 2010 07:53:30 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 72BB73A6823 for <martini@ietf.org>; Fri, 19 Mar 2010 07:53:30 -0700 (PDT)
Received: from [192.168.0.128] (ppp-70-249-147-216.dsl.rcsntx.swbell.net [70.249.147.216]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o2JErb7x072324 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Mar 2010 09:53:38 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4BA38FF1.8000903@nostrum.com>
Date: Fri, 19 Mar 2010 09:53:37 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: jan.van.geel@belgacom.be
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org>	<A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net>	<4BA37DBF.8060404@cisco.com>	<9ae56b1e1003190650s5c402e39g3aa840f31673e4c6@mail.gmail.com> <4BA387D3.9070704@nostrum.com> <208EAE1DFA28FC419529619ABB862244161769256F@CMS03.BGC.NET>
In-Reply-To: <208EAE1DFA28FC419529619ABB862244161769256F@CMS03.BGC.NET>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 70.249.147.216 is authenticated by a trusted mechanism)
Cc: martini@ietf.org
Subject: Re: [martini] #15: support for non E.164 numbers
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: Fri, 19 Mar 2010 14:53:31 -0000

On 03/19/2010 09:25 AM, jan.van.geel@belgacom.be wrote:
> It seems that you are in hurry to provide a solution to a problem, for which another forum already provided a solution.
> In order to win time, why not envisaging adopting that solution and study possible enhancements.
>    

As we've been over many times on the list and at interim meetings, the 
problems in those solutions are myriad. No one has stepped forward with 
plausible ways to address such problems -- probably because the problems 
are inherent in the mechanism itself, and not minor flaws.

I would be delighted if someone could prove me wrong by proposing 
acceptable changes to the solutions you reference that address the suite 
of problems that have been raised in MARTINI. I have no burning desire 
to author a draft that addresses a problem that I have no interest in. 
But no one else is coming up with solutions, and the problems inherent 
in shaken and its progenitors are profound enough that I do not believe 
the IETF can endorse them.

/a

From D.Hancock@CableLabs.com  Fri Mar 19 08:25:04 2010
Return-Path: <D.Hancock@CableLabs.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 76AFB3A6A89 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 08:25:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.188
X-Spam-Level: 
X-Spam-Status: No, score=0.188 tagged_above=-999 required=5 tests=[AWL=-0.480,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_MODEMCABLE=0.768,  HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001]
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 yYareeOuinFi for <martini@core3.amsl.com>; Fri, 19 Mar 2010 08:25:00 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 39A2C3A6860 for <martini@ietf.org>; Fri, 19 Mar 2010 08:25:00 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o2JFPCND009260; Fri, 19 Mar 2010 09:25:12 -0600
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Fri, 19 Mar 2010 09:25:12 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Fri, 19 Mar 2010 09:25:12 -0600
From: David Hancock <D.Hancock@CableLabs.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>, "martini@ietf.org" <martini@ietf.org>
Date: Fri, 19 Mar 2010 09:25:11 -0600
Thread-Topic: [martini] REMINDER: Call for Adoption of "Registration for Multiple	Phone Numbers in the SIP"
Thread-Index: AcrA0nOh6uKvC/BfTwaofzWH1iL4sgGpd8tg
Message-ID: <76AC5FEF83F1E64491446437EA81A61F7CD4E30A9B@srvxchg>
References: <BLU137-DS152FACD79E78C9460523D593320@phx.gbl>
In-Reply-To: <BLU137-DS152FACD79E78C9460523D593320@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_76AC5FEF83F1E64491446437EA81A61F7CD4E30A9Bsrvxchg_"
MIME-Version: 1.0
X-Approved: ondar
Subject: Re: [martini] REMINDER: Call for Adoption of "Registration for Multiple	Phone Numbers in the SIP"
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: Fri, 19 Mar 2010 15:25:04 -0000

--_000_76AC5FEF83F1E64491446437EA81A61F7CD4E30A9Bsrvxchg_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I believe the GIN solution is technically sound, and in the interest of mak=
ing progress toward an IETF-sanctioned solution, I vote for adopting the GI=
N draft as a MARTINI WG item.

David


________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Bernard Aboba
Sent: Wednesday, March 10, 2010 9:22 PM
To: martini@ietf.org
Subject: [martini] REMINDER: Call for Adoption of "Registration for Multipl=
e Phone Numbers in the SIP"

This is a reminder that the IETF MARTINI WG is currently holding a Call for=
 Adoption of "Registration for Multiple Phone Numbers in the SIP" as a MART=
INI WG work item.  The MARTINI WG Call for Adoption will last until Friday,=
 March 19, 2010.
More information on the Call for Adoption is available here:
http://www.ietf.org/mail-archive/web/martini/current/msg00916.html

Note that the Call for Adoption not only requests WG participants to state =
their opinions on whether the GIN document is ready for adoption,   but als=
o solicits in depth reviews of the draft.   Every comment from editorial NI=
Ts to technical issues is fair game, regardless of how minor (or major) the=
 issue might be.


--_000_76AC5FEF83F1E64491446437EA81A61F7CD4E30A9Bsrvxchg_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:st=3D"&#1;" =
xmlns=3D"http://www.w3.org/TR/REC-html40"
xmlns:ns0=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/"
xmlns:ns1=3D"http://schemas.microsoft.com/office/2006/digsig-setup"
xmlns:ns2=3D"http://schemas.microsoft.com/office/2006/digsig"
xmlns:ns3=3D"http://schemas.openxmlformats.org/package/2006/digital-signatu=
re"
xmlns:ns4=3D"http://schemas.openxmlformats.org/markup-compatibility/2006"
xmlns:ns5=3D"http://schemas.microsoft.com/office/2004/12/omml"
xmlns:ns6=3D"http://schemas.openxmlformats.org/package/2006/relationships"
xmlns:ns7=3D"http://microsoft.com/sharepoint/webpartpages"
xmlns:ns8=3D"http://schemas.microsoft.com/exchange/services/2006/types"
xmlns:ns9=3D"http://schemas.microsoft.com/exchange/services/2006/messages"
xmlns:ns10=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/"
xmlns:ns11=3D"http://microsoft.com/webservices/SharePointPortalServer/Publi=
shedLinksService"
xmlns:ns12=3D"urn:schemas-microsoft-com:">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.Comment-blue, li.Comment-blue, div.Comment-blue
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Times New Roman";
	font-weight:bold;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:Calibri;
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I believe the GIN solution is technica=
lly
sound, and in the interest of making progress toward an IETF-sanctioned
solution, I vote for adopting the GIN draft as a MARTINI WG item.<o:p></o:p=
></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>David<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;font-family:"Times=
 New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>Bernard Aboba<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, March 10, 2=
010
9:22 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> martini@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [martini] REMINDER:=
 Call
for Adoption of &quot;Registration for Multiple Phone Numbers in the SIP&qu=
ot;</span></font><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt;font-fami=
ly:"Times New Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'>This is a reminder=
 that the
IETF MARTINI WG is currently holding a Call for Adoption of &#8220;Registra=
tion for
Multiple Phone Numbers in the SIP&#8221; as a MARTINI WG work item. &nbsp;T=
he MARTINI
WG Call for Adoption will last until Friday, March 19, 2010.<o:p></o:p></sp=
an></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'>More
information on the Call for Adoption is available here:<o:p></o:p></span></=
font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'><a
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00916.html"=
>http://www.ietf.org/mail-archive/web/martini/current/msg00916.html</a><o:p=
></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'>Note
that the Call for Adoption not only requests WG participants to state their
opinions on whether the GIN document is ready for adoption,&nbsp; &nbsp;but
also solicits in depth reviews of the draft.&nbsp; &nbsp;Every comment from
editorial NITs to technical issues is fair game, regardless of how minor (o=
r
major) the issue might be. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>

</body>

</html>

--_000_76AC5FEF83F1E64491446437EA81A61F7CD4E30A9Bsrvxchg_--

From richard@shockey.us  Fri Mar 19 12:06:22 2010
Return-Path: <richard@shockey.us>
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 209323A6964 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 12:06:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.291
X-Spam-Level: 
X-Spam-Status: No, score=-1.291 tagged_above=-999 required=5 tests=[AWL=0.178,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 AT91BtyRddM7 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 12:06:21 -0700 (PDT)
Received: from outbound-mail-360.bluehost.com (outbound-mail-360.bluehost.com [66.147.249.254]) by core3.amsl.com (Postfix) with SMTP id DBC883A68C6 for <martini@ietf.org>; Fri, 19 Mar 2010 12:06:20 -0700 (PDT)
Received: (qmail 30394 invoked by uid 0); 19 Mar 2010 19:06:34 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy2.bluehost.com with SMTP; 19 Mar 2010 19:06:34 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=B4VNN3PuCDDM5NwLOUb4zELrJ7P9hPpNB0X8tNJZ6MB9kc6CLQiRfhckx8hiF9v2h89jyeDAXMJ0tOWp+ANP/HIaJM06JGRrgJGnap5AZpG9HiD7DPMTX/7rHpjDEaI0;
Received: from pool-173-66-69-79.washdc.fios.verizon.net ([173.66.69.79] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from <richard@shockey.us>) id 1NshWk-0001Ae-3x; Fri, 19 Mar 2010 13:06:34 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>, "'Elwell, John'" <john.elwell@siemens-enterprise.com>
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org>	<A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net> <4BA37DBF.8060404@cisco.com>
In-Reply-To: <4BA37DBF.8060404@cisco.com>
Date: Fri, 19 Mar 2010 15:06:29 -0400
Message-ID: <014c01cac797$48f3b240$dadb16c0$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcrHaR8OEntYalWxQjmL+ggE8+OtigALf9hg
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.66.69.79 authed with richard@shockey.us}
Cc: trac@localhost.amsl.com, martini@ietf.org
Subject: Re: [martini] #15: support for non E.164 numbers
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: Fri, 19 Mar 2010 19:06:22 -0000

+1 as well. 

Politics in ENUM ???  Naaah. Whatever gave you that thought?  :-) 

-----Original Message-----
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf
Of Paul Kyzivat
Sent: Friday, March 19, 2010 9:36 AM
To: Elwell, John
Cc: trac@localhost.amsl.com; martini@ietf.org
Subject: Re: [martini] #15: support for non E.164 numbers

Jon,

I agree with you here.

Solving this in general will require coming up with an approach for 
routing local TEL URIs based on phone-context. I can think of various 
ways to do that, but fear there would be as much politics involved as 
there has been with ENUM.

	Thanks,
	Paul

Elwell, John wrote:
> As an individual, I don't see an urgent need to solve this in the initial
phase. Present deployments use fully-qualified E.164 numbers (or numbers
that can be turned into fully-qualified E.164 numbers), and it is for these
deployments that we urgently need a standard on which to converge. Support
for non-E.164-based (private numbers) might be nice to have, but not
essential. 
> 
> I guess an important point is whether these non-E.164 numbers are globally
unique (as a result of a phone-context parameter), in which case they might
be easier to accommodate, but even then I am not sure. If I have a telephone
number in the form tel:1234;phone-context=pbx.com, how does this get routed
to ssp.com in order to get onward-routed to the PBX? It might work if you
start off with sip:1234;phone-context=pbx.com@ssp.com;user=phone, but how
would the calling UA construct such a URI in the first place (unless
returning a received URI)?
> 
> It seems to me that considerations are similar to non-number-based SIP
URIs, and therefore this should be treated in the same way as #16 (depending
on what we decide for that - see my recommendation in my previous email).
> 
> John
> 
> 
>> -----Original Message-----
>> From: martini-bounces@ietf.org 
>> [mailto:martini-bounces@ietf.org] On Behalf Of martini issue tracker
>> Sent: 18 March 2010 22:03
>> To: ietf.hanserik@gmail.com
>> Cc: martini@ietf.org
>> Subject: [martini] #15: support for non E.164 numbers
>>
>> #15: support for non E.164 numbers
>> -------------------------------------+------------------------
>> --------------
>>  Reporter:  ietf.hanserik@...          |       Owner:            
>>      Type:  defect                   |      Status:  new       
>>  Priority:  critical                 |   Milestone:  milestone1
>> Component:  reqs                     |     Version:  1.0       
>>  Severity:  In WG Last Call          |    Keywords:            
>> -------------------------------------+------------------------
>> --------------
>>  REQ19 - The mechanism MUST allow a set of assigned telephone 
>> numbers to
>>  comprise local numbers as specified in RFC3966, which can be in
>>  contiguous ranges, discrete, or in any combination of the two.
>>
>> -- 
>> Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/15>
>> martini <http://tools.ietf.org/martini/>
>>
>> _______________________________________________
>> martini mailing list
>> martini@ietf.org
>> https://www.ietf.org/mailman/listinfo/martini
>>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
> 
_______________________________________________
martini mailing list
martini@ietf.org
https://www.ietf.org/mailman/listinfo/martini


From richard@shockey.us  Fri Mar 19 12:09:05 2010
Return-Path: <richard@shockey.us>
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 97F913A6A09 for <martini@core3.amsl.com>; Fri, 19 Mar 2010 12:09:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.367
X-Spam-Level: 
X-Spam-Status: No, score=-0.367 tagged_above=-999 required=5 tests=[AWL=-0.757, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13]
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 cnf4M5+1E3oz for <martini@core3.amsl.com>; Fri, 19 Mar 2010 12:09:04 -0700 (PDT)
Received: from outbound-mail-360.bluehost.com (outbound-mail-360.bluehost.com [66.147.249.254]) by core3.amsl.com (Postfix) with SMTP id C8D343A67A1 for <martini@ietf.org>; Fri, 19 Mar 2010 12:09:03 -0700 (PDT)
Received: (qmail 5005 invoked by uid 0); 19 Mar 2010 19:09:16 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy2.bluehost.com with SMTP; 19 Mar 2010 19:09:15 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=ldkhsc62d7XKaW23/xUj9QCNfjwQ67G9n3EMFLxg7ckdFNOAhWLw/VuKznf2sWRk2+YWA8CA+re+2LQaPJ/cCmc3Mj1YByQwvdwpoqntXHkUi9kUkuEu68niiLh9EOIb;
Received: from pool-173-66-69-79.washdc.fios.verizon.net ([173.66.69.79] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from <richard@shockey.us>) id 1NshZL-0002LF-EB; Fri, 19 Mar 2010 13:09:15 -0600
From: "Richard Shockey" <richard@shockey.us>
To: <jan.van.geel@belgacom.be>, <adam@nostrum.com>, <ietf.hanserik@gmail.com>
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org>	<A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net>	<4BA37DBF.8060404@cisco.com>	<9ae56b1e1003190650s5c402e39g3aa840f31673e4c6@mail.gmail.com>	<4BA387D3.9070704@nostrum.com> <208EAE1DFA28FC419529619ABB862244161769256F@CMS03.BGC.NET>
In-Reply-To: <208EAE1DFA28FC419529619ABB862244161769256F@CMS03.BGC.NET>
Date: Fri, 19 Mar 2010 15:09:11 -0400
Message-ID: <014d01cac797$a91b2cc0$fb518640$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcrHbyXmJpkjpPWOTVGRFTk2e5FH2wAAKV/QAAnv+aA=
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.66.69.79 authed with richard@shockey.us}
Cc: trac@localhost.amsl.com, martini@ietf.org
Subject: Re: [martini] #15: support for non E.164 numbers
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: Fri, 19 Mar 2010 19:09:05 -0000

I do not agree that the 3GPP solution actually solves the problem we are
trying to address here.

-----Original Message-----
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf
Of jan.van.geel@belgacom.be
Sent: Friday, March 19, 2010 10:25 AM
To: adam@nostrum.com; ietf.hanserik@gmail.com
Cc: trac@localhost.amsl.com; martini@ietf.org
Subject: Re: [martini] #15: support for non E.164 numbers

It seems that you are in hurry to provide a solution to a problem, for which
another forum already provided a solution.
In order to win time, why not envisaging adopting that solution and study
possible enhancements.

Kind regards

Jan Van Geel 
IT and Network Development Specialist 
Belgacom SDE/SDV/PSE/NST/NCP 
Tel: +32 2 202 1035 
Tel: +32 2 207 9032 
Email : jan.van.geel@belgacom.be 
www.cyberwezz.tk 


-----Original Message-----
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf
Of Adam Roach
Sent: 19 March 2010 15:19
To: Hans Erik van Elburg
Cc: trac@localhost.amsl.com; martini@ietf.org
Subject: Re: [martini] #15: support for non E.164 numbers


On 3/19/10 08:50, Mar 19, Hans Erik van Elburg wrote:
> So the argument here goes: we don't know how local numbers would be 
> routed to the SSP therefore we will not allow local numbers to be 
> delivered to IP-PBX's by that SSP even if they only have significance 
> within the SSP domain and are understood by the PBX.

The issue really comes down to global uniqueness. I don't think GIN 
currently forbids private numbers; it's just not something we're taking 
on as a design constraint. If an SSP and their customers can guarantee 
uniqueness of user portions among all PBXes, they would be free (within 
the current GIN framework) to try to make that work. And it probably will.

But we're explicitly in an unprecedented hurry here (when else has a WG 
had three interims in two months?), and taking on the additional 
analysis to ensure that private numbering works, and making adjustments 
to the protocol to accommodate it, don't fit into that mode of operation.

>
> I can not really follow that logic. Seems like forced limitation of 
> freedom by design.

Perhaps -- that might be the other side of the coin that I would 
characterize as "restricting the solution space for the sake of expediency."

Some projects are planned based on "how long would it take to design X 
so that it is perfect." Others are planned based on "we have X amount of 
time; what can you design in that timeframe?" In the IETF, we tend to 
deal with the former, and the answer is "3 to 5 years, unless someone 
disagrees with something, in which case it will take longer." For the 
first MARTINI deliverables, we're dealing with the latter, where the 
timeframe is "within 3 to 6 months."

/a
_______________________________________________
martini mailing list
martini@ietf.org
https://www.ietf.org/mailman/listinfo/martini

**** DISCLAIMER ****
http://www.belgacom.be/maildisclaimer
_______________________________________________
martini mailing list
martini@ietf.org
https://www.ietf.org/mailman/listinfo/martini


From john.elwell@siemens-enterprise.com  Sun Mar 21 07:23:13 2010
Return-Path: <john.elwell@siemens-enterprise.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 47A0C3A6964 for <martini@core3.amsl.com>; Sun, 21 Mar 2010 07:23:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.377
X-Spam-Level: 
X-Spam-Status: No, score=-0.377 tagged_above=-999 required=5 tests=[AWL=-1.322, BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13]
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 WjgOVki3zZdy for <martini@core3.amsl.com>; Sun, 21 Mar 2010 07:23:12 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id AF0183A69CE for <martini@ietf.org>; Sun, 21 Mar 2010 07:20:23 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1286957; Sun, 21 Mar 2010 15:20:18 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id CFD881EB82B5; Sun, 21 Mar 2010 15:20:18 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.57]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Sun, 21 Mar 2010 15:20:18 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Gonzalo Camarillo <gcamaril@gmail.com>
Date: Sun, 21 Mar 2010 15:20:18 +0100
Thread-Topic: [martini] #17: Desirable to align with existing standards
Thread-Index: AcrHqbj4cV8buxFZSkOizTP0IANtfQApuWFw
Message-ID: <A444A0F8084434499206E78C106220CAC21E6B91@MCHP058A.global-ad.net>
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982764@MCHP058A.global-ad.net> <4BA38882.9000008@gmail.com>
In-Reply-To: <4BA38882.9000008@gmail.com>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #17: Desirable to align with existing standards
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: Sun, 21 Mar 2010 14:23:13 -0000

I assume this request is directed at Hans Erik.

John=20

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:gcamaril@gmail.com]=20
> Sent: 19 March 2010 14:22
> To: Elwell, John
> Cc: martini@ietf.org
> Subject: Re: [martini] #17: Desirable to align with existing standards
>=20
> Hi,
>=20
> could you please provide references to the ETSI and 3GPP=20
> specs mentioned
> below?
>=20
> Thanks,
>=20
> Gonzalo
>=20
> On 19/03/2010 1:01 PM, Elwell, John wrote:
> > As individual, I would remark that the market is already=20
> fragmented between SIP and IMS-SIP, which makes things difficult.
> >=20
> > As editor, I seek guidance from others on this one.
> >=20
> > John
> >=20
> >> -----Original Message-----
> >> From: martini-bounces@ietf.org=20
> >> [mailto:martini-bounces@ietf.org] On Behalf Of martini=20
> issue tracker
> >> Sent: 18 March 2010 22:21
> >> To: ietf.hanserik@gmail.com
> >> Cc: martini@ietf.org
> >> Subject: [martini] #17: Desirable to align with existing standards
> >>
> >> #17: Desirable to align with existing standards
> >> -------------------------------------+------------------------
> >> --------------
> >>  Reporter:  ietf.hanserik@...          |       Owner:           =20
> >>      Type:  enhancement              |      Status:  new      =20
> >>  Priority:  major                    |   Milestone:  milestone1
> >> Component:  reqs                     |     Version:  1.0      =20
> >>  Severity:  In WG Last Call          |    Keywords:           =20
> >> -------------------------------------+------------------------
> >> --------------
> >>  DES5 - The mechanism SHOULD be aligned as much as possible=20
> >> with mechanisms
> >>  already standardised in other SDO's like ETSI and 3GPP in order to
> >>  prohibit a fragmentation of the market.
> >>
> >> --=20
> >> Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/17>
> >> martini <http://tools.ietf.org/martini/>
> >>
> >> _______________________________________________
> >> martini mailing list
> >> martini@ietf.org
> >> https://www.ietf.org/mailman/listinfo/martini
> >>
> > _______________________________________________
> > martini mailing list
> > martini@ietf.org
> > https://www.ietf.org/mailman/listinfo/martini
> >=20
> =

From gonzalo.camarillo@ericsson.com  Sun Mar 21 09:25:57 2010
Return-Path: <gonzalo.camarillo@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 941103A69ED for <martini@core3.amsl.com>; Sun, 21 Mar 2010 09:25:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.656
X-Spam-Level: 
X-Spam-Status: No, score=-101.656 tagged_above=-999 required=5 tests=[AWL=-1.046, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 0U2QnbmZnWFE for <martini@core3.amsl.com>; Sun, 21 Mar 2010 09:25:56 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id AC6173A69D9 for <martini@ietf.org>; Sun, 21 Mar 2010 09:25:39 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bf6ae000005bec-00-4ba648910556
Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 23.7B.23532.19846AB4; Sun, 21 Mar 2010 17:25:54 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 21 Mar 2010 17:24:31 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 21 Mar 2010 17:24:31 +0100
Received: from [131.160.126.142] (rvi2-126-142.lmf.ericsson.se [131.160.126.142]) by mail.lmf.ericsson.se (Postfix) with ESMTP id B59CB26B8; Sun, 21 Mar 2010 18:24:30 +0200 (EET)
Message-ID: <4BA6483D.2020402@ericsson.com>
Date: Sun, 21 Mar 2010 09:24:29 -0700
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org>	<A444A0F8084434499206E78C106220CABE982764@MCHP058A.global-ad.net>	<4BA38882.9000008@gmail.com> <A444A0F8084434499206E78C106220CAC21E6B91@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CAC21E6B91@MCHP058A.global-ad.net>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Mar 2010 16:24:31.0427 (UTC) FILETIME=[FC60B130:01CAC912]
X-Brightmail-Tracker: AAAAAA==
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #17: Desirable to align with existing standards
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: Sun, 21 Mar 2010 16:25:57 -0000

Hi,

well, I do not care who answers as long as the information is sent ;o)

Thanks,

Gonzalo

On 21/03/2010 7:20 AM, Elwell, John wrote:
> I assume this request is directed at Hans Erik.
> 
> John 
> 
>> -----Original Message-----
>> From: Gonzalo Camarillo [mailto:gcamaril@gmail.com] 
>> Sent: 19 March 2010 14:22
>> To: Elwell, John
>> Cc: martini@ietf.org
>> Subject: Re: [martini] #17: Desirable to align with existing standards
>>
>> Hi,
>>
>> could you please provide references to the ETSI and 3GPP 
>> specs mentioned
>> below?
>>
>> Thanks,
>>
>> Gonzalo
>>
>> On 19/03/2010 1:01 PM, Elwell, John wrote:
>>> As individual, I would remark that the market is already 
>> fragmented between SIP and IMS-SIP, which makes things difficult.
>>>
>>> As editor, I seek guidance from others on this one.
>>>
>>> John
>>>
>>>> -----Original Message-----
>>>> From: martini-bounces@ietf.org 
>>>> [mailto:martini-bounces@ietf.org] On Behalf Of martini 
>> issue tracker
>>>> Sent: 18 March 2010 22:21
>>>> To: ietf.hanserik@gmail.com
>>>> Cc: martini@ietf.org
>>>> Subject: [martini] #17: Desirable to align with existing standards
>>>>
>>>> #17: Desirable to align with existing standards
>>>> -------------------------------------+------------------------
>>>> --------------
>>>>  Reporter:  ietf.hanserik@...          |       Owner:            
>>>>      Type:  enhancement              |      Status:  new       
>>>>  Priority:  major                    |   Milestone:  milestone1
>>>> Component:  reqs                     |     Version:  1.0       
>>>>  Severity:  In WG Last Call          |    Keywords:            
>>>> -------------------------------------+------------------------
>>>> --------------
>>>>  DES5 - The mechanism SHOULD be aligned as much as possible 
>>>> with mechanisms
>>>>  already standardised in other SDO's like ETSI and 3GPP in order to
>>>>  prohibit a fragmentation of the market.
>>>>
>>>> -- 
>>>> Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/17>
>>>> martini <http://tools.ietf.org/martini/>
>>>>
>>>> _______________________________________________
>>>> martini mailing list
>>>> martini@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/martini
>>>>
>>> _______________________________________________
>>> martini mailing list
>>> martini@ietf.org
>>> https://www.ietf.org/mailman/listinfo/martini
>>>
>>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
> 


From spencer@wonderhamster.org  Sun Mar 21 13:41:05 2010
Return-Path: <spencer@wonderhamster.org>
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 6D1D63A680C for <martini@core3.amsl.com>; Sun, 21 Mar 2010 13:41:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.132
X-Spam-Level: *
X-Spam-Status: No, score=1.132 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, STOX_REPLY_TYPE=0.001]
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 FWfpsQM+3yuB for <martini@core3.amsl.com>; Sun, 21 Mar 2010 13:41:04 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id F00763A6813 for <martini@ietf.org>; Sun, 21 Mar 2010 13:41:02 -0700 (PDT)
Received: from S73602b ([130.129.24.155]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0Lp39Q-1NNQb60Qbs-00eqk9; Sun, 21 Mar 2010 16:41:15 -0400
Message-ID: <08244E6723F843F4BB4579F33DF4B1EF@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org>	<A444A0F8084434499206E78C106220CABE982764@MCHP058A.global-ad.net>	<4BA38882.9000008@gmail.com><A444A0F8084434499206E78C106220CAC21E6B91@MCHP058A.global-ad.net> <4BA6483D.2020402@ericsson.com>
Date: Sun, 21 Mar 2010 15:41:03 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX19YLmEb0nF24HyQx/1xJaSI38kRI9KqLjfjIC5 BnDec9xYJ970NSI2QSdXf+BBE/7QJVLlqB1ZZ/7AwLMnt+3R83 QSjl+oNRpibUtCXLwhNSNmEQXqp/5pHuXDONU07Qi8=
Cc: martini@ietf.org
Subject: Re: [martini] #17: Desirable to align with existing standards
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: Sun, 21 Mar 2010 20:41:05 -0000

Hi, Gonzalo,

John had added
   [ETSI TS 182 025]
              "ETSI TS 182 025 "Telecommunications and Internet
              converged Services and Protocols for Advanced Networking
              (TISPAN); Business trunking; Architecture and functional
              description"".as a reference in

http://tools.ietf.org/html/draft-ietf-martini-reqs-02 - I'm not smart about
ETSI, but I had hoped that specification was the appropriate reference :D

Thanks,

Spencer

> Hi,
>
> well, I do not care who answers as long as the information is sent ;o)
>
> Thanks,
>
> Gonzalo
>
> On 21/03/2010 7:20 AM, Elwell, John wrote:
>> I assume this request is directed at Hans Erik.
>>
>> John
>>
>>> -----Original Message-----
>>> From: Gonzalo Camarillo [mailto:gcamaril@gmail.com]
>>> Sent: 19 March 2010 14:22
>>> To: Elwell, John
>>> Cc: martini@ietf.org
>>> Subject: Re: [martini] #17: Desirable to align with existing standards
>>>
>>> Hi,
>>>
>>> could you please provide references to the ETSI and 3GPP
>>> specs mentioned
>>> below?
>>>
>>> Thanks,
>>>
>>> Gonzalo
>>>
>>> On 19/03/2010 1:01 PM, Elwell, John wrote:
>>>> As individual, I would remark that the market is already
>>> fragmented between SIP and IMS-SIP, which makes things difficult.
>>>>
>>>> As editor, I seek guidance from others on this one.
>>>>
>>>> John
>>>>
>>>>> -----Original Message-----
>>>>> From: martini-bounces@ietf.org
>>>>> [mailto:martini-bounces@ietf.org] On Behalf Of martini
>>> issue tracker
>>>>> Sent: 18 March 2010 22:21
>>>>> To: ietf.hanserik@gmail.com
>>>>> Cc: martini@ietf.org
>>>>> Subject: [martini] #17: Desirable to align with existing standards
>>>>>
>>>>> #17: Desirable to align with existing standards
>>>>> -------------------------------------+------------------------
>>>>> --------------
>>>>>  Reporter:  ietf.hanserik@...          |       Owner:
>>>>>      Type:  enhancement              |      Status:  new
>>>>>  Priority:  major                    |   Milestone:  milestone1
>>>>> Component:  reqs                     |     Version:  1.0
>>>>>  Severity:  In WG Last Call          |    Keywords:
>>>>> -------------------------------------+------------------------
>>>>> --------------
>>>>>  DES5 - The mechanism SHOULD be aligned as much as possible
>>>>> with mechanisms
>>>>>  already standardised in other SDO's like ETSI and 3GPP in order to
>>>>>  prohibit a fragmentation of the market.
>>>>>
>>>>> -- 
>>>>> Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/17>
>>>>> martini <http://tools.ietf.org/martini/>
>>>>>
>>>>> _______________________________________________
>>>>> martini mailing list
>>>>> martini@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/martini
>>>>>
>>>> _______________________________________________
>>>> martini mailing list
>>>> martini@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/martini
>>>>
>>>
>> _______________________________________________
>> martini mailing list
>> martini@ietf.org
>> https://www.ietf.org/mailman/listinfo/martini
>>
>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini


From john.elwell@siemens-enterprise.com  Sun Mar 21 14:09:29 2010
Return-Path: <john.elwell@siemens-enterprise.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 9A0303A6A1C for <martini@core3.amsl.com>; Sun, 21 Mar 2010 14:09:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.247
X-Spam-Level: 
X-Spam-Status: No, score=-0.247 tagged_above=-999 required=5 tests=[AWL=-1.378, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
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 o9AlXf3gLFkA for <martini@core3.amsl.com>; Sun, 21 Mar 2010 14:09:28 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 55A823A6980 for <martini@ietf.org>; Sun, 21 Mar 2010 14:09:25 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1288707; Sun, 21 Mar 2010 22:09:39 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id 057AF23F028E; Sun, 21 Mar 2010 22:09:38 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Sun, 21 Mar 2010 22:09:38 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Spencer Dawkins <spencer@wonderhamster.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Date: Sun, 21 Mar 2010 22:09:35 +0100
Thread-Topic: [martini] #17: Desirable to align with existing standards
Thread-Index: AcrJNtxxA6VD+LYYTquq2AHM3yhVSQAA3gPQ
Message-ID: <A444A0F8084434499206E78C106220CADDE42862@MCHP058A.global-ad.net>
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982764@MCHP058A.global-ad.net> <4BA38882.9000008@gmail.com><A444A0F8084434499206E78C106220CAC21E6B91@MCHP058A.global-ad.net> <4BA6483D.2020402@ericsson.com> <08244E6723F843F4BB4579F33DF4B1EF@china.huawei.com>
In-Reply-To: <08244E6723F843F4BB4579F33DF4B1EF@china.huawei.com>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #17: Desirable to align with existing standards
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: Sun, 21 Mar 2010 21:09:29 -0000

Yes, I did reference this, but the nature of that standard (delta to a delt=
a to a delta) is such that it requires a whole lot more digging to identify=
 the specific aspects of the TISPAN/3GPP solution that that are germane to =
the issues we are talking about. I was hoping that Hans Erik could help us =
to nail down particular aspects of the solution, with appropriate reference=
s, that he believes we need to align with.

John=20

> -----Original Message-----
> From: Spencer Dawkins [mailto:spencer@wonderhamster.org]=20
> Sent: 21 March 2010 20:41
> To: Gonzalo Camarillo; Elwell, John
> Cc: martini@ietf.org
> Subject: Re: [martini] #17: Desirable to align with existing standards
>=20
> Hi, Gonzalo,
>=20
> John had added
>    [ETSI TS 182 025]
>               "ETSI TS 182 025 "Telecommunications and Internet
>               converged Services and Protocols for Advanced Networking
>               (TISPAN); Business trunking; Architecture and functional
>               description"".as a reference in
>=20
> http://tools.ietf.org/html/draft-ietf-martini-reqs-02 - I'm=20
> not smart about
> ETSI, but I had hoped that specification was the appropriate=20
> reference :D
>=20
> Thanks,
>=20
> Spencer
>=20
> > Hi,
> >
> > well, I do not care who answers as long as the information=20
> is sent ;o)
> >
> > Thanks,
> >
> > Gonzalo
> >
> > On 21/03/2010 7:20 AM, Elwell, John wrote:
> >> I assume this request is directed at Hans Erik.
> >>
> >> John
> >>
> >>> -----Original Message-----
> >>> From: Gonzalo Camarillo [mailto:gcamaril@gmail.com]
> >>> Sent: 19 March 2010 14:22
> >>> To: Elwell, John
> >>> Cc: martini@ietf.org
> >>> Subject: Re: [martini] #17: Desirable to align with=20
> existing standards
> >>>
> >>> Hi,
> >>>
> >>> could you please provide references to the ETSI and 3GPP
> >>> specs mentioned
> >>> below?
> >>>
> >>> Thanks,
> >>>
> >>> Gonzalo
> >>>
> >>> On 19/03/2010 1:01 PM, Elwell, John wrote:
> >>>> As individual, I would remark that the market is already
> >>> fragmented between SIP and IMS-SIP, which makes things difficult.
> >>>>
> >>>> As editor, I seek guidance from others on this one.
> >>>>
> >>>> John
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: martini-bounces@ietf.org
> >>>>> [mailto:martini-bounces@ietf.org] On Behalf Of martini
> >>> issue tracker
> >>>>> Sent: 18 March 2010 22:21
> >>>>> To: ietf.hanserik@gmail.com
> >>>>> Cc: martini@ietf.org
> >>>>> Subject: [martini] #17: Desirable to align with=20
> existing standards
> >>>>>
> >>>>> #17: Desirable to align with existing standards
> >>>>> -------------------------------------+------------------------
> >>>>> --------------
> >>>>>  Reporter:  ietf.hanserik@...          |       Owner:
> >>>>>      Type:  enhancement              |      Status:  new
> >>>>>  Priority:  major                    |   Milestone:  milestone1
> >>>>> Component:  reqs                     |     Version:  1.0
> >>>>>  Severity:  In WG Last Call          |    Keywords:
> >>>>> -------------------------------------+------------------------
> >>>>> --------------
> >>>>>  DES5 - The mechanism SHOULD be aligned as much as possible
> >>>>> with mechanisms
> >>>>>  already standardised in other SDO's like ETSI and 3GPP=20
> in order to
> >>>>>  prohibit a fragmentation of the market.
> >>>>>
> >>>>> --=20
> >>>>> Ticket URL:=20
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/17>
> >>>>> martini <http://tools.ietf.org/martini/>
> >>>>>
> >>>>> _______________________________________________
> >>>>> martini mailing list
> >>>>> martini@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/martini
> >>>>>
> >>>> _______________________________________________
> >>>> martini mailing list
> >>>> martini@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/martini
> >>>>
> >>>
> >> _______________________________________________
> >> martini mailing list
> >> martini@ietf.org
> >> https://www.ietf.org/mailman/listinfo/martini
> >>
> >
> > _______________________________________________
> > martini mailing list
> > martini@ietf.org
> > https://www.ietf.org/mailman/listinfo/martini
>=20
> =

From HKaplan@acmepacket.com  Sun Mar 21 16:26:10 2010
Return-Path: <HKaplan@acmepacket.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 569133A68AE for <martini@core3.amsl.com>; Sun, 21 Mar 2010 16:26:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.433
X-Spam-Level: 
X-Spam-Status: No, score=-0.433 tagged_above=-999 required=5 tests=[AWL=-2.164, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_31=0.6]
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 7bC3RjmoOcmY for <martini@core3.amsl.com>; Sun, 21 Mar 2010 16:26:09 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id D2C073A68AB for <martini@ietf.org>; Sun, 21 Mar 2010 16:26:08 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Sun, 21 Mar 2010 19:26:24 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Sun, 21 Mar 2010 19:26:16 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Brian Lindsay <blindsay@nortel.com>, Tyler Parkin <tyler@foxfam.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, Adam Roach <adam@nostrum.com>, Spencer Dawkins <spencer@wonderhamster.org>
Date: Sun, 21 Mar 2010 19:26:07 -0400
Thread-Topic: [martini] Middlebox needs - admitting inbound requests
Thread-Index: Acq3DhVedCe9ueLhSy6la+jrT0lQfwBp1v2wBCWBabA=
Message-ID: <430FC6BDED356B4C8498F634416644A91A79CD1821@mail>
References: <C7AC4291.14C39%adam@nostrum.com><99BF4620352B4F9C9E090F9004C31924@china.huawei.com><4B86F875.6070902@nostrum.com><00b101cab66c$3ce34150$430510ac@CORPORATE.VOX.NET><09B7DBFE70A9E24BBB21689DAD3A06141CB0F52A@zcarhxm1.corp.nortel.com> <00ca01cab67a$7fd21460$430510ac@CORPORATE.VOX.NET> <A444A0F8084434499206E78C106220CABBB22E97@MCHP058A.global-ad.net> <000901cab6f5$968a9df0$010c030a@CORPORATE.VOX.NET> <A444A0F8084434499206E78C106220CABBB232D7@MCHP058A.global-ad.net> <008201cab70e$0d82c6e0$010c030a@CORPORATE.VOX.NET> <09B7DBFE70A9E24BBB21689DAD3A06141CB5DF53@zcarhxm1.corp.nortel.com>
In-Reply-To: <09B7DBFE70A9E24BBB21689DAD3A06141CB5DF53@zcarhxm1.corp.nortel.com>
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
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, MARTINI <martini@ietf.org>
Subject: Re: [martini] Middlebox needs - admitting inbound requests
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: Sun, 21 Mar 2010 23:26:10 -0000

I think having SBC's use unique ports per PBX would be a really bad way to =
go.  I don't know what other's experiences were with that, but we've got a =
mode setting for doing it that way because some registrars required it be d=
one that way, but it had really nasty issues merely because of that mechani=
sm.  Like you can't get more than ~60k subscribers per IP; if UA's move/go-=
away you have to decide when you can reclaim ports; if you're completely re=
booted then the ports get allocated in a different order which confuses reg=
istrars; if you need to switch to TCP for some messages/cases then the mapp=
ing can't possibly be kept; you get the idea.

I think it's been discussed before on this list (or maybe it was in SIP-For=
um), that one clean way would be for the SBC to insert a Path header identi=
fying itself and a cookie, and that cookie provide the route or registratio=
n-cache-key information it needs.  Or it can insert a Path with pretty much=
 anything it needs - as long as the core registrar/proxies support Path and=
 thus reflect the received Path list by adding them as Route header lists f=
or the requests they route to the PBX through the SBC.

Of course some things in Martini may well require changes in middleboxes, b=
ut that's why there's the option-tag. :)

-hadriel

> -----Original Message-----
> From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behal=
f
> Of Brian Lindsay
> Sent: Sunday, February 28, 2010 3:52 PM
> To: Tyler Parkin; Elwell, John; Adam Roach; Spencer Dawkins
> Cc: Bernard Aboba; MARTINI
> Subject: Re: [martini] Middlebox needs - admitting inbound requests
>=20
> Hi Tyler,
>=20
>   I believe some SBCs that "NAT" as you describe would (or could) use a
> unique port on the northbound side per registered entity. So the SBC
> would be able to maintain a mapping from the client-side contact/routing
> info to a unique northbound address/port that it would receive requests
> on (for requests towards the SIP PBX). In this case, there shouldn't be
> any problems routing the request.
>=20
>   Also, I think the MARTINI-Shaken approach wouldn't have a problem in
> this case either, since the domain portion of the request uri (from the
> "SSP") contains a domain name representing the enterprise/PBX, rather
> than an IP address derived from the contact.
>=20
>   Thanks
>      Brian
>=20
> -----Original Message-----
> From: Tyler Parkin [mailto:tyler@foxfam.com]
> Sent: Friday, February 26, 2010 1:04 PM
> To: Elwell, John; Lindsay, Brian (CAR:AR00); Adam Roach; Spencer Dawkins
> Cc: Bernard Aboba; MARTINI
> Subject: Re: [martini] Middlebox needs - admitting inbound requests
>=20
>=20
> > ----- Original Message -----
> > From: "Elwell, John" <john.elwell@siemens-enterprise.com>
> > To: "Tyler Parkin" <tyler@foxfam.com>; "Brian Lindsay"
> > <blindsay@nortel.com>; "Adam Roach" <adam@nostrum.com>; "Spencer
> > Dawkins"
> > <spencer@wonderhamster.org>
> > Cc: "Bernard Aboba" <bernard_aboba@hotmail.com>; "MARTINI"
> > <martini@ietf.org>
> > Sent: Friday, February 26, 2010 5:34 AM
> > Subject: RE: [martini] Middlebox needs - admitting inbound requests
> >
> >
> > Tyler,
> >
> > I found this thread a little mixed up between outbound requests from
> > the PBX and inbound requests  to the PBX, so I am not sure I
> > understood everything.
> > [tyler] sorry for the confusion, I think we're looking at it in
> > different directions... inbound to me is inbound to the SSP, where to
> > you inbound is to the PBX.  I guess we'll stick w/ inbound =3D to the
> > PBX
> >
> > As far as inbound request are concerned, I think with gin-01 the
> > problems you raise should be solvable, but it perhaps requires use of
> > Proxy-Require, as already discussed. The middlebox does not need to
> > know exactly which E.164s are implicitly registered, but when it gets
> > a request to the PBX's IP address (presumably with Route indicating
> > the IP address of the middlebox) it should assume the E.164 in the
> > user part is indeed a registered AOR.
> > [tyler] my point is that the middlebox doesn't get a request to the
> > PBX's IP address.
> [JRE] Why not? If the Contact URI contains the IP address (as in
> gin-01), this will be registered at the registrar and will be returned
> as the target of an inbound request to the PBX.
>=20
> > The softswitch/registrar generating the call doesn't know the PBX's IP
>=20
> > because it was masked during the initial registration.
> [JRE] Why would it be masked? I understand that the registrar would not
> see the IP address at the transport level from which the REGISTER
> request arrived at the middlebox, but it would see the IP address in the
> Contact URI.
> [Tyler] In most scenarios where a middlebox (aka SBC) exists, the SBC
> performs two-way NAT functions, and NAT's the headers/URI's for inbound
> and outbound messaging.  Therefore, a request received on the public
> side from user@PBXIP is sent to the registrar as user@SBCPRIVATEIP.  The
> oposite direction (SSP -> PBX) is received by the SBC as user@SSPIP and
> NAT'd to user@SBCPUBLICIP.
>=20
> > Any
> > requests from from the registrar/softswitch to the middlebox (destined
>=20
> > for the PBX) will only have user@middlebox, perhaps w/ a cookie.
> > The middelbox
> > needs to map user@middlebox to whatever IP/host originally registered.
> > Today, the middlebox keeps a cache where the initial (individual)
> > registration might be user@1.1.1.1, and the registration forwarded to
> > the registrar is user@2.2.2.2.  That way when the registrar sends a
> > request to the middlebox for user@2.2.2.2 it maps it to user@1.1.1.1
> > and all is good.
> > If the middelbox doesn't have knowledge of the user (because of
> > implicit),
> [JRE] Are you suggesting that each user behind the PBX would register
> with a different IP address, so you need to know whether it is user1 or
> user2 in order to send requests to 11.11.11.11 or 22.22.22.22? If so,
> that is not the scenario that MARTINI is addressing. MARTINI is
> addressing the case where requests to user1, user2 etc. on a given PBX
> all need to be routed to the PBX's IP address. So as long as the
> middlebox knows the request needs to go to the PBX, it doesn't need to
> know that particular user.
> [Tyler] Agreed, I shouldn't have used the term user.  The middlebox in
> this scenario wouldn't care about individual users, it's point of
> contact is the PBX.  All PBX's send register requests to the middlebox
> from different IP's/domains, granted.  After NAT, however, all the
> requests from the SBC to the registrar appear to come from the same IP.
> We NAT in both directions, which is pretty standard, so we don't expose
> core equipment to the public, and we don't expose end user IP's to
> peers.  Plus it allows virtual route tables internally and resolves any
> issues with overlapping address space.
>=20
> > it can't make the mapping unless it has something else to associate to
>=20
> > the original implicit reg (like a cookie, or knowledge of the
> > extensions).
> >
> > Now concerning outbound requests (this was what my earlier message was
>=20
> > about, although somewhere further back that got brought across to this
>=20
> > thread rather than the thread concerning outbound requests, so the
> > thread title was wrong). Assuming an entity has knowledge of
> > registered E.164 numbers, it is not clear to me how it would deal with
>=20
> > a request where the From/PAI in the request from the PBX is not one of
>=20
> > the implicitly registered ones. This can arise, for example, if the
> > request originates elsewhere in the enterprise and "breaks out" to the
>=20
> > SSP via this particular PBX. Or if the call originated elsewhere and
> > was forwarded by the PBX to the SSP. I appreciate that there may be
> > some arrangements between PBX and SSP where this is forbidden by
> > policy, but in the general case I would expect it to work, so that the
>=20
> > callee has a correct AOR to which it can make a return call.
> > [tyler] methods dealing with this situation today (A calls B, B
> > forwards the call to C) would use from=3DA and PAI=3DB, where B is a
> > registered endpoint (and billable by the SSP).  Not sure if that's
> > what you're asking?
> [JRE] Yes, that was what I was asking, and I know that it sometimes
> works the way you describe, but this is bad because PAI=3DB is wrong - it
> is not compliant with RFC 3325, since it is not the source of the
> request. If the callee used that to make a return call, the return call
> would arrive at the wrong place. For example, if a customer calls me on
> my office number and the PBX forwards it to my home via the SSP, if my
> phone stores the PAI as the caller's number and I try to make a return
> call, the return call goes to my office phone, not to my customer.
> [Tyler] The source of the forward leg of the call is B, not A.  Calling
> area requirements and n11 need to be based on B.  Why would the callee
> use PAI to return a call?  That would be in violation of 3325 as well
> since it would obviate any callerid blocking/suppression requirements.
> I guess whether the PBX should strip PAI before sending it to your phone
> is arguable.  Agreed, using PAI to assert a different ID than From
> (where from isn't private) might not strictly adhere to 3325, but I
> think alternate ID's vs suppressed ID's is splitting hairs a little.
>=20
> John
>=20
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini

From ietf.hanserik@gmail.com  Mon Mar 22 02:12:23 2010
Return-Path: <ietf.hanserik@gmail.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 839A93A681A for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.046
X-Spam-Level: 
X-Spam-Status: No, score=0.046 tagged_above=-999 required=5 tests=[AWL=-1.086,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 QNlXrBgVwl5g for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:12:22 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by core3.amsl.com (Postfix) with ESMTP id C90363A67F6 for <martini@ietf.org>; Mon, 22 Mar 2010 02:12:21 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 4so402172eyf.51 for <martini@ietf.org>; Mon, 22 Mar 2010 02:12:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=LIMUbmv8H7Cc1ST9lljqjY5uQR7X0mf2Fkrgy7Iuk4E=; b=TN7zni6licM4nZK/28HsmGfHlOw64Pav2qcP7lG9BHO+XHws0d6OF8QcuR5DbOerm2 cVg74yoXH6408Y38Qe1jRWXeP5OQeXR9St5ahlRHvOteXoozUwzopVP657qC/X3xCVZW iMUy0j0QcyYVetYjq268U8G4jz9MPjQQDvPRE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=FWg2FnWaqwLgtBXO4/yG+4ZwXwAvzP9+YUn3VkzBt4LuqCkZ2UvGKfCFRHB+ScgcKG nhVuyjRYnZnnnJzFYJIxo9ybUsTbNPhbFSJhbY3Sbv8e4ZS5jX3S2x3RKsvw3wej0E3N 1esDC4GkNyKm4RTbFTt9dv/GPFzIBc94roHJg=
MIME-Version: 1.0
Received: by 10.213.100.7 with SMTP id w7mr1985180ebn.23.1269249154043; Mon,  22 Mar 2010 02:12:34 -0700 (PDT)
In-Reply-To: <08244E6723F843F4BB4579F33DF4B1EF@china.huawei.com>
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982764@MCHP058A.global-ad.net> <4BA38882.9000008@gmail.com> <A444A0F8084434499206E78C106220CAC21E6B91@MCHP058A.global-ad.net> <4BA6483D.2020402@ericsson.com> <08244E6723F843F4BB4579F33DF4B1EF@china.huawei.com>
Date: Mon, 22 Mar 2010 10:12:33 +0100
Message-ID: <9ae56b1e1003220212l3f44b540h499012c7009ceb07@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
Content-Type: multipart/alternative; boundary=00504502d037f5501f048260182b
Cc: martini@ietf.org
Subject: Re: [martini] #17: Desirable to align with existing standards
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, 22 Mar 2010 09:12:23 -0000

--00504502d037f5501f048260182b
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Hi following are the specs related to the subject, where indeed 182 025
contains the protocol solution.

ETSI TS 181 019: "Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN); Business Communication
Requirements".

ETSI TS 182 023: "Telecommunications and Internet Converged Services and
Protocols for Advanced Networking (TISPAN); Core and Enterprise NGN
Interaction Scenarios and Architectural Requirements".

ETSI TS 182 025 "Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN); Business trunking; Architecture
and functional description

3GPP I guess it is 24.229. But others are better equipped to answer that
question.

Best Regards,
/Hans Erik van Elburg

On Sun, Mar 21, 2010 at 9:41 PM, Spencer Dawkins
<spencer@wonderhamster.org>wrote:

> Hi, Gonzalo,
>
> John had added
>  [ETSI TS 182 025]
>             "ETSI TS 182 025 "Telecommunications and Internet
>             converged Services and Protocols for Advanced Networking
>             (TISPAN); Business trunking; Architecture and functional
>             description"".as a reference in
>
> http://tools.ietf.org/html/draft-ietf-martini-reqs-02 - I'm not smart
> about
> ETSI, but I had hoped that specification was the appropriate reference :D
>
> Thanks,
>
> Spencer
>
>
>  Hi,
>>
>> well, I do not care who answers as long as the information is sent ;o)
>>
>> Thanks,
>>
>> Gonzalo
>>
>> On 21/03/2010 7:20 AM, Elwell, John wrote:
>>
>>> I assume this request is directed at Hans Erik.
>>>
>>> John
>>>
>>>  -----Original Message-----
>>>> From: Gonzalo Camarillo [mailto:gcamaril@gmail.com]
>>>> Sent: 19 March 2010 14:22
>>>> To: Elwell, John
>>>> Cc: martini@ietf.org
>>>> Subject: Re: [martini] #17: Desirable to align with existing standards
>>>>
>>>> Hi,
>>>>
>>>> could you please provide references to the ETSI and 3GPP
>>>> specs mentioned
>>>> below?
>>>>
>>>> Thanks,
>>>>
>>>> Gonzalo
>>>>
>>>> On 19/03/2010 1:01 PM, Elwell, John wrote:
>>>>
>>>>> As individual, I would remark that the market is already
>>>>>
>>>> fragmented between SIP and IMS-SIP, which makes things difficult.
>>>>
>>>>>
>>>>> As editor, I seek guidance from others on this one.
>>>>>
>>>>> John
>>>>>
>>>>>  -----Original Message-----
>>>>>> From: martini-bounces@ietf.org
>>>>>> [mailto:martini-bounces@ietf.org] On Behalf Of martini
>>>>>>
>>>>> issue tracker
>>>>
>>>>> Sent: 18 March 2010 22:21
>>>>>> To: ietf.hanserik@gmail.com
>>>>>> Cc: martini@ietf.org
>>>>>> Subject: [martini] #17: Desirable to align with existing standards
>>>>>>
>>>>>> #17: Desirable to align with existing standards
>>>>>> -------------------------------------+------------------------
>>>>>> --------------
>>>>>>  Reporter:  ietf.hanserik@...          |       Owner:
>>>>>>     Type:  enhancement              |      Status:  new
>>>>>>  Priority:  major                    |   Milestone:  milestone1
>>>>>> Component:  reqs                     |     Version:  1.0
>>>>>>  Severity:  In WG Last Call          |    Keywords:
>>>>>> -------------------------------------+------------------------
>>>>>> --------------
>>>>>>  DES5 - The mechanism SHOULD be aligned as much as possible
>>>>>> with mechanisms
>>>>>>  already standardised in other SDO's like ETSI and 3GPP in order to
>>>>>>  prohibit a fragmentation of the market.
>>>>>>
>>>>>> --
>>>>>> Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/17>
>>>>>> martini <http://tools.ietf.org/martini/>
>>>>>>
>>>>>> _______________________________________________
>>>>>> martini mailing list
>>>>>> martini@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/martini
>>>>>>
>>>>>>  _______________________________________________
>>>>> martini mailing list
>>>>> martini@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/martini
>>>>>
>>>>>
>>>>  _______________________________________________
>>> martini mailing list
>>> martini@ietf.org
>>> https://www.ietf.org/mailman/listinfo/martini
>>>
>>>
>> _______________________________________________
>> martini mailing list
>> martini@ietf.org
>> https://www.ietf.org/mailman/listinfo/martini
>>
>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>

--00504502d037f5501f048260182b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>Hi following are the specs related to the subject, where indeed =
182 025 contains the protocol solution.<br><br><meta http-equiv=3D"Content-=
Type" content=3D"text/html; charset=3Dutf-8"><meta name=3D"ProgId" content=
=3D"Word.Document"><meta name=3D"Generator" content=3D"Microsoft Word 11"><=
meta name=3D"Originator" content=3D"Microsoft Word 11"><link rel=3D"File-Li=
st" href=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5CTemp%5Cmsoh=
tml1%5C01%5Cclip_filelist.xml"><style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:9.0pt;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-layout-grid-align:none;
	punctuation-wrap:simple;
	text-autospace:none;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-ansi-language:EN-GB;
	mso-fareast-language:EN-US;}
p.EX, li.EX, div.EX
	{mso-style-name:EX;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:9.0pt;
	margin-left:85.1pt;
	text-indent:-70.9pt;
	mso-pagination:widow-orphan lines-together;
	mso-layout-grid-align:none;
	punctuation-wrap:simple;
	text-autospace:none;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-ansi-language:EN-GB;
	mso-fareast-language:EN-US;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>ETSI TS 181 019: &quot;Telecommunications and Internet converged Se=
rvices and Protocols for Advanced Networking (TISPAN); Business Communicati=
on Requirements&quot;.<br><br><meta http-equiv=3D"Content-Type" content=3D"=
text/html; charset=3Dutf-8"><meta name=3D"ProgId" content=3D"Word.Document"=
><meta name=3D"Generator" content=3D"Microsoft Word 11"><meta name=3D"Origi=
nator" content=3D"Microsoft Word 11"><link rel=3D"File-List" href=3D"file:/=
//C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_f=
ilelist.xml"><style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:9.0pt;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-layout-grid-align:none;
	punctuation-wrap:simple;
	text-autospace:none;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-ansi-language:EN-GB;
	mso-fareast-language:EN-US;}
p.EX, li.EX, div.EX
	{mso-style-name:EX;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:9.0pt;
	margin-left:85.1pt;
	text-indent:-70.9pt;
	mso-pagination:widow-orphan lines-together;
	mso-layout-grid-align:none;
	punctuation-wrap:simple;
	text-autospace:none;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-ansi-language:EN-GB;
	mso-fareast-language:EN-US;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>ETSI TS 182 023: &quot;Telecommunications and Internet Converged Se=
rvices and Protocols for Advanced Networking (TISPAN); Core and Enterprise =
NGN Interaction Scenarios and Architectural Requirements&quot;.<br><br>
ETSI TS 182 025 &quot;Telecommunications and Internet converged Services an=
d Protocols for Advanced Networking (TISPAN); Business trunking; Architectu=
re and functional description<br>
<br>3GPP I guess it is 24.229. But others are better equipped to answer tha=
t question.<br><br>Best Regards,<br>/Hans Erik van Elburg<br>
<br><div class=3D"gmail_quote">On Sun, Mar 21, 2010 at 9:41 PM, Spencer Daw=
kins <span dir=3D"ltr">&lt;<a href=3D"mailto:spencer@wonderhamster.org">spe=
ncer@wonderhamster.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, =
204, 204); padding-left: 1ex;">
Hi, Gonzalo,<br>
<br>
John had added<br>
 =A0[ETSI TS 182 025]<br>
 =A0 =A0 =A0 =A0 =A0 =A0 &quot;ETSI TS 182 025 &quot;Telecommunications and=
 Internet<br>
 =A0 =A0 =A0 =A0 =A0 =A0 converged Services and Protocols for Advanced Netw=
orking<br>
 =A0 =A0 =A0 =A0 =A0 =A0 (TISPAN); Business trunking; Architecture and func=
tional<br>
 =A0 =A0 =A0 =A0 =A0 =A0 description&quot;&quot;.as a reference in<br>
<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-martini-reqs-02" target=3D=
"_blank">http://tools.ietf.org/html/draft-ietf-martini-reqs-02</a> - I&#39;=
m not smart about<br>
ETSI, but I had hoped that specification was the appropriate reference :D<b=
r>
<br>
Thanks,<br><font color=3D"#888888">
<br>
Spencer</font><div><div></div><div class=3D"h5"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi,<br>
<br>
well, I do not care who answers as long as the information is sent ;o)<br>
<br>
Thanks,<br>
<br>
Gonzalo<br>
<br>
On 21/03/2010 7:20 AM, Elwell, John wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I assume this request is directed at Hans Erik.<br>
<br>
John<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
-----Original Message-----<br>
From: Gonzalo Camarillo [mailto:<a href=3D"mailto:gcamaril@gmail.com" targe=
t=3D"_blank">gcamaril@gmail.com</a>]<br>
Sent: 19 March 2010 14:22<br>
To: Elwell, John<br>
Cc: <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org<=
/a><br>
Subject: Re: [martini] #17: Desirable to align with existing standards<br>
<br>
Hi,<br>
<br>
could you please provide references to the ETSI and 3GPP<br>
specs mentioned<br>
below?<br>
<br>
Thanks,<br>
<br>
Gonzalo<br>
<br>
On 19/03/2010 1:01 PM, Elwell, John wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
As individual, I would remark that the market is already<br>
</blockquote>
fragmented between SIP and IMS-SIP, which makes things difficult.<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
As editor, I seek guidance from others on this one.<br>
<br>
John<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
-----Original Message-----<br>
From: <a href=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">martini=
-bounces@ietf.org</a><br>
[mailto:<a href=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">marti=
ni-bounces@ietf.org</a>] On Behalf Of martini<br>
</blockquote></blockquote>
issue tracker<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><blockquote class=
=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid=
 rgb(204, 204, 204); padding-left: 1ex;">

Sent: 18 March 2010 22:21<br>
To: <a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">ietf.hanse=
rik@gmail.com</a><br>
Cc: <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org<=
/a><br>
Subject: [martini] #17: Desirable to align with existing standards<br>
<br>
#17: Desirable to align with existing standards<br>
-------------------------------------+------------------------<br>
--------------<br>
=A0Reporter: =A0ietf.hanserik@... =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0 Owner:<b=
r>
 =A0 =A0 Type: =A0enhancement =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0Statu=
s: =A0new<br>
=A0Priority: =A0major =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 Mileston=
e: =A0milestone1<br>
Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 Versio=
n: =A01.0<br>
=A0Severity: =A0In WG Last Call =A0 =A0 =A0 =A0 =A0| =A0 =A0Keywords:<br>
-------------------------------------+------------------------<br>
--------------<br>
=A0DES5 - The mechanism SHOULD be aligned as much as possible<br>
with mechanisms<br>
=A0already standardised in other SDO&#39;s like ETSI and 3GPP in order to<b=
r>
=A0prohibit a fragmentation of the market.<br>
<br>
-- <br>
Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticke=
t/17" target=3D"_blank">http://trac.tools.ietf.org/wg/martini/trac/ticket/1=
7</a>&gt;<br>
martini &lt;<a href=3D"http://tools.ietf.org/martini/" target=3D"_blank">ht=
tp://tools.ietf.org/martini/</a>&gt;<br>
<br>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
<br>
</blockquote>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
<br>
</blockquote>
<br>
</blockquote>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
<br>
</blockquote>
<br>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
</blockquote>
<br>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
</div></div></blockquote></div><br>

--00504502d037f5501f048260182b--

From ietf.hanserik@gmail.com  Mon Mar 22 02:19:40 2010
Return-Path: <ietf.hanserik@gmail.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 96BB93A6818 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.224
X-Spam-Level: 
X-Spam-Status: No, score=0.224 tagged_above=-999 required=5 tests=[AWL=-0.722,  BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 8MPfS1sAbgbP for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:19:38 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by core3.amsl.com (Postfix) with ESMTP id 3CC0B3A6926 for <martini@ietf.org>; Mon, 22 Mar 2010 02:19:19 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 4so402504eyf.51 for <martini@ietf.org>; Mon, 22 Mar 2010 02:19:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=yfFhqOJcW2LTV67v83xTt0OLNf1xgYmYSBKyb5wtZu8=; b=NAi/n5aLWIyG9JJ/S8Co2VPZHnuFO4ett4JjTritafZf+AkjNJmYEkw67sAutYpd7B KsfcvjznEPBEOetkisfGJmGYXGf3Jsxbd3H1gXMPpFvwwfAKIqIM/6JOGq55o1iCm0NS Rl9tUADJ0Q1Rb+c8nX6kfObThT8/UDvHlCVHI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=aXcnRkv/JDiuHLIDV45eOj/7dK4emN7dgbN6At7zqLfylsDZlEolK6wAfikgJe1KaP 7Gt+R0wsEVGVojixIqOg4yYWIpVl37zKbfvyogMeHnYHbswiwfmF21Sl7PmuiAfpjyyo swcn/xbDdbZW6tu4/8eNiM8bpHq0RbNSD0pds=
MIME-Version: 1.0
Received: by 10.213.34.79 with HTTP; Mon, 22 Mar 2010 02:19:24 -0700 (PDT)
In-Reply-To: <A444A0F8084434499206E78C106220CADDE42862@MCHP058A.global-ad.net>
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982764@MCHP058A.global-ad.net> <4BA38882.9000008@gmail.com> <A444A0F8084434499206E78C106220CAC21E6B91@MCHP058A.global-ad.net> <4BA6483D.2020402@ericsson.com> <08244E6723F843F4BB4579F33DF4B1EF@china.huawei.com> <A444A0F8084434499206E78C106220CADDE42862@MCHP058A.global-ad.net>
Date: Mon, 22 Mar 2010 10:19:24 +0100
Received: by 10.213.52.13 with SMTP id f13mr2812666ebg.44.1269249564656; Mon,  22 Mar 2010 02:19:24 -0700 (PDT)
Message-ID: <9ae56b1e1003220219o34769006h591b3c21451e31f@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Content-Type: multipart/alternative; boundary=00163602601f6ecf3a048260315a
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #17: Desirable to align with existing standards
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, 22 Mar 2010 09:19:40 -0000

--00163602601f6ecf3a048260315a
Content-Type: text/plain; charset=ISO-8859-1

I think that a lot of valid issues have been raised with the existing
proposed solution and I have nothing against solving those. I have a problem
with a solution that can only handle E.164 numbers and can't even deliver
the other variants of calls or requires a completely different solution. And
with that my main concern is the method of constructing the new Request URI.
If people want to use that solution they can do so anyway as it is legal
according to RFC3261, you don't need an RFC for that.

BR,
/Hans Erik van Elburg

On Sun, Mar 21, 2010 at 10:09 PM, Elwell, John <
john.elwell@siemens-enterprise.com> wrote:

> Yes, I did reference this, but the nature of that standard (delta to a
> delta to a delta) is such that it requires a whole lot more digging to
> identify the specific aspects of the TISPAN/3GPP solution that that are
> germane to the issues we are talking about. I was hoping that Hans Erik
> could help us to nail down particular aspects of the solution, with
> appropriate references, that he believes we need to align with.
>
> John
>
> > -----Original Message-----
> > From: Spencer Dawkins [mailto:spencer@wonderhamster.org]
> > Sent: 21 March 2010 20:41
> > To: Gonzalo Camarillo; Elwell, John
> > Cc: martini@ietf.org
> > Subject: Re: [martini] #17: Desirable to align with existing standards
> >
> > Hi, Gonzalo,
> >
> > John had added
> >    [ETSI TS 182 025]
> >               "ETSI TS 182 025 "Telecommunications and Internet
> >               converged Services and Protocols for Advanced Networking
> >               (TISPAN); Business trunking; Architecture and functional
> >               description"".as a reference in
> >
> > http://tools.ietf.org/html/draft-ietf-martini-reqs-02 - I'm
> > not smart about
> > ETSI, but I had hoped that specification was the appropriate
> > reference :D
> >
> > Thanks,
> >
> > Spencer
> >
> > > Hi,
> > >
> > > well, I do not care who answers as long as the information
> > is sent ;o)
> > >
> > > Thanks,
> > >
> > > Gonzalo
> > >
> > > On 21/03/2010 7:20 AM, Elwell, John wrote:
> > >> I assume this request is directed at Hans Erik.
> > >>
> > >> John
> > >>
> > >>> -----Original Message-----
> > >>> From: Gonzalo Camarillo [mailto:gcamaril@gmail.com]
> > >>> Sent: 19 March 2010 14:22
> > >>> To: Elwell, John
> > >>> Cc: martini@ietf.org
> > >>> Subject: Re: [martini] #17: Desirable to align with
> > existing standards
> > >>>
> > >>> Hi,
> > >>>
> > >>> could you please provide references to the ETSI and 3GPP
> > >>> specs mentioned
> > >>> below?
> > >>>
> > >>> Thanks,
> > >>>
> > >>> Gonzalo
> > >>>
> > >>> On 19/03/2010 1:01 PM, Elwell, John wrote:
> > >>>> As individual, I would remark that the market is already
> > >>> fragmented between SIP and IMS-SIP, which makes things difficult.
> > >>>>
> > >>>> As editor, I seek guidance from others on this one.
> > >>>>
> > >>>> John
> > >>>>
> > >>>>> -----Original Message-----
> > >>>>> From: martini-bounces@ietf.org
> > >>>>> [mailto:martini-bounces@ietf.org] On Behalf Of martini
> > >>> issue tracker
> > >>>>> Sent: 18 March 2010 22:21
> > >>>>> To: ietf.hanserik@gmail.com
> > >>>>> Cc: martini@ietf.org
> > >>>>> Subject: [martini] #17: Desirable to align with
> > existing standards
> > >>>>>
> > >>>>> #17: Desirable to align with existing standards
> > >>>>> -------------------------------------+------------------------
> > >>>>> --------------
> > >>>>>  Reporter:  ietf.hanserik@...          |       Owner:
> > >>>>>      Type:  enhancement              |      Status:  new
> > >>>>>  Priority:  major                    |   Milestone:  milestone1
> > >>>>> Component:  reqs                     |     Version:  1.0
> > >>>>>  Severity:  In WG Last Call          |    Keywords:
> > >>>>> -------------------------------------+------------------------
> > >>>>> --------------
> > >>>>>  DES5 - The mechanism SHOULD be aligned as much as possible
> > >>>>> with mechanisms
> > >>>>>  already standardised in other SDO's like ETSI and 3GPP
> > in order to
> > >>>>>  prohibit a fragmentation of the market.
> > >>>>>
> > >>>>> --
> > >>>>> Ticket URL:
> > <http://trac.tools.ietf.org/wg/martini/trac/ticket/17>
> > >>>>> martini <http://tools.ietf.org/martini/>
> > >>>>>
> > >>>>> _______________________________________________
> > >>>>> martini mailing list
> > >>>>> martini@ietf.org
> > >>>>> https://www.ietf.org/mailman/listinfo/martini
> > >>>>>
> > >>>> _______________________________________________
> > >>>> martini mailing list
> > >>>> martini@ietf.org
> > >>>> https://www.ietf.org/mailman/listinfo/martini
> > >>>>
> > >>>
> > >> _______________________________________________
> > >> martini mailing list
> > >> martini@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/martini
> > >>
> > >
> > > _______________________________________________
> > > martini mailing list
> > > martini@ietf.org
> > > https://www.ietf.org/mailman/listinfo/martini
> >
> >
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>

--00163602601f6ecf3a048260315a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I think that a lot of valid issues have been raised with the existing propo=
sed solution and I have nothing against solving those. I have a problem wit=
h a solution that can only handle E.164 numbers and can&#39;t even deliver =
the other variants of calls or requires a completely different solution. An=
d with that my main concern is the method of constructing the new Request U=
RI. If people want to use that solution they can do so anyway as it is lega=
l according to RFC3261, you don&#39;t need an RFC for that.<br>
<br>BR,<br clear=3D"all">/Hans Erik van Elburg<br>
<br><div class=3D"gmail_quote">On Sun, Mar 21, 2010 at 10:09 PM, Elwell, Jo=
hn <span dir=3D"ltr">&lt;<a href=3D"mailto:john.elwell@siemens-enterprise.c=
om">john.elwell@siemens-enterprise.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px=
 solid rgb(204, 204, 204); padding-left: 1ex;">
Yes, I did reference this, but the nature of that standard (delta to a delt=
a to a delta) is such that it requires a whole lot more digging to identify=
 the specific aspects of the TISPAN/3GPP solution that that are germane to =
the issues we are talking about. I was hoping that Hans Erik could help us =
to nail down particular aspects of the solution, with appropriate reference=
s, that he believes we need to align with.<br>

<font color=3D"#888888"><br>
John<br>
</font><div><div></div><div class=3D"h5"><br>
&gt; -----Original Message-----<br>
&gt; From: Spencer Dawkins [mailto:<a href=3D"mailto:spencer@wonderhamster.=
org">spencer@wonderhamster.org</a>]<br>
&gt; Sent: 21 March 2010 20:41<br>
&gt; To: Gonzalo Camarillo; Elwell, John<br>
&gt; Cc: <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; Subject: Re: [martini] #17: Desirable to align with existing standards=
<br>
&gt;<br>
&gt; Hi, Gonzalo,<br>
&gt;<br>
&gt; John had added<br>
&gt; =A0 =A0[ETSI TS 182 025]<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 &quot;ETSI TS 182 025 &quot;Telecommunicat=
ions and Internet<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 converged Services and Protocols for Advan=
ced Networking<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 (TISPAN); Business trunking; Architecture =
and functional<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 description&quot;&quot;.as a reference in<=
br>
&gt;<br>
&gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-martini-reqs-02" targ=
et=3D"_blank">http://tools.ietf.org/html/draft-ietf-martini-reqs-02</a> - I=
&#39;m<br>
&gt; not smart about<br>
&gt; ETSI, but I had hoped that specification was the appropriate<br>
&gt; reference :D<br>
&gt;<br>
&gt; Thanks,<br>
&gt;<br>
&gt; Spencer<br>
&gt;<br>
&gt; &gt; Hi,<br>
&gt; &gt;<br>
&gt; &gt; well, I do not care who answers as long as the information<br>
&gt; is sent ;o)<br>
&gt; &gt;<br>
&gt; &gt; Thanks,<br>
&gt; &gt;<br>
&gt; &gt; Gonzalo<br>
&gt; &gt;<br>
&gt; &gt; On 21/03/2010 7:20 AM, Elwell, John wrote:<br>
&gt; &gt;&gt; I assume this request is directed at Hans Erik.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; John<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt; From: Gonzalo Camarillo [mailto:<a href=3D"mailto:gcamari=
l@gmail.com">gcamaril@gmail.com</a>]<br>
&gt; &gt;&gt;&gt; Sent: 19 March 2010 14:22<br>
&gt; &gt;&gt;&gt; To: Elwell, John<br>
&gt; &gt;&gt;&gt; Cc: <a href=3D"mailto:martini@ietf.org">martini@ietf.org<=
/a><br>
&gt; &gt;&gt;&gt; Subject: Re: [martini] #17: Desirable to align with<br>
&gt; existing standards<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Hi,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; could you please provide references to the ETSI and 3GPP<=
br>
&gt; &gt;&gt;&gt; specs mentioned<br>
&gt; &gt;&gt;&gt; below?<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Thanks,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Gonzalo<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; On 19/03/2010 1:01 PM, Elwell, John wrote:<br>
&gt; &gt;&gt;&gt;&gt; As individual, I would remark that the market is alre=
ady<br>
&gt; &gt;&gt;&gt; fragmented between SIP and IMS-SIP, which makes things di=
fficult.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; As editor, I seek guidance from others on this one.<b=
r>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; John<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt;&gt;&gt; From: <a href=3D"mailto:martini-bounces@ietf.org"=
>martini-bounces@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; [mailto:<a href=3D"mailto:martini-bounces@ietf.or=
g">martini-bounces@ietf.org</a>] On Behalf Of martini<br>
&gt; &gt;&gt;&gt; issue tracker<br>
&gt; &gt;&gt;&gt;&gt;&gt; Sent: 18 March 2010 22:21<br>
&gt; &gt;&gt;&gt;&gt;&gt; To: <a href=3D"mailto:ietf.hanserik@gmail.com">ie=
tf.hanserik@gmail.com</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; Cc: <a href=3D"mailto:martini@ietf.org">martini@i=
etf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; Subject: [martini] #17: Desirable to align with<b=
r>
&gt; existing standards<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; #17: Desirable to align with existing standards<b=
r>
&gt; &gt;&gt;&gt;&gt;&gt; -------------------------------------+-----------=
-------------<br>
&gt; &gt;&gt;&gt;&gt;&gt; --------------<br>
&gt; &gt;&gt;&gt;&gt;&gt; =A0Reporter: =A0ietf.hanserik@... =A0 =A0 =A0 =A0=
 =A0| =A0 =A0 =A0 Owner:<br>
&gt; &gt;&gt;&gt;&gt;&gt; =A0 =A0 =A0Type: =A0enhancement =A0 =A0 =A0 =A0 =
=A0 =A0 =A0| =A0 =A0 =A0Status: =A0new<br>
&gt; &gt;&gt;&gt;&gt;&gt; =A0Priority: =A0major =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0| =A0 Milestone: =A0milestone1<br>
&gt; &gt;&gt;&gt;&gt;&gt; Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 | =A0 =A0 Version: =A01.0<br>
&gt; &gt;&gt;&gt;&gt;&gt; =A0Severity: =A0In WG Last Call =A0 =A0 =A0 =A0 =
=A0| =A0 =A0Keywords:<br>
&gt; &gt;&gt;&gt;&gt;&gt; -------------------------------------+-----------=
-------------<br>
&gt; &gt;&gt;&gt;&gt;&gt; --------------<br>
&gt; &gt;&gt;&gt;&gt;&gt; =A0DES5 - The mechanism SHOULD be aligned as much=
 as possible<br>
&gt; &gt;&gt;&gt;&gt;&gt; with mechanisms<br>
&gt; &gt;&gt;&gt;&gt;&gt; =A0already standardised in other SDO&#39;s like E=
TSI and 3GPP<br>
&gt; in order to<br>
&gt; &gt;&gt;&gt;&gt;&gt; =A0prohibit a fragmentation of the market.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; --<br>
&gt; &gt;&gt;&gt;&gt;&gt; Ticket URL:<br>
&gt; &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/17" t=
arget=3D"_blank">http://trac.tools.ietf.org/wg/martini/trac/ticket/17</a>&g=
t;<br>
&gt; &gt;&gt;&gt;&gt;&gt; martini &lt;<a href=3D"http://tools.ietf.org/mart=
ini/" target=3D"_blank">http://tools.ietf.org/martini/</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; _______________________________________________<b=
r>
&gt; &gt;&gt;&gt;&gt;&gt; martini mailing list<br>
&gt; &gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:martini@ietf.org">martini@ietf.=
org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/=
martini" target=3D"_blank">https://www.ietf.org/mailman/listinfo/martini</a=
><br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; _______________________________________________<br>
&gt; &gt;&gt;&gt;&gt; martini mailing list<br>
&gt; &gt;&gt;&gt;&gt; <a href=3D"mailto:martini@ietf.org">martini@ietf.org<=
/a><br>
&gt; &gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mart=
ini" target=3D"_blank">https://www.ietf.org/mailman/listinfo/martini</a><br=
>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt; _______________________________________________<br>
&gt; &gt;&gt; martini mailing list<br>
&gt; &gt;&gt; <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; &gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/martini" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/martini</a><br>
&gt; &gt;&gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; martini mailing list<br>
&gt; &gt; <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/martini</a><br>
&gt;<br>
&gt;<br>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
</div></div></blockquote></div><br>

--00163602601f6ecf3a048260315a--

From ietf.hanserik@gmail.com  Mon Mar 22 02:25:10 2010
Return-Path: <ietf.hanserik@gmail.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 582A33A6B52 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:25:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.264
X-Spam-Level: 
X-Spam-Status: No, score=-0.264 tagged_above=-999 required=5 tests=[AWL=-1.396, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 aVLzwGb8OEG4 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:25:06 -0700 (PDT)
Received: from mail-ew0-f223.google.com (mail-ew0-f223.google.com [209.85.219.223]) by core3.amsl.com (Postfix) with ESMTP id AD5F23A68B9 for <martini@ietf.org>; Mon, 22 Mar 2010 02:24:27 -0700 (PDT)
Received: by ewy23 with SMTP id 23so423015ewy.14 for <martini@ietf.org>; Mon, 22 Mar 2010 02:24:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=jd/9lpOp5qdapin9vLcsnxygFN++MqpOJ+Hh/NT7vTU=; b=iJtxGndbOQZGcLZGZHFpvbxiMgmS/Km5xD3fG1tro0oIqMLurWImdIIEXiTkHsvZTW Q6tqpbmVikdljb4HltYkjbTL1IbOBBXmUYoakibZrrZn9mn3JRZWDOYnZRZaDGtRqOfh p24fs6is6I5x6WRI56v3iAzvibQ9g/AeKUz18=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LHjB5NN02pGl6j7dJZjU9HTvJcVp5fypommd1oFX4g25KExRxhOeOFjdkzZmKh4OGL iWUPsdv3mVCdkhDJ62GWVXMDWmX0FGz/BV8rnXpip4YvctjYSahNhv1kUUc3dq/1Ftl5 crrRAE/Pp22O9nc2WxGPwL4qgqNhVjDgiRq/w=
MIME-Version: 1.0
Received: by 10.213.34.79 with HTTP; Mon, 22 Mar 2010 02:24:39 -0700 (PDT)
In-Reply-To: <014d01cac797$a91b2cc0$fb518640$@us>
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net> <4BA37DBF.8060404@cisco.com> <9ae56b1e1003190650s5c402e39g3aa840f31673e4c6@mail.gmail.com> <4BA387D3.9070704@nostrum.com> <208EAE1DFA28FC419529619ABB862244161769256F@CMS03.BGC.NET> <014d01cac797$a91b2cc0$fb518640$@us>
Date: Mon, 22 Mar 2010 10:24:39 +0100
Received: by 10.213.1.143 with SMTP id 15mr2822949ebf.55.1269249879547; Mon,  22 Mar 2010 02:24:39 -0700 (PDT)
Message-ID: <9ae56b1e1003220224t4bd61924scaaa9dfcb6220cbf@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: Richard Shockey <richard@shockey.us>
Content-Type: multipart/alternative; boundary=000e0cd1f8b4339fa50482604446
Cc: trac@localhost.amsl.com, martini@ietf.org
Subject: Re: [martini] #15: support for non E.164 numbers
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, 22 Mar 2010 09:25:10 -0000

--000e0cd1f8b4339fa50482604446
Content-Type: text/plain; charset=ISO-8859-1

So what problem are you addressing then?

/Hans Erik van Elburg


On Fri, Mar 19, 2010 at 8:09 PM, Richard Shockey <richard@shockey.us> wrote:

> I do not agree that the 3GPP solution actually solves the problem we are
> trying to address here.
>
> -----Original Message-----
> From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf
> Of jan.van.geel@belgacom.be
> Sent: Friday, March 19, 2010 10:25 AM
> To: adam@nostrum.com; ietf.hanserik@gmail.com
> Cc: trac@localhost.amsl.com; martini@ietf.org
> Subject: Re: [martini] #15: support for non E.164 numbers
>
> It seems that you are in hurry to provide a solution to a problem, for
> which
> another forum already provided a solution.
> In order to win time, why not envisaging adopting that solution and study
> possible enhancements.
>
> Kind regards
>
> Jan Van Geel
> IT and Network Development Specialist
> Belgacom SDE/SDV/PSE/NST/NCP
> Tel: +32 2 202 1035
> Tel: +32 2 207 9032
> Email : jan.van.geel@belgacom.be
> www.cyberwezz.tk
>
>
> -----Original Message-----
> From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf
> Of Adam Roach
> Sent: 19 March 2010 15:19
> To: Hans Erik van Elburg
> Cc: trac@localhost.amsl.com; martini@ietf.org
> Subject: Re: [martini] #15: support for non E.164 numbers
>
>
> On 3/19/10 08:50, Mar 19, Hans Erik van Elburg wrote:
> > So the argument here goes: we don't know how local numbers would be
> > routed to the SSP therefore we will not allow local numbers to be
> > delivered to IP-PBX's by that SSP even if they only have significance
> > within the SSP domain and are understood by the PBX.
>
> The issue really comes down to global uniqueness. I don't think GIN
> currently forbids private numbers; it's just not something we're taking
> on as a design constraint. If an SSP and their customers can guarantee
> uniqueness of user portions among all PBXes, they would be free (within
> the current GIN framework) to try to make that work. And it probably will.
>
> But we're explicitly in an unprecedented hurry here (when else has a WG
> had three interims in two months?), and taking on the additional
> analysis to ensure that private numbering works, and making adjustments
> to the protocol to accommodate it, don't fit into that mode of operation.
>
> >
> > I can not really follow that logic. Seems like forced limitation of
> > freedom by design.
>
> Perhaps -- that might be the other side of the coin that I would
> characterize as "restricting the solution space for the sake of
> expediency."
>
> Some projects are planned based on "how long would it take to design X
> so that it is perfect." Others are planned based on "we have X amount of
> time; what can you design in that timeframe?" In the IETF, we tend to
> deal with the former, and the answer is "3 to 5 years, unless someone
> disagrees with something, in which case it will take longer." For the
> first MARTINI deliverables, we're dealing with the latter, where the
> timeframe is "within 3 to 6 months."
>
> /a
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>
> **** DISCLAIMER ****
> http://www.belgacom.be/maildisclaimer
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>
>

--000e0cd1f8b4339fa50482604446
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

So what problem are you addressing then?<br><br>/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Fri, Mar 19, 2010 at 8:09 PM, Richard=
 Shockey <span dir=3D"ltr">&lt;<a href=3D"mailto:richard@shockey.us">richar=
d@shockey.us</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);=
 padding-left: 1ex;">
I do not agree that the 3GPP solution actually solves the problem we are<br=
>
trying to address here.<br>
<div class=3D"im"><br>
-----Original Message-----<br>
From: <a href=3D"mailto:martini-bounces@ietf.org">martini-bounces@ietf.org<=
/a> [mailto:<a href=3D"mailto:martini-bounces@ietf.org">martini-bounces@iet=
f.org</a>] On Behalf<br>
</div><div><div></div><div class=3D"h5">Of <a href=3D"mailto:jan.van.geel@b=
elgacom.be">jan.van.geel@belgacom.be</a><br>
Sent: Friday, March 19, 2010 10:25 AM<br>
To: <a href=3D"mailto:adam@nostrum.com">adam@nostrum.com</a>; <a href=3D"ma=
ilto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</a><br>
Cc: <a href=3D"mailto:trac@localhost.amsl.com">trac@localhost.amsl.com</a>;=
 <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
Subject: Re: [martini] #15: support for non E.164 numbers<br>
<br>
It seems that you are in hurry to provide a solution to a problem, for whic=
h<br>
another forum already provided a solution.<br>
In order to win time, why not envisaging adopting that solution and study<b=
r>
possible enhancements.<br>
<br>
Kind regards<br>
<br>
Jan Van Geel<br>
IT and Network Development Specialist<br>
Belgacom SDE/SDV/PSE/NST/NCP<br>
Tel: +32 2 202 1035<br>
Tel: +32 2 207 9032<br>
Email : <a href=3D"mailto:jan.van.geel@belgacom.be">jan.van.geel@belgacom.b=
e</a><br>
<a href=3D"http://www.cyberwezz.tk" target=3D"_blank">www.cyberwezz.tk</a><=
br>
<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:martini-bounces@ietf.org">martini-bounces@ietf.org<=
/a> [mailto:<a href=3D"mailto:martini-bounces@ietf.org">martini-bounces@iet=
f.org</a>] On Behalf<br>
Of Adam Roach<br>
Sent: 19 March 2010 15:19<br>
To: Hans Erik van Elburg<br>
Cc: <a href=3D"mailto:trac@localhost.amsl.com">trac@localhost.amsl.com</a>;=
 <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
Subject: Re: [martini] #15: support for non E.164 numbers<br>
<br>
<br>
On 3/19/10 08:50, Mar 19, Hans Erik van Elburg wrote:<br>
&gt; So the argument here goes: we don&#39;t know how local numbers would b=
e<br>
&gt; routed to the SSP therefore we will not allow local numbers to be<br>
&gt; delivered to IP-PBX&#39;s by that SSP even if they only have significa=
nce<br>
&gt; within the SSP domain and are understood by the PBX.<br>
<br>
The issue really comes down to global uniqueness. I don&#39;t think GIN<br>
currently forbids private numbers; it&#39;s just not something we&#39;re ta=
king<br>
on as a design constraint. If an SSP and their customers can guarantee<br>
uniqueness of user portions among all PBXes, they would be free (within<br>
the current GIN framework) to try to make that work. And it probably will.<=
br>
<br>
But we&#39;re explicitly in an unprecedented hurry here (when else has a WG=
<br>
had three interims in two months?), and taking on the additional<br>
analysis to ensure that private numbering works, and making adjustments<br>
to the protocol to accommodate it, don&#39;t fit into that mode of operatio=
n.<br>
<br>
&gt;<br>
&gt; I can not really follow that logic. Seems like forced limitation of<br=
>
&gt; freedom by design.<br>
<br>
Perhaps -- that might be the other side of the coin that I would<br>
characterize as &quot;restricting the solution space for the sake of expedi=
ency.&quot;<br>
<br>
Some projects are planned based on &quot;how long would it take to design X=
<br>
so that it is perfect.&quot; Others are planned based on &quot;we have X am=
ount of<br>
time; what can you design in that timeframe?&quot; In the IETF, we tend to<=
br>
deal with the former, and the answer is &quot;3 to 5 years, unless someone<=
br>
disagrees with something, in which case it will take longer.&quot; For the<=
br>
first MARTINI deliverables, we&#39;re dealing with the latter, where the<br=
>
timeframe is &quot;within 3 to 6 months.&quot;<br>
<br>
/a<br>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
<br>
**** DISCLAIMER ****<br>
<a href=3D"http://www.belgacom.be/maildisclaimer" target=3D"_blank">http://=
www.belgacom.be/maildisclaimer</a><br>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
<br>
</div></div></blockquote></div><br>

--000e0cd1f8b4339fa50482604446--

From ietf.hanserik@gmail.com  Mon Mar 22 02:33:58 2010
Return-Path: <ietf.hanserik@gmail.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 82AE63A6B43 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.171
X-Spam-Level: 
X-Spam-Status: No, score=-0.171 tagged_above=-999 required=5 tests=[AWL=-1.303, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 Lb2URHxnR7CQ for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:33:57 -0700 (PDT)
Received: from mail-ew0-f223.google.com (mail-ew0-f223.google.com [209.85.219.223]) by core3.amsl.com (Postfix) with ESMTP id 18DE628C0F4 for <martini@ietf.org>; Mon, 22 Mar 2010 02:30:51 -0700 (PDT)
Received: by ewy23 with SMTP id 23so424686ewy.14 for <martini@ietf.org>; Mon, 22 Mar 2010 02:31:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=v+9xA042tYT1mneoGQ4z47RGudgUx83Byln6Z04SFjw=; b=X0NSafWSgELozfsO6qP1ewx5yYQfxvhr7oVYyekQON7AIzAoO6VPFSiWkk1xzDQHrB +4BkRWJKRYA6KtU8F+WTMc2y4amtDmiywl0LpRIyvN89/Ru/T5VIDn8ZdSP9FduhpCZB pp0SdldiiK3XSQOxbPhMC0k5gxDSrJNe8cfQY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=v7wpg8RJBGetvc1OlxEvuplurMDXMZL3K4sZuZJjbJx278l2vWwbsn6rnuOpi0Jd5H 7pg3GYKlQwSqFluLbXFI1w8YF8uDYKbtywMwPQFgvRi1hENABJUyo0/GMCZqiuFdfpB3 oMx1uCqLLIAgvbrehMybK0dXwf5GtpGvsCwqo=
MIME-Version: 1.0
Received: by 10.213.34.79 with HTTP; Mon, 22 Mar 2010 02:31:05 -0700 (PDT)
In-Reply-To: <4BA387D3.9070704@nostrum.com>
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net> <4BA37DBF.8060404@cisco.com> <9ae56b1e1003190650s5c402e39g3aa840f31673e4c6@mail.gmail.com> <4BA387D3.9070704@nostrum.com>
Date: Mon, 22 Mar 2010 10:31:05 +0100
Received: by 10.213.55.3 with SMTP id s3mr2797627ebg.1.1269250265933; Mon, 22  Mar 2010 02:31:05 -0700 (PDT)
Message-ID: <9ae56b1e1003220231l619ccbd4sf115cae76dbebbac@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: Adam Roach <adam@nostrum.com>
Content-Type: multipart/alternative; boundary=00148531a8683b6c390482605bdf
Cc: "trac@localhost.amsl.com" <trac@localhost.amsl.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #15: support for non E.164 numbers
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, 22 Mar 2010 09:33:58 -0000

--00148531a8683b6c390482605bdf
Content-Type: text/plain; charset=ISO-8859-1

Can you explain the "unprecedented hurry"?

/Hans Erik van Elburg


On Fri, Mar 19, 2010 at 3:18 PM, Adam Roach <adam@nostrum.com> wrote:

>
> On 3/19/10 08:50, Mar 19, Hans Erik van Elburg wrote:
>
>> So the argument here goes: we don't know how local numbers would be routed
>> to the SSP therefore we will not allow local numbers to be delivered to
>> IP-PBX's by that SSP even if they only have significance within the SSP
>> domain and are understood by the PBX.
>>
>
> The issue really comes down to global uniqueness. I don't think GIN
> currently forbids private numbers; it's just not something we're taking on
> as a design constraint. If an SSP and their customers can guarantee
> uniqueness of user portions among all PBXes, they would be free (within the
> current GIN framework) to try to make that work. And it probably will.
>
> But we're explicitly in an unprecedented hurry here (when else has a WG had
> three interims in two months?), and taking on the additional analysis to
> ensure that private numbering works, and making adjustments to the protocol
> to accommodate it, don't fit into that mode of operation.
>
>
>
>> I can not really follow that logic. Seems like forced limitation of
>> freedom by design.
>>
>
> Perhaps -- that might be the other side of the coin that I would
> characterize as "restricting the solution space for the sake of expediency."
>
> Some projects are planned based on "how long would it take to design X so
> that it is perfect." Others are planned based on "we have X amount of time;
> what can you design in that timeframe?" In the IETF, we tend to deal with
> the former, and the answer is "3 to 5 years, unless someone disagrees with
> something, in which case it will take longer." For the first MARTINI
> deliverables, we're dealing with the latter, where the timeframe is "within
> 3 to 6 months."
>
> /a
>

--00148531a8683b6c390482605bdf
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Can you explain the &quot;unprecedented hurry&quot;?<br><br clear=3D"all">/=
Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Fri, Mar 19, 2010 at 3:18 PM, Adam Ro=
ach <span dir=3D"ltr">&lt;<a href=3D"mailto:adam@nostrum.com">adam@nostrum.=
com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-=
left: 1ex;">
<div class=3D"im"><br>
On 3/19/10 08:50, Mar 19, Hans Erik van Elburg wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
So the argument here goes: we don&#39;t know how local numbers would be rou=
ted to the SSP therefore we will not allow local numbers to be delivered to=
 IP-PBX&#39;s by that SSP even if they only have significance within the SS=
P domain and are understood by the PBX.<br>

</blockquote>
<br></div>
The issue really comes down to global uniqueness. I don&#39;t think GIN cur=
rently forbids private numbers; it&#39;s just not something we&#39;re takin=
g on as a design constraint. If an SSP and their customers can guarantee un=
iqueness of user portions among all PBXes, they would be free (within the c=
urrent GIN framework) to try to make that work. And it probably will.<br>

<br>
But we&#39;re explicitly in an unprecedented hurry here (when else has a WG=
 had three interims in two months?), and taking on the additional analysis =
to ensure that private numbering works, and making adjustments to the proto=
col to accommodate it, don&#39;t fit into that mode of operation.<div class=
=3D"im">
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
I can not really follow that logic. Seems like forced limitation of freedom=
 by design.<br>
</blockquote>
<br></div>
Perhaps -- that might be the other side of the coin that I would characteri=
ze as &quot;restricting the solution space for the sake of expediency.&quot=
;<br>
<br>
Some projects are planned based on &quot;how long would it take to design X=
 so that it is perfect.&quot; Others are planned based on &quot;we have X a=
mount of time; what can you design in that timeframe?&quot; In the IETF, we=
 tend to deal with the former, and the answer is &quot;3 to 5 years, unless=
 someone disagrees with something, in which case it will take longer.&quot;=
 For the first MARTINI deliverables, we&#39;re dealing with the latter, whe=
re the timeframe is &quot;within 3 to 6 months.&quot;<br>
<font color=3D"#888888">
<br>
/a<br>
</font></blockquote></div><br>

--00148531a8683b6c390482605bdf--

From bruno.chatras@orange-ftgroup.com  Mon Mar 22 02:36:29 2010
Return-Path: <bruno.chatras@orange-ftgroup.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 6FFDB3A67E9 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.476
X-Spam-Level: 
X-Spam-Status: No, score=-0.476 tagged_above=-999 required=5 tests=[AWL=-1.772, BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
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 iW6SExwymQRL for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:36:28 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) by core3.amsl.com (Postfix) with ESMTP id F1D773A6359 for <martini@ietf.org>; Mon, 22 Mar 2010 02:36:27 -0700 (PDT)
Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda11.si.francetelecom.fr (ESMTP service) with ESMTP id 66FE81B825F; Mon, 22 Mar 2010 10:36:43 +0100 (CET)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id 414C8158077; Mon, 22 Mar 2010 10:36:43 +0100 (CET)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 22 Mar 2010 10:36:43 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Mar 2010 10:36:41 +0100
Message-ID: <26069_1269250603_4BA73A2B_26069_20257_1_9ECCF01B52E7AB408A7EB85352642141013CE397@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] #15: support for non E.164 numbers
Thread-Index: AcrG5sLK8AdLEaxATGmDd7ZN6oXUSwAagbNgAJR2UWA=
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net>
From: <bruno.chatras@orange-ftgroup.com>
To: <john.elwell@siemens-enterprise.com>, <trac@localhost.amsl.com>, <ietf.hanserik@gmail.com>
X-OriginalArrivalTime: 22 Mar 2010 09:36:43.0029 (UTC) FILETIME=[2E7D3450:01CAC9A3]
X-PMX-Version: 5.5.7.378829, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.3.22.82125
Cc: martini@ietf.org
Subject: Re: [martini] #15: support for non E.164 numbers
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, 22 Mar 2010 09:36:29 -0000

As you said considerations are similar to non-number-based SIP URIs. Theref=
ore my comment will be very similar as well. By designing an E.164 solution=
 only in the first phase we run a risk that a PBX supporting both types of =
numbers will have to support two completely different solutions.


> -----Message d'origine-----
> De : martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] De la part de Elwell, John
> Envoy=E9 : vendredi 19 mars 2010 11:55
> =C0 : trac@localhost.amsl.com; ietf.hanserik@gmail.com
> Cc : martini@ietf.org
> Objet : Re: [martini] #15: support for non E.164 numbers
>=20
> As an individual, I don't see an urgent need to solve this in=20
> the initial phase. Present deployments use fully-qualified=20
> E.164 numbers (or numbers that can be turned into=20
> fully-qualified E.164 numbers), and it is for these=20
> deployments that we urgently need a standard on which to=20
> converge. Support for non-E.164-based (private numbers) might=20
> be nice to have, but not essential.=20
>=20
> I guess an important point is whether these non-E.164 numbers=20
> are globally unique (as a result of a phone-context=20
> parameter), in which case they might be easier to=20
> accommodate, but even then I am not sure. If I have a=20
> telephone number in the form tel:1234;phone-context=3Dpbx.com,=20
> how does this get routed to ssp.com in order to get=20
> onward-routed to the PBX? It might work if you start off with=20
> sip:1234;phone-context=3Dpbx.com@ssp.com;user=3Dphone, but how=20
> would the calling UA construct such a URI in the first place=20
> (unless returning a received URI)?
>=20
> It seems to me that considerations are similar to=20
> non-number-based SIP URIs, and therefore this should be=20
> treated in the same way as #16 (depending on what we decide=20
> for that - see my recommendation in my previous email).
>=20
> John
>=20
>=20
> > -----Original Message-----
> > From: martini-bounces@ietf.org
> > [mailto:martini-bounces@ietf.org] On Behalf Of martini issue tracker
> > Sent: 18 March 2010 22:03
> > To: ietf.hanserik@gmail.com
> > Cc: martini@ietf.org
> > Subject: [martini] #15: support for non E.164 numbers
> >=20
> > #15: support for non E.164 numbers
> > -------------------------------------+------------------------
> > --------------
> >  Reporter:  ietf.hanserik@...          |       Owner:=20=20=20=20=20=20=
=20=20=20=20=20=20
> >      Type:  defect                   |      Status:  new=20=20=20=20=20=
=20=20
> >  Priority:  critical                 |   Milestone:  milestone1
> > Component:  reqs                     |     Version:  1.0=20=20=20=20=20=
=20=20
> >  Severity:  In WG Last Call          |    Keywords:=20=20=20=20=20=20=
=20=20=20=20=20=20
> > -------------------------------------+------------------------
> > --------------
> >  REQ19 - The mechanism MUST allow a set of assigned=20
> telephone numbers=20
> > to  comprise local numbers as specified in RFC3966, which=20
> can be in=20=20
> > contiguous ranges, discrete, or in any combination of the two.
> >=20
> > --
> > Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/15>
> > martini <http://tools.ietf.org/martini/>
> >=20
> > _______________________________________________
> > martini mailing list
> > martini@ietf.org
> > https://www.ietf.org/mailman/listinfo/martini
> >=20
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>=20

*********************************
This message and any attachments (the "message") are confidential and inten=
ded solely for the addressees.=20
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.=20
France Telecom Group shall not be liable for the message if altered, change=
d or falsified.
If you are not the intended addressee of this message, please cancel it imm=
ediately and inform the sender.
********************************


From ietf.hanserik@gmail.com  Mon Mar 22 02:41:57 2010
Return-Path: <ietf.hanserik@gmail.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 A188A3A6765 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[AWL=-1.222,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 LfIgnMBOlKQ5 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:41:56 -0700 (PDT)
Received: from mail-ew0-f223.google.com (mail-ew0-f223.google.com [209.85.219.223]) by core3.amsl.com (Postfix) with ESMTP id 6B9A93A6359 for <martini@ietf.org>; Mon, 22 Mar 2010 02:41:56 -0700 (PDT)
Received: by ewy23 with SMTP id 23so427677ewy.14 for <martini@ietf.org>; Mon, 22 Mar 2010 02:42:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=3V5yyfXjykAqGbzaRdYPG0/R1AsTDDlzyA+IyJ1sVfM=; b=HKHaKfC/DD7QYAF6+rSnBF31NzsGKkvvqn6Qndm3scP0hZDQO6A+r3d6V+0iSm6Am+ +9ooiC6lKfL8o1NBk+dKg1oZvIBHGd1Q1ECSN28OVPyzTamhjFRMKswFZ81RFZSs5fkS Z9mSOm3MSSizR/okP+18mfCeiF3q+NsNcoKY8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Y8eap5d6RrAACzcyLhp9VTQ6S/E18x1lrGXjjdwtSM2T/moAdtREFxGxCkzQeGjGu2 yYUxfOKkYvOdOg5rqYMFWGlkz01n09kU/1pQsOQGzU2GkzR/BxZUDvBNPWu+em4eEVF/ KyOHsAby2aeVud++t9EsVHCtA5yesFqL/3QIM=
MIME-Version: 1.0
Received: by 10.213.43.135 with SMTP id w7mr1045207ebe.89.1269250929249; Mon,  22 Mar 2010 02:42:09 -0700 (PDT)
In-Reply-To: <4BA38FF1.8000903@nostrum.com>
References: <065.0881de899bd9e7c8fe255eb1b2119130@tools.ietf.org> <A444A0F8084434499206E78C106220CABE982756@MCHP058A.global-ad.net> <4BA37DBF.8060404@cisco.com> <9ae56b1e1003190650s5c402e39g3aa840f31673e4c6@mail.gmail.com> <4BA387D3.9070704@nostrum.com> <208EAE1DFA28FC419529619ABB862244161769256F@CMS03.BGC.NET> <4BA38FF1.8000903@nostrum.com>
Date: Mon, 22 Mar 2010 10:42:09 +0100
Message-ID: <9ae56b1e1003220242i7b67a5bdp95979b349ba51630@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: Adam Roach <adam@nostrum.com>
Content-Type: multipart/alternative; boundary=00148531b64dc4ceb70482608208
Cc: martini@ietf.org
Subject: Re: [martini] #15: support for non E.164 numbers
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, 22 Mar 2010 09:41:58 -0000

--00148531b64dc4ceb70482608208
Content-Type: text/plain; charset=ISO-8859-1

An acceptable change would be where the Request-URI would be kept unchanged
and a Contact header populated on the Route header, for example.

Have not understood what is so wrong with that.

/Hans Erik van Elburg

On Fri, Mar 19, 2010 at 3:53 PM, Adam Roach <adam@nostrum.com> wrote:

> On 03/19/2010 09:25 AM, jan.van.geel@belgacom.be wrote:
>
>> It seems that you are in hurry to provide a solution to a problem, for
>> which another forum already provided a solution.
>> In order to win time, why not envisaging adopting that solution and study
>> possible enhancements.
>>
>>
>
> As we've been over many times on the list and at interim meetings, the
> problems in those solutions are myriad. No one has stepped forward with
> plausible ways to address such problems -- probably because the problems are
> inherent in the mechanism itself, and not minor flaws.
>
> I would be delighted if someone could prove me wrong by proposing
> acceptable changes to the solutions you reference that address the suite of
> problems that have been raised in MARTINI. I have no burning desire to
> author a draft that addresses a problem that I have no interest in. But no
> one else is coming up with solutions, and the problems inherent in shaken
> and its progenitors are profound enough that I do not believe the IETF can
> endorse them.
>
> /a
>

--00148531b64dc4ceb70482608208
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

An acceptable change would be where the Request-URI would be kept unchanged=
 and a Contact header populated on the Route header, for example.<br><br>Ha=
ve not understood what is so wrong with that. <br><br clear=3D"all">/Hans E=
rik van Elburg<br>

<br><div class=3D"gmail_quote">On Fri, Mar 19, 2010 at 3:53 PM, Adam Roach =
<span dir=3D"ltr">&lt;<a href=3D"mailto:adam@nostrum.com">adam@nostrum.com<=
/a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:=
 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left=
: 1ex;">
<div class=3D"im">On 03/19/2010 09:25 AM, <a href=3D"mailto:jan.van.geel@be=
lgacom.be" target=3D"_blank">jan.van.geel@belgacom.be</a> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
It seems that you are in hurry to provide a solution to a problem, for whic=
h another forum already provided a solution.<br>
In order to win time, why not envisaging adopting that solution and study p=
ossible enhancements.<br>
 =A0 <br>
</blockquote>
<br></div>
As we&#39;ve been over many times on the list and at interim meetings, the =
problems in those solutions are myriad. No one has stepped forward with pla=
usible ways to address such problems -- probably because the problems are i=
nherent in the mechanism itself, and not minor flaws.<br>

<br>
I would be delighted if someone could prove me wrong by proposing acceptabl=
e changes to the solutions you reference that address the suite of problems=
 that have been raised in MARTINI. I have no burning desire to author a dra=
ft that addresses a problem that I have no interest in. But no one else is =
coming up with solutions, and the problems inherent in shaken and its proge=
nitors are profound enough that I do not believe the IETF can endorse them.=
<br>
<font color=3D"#888888">
<br>
/a<br>
</font></blockquote></div><br>

--00148531b64dc4ceb70482608208--

From ietf.hanserik@gmail.com  Mon Mar 22 02:46:45 2010
Return-Path: <ietf.hanserik@gmail.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 B0FC83A68A0 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:46:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.282
X-Spam-Level: 
X-Spam-Status: No, score=0.282 tagged_above=-999 required=5 tests=[AWL=-1.450,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6]
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 ftI3sc1D6Oat for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:46:43 -0700 (PDT)
Received: from mail-ew0-f223.google.com (mail-ew0-f223.google.com [209.85.219.223]) by core3.amsl.com (Postfix) with ESMTP id AFD463A67A5 for <martini@ietf.org>; Mon, 22 Mar 2010 02:46:14 -0700 (PDT)
Received: by ewy23 with SMTP id 23so428818ewy.14 for <martini@ietf.org>; Mon, 22 Mar 2010 02:46:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=KStab/X76uhP5/jt00KV7sPzGASbXU7cd2bNEll84fk=; b=GZJTLeGQx4jc1tm0VMkm2/kLFy2P+RgGpV1rU6GgfMY4ejvTyFEU94ioZuZUpcL2T8 AJGbLzEfblKMQ7DMTuZMuWuYlfDYXQqTGJNKPB5LsZjZYdTZdue9s026fhtLuBYmw4bf FUIHCtHjH7apJWAgrRP9LTVy8Cd56nQPYUJEs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=S+C6LfaWqwSyJ2f7tUsRfsfkZG5wvjMEAjKlLIzyb8zCWwLe+kOU4VrBSw7J8iy3zc PIQePOpk1LtTViiLzD6EwaNvAsYJmtlPCfwCK7jGrhrJkUFR27xP8GVWBOlnT3xv14d2 4Bq0eS9ZD7XuK9qBvmY78o1BBWc038ty/VTh4=
MIME-Version: 1.0
Received: by 10.213.34.79 with HTTP; Mon, 22 Mar 2010 02:46:31 -0700 (PDT)
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79CD1821@mail>
References: <C7AC4291.14C39%adam@nostrum.com> <00b101cab66c$3ce34150$430510ac@CORPORATE.VOX.NET> <09B7DBFE70A9E24BBB21689DAD3A06141CB0F52A@zcarhxm1.corp.nortel.com> <00ca01cab67a$7fd21460$430510ac@CORPORATE.VOX.NET> <A444A0F8084434499206E78C106220CABBB22E97@MCHP058A.global-ad.net> <000901cab6f5$968a9df0$010c030a@CORPORATE.VOX.NET> <A444A0F8084434499206E78C106220CABBB232D7@MCHP058A.global-ad.net> <008201cab70e$0d82c6e0$010c030a@CORPORATE.VOX.NET> <09B7DBFE70A9E24BBB21689DAD3A06141CB5DF53@zcarhxm1.corp.nortel.com> <430FC6BDED356B4C8498F634416644A91A79CD1821@mail>
Date: Mon, 22 Mar 2010 10:46:31 +0100
Received: by 10.213.52.13 with SMTP id f13mr2830549ebg.44.1269251191196; Mon,  22 Mar 2010 02:46:31 -0700 (PDT)
Message-ID: <9ae56b1e1003220246w7a8a13d6v9d5d689ae577a188@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Content-Type: multipart/alternative; boundary=00163602601f61d0b204826092a6
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, MARTINI <martini@ietf.org>
Subject: Re: [martini] Middlebox needs - admitting inbound requests
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, 22 Mar 2010 09:46:45 -0000

--00163602601f61d0b204826092a6
Content-Type: text/plain; charset=ISO-8859-1

Path makes sense. Is it a problem to require support for Path by the SSP?

/Hans Erik van Elburg


On Mon, Mar 22, 2010 at 12:26 AM, Hadriel Kaplan <HKaplan@acmepacket.com>wrote:

>
> I think having SBC's use unique ports per PBX would be a really bad way to
> go.  I don't know what other's experiences were with that, but we've got a
> mode setting for doing it that way because some registrars required it be
> done that way, but it had really nasty issues merely because of that
> mechanism.  Like you can't get more than ~60k subscribers per IP; if UA's
> move/go-away you have to decide when you can reclaim ports; if you're
> completely rebooted then the ports get allocated in a different order which
> confuses registrars; if you need to switch to TCP for some messages/cases
> then the mapping can't possibly be kept; you get the idea.
>
> I think it's been discussed before on this list (or maybe it was in
> SIP-Forum), that one clean way would be for the SBC to insert a Path header
> identifying itself and a cookie, and that cookie provide the route or
> registration-cache-key information it needs.  Or it can insert a Path with
> pretty much anything it needs - as long as the core registrar/proxies
> support Path and thus reflect the received Path list by adding them as Route
> header lists for the requests they route to the PBX through the SBC.
>
> Of course some things in Martini may well require changes in middleboxes,
> but that's why there's the option-tag. :)
>
> -hadriel
>
> > -----Original Message-----
> > From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On
> Behalf
> > Of Brian Lindsay
> > Sent: Sunday, February 28, 2010 3:52 PM
> > To: Tyler Parkin; Elwell, John; Adam Roach; Spencer Dawkins
> > Cc: Bernard Aboba; MARTINI
> > Subject: Re: [martini] Middlebox needs - admitting inbound requests
> >
> > Hi Tyler,
> >
> >   I believe some SBCs that "NAT" as you describe would (or could) use a
> > unique port on the northbound side per registered entity. So the SBC
> > would be able to maintain a mapping from the client-side contact/routing
> > info to a unique northbound address/port that it would receive requests
> > on (for requests towards the SIP PBX). In this case, there shouldn't be
> > any problems routing the request.
> >
> >   Also, I think the MARTINI-Shaken approach wouldn't have a problem in
> > this case either, since the domain portion of the request uri (from the
> > "SSP") contains a domain name representing the enterprise/PBX, rather
> > than an IP address derived from the contact.
> >
> >   Thanks
> >      Brian
> >
> > -----Original Message-----
> > From: Tyler Parkin [mailto:tyler@foxfam.com]
> > Sent: Friday, February 26, 2010 1:04 PM
> > To: Elwell, John; Lindsay, Brian (CAR:AR00); Adam Roach; Spencer Dawkins
> > Cc: Bernard Aboba; MARTINI
> > Subject: Re: [martini] Middlebox needs - admitting inbound requests
> >
> >
> > > ----- Original Message -----
> > > From: "Elwell, John" <john.elwell@siemens-enterprise.com>
> > > To: "Tyler Parkin" <tyler@foxfam.com>; "Brian Lindsay"
> > > <blindsay@nortel.com>; "Adam Roach" <adam@nostrum.com>; "Spencer
> > > Dawkins"
> > > <spencer@wonderhamster.org>
> > > Cc: "Bernard Aboba" <bernard_aboba@hotmail.com>; "MARTINI"
> > > <martini@ietf.org>
> > > Sent: Friday, February 26, 2010 5:34 AM
> > > Subject: RE: [martini] Middlebox needs - admitting inbound requests
> > >
> > >
> > > Tyler,
> > >
> > > I found this thread a little mixed up between outbound requests from
> > > the PBX and inbound requests  to the PBX, so I am not sure I
> > > understood everything.
> > > [tyler] sorry for the confusion, I think we're looking at it in
> > > different directions... inbound to me is inbound to the SSP, where to
> > > you inbound is to the PBX.  I guess we'll stick w/ inbound = to the
> > > PBX
> > >
> > > As far as inbound request are concerned, I think with gin-01 the
> > > problems you raise should be solvable, but it perhaps requires use of
> > > Proxy-Require, as already discussed. The middlebox does not need to
> > > know exactly which E.164s are implicitly registered, but when it gets
> > > a request to the PBX's IP address (presumably with Route indicating
> > > the IP address of the middlebox) it should assume the E.164 in the
> > > user part is indeed a registered AOR.
> > > [tyler] my point is that the middlebox doesn't get a request to the
> > > PBX's IP address.
> > [JRE] Why not? If the Contact URI contains the IP address (as in
> > gin-01), this will be registered at the registrar and will be returned
> > as the target of an inbound request to the PBX.
> >
> > > The softswitch/registrar generating the call doesn't know the PBX's IP
> >
> > > because it was masked during the initial registration.
> > [JRE] Why would it be masked? I understand that the registrar would not
> > see the IP address at the transport level from which the REGISTER
> > request arrived at the middlebox, but it would see the IP address in the
> > Contact URI.
> > [Tyler] In most scenarios where a middlebox (aka SBC) exists, the SBC
> > performs two-way NAT functions, and NAT's the headers/URI's for inbound
> > and outbound messaging.  Therefore, a request received on the public
> > side from user@PBXIP is sent to the registrar as user@SBCPRIVATEIP.  The
> > oposite direction (SSP -> PBX) is received by the SBC as user@SSPIP and
> > NAT'd to user@SBCPUBLICIP.
> >
> > > Any
> > > requests from from the registrar/softswitch to the middlebox (destined
> >
> > > for the PBX) will only have user@middlebox, perhaps w/ a cookie.
> > > The middelbox
> > > needs to map user@middlebox to whatever IP/host originally registered.
> > > Today, the middlebox keeps a cache where the initial (individual)
> > > registration might be user@1.1.1.1, and the registration forwarded to
> > > the registrar is user@2.2.2.2.  That way when the registrar sends a
> > > request to the middlebox for user@2.2.2.2 it maps it to user@1.1.1.1
> > > and all is good.
> > > If the middelbox doesn't have knowledge of the user (because of
> > > implicit),
> > [JRE] Are you suggesting that each user behind the PBX would register
> > with a different IP address, so you need to know whether it is user1 or
> > user2 in order to send requests to 11.11.11.11 or 22.22.22.22? If so,
> > that is not the scenario that MARTINI is addressing. MARTINI is
> > addressing the case where requests to user1, user2 etc. on a given PBX
> > all need to be routed to the PBX's IP address. So as long as the
> > middlebox knows the request needs to go to the PBX, it doesn't need to
> > know that particular user.
> > [Tyler] Agreed, I shouldn't have used the term user.  The middlebox in
> > this scenario wouldn't care about individual users, it's point of
> > contact is the PBX.  All PBX's send register requests to the middlebox
> > from different IP's/domains, granted.  After NAT, however, all the
> > requests from the SBC to the registrar appear to come from the same IP.
> > We NAT in both directions, which is pretty standard, so we don't expose
> > core equipment to the public, and we don't expose end user IP's to
> > peers.  Plus it allows virtual route tables internally and resolves any
> > issues with overlapping address space.
> >
> > > it can't make the mapping unless it has something else to associate to
> >
> > > the original implicit reg (like a cookie, or knowledge of the
> > > extensions).
> > >
> > > Now concerning outbound requests (this was what my earlier message was
> >
> > > about, although somewhere further back that got brought across to this
> >
> > > thread rather than the thread concerning outbound requests, so the
> > > thread title was wrong). Assuming an entity has knowledge of
> > > registered E.164 numbers, it is not clear to me how it would deal with
> >
> > > a request where the From/PAI in the request from the PBX is not one of
> >
> > > the implicitly registered ones. This can arise, for example, if the
> > > request originates elsewhere in the enterprise and "breaks out" to the
> >
> > > SSP via this particular PBX. Or if the call originated elsewhere and
> > > was forwarded by the PBX to the SSP. I appreciate that there may be
> > > some arrangements between PBX and SSP where this is forbidden by
> > > policy, but in the general case I would expect it to work, so that the
> >
> > > callee has a correct AOR to which it can make a return call.
> > > [tyler] methods dealing with this situation today (A calls B, B
> > > forwards the call to C) would use from=A and PAI=B, where B is a
> > > registered endpoint (and billable by the SSP).  Not sure if that's
> > > what you're asking?
> > [JRE] Yes, that was what I was asking, and I know that it sometimes
> > works the way you describe, but this is bad because PAI=B is wrong - it
> > is not compliant with RFC 3325, since it is not the source of the
> > request. If the callee used that to make a return call, the return call
> > would arrive at the wrong place. For example, if a customer calls me on
> > my office number and the PBX forwards it to my home via the SSP, if my
> > phone stores the PAI as the caller's number and I try to make a return
> > call, the return call goes to my office phone, not to my customer.
> > [Tyler] The source of the forward leg of the call is B, not A.  Calling
> > area requirements and n11 need to be based on B.  Why would the callee
> > use PAI to return a call?  That would be in violation of 3325 as well
> > since it would obviate any callerid blocking/suppression requirements.
> > I guess whether the PBX should strip PAI before sending it to your phone
> > is arguable.  Agreed, using PAI to assert a different ID than From
> > (where from isn't private) might not strictly adhere to 3325, but I
> > think alternate ID's vs suppressed ID's is splitting hairs a little.
> >
> > John
> >
> > _______________________________________________
> > martini mailing list
> > martini@ietf.org
> > https://www.ietf.org/mailman/listinfo/martini
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>

--00163602601f61d0b204826092a6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Path makes sense. Is it a problem to require support for Path by the SSP?<b=
r><br clear=3D"all">/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Mon, Mar 22, 2010 at 12:26 AM, Hadrie=
l Kaplan <span dir=3D"ltr">&lt;<a href=3D"mailto:HKaplan@acmepacket.com">HK=
aplan@acmepacket.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 20=
4, 204); padding-left: 1ex;">
<br>
I think having SBC&#39;s use unique ports per PBX would be a really bad way=
 to go. =A0I don&#39;t know what other&#39;s experiences were with that, bu=
t we&#39;ve got a mode setting for doing it that way because some registrar=
s required it be done that way, but it had really nasty issues merely becau=
se of that mechanism. =A0Like you can&#39;t get more than ~60k subscribers =
per IP; if UA&#39;s move/go-away you have to decide when you can reclaim po=
rts; if you&#39;re completely rebooted then the ports get allocated in a di=
fferent order which confuses registrars; if you need to switch to TCP for s=
ome messages/cases then the mapping can&#39;t possibly be kept; you get the=
 idea.<br>

<br>
I think it&#39;s been discussed before on this list (or maybe it was in SIP=
-Forum), that one clean way would be for the SBC to insert a Path header id=
entifying itself and a cookie, and that cookie provide the route or registr=
ation-cache-key information it needs. =A0Or it can insert a Path with prett=
y much anything it needs - as long as the core registrar/proxies support Pa=
th and thus reflect the received Path list by adding them as Route header l=
ists for the requests they route to the PBX through the SBC.<br>

<br>
Of course some things in Martini may well require changes in middleboxes, b=
ut that&#39;s why there&#39;s the option-tag. :)<br>
<br>
-hadriel<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:martini-bounces@ietf.org">martini-bounces@ietf=
.org</a> [mailto:<a href=3D"mailto:martini-bounces@ietf.org">martini-bounce=
s@ietf.org</a>] On Behalf<br>
&gt; Of Brian Lindsay<br>
&gt; Sent: Sunday, February 28, 2010 3:52 PM<br>
&gt; To: Tyler Parkin; Elwell, John; Adam Roach; Spencer Dawkins<br>
&gt; Cc: Bernard Aboba; MARTINI<br>
&gt; Subject: Re: [martini] Middlebox needs - admitting inbound requests<br=
>
&gt;<br>
&gt; Hi Tyler,<br>
&gt;<br>
&gt; =A0 I believe some SBCs that &quot;NAT&quot; as you describe would (or=
 could) use a<br>
&gt; unique port on the northbound side per registered entity. So the SBC<b=
r>
&gt; would be able to maintain a mapping from the client-side contact/routi=
ng<br>
&gt; info to a unique northbound address/port that it would receive request=
s<br>
&gt; on (for requests towards the SIP PBX). In this case, there shouldn&#39=
;t be<br>
&gt; any problems routing the request.<br>
&gt;<br>
&gt; =A0 Also, I think the MARTINI-Shaken approach wouldn&#39;t have a prob=
lem in<br>
&gt; this case either, since the domain portion of the request uri (from th=
e<br>
&gt; &quot;SSP&quot;) contains a domain name representing the enterprise/PB=
X, rather<br>
&gt; than an IP address derived from the contact.<br>
&gt;<br>
&gt; =A0 Thanks<br>
&gt; =A0 =A0 =A0Brian<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: Tyler Parkin [mailto:<a href=3D"mailto:tyler@foxfam.com">tyler@f=
oxfam.com</a>]<br>
&gt; Sent: Friday, February 26, 2010 1:04 PM<br>
&gt; To: Elwell, John; Lindsay, Brian (CAR:AR00); Adam Roach; Spencer Dawki=
ns<br>
&gt; Cc: Bernard Aboba; MARTINI<br>
&gt; Subject: Re: [martini] Middlebox needs - admitting inbound requests<br=
>
&gt;<br>
&gt;<br>
&gt; &gt; ----- Original Message -----<br>
&gt; &gt; From: &quot;Elwell, John&quot; &lt;<a href=3D"mailto:john.elwell@=
siemens-enterprise.com">john.elwell@siemens-enterprise.com</a>&gt;<br>
&gt; &gt; To: &quot;Tyler Parkin&quot; &lt;<a href=3D"mailto:tyler@foxfam.c=
om">tyler@foxfam.com</a>&gt;; &quot;Brian Lindsay&quot;<br>
&gt; &gt; &lt;<a href=3D"mailto:blindsay@nortel.com">blindsay@nortel.com</a=
>&gt;; &quot;Adam Roach&quot; &lt;<a href=3D"mailto:adam@nostrum.com">adam@=
nostrum.com</a>&gt;; &quot;Spencer<br>
&gt; &gt; Dawkins&quot;<br>
&gt; &gt; &lt;<a href=3D"mailto:spencer@wonderhamster.org">spencer@wonderha=
mster.org</a>&gt;<br>
&gt; &gt; Cc: &quot;Bernard Aboba&quot; &lt;<a href=3D"mailto:bernard_aboba=
@hotmail.com">bernard_aboba@hotmail.com</a>&gt;; &quot;MARTINI&quot;<br>
&gt; &gt; &lt;<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a>&gt;<=
br>
&gt; &gt; Sent: Friday, February 26, 2010 5:34 AM<br>
&gt; &gt; Subject: RE: [martini] Middlebox needs - admitting inbound reques=
ts<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Tyler,<br>
&gt; &gt;<br>
&gt; &gt; I found this thread a little mixed up between outbound requests f=
rom<br>
&gt; &gt; the PBX and inbound requests =A0to the PBX, so I am not sure I<br=
>
&gt; &gt; understood everything.<br>
&gt; &gt; [tyler] sorry for the confusion, I think we&#39;re looking at it =
in<br>
&gt; &gt; different directions... inbound to me is inbound to the SSP, wher=
e to<br>
&gt; &gt; you inbound is to the PBX. =A0I guess we&#39;ll stick w/ inbound =
=3D to the<br>
&gt; &gt; PBX<br>
&gt; &gt;<br>
&gt; &gt; As far as inbound request are concerned, I think with gin-01 the<=
br>
&gt; &gt; problems you raise should be solvable, but it perhaps requires us=
e of<br>
&gt; &gt; Proxy-Require, as already discussed. The middlebox does not need =
to<br>
&gt; &gt; know exactly which E.164s are implicitly registered, but when it =
gets<br>
&gt; &gt; a request to the PBX&#39;s IP address (presumably with Route indi=
cating<br>
&gt; &gt; the IP address of the middlebox) it should assume the E.164 in th=
e<br>
&gt; &gt; user part is indeed a registered AOR.<br>
&gt; &gt; [tyler] my point is that the middlebox doesn&#39;t get a request =
to the<br>
&gt; &gt; PBX&#39;s IP address.<br>
&gt; [JRE] Why not? If the Contact URI contains the IP address (as in<br>
&gt; gin-01), this will be registered at the registrar and will be returned=
<br>
&gt; as the target of an inbound request to the PBX.<br>
&gt;<br>
&gt; &gt; The softswitch/registrar generating the call doesn&#39;t know the=
 PBX&#39;s IP<br>
&gt;<br>
&gt; &gt; because it was masked during the initial registration.<br>
&gt; [JRE] Why would it be masked? I understand that the registrar would no=
t<br>
&gt; see the IP address at the transport level from which the REGISTER<br>
&gt; request arrived at the middlebox, but it would see the IP address in t=
he<br>
&gt; Contact URI.<br>
&gt; [Tyler] In most scenarios where a middlebox (aka SBC) exists, the SBC<=
br>
&gt; performs two-way NAT functions, and NAT&#39;s the headers/URI&#39;s fo=
r inbound<br>
&gt; and outbound messaging. =A0Therefore, a request received on the public=
<br>
&gt; side from user@PBXIP is sent to the registrar as user@SBCPRIVATEIP. =
=A0The<br>
&gt; oposite direction (SSP -&gt; PBX) is received by the SBC as user@SSPIP=
 and<br>
&gt; NAT&#39;d to user@SBCPUBLICIP.<br>
&gt;<br>
&gt; &gt; Any<br>
&gt; &gt; requests from from the registrar/softswitch to the middlebox (des=
tined<br>
&gt;<br>
&gt; &gt; for the PBX) will only have user@middlebox, perhaps w/ a cookie.<=
br>
&gt; &gt; The middelbox<br>
&gt; &gt; needs to map user@middlebox to whatever IP/host originally regist=
ered.<br>
&gt; &gt; Today, the middlebox keeps a cache where the initial (individual)=
<br>
&gt; &gt; registration might be <a href=3D"mailto:user@1.1.1.1">user@1.1.1.=
1</a>, and the registration forwarded to<br>
&gt; &gt; the registrar is <a href=3D"mailto:user@2.2.2.2">user@2.2.2.2</a>=
. =A0That way when the registrar sends a<br>
&gt; &gt; request to the middlebox for <a href=3D"mailto:user@2.2.2.2">user=
@2.2.2.2</a> it maps it to <a href=3D"mailto:user@1.1.1.1">user@1.1.1.1</a>=
<br>
&gt; &gt; and all is good.<br>
&gt; &gt; If the middelbox doesn&#39;t have knowledge of the user (because =
of<br>
&gt; &gt; implicit),<br>
&gt; [JRE] Are you suggesting that each user behind the PBX would register<=
br>
&gt; with a different IP address, so you need to know whether it is user1 o=
r<br>
&gt; user2 in order to send requests to 11.11.11.11 or 22.22.22.22? If so,<=
br>
&gt; that is not the scenario that MARTINI is addressing. MARTINI is<br>
&gt; addressing the case where requests to user1, user2 etc. on a given PBX=
<br>
&gt; all need to be routed to the PBX&#39;s IP address. So as long as the<b=
r>
&gt; middlebox knows the request needs to go to the PBX, it doesn&#39;t nee=
d to<br>
&gt; know that particular user.<br>
&gt; [Tyler] Agreed, I shouldn&#39;t have used the term user. =A0The middle=
box in<br>
&gt; this scenario wouldn&#39;t care about individual users, it&#39;s point=
 of<br>
&gt; contact is the PBX. =A0All PBX&#39;s send register requests to the mid=
dlebox<br>
&gt; from different IP&#39;s/domains, granted. =A0After NAT, however, all t=
he<br>
&gt; requests from the SBC to the registrar appear to come from the same IP=
.<br>
&gt; We NAT in both directions, which is pretty standard, so we don&#39;t e=
xpose<br>
&gt; core equipment to the public, and we don&#39;t expose end user IP&#39;=
s to<br>
&gt; peers. =A0Plus it allows virtual route tables internally and resolves =
any<br>
&gt; issues with overlapping address space.<br>
&gt;<br>
&gt; &gt; it can&#39;t make the mapping unless it has something else to ass=
ociate to<br>
&gt;<br>
&gt; &gt; the original implicit reg (like a cookie, or knowledge of the<br>
&gt; &gt; extensions).<br>
&gt; &gt;<br>
&gt; &gt; Now concerning outbound requests (this was what my earlier messag=
e was<br>
&gt;<br>
&gt; &gt; about, although somewhere further back that got brought across to=
 this<br>
&gt;<br>
&gt; &gt; thread rather than the thread concerning outbound requests, so th=
e<br>
&gt; &gt; thread title was wrong). Assuming an entity has knowledge of<br>
&gt; &gt; registered E.164 numbers, it is not clear to me how it would deal=
 with<br>
&gt;<br>
&gt; &gt; a request where the From/PAI in the request from the PBX is not o=
ne of<br>
&gt;<br>
&gt; &gt; the implicitly registered ones. This can arise, for example, if t=
he<br>
&gt; &gt; request originates elsewhere in the enterprise and &quot;breaks o=
ut&quot; to the<br>
&gt;<br>
&gt; &gt; SSP via this particular PBX. Or if the call originated elsewhere =
and<br>
&gt; &gt; was forwarded by the PBX to the SSP. I appreciate that there may =
be<br>
&gt; &gt; some arrangements between PBX and SSP where this is forbidden by<=
br>
&gt; &gt; policy, but in the general case I would expect it to work, so tha=
t the<br>
&gt;<br>
&gt; &gt; callee has a correct AOR to which it can make a return call.<br>
&gt; &gt; [tyler] methods dealing with this situation today (A calls B, B<b=
r>
&gt; &gt; forwards the call to C) would use from=3DA and PAI=3DB, where B i=
s a<br>
&gt; &gt; registered endpoint (and billable by the SSP). =A0Not sure if tha=
t&#39;s<br>
&gt; &gt; what you&#39;re asking?<br>
&gt; [JRE] Yes, that was what I was asking, and I know that it sometimes<br=
>
&gt; works the way you describe, but this is bad because PAI=3DB is wrong -=
 it<br>
&gt; is not compliant with RFC 3325, since it is not the source of the<br>
&gt; request. If the callee used that to make a return call, the return cal=
l<br>
&gt; would arrive at the wrong place. For example, if a customer calls me o=
n<br>
&gt; my office number and the PBX forwards it to my home via the SSP, if my=
<br>
&gt; phone stores the PAI as the caller&#39;s number and I try to make a re=
turn<br>
&gt; call, the return call goes to my office phone, not to my customer.<br>
&gt; [Tyler] The source of the forward leg of the call is B, not A. =A0Call=
ing<br>
&gt; area requirements and n11 need to be based on B. =A0Why would the call=
ee<br>
&gt; use PAI to return a call? =A0That would be in violation of 3325 as wel=
l<br>
&gt; since it would obviate any callerid blocking/suppression requirements.=
<br>
&gt; I guess whether the PBX should strip PAI before sending it to your pho=
ne<br>
&gt; is arguable. =A0Agreed, using PAI to assert a different ID than From<b=
r>
&gt; (where from isn&#39;t private) might not strictly adhere to 3325, but =
I<br>
&gt; think alternate ID&#39;s vs suppressed ID&#39;s is splitting hairs a l=
ittle.<br>
&gt;<br>
&gt; John<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; martini mailing list<br>
&gt; <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/martini</a><br>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
</blockquote></div><br>

--00163602601f61d0b204826092a6--

From bruno.chatras@orange-ftgroup.com  Mon Mar 22 02:58:32 2010
Return-Path: <bruno.chatras@orange-ftgroup.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 1F7F73A68B9 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:58:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.384
X-Spam-Level: 
X-Spam-Status: No, score=-1.384 tagged_above=-999 required=5 tests=[AWL=-1.865, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 GW+MVcjA+v1I for <martini@core3.amsl.com>; Mon, 22 Mar 2010 02:58:30 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 8C1A33A688B for <martini@ietf.org>; Mon, 22 Mar 2010 02:58:25 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 6ADEA8B8020; Mon, 22 Mar 2010 10:56:46 +0000 (UTC)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id E3A1B8B802E; Mon, 22 Mar 2010 10:54:29 +0000 (UTC)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 22 Mar 2010 10:55:20 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAC9A5.C79138C7"
Date: Mon, 22 Mar 2010 10:55:18 +0100
Message-ID: <9ECCF01B52E7AB408A7EB85352642141013CE3FD@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <9ae56b1e1003220219o34769006h591b3c21451e31f@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] #17: Desirable to align with existing standards
Thread-Index: AcrJoO3R5SHT1kYvQxuKn7EmeeZ6mQABEU5Q
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org><A444A0F8084434499206E78C106220CABE982764@MCHP058A.global-ad.net><4BA38882.9000008@gmail.com><A444A0F8084434499206E78C106220CAC21E6B91@MCHP058A.global-ad.net><4BA6483D.2020402@ericsson.com><08244E6723F843F4BB4579F33DF4B1EF@china.huawei.com><A444A0F8084434499206E78C106220CADDE42862@MCHP058A.global-ad.net> <9ae56b1e1003220219o34769006h591b3c21451e31f@mail.gmail.com>
From: <bruno.chatras@orange-ftgroup.com>
To: <ietf.hanserik@gmail.com>, <john.elwell@siemens-enterprise.com>
X-OriginalArrivalTime: 22 Mar 2010 09:55:20.0191 (UTC) FILETIME=[C85E98F0:01CAC9A5]
Cc: martini@ietf.org
Subject: Re: [martini] #17: Desirable to align with existing standards
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, 22 Mar 2010 09:58:32 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CAC9A5.C79138C7
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Yes the method of constructing the new Request URI is the main concern. =
If the GIN draft is adopted as a basis for the IETF solution and is not =
modified on that point, a PBX will find different things in the Request =
URI of inbound requests depending on whether it is connected to an IMS =
or a GIN-based network. I don't believe that's what the Industry is =
looking for.


________________________________

	De : martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] De la =
part de Hans Erik van Elburg
	Envoy=E9 : lundi 22 mars 2010 10:19
	=C0 : Elwell, John
	Cc : martini@ietf.org
	Objet : Re: [martini] #17: Desirable to align with existing standards
=09
=09
	I think that a lot of valid issues have been raised with the existing =
proposed solution and I have nothing against solving those. I have a =
problem with a solution that can only handle E.164 numbers and can't =
even deliver the other variants of calls or requires a completely =
different solution. And with that my main concern is the method of =
constructing the new Request URI. If people want to use that solution =
they can do so anyway as it is legal according to RFC3261, you don't =
need an RFC for that.
=09
	BR,
	/Hans Erik van Elburg
=09
=09
	On Sun, Mar 21, 2010 at 10:09 PM, Elwell, John =
<john.elwell@siemens-enterprise.com> wrote:
=09

		Yes, I did reference this, but the nature of that standard (delta to a =
delta to a delta) is such that it requires a whole lot more digging to =
identify the specific aspects of the TISPAN/3GPP solution that that are =
germane to the issues we are talking about. I was hoping that Hans Erik =
could help us to nail down particular aspects of the solution, with =
appropriate references, that he believes we need to align with.
	=09
		John
	=09

		> -----Original Message-----
		> From: Spencer Dawkins [mailto:spencer@wonderhamster.org]
		> Sent: 21 March 2010 20:41
		> To: Gonzalo Camarillo; Elwell, John
		> Cc: martini@ietf.org
		> Subject: Re: [martini] #17: Desirable to align with existing =
standards
		>
		> Hi, Gonzalo,
		>
		> John had added
		>    [ETSI TS 182 025]
		>               "ETSI TS 182 025 "Telecommunications and Internet
		>               converged Services and Protocols for Advanced =
Networking
		>               (TISPAN); Business trunking; Architecture and =
functional
		>               description"".as a reference in
		>
		> http://tools.ietf.org/html/draft-ietf-martini-reqs-02 - I'm
		> not smart about
		> ETSI, but I had hoped that specification was the appropriate
		> reference :D
		>
		> Thanks,
		>
		> Spencer
		>
		> > Hi,
		> >
		> > well, I do not care who answers as long as the information
		> is sent ;o)
		> >
		> > Thanks,
		> >
		> > Gonzalo
		> >
		> > On 21/03/2010 7:20 AM, Elwell, John wrote:
		> >> I assume this request is directed at Hans Erik.
		> >>
		> >> John
		> >>
		> >>> -----Original Message-----
		> >>> From: Gonzalo Camarillo [mailto:gcamaril@gmail.com]
		> >>> Sent: 19 March 2010 14:22
		> >>> To: Elwell, John
		> >>> Cc: martini@ietf.org
		> >>> Subject: Re: [martini] #17: Desirable to align with
		> existing standards
		> >>>
		> >>> Hi,
		> >>>
		> >>> could you please provide references to the ETSI and 3GPP
		> >>> specs mentioned
		> >>> below?
		> >>>
		> >>> Thanks,
		> >>>
		> >>> Gonzalo
		> >>>
		> >>> On 19/03/2010 1:01 PM, Elwell, John wrote:
		> >>>> As individual, I would remark that the market is already
		> >>> fragmented between SIP and IMS-SIP, which makes things =
difficult.
		> >>>>
		> >>>> As editor, I seek guidance from others on this one.
		> >>>>
		> >>>> John
		> >>>>
		> >>>>> -----Original Message-----
		> >>>>> From: martini-bounces@ietf.org
		> >>>>> [mailto:martini-bounces@ietf.org] On Behalf Of martini
		> >>> issue tracker
		> >>>>> Sent: 18 March 2010 22:21
		> >>>>> To: ietf.hanserik@gmail.com
		> >>>>> Cc: martini@ietf.org
		> >>>>> Subject: [martini] #17: Desirable to align with
		> existing standards
		> >>>>>
		> >>>>> #17: Desirable to align with existing standards
		> >>>>> -------------------------------------+------------------------
		> >>>>> --------------
		> >>>>>  Reporter:  ietf.hanserik@...          |       Owner:
		> >>>>>      Type:  enhancement              |      Status:  new
		> >>>>>  Priority:  major                    |   Milestone:  =
milestone1
		> >>>>> Component:  reqs                     |     Version:  1.0
		> >>>>>  Severity:  In WG Last Call          |    Keywords:
		> >>>>> -------------------------------------+------------------------
		> >>>>> --------------
		> >>>>>  DES5 - The mechanism SHOULD be aligned as much as possible
		> >>>>> with mechanisms
		> >>>>>  already standardised in other SDO's like ETSI and 3GPP
		> in order to
		> >>>>>  prohibit a fragmentation of the market.
		> >>>>>
		> >>>>> --
		> >>>>> Ticket URL:
		> <http://trac.tools.ietf.org/wg/martini/trac/ticket/17>
		> >>>>> martini <http://tools.ietf.org/martini/>
		> >>>>>
		> >>>>> _______________________________________________
		> >>>>> martini mailing list
		> >>>>> martini@ietf.org
		> >>>>> https://www.ietf.org/mailman/listinfo/martini
		> >>>>>
		> >>>> _______________________________________________
		> >>>> martini mailing list
		> >>>> martini@ietf.org
		> >>>> https://www.ietf.org/mailman/listinfo/martini
		> >>>>
		> >>>
		> >> _______________________________________________
		> >> martini mailing list
		> >> martini@ietf.org
		> >> https://www.ietf.org/mailman/listinfo/martini
		> >>
		> >
		> > _______________________________________________
		> > martini mailing list
		> > martini@ietf.org
		> > https://www.ietf.org/mailman/listinfo/martini
		>
		>
		_______________________________________________
		martini mailing list
		martini@ietf.org
		https://www.ietf.org/mailman/listinfo/martini
	=09



------_=_NextPart_001_01CAC9A5.C79138C7
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D733095109-22032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Yes the method of constructing the new Request =
URI is the=20
main concern. If the GIN draft is adopted as a basis for the IETF =
solution and=20
is not modified on that point, <SPAN lang=3DFR>a PBX will find different =
things in=20
the Request URI of inbound requests depending on whether it is connected =
to an=20
IMS or a GIN-based network. I don't believe that's what the Industry is =
looking=20
for.</SPAN></FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Dfr dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>De&nbsp;:</B> martini-bounces@ietf.org =

  [mailto:martini-bounces@ietf.org] <B>De la part de</B> Hans Erik van=20
  Elburg<BR><B>Envoy=E9&nbsp;:</B> lundi 22 mars 2010 =
10:19<BR><B>=C0&nbsp;:</B>=20
  Elwell, John<BR><B>Cc&nbsp;:</B> =
martini@ietf.org<BR><B>Objet&nbsp;:</B> Re:=20
  [martini] #17: Desirable to align with existing =
standards<BR></FONT><BR></DIV>
  <DIV></DIV>I think that a lot of valid issues have been raised with =
the=20
  existing proposed solution and I have nothing against solving those. I =
have a=20
  problem with a solution that can only handle E.164 numbers and can't =
even=20
  deliver the other variants of calls or requires a completely different =

  solution. And with that my main concern is the method of constructing =
the new=20
  Request URI. If people want to use that solution they can do so anyway =
as it=20
  is legal according to RFC3261, you don't need an RFC for =
that.<BR><BR>BR,<BR=20
  clear=3Dall>/Hans Erik van Elburg<BR><BR>
  <DIV class=3Dgmail_quote>On Sun, Mar 21, 2010 at 10:09 PM, Elwell, =
John <SPAN=20
  dir=3Dltr>&lt;<A=20
  =
href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-en=
terprise.com</A>&gt;</SPAN>=20
  wrote:<BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">Yes,=20
    I did reference this, but the nature of that standard (delta to a =
delta to a=20
    delta) is such that it requires a whole lot more digging to identify =
the=20
    specific aspects of the TISPAN/3GPP solution that that are germane =
to the=20
    issues we are talking about. I was hoping that Hans Erik could help =
us to=20
    nail down particular aspects of the solution, with appropriate =
references,=20
    that he believes we need to align with.<BR><FONT=20
    color=3D#888888><BR>John<BR></FONT>
    <DIV>
    <DIV></DIV>
    <DIV class=3Dh5><BR>&gt; -----Original Message-----<BR>&gt; From: =
Spencer=20
    Dawkins [mailto:<A=20
    =
href=3D"mailto:spencer@wonderhamster.org">spencer@wonderhamster.org</A>]<=
BR>&gt;=20
    Sent: 21 March 2010 20:41<BR>&gt; To: Gonzalo Camarillo; Elwell,=20
    John<BR>&gt; Cc: <A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; =
Subject: Re:=20
    [martini] #17: Desirable to align with existing =
standards<BR>&gt;<BR>&gt;=20
    Hi, Gonzalo,<BR>&gt;<BR>&gt; John had added<BR>&gt; &nbsp; =
&nbsp;[ETSI TS=20
    182 025]<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
"ETSI TS=20
    182 025 "Telecommunications and Internet<BR>&gt; &nbsp; &nbsp; =
&nbsp; &nbsp;=20
    &nbsp; &nbsp; &nbsp; converged Services and Protocols for Advanced=20
    Networking<BR>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
    (TISPAN); Business trunking; Architecture and functional<BR>&gt; =
&nbsp;=20
    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; description"".as a =
reference=20
    in<BR>&gt;<BR>&gt; <A=20
    href=3D"http://tools.ietf.org/html/draft-ietf-martini-reqs-02"=20
    =
target=3D_blank>http://tools.ietf.org/html/draft-ietf-martini-reqs-02</A>=
 -=20
    I'm<BR>&gt; not smart about<BR>&gt; ETSI, but I had hoped that =
specification=20
    was the appropriate<BR>&gt; reference :D<BR>&gt;<BR>&gt;=20
    Thanks,<BR>&gt;<BR>&gt; Spencer<BR>&gt;<BR>&gt; &gt; Hi,<BR>&gt;=20
    &gt;<BR>&gt; &gt; well, I do not care who answers as long as the=20
    information<BR>&gt; is sent ;o)<BR>&gt; &gt;<BR>&gt; &gt; =
Thanks,<BR>&gt;=20
    &gt;<BR>&gt; &gt; Gonzalo<BR>&gt; &gt;<BR>&gt; &gt; On 21/03/2010 =
7:20 AM,=20
    Elwell, John wrote:<BR>&gt; &gt;&gt; I assume this request is =
directed at=20
    Hans Erik.<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; John<BR>&gt; =
&gt;&gt;<BR>&gt;=20
    &gt;&gt;&gt; -----Original Message-----<BR>&gt; &gt;&gt;&gt; From: =
Gonzalo=20
    Camarillo [mailto:<A=20
    href=3D"mailto:gcamaril@gmail.com">gcamaril@gmail.com</A>]<BR>&gt;=20
    &gt;&gt;&gt; Sent: 19 March 2010 14:22<BR>&gt; &gt;&gt;&gt; To: =
Elwell,=20
    John<BR>&gt; &gt;&gt;&gt; Cc: <A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; =
&gt;&gt;&gt;=20
    Subject: Re: [martini] #17: Desirable to align with<BR>&gt; existing =

    standards<BR>&gt; &gt;&gt;&gt;<BR>&gt; &gt;&gt;&gt; Hi,<BR>&gt;=20
    &gt;&gt;&gt;<BR>&gt; &gt;&gt;&gt; could you please provide =
references to the=20
    ETSI and 3GPP<BR>&gt; &gt;&gt;&gt; specs mentioned<BR>&gt; =
&gt;&gt;&gt;=20
    below?<BR>&gt; &gt;&gt;&gt;<BR>&gt; &gt;&gt;&gt; Thanks,<BR>&gt;=20
    &gt;&gt;&gt;<BR>&gt; &gt;&gt;&gt; Gonzalo<BR>&gt; =
&gt;&gt;&gt;<BR>&gt;=20
    &gt;&gt;&gt; On 19/03/2010 1:01 PM, Elwell, John wrote:<BR>&gt;=20
    &gt;&gt;&gt;&gt; As individual, I would remark that the market is=20
    already<BR>&gt; &gt;&gt;&gt; fragmented between SIP and IMS-SIP, =
which makes=20
    things difficult.<BR>&gt; &gt;&gt;&gt;&gt;<BR>&gt; &gt;&gt;&gt;&gt; =
As=20
    editor, I seek guidance from others on this one.<BR>&gt;=20
    &gt;&gt;&gt;&gt;<BR>&gt; &gt;&gt;&gt;&gt; John<BR>&gt;=20
    &gt;&gt;&gt;&gt;<BR>&gt; &gt;&gt;&gt;&gt;&gt; -----Original=20
    Message-----<BR>&gt; &gt;&gt;&gt;&gt;&gt; From: <A=20
    =
href=3D"mailto:martini-bounces@ietf.org">martini-bounces@ietf.org</A><BR>=
&gt;=20
    &gt;&gt;&gt;&gt;&gt; [mailto:<A=20
    =
href=3D"mailto:martini-bounces@ietf.org">martini-bounces@ietf.org</A>] =
On=20
    Behalf Of martini<BR>&gt; &gt;&gt;&gt; issue tracker<BR>&gt;=20
    &gt;&gt;&gt;&gt;&gt; Sent: 18 March 2010 22:21<BR>&gt; =
&gt;&gt;&gt;&gt;&gt;=20
    To: <A=20
    =
href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</A><BR>&g=
t;=20
    &gt;&gt;&gt;&gt;&gt; Cc: <A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt;=20
    &gt;&gt;&gt;&gt;&gt; Subject: [martini] #17: Desirable to align =
with<BR>&gt;=20
    existing standards<BR>&gt; &gt;&gt;&gt;&gt;&gt;<BR>&gt; =
&gt;&gt;&gt;&gt;&gt;=20
    #17: Desirable to align with existing standards<BR>&gt; =
&gt;&gt;&gt;&gt;&gt;=20
    =
-------------------------------------+------------------------<BR>&gt;=20
    &gt;&gt;&gt;&gt;&gt; --------------<BR>&gt; &gt;&gt;&gt;&gt;&gt;=20
    &nbsp;Reporter: &nbsp;ietf.hanserik@... &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;|=20
    &nbsp; &nbsp; &nbsp; Owner:<BR>&gt; &gt;&gt;&gt;&gt;&gt; &nbsp; =
&nbsp;=20
    &nbsp;Type: &nbsp;enhancement &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=20
    &nbsp;| &nbsp; &nbsp; &nbsp;Status: &nbsp;new<BR>&gt; =
&gt;&gt;&gt;&gt;&gt;=20
    &nbsp;Priority: &nbsp;major &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;=20
    &nbsp; &nbsp; &nbsp;| &nbsp; Milestone: &nbsp;milestone1<BR>&gt;=20
    &gt;&gt;&gt;&gt;&gt; Component: &nbsp;reqs &nbsp; &nbsp; &nbsp; =
&nbsp;=20
    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; Version:=20
    &nbsp;1.0<BR>&gt; &gt;&gt;&gt;&gt;&gt; &nbsp;Severity: &nbsp;In WG =
Last Call=20
    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp;Keywords:<BR>&gt;=20
    &gt;&gt;&gt;&gt;&gt;=20
    =
-------------------------------------+------------------------<BR>&gt;=20
    &gt;&gt;&gt;&gt;&gt; --------------<BR>&gt; &gt;&gt;&gt;&gt;&gt; =
&nbsp;DES5=20
    - The mechanism SHOULD be aligned as much as possible<BR>&gt;=20
    &gt;&gt;&gt;&gt;&gt; with mechanisms<BR>&gt; &gt;&gt;&gt;&gt;&gt;=20
    &nbsp;already standardised in other SDO's like ETSI and 3GPP<BR>&gt; =
in=20
    order to<BR>&gt; &gt;&gt;&gt;&gt;&gt; &nbsp;prohibit a fragmentation =
of the=20
    market.<BR>&gt; &gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt;&gt;&gt;&gt;&gt; =
--<BR>&gt;=20
    &gt;&gt;&gt;&gt;&gt; Ticket URL:<BR>&gt; &lt;<A=20
    href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/17"=20
    =
target=3D_blank>http://trac.tools.ietf.org/wg/martini/trac/ticket/17</A>&=
gt;<BR>&gt;=20
    &gt;&gt;&gt;&gt;&gt; martini &lt;<A =
href=3D"http://tools.ietf.org/martini/"=20
    target=3D_blank>http://tools.ietf.org/martini/</A>&gt;<BR>&gt;=20
    &gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt;&gt;&gt;&gt;&gt;=20
    _______________________________________________<BR>&gt; =
&gt;&gt;&gt;&gt;&gt;=20
    martini mailing list<BR>&gt; &gt;&gt;&gt;&gt;&gt; <A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt;=20
    &gt;&gt;&gt;&gt;&gt; <A =
href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
    =
target=3D_blank>https://www.ietf.org/mailman/listinfo/martini</A><BR>&gt;=
=20
    &gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt;&gt;&gt;&gt;=20
    _______________________________________________<BR>&gt; =
&gt;&gt;&gt;&gt;=20
    martini mailing list<BR>&gt; &gt;&gt;&gt;&gt; <A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; =
&gt;&gt;&gt;&gt;=20
    <A href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
    =
target=3D_blank>https://www.ietf.org/mailman/listinfo/martini</A><BR>&gt;=
=20
    &gt;&gt;&gt;&gt;<BR>&gt; &gt;&gt;&gt;<BR>&gt; &gt;&gt;=20
    _______________________________________________<BR>&gt; &gt;&gt; =
martini=20
    mailing list<BR>&gt; &gt;&gt; <A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; =
&gt;&gt; <A=20
    href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
    =
target=3D_blank>https://www.ietf.org/mailman/listinfo/martini</A><BR>&gt;=
=20
    &gt;&gt;<BR>&gt; &gt;<BR>&gt; &gt;=20
    _______________________________________________<BR>&gt; &gt; martini =
mailing=20
    list<BR>&gt; &gt; <A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; &gt; =
<A=20
    href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
    =
target=3D_blank>https://www.ietf.org/mailman/listinfo/martini</A><BR>&gt;=
<BR>&gt;<BR>_______________________________________________<BR>martini=20
    mailing list<BR><A =
href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR><A=20
    href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
    =
target=3D_blank>https://www.ietf.org/mailman/listinfo/martini</A><BR></DI=
V></DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CAC9A5.C79138C7--

From trac@tools.ietf.org  Mon Mar 22 08:07:22 2010
Return-Path: <trac@tools.ietf.org>
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 2399D3A6960 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 08:07:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.519
X-Spam-Level: 
X-Spam-Status: No, score=-100.519 tagged_above=-999 required=5 tests=[AWL=-1.649, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 RHZZWvO7Q6Ws for <martini@core3.amsl.com>; Mon, 22 Mar 2010 08:07:21 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 6C8AA3A691E for <martini@ietf.org>; Mon, 22 Mar 2010 08:07:21 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NtjE9-0001fy-72; Mon, 22 Mar 2010 08:07:37 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com, bernard_aboba@hotmail.com
X-Trac-Project: martini
Date: Mon, 22 Mar 2010 15:07:37 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/18
Message-ID: <067.d55f218aa49a60c488c40b0816b9c460@tools.ietf.org>
X-Trac-Ticket-ID: 18
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, bernard_aboba@hotmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #18: References
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 22 Mar 2010 15:07:22 -0000

#18: References
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  john.elwell@…                     
     Type:  defect                     |      Status:  new                               
 Priority:  minor                      |   Milestone:  milestone1                        
Component:  reqs                       |     Version:  1.0                               
 Severity:  In WG Last Call            |    Keywords:                                    
---------------------------------------+------------------------------------
 The requirements document currently references [ETSI TS 182 025]. It may
 be desirable to add additional references.

 From Hans Erik (see http://www.ietf.org/mail-
 archive/web/martini/current/msg01002.html):

 ETSI TS 181 019: "Telecommunications and Internet converged Services and
 Protocols for Advanced Networking (TISPAN); Business Communication
 Requirements".

 ETSI TS 182 023: "Telecommunications and Internet Converged Services and
 Protocols for Advanced Networking (TISPAN); Core and Enterprise NGN
 Interaction Scenarios and Architectural Requirements".

 ETSI TS 182 025 "Telecommunications and Internet converged Services and
 Protocols for Advanced Networking (TISPAN); Business trunking;
 Architecture and functional description

 3GPP I guess it is 24.229. But others are better equipped to answer that
 question.

 Best Regards,
 /Hans Erik van Elburg

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/18>
martini <http://tools.ietf.org/martini/>


From john.elwell@siemens-enterprise.com  Mon Mar 22 09:59:26 2010
Return-Path: <john.elwell@siemens-enterprise.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 395513A6978 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 09:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.21
X-Spam-Level: 
X-Spam-Status: No, score=-0.21 tagged_above=-999 required=5 tests=[AWL=-1.341,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
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 mLBc9kun7Dpz for <martini@core3.amsl.com>; Mon, 22 Mar 2010 09:59:25 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 30A283A6960 for <martini@ietf.org>; Mon, 22 Mar 2010 09:59:24 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1301076; Mon, 22 Mar 2010 17:59:39 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id 9944923F028E; Mon, 22 Mar 2010 17:59:39 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 22 Mar 2010 17:59:39 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "trac@localhost.localdomain" <trac@localhost.localdomain>, "bernard_aboba@hotmail.com" <bernard_aboba@hotmail.com>
Date: Mon, 22 Mar 2010 17:59:38 +0100
Thread-Topic: [martini] #18: References
Thread-Index: AcrJ0WzQQ+EwZegRQMKNlllNv1e+NwADqaDA
Message-ID: <A444A0F8084434499206E78C106220CADDE42E0C@MCHP058A.global-ad.net>
References: <067.d55f218aa49a60c488c40b0816b9c460@tools.ietf.org>
In-Reply-To: <067.d55f218aa49a60c488c40b0816b9c460@tools.ietf.org>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #18: References
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, 22 Mar 2010 16:59:26 -0000

I am not sure it is worth adding references to ETSI and 3GPP documents that=
 are already referenced from TS 182 025. However, to address the concerns r=
aised in #17, I think the WG needs to have more specific references to part=
icular aspects of these ETSI/3GPP documents that folks think we need compat=
ibility with and where the present gin-00 draft deviates. Whether these nee=
d to end up in the requirements document we can decide later, when we have =
a better understanding.

John=20

> -----Original Message-----
> From: martini issue tracker [mailto:trac@tools.ietf.org]=20
> Sent: 22 March 2010 08:08
> To: Elwell, John; bernard_aboba@hotmail.com
> Cc: martini@ietf.org
> Subject: [martini] #18: References
>=20
> #18: References
> ---------------------------------------+----------------------
> --------------
>  Reporter:  bernard_aboba@...            |       Owner: =20
> john.elwell@...                    =20
>      Type:  defect                     |      Status:  new   =20
>                           =20
>  Priority:  minor                      |   Milestone: =20
> milestone1                       =20
> Component:  reqs                       |     Version:  1.0   =20
>                           =20
>  Severity:  In WG Last Call            |    Keywords:        =20
>                           =20
> ---------------------------------------+----------------------
> --------------
>  The requirements document currently references [ETSI TS 182=20
> 025]. It may
>  be desirable to add additional references.
>=20
>  From Hans Erik (see http://www.ietf.org/mail-
>  archive/web/martini/current/msg01002.html):
>=20
>  ETSI TS 181 019: "Telecommunications and Internet converged=20
> Services and
>  Protocols for Advanced Networking (TISPAN); Business Communication
>  Requirements".
>=20
>  ETSI TS 182 023: "Telecommunications and Internet Converged=20
> Services and
>  Protocols for Advanced Networking (TISPAN); Core and Enterprise NGN
>  Interaction Scenarios and Architectural Requirements".
>=20
>  ETSI TS 182 025 "Telecommunications and Internet converged=20
> Services and
>  Protocols for Advanced Networking (TISPAN); Business trunking;
>  Architecture and functional description
>=20
>  3GPP I guess it is 24.229. But others are better equipped to=20
> answer that
>  question.
>=20
>  Best Regards,
>  /Hans Erik van Elburg
>=20
> --=20
> Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/18>
> martini <http://tools.ietf.org/martini/>
>=20
> =

From bruno.chatras@orange-ftgroup.com  Mon Mar 22 10:53:12 2010
Return-Path: <bruno.chatras@orange-ftgroup.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 B71CC3A69D1 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 10:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.011
X-Spam-Level: 
X-Spam-Status: No, score=-1.011 tagged_above=-999 required=5 tests=[AWL=-1.492, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 37Cbs6IxqQzN for <martini@core3.amsl.com>; Mon, 22 Mar 2010 10:53:11 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 956CA3A68B3 for <martini@ietf.org>; Mon, 22 Mar 2010 10:53:11 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 6377C8B8008; Mon, 22 Mar 2010 18:51:07 +0000 (UTC)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id 1510D8B8009; Mon, 22 Mar 2010 18:50:17 +0000 (UTC)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 22 Mar 2010 18:51:13 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Mar 2010 18:51:12 +0100
Message-ID: <9ECCF01B52E7AB408A7EB853526421410140023D@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <A444A0F8084434499206E78C106220CADDE42E0C@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] #18: References
Thread-Index: AcrJ0WzQQ+EwZegRQMKNlllNv1e+NwADqaDAAAH9vkA=
References: <067.d55f218aa49a60c488c40b0816b9c460@tools.ietf.org> <A444A0F8084434499206E78C106220CADDE42E0C@MCHP058A.global-ad.net>
From: <bruno.chatras@orange-ftgroup.com>
To: <john.elwell@siemens-enterprise.com>, <trac@localhost.localdomain>, <bernard_aboba@hotmail.com>
X-OriginalArrivalTime: 22 Mar 2010 17:51:13.0322 (UTC) FILETIME=[435CA0A0:01CAC9E8]
Cc: martini@ietf.org
Subject: Re: [martini] #18: References
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, 22 Mar 2010 17:53:12 -0000

The main aspect is the Request-URI for inbound requests. According to TS =
182 025, it contains the initial target identity. According to the =
gin-00 draft it will contain the registered contact.

> -----Message d'origine-----
> De : martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] De la part de Elwell, John
> Envoy=E9 : lundi 22 mars 2010 18:00
> =C0 : trac@localhost.localdomain; bernard_aboba@hotmail.com
> Cc : martini@ietf.org
> Objet : Re: [martini] #18: References
>=20
> I am not sure it is worth adding references to ETSI and 3GPP=20
> documents that are already referenced from TS 182 025.=20
> However, to address the concerns raised in #17, I think the=20
> WG needs to have more specific references to particular=20
> aspects of these ETSI/3GPP documents that folks think we need=20
> compatibility with and where the present gin-00 draft=20
> deviates. Whether these need to end up in the requirements=20
> document we can decide later, when we have a better understanding.
>=20
> John=20
>=20
> > -----Original Message-----
> > From: martini issue tracker [mailto:trac@tools.ietf.org]
> > Sent: 22 March 2010 08:08
> > To: Elwell, John; bernard_aboba@hotmail.com
> > Cc: martini@ietf.org
> > Subject: [martini] #18: References
> >=20
> > #18: References
> > ---------------------------------------+----------------------
> > --------------
> >  Reporter:  bernard_aboba@...            |       Owner: =20
> > john.elwell@...                    =20
> >      Type:  defect                     |      Status:  new   =20
> >                           =20
> >  Priority:  minor                      |   Milestone: =20
> > milestone1                       =20
> > Component:  reqs                       |     Version:  1.0   =20
> >                           =20
> >  Severity:  In WG Last Call            |    Keywords:        =20
> >                           =20
> > ---------------------------------------+----------------------
> > --------------
> >  The requirements document currently references [ETSI TS=20
> 182 025]. It=20
> > may  be desirable to add additional references.
> >=20
> >  From Hans Erik (see http://www.ietf.org/mail-
> >  archive/web/martini/current/msg01002.html):
> >=20
> >  ETSI TS 181 019: "Telecommunications and Internet=20
> converged Services=20
> > and  Protocols for Advanced Networking (TISPAN); Business=20
> > Communication  Requirements".
> >=20
> >  ETSI TS 182 023: "Telecommunications and Internet=20
> Converged Services=20
> > and  Protocols for Advanced Networking (TISPAN); Core and=20
> Enterprise=20
> > NGN  Interaction Scenarios and Architectural Requirements".
> >=20
> >  ETSI TS 182 025 "Telecommunications and Internet converged=20
> Services=20
> > and  Protocols for Advanced Networking (TISPAN); Business=20
> trunking; =20
> > Architecture and functional description
> >=20
> >  3GPP I guess it is 24.229. But others are better equipped=20
> to answer=20
> > that  question.
> >=20
> >  Best Regards,
> >  /Hans Erik van Elburg
> >=20
> > --
> > Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/18>
> > martini <http://tools.ietf.org/martini/>
> >=20
> >=20
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>=20

From dean.willis@softarmor.com  Mon Mar 22 11:18:21 2010
Return-Path: <dean.willis@softarmor.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 E23A43A6B59 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 11:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.39
X-Spam-Level: 
X-Spam-Status: No, score=0.39 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13]
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 m5qlsa7qT7C5 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 11:18:21 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 20DB63A6B5C for <martini@ietf.org>; Mon, 22 Mar 2010 11:18:20 -0700 (PDT)
Received: from [130.129.28.97] ([130.129.28.97]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id o2MIIXcr001536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 22 Mar 2010 13:18:35 -0500
Message-ID: <4BA7B474.1070501@softarmor.com>
Date: Mon, 22 Mar 2010 13:18:28 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: bruno.chatras@orange-ftgroup.com
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org><A444A0F8084434499206E78C106220CABE982764@MCHP058A.global-ad.net><4BA38882.9000008@gmail.com><A444A0F8084434499206E78C106220CAC21E6B91@MCHP058A.global-ad.net><4BA6483D.2020402@ericsson.com><08244E6723F843F4BB4579F33DF4B1EF@china.huawei.com><A444A0F8084434499206E78C106220CADDE42862@MCHP058A.global-ad.net>	<9ae56b1e1003220219o34769006h591b3c21451e31f@mail.gmail.com> <9ECCF01B52E7AB408A7EB85352642141013CE3FD@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <9ECCF01B52E7AB408A7EB85352642141013CE3FD@ftrdmel0.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: martini@ietf.org
Subject: Re: [martini] #17: Desirable to align with existing standards
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, 22 Mar 2010 18:18:22 -0000

bruno.chatras@orange-ftgroup.com wrote:
> Yes the method of constructing the new Request URI is the main concern.
> If the GIN draft is adopted as a basis for the IETF solution and is not
> modified on that point, a PBX will find different things in the Request
> URI of inbound requests depending on whether it is connected to an IMS
> or a GIN-based network. I don't believe that's what the Industry is
> looking for.
> 

If anybody bothered to adopt the IMS model, then a PBX would find
different things in the request URI depending on whether it registered
multiple AORs conventionally using RFC 3261 or used this "implicit bulk
registration" hack.

I don't believe that's what the industry is looking for.

I AM in favor of fixing RFC 3261's rather broken proxy contact-routing
model. MARTINI is not the place to do this; it's a much bigger problem
than we're chartered for (and no, IMS doesn't currently fix this in the
general case either -- it did a special-case bandaid that it a different
special-case than the one raised by SIP Forum).

--
Dean

From dean.willis@softarmor.com  Mon Mar 22 11:21:46 2010
Return-Path: <dean.willis@softarmor.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 BBBA43A6850 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 11:21:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.76
X-Spam-Level: 
X-Spam-Status: No, score=0.76 tagged_above=-999 required=5 tests=[AWL=-0.370,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
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 GrT+D9SbI8Hu for <martini@core3.amsl.com>; Mon, 22 Mar 2010 11:21:46 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id E30523A682E for <martini@ietf.org>; Mon, 22 Mar 2010 11:21:45 -0700 (PDT)
Received: from [130.129.28.97] ([130.129.28.97]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id o2MIM1Aa001595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 22 Mar 2010 13:22:03 -0500
Message-ID: <4BA7B544.40309@softarmor.com>
Date: Mon, 22 Mar 2010 13:21:56 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: bruno.chatras@orange-ftgroup.com
References: <067.d55f218aa49a60c488c40b0816b9c460@tools.ietf.org>	<A444A0F8084434499206E78C106220CADDE42E0C@MCHP058A.global-ad.net> <9ECCF01B52E7AB408A7EB853526421410140023D@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <9ECCF01B52E7AB408A7EB853526421410140023D@ftrdmel0.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: martini@ietf.org
Subject: Re: [martini] #18: References
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, 22 Mar 2010 18:21:46 -0000

bruno.chatras@orange-ftgroup.com wrote:
> The main aspect is the Request-URI for inbound requests. According to
> TS 182 025, it contains the initial target identity. According to the
> gin-00 draft it will contain the registered contact.
> 

And the main argument for the gin approach is because that's what is
done in RFC 3261 and devices based on that RFC. This allows "third
party" bulk registration to work with properly configured conventional
PBX (or other UAs) that are otherwise unaware of the extension. The IMS
approach requires a much more significant impact to the installed base.

--
Dean

From adam@nostrum.com  Mon Mar 22 11:25:25 2010
Return-Path: <adam@nostrum.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 E952A3A6952 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 11:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.541
X-Spam-Level: 
X-Spam-Status: No, score=-0.541 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, SPF_PASS=-0.001]
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 hHiqnDRyU8vE for <martini@core3.amsl.com>; Mon, 22 Mar 2010 11:25:25 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 1B3A03A69E5 for <martini@ietf.org>; Mon, 22 Mar 2010 11:25:23 -0700 (PDT)
Received: from dhcp-wireless-open-abg-24-56.meeting.ietf.org (dhcp-wireless-open-abg-24-56.meeting.ietf.org [130.129.24.56]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o2MIPcHa044224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Mar 2010 13:25:39 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4BA7B622.3010309@nostrum.com>
Date: Mon, 22 Mar 2010 11:25:38 -0700
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: bruno.chatras@orange-ftgroup.com
References: <067.d55f218aa49a60c488c40b0816b9c460@tools.ietf.org>	<A444A0F8084434499206E78C106220CADDE42E0C@MCHP058A.global-ad.net> <9ECCF01B52E7AB408A7EB853526421410140023D@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <9ECCF01B52E7AB408A7EB853526421410140023D@ftrdmel0.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Received-SPF: pass (nostrum.com: 130.129.24.56 is authenticated by a trusted mechanism)
Cc: bernard_aboba@hotmail.com, trac@localhost.localdomain, martini@ietf.org
Subject: Re: [martini] #18: References
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, 22 Mar 2010 18:25:26 -0000

Bruno:

I invite you to more carefully examine the example messages in section 
8.2 of the gin-01 draft.

/a

On 3/22/10 10:51 AM, bruno.chatras@orange-ftgroup.com wrote:
> The main aspect is the Request-URI for inbound requests. According to TS 182 025, it contains the initial target identity. According to the gin-00 draft it will contain the registered contact.
>
>    
>> -----Message d'origine-----
>> De : martini-bounces@ietf.org
>> [mailto:martini-bounces@ietf.org] De la part de Elwell, John
>> Envoyé : lundi 22 mars 2010 18:00
>> À : trac@localhost.localdomain; bernard_aboba@hotmail.com
>> Cc : martini@ietf.org
>> Objet : Re: [martini] #18: References
>>
>> I am not sure it is worth adding references to ETSI and 3GPP
>> documents that are already referenced from TS 182 025.
>> However, to address the concerns raised in #17, I think the
>> WG needs to have more specific references to particular
>> aspects of these ETSI/3GPP documents that folks think we need
>> compatibility with and where the present gin-00 draft
>> deviates. Whether these need to end up in the requirements
>> document we can decide later, when we have a better understanding.
>>
>> John
>>
>>      
>>> -----Original Message-----
>>> From: martini issue tracker [mailto:trac@tools.ietf.org]
>>> Sent: 22 March 2010 08:08
>>> To: Elwell, John; bernard_aboba@hotmail.com
>>> Cc: martini@ietf.org
>>> Subject: [martini] #18: References
>>>
>>> #18: References
>>> ---------------------------------------+----------------------
>>> --------------
>>>   Reporter:  bernard_aboba@...            |       Owner:
>>> john.elwell@...
>>>       Type:  defect                     |      Status:  new
>>>
>>>   Priority:  minor                      |   Milestone:
>>> milestone1
>>> Component:  reqs                       |     Version:  1.0
>>>
>>>   Severity:  In WG Last Call            |    Keywords:
>>>
>>> ---------------------------------------+----------------------
>>> --------------
>>>   The requirements document currently references [ETSI TS
>>>        
>> 182 025]. It
>>      
>>> may  be desirable to add additional references.
>>>
>>>   From Hans Erik (see http://www.ietf.org/mail-
>>>   archive/web/martini/current/msg01002.html):
>>>
>>>   ETSI TS 181 019: "Telecommunications and Internet
>>>        
>> converged Services
>>      
>>> and  Protocols for Advanced Networking (TISPAN); Business
>>> Communication  Requirements".
>>>
>>>   ETSI TS 182 023: "Telecommunications and Internet
>>>        
>> Converged Services
>>      
>>> and  Protocols for Advanced Networking (TISPAN); Core and
>>>        
>> Enterprise
>>      
>>> NGN  Interaction Scenarios and Architectural Requirements".
>>>
>>>   ETSI TS 182 025 "Telecommunications and Internet converged
>>>        
>> Services
>>      
>>> and  Protocols for Advanced Networking (TISPAN); Business
>>>        
>> trunking;
>>      
>>> Architecture and functional description
>>>
>>>   3GPP I guess it is 24.229. But others are better equipped
>>>        
>> to answer
>>      
>>> that  question.
>>>
>>>   Best Regards,
>>>   /Hans Erik van Elburg
>>>
>>> --
>>> Ticket URL:<http://trac.tools.ietf.org/wg/martini/trac/ticket/18>
>>> martini<http://tools.ietf.org/martini/>
>>>
>>>
>>>        
>> _______________________________________________
>> martini mailing list
>> martini@ietf.org
>> https://www.ietf.org/mailman/listinfo/martini
>>
>>      
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>    


From md3135@att.com  Mon Mar 22 11:28:46 2010
Return-Path: <md3135@att.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 A11863A68B6 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 11:28:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.469
X-Spam-Level: 
X-Spam-Status: No, score=-105.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_MED=-4,  USER_IN_WHITELIST=-100]
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 NVKYMU+qusZg for <martini@core3.amsl.com>; Mon, 22 Mar 2010 11:28:45 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by core3.amsl.com (Postfix) with ESMTP id 0B0143A688F for <martini@ietf.org>; Mon, 22 Mar 2010 11:28:44 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: md3135@att.com
X-Msg-Ref: server-15.tower-120.messagelabs.com!1269282541!25106915!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 11477 invoked from network); 22 Mar 2010 18:29:01 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-15.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Mar 2010 18:29:01 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o2MISng8024078 for <martini@ietf.org>; Mon, 22 Mar 2010 14:28:49 -0400
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o2MISiS9023983 for <martini@ietf.org>; Mon, 22 Mar 2010 14:28:44 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Mar 2010 14:28:54 -0400
Message-ID: <14C85D6CCBE92743AF33663BF5D24EBA0602ED82@gaalpa1msgusr7e.ugd.att.com>
In-Reply-To: <4BA7B474.1070501@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] #17: Desirable to align with existing standards
Thread-Index: AcrJ7B8V5lTvyWTtQ5euqq/4cjTNzQAAQfsg
References: <065.6d7dff0b1a1b8d1c69a7d94c4dd17866@tools.ietf.org><A444A0F8084434499206E78C106220CABE982764@MCHP058A.global-ad.net><4BA38882.9000008@gmail.com><A444A0F8084434499206E78C106220CAC21E6B91@MCHP058A.global-ad.net><4BA6483D.2020402@ericsson.com><08244E6723F843F4BB4579F33DF4B1EF@china.huawei.com><A444A0F8084434499206E78C106220CADDE42862@MCHP058A.global-ad.net>	<9ae56b1e1003220219o34769006h591b3c21451e31f@mail.gmail.com><9ECCF01B52E7AB408A7EB85352642141013CE3FD@ftrdmel0.rd.francetelecom.fr> <4BA7B474.1070501@softarmor.com>
From: "DOLLY, MARTIN C (ATTLABS)" <md3135@att.com>
To: "Dean Willis" <dean.willis@softarmor.com>, <bruno.chatras@orange-ftgroup.com>
Cc: martini@ietf.org
Subject: Re: [martini] #17: Desirable to align with existing standards
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, 22 Mar 2010 18:28:46 -0000

Disagree Dean. There is an IMS model which is being standardized, and to
that Bruno is correct. Then there is a non-IMS, where we already know
how to do this today.

-----Original Message-----
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On
Behalf Of Dean Willis
Sent: Monday, March 22, 2010 2:18 PM
To: bruno.chatras@orange-ftgroup.com
Cc: martini@ietf.org
Subject: Re: [martini] #17: Desirable to align with existing standards

bruno.chatras@orange-ftgroup.com wrote:
> Yes the method of constructing the new Request URI is the main
concern.
> If the GIN draft is adopted as a basis for the IETF solution and is
not
> modified on that point, a PBX will find different things in the
Request
> URI of inbound requests depending on whether it is connected to an IMS
> or a GIN-based network. I don't believe that's what the Industry is
> looking for.
>=20

If anybody bothered to adopt the IMS model, then a PBX would find
different things in the request URI depending on whether it registered
multiple AORs conventionally using RFC 3261 or used this "implicit bulk
registration" hack.

I don't believe that's what the industry is looking for.

I AM in favor of fixing RFC 3261's rather broken proxy contact-routing
model. MARTINI is not the place to do this; it's a much bigger problem
than we're chartered for (and no, IMS doesn't currently fix this in the
general case either -- it did a special-case bandaid that it a different
special-case than the one raised by SIP Forum).

--
Dean
_______________________________________________
martini mailing list
martini@ietf.org
https://www.ietf.org/mailman/listinfo/martini

From bruno.chatras@orange-ftgroup.com  Mon Mar 22 11:38:23 2010
Return-Path: <bruno.chatras@orange-ftgroup.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 8D1253A659A for <martini@core3.amsl.com>; Mon, 22 Mar 2010 11:38:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.762
X-Spam-Level: 
X-Spam-Status: No, score=-0.762 tagged_above=-999 required=5 tests=[AWL=-1.243, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 NZnOH0GpEkpA for <martini@core3.amsl.com>; Mon, 22 Mar 2010 11:38:22 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 3EB893A67F9 for <martini@ietf.org>; Mon, 22 Mar 2010 11:38:22 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id D7AB58B8006; Mon, 22 Mar 2010 19:37:28 +0000 (UTC)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id 899668B8003; Mon, 22 Mar 2010 19:37:18 +0000 (UTC)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 22 Mar 2010 19:37:56 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Mar 2010 19:37:56 +0100
Message-ID: <9ECCF01B52E7AB408A7EB853526421410140025E@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <4BA7B622.3010309@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] #18: References
Thread-Index: AcrJ7SixO4y4Jn6WQHWSc496GpIPkgAADEpg
References: <067.d55f218aa49a60c488c40b0816b9c460@tools.ietf.org>	<A444A0F8084434499206E78C106220CADDE42E0C@MCHP058A.global-ad.net> <9ECCF01B52E7AB408A7EB853526421410140023D@ftrdmel0.rd.francetelecom.fr> <4BA7B622.3010309@nostrum.com>
From: <bruno.chatras@orange-ftgroup.com>
To: <adam@nostrum.com>
X-OriginalArrivalTime: 22 Mar 2010 18:37:56.0623 (UTC) FILETIME=[CA4269F0:01CAC9EE]
Cc: bernard_aboba@hotmail.com, trac@localhost.localdomain, martini@ietf.org
Subject: Re: [martini] #18: References
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, 22 Mar 2010 18:38:23 -0000

I think I did it already but I should have said "a special contact built =
as described in the gin draft". In section 8.2 the R-URI =
contains:"+12145550105@pbx.example" which is different from the original =
target identity "sip:+12145550105@ssp.example.com". So there is indeed a =
difference with the 3GPP solution. It does not matter too much in =
practice because it's an E.164 number and the PBX will likely ignore the =
domain name anyway. However this prevents extending the solution to =
other forms of identities.

There is nothing new comapred to previous emails I sent but I was just =
answering John's request "to have more specific references to particular =
aspects of these ETSI/3GPP documents that folks think we need =
compatibility with and where the present gin-00 draft deviates."


> -----Message d'origine-----
> De : Adam Roach [mailto:adam@nostrum.com]=20
> Envoy=E9 : lundi 22 mars 2010 19:26
> =C0 : CHATRAS Bruno RD-CORE-ISS
> Cc : john.elwell@siemens-enterprise.com;=20
> trac@localhost.localdomain; bernard_aboba@hotmail.com;=20
> martini@ietf.org
> Objet : Re: [martini] #18: References
>=20
> Bruno:
>=20
> I invite you to more carefully examine the example messages in section
> 8.2 of the gin-01 draft.
>=20
> /a
>=20
> On 3/22/10 10:51 AM, bruno.chatras@orange-ftgroup.com wrote:
> > The main aspect is the Request-URI for inbound requests.=20
> According to TS 182 025, it contains the initial target=20
> identity. According to the gin-00 draft it will contain the=20
> registered contact.
> >
> >   =20
> >> -----Message d'origine-----
> >> De : martini-bounces@ietf.org
> >> [mailto:martini-bounces@ietf.org] De la part de Elwell,=20
> John Envoy=E9 :=20
> >> lundi 22 mars 2010 18:00 =C0 : trac@localhost.localdomain;=20
> >> bernard_aboba@hotmail.com Cc : martini@ietf.org Objet :=20
> Re: [martini]=20
> >> #18: References
> >>
> >> I am not sure it is worth adding references to ETSI and 3GPP=20
> >> documents that are already referenced from TS 182 025.
> >> However, to address the concerns raised in #17, I think=20
> the WG needs=20
> >> to have more specific references to particular aspects of these=20
> >> ETSI/3GPP documents that folks think we need compatibility=20
> with and=20
> >> where the present gin-00 draft deviates. Whether these=20
> need to end up=20
> >> in the requirements document we can decide later, when we have a=20
> >> better understanding.
> >>
> >> John
> >>
> >>     =20
> >>> -----Original Message-----
> >>> From: martini issue tracker [mailto:trac@tools.ietf.org]
> >>> Sent: 22 March 2010 08:08
> >>> To: Elwell, John; bernard_aboba@hotmail.com
> >>> Cc: martini@ietf.org
> >>> Subject: [martini] #18: References
> >>>
> >>> #18: References
> >>> ---------------------------------------+----------------------
> >>> --------------
> >>>   Reporter:  bernard_aboba@...            |       Owner:
> >>> john.elwell@...
> >>>       Type:  defect                     |      Status:  new
> >>>
> >>>   Priority:  minor                      |   Milestone:
> >>> milestone1
> >>> Component:  reqs                       |     Version:  1.0
> >>>
> >>>   Severity:  In WG Last Call            |    Keywords:
> >>>
> >>> ---------------------------------------+----------------------
> >>> --------------
> >>>   The requirements document currently references [ETSI TS
> >>>       =20
> >> 182 025]. It
> >>     =20
> >>> may  be desirable to add additional references.
> >>>
> >>>   From Hans Erik (see http://www.ietf.org/mail-
> >>>   archive/web/martini/current/msg01002.html):
> >>>
> >>>   ETSI TS 181 019: "Telecommunications and Internet
> >>>       =20
> >> converged Services
> >>     =20
> >>> and  Protocols for Advanced Networking (TISPAN); Business=20
> >>> Communication  Requirements".
> >>>
> >>>   ETSI TS 182 023: "Telecommunications and Internet
> >>>       =20
> >> Converged Services
> >>     =20
> >>> and  Protocols for Advanced Networking (TISPAN); Core and
> >>>       =20
> >> Enterprise
> >>     =20
> >>> NGN  Interaction Scenarios and Architectural Requirements".
> >>>
> >>>   ETSI TS 182 025 "Telecommunications and Internet converged
> >>>       =20
> >> Services
> >>     =20
> >>> and  Protocols for Advanced Networking (TISPAN); Business
> >>>       =20
> >> trunking;
> >>     =20
> >>> Architecture and functional description
> >>>
> >>>   3GPP I guess it is 24.229. But others are better equipped
> >>>       =20
> >> to answer
> >>     =20
> >>> that  question.
> >>>
> >>>   Best Regards,
> >>>   /Hans Erik van Elburg
> >>>
> >>> --
> >>> Ticket URL:<http://trac.tools.ietf.org/wg/martini/trac/ticket/18>
> >>> martini<http://tools.ietf.org/martini/>
> >>>
> >>>
> >>>       =20
> >> _______________________________________________
> >> martini mailing list
> >> martini@ietf.org
> >> https://www.ietf.org/mailman/listinfo/martini
> >>
> >>     =20
> > _______________________________________________
> > martini mailing list
> > martini@ietf.org
> > https://www.ietf.org/mailman/listinfo/martini
> >   =20
>=20
>=20

From HKaplan@acmepacket.com  Mon Mar 22 11:49:20 2010
Return-Path: <HKaplan@acmepacket.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 8BCDE3A6B57 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 11:49:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[AWL=-0.782,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
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 a9SgrUmAU+I0 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 11:49:19 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id A398D3A6A26 for <martini@ietf.org>; Mon, 22 Mar 2010 11:49:13 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Mon, 22 Mar 2010 14:49:29 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Mon, 22 Mar 2010 14:49:29 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "bruno.chatras@orange-ftgroup.com" <bruno.chatras@orange-ftgroup.com>, "john.elwell@siemens-enterprise.com" <john.elwell@siemens-enterprise.com>,  "trac@localhost.localdomain" <trac@localhost.localdomain>, "bernard_aboba@hotmail.com" <bernard_aboba@hotmail.com>
Date: Mon, 22 Mar 2010 14:49:26 -0400
Thread-Topic: [martini] #18: References
Thread-Index: AcrJ0WzQQ+EwZegRQMKNlllNv1e+NwADqaDAAAH9vkAAAcseMA==
Message-ID: <430FC6BDED356B4C8498F634416644A91A79CD19AD@mail>
References: <067.d55f218aa49a60c488c40b0816b9c460@tools.ietf.org> <A444A0F8084434499206E78C106220CADDE42E0C@MCHP058A.global-ad.net> <9ECCF01B52E7AB408A7EB853526421410140023D@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <9ECCF01B52E7AB408A7EB853526421410140023D@ftrdmel0.rd.francetelecom.fr>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #18: References
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, 22 Mar 2010 18:49:20 -0000

> -----Original Message-----
> From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behal=
f
> Of bruno.chatras@orange-ftgroup.com
> Sent: Monday, March 22, 2010 1:51 PM
>=20
> The main aspect is the Request-URI for inbound requests. According to TS
> 182 025, it contains the initial target identity.=20

Yes, but that's one of the issues I think: it *shouldn't* contain the initi=
al target identity.  Not completely/exactly.  The target identity's host/do=
main portion was the SSP's domain - the PBX is not in the SSP's domain, is =
not authoritative for the SSP's domain, and many of them won't accept it wi=
th the SSP's domain.  For example, a middlebox often re-writes it to be the=
 PBX's domain/IP.=20

I know it's not always done, and not a universal problem - but that's part =
of the problem - what needs to be signaled is not universally the same/cons=
istent.

For example, if this was a traditional static or rfc3261/3263 "peering" rel=
ationship to the PBX, the request-URI would have been re-targeted to the PB=
X's domain - not left alone.

-hadriel

From ietf.hanserik@gmail.com  Mon Mar 22 12:25:14 2010
Return-Path: <ietf.hanserik@gmail.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 CF53C3A6B2B for <martini@core3.amsl.com>; Mon, 22 Mar 2010 12:25:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.063
X-Spam-Level: 
X-Spam-Status: No, score=0.063 tagged_above=-999 required=5 tests=[AWL=-1.069,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 IpkSXoN6Ctmk for <martini@core3.amsl.com>; Mon, 22 Mar 2010 12:25:13 -0700 (PDT)
Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216]) by core3.amsl.com (Postfix) with ESMTP id 193483A6901 for <martini@ietf.org>; Mon, 22 Mar 2010 12:25:09 -0700 (PDT)
Received: by ewy8 with SMTP id 8so340900ewy.28 for <martini@ietf.org>; Mon, 22 Mar 2010 12:25:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=y5APFfkAexG3RYzmsVHEexcVvCo3NXkqSkp5bj0Mho8=; b=OE58wMBRrzDA/1e7c15ZvQVS07VTDpQhu2MqU0/eWTF1uS4eAFT5rZmtsMrjvFPlNe 1CjBRSLnChmL8A97perpsOBz+kX62muqNLVRy2DPY8/NQYIUkPeLUIjcwGSlWRN+i6m8 6W9Vot4S8WiORmk8YGQ94GoW1mizypMqpoCM0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=RCkJFdkds22uCtqS2/9SRw0NI9CdN9wWs+F+HIoVDfwMgwtL//d9q2k/tSq7ppcO84 FoF8PUQYkRLjn7037YVBai5y0vRxK/q4He9+hPHTEfmpSOkLXERsWP7/7wNUlGoeqQZl xPeP7e3ZDyoqhRUN+VVzHrV3CK6RLFBq7e//Y=
MIME-Version: 1.0
Received: by 10.213.34.79 with HTTP; Mon, 22 Mar 2010 12:25:23 -0700 (PDT)
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79CD19AD@mail>
References: <067.d55f218aa49a60c488c40b0816b9c460@tools.ietf.org> <A444A0F8084434499206E78C106220CADDE42E0C@MCHP058A.global-ad.net> <9ECCF01B52E7AB408A7EB853526421410140023D@ftrdmel0.rd.francetelecom.fr> <430FC6BDED356B4C8498F634416644A91A79CD19AD@mail>
Date: Mon, 22 Mar 2010 20:25:23 +0100
Received: by 10.213.43.14 with SMTP id u14mr242985ebe.19.1269285923726; Mon,  22 Mar 2010 12:25:23 -0700 (PDT)
Message-ID: <9ae56b1e1003221225h675b22etf7b8f128f8748834@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Content-Type: multipart/alternative; boundary=0016362571249a37e8048268a8b2
Cc: "bernard_aboba@hotmail.com" <bernard_aboba@hotmail.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #18: References
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, 22 Mar 2010 19:25:14 -0000

--0016362571249a37e8048268a8b2
Content-Type: text/plain; charset=ISO-8859-1

That thae PBX can not accept the SSP domain is an assumption, there are
several possibilities:
- the arrangement indeed uses the service provider domain, in this case a
pbx using this configuration that receives requests via the trunk should
just happily accepts such requests as it was configured to do so.
- if the arrangenment does use the corporate domain then there is also not
an issue.

The problem is only there if one has to assume that the PBX does not need
any adaptation towards this mechanism, but then it will also not support the
special option tag etc. And for that one has to fallback on the famous
middlebox anyway.

/Hans Erik van Elburg


On Mon, Mar 22, 2010 at 7:49 PM, Hadriel Kaplan <HKaplan@acmepacket.com>wrote:

>
>
> > -----Original Message-----
> > From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On
> Behalf
> > Of bruno.chatras@orange-ftgroup.com
> > Sent: Monday, March 22, 2010 1:51 PM
> >
> > The main aspect is the Request-URI for inbound requests. According to TS
> > 182 025, it contains the initial target identity.
>
> Yes, but that's one of the issues I think: it *shouldn't* contain the
> initial target identity.  Not completely/exactly.  The target identity's
> host/domain portion was the SSP's domain - the PBX is not in the SSP's
> domain, is not authoritative for the SSP's domain, and many of them won't
> accept it with the SSP's domain.  For example, a middlebox often re-writes
> it to be the PBX's domain/IP.
>
> I know it's not always done, and not a universal problem - but that's part
> of the problem - what needs to be signaled is not universally the
> same/consistent.
>
> For example, if this was a traditional static or rfc3261/3263 "peering"
> relationship to the PBX, the request-URI would have been re-targeted to the
> PBX's domain - not left alone.
>
> -hadriel
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>

--0016362571249a37e8048268a8b2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

That thae PBX can not accept the SSP domain is an assumption, there are sev=
eral possibilities:<br>- the arrangement indeed uses the service provider d=
omain, in this case a pbx using this configuration that receives requests v=
ia the trunk should just happily accepts such requests as it was configured=
 to do so.<br>
- if the arrangenment does use the corporate domain then there is also not =
an issue.<br><br>The problem is only there if one has to assume that the PB=
X does not need any adaptation towards this mechanism, but then it will als=
o not support the special option tag etc. And for that one has to fallback =
on the famous middlebox anyway.<br>
<br clear=3D"all">/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Mon, Mar 22, 2010 at 7:49 PM, Hadriel=
 Kaplan <span dir=3D"ltr">&lt;<a href=3D"mailto:HKaplan@acmepacket.com">HKa=
plan@acmepacket.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204=
, 204); padding-left: 1ex;">
<div class=3D"im"><br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:martini-bounces@ietf.org">martini-bounces@ietf=
.org</a> [mailto:<a href=3D"mailto:martini-bounces@ietf.org">martini-bounce=
s@ietf.org</a>] On Behalf<br>
&gt; Of <a href=3D"mailto:bruno.chatras@orange-ftgroup.com">bruno.chatras@o=
range-ftgroup.com</a><br>
&gt; Sent: Monday, March 22, 2010 1:51 PM<br>
&gt;<br>
&gt; The main aspect is the Request-URI for inbound requests. According to =
TS<br>
&gt; 182 025, it contains the initial target identity.<br>
<br>
</div>Yes, but that&#39;s one of the issues I think: it *shouldn&#39;t* con=
tain the initial target identity. =A0Not completely/exactly. =A0The target =
identity&#39;s host/domain portion was the SSP&#39;s domain - the PBX is no=
t in the SSP&#39;s domain, is not authoritative for the SSP&#39;s domain, a=
nd many of them won&#39;t accept it with the SSP&#39;s domain. =A0For examp=
le, a middlebox often re-writes it to be the PBX&#39;s domain/IP.<br>

<br>
I know it&#39;s not always done, and not a universal problem - but that&#39=
;s part of the problem - what needs to be signaled is not universally the s=
ame/consistent.<br>
<br>
For example, if this was a traditional static or rfc3261/3263 &quot;peering=
&quot; relationship to the PBX, the request-URI would have been re-targeted=
 to the PBX&#39;s domain - not left alone.<br>
<font color=3D"#888888"><br>
-hadriel<br>
</font><div><div></div><div class=3D"h5">__________________________________=
_____________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
</div></div></blockquote></div><br>

--0016362571249a37e8048268a8b2--

From spencer@wonderhamster.org  Mon Mar 22 12:33:36 2010
Return-Path: <spencer@wonderhamster.org>
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 AE8C828C101 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 12:33:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.432
X-Spam-Level: *
X-Spam-Status: No, score=1.432 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, STOX_REPLY_TYPE=0.001]
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 yiJeCUmfsXXU for <martini@core3.amsl.com>; Mon, 22 Mar 2010 12:33:36 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id ED13A3A67F0 for <martini@ietf.org>; Mon, 22 Mar 2010 12:33:35 -0700 (PDT)
Received: from S73602b (dhcp-wireless-open-abg-28-253.meeting.ietf.org [130.129.28.253]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0LjZyK-1NMfYG232G-00bPKg; Mon, 22 Mar 2010 15:33:50 -0400
Message-ID: <23BB987942DB4FEEA7F3A795C578F915@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Hans Erik van Elburg" <ietf.hanserik@gmail.com>, "Hadriel Kaplan" <HKaplan@acmepacket.com>
References: <067.d55f218aa49a60c488c40b0816b9c460@tools.ietf.org><A444A0F8084434499206E78C106220CADDE42E0C@MCHP058A.global-ad.net><9ECCF01B52E7AB408A7EB853526421410140023D@ftrdmel0.rd.francetelecom.fr><430FC6BDED356B4C8498F634416644A91A79CD19AD@mail> <9ae56b1e1003221225h675b22etf7b8f128f8748834@mail.gmail.com>
Date: Mon, 22 Mar 2010 14:33:35 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX19yvMxTJWQT0RO3STA5BSIfB1uhTBkERb7V3Vo zWnTaNPVmVG1L5ygrB2mOvYag+rmDE6yCc/OCEmt1UPA+jzpQZ fiaDOs6ev6BCDzhGsJzt/+pgaspN6khsdpcTK4B50k=
Cc: bernard_aboba@hotmail.com, martini@ietf.org
Subject: Re: [martini] #18: References
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, 22 Mar 2010 19:33:36 -0000

As chair - I hope that we have a good discussion, with good remote 
participation, in the Martini session that starts in about 27 minutes ;-)

Spencer 


From adam@nostrum.com  Mon Mar 22 13:17:21 2010
Return-Path: <adam@nostrum.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 BD8D33A6880 for <martini@core3.amsl.com>; Mon, 22 Mar 2010 13:17:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.005
X-Spam-Level: 
X-Spam-Status: No, score=-1.005 tagged_above=-999 required=5 tests=[AWL=0.465,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, SPF_PASS=-0.001]
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 u+-NLZ4-jukK for <martini@core3.amsl.com>; Mon, 22 Mar 2010 13:17:20 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id A45063A6B7F for <martini@ietf.org>; Mon, 22 Mar 2010 13:17:04 -0700 (PDT)
Received: from dhcp-wireless-open-abg-24-56.meeting.ietf.org (dhcp-wireless-open-abg-24-56.meeting.ietf.org [130.129.24.56]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o2MKHIKh052564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Mar 2010 15:17:20 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4BA7D04E.1090802@nostrum.com>
Date: Mon, 22 Mar 2010 13:17:18 -0700
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: bruno.chatras@orange-ftgroup.com
References: <067.d55f218aa49a60c488c40b0816b9c460@tools.ietf.org>	<A444A0F8084434499206E78C106220CADDE42E0C@MCHP058A.global-ad.net> <9ECCF01B52E7AB408A7EB853526421410140023D@ftrdmel0.rd.francetelecom.fr> <4BA7B622.3010309@nostrum.com> <9ECCF01B52E7AB408A7EB853526421410140025E@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <9ECCF01B52E7AB408A7EB853526421410140025E@ftrdmel0.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 130.129.24.56 is authenticated by a trusted mechanism)
Cc: bernard_aboba@hotmail.com, martini@ietf.org
Subject: Re: [martini] #18: References
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, 22 Mar 2010 20:17:21 -0000

On 3/22/10 11:37 AM, bruno.chatras@orange-ftgroup.com wrote:
> I think I did it already but I should have said "a special contact built as described in the gin draft". In section 8.2 the R-URI contains:"+12145550105@pbx.example" which is different from the original target identity "sip:+12145550105@ssp.example.com". So there is indeed a difference with the 3GPP solution.

Certainly you recognize that, for the example in section 8.2,  
everything other that the user portion of the URI is under the complete 
and total, unfettered control of the PBX, right? The PBX can put 
whatever it wants in there, even if it is something as inadvisable as 
the SSP's domain. The GIN draft does nothing to prevent it. I don't 
think it's a good idea, but there's nothing to stop it.

/a

From trac@tools.ietf.org  Tue Mar 23 02:04:38 2010
Return-Path: <trac@tools.ietf.org>
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 8C4383A68BA for <martini@core3.amsl.com>; Tue, 23 Mar 2010 02:04:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.87
X-Spam-Level: 
X-Spam-Status: No, score=-98.87 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 xtxAheGEBmWJ for <martini@core3.amsl.com>; Tue, 23 Mar 2010 02:04:37 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id EC6263A688A for <martini@ietf.org>; Tue, 23 Mar 2010 02:04:34 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nu02f-0003lY-97; Tue, 23 Mar 2010 02:04:53 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: ietf.hanserik@gmail.com
X-Trac-Project: martini
Date: Tue, 23 Mar 2010 09:04:53 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/19
Message-ID: <065.085b3ce99cf6d76da0963ed019c27c11@tools.ietf.org>
X-Trac-Ticket-ID: 19
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: ietf.hanserik@gmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #19: Remove DES4
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 23 Mar 2010 09:04:38 -0000

#19: Remove DES4
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |       Owner:            
     Type:  defect                   |      Status:  new       
 Priority:  major                    |   Milestone:  milestone1
Component:  reqs                     |     Version:  1.0       
 Severity:  In WG Last Call          |    Keywords:            
-------------------------------------+--------------------------------------
 Please remove DES4, there is no objective means to measure compliance.

 I re-raised this in the jabberroom as the editor seemed to have missed
 this comment, but the comment was not forwarded to the room.

 See also:
 http://www.ietf.org/mail-archive/web/martini/current/msg00982.html

 Bernard suggested replacing it with more objective requirements:
 http://www.ietf.org/mail-archive/web/martini/current/msg00983.html

 That is also fine. But maybe more trackable as a separate issues.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/19>
martini <http://tools.ietf.org/martini/>


From john.elwell@siemens-enterprise.com  Tue Mar 23 07:48:28 2010
Return-Path: <john.elwell@siemens-enterprise.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 F1E333A69E8 for <martini@core3.amsl.com>; Tue, 23 Mar 2010 07:48:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.131
X-Spam-Level: *
X-Spam-Status: No, score=1.131 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
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 XrZE2dpVYAbc for <martini@core3.amsl.com>; Tue, 23 Mar 2010 07:48:28 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id C2C4B3A67A2 for <martini@ietf.org>; Tue, 23 Mar 2010 07:48:27 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1313025; Tue, 23 Mar 2010 15:48:45 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id B7C3923F02AE; Tue, 23 Mar 2010 15:48:45 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Tue, 23 Mar 2010 15:48:45 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "trac@localhost.amsl.com" <trac@localhost.amsl.com>, "ietf.hanserik@gmail.com" <ietf.hanserik@gmail.com>
Date: Tue, 23 Mar 2010 15:48:44 +0100
Thread-Topic: [martini]  #19: Remove DES4
Thread-Index: AcrKZ+5GHu6R9JkRRlCsx8SbCumbPgAL0AuQ
Message-ID: <A444A0F8084434499206E78C106220CADDE433CE@MCHP058A.global-ad.net>
References: <065.085b3ce99cf6d76da0963ed019c27c11@tools.ietf.org>
In-Reply-To: <065.085b3ce99cf6d76da0963ed019c27c11@tools.ietf.org>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #19: Remove DES4
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, 23 Mar 2010 14:48:29 -0000

Sorry, #19 wasn't there when I prepared my slides. I have some sympathy for=
 removing this, since it is impossible to say whether a given solution comp=
lies or not. In fact, having assessed gin-01 against req-02, DES4 was the o=
nly one where the answer is not clearly "yes".

So if no objections, I will remove it as a formal requirement.

John

> -----Original Message-----
> From: martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] On Behalf Of martini issue tracker
> Sent: 23 March 2010 02:05
> To: ietf.hanserik@gmail.com
> Cc: martini@ietf.org
> Subject: [martini] #19: Remove DES4
>=20
> #19: Remove DES4
> -------------------------------------+------------------------
> --------------
>  Reporter:  ietf.hanserik@...          |       Owner:           =20
>      Type:  defect                   |      Status:  new      =20
>  Priority:  major                    |   Milestone:  milestone1
> Component:  reqs                     |     Version:  1.0      =20
>  Severity:  In WG Last Call          |    Keywords:           =20
> -------------------------------------+------------------------
> --------------
>  Please remove DES4, there is no objective means to measure=20
> compliance.
>=20
>  I re-raised this in the jabberroom as the editor seemed to=20
> have missed
>  this comment, but the comment was not forwarded to the room.
>=20
>  See also:
>  http://www.ietf.org/mail-archive/web/martini/current/msg00982.html
>=20
>  Bernard suggested replacing it with more objective requirements:
>  http://www.ietf.org/mail-archive/web/martini/current/msg00983.html
>=20
>  That is also fine. But maybe more trackable as a separate issues.
>=20
> --=20
> Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/19>
> martini <http://tools.ietf.org/martini/>
>=20
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
> =

From trac@tools.ietf.org  Tue Mar 23 10:27:01 2010
Return-Path: <trac@tools.ietf.org>
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 5622D3A6CCC for <martini@core3.amsl.com>; Tue, 23 Mar 2010 10:27:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.87
X-Spam-Level: 
X-Spam-Status: No, score=-98.87 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 Ai+QgP66qaev for <martini@core3.amsl.com>; Tue, 23 Mar 2010 10:27:00 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 9E0C73A6CC8 for <martini@ietf.org>; Tue, 23 Mar 2010 10:26:59 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nu7ss-0001DC-St; Tue, 23 Mar 2010 10:27:18 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: ietf.hanserik@gmail.com
X-Trac-Project: martini
Date: Tue, 23 Mar 2010 17:27:18 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/20
Message-ID: <065.606d2b6083a21b5a6fdc3bf7754c2d3e@tools.ietf.org>
X-Trac-Ticket-ID: 20
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: ietf.hanserik@gmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #20: Section 3.1.2 does not decscribe an issue
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 23 Mar 2010 17:27:01 -0000

#20: Section 3.1.2 does not decscribe an issue
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |       Owner:            
     Type:  defect                   |      Status:  new       
 Priority:  minor                    |   Milestone:  milestone1
Component:  reqs                     |     Version:  1.0       
 Severity:  In WG Last Call          |    Keywords:            
-------------------------------------+--------------------------------------
 Section "3.1.2. Undefined behaviour on PAU mismatch" describes a non-
 issue. It is the same as if we would make it an issue when subscribing for
 someones location and get unexpected locations returned. It also assumes
 that matching needs to take place in the PBX with some other predefined
 (?) list.

 Suggest to remove this section.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/20>
martini <http://tools.ietf.org/martini/>


From francois.audet@skype.net  Tue Mar 23 10:39:33 2010
Return-Path: <francois.audet@skype.net>
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 7A60A3A68F1 for <martini@core3.amsl.com>; Tue, 23 Mar 2010 10:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.169
X-Spam-Level: 
X-Spam-Status: No, score=-7.169 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HABEAS_ACCREDITED_SOI=-4.3, 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 tZiGWIjjxukP for <martini@core3.amsl.com>; Tue, 23 Mar 2010 10:39:32 -0700 (PDT)
Received: from rhv-mipot-001.corp.ebay.com (rhv-mipot-001.corp.ebay.com [216.33.244.6]) by core3.amsl.com (Postfix) with ESMTP id 93BCD3A686C for <martini@ietf.org>; Tue, 23 Mar 2010 10:39:32 -0700 (PDT)
X-EBay-Corp: Yes
X-IronPort-AV: E=Sophos;i="4.51,296,1267430400"; d="scan'208";a="55919493"
Received: from rhv-vtenf-001.corp.ebay.com (HELO RHV-MEXHT-001.corp.ebay.com) ([10.112.113.52]) by rhv-mipot-001.corp.ebay.com with ESMTP; 23 Mar 2010 10:39:52 -0700
Received: from RHV-MEXMS-006.corp.ebay.com ([10.245.17.140]) by RHV-MEXHT-001.corp.ebay.com ([10.245.24.100]) with mapi; Tue, 23 Mar 2010 10:39:51 -0700
From: "Audet, Francois" <francois.audet@skype.net>
To: "martini@ietf.org" <martini@ietf.org>
Date: Tue, 23 Mar 2010 10:39:50 -0700
Thread-Topic: Comments on draft-roach-martini-gin-01
Thread-Index: AcrKr9Z5iXh4s8UeQm2+8ab8Z6ZvRQ==
Message-ID: <64EA3B56-2790-4E46-BD67-4253AD918EEC@skype.net>
References: <065.085b3ce99cf6d76da0963ed019c27c11@tools.ietf.org> <A444A0F8084434499206E78C106220CADDE433CE@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CADDE433CE@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-ems-proccessed: 10SqDH0iR7ekR7SRpKqm5A==
x-ems-stamp: 6jxPV+fnMP77HX57TN7UZQ==
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter: Scanned
Cc: Theo Zourzouvillys <theo.zourzouvillys@skype.net>
Subject: [martini] Comments on draft-roach-martini-gin-01
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, 23 Mar 2010 17:39:33 -0000

Hi all,

I had a quick look at draft-roach-martini-gin-01, and specifically at secti=
ons 7.1, 7.3, 7.4, 7.5.

I don't believe that it makes any sense to have sections 7.3 (on Outbound),=
 7.4 (on Path) and section 7.5 (Service route) as separate sections.

In particular, I feel the topic of outbound is really intertwined with sect=
ion 7.1 (GRUU).

Section 7.1 talks first about Self-made GRUUs (7.1.1) and then Anonymous GR=
UUs (7.1.2). When I read this section, it feels very theoretical to me (as =
it is crafted on the GRUU specification). The second paragraph of 7.1.2.1 a=
ttempts to explain when a self-made GRUU is not appropriate, but it is not =
easy to follow.

Rather, it seems to me that we should think about what is our target audien=
ce for this specification: who will be deploying this? For example, it seem=
s to me that lots of PBXs will be deployed behind a NAT/FW. This points to =
the use of Outbound. Furthermore, the fact that many virtual end-users are =
effectively using the same registration, it seems to me that a good high-av=
ailability mechanism (multiple signaling connections) is required, in case =
a connection fails. Again, this points to using Outbound.

In other words, the questions the reader will have is more likely to be "Am=
 I using this behind a NAT/FW?" and "Do I need redundant signaling connecti=
ons?", rather than "Do I want to use a self-made GRUU?" or "Do I want an an=
onymous public GRUU?".

I would therefore rewrite section 7.1 to talk about the topology of the dep=
loyment first. In the more common deployment model, this will imply Outboun=
d (which includes support for Path, and the +sip.instance). Sections 7.3-7.=
5 can then be eliminated. The use of the "self-made" GRUUs will be restrict=
ed to the case of "I'm not behind a NAT/FW", and "I don't need multiple sig=
naling connections".

PS: I really don't see much to be said about Service routes.=

From trac@tools.ietf.org  Tue Mar 23 10:53:00 2010
Return-Path: <trac@tools.ietf.org>
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 5F5AD3A6D4F for <martini@core3.amsl.com>; Tue, 23 Mar 2010 10:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.87
X-Spam-Level: 
X-Spam-Status: No, score=-98.87 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 SCkWxY+X0kyG for <martini@core3.amsl.com>; Tue, 23 Mar 2010 10:52:59 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 3FF633A6C41 for <martini@ietf.org>; Tue, 23 Mar 2010 10:41:52 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nu87I-0006Fa-7q; Tue, 23 Mar 2010 10:42:12 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: ietf.hanserik@gmail.com
X-Trac-Project: martini
Date: Tue, 23 Mar 2010 17:42:12 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/21
Message-ID: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org>
X-Trac-Ticket-ID: 21
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: ietf.hanserik@gmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #21: 3.2.2 describes an issue with some PBX
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 23 Mar 2010 17:53:00 -0000

#21: 3.2.2 describes an issue with some PBX
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |       Owner:            
     Type:  defect                   |      Status:  new       
 Priority:  minor                    |   Milestone:  milestone1
Component:  reqs                     |     Version:  1.0       
 Severity:  In WG Last Call          |    Keywords:            
-------------------------------------+--------------------------------------
 It is not clear why this document mentions an issue with some PBX, where
 these PBX do not comply with any of the trunking mechanisms defined.

 This chapter should focus on technical issues of the existing defined
 mechanisms not on issues with arbitrary PBX not interworking with a
 specified mechanism just for the reason they have not implemented the
 mechanism.

 Suggest to remove this section.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/21>
martini <http://tools.ietf.org/martini/>


From D.Hancock@CableLabs.com  Tue Mar 23 18:03:27 2010
Return-Path: <D.Hancock@CableLabs.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 E47A53A6969 for <martini@core3.amsl.com>; Tue, 23 Mar 2010 18:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.468
X-Spam-Level: ****
X-Spam-Status: No, score=4.468 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, J_CHICKENPOX_45=0.6]
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 tURLa8nMUoY8 for <martini@core3.amsl.com>; Tue, 23 Mar 2010 18:03:13 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 565D93A6876 for <martini@ietf.org>; Tue, 23 Mar 2010 18:03:11 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o2O13UlL031546 for <martini@ietf.org>; Tue, 23 Mar 2010 19:03:30 -0600
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Tue, 23 Mar 2010 19:03:30 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Tue, 23 Mar 2010 19:03:30 -0600
From: David Hancock <D.Hancock@CableLabs.com>
To: "martini@ietf.org" <martini@ietf.org>
Date: Tue, 23 Mar 2010 19:03:28 -0600
Thread-Topic: Draft MARTINI Minutes from Monday's session at IETF#77
Thread-Index: AcrK7dBghdumtOiTTGK5bKElMd3+0w==
Message-ID: <76AC5FEF83F1E64491446437EA81A61F7CD4E30E79@srvxchg>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_76AC5FEF83F1E64491446437EA81A61F7CD4E30E79srvxchg_"
MIME-Version: 1.0
X-Approved: ondar
Subject: [martini] Draft MARTINI Minutes from Monday's session at IETF#77
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: Wed, 24 Mar 2010 01:03:28 -0000

--_000_76AC5FEF83F1E64491446437EA81A61F7CD4E30E79srvxchg_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Here are draft minutes from Monday's MARTINI meeting for your review.

Comments welcome.

Thanks
David

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Begin Draft MA=
RTINI Minutes=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D

1. Preliminaries (Bernard & Spencer)

Bernard Aboba: Encourage people to submit comments regarding GIN to the iss=
ue tracker.

Keith Drage:
-          Not only tracker entries are comments -- anything that appears o=
n the mailing list should also be considered a comment.
-          Group is moving too fast to allow sufficient review time, especi=
ally given 3GPP meeting conflicts.

Bernard Aboba: We're actually behind w.r.t. the schedule agreed in MARTINI.

Keith Drage: Due to meeting conflicts, etc, did not have an opportunity to =
contribute to the schedule.

Cullen Jennings: Words of praise for the current MARTINI process/progress.

2. Requirements (John Elwell & Hadriel Kaplan)

John Elwell's presentation on "Recent Issues" (slides 2 thru 5) ...

John Elwell: Issue # 16 - requirement for AOR extensibility is still open

Keith Drage: Believe there should be a requirement to support private numbe=
rs

John Elwell: Yes, issue-16 is being re-opened so solution can support exten=
sibility

Bernard Abobe: What does extensibility mean - does it mean a new version to=
 GIN?

Adam Roach: It means that GIN would not constrain the support of additional=
 AOR forms.

Hadriel Kaplan: The requirements doc should only state what is required, an=
d we've always said we're not required to support private numbers.

Jon Peterson: It would be useful to explain somewhere why support of privat=
e numbers wasn't included as a requirement.

John Elwell: The issue is that if we open it up to support AOR forms beyond=
 E.164 numbers, then we have to support domain routing. And domain routing =
has issues such as ambiguity of ownership, say when an enterprise user AOR =
has the domain of the SSP. These issues can be bypassed if we limit AORs to=
 E.164-only, since E.164 numbers are globally unique and therefore routing =
is unambiguous.

Jon Peterson: That information should be explicitly documented then.

Bernard Abobe: Where do we add that text? Req's doc or GIN draft?

Jon Peterson: It should be documented in the requirements doc. Add somethin=
g about domain routing concerns. (Agreed**)

Keith Drage: E.164 numbers can be carried either in a Tel URI or a SIP URI =
containing a Tel URI. In the case of SIP URI there is still a domain name, =
so how does that avoid the problem you raised?

Gonzalez: The requirements document needs to be explicit - when referring t=
o E.164 numbers are we talking about Tel or SIP URIs? (Agreed**)

John Elwell introduces new issue - should there be a requirement to support=
 Private numbers?

John Elwell: Even without an explicit requirement, it may just work.

Paul Kyzivat: What is the real requirement?  Is it to support service numbe=
rs like 911, 411, etc? They aren't E.164 numbers, and there isn't general a=
greement on how they're encoded as local numbers.

John Elwell: This requirement is about support of private numbers for PBX e=
xtensions. The SSP network must be able to route a call between PBXs servin=
g a single enterprise based on the private number of the called enterprise =
user (not the public E.164-based AOR).

Keith Drage: Agreed. In addition this requirement includes the case where a=
n enterprise has both PBX and Centrex users that want to call each other vi=
a abbreviated dialing.

Adam Roach: Can we assume that there is a mechanism to route inter-PBX call=
s directly, thus bypasses the SSP network? If we require the SSP to route t=
hese private calls then it breaks enterprise user mobility.

Keith Drage: Unfortunately, the bypass option doesn't work for the Centrex-=
to-PBX case.

Adam Roach: If we have to support this, then it'll destroy user mobility.

Hadriel Kaplan: We don't have to support Centrex. Rather, Centrex is an exa=
mple showing why the SSP has to support private number routing. Hadriel thi=
nks it will actually work, and doesn't see the problem Adam has with mobili=
ty. Also, Hadriel doesn't think this needs to be a requirement.

Spencer Dawkins (as WG chair) asks people to make comments on list.

Hadriel Kaplan's presentation on "Current Problems" (slides 6 thru 8) ...

Hadriel Kaplan: One of the problems with current mechanisms is there is no =
explicit indicator that this registration (from the SIP-PBX) is any differe=
nt than normal RC3261 registration.

Keith Drage: Instead of using an indicator, current solutions like the one =
defined for IMS use configured data in the SSP to indicate that the registe=
r is coming from a PBX. Even if we add an option tag, the SSP will still ne=
ed some configuration data to indicate this is a PBX registration, so it is=
n't clear how the addition of the option tag adds any value.

Request from Hadriel asking Keith to submit to list why SSP configuration d=
ata is still needed when an indicator is used.

Richard Shockey: The need for an option tag was the primary driver for brin=
ging this problem to MARTINI.

3. Solution Updates

Adam Roach - GIN draft presentation

Adam Roach: The risk in adding Proxy-Require option tag is that proxies in =
the signaling chain that don't need to do anything special with this extens=
ion but don't recognize the option-tag will reject request. The risk is mit=
igated in this case since a REGISTER request traverses a tightly constraine=
d set of proxies that are owned by and under the control of the serving SSP=
.

Dean Willis: Is the Proxy-Require option tag or the new contact parameter r=
equired by intermediaries?

Adam Roach: It's both -- the option tag says I'm using a new parameter in m=
y Contact header, and the 'bnc' parameter is that parameter. You could have=
 multiple contacts, only some of which had the 'bnc' parameter.

Adam Roach: One of the restrictions of using this mechanism is that the PBX=
 can't put anything in the user portion of the Contact URI. Therefore, the =
PBX will have to use Contact URI parameters to carry any data that it wants=
 returned in subsequent incoming requests.

Adam Roach: There is an open issue regarding use of the user=3Dphone parame=
ter in the REGISTER Contact header. The issue being -- is it valid for the =
PBX to include a "user=3Dphone" parameter on a contact URI that has no user=
 portion? Here are the resolution options...
1. Keep mechanism as-is (i.e., let PBX choose whether it needs "user=3Dphon=
e")
2. Forbid "user=3Dphone" on "bnc" URIs, and specify that the SSP must add "=
user=3Dphone"
3. Forbid "user=3Dphone" altogether

Henning Schulzrinne: The solution should be close to what is implemented. D=
o what is pragmatic and simple, and avoid creating new error conditions; i.=
e. a vote for option-1

Christer Holmberg: Are you allowed to have "user=3Dphone" without a user pa=
rt?

John Elwell: Didn't understand that it was OK for the PBX not to include us=
er=3Dphone. Which means there's a 4th option - which is to require inclusio=
n of user=3Dphone.

Hadriel Kaplan: There is talk of using new parameters instead of user=3Dpho=
ne, such as user=3Dfax. For example, the originator of a call wants to targ=
et the request to a FAX machine.

Adam Roach: One solution for this would be to register FAX URIs with a sepa=
rate REGISTER request.

Paul Kyzivat: Has anyone actually proposed defining a user=3Dfax parameter?=
 If not, we could consider it out-of-scope.

Hadriel Kaplan: Want to avoid having to open GIN up every time someone adds=
 a new parameter, so we need to think about this

Bernard Abobe: Any other contact URI parameters added by the PBX need to be=
 echoed back in subsequent requests.

Jon Peterson: In this case the 'bnc' parameter is the most significant para=
meter carried in the Contact URI, and its presence should remove any confus=
ion over the use and meaning of "user=3Dphone" in the Contact URI (i.e., su=
pport for option-1).

HUM - does group favor option-1? HUM results: in favor of option of #1.

Keith Drage: Object to taking a HUM on something that isn't adopted as a WG=
 item.

Cullen - Believes the HUM is OK in this case - take the temperature of the =
room on a specific technical point to provide input to draft author.

Keith Drage: Some service providers have voiced their opposition to the GIN=
 solution on the list.

Richard: Agreed, although there has also been support for GIN from cable op=
erators.

Adam Roach introduces new open issue - Is there a need to signal list of en=
terprise phone numbers between PBX and SSP network?

David Schwartz: Would it be possible to propose a mechanism without mandati=
ng it?

Spencer Dawkins (as WG chair): Haven't seen people saying that we have to h=
ave this. Anyone who feels strongly that this is needed should write their =
own draft. It's not worth trying to solve this as part of GIN because of th=
e "size of response" issue.

Hadriel Kaplan: People that need this information have other ways to get it=
.

Keith Drage: Need to understand the root requirement, since that may dictat=
e what solution applies. For example, if the requirement is to provide a wa=
y for the SSP network to tell the PBX that an enterprise user is no longer =
registered, then an extension to the reg-event package may be a better solu=
tion.

Jon Peterson: It may be odious (onerous?) to support this, but we should do=
 it. If we decide to not to, then we need to put a warning in GIN that it i=
sn't supported.

Adam Roach: To be semantically consistent with the way REGISTER works today=
, the list would be  communicated as part of REGISTER transaction. Any solu=
tion we come up with can probably be retrofitted on top of the GIN solution=
.

John Elwell: Supports documenting the solution is a separate draft using a =
mechanism outside of registration (e.g., reg-event package). If we do use R=
EGISTER, then put the list in the REGISTER request.

Hadriel Kaplan: With the GIN solution you're registering a template, not th=
e actual AORs.

Martin Thompson: Could we use indirection to solve response-size problem?

Christer Holmberg: Once PBX is registered can I add/remove AORs from the li=
st?

Adam Roach: There is a hole in the current GIN text related to this. Will r=
esolve in the next version

Dale Worley: Agree with Hadriel that GIN is registering a template. Therefo=
re, if the SSP assigns a new number to an already-registered PBX, then it i=
s immediately available for use, you don't have to wait for the next REGIST=
ER.

Adam Roach:  New topic - Outbound, Service Route & Path need to be looked a=
t w.r.t. GIN.

Adam Roach: The intermediaries originally could assume that REGISTER was fo=
r the single AOR in To header. Are here any impacts or security concerns du=
e to fact hat now we're registering multiple AORs?

Bernard Abobe: How much of these pending issues can we resolve by Friday? C=
ould we spin anther version of the draft this week for review at the Friday=
 meeting? Also, can we get volunteers to review potential impacts to Outbou=
nd, Service Route, and Path?

Someone (Cullen?) volunteered Francois Audet for Outbound. Cullen agreed to=
 contact Francois on this, and will work offline to get volunteers for Serv=
ice Route and Path.

Hadriel Kaplan: Request that MARTINI mandate support of Path.

Adam Roach: If SIP-PBX wants to put an FQDN in the domain of the Contact UR=
I, then it needs to support Path to convey PBX IP address.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D End Draft MARTINI Minutes =3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D




--_000_76AC5FEF83F1E64491446437EA81A61F7CD4E30E79srvxchg_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"Street"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.Comment-blue, li.Comment-blue, div.Comment-blue
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Times New Roman";
	font-weight:bold;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1840655064;
	mso-list-type:hybrid;
	mso-list-template-ids:1059606824 233206474 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:16;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:21.0pt;
	mso-level-number-position:left;
	margin-left:21.0pt;
	text-indent:-.25in;
	font-family:Arial;
	mso-fareast-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Here are draft minutes from Monday&#8217;s MARTINI meeti=
ng
for your review. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Comments welcome.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Thanks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>David<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D Begin Draft MARTINI Minutes=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span style=3D'font-siz=
e:10.0pt;
font-family:Arial;font-weight:bold'><o:p>&nbsp;</o:p></span></font></b></p>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span style=3D'font-siz=
e:10.0pt;
font-family:Arial;font-weight:bold'>1. Preliminaries (Bernard &amp; Spencer=
)<o:p></o:p></span></font></b></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Bernard Aboba: Encourage people to submit comments regar=
ding
GIN to the issue tracker.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Keith Drage:<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:21.0pt;text-indent:-.25in;mso-lis=
t:l0 level1 lfo1'><![if !supportLists]><font
size=3D2 face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'><s=
pan
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 face=3DArial><s=
pan
style=3D'font-size:10.0pt;font-family:Arial'>Not only tracker entries are
comments -- anything that appears on the mailing list should also be consid=
ered
a comment.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:21.0pt;text-indent:-.25in;mso-lis=
t:l0 level1 lfo1'><![if !supportLists]><font
size=3D2 face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'><s=
pan
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 face=3DArial><s=
pan
style=3D'font-size:10.0pt;font-family:Arial'>Group is moving too fast to al=
low
sufficient review time, especially given 3GPP meeting conflicts.<o:p></o:p>=
</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Bernard Aboba: We&#8217;re actually behind w.r.t. the
schedule agreed in MARTINI. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Keith Drage: Due to meeting conflicts, etc, did not have=
 an
opportunity to contribute to the schedule.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Cullen <st1:City w:st=3D"on"><st1:place w:st=3D"on">Jenn=
ings</st1:place></st1:City>:
Words of praise for the current MARTINI process/progress.<o:p></o:p></span>=
</font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span style=3D'font-siz=
e:10.0pt;
font-family:Arial;font-weight:bold'>2. Requirements (John Elwell &amp; Hadr=
iel
Kaplan)<o:p></o:p></span></font></b></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span style=3D'font-siz=
e:10.0pt;
font-family:Arial;font-weight:bold'>John Elwell&#8217;s presentation on &#8=
220;Recent
Issues&#8221; (slides 2 thru 5) &#8230;<o:p></o:p></span></font></b></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>John Elwell: Issue # 16 &#8211=
;
requirement for AOR extensibility is still open<o:p></o:p></span></font></p=
>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Keith Drage: Believe there sho=
uld be
a requirement to support private numbers<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>John Elwell: Yes, issue-16 is =
being
re-opened so solution can support extensibility<o:p></o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Bernard Abobe: What does
extensibility mean &#8211; does it mean a new version to GIN?<o:p></o:p></s=
pan></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Adam Roach: It means that GIN =
would
not constrain the support of additional AOR forms.<o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Hadriel Kaplan: The requiremen=
ts doc
should only state what is required, and we&#8217;ve always said we&#8217;re=
 not
required to support private numbers.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Jon Peterson: It would be usef=
ul to
explain somewhere why support of private numbers wasn&#8217;t included as a
requirement. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>John Elwell: The issue is that=
 if we
open it up to support AOR forms beyond E.164 numbers, then we have to suppo=
rt
domain routing. And domain routing has issues such as ambiguity of ownershi=
p,
say when an enterprise user AOR has the domain of the SSP. These issues can=
 be
bypassed if we limit AORs to E.164-only, since E.164 numbers are globally
unique and therefore routing is unambiguous. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Jon Peterson: That information
should be explicitly documented then. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Bernard Abobe: Where do we add=
 that
text? Req&#8217;s doc or GIN draft? <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Jon Peterson: It should be doc=
umented
in the requirements doc. Add something about domain routing concerns. (Agre=
ed**)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Keith Drage: E.164 numbers can=
 be carried
either in a Tel URI or a SIP URI containing a Tel URI. In the case of SIP U=
RI
there is still a domain name, so how does that avoid the problem you raised=
?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Gonzalez: The requirements doc=
ument
needs to be explicit &#8211; when referring to E.164 numbers are we talking
about Tel or SIP URIs? (Agreed**)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><b><font size=3D2 face=3DA=
rial><span
style=3D'font-size:10.0pt;font-family:Arial;font-weight:bold'>John Elwell
introduces new issue &#8211; should there be a requirement to support Priva=
te
numbers? <o:p></o:p></span></font></b></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>John Elwell: Even without an
explicit requirement, it may just work. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Paul Kyzivat: What is the real
requirement? &nbsp;Is it to support service numbers like 911, 411, etc? The=
y
aren&#8217;t E.164 numbers, and there isn&#8217;t general agreement on how
they&#8217;re encoded as local numbers. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>John Elwell: This requirement =
is
about support of private numbers for PBX extensions. The SSP network must b=
e
able to route a call between PBXs serving a single enterprise based on the
private number of the called enterprise user (not the public E.164-based AO=
R). <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Keith Drage: Agreed. In additi=
on this
requirement includes the case where an enterprise has both PBX and Centrex =
users
that want to call each other via abbreviated dialing. &nbsp;<o:p></o:p></sp=
an></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Adam Roach: Can we assume that=
 there
is a mechanism to route inter-PBX calls directly, thus bypasses the SSP net=
work?
If we require the SSP to route these private calls then it breaks enterpris=
e
user mobility. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Keith Drage: Unfortunately, th=
e
bypass option doesn&#8217;t work for the Centrex-to-PBX case. &nbsp;<o:p></=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Adam Roach: If we have to supp=
ort
this, then it&#8217;ll destroy user mobility.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Hadriel Kaplan: We don&#8217;t=
 have
to support Centrex. Rather, Centrex is an example showing why the SSP has t=
o
support private number routing. Hadriel thinks it will actually work, and
doesn&#8217;t see the problem Adam has with mobility. Also, Hadriel doesn&#=
8217;t
think this needs to be a requirement. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Spencer Dawkins (as WG chair) =
asks
people to make comments on list.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span style=3D'font-siz=
e:10.0pt;
font-family:Arial;font-weight:bold'>Hadriel Kaplan&#8217;s presentation on =
&#8220;Current
Problems&#8221; (slides 6 thru 8) &#8230;<o:p></o:p></span></font></b></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Hadriel Kaplan: One of the pro=
blems
with current mechanisms is there is no explicit indicator that this registr=
ation
(from the SIP-PBX) is any different than normal RC3261 registration.<o:p></=
o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Keith Drage: Instead of using =
an
indicator, current solutions like the one defined for IMS use configured da=
ta
in the SSP to indicate that the register is coming from a PBX. Even if we a=
dd
an option tag, the SSP will still need some configuration data to indicate =
this
is a PBX registration, so it isn&#8217;t clear how the addition of the opti=
on
tag adds any value. <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Request from Hadriel asking Ke=
ith to
submit to list why SSP configuration data is still needed when an indicator=
 is
used. <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Richard Shockey: The need for =
an
option tag was the primary driver for bringing this problem to MARTINI. <o:=
p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span style=3D'font-siz=
e:10.0pt;
font-family:Arial;font-weight:bold'>3. Solution Updates<o:p></o:p></span></=
font></b></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span style=3D'font-siz=
e:10.0pt;
font-family:Arial;font-weight:bold'>Adam Roach &#8211; GIN draft presentati=
on<o:p></o:p></span></font></b></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Adam Roach: The risk in adding=
 Proxy-Require
option tag is that proxies in the signaling chain that don&#8217;t need to =
do
anything special with this extension but don&#8217;t recognize the option-t=
ag
will reject request. The risk is mitigated in this case since a REGISTER
request traverses a tightly constrained set of proxies that are owned by an=
d
under the control of the serving SSP. <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Dean Willis: Is the Proxy-Requ=
ire option
tag or the new contact parameter required by intermediaries?<o:p></o:p></sp=
an></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Adam Roach: It&#8217;s both --=
 the
option tag says I&#8217;m using a new parameter in my Contact header, and t=
he &#8216;bnc&#8217;
parameter is that parameter. You could have multiple contacts, only some of
which had the &#8216;bnc&#8217; parameter.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'>Adam Roach: One of the restric=
tions
of using this mechanism is that the PBX can&#8217;t put anything in the use=
r
portion of the Contact URI. Therefore, the PBX will have to use Contact URI
parameters to carry any data that it wants returned in subsequent incoming
requests. <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:3.0pt'><font size=3D2 face=3DAria=
l><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Adam Roach: There is an open issue regarding use of the =
user=3Dphone
parameter in the REGISTER Contact header. The issue being -- is it valid fo=
r
the PBX to include a &#8220;user=3Dphone&#8221; parameter on a contact URI =
that
has no user portion? Here are the resolution options&#8230;<o:p></o:p></spa=
n></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>1. Keep mechanism as-is (i.e., let PBX choose whether it
needs &#8220;user=3Dphone&#8221;)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>2. Forbid &#8220;user=3Dphone&#8221; on &#8220;bnc&#8221=
;
URIs, and specify that the SSP must add &#8220;user=3Dphone&#8221;<o:p></o:=
p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>3. Forbid &#8220;user=3Dphone&#8221; altogether &nbsp;<o=
:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Henning Schulzrinne: The solution should be close to wha=
t is
implemented. Do what is pragmatic and simple, and avoid creating new error
conditions; i.e. a vote for option-1<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Christer Holmberg: Are you allowed to have
&#8220;user=3Dphone&#8221; without a user part?<o:p></o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>John Elwell: Didn&#8217;t understand that it was OK for =
the
PBX not to include user=3Dphone. Which means there&#8217;s a 4<sup>th</sup>
option &#8211; which is to require inclusion of user=3Dphone. <o:p></o:p></=
span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Hadriel Kaplan: There is talk of using new parameters
instead of user=3Dphone, such as user=3Dfax. For example, the originator of=
 a call wants
to target the request to a FAX machine.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Adam Roach: One solution for this would be to register F=
AX
URIs with a separate REGISTER request. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Paul Kyzivat: Has anyone actually proposed defining a us=
er=3Dfax
parameter? If not, we could consider it out-of-scope.<o:p></o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Hadriel Kaplan: Want to avoid having to open GIN up ever=
y
time someone adds a new parameter, so we need to think about this<o:p></o:p=
></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Bernard Abobe: Any other contact URI parameters added by=
 the
PBX need to be echoed back in subsequent requests.<o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Jon Peterson: In this case the &#8216;bnc&#8217; paramet=
er
is the most significant parameter carried in the Contact URI, and its prese=
nce should
remove any confusion over the use and meaning of &#8220;user=3Dphone&#8221;=
 in
the Contact URI (i.e., support for option-1).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>HUM &#8211; does group favor option-1? HUM results: in f=
avor
of option of #1.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Keith Drage: Object to taking a HUM on something that
isn&#8217;t adopted as a WG item.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Cullen &#8211; Believes the HUM is OK in this case &#821=
1; take
the temperature of the room on a specific technical point to provide input =
to draft
author.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Keith Drage: Some service providers have voiced their
opposition to the GIN solution on the list.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Richard: Agreed, although there has also been support fo=
r
GIN from cable operators.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span style=3D'font-siz=
e:10.0pt;
font-family:Arial;font-weight:bold'>Adam Roach introduces new open issue &#=
8211;
Is there a need to signal list of enterprise phone numbers between PBX and =
SSP
network?<o:p></o:p></span></font></b></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>David Schwartz: Would it be possible to propose a mechan=
ism
without mandating it? <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Spencer Dawkins (as WG chair): Haven&#8217;t seen people
saying that we have to have this. Anyone who feels strongly that this is ne=
eded
should write their own draft. It&#8217;s not worth trying to solve this as =
part
of GIN because of the &#8220;size of response&#8221; issue. &nbsp;<o:p></o:=
p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Hadriel Kaplan: People that need this information have o=
ther
ways to get it. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Keith Drage: Need to understand the root requirement, si=
nce
that may dictate what solution applies. For example, if the requirement is =
to provide
a way for the SSP network to tell the PBX that an enterprise user is no lon=
ger
registered, then an extension to the reg-event package may be a better solu=
tion.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Jon Peterson: It may be odious (onerous?) to support thi=
s,
but we should do it. If we decide to not to, then we need to put a warning =
in
GIN that it isn&#8217;t supported. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Adam Roach: To be semantically consistent with the way
REGISTER works today, the list would be &nbsp;communicated as part of REGIS=
TER
transaction. Any solution we come up with can probably be retrofitted on to=
p of
the GIN solution.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>John Elwell: Supports documenting the solution is a sepa=
rate
draft using a mechanism outside of registration (e.g., reg-event package). =
If we
do use REGISTER, then put the list in the REGISTER request. <o:p></o:p></sp=
an></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Hadriel Kaplan: With the GIN solution you&#8217;re
registering a template, not the actual AORs. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Martin Thompson: Could we use indirection to solve respo=
nse-size
problem?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Christer Holmberg: Once PBX is registered can I add/remo=
ve
AORs from the list?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Adam Roach: There is a hole in the current GIN text rela=
ted
to this. Will resolve in the next version<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Dale Worley: Agree with Hadriel that GIN is registering =
a
template. Therefore, if the SSP assigns a new number to an already-register=
ed
PBX, then it is immediately available for use, you don&#8217;t have to wait=
 for
the next REGISTER.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span style=3D'font-siz=
e:10.0pt;
font-family:Arial;font-weight:bold'>Adam Roach:&nbsp; New topic &#8211; Out=
bound,
<st1:Street w:st=3D"on"><st1:address w:st=3D"on">Service Route</st1:address=
></st1:Street>
&amp; Path need to be looked at w.r.t. GIN.</span></font></b><font size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'> <o:p></o:p=
></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Adam Roach: The intermediaries originally could assume t=
hat REGISTER
was for the single AOR in To header. Are here any impacts or security conce=
rns
due to fact hat now we&#8217;re registering multiple AORs?<o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Bernard Abobe: How much of these pending issues can we r=
esolve
by Friday? Could we spin anther version of the draft this week for review a=
t
the Friday meeting? Also, can we get volunteers to review potential impacts=
 to
Outbound, <st1:Street w:st=3D"on"><st1:address w:st=3D"on">Service Route</s=
t1:address></st1:Street>,
and Path?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Someone (Cullen?) volunteered Francois Audet for Outboun=
d. Cullen
agreed to contact Francois on this, and will work offline to get volunteers=
 for
<st1:Street w:st=3D"on"><st1:address w:st=3D"on">Service Route</st1:address=
></st1:Street>
and Path. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Hadriel Kaplan: Request that MARTINI mandate support of
Path. &nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Adam Roach: If SIP-PBX wants to put an FQDN in the domai=
n of
the Contact URI, then it needs to support Path to convey PBX IP address.<o:=
p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D End Draft MARTINI Minutes
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--_000_76AC5FEF83F1E64491446437EA81A61F7CD4E30E79srvxchg_--

From john.elwell@siemens-enterprise.com  Wed Mar 24 08:02:49 2010
Return-Path: <john.elwell@siemens-enterprise.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 E32D23A681E for <martini@core3.amsl.com>; Wed, 24 Mar 2010 08:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.498
X-Spam-Level: *
X-Spam-Status: No, score=1.498 tagged_above=-999 required=5 tests=[AWL=-0.833,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_43=0.6, J_CHICKENPOX_45=0.6]
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 PWqjTiQXmctr for <martini@core3.amsl.com>; Wed, 24 Mar 2010 08:02:48 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id D775A3A6778 for <martini@ietf.org>; Wed, 24 Mar 2010 08:02:47 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1329162; Wed, 24 Mar 2010 16:03:07 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 8D3531EB82BF; Wed, 24 Mar 2010 16:03:07 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Wed, 24 Mar 2010 16:03:07 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: David Hancock <D.Hancock@CableLabs.com>, "martini@ietf.org" <martini@ietf.org>
Date: Wed, 24 Mar 2010 16:03:05 +0100
Thread-Topic: Draft MARTINI Minutes from Monday's session at IETF#77
Thread-Index: AcrK7dBghdumtOiTTGK5bKElMd3+0wAdLk1w
Message-ID: <A444A0F8084434499206E78C106220CADE09A3E9@MCHP058A.global-ad.net>
References: <76AC5FEF83F1E64491446437EA81A61F7CD4E30E79@srvxchg>
In-Reply-To: <76AC5FEF83F1E64491446437EA81A61F7CD4E30E79@srvxchg>
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
Subject: Re: [martini] Draft MARTINI Minutes from Monday's session at IETF#77
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: Wed, 24 Mar 2010 15:02:50 -0000

"John Elwell: This requirement is about support of private numbers for PBX =
extensions. The SSP network must be able to route a call between PBXs servi=
ng a single enterprise based on the private number of the called enterprise=
 user (not the public E.164-based AOR)."

Just to remove any ambiguity, please rephrase the second sentence as follow=
s:
"Adopting this requirement would mean that the SSP network must be able to =
route a call between PBXs serving a single enterprise based on the private =
number of the called enterprise user (not the public E.164-based AOR)."

John


> -----Original Message-----
> From: martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] On Behalf Of David Hancock
> Sent: 23 March 2010 18:03
> To: martini@ietf.org
> Subject: [martini] Draft MARTINI Minutes from Monday's=20
> session at IETF#77
>=20
> Here are draft minutes from Monday's MARTINI meeting for your review.=20
>=20
> =20
>=20
> Comments welcome.
>=20
> =20
>=20
> Thanks
>=20
> David
>=20
> =20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Begin Draft =
MARTINI=20
> Minutes=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
>=20
> =20
>=20
> 1. Preliminaries (Bernard & Spencer)
>=20
> =20
>=20
> Bernard Aboba: Encourage people to submit comments regarding=20
> GIN to the issue tracker.
>=20
> =20
>=20
> Keith Drage:
>=20
> -          Not only tracker entries are comments -- anything=20
> that appears on the mailing list should also be considered a comment.
>=20
> -          Group is moving too fast to allow sufficient=20
> review time, especially given 3GPP meeting conflicts.
>=20
> =20
>=20
> Bernard Aboba: We're actually behind w.r.t. the schedule=20
> agreed in MARTINI.=20
>=20
> =20
>=20
> Keith Drage: Due to meeting conflicts, etc, did not have an=20
> opportunity to contribute to the schedule.
>=20
> =20
>=20
> Cullen Jennings: Words of praise for the current MARTINI=20
> process/progress.
>=20
> =20
>=20
> 2. Requirements (John Elwell & Hadriel Kaplan)
>=20
> =20
>=20
> John Elwell's presentation on "Recent Issues" (slides 2 thru 5) ...
>=20
> =20
>=20
> John Elwell: Issue # 16 - requirement for AOR extensibility=20
> is still open
>=20
> =20
>=20
> Keith Drage: Believe there should be a requirement to support=20
> private numbers
>=20
> =20
>=20
> John Elwell: Yes, issue-16 is being re-opened so solution can=20
> support extensibility
>=20
> =20
>=20
> Bernard Abobe: What does extensibility mean - does it mean a=20
> new version to GIN?
>=20
> =20
>=20
> Adam Roach: It means that GIN would not constrain the support=20
> of additional AOR forms.
>=20
> =20
>=20
> Hadriel Kaplan: The requirements doc should only state what=20
> is required, and we've always said we're not required to=20
> support private numbers.
>=20
> =20
>=20
> Jon Peterson: It would be useful to explain somewhere why=20
> support of private numbers wasn't included as a requirement.=20
>=20
> =20
>=20
> John Elwell: The issue is that if we open it up to support=20
> AOR forms beyond E.164 numbers, then we have to support=20
> domain routing. And domain routing has issues such as=20
> ambiguity of ownership, say when an enterprise user AOR has=20
> the domain of the SSP. These issues can be bypassed if we=20
> limit AORs to E.164-only, since E.164 numbers are globally=20
> unique and therefore routing is unambiguous.=20
>=20
> =20
>=20
> Jon Peterson: That information should be explicitly documented then.=20
>=20
> =20
>=20
> Bernard Abobe: Where do we add that text? Req's doc or GIN draft?=20
>=20
> =20
>=20
> Jon Peterson: It should be documented in the requirements=20
> doc. Add something about domain routing concerns. (Agreed**)
>=20
> =20
>=20
> Keith Drage: E.164 numbers can be carried either in a Tel URI=20
> or a SIP URI containing a Tel URI. In the case of SIP URI=20
> there is still a domain name, so how does that avoid the=20
> problem you raised?
>=20
> =20
>=20
> Gonzalez: The requirements document needs to be explicit -=20
> when referring to E.164 numbers are we talking about Tel or=20
> SIP URIs? (Agreed**)
>=20
> =20
>=20
> John Elwell introduces new issue - should there be a=20
> requirement to support Private numbers?=20
>=20
> =20
>=20
> John Elwell: Even without an explicit requirement, it may just work.=20
>=20
> =20
>=20
> Paul Kyzivat: What is the real requirement?  Is it to support=20
> service numbers like 911, 411, etc? They aren't E.164=20
> numbers, and there isn't general agreement on how they're=20
> encoded as local numbers.=20
>=20
> =20
>=20
> John Elwell: This requirement is about support of private=20
> numbers for PBX extensions. The SSP network must be able to=20
> route a call between PBXs serving a single enterprise based=20
> on the private number of the called enterprise user (not the=20
> public E.164-based AOR).=20
>=20
> =20
>=20
> Keith Drage: Agreed. In addition this requirement includes=20
> the case where an enterprise has both PBX and Centrex users=20
> that want to call each other via abbreviated dialing. =20
>=20
> =20
>=20
> Adam Roach: Can we assume that there is a mechanism to route=20
> inter-PBX calls directly, thus bypasses the SSP network? If=20
> we require the SSP to route these private calls then it=20
> breaks enterprise user mobility.=20
>=20
> =20
>=20
> Keith Drage: Unfortunately, the bypass option doesn't work=20
> for the Centrex-to-PBX case. =20
>=20
> =20
>=20
> Adam Roach: If we have to support this, then it'll destroy=20
> user mobility.
>=20
> =20
>=20
> Hadriel Kaplan: We don't have to support Centrex. Rather,=20
> Centrex is an example showing why the SSP has to support=20
> private number routing. Hadriel thinks it will actually work,=20
> and doesn't see the problem Adam has with mobility. Also,=20
> Hadriel doesn't think this needs to be a requirement.=20
>=20
> =20
>=20
> Spencer Dawkins (as WG chair) asks people to make comments on list.
>=20
> =20
>=20
> Hadriel Kaplan's presentation on "Current Problems" (slides 6=20
> thru 8) ...
>=20
> =20
>=20
> Hadriel Kaplan: One of the problems with current mechanisms=20
> is there is no explicit indicator that this registration=20
> (from the SIP-PBX) is any different than normal RC3261 registration.
>=20
> =20
>=20
> Keith Drage: Instead of using an indicator, current solutions=20
> like the one defined for IMS use configured data in the SSP=20
> to indicate that the register is coming from a PBX. Even if=20
> we add an option tag, the SSP will still need some=20
> configuration data to indicate this is a PBX registration, so=20
> it isn't clear how the addition of the option tag adds any value.=20
>=20
> =20
>=20
> Request from Hadriel asking Keith to submit to list why SSP=20
> configuration data is still needed when an indicator is used.=20
>=20
> =20
>=20
> Richard Shockey: The need for an option tag was the primary=20
> driver for bringing this problem to MARTINI.=20
>=20
> =20
>=20
> 3. Solution Updates
>=20
> =20
>=20
> Adam Roach - GIN draft presentation
>=20
> =20
>=20
> Adam Roach: The risk in adding Proxy-Require option tag is=20
> that proxies in the signaling chain that don't need to do=20
> anything special with this extension but don't recognize the=20
> option-tag will reject request. The risk is mitigated in this=20
> case since a REGISTER request traverses a tightly constrained=20
> set of proxies that are owned by and under the control of the=20
> serving SSP.=20
>=20
> =20
>=20
> Dean Willis: Is the Proxy-Require option tag or the new=20
> contact parameter required by intermediaries?
>=20
> =20
>=20
> Adam Roach: It's both -- the option tag says I'm using a new=20
> parameter in my Contact header, and the 'bnc' parameter is=20
> that parameter. You could have multiple contacts, only some=20
> of which had the 'bnc' parameter.
>=20
> =20
>=20
> Adam Roach: One of the restrictions of using this mechanism=20
> is that the PBX can't put anything in the user portion of the=20
> Contact URI. Therefore, the PBX will have to use Contact URI=20
> parameters to carry any data that it wants returned in=20
> subsequent incoming requests.=20
>=20
> =20
>=20
> Adam Roach: There is an open issue regarding use of the=20
> user=3Dphone parameter in the REGISTER Contact header. The=20
> issue being -- is it valid for the PBX to include a=20
> "user=3Dphone" parameter on a contact URI that has no user=20
> portion? Here are the resolution options...
>=20
> 1. Keep mechanism as-is (i.e., let PBX choose whether it=20
> needs "user=3Dphone")
>=20
> 2. Forbid "user=3Dphone" on "bnc" URIs, and specify that the=20
> SSP must add "user=3Dphone"
>=20
> 3. Forbid "user=3Dphone" altogether =20
>=20
> =20
>=20
> Henning Schulzrinne: The solution should be close to what is=20
> implemented. Do what is pragmatic and simple, and avoid=20
> creating new error conditions; i.e. a vote for option-1
>=20
> =20
>=20
> Christer Holmberg: Are you allowed to have "user=3Dphone"=20
> without a user part?
>=20
> =20
>=20
> John Elwell: Didn't understand that it was OK for the PBX not=20
> to include user=3Dphone. Which means there's a 4th option -=20
> which is to require inclusion of user=3Dphone.=20
>=20
> =20
>=20
> Hadriel Kaplan: There is talk of using new parameters instead=20
> of user=3Dphone, such as user=3Dfax. For example, the originator=20
> of a call wants to target the request to a FAX machine.
>=20
> =20
>=20
> Adam Roach: One solution for this would be to register FAX=20
> URIs with a separate REGISTER request.=20
>=20
> =20
>=20
> Paul Kyzivat: Has anyone actually proposed defining a=20
> user=3Dfax parameter? If not, we could consider it out-of-scope.
>=20
> =20
>=20
> Hadriel Kaplan: Want to avoid having to open GIN up every=20
> time someone adds a new parameter, so we need to think about this
>=20
> =20
>=20
> Bernard Abobe: Any other contact URI parameters added by the=20
> PBX need to be echoed back in subsequent requests.
>=20
> =20
>=20
> Jon Peterson: In this case the 'bnc' parameter is the most=20
> significant parameter carried in the Contact URI, and its=20
> presence should remove any confusion over the use and meaning=20
> of "user=3Dphone" in the Contact URI (i.e., support for option-1).
>=20
> =20
>=20
> HUM - does group favor option-1? HUM results: in favor of=20
> option of #1.
>=20
> =20
>=20
> Keith Drage: Object to taking a HUM on something that isn't=20
> adopted as a WG item.
>=20
> =20
>=20
> Cullen - Believes the HUM is OK in this case - take the=20
> temperature of the room on a specific technical point to=20
> provide input to draft author.
>=20
> =20
>=20
> Keith Drage: Some service providers have voiced their=20
> opposition to the GIN solution on the list.
>=20
> =20
>=20
> Richard: Agreed, although there has also been support for GIN=20
> from cable operators.
>=20
> =20
>=20
> Adam Roach introduces new open issue - Is there a need to=20
> signal list of enterprise phone numbers between PBX and SSP network?
>=20
> =20
>=20
> David Schwartz: Would it be possible to propose a mechanism=20
> without mandating it?=20
>=20
> =20
>=20
> Spencer Dawkins (as WG chair): Haven't seen people saying=20
> that we have to have this. Anyone who feels strongly that=20
> this is needed should write their own draft. It's not worth=20
> trying to solve this as part of GIN because of the "size of=20
> response" issue. =20
>=20
> =20
>=20
> Hadriel Kaplan: People that need this information have other=20
> ways to get it.=20
>=20
> =20
>=20
> Keith Drage: Need to understand the root requirement, since=20
> that may dictate what solution applies. For example, if the=20
> requirement is to provide a way for the SSP network to tell=20
> the PBX that an enterprise user is no longer registered, then=20
> an extension to the reg-event package may be a better solution.
>=20
> =20
>=20
> Jon Peterson: It may be odious (onerous?) to support this,=20
> but we should do it. If we decide to not to, then we need to=20
> put a warning in GIN that it isn't supported.=20
>=20
> =20
>=20
> Adam Roach: To be semantically consistent with the way=20
> REGISTER works today, the list would be  communicated as part=20
> of REGISTER transaction. Any solution we come up with can=20
> probably be retrofitted on top of the GIN solution.
>=20
> =20
>=20
> John Elwell: Supports documenting the solution is a separate=20
> draft using a mechanism outside of registration (e.g.,=20
> reg-event package). If we do use REGISTER, then put the list=20
> in the REGISTER request.=20
>=20
> =20
>=20
> Hadriel Kaplan: With the GIN solution you're registering a=20
> template, not the actual AORs.=20
>=20
> =20
>=20
> Martin Thompson: Could we use indirection to solve=20
> response-size problem?
>=20
> =20
>=20
> Christer Holmberg: Once PBX is registered can I add/remove=20
> AORs from the list?
>=20
> =20
>=20
> Adam Roach: There is a hole in the current GIN text related=20
> to this. Will resolve in the next version
>=20
> =20
>=20
> Dale Worley: Agree with Hadriel that GIN is registering a=20
> template. Therefore, if the SSP assigns a new number to an=20
> already-registered PBX, then it is immediately available for=20
> use, you don't have to wait for the next REGISTER.
>=20
> =20
>=20
> Adam Roach:  New topic - Outbound, Service Route & Path need=20
> to be looked at w.r.t. GIN.=20
>=20
> =20
>=20
> Adam Roach: The intermediaries originally could assume that=20
> REGISTER was for the single AOR in To header. Are here any=20
> impacts or security concerns due to fact hat now we're=20
> registering multiple AORs?
>=20
> =20
>=20
> Bernard Abobe: How much of these pending issues can we=20
> resolve by Friday? Could we spin anther version of the draft=20
> this week for review at the Friday meeting? Also, can we get=20
> volunteers to review potential impacts to Outbound, Service=20
> Route, and Path?
>=20
> =20
>=20
> Someone (Cullen?) volunteered Francois Audet for Outbound.=20
> Cullen agreed to contact Francois on this, and will work=20
> offline to get volunteers for Service Route and Path.=20
>=20
> =20
>=20
> Hadriel Kaplan: Request that MARTINI mandate support of Path. =20
>=20
> =20
>=20
> Adam Roach: If SIP-PBX wants to put an FQDN in the domain of=20
> the Contact URI, then it needs to support Path to convey PBX=20
> IP address.
>=20
> =20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D End Draft MARTINI Minutes=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=20
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> =

From adam@nostrum.com  Wed Mar 24 15:30:45 2010
Return-Path: <adam@nostrum.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 90A993A6B75 for <martini@core3.amsl.com>; Wed, 24 Mar 2010 15:30:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.155
X-Spam-Level: 
X-Spam-Status: No, score=0.155 tagged_above=-999 required=5 tests=[AWL=1.625,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, SPF_PASS=-0.001]
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 HdUK6+2lMBVG for <martini@core3.amsl.com>; Wed, 24 Mar 2010 15:30:45 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 73F1A3A68C8 for <martini@ietf.org>; Wed, 24 Mar 2010 15:30:43 -0700 (PDT)
Received: from dhcp-wireless-open-abg-24-56.meeting.ietf.org (dhcp-wireless-open-abg-24-56.meeting.ietf.org [130.129.24.56] (may be forged)) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o2OMV24Y083718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <martini@ietf.org>; Wed, 24 Mar 2010 17:31:03 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4BAA929F.7070004@nostrum.com>
Date: Wed, 24 Mar 2010 15:30:55 -0700
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: "martini@ietf.org" <martini@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 130.129.24.56 is authenticated by a trusted mechanism)
Subject: [martini] New version of GIN
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: Wed, 24 Mar 2010 22:30:45 -0000

I have posted a new version of the GIN draft that addresses many of the 
open trac issues. In particular, this version performs an analysis 
against the requirements document (John Elwell will lead a discussion 
around this analysis on Friday). I've also addressed a number of 
editorial issues and completed the IANA considerations section.

New draft available here:

http://www.ietf.org/id/draft-roach-martini-gin-02.txt

Diffs available here:

http://tools.ietf.org/rfcdiff?url2=draft-roach-martini-gin-02.txt

/a

From trac@tools.ietf.org  Wed Mar 24 17:25:18 2010
Return-Path: <trac@tools.ietf.org>
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 D463A3A6B34 for <martini@core3.amsl.com>; Wed, 24 Mar 2010 17:25:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.609
X-Spam-Level: 
X-Spam-Status: No, score=-100.609 tagged_above=-999 required=5 tests=[AWL=0.861, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 dVio4W37Snrf for <martini@core3.amsl.com>; Wed, 24 Mar 2010 17:25:17 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 8A2C63A6AF3 for <martini@ietf.org>; Wed, 24 Mar 2010 17:25:16 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NuatF-0000JC-P3; Wed, 24 Mar 2010 17:25:37 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: ietf.hanserik@gmail.com
X-Trac-Project: martini
Date: Thu, 25 Mar 2010 00:25:37 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/22
Message-ID: <065.2f0c12b2e457bc22e0ddda7aaacde504@tools.ietf.org>
X-Trac-Ticket-ID: 22
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: ietf.hanserik@gmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #22: 3.2.3 as currently phrased not really an issue
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 25 Mar 2010 00:25:18 -0000

#22: 3.2.3 as currently phrased not really an issue
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |       Owner:            
     Type:  defect                   |      Status:  new       
 Priority:  minor                    |   Milestone:  milestone1
Component:  reqs                     |     Version:  1.0       
 Severity:  In WG Last Call          |    Keywords:            
-------------------------------------+--------------------------------------
 3.2.3. Request-URI mis-routing

 This is again not an issue with a mechanism, but with a PBX not complying
 or implementing that mechanism. This can not be resolved by writing a new
 specification introducing yet another mechanism...

 Tend to think therefore that this is a non-issue, suggest to remove the
 section.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/22>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Wed Mar 24 18:04:11 2010
Return-Path: <trac@tools.ietf.org>
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 9E6233A6A0C for <martini@core3.amsl.com>; Wed, 24 Mar 2010 18:04:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.751
X-Spam-Level: 
X-Spam-Status: No, score=-99.751 tagged_above=-999 required=5 tests=[AWL=-0.140, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 ZTfCLrlkON-g for <martini@core3.amsl.com>; Wed, 24 Mar 2010 18:04:09 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 3C5DB3A67D4 for <martini@ietf.org>; Wed, 24 Mar 2010 18:04:09 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NubUs-0000kS-At; Wed, 24 Mar 2010 18:04:30 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: ietf.hanserik@gmail.com
X-Trac-Project: martini
Date: Thu, 25 Mar 2010 01:04:30 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/23
Message-ID: <065.40c2d598244935a425326d5bba86bee7@tools.ietf.org>
X-Trac-Ticket-ID: 23
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: ietf.hanserik@gmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini] #23: 3.3 unlear whether mentioned issues are tackled or not
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 25 Mar 2010 01:04:11 -0000

#23: 3.3 unlear whether mentioned issues are tackled or not
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |       Owner:            
     Type:  defect                   |      Status:  new       
 Priority:  minor                    |   Milestone:  milestone1
Component:  reqs                     |     Version:  1.0       
 Severity:  In WG Last Call          |    Keywords:            
-------------------------------------+--------------------------------------
 3.3.  Policy-related issues
        3.3.1.  Authorization policy mismatches
        3.3.2.  PAI or PPI URI mismatches

 The issues described are valid for requests sent from an IP-PBX to the
 SSP. But the rest of the reqs not the gin draft for that matter seem to
 address requests other then REGISTER.

 So questions are these issues still relevant, if so are there missing
 requirements? or do we need text explaining why these scenarios are not
 further covered?

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/23>
martini <http://tools.ietf.org/martini/>


From ietf.hanserik@gmail.com  Wed Mar 24 18:42:02 2010
Return-Path: <ietf.hanserik@gmail.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 1F20F3A6BD6 for <martini@core3.amsl.com>; Wed, 24 Mar 2010 18:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.359
X-Spam-Level: *
X-Spam-Status: No, score=1.359 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, 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 CGqdudrG3qIW for <martini@core3.amsl.com>; Wed, 24 Mar 2010 18:42:01 -0700 (PDT)
Received: from mail-ew0-f227.google.com (mail-ew0-f227.google.com [209.85.219.227]) by core3.amsl.com (Postfix) with ESMTP id C21B83A6BD5 for <martini@ietf.org>; Wed, 24 Mar 2010 18:41:59 -0700 (PDT)
Received: by ewy27 with SMTP id 27so2136569ewy.13 for <martini@ietf.org>; Wed, 24 Mar 2010 18:42:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:received:message-id :subject:from:to:cc:content-type; bh=YKv7RXNlFiDA43eFWQJyKY5FRVhWf/n9UQPK4RmSwfk=; b=OcvlBY4PTLgrY+96cA0SZ092h9Xdfs/dr8fk5cXw0/VRf51wI7lb6hQmVBjGsz9By9 HAB0LDJsQ/qn2xcR3wjrbjb5+yceu+wnWkdDwDZ3nSx/oSdYNWGpfoRd+OxLv9YLdv7I IvxB6UUg4w+cXIanohXChxyg5XH7IXx5BrDXU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=uZrYqF4rVTkiRwT3tsut0K2489Hz8AVx0rAiZDzU2esawPhyPDHJDJFAfTwUaGPH2h RBdqrFMHfBYqaeYyNG5ByutKN5nO10X7lSOjp5+WP7rI8XoaH1J33F2y65vDYhktkGRj zTNN5hnMuCHwr4/B/dfYp46TcBcn00bsHz2mc=
MIME-Version: 1.0
Received: by 10.213.36.7 with HTTP; Wed, 24 Mar 2010 18:42:14 -0700 (PDT)
Date: Thu, 25 Mar 2010 02:42:14 +0100
Received: by 10.213.2.79 with SMTP id 15mr2483885ebi.59.1269481334577; Wed, 24  Mar 2010 18:42:14 -0700 (PDT)
Message-ID: <9ae56b1e1003241842m2525cf68k6da34b0e370c2d3d@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>,  Hadriel Kaplan <HKaplan@acmepacket.com>
Content-Type: multipart/alternative; boundary=001517476818ff1a28048296273b
Cc: martini@ietf.org
Subject: [martini] Q on REQ10 from draft-ietf-martini-reqs-02
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: Thu, 25 Mar 2010 01:42:02 -0000

--001517476818ff1a28048296273b
Content-Type: text/plain; charset=ISO-8859-1

Hi John, Hadriel,

"REQ10 - The mechanism MUST work in the presence of intermediate SIP
entities on the SSP side of the SIP-PBX-to-SSP interface (i.e.,
between the SIP-PBX and the SSP's domain proxy), where those
intermediate SIP entities need to be on the path of inbound requests
to the PBX."

Are these arbitrary intermediary SIP entities? Do they have to be aware of
the extension or not?

Does this mean that we need Proxy-Require: path?

/Hans Erik van Elburg

--001517476818ff1a28048296273b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi John, Hadriel,<br><br>&quot;REQ10 - The mechanism MUST work in the prese=
nce of intermediate SIP<br>   entities on the SSP side of the SIP-PBX-to-SS=
P interface (i.e.,<br>   between the SIP-PBX and the SSP&#39;s domain proxy=
), where those<br>
   intermediate SIP entities need to be on the path of inbound requests<br>=
   to the PBX.&quot;<br><br>Are these arbitrary intermediary SIP entities? =
Do they have to be aware of the extension or not?<br><br>Does this mean tha=
t we need Proxy-Require: path?<br>
<br clear=3D"all">/Hans Erik van Elburg<br>

--001517476818ff1a28048296273b--

From john.elwell@siemens-enterprise.com  Wed Mar 24 18:54:40 2010
Return-Path: <john.elwell@siemens-enterprise.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 9562E3A6B1F for <martini@core3.amsl.com>; Wed, 24 Mar 2010 18:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.031
X-Spam-Level: 
X-Spam-Status: No, score=0.031 tagged_above=-999 required=5 tests=[AWL=1.273,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 Y1KoUE2BwnwJ for <martini@core3.amsl.com>; Wed, 24 Mar 2010 18:54:39 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 76EFE3A695C for <martini@ietf.org>; Wed, 24 Mar 2010 18:54:39 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1335659; Thu, 25 Mar 2010 02:54:59 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id E2DDD23F02AA; Thu, 25 Mar 2010 02:54:59 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Thu, 25 Mar 2010 02:55:00 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>, Hadriel Kaplan <HKaplan@acmepacket.com>
Date: Thu, 25 Mar 2010 02:54:57 +0100
Thread-Topic: Q on REQ10 from draft-ietf-martini-reqs-02
Thread-Index: AcrLvGXBINc7KRAZTZmpzqCKM7kmDwAAWNtg
Message-ID: <A444A0F8084434499206E78C106220CADE09A645@MCHP058A.global-ad.net>
References: <9ae56b1e1003241842m2525cf68k6da34b0e370c2d3d@mail.gmail.com>
In-Reply-To: <9ae56b1e1003241842m2525cf68k6da34b0e370c2d3d@mail.gmail.com>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Q on REQ10 from draft-ietf-martini-reqs-02
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: Thu, 25 Mar 2010 01:54:40 -0000

That is a matter for the solution to determine. A solution might work witho=
ut special support, might work better with special support, or might requir=
e special support. This will dictate whether mechanisms such as Proxy-Requi=
re are needed.

John=20

> -----Original Message-----
> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]=20
> Sent: 24 March 2010 18:42
> To: Elwell, John; Hadriel Kaplan
> Cc: martini@ietf.org
> Subject: Q on REQ10 from draft-ietf-martini-reqs-02
>=20
> Hi John, Hadriel,
>=20
> "REQ10 - The mechanism MUST work in the presence of intermediate SIP
> entities on the SSP side of the SIP-PBX-to-SSP interface (i.e.,
> between the SIP-PBX and the SSP's domain proxy), where those
> intermediate SIP entities need to be on the path of inbound requests
> to the PBX."
>=20
> Are these arbitrary intermediary SIP entities? Do they have=20
> to be aware of the extension or not?
>=20
> Does this mean that we need Proxy-Require: path?
>=20
> /Hans Erik van Elburg
>=20
> =

From ietf.hanserik@gmail.com  Thu Mar 25 03:28:19 2010
Return-Path: <ietf.hanserik@gmail.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 75FA13A6A25 for <martini@core3.amsl.com>; Thu, 25 Mar 2010 03:28:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.359
X-Spam-Level: *
X-Spam-Status: No, score=1.359 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, 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 pQQniW3JSJ-N for <martini@core3.amsl.com>; Thu, 25 Mar 2010 03:28:18 -0700 (PDT)
Received: from mail-ew0-f227.google.com (mail-ew0-f227.google.com [209.85.219.227]) by core3.amsl.com (Postfix) with ESMTP id 42FCA3A6925 for <martini@ietf.org>; Thu, 25 Mar 2010 03:28:17 -0700 (PDT)
Received: by ewy27 with SMTP id 27so2236521ewy.13 for <martini@ietf.org>; Thu, 25 Mar 2010 03:28:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=0UU2AGqq3AX8xYfEObr3XPN10zOaG4PtuUVM5VhWVuE=; b=dlyLVVMNvcXugk5fWiUeMxQdGVlpuM0lo65GCd5douM8z66EnRFJgMc5GVf4JpPTGA 2Cyunx952RFg5uYEvBOluZ7op30JaCLkC03JR4AGZ1J33KRfF0ENsfcjW7ShV5GT2wVh GwlpS1tc5kY7n1Jy6kOB24NsVb9sJXD3NRH/c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=GEccmoo5fU0a1lme/HxJmiydc3GqsY4+W9XWuETK0yjn/ARlls7QKf9pSeS7GrF2u/ T3MrM6//eqRIG0Rb2zgthJRI9wzLa/K3UZIJnJ++686aogdJuZp69Svr/GIN41cBE4Ua TqBZu5rFePjAQkmfFPvjWAwpN8eeH5T/MBB0U=
MIME-Version: 1.0
Received: by 10.213.109.91 with SMTP id i27mr4796843ebp.3.1269512915711; Thu,  25 Mar 2010 03:28:35 -0700 (PDT)
In-Reply-To: <A444A0F8084434499206E78C106220CADE09A645@MCHP058A.global-ad.net>
References: <9ae56b1e1003241842m2525cf68k6da34b0e370c2d3d@mail.gmail.com> <A444A0F8084434499206E78C106220CADE09A645@MCHP058A.global-ad.net>
Date: Thu, 25 Mar 2010 11:28:35 +0100
Message-ID: <9ae56b1e1003250328y6db7de2cifba0bed2b49dfba1@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Content-Type: multipart/alternative; boundary=000e0cdf754060f73404829d82d0
Cc: "martini@ietf.org" <martini@ietf.org>, Hadriel Kaplan <HKaplan@acmepacket.com>
Subject: Re: [martini] Q on REQ10 from draft-ietf-martini-reqs-02
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: Thu, 25 Mar 2010 10:28:19 -0000

--000e0cdf754060f73404829d82d0
Content-Type: text/plain; charset=ISO-8859-1

Hi John,

Right. But it is not as if there is not a state of the art that you are
formulating your requirements against.

Are these arbitrary intermediary SIP entities? edge proxies? SBC's?

What does it mean to be on THE path? Is it always the same path?

If the requirement states that path is understood as the path concept in the
Path RFC then it is unambigous what is ment.

Additrional question while rereading, why does the requirement only adress
intermediary entities on the SSP side? It is very likely that corporates
deploy SBC like devices on the edge too, to protect their network, too fix
media routing etc. You do not want to disallow that.

BR,
/Hans Erik van Elburg

On Thu, Mar 25, 2010 at 2:54 AM, Elwell, John <
john.elwell@siemens-enterprise.com> wrote:

> That is a matter for the solution to determine. A solution might work
> without special support, might work better with special support, or might
> require special support. This will dictate whether mechanisms such as
> Proxy-Require are needed.
>
> John
>
> > -----Original Message-----
> > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
> > Sent: 24 March 2010 18:42
> > To: Elwell, John; Hadriel Kaplan
> > Cc: martini@ietf.org
> > Subject: Q on REQ10 from draft-ietf-martini-reqs-02
> >
> > Hi John, Hadriel,
> >
> > "REQ10 - The mechanism MUST work in the presence of intermediate SIP
> > entities on the SSP side of the SIP-PBX-to-SSP interface (i.e.,
> > between the SIP-PBX and the SSP's domain proxy), where those
> > intermediate SIP entities need to be on the path of inbound requests
> > to the PBX."
> >
> > Are these arbitrary intermediary SIP entities? Do they have
> > to be aware of the extension or not?
> >
> > Does this mean that we need Proxy-Require: path?
> >
> > /Hans Erik van Elburg
> >
> >
>

--000e0cdf754060f73404829d82d0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi John,<br><br>Right. But it is not as if there is not a state of the art =
that you are formulating your requirements against.<br><br>Are these arbitr=
ary intermediary SIP entities? edge proxies? SBC&#39;s?<br><br>What does it=
 mean to be on THE path? Is it always the same path?<br>
<br>If the requirement states that path is understood as the path concept i=
n the Path RFC then it is unambigous what is ment. <br><br>Additrional ques=
tion while rereading, why does the requirement only adress intermediary ent=
ities on the SSP side? It is very likely that corporates deploy SBC like de=
vices on the edge too, to protect their network, too fix media routing etc.=
 You do not want to disallow that.<br>
<br>BR,<br clear=3D"all">/Hans Erik van Elburg<br>
<br><div class=3D"gmail_quote">On Thu, Mar 25, 2010 at 2:54 AM, Elwell, Joh=
n <span dir=3D"ltr">&lt;<a href=3D"mailto:john.elwell@siemens-enterprise.co=
m">john.elwell@siemens-enterprise.com</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px =
solid rgb(204, 204, 204); padding-left: 1ex;">
That is a matter for the solution to determine. A solution might work witho=
ut special support, might work better with special support, or might requir=
e special support. This will dictate whether mechanisms such as Proxy-Requi=
re are needed.<br>

<font color=3D"#888888"><br>
John<br>
</font><div><div></div><div class=3D"h5"><br>
&gt; -----Original Message-----<br>
&gt; From: Hans Erik van Elburg [mailto:<a href=3D"mailto:ietf.hanserik@gma=
il.com">ietf.hanserik@gmail.com</a>]<br>
&gt; Sent: 24 March 2010 18:42<br>
&gt; To: Elwell, John; Hadriel Kaplan<br>
&gt; Cc: <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; Subject: Q on REQ10 from draft-ietf-martini-reqs-02<br>
&gt;<br>
&gt; Hi John, Hadriel,<br>
&gt;<br>
&gt; &quot;REQ10 - The mechanism MUST work in the presence of intermediate =
SIP<br>
&gt; entities on the SSP side of the SIP-PBX-to-SSP interface (i.e.,<br>
&gt; between the SIP-PBX and the SSP&#39;s domain proxy), where those<br>
&gt; intermediate SIP entities need to be on the path of inbound requests<b=
r>
&gt; to the PBX.&quot;<br>
&gt;<br>
&gt; Are these arbitrary intermediary SIP entities? Do they have<br>
&gt; to be aware of the extension or not?<br>
&gt;<br>
&gt; Does this mean that we need Proxy-Require: path?<br>
&gt;<br>
&gt; /Hans Erik van Elburg<br>
&gt;<br>
&gt; </div></div></blockquote></div><br>

--000e0cdf754060f73404829d82d0--

From john.elwell@siemens-enterprise.com  Thu Mar 25 08:09:54 2010
Return-Path: <john.elwell@siemens-enterprise.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 7DA5A3A68D4 for <martini@core3.amsl.com>; Thu, 25 Mar 2010 08:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.239
X-Spam-Level: *
X-Spam-Status: No, score=1.239 tagged_above=-999 required=5 tests=[AWL=-0.119,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, 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 n-PpV+jkeKE7 for <martini@core3.amsl.com>; Thu, 25 Mar 2010 08:09:53 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 6AAD03A687B for <martini@ietf.org>; Thu, 25 Mar 2010 08:09:52 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1344928; Thu, 25 Mar 2010 16:10:13 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 40E4C1EB82AE; Thu, 25 Mar 2010 16:10:13 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Thu, 25 Mar 2010 16:10:13 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>
Date: Thu, 25 Mar 2010 16:10:11 +0100
Thread-Topic: Q on REQ10 from draft-ietf-martini-reqs-02
Thread-Index: AcrMBe4l49Q10IZVSxWwiCpcUBnoVgAJnDng
Message-ID: <A444A0F8084434499206E78C106220CADE09A9FF@MCHP058A.global-ad.net>
References: <9ae56b1e1003241842m2525cf68k6da34b0e370c2d3d@mail.gmail.com> <A444A0F8084434499206E78C106220CADE09A645@MCHP058A.global-ad.net> <9ae56b1e1003250328y6db7de2cifba0bed2b49dfba1@mail.gmail.com>
In-Reply-To: <9ae56b1e1003250328y6db7de2cifba0bed2b49dfba1@mail.gmail.com>
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
Cc: "martini@ietf.org" <martini@ietf.org>, Hadriel Kaplan <HKaplan@acmepacket.com>
Subject: Re: [martini] Q on REQ10 from draft-ietf-martini-reqs-02
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: Thu, 25 Mar 2010 15:09:54 -0000

=20

> -----Original Message-----
> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]=20
> Sent: 25 March 2010 03:29
> To: Elwell, John
> Cc: Hadriel Kaplan; martini@ietf.org
> Subject: Re: Q on REQ10 from draft-ietf-martini-reqs-02
>=20
> Hi John,
>=20
> Right. But it is not as if there is not a state of the art=20
> that you are formulating your requirements against.
>=20
> Are these arbitrary intermediary SIP entities? edge proxies? SBC's?
[JRE] Any of these.

>=20
> What does it mean to be on THE path? Is it always the same path?
[JRE] On the path that requests follow. It is difficult to get more precise=
 without anticipating solutions.

>=20
> If the requirement states that path is understood as the path=20
> concept in the Path RFC then it is unambigous what is ment.=20
>=20
> Additrional question while rereading, why does the=20
> requirement only adress intermediary entities on the SSP=20
> side? It is very likely that corporates deploy SBC like=20
> devices on the edge too, to protect their network, too fix=20
> media routing etc. You do not want to disallow that.
[JRE] I thought this question had been answered earlier. Where there is an =
SBC, for example, on the boundary of the enterprise network, this would rep=
resent the PBX. Typically it is that device that will initiate the REGISTER=
 request, for example. So the edge device IS the SIP-PBX - the fact that it=
 might not be the complete PBX, but just an edge device, does not seem to m=
atter.

John
=20
>=20
> BR,
> /Hans Erik van Elburg
>=20
>=20
> On Thu, Mar 25, 2010 at 2:54 AM, Elwell, John=20
> <john.elwell@siemens-enterprise.com> wrote:
>=20
>=20
> 	That is a matter for the solution to determine. A=20
> solution might work without special support, might work=20
> better with special support, or might require special=20
> support. This will dictate whether mechanisms such as=20
> Proxy-Require are needed.
> =09
> 	John
> =09
>=20
> 	> -----Original Message-----
> 	> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
> 	> Sent: 24 March 2010 18:42
> 	> To: Elwell, John; Hadriel Kaplan
> 	> Cc: martini@ietf.org
> 	> Subject: Q on REQ10 from draft-ietf-martini-reqs-02
> 	>
> 	> Hi John, Hadriel,
> 	>
> 	> "REQ10 - The mechanism MUST work in the presence of=20
> intermediate SIP
> 	> entities on the SSP side of the SIP-PBX-to-SSP=20
> interface (i.e.,
> 	> between the SIP-PBX and the SSP's domain proxy), where those
> 	> intermediate SIP entities need to be on the path of=20
> inbound requests
> 	> to the PBX."
> 	>
> 	> Are these arbitrary intermediary SIP entities? Do they have
> 	> to be aware of the extension or not?
> 	>
> 	> Does this mean that we need Proxy-Require: path?
> 	>
> 	> /Hans Erik van Elburg
> 	>
> 	>=20
>=20
>=20
> =

From ietf.hanserik@gmail.com  Thu Mar 25 10:36:33 2010
Return-Path: <ietf.hanserik@gmail.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 7BD093A6B8A for <martini@core3.amsl.com>; Thu, 25 Mar 2010 10:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.359
X-Spam-Level: *
X-Spam-Status: No, score=1.359 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, 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 o5QXXGKm-jjn for <martini@core3.amsl.com>; Thu, 25 Mar 2010 10:36:32 -0700 (PDT)
Received: from mail-ew0-f227.google.com (mail-ew0-f227.google.com [209.85.219.227]) by core3.amsl.com (Postfix) with ESMTP id 433683A6E24 for <martini@ietf.org>; Thu, 25 Mar 2010 10:32:01 -0700 (PDT)
Received: by ewy27 with SMTP id 27so2750367ewy.33 for <martini@ietf.org>; Thu, 25 Mar 2010 10:32:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=Ei6cpK0vlXoyOfG0SUQrwRJ3jLyQE7XH8Qo4wKj/JBs=; b=CH7jic4N9cyRP10YR4sf6MwlA9nUravxy6N0Cw/yqQJuDFjejC5Zif1g5O7a9HPpfD anblYo9Oa7Xn6+mCgnaJ1EeejkG8FOhegeAHH7QQek4vvdv65U5N5tbKGKn4DNvb+7vr Q6ugBuXJ6Q/xZXXQH2gBqj5ozlElSgUmA2dX4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=lVckYATGtjXKT1sa/HGNUZkLxzNXIOMGwQfjhhs+7ccBA1TJlFGA/qTWbBIQxqMA75 7g22ujjRrwJX0tPkt1IpYSEaGAVYA+1hqJz9hwTnT6TZY3SG0ywAHyl/39qSgj4FkjCc 1aPT5zmEh+IinqgyyC2aPF620e+fjhLTg4O1Y=
MIME-Version: 1.0
Received: by 10.213.6.193 with HTTP; Thu, 25 Mar 2010 10:32:19 -0700 (PDT)
In-Reply-To: <A444A0F8084434499206E78C106220CADE09A9FF@MCHP058A.global-ad.net>
References: <9ae56b1e1003241842m2525cf68k6da34b0e370c2d3d@mail.gmail.com> <A444A0F8084434499206E78C106220CADE09A645@MCHP058A.global-ad.net> <9ae56b1e1003250328y6db7de2cifba0bed2b49dfba1@mail.gmail.com> <A444A0F8084434499206E78C106220CADE09A9FF@MCHP058A.global-ad.net>
Date: Thu, 25 Mar 2010 18:32:19 +0100
Received: by 10.213.1.203 with SMTP id 11mr743944ebg.37.1269538339184; Thu, 25  Mar 2010 10:32:19 -0700 (PDT)
Message-ID: <9ae56b1e1003251032x68eff4cfp4fae98b7e1e18ecf@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Content-Type: multipart/alternative; boundary=000e0cd1f92cbc5f750482a36da1
Cc: "martini@ietf.org" <martini@ietf.org>, Hadriel Kaplan <HKaplan@acmepacket.com>
Subject: Re: [martini] Q on REQ10 from draft-ietf-martini-reqs-02
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: Thu, 25 Mar 2010 17:36:33 -0000

--000e0cd1f92cbc5f750482a36da1
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Mar 25, 2010 at 4:10 PM, Elwell, John <
john.elwell@siemens-enterprise.com> wrote:

>
> > Additrional question while rereading, why does the
> > requirement only adress intermediary entities on the SSP
> > side? It is very likely that corporates deploy SBC like
> > devices on the edge too, to protect their network, too fix
> > media routing etc. You do not want to disallow that.
>
[JRE] I thought this question had been answered earlier. Where there is an
> SBC, for example, on the boundary of the enterprise network, this would
> represent the PBX. Typically it is that device that will initiate the
> REGISTER request, for example. So the edge device IS the SIP-PBX - the fact
> that it might not be the complete PBX, but just an edge device, does not
> seem to matter.
>
>
[HE] I do think it is an unnecessary scoping, why distinguish whether
intermediary SIP entities belong to the SSPs or the enterprise? Saying that
an enterprise SBC shall do the registration on behalf of the PBX is
unnecessarily narrowing down the set of deployments too.

Suggest to rewrite the requirement as:
*
**"REQ10 - The mechanism MUST work in the presence of a sequence of
intermediate SIP entities on the SIP-PBX-to-SSP interface (i.e., between the
SIP-PBX and the SSP's domain proxy), where those intermediate SIP entities
indicated during registration they wished to be on the path for future
requests towards the registering UA (SIP-PBX)."* *
*
This is completely OK, as the martini charter is explicit about that it is
working an a registration based solution. This is also reflected in REQ3.

BR,
/Hans Erik

--000e0cd1f92cbc5f750482a36da1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote">On Thu, Mar 25, 2010 at 4:10 PM, Elwell, Joh=
n <span dir=3D"ltr">&lt;<a href=3D"mailto:john.elwell@siemens-enterprise.co=
m">john.elwell@siemens-enterprise.com</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px =
solid rgb(204, 204, 204); padding-left: 1ex;">
<div class=3D"im"><br>
&gt; Additrional question while rereading, why does the<br>
&gt; requirement only adress intermediary entities on the SSP<br>
&gt; side? It is very likely that corporates deploy SBC like<br>
&gt; devices on the edge too, to protect their network, too fix<br>
&gt; media routing etc. You do not want to disallow that.<br>
</div></blockquote><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0=
pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;=
">[JRE] I thought this question had been answered earlier. Where there is a=
n SBC, for example, on the boundary of the enterprise network, this would r=
epresent the PBX. Typically it is that device that will initiate the REGIST=
ER request, for example. So the edge device IS the SIP-PBX - the fact that =
it might not be the complete PBX, but just an edge device, does not seem to=
 matter.<br>

<br></blockquote><div><br><meta http-equiv=3D"Content-Type" content=3D"text=
/html; charset=3Dutf-8"><meta name=3D"ProgId" content=3D"Word.Document"><me=
ta name=3D"Generator" content=3D"Microsoft Word 12"><meta name=3D"Originato=
r" content=3D"Microsoft Word 12"><link rel=3D"File-List" href=3D"file:///C:=
%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_f=
ilelist.xml"><link rel=3D"themeData" href=3D"file:///C:%5CDOCUME%7E1%5CDTC1=
02%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link=
 rel=3D"colorSchemeMapping" href=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5C=
LOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><style=
>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-alt:"Calisto MT";
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-1610611985 1107304683 0 0 159 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-alt:"Arial Rounded MT Bold";
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1610611985 1073750139 0 0 159 0;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-1610611985 1073750091 0 0 159 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;
	mso-fareast-language:EN-US;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.5pt;
	font-family:Consolas;
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:"Times New Roman";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Plain Text";
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Consolas;
	mso-ascii-font-family:Consolas;
	mso-fareast-font-family:"Times New Roman";
	mso-hansi-font-family:Consolas;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:DE;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;
	mso-fareast-language:EN-US;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>[HE] I do think it is an unnecessary scoping, why distinguish wheth=
er intermediary SIP entities belong to the SSPs or the enterprise? Saying t=
hat an enterprise SBC shall do the registration on behalf of the PBX is unn=
ecessarily narrowing down the set of deployments too.<span style=3D"color: =
black;"></span> <br>
<br><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8=
"><meta name=3D"ProgId" content=3D"Word.Document"><meta name=3D"Generator" =
content=3D"Microsoft Word 12"><meta name=3D"Originator" content=3D"Microsof=
t Word 12"><link rel=3D"File-List" href=3D"file:///C:%5CDOCUME%7E1%5CDTC102=
%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link rel=
=3D"themeData" href=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5C=
Temp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link rel=3D"colorSchemeMap=
ping" href=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5CTemp%5Cms=
ohtmlclip1%5C01%5Cclip_colorschememapping.xml"><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-alt:"Calisto MT";
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-1610611985 1107304683 0 0 159 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-alt:"Arial Rounded MT Bold";
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1610611985 1073750139 0 0 159 0;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-1610611985 1073750091 0 0 159 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;
	mso-fareast-language:EN-US;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.5pt;
	font-family:Consolas;
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:"Times New Roman";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Plain Text";
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Consolas;
	mso-ascii-font-family:Consolas;
	mso-fareast-font-family:"Times New Roman";
	mso-hansi-font-family:Consolas;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:DE;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;
	mso-fareast-language:EN-US;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>Suggest to rewrite the requirement as:<br><b><br></b><b>&quot;REQ10=
 - The mechanism MUST work in the presence of a sequence of intermediate=20
SIP entities on the SIP-PBX-to-SSP interface (i.e., between the SIP-PBX=20
and the SSP&#39;s domain proxy), where those intermediate SIP entities indi=
cated during=20
registration they wished to be on the path for future requests towards=20
the registering UA (SIP-PBX).&quot;<span style=3D"color: black;"></span></b=
>

<b><br>
</b><br>This is completely OK, as the martini charter is explicit about tha=
t it is working an a registration based solution. This is also reflected in=
 REQ3.<br><br>BR,<br>/Hans Erik<br></div></div>

--000e0cd1f92cbc5f750482a36da1--

From trac@tools.ietf.org  Thu Mar 25 12:43:15 2010
Return-Path: <trac@tools.ietf.org>
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 5A4593A6B70 for <martini@core3.amsl.com>; Thu, 25 Mar 2010 12:43:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.727
X-Spam-Level: 
X-Spam-Status: No, score=-100.727 tagged_above=-999 required=5 tests=[AWL=0.743, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 LObcxL9WlzrU for <martini@core3.amsl.com>; Thu, 25 Mar 2010 12:43:11 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 6F3233A6A2A for <martini@ietf.org>; Thu, 25 Mar 2010 12:43:11 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nusxp-0006Tp-EB; Thu, 25 Mar 2010 12:43:33 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Thu, 25 Mar 2010 19:43:33 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/18#comment:1
Message-ID: <076.fee145d02593ec8ea3d53fc07698ca7c@tools.ietf.org>
References: <067.d55f218aa49a60c488c40b0816b9c460@tools.ietf.org>
X-Trac-Ticket-ID: 18
In-Reply-To: <067.d55f218aa49a60c488c40b0816b9c460@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #18: References
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 25 Mar 2010 19:43:15 -0000

#18: References
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:  john.elwell@…                     
     Type:  defect                     |       Status:  closed                            
 Priority:  minor                      |    Milestone:  milestone1                        
Component:  reqs                       |      Version:  1.0                               
 Severity:  In WG Last Call            |   Resolution:  wontfix                           
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by john.elwell@…):

  * status:  new => closed
  * resolution:  => wontfix


Comment:

 We have a reference to TS 182 025, and that in turn references the others,
 so I see no need to add these others to the draft.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/18#comment:1>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Thu Mar 25 12:46:37 2010
Return-Path: <trac@tools.ietf.org>
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 7AC703A6A7A for <martini@core3.amsl.com>; Thu, 25 Mar 2010 12:46:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.776
X-Spam-Level: 
X-Spam-Status: No, score=-100.776 tagged_above=-999 required=5 tests=[AWL=0.694, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 Uqp6P91MjqHu for <martini@core3.amsl.com>; Thu, 25 Mar 2010 12:46:36 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id C2E2D3A6895 for <martini@ietf.org>; Thu, 25 Mar 2010 12:46:36 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nut19-0007gW-FO; Thu, 25 Mar 2010 12:46:59 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Thu, 25 Mar 2010 19:46:59 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/19#comment:1
Message-ID: <074.6a967cbbdf4d364d58ff0c3d1c830eca@tools.ietf.org>
References: <065.085b3ce99cf6d76da0963ed019c27c11@tools.ietf.org>
X-Trac-Ticket-ID: 19
In-Reply-To: <065.085b3ce99cf6d76da0963ed019c27c11@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #19: Remove DES4
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 25 Mar 2010 19:46:37 -0000

#19: Remove DES4
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |        Owner:            
     Type:  defect                   |       Status:  closed    
 Priority:  major                    |    Milestone:  milestone1
Component:  reqs                     |      Version:  1.0       
 Severity:  In WG Last Call          |   Resolution:  fixed     
 Keywords:                           |  
-------------------------------------+--------------------------------------
Changes (by john.elwell@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/19#comment:1>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Thu Mar 25 13:14:43 2010
Return-Path: <trac@tools.ietf.org>
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 31DA13A6A0A for <martini@core3.amsl.com>; Thu, 25 Mar 2010 13:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.89
X-Spam-Level: 
X-Spam-Status: No, score=-99.89 tagged_above=-999 required=5 tests=[AWL=-0.279, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 707HSwBDsACA for <martini@core3.amsl.com>; Thu, 25 Mar 2010 13:14:37 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 37B463A67D3 for <martini@ietf.org>; Thu, 25 Mar 2010 13:14:34 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NutSC-0001im-IK; Thu, 25 Mar 2010 13:14:56 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Thu, 25 Mar 2010 20:14:56 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/20#comment:1
Message-ID: <074.d5b79c9d002d1d9a8fbdcbdc4568c32c@tools.ietf.org>
References: <065.606d2b6083a21b5a6fdc3bf7754c2d3e@tools.ietf.org>
X-Trac-Ticket-ID: 20
In-Reply-To: <065.606d2b6083a21b5a6fdc3bf7754c2d3e@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #20: Section 3.1.2 does not decscribe an issue
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 25 Mar 2010 20:14:44 -0000

#20: Section 3.1.2 does not decscribe an issue
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |       Owner:  john.elwell@…                     
     Type:  defect                   |      Status:  assigned                          
 Priority:  minor                    |   Milestone:  milestone1                        
Component:  reqs                     |     Version:  1.0                               
 Severity:  In WG Last Call          |    Keywords:                                    
-------------------------------------+--------------------------------------
Changes (by john.elwell@…):

  * owner:  => john.elwell@…
  * status:  new => assigned


Comment:

 I disagree that it is not an issue if you receive unexpected PAU. If the
 PBX receives unexpected values, what does it do with them? They clearly
 will not map to any PBX extensions. Even worse, if the PAU omits certain
 values the PBX expects, what action does the PBX take? Unless others speak
 up soon in favour of making any change to 3.1.2, I will close this as
 'won't fix'.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/20#comment:1>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Thu Mar 25 13:24:04 2010
Return-Path: <trac@tools.ietf.org>
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 D05C53A6A7E for <martini@core3.amsl.com>; Thu, 25 Mar 2010 13:24:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.803
X-Spam-Level: 
X-Spam-Status: No, score=-100.803 tagged_above=-999 required=5 tests=[AWL=0.667, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 VAX1FGkHVCFR for <martini@core3.amsl.com>; Thu, 25 Mar 2010 13:24:02 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 4FCE13A6C8B for <martini@ietf.org>; Thu, 25 Mar 2010 13:21:53 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NutZI-0001Rl-0g; Thu, 25 Mar 2010 13:22:16 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Thu, 25 Mar 2010 20:22:15 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1
Message-ID: <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org>
X-Trac-Ticket-ID: 21
In-Reply-To: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 25 Mar 2010 20:24:04 -0000

#21: 3.2.2 describes an issue with some PBX
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |        Owner:            
     Type:  defect                   |       Status:  closed    
 Priority:  minor                    |    Milestone:  milestone1
Component:  reqs                     |      Version:  1.0       
 Severity:  In WG Last Call          |   Resolution:  invalid   
 Keywords:                           |  
-------------------------------------+--------------------------------------
Changes (by john.elwell@…):

  * status:  new => closed
  * resolution:  => invalid


Comment:

 The text of 3.2.2 just underlines the fact that there are different
 implementations around. A PBX that expects the loose route mechanism to be
 used would fail to interwork with SSPs using a different mechanism (e.g.,
 SIPconnect 1.0), and a PBX not expecting the loose route mechanism to be
 used would fail to interwork with a loose route implementation (e.g.,
 ETSI/3GPP). Hence the urgent need for a standard.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
martini <http://tools.ietf.org/martini/>


From HKaplan@acmepacket.com  Thu Mar 25 13:25:38 2010
Return-Path: <HKaplan@acmepacket.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 4B1003A6907 for <martini@core3.amsl.com>; Thu, 25 Mar 2010 13:25:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.969
X-Spam-Level: 
X-Spam-Status: No, score=0.969 tagged_above=-999 required=5 tests=[AWL=-0.390,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, 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 axiNbqZzkewz for <martini@core3.amsl.com>; Thu, 25 Mar 2010 13:25:35 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id EFF693A6CC2 for <martini@ietf.org>; Thu, 25 Mar 2010 13:23:20 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Thu, 25 Mar 2010 16:23:42 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Thu, 25 Mar 2010 16:23:42 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
Date: Thu, 25 Mar 2010 16:23:40 -0400
Thread-Topic: Q on REQ10 from draft-ietf-martini-reqs-02
Thread-Index: AcrMQSxNZgJmaBn6TH2bzyrSsssaxAAF9MpA
Message-ID: <430FC6BDED356B4C8498F634416644A91A79E923BA@mail>
References: <9ae56b1e1003241842m2525cf68k6da34b0e370c2d3d@mail.gmail.com> <A444A0F8084434499206E78C106220CADE09A645@MCHP058A.global-ad.net> <9ae56b1e1003250328y6db7de2cifba0bed2b49dfba1@mail.gmail.com> <A444A0F8084434499206E78C106220CADE09A9FF@MCHP058A.global-ad.net> <9ae56b1e1003251032x68eff4cfp4fae98b7e1e18ecf@mail.gmail.com>
In-Reply-To: <9ae56b1e1003251032x68eff4cfp4fae98b7e1e18ecf@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_430FC6BDED356B4C8498F634416644A91A79E923BAmail_"
MIME-Version: 1.0
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Q on REQ10 from draft-ietf-martini-reqs-02
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: Thu, 25 Mar 2010 20:25:38 -0000

--_000_430FC6BDED356B4C8498F634416644A91A79E923BAmail_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Yeah I agree with Hans Erik - no harm in just making it generic.
-hadriel

________________________________
From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
Sent: Thursday, March 25, 2010 1:32 PM
To: Elwell, John
Cc: Hadriel Kaplan; martini@ietf.org
Subject: Re: Q on REQ10 from draft-ietf-martini-reqs-02


On Thu, Mar 25, 2010 at 4:10 PM, Elwell, John <john.elwell@siemens-enterpri=
se.com<mailto:john.elwell@siemens-enterprise.com>> wrote:

> Additrional question while rereading, why does the
> requirement only adress intermediary entities on the SSP
> side? It is very likely that corporates deploy SBC like
> devices on the edge too, to protect their network, too fix
> media routing etc. You do not want to disallow that.
[JRE] I thought this question had been answered earlier. Where there is an =
SBC, for example, on the boundary of the enterprise network, this would rep=
resent the PBX. Typically it is that device that will initiate the REGISTER=
 request, for example. So the edge device IS the SIP-PBX - the fact that it=
 might not be the complete PBX, but just an edge device, does not seem to m=
atter.

[HE] I do think it is an unnecessary scoping, why distinguish whether inter=
mediary SIP entities belong to the SSPs or the enterprise? Saying that an e=
nterprise SBC shall do the registration on behalf of the PBX is unnecessari=
ly narrowing down the set of deployments too.

Suggest to rewrite the requirement as:

"REQ10 - The mechanism MUST work in the presence of a sequence of intermedi=
ate SIP entities on the SIP-PBX-to-SSP interface (i.e., between the SIP-PBX=
 and the SSP's domain proxy), where those intermediate SIP entities indicat=
ed during registration they wished to be on the path for future requests to=
wards the registering UA (SIP-PBX)."

This is completely OK, as the martini charter is explicit about that it is =
working an a registration based solution. This is also reflected in REQ3.

BR,
/Hans Erik

--_000_430FC6BDED356B4C8498F634416644A91A79E923BAmail_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"Person=
Name"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--p.MSONORMAL
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-theme-font:minor-bidi;}
li.MSONORMAL
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-theme-font:minor-bidi;}
div.MSONORMAL
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-theme-font:minor-bidi;}
p.MSOPLAINTEXT
	{mso-style-priority:99;}
li.MSOPLAINTEXT
	{mso-style-priority:99;}
div.MSOPLAINTEXT
	{mso-style-priority:99;}
span.PLAINTEXTCHAR
	{mso-style-priority:99;
	mso-style-unhide:no;}
.MSOCHPDEFAULT
	{mso-default-props:yes;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-theme-font:minor-bidi;}
p.MSONORMAL
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-theme-font:minor-bidi;}
li.MSONORMAL
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-theme-font:minor-bidi;}
div.MSONORMAL
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-theme-font:minor-bidi;}
p.MSOPLAINTEXT
	{mso-style-priority:99;}
li.MSOPLAINTEXT
	{mso-style-priority:99;}
div.MSOPLAINTEXT
	{mso-style-priority:99;}
span.PLAINTEXTCHAR
	{mso-style-priority:99;
	mso-style-unhide:no;}
.MSOCHPDEFAULT
	{mso-default-props:yes;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-theme-font:minor-bidi;}

 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Yeah I agree with Hans Erik &#8211; no=
 harm
in just making it generic.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>-hadriel<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;font-family:"Times=
 New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> <st1:Per=
sonName
w:st=3D"on">Hans Erik van Elburg</st1:PersonName>
[mailto:ietf.hanserik@gmail.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, March 25, 20=
10
1:32 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Elwell, John<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName w:st=3D"=
on">Hadriel
 Kaplan</st1:PersonName>; martini@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: Q on REQ10 from
draft-ietf-martini-reqs-02</span></font><font size=3D3 face=3D"Times New Ro=
man"><span
style=3D'font-size:12.0pt;font-family:"Times New Roman"'><o:p></o:p></span>=
</font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'>On
Thu, Mar 25, 2010 at 4:10 PM, Elwell, John &lt;<a
href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-ente=
rprise.com</a>&gt;
wrote:<o:p></o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'><br>
&gt; Additrional question while rereading, why does the<br>
&gt; requirement only adress intermediary entities on the SSP<br>
&gt; side? It is very likely that corporates deploy SBC like<br>
&gt; devices on the edge too, to protect their network, too fix<br>
&gt; media routing etc. You do not want to disallow that.<o:p></o:p></span>=
</font></p>

</div>

<blockquote style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 face=3DC=
alibri><span
style=3D'font-size:11.0pt'>[JRE] I thought this question had been answered
earlier. Where there is an SBC, for example, on the boundary of the enterpr=
ise
network, this would represent the PBX. Typically it is that device that wil=
l
initiate the REGISTER request, for example. So the edge device IS the SIP-P=
BX -
the fact that it might not be the complete PBX, but just an edge device, do=
es
not seem to matter.<o:p></o:p></span></font></p>

</blockquote>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'><br>
</span></font><font size=3D3 face=3D"Times New Roman"><span style=3D'font-s=
ize:12.0pt;
font-family:"Times New Roman"'>
<link rel=3DthemeData
href=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtmlc=
lip1%5C01%5Cclip_themedata.thmx">
<link rel=3DcolorSchemeMapping
href=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtmlc=
lip1%5C01%5Cclip_colorschememapping.xml">
[HE] I do think it is an unnecessary scoping, why distinguish whether
intermediary SIP entities belong to the SSPs or the enterprise? Saying that=
 an
enterprise SBC shall do the registration on behalf of the PBX is unnecessar=
ily
narrowing down the set of deployments too. <br>
<br>
<link rel=3DthemeData
href=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtmlc=
lip1%5C01%5Cclip_themedata.thmx">
<link rel=3DcolorSchemeMapping
href=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtmlc=
lip1%5C01%5Cclip_colorschememapping.xml">
Suggest to rewrite the requirement as:<br>
<b><span style=3D'font-weight:bold'><br>
&quot;REQ10 - The mechanism MUST work in the presence of a sequence of
intermediate SIP entities on the SIP-PBX-to-SSP interface (i.e., between th=
e
SIP-PBX and the SSP's domain proxy), where those intermediate SIP entities
indicated during registration they wished to be on the path for future requ=
ests
towards the registering UA (SIP-PBX).&quot;</span></b> <b><span
style=3D'font-weight:bold'><br>
</span></b><br>
This is completely OK, as the martini charter is explicit about that it is
working an a registration based solution. This is also reflected in REQ3.<b=
r>
<br>
BR,<br>
/Hans Erik<o:p></o:p></span></font></p>

</div>

</div>

</div>

</div>

</body>

</html>

--_000_430FC6BDED356B4C8498F634416644A91A79E923BAmail_--

From trac@tools.ietf.org  Thu Mar 25 13:28:00 2010
Return-Path: <trac@tools.ietf.org>
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 391603A6907 for <martini@core3.amsl.com>; Thu, 25 Mar 2010 13:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.84
X-Spam-Level: 
X-Spam-Status: No, score=-100.84 tagged_above=-999 required=5 tests=[AWL=0.630, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 rWetej9prJ20 for <martini@core3.amsl.com>; Thu, 25 Mar 2010 13:27:59 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 873EA3A6984 for <martini@ietf.org>; Thu, 25 Mar 2010 13:27:55 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nutf7-0007mr-SO; Thu, 25 Mar 2010 13:28:17 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Thu, 25 Mar 2010 20:28:17 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/22#comment:1
Message-ID: <074.a040c9b2b948190227ce95413557774d@tools.ietf.org>
References: <065.2f0c12b2e457bc22e0ddda7aaacde504@tools.ietf.org>
X-Trac-Ticket-ID: 22
In-Reply-To: <065.2f0c12b2e457bc22e0ddda7aaacde504@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #22: 3.2.3 as currently phrased not really an issue
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 25 Mar 2010 20:28:00 -0000

#22: 3.2.3 as currently phrased not really an issue
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |        Owner:            
     Type:  defect                   |       Status:  closed    
 Priority:  minor                    |    Milestone:  milestone1
Component:  reqs                     |      Version:  1.0       
 Severity:  In WG Last Call          |   Resolution:  invalid   
 Keywords:                           |  
-------------------------------------+--------------------------------------
Changes (by john.elwell@…):

  * status:  new => closed
  * resolution:  => invalid


Comment:

 A PBX acting on SIP URIs identifying the SSP's domain as if it were its
 own domain would not be compliant with RFC 3261. So the use of such URIs
 is indeed a problem that needs to be solved.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/22#comment:1>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Thu Mar 25 13:37:37 2010
Return-Path: <trac@tools.ietf.org>
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 92D633A6892 for <martini@core3.amsl.com>; Thu, 25 Mar 2010 13:37:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.874
X-Spam-Level: 
X-Spam-Status: No, score=-100.874 tagged_above=-999 required=5 tests=[AWL=0.597, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 x5UoCBnJFGlp for <martini@core3.amsl.com>; Thu, 25 Mar 2010 13:37:36 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id D65003A6874 for <martini@ietf.org>; Thu, 25 Mar 2010 13:37:36 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NutoV-00040T-JE; Thu, 25 Mar 2010 13:37:59 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Thu, 25 Mar 2010 20:37:59 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/23#comment:1
Message-ID: <074.4856e6097fefd76af94b8c0ef95fbe7e@tools.ietf.org>
References: <065.40c2d598244935a425326d5bba86bee7@tools.ietf.org>
X-Trac-Ticket-ID: 23
In-Reply-To: <065.40c2d598244935a425326d5bba86bee7@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #23: 3.3 unlear whether mentioned issues are tackled or not
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Thu, 25 Mar 2010 20:37:37 -0000

#23: 3.3 unlear whether mentioned issues are tackled or not
-------------------------------------+--------------------------------------
 Reporter:  ietf.hanserik@…          |       Owner:  john.elwell@…                     
     Type:  defect                   |      Status:  assigned                          
 Priority:  minor                    |   Milestone:  milestone1                        
Component:  reqs                     |     Version:  1.0                               
 Severity:  In WG Last Call          |    Keywords:                                    
-------------------------------------+--------------------------------------
Changes (by john.elwell@…):

  * owner:  => john.elwell@…
  * status:  new => assigned


Comment:

 I am inclined to accept this comment, but the text came from Hadriel
 orginally. Hadriel, can you give an opinion whether we should delete
 sections 3.3.1 and 3.3.2 (and hence 3.3)?

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/23#comment:1>
martini <http://tools.ietf.org/martini/>


From john.elwell@siemens-enterprise.com  Thu Mar 25 13:41:13 2010
Return-Path: <john.elwell@siemens-enterprise.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 E3D7A3A6CEA for <martini@core3.amsl.com>; Thu, 25 Mar 2010 13:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.162
X-Spam-Level: 
X-Spam-Status: No, score=-0.162 tagged_above=-999 required=5 tests=[AWL=1.308,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 UQMJh-tHvV-h for <martini@core3.amsl.com>; Thu, 25 Mar 2010 13:41:13 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 3C6D43A6CE3 for <martini@ietf.org>; Thu, 25 Mar 2010 13:41:11 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1349212; Thu, 25 Mar 2010 21:41:33 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id CD8EF1EB82AB; Thu, 25 Mar 2010 21:41:33 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Thu, 25 Mar 2010 21:41:33 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Date: Thu, 25 Mar 2010 21:41:31 +0100
Thread-Topic: [martini] #23: 3.3 unlear whether mentioned issues are tackled or not
Thread-Index: AcrMWxTkBeHyRjJjT56kmXBW3+w0DwAACIAA
Message-ID: <A444A0F8084434499206E78C106220CADE09ABF2@MCHP058A.global-ad.net>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: [martini] FW: #23: 3.3 unlear whether mentioned issues are tackled or not
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: Thu, 25 Mar 2010 20:41:14 -0000

Hadriel,

I am forwarding this, as you are not explicitly addressed on the tracker me=
ssage. Please give your opinion on this matter. The issue is that sections =
3.2.1 and 3.2.2 do not seem relevant to the MARTINI question, and are not e=
ven backed up by any requirements in section 4 or by any mechanism in the g=
in draft.

Thanks,

John=20

> -----Original Message-----
> From: martini issue tracker [mailto:trac@tools.ietf.org]=20
> Sent: 25 March 2010 13:38
> To: Elwell, John
> Cc: martini@ietf.org
> Subject: Re: [martini] #23: 3.3 unlear whether mentioned=20
> issues are tackled or not
>=20
> #23: 3.3 unlear whether mentioned issues are tackled or not
> -------------------------------------+------------------------
> --------------
>  Reporter:  ietf.hanserik@...          |       Owner: =20
> john.elwell@...                    =20
>      Type:  defect                   |      Status:  assigned=20
>                         =20
>  Priority:  minor                    |   Milestone: =20
> milestone1                       =20
> Component:  reqs                     |     Version:  1.0     =20
>                         =20
>  Severity:  In WG Last Call          |    Keywords:          =20
>                         =20
> -------------------------------------+------------------------
> --------------
> Changes (by john.elwell@...):
>=20
>   * owner:  =3D> john.elwell@...
>   * status:  new =3D> assigned
>=20
>=20
> Comment:
>=20
>  I am inclined to accept this comment, but the text came from Hadriel
>  orginally. Hadriel, can you give an opinion whether we should delete
>  sections 3.3.1 and 3.3.2 (and hence 3.3)?
>=20
> --=20
> Ticket URL:=20
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/23#comment:1>
> martini <http://tools.ietf.org/martini/>
>=20
> =

From john.elwell@siemens-enterprise.com  Thu Mar 25 13:45:41 2010
Return-Path: <john.elwell@siemens-enterprise.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 45DED3A693C for <martini@core3.amsl.com>; Thu, 25 Mar 2010 13:45:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.122
X-Spam-Level: *
X-Spam-Status: No, score=1.122 tagged_above=-999 required=5 tests=[AWL=-0.237,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, 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 D69qIVZ05VuQ for <martini@core3.amsl.com>; Thu, 25 Mar 2010 13:45:36 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 5849A3A6950 for <martini@ietf.org>; Thu, 25 Mar 2010 13:45:35 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1349381; Thu, 25 Mar 2010 21:45:56 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id C225A23F028E; Thu, 25 Mar 2010 21:45:56 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Thu, 25 Mar 2010 21:45:56 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>, Hans Erik van Elburg <ietf.hanserik@gmail.com>
Date: Thu, 25 Mar 2010 21:45:54 +0100
Thread-Topic: Q on REQ10 from draft-ietf-martini-reqs-02
Thread-Index: AcrMQSxNZgJmaBn6TH2bzyrSsssaxAAF9MpAAADI8CA=
Message-ID: <A444A0F8084434499206E78C106220CADE09ABF7@MCHP058A.global-ad.net>
References: <9ae56b1e1003241842m2525cf68k6da34b0e370c2d3d@mail.gmail.com> <A444A0F8084434499206E78C106220CADE09A645@MCHP058A.global-ad.net> <9ae56b1e1003250328y6db7de2cifba0bed2b49dfba1@mail.gmail.com> <A444A0F8084434499206E78C106220CADE09A9FF@MCHP058A.global-ad.net> <9ae56b1e1003251032x68eff4cfp4fae98b7e1e18ecf@mail.gmail.com> <430FC6BDED356B4C8498F634416644A91A79E923BA@mail>
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79E923BA@mail>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A444A0F8084434499206E78C106220CADE09ABF7MCHP058Aglobala_"
MIME-Version: 1.0
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Q on REQ10 from draft-ietf-martini-reqs-02
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: Thu, 25 Mar 2010 20:45:41 -0000

--_000_A444A0F8084434499206E78C106220CADE09ABF7MCHP058Aglobala_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Done in my working copy.

John

________________________________
From: Hadriel Kaplan [mailto:HKaplan@acmepacket.com]
Sent: 25 March 2010 13:24
To: Hans Erik van Elburg; Elwell, John
Cc: martini@ietf.org
Subject: RE: Q on REQ10 from draft-ietf-martini-reqs-02

Yeah I agree with Hans Erik - no harm in just making it generic.
-hadriel

________________________________
From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
Sent: Thursday, March 25, 2010 1:32 PM
To: Elwell, John
Cc: Hadriel Kaplan; martini@ietf.org
Subject: Re: Q on REQ10 from draft-ietf-martini-reqs-02


On Thu, Mar 25, 2010 at 4:10 PM, Elwell, John <john.elwell@siemens-enterpri=
se.com<mailto:john.elwell@siemens-enterprise.com>> wrote:

> Additrional question while rereading, why does the
> requirement only adress intermediary entities on the SSP
> side? It is very likely that corporates deploy SBC like
> devices on the edge too, to protect their network, too fix
> media routing etc. You do not want to disallow that.
[JRE] I thought this question had been answered earlier. Where there is an =
SBC, for example, on the boundary of the enterprise network, this would rep=
resent the PBX. Typically it is that device that will initiate the REGISTER=
 request, for example. So the edge device IS the SIP-PBX - the fact that it=
 might not be the complete PBX, but just an edge device, does not seem to m=
atter.

[HE] I do think it is an unnecessary scoping, why distinguish whether inter=
mediary SIP entities belong to the SSPs or the enterprise? Saying that an e=
nterprise SBC shall do the registration on behalf of the PBX is unnecessari=
ly narrowing down the set of deployments too.

Suggest to rewrite the requirement as:

"REQ10 - The mechanism MUST work in the presence of a sequence of intermedi=
ate SIP entities on the SIP-PBX-to-SSP interface (i.e., between the SIP-PBX=
 and the SSP's domain proxy), where those intermediate SIP entities indicat=
ed during registration they wished to be on the path for future requests to=
wards the registering UA (SIP-PBX)."

This is completely OK, as the martini charter is explicit about that it is =
working an a registration based solution. This is also reflected in REQ3.

BR,
/Hans Erik

--_000_A444A0F8084434499206E78C106220CADE09ABF7MCHP058Aglobala_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.5921" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagTyp=
e><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: MS Mincho;
}
@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: @MS Mincho;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Consolas;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MSONORMAL {
	mso-style-unhide: no; mso-style-qformat: yes; mso-ascii-theme-font: minor-=
latin; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-lat=
in; mso-bidi-theme-font: minor-bidi
}
LI.MSONORMAL {
	mso-style-unhide: no; mso-style-qformat: yes; mso-ascii-theme-font: minor-=
latin; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-lat=
in; mso-bidi-theme-font: minor-bidi
}
DIV.MSONORMAL {
	mso-style-unhide: no; mso-style-qformat: yes; mso-ascii-theme-font: minor-=
latin; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-lat=
in; mso-bidi-theme-font: minor-bidi
}
P.MSOPLAINTEXT {
	mso-style-priority: 99
}
LI.MSOPLAINTEXT {
	mso-style-priority: 99
}
DIV.MSOPLAINTEXT {
	mso-style-priority: 99
}
SPAN.PLAINTEXTCHAR {
	mso-style-unhide: no; mso-style-priority: 99
}
.MSOCHPDEFAULT {
	mso-ascii-theme-font: minor-latin; mso-fareast-theme-font: minor-latin; ms=
o-hansi-theme-font: minor-latin; mso-bidi-theme-font: minor-bidi; mso-defau=
lt-props: yes
}
P.MSONORMAL {
	mso-style-unhide: no; mso-style-qformat: yes; mso-ascii-theme-font: minor-=
latin; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-lat=
in; mso-bidi-theme-font: minor-bidi
}
LI.MSONORMAL {
	mso-style-unhide: no; mso-style-qformat: yes; mso-ascii-theme-font: minor-=
latin; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-lat=
in; mso-bidi-theme-font: minor-bidi
}
DIV.MSONORMAL {
	mso-style-unhide: no; mso-style-qformat: yes; mso-ascii-theme-font: minor-=
latin; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-lat=
in; mso-bidi-theme-font: minor-bidi
}
P.MSOPLAINTEXT {
	mso-style-priority: 99
}
LI.MSOPLAINTEXT {
	mso-style-priority: 99
}
DIV.MSOPLAINTEXT {
	mso-style-priority: 99
}
SPAN.PLAINTEXTCHAR {
	mso-style-unhide: no; mso-style-priority: 99
}
.MSOCHPDEFAULT {
	mso-ascii-theme-font: minor-latin; mso-fareast-theme-font: minor-latin; ms=
o-hansi-theme-font: minor-latin; mso-bidi-theme-font: minor-bidi; mso-defau=
lt-props: yes
}
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
P.MsoPlainText {
	FONT-SIZE: 10.5pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Consolas
}
LI.MsoPlainText {
	FONT-SIZE: 10.5pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Consolas
}
DIV.MsoPlainText {
	FONT-SIZE: 10.5pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Consolas
}
SPAN.PlainTextChar {
	FONT-FAMILY: Consolas
}
SPAN.EmailStyle19 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dblue link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D359434520-25032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Done in my working copy.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D359434520-25032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D359434520-25032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>John</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Hadriel Kaplan=20
  [mailto:HKaplan@acmepacket.com] <BR><B>Sent:</B> 25 March 2010=20
  13:24<BR><B>To:</B> Hans Erik van Elburg; Elwell, John<BR><B>Cc:</B>=20
  martini@ietf.org<BR><B>Subject:</B> RE: Q on REQ10 from=20
  draft-ietf-martini-reqs-02<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Yeah I agree w=
ith=20
  Hans Erik &#8211; no harm in just making it generic.<o:p></o:p></SPAN></F=
ONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">-hadriel<o:p><=
/o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o=
:p></SPAN></FONT></P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: mediu=
m none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt sol=
id; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <DIV>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT=
=20
  face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</=
SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahom=
a">=20
  <st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: url(res://ie=
tag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">Hans Erik van Elburg</st1:PersonName>=20
  [mailto:ietf.hanserik@gmail.com] <BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, March 25, 2010 1:3=
2=20
  PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Elwell,=20
  John<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> <st1:PersonNa=
me=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: url(res://ie=
tag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">Hadriel Kaplan</st1:PersonName>;=20
  martini@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Subject:</SPAN><=
/B> Re:=20
  Q on REQ10 from draft-ietf-martini-reqs-02</SPAN></FONT><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'"><o:p></o:p></SP=
AN></FONT></P></DIV>
  <P class=3DMsoNormal><FONT face=3DCalibri size=3D2><SPAN=20
  style=3D"FONT-SIZE: 11pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DCalibri size=3D2><SPAN=20
  style=3D"FONT-SIZE: 11pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DCalibri size=3D2><SPAN style=3D"FONT-SI=
ZE: 11pt">On=20
  Thu, Mar 25, 2010 at 4:10 PM, Elwell, John &lt;<A=20
  href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-en=
terprise.com</A>&gt;=20
  wrote:<o:p></o:p></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DCalibri size=3D2><SPAN=20
  style=3D"FONT-SIZE: 11pt"><BR>&gt; Additrional question while rereading, =
why=20
  does the<BR>&gt; requirement only adress intermediary entities on the=20
  SSP<BR>&gt; side? It is very likely that corporates deploy SBC like<BR>&g=
t;=20
  devices on the edge too, to protect their network, too fix<BR>&gt; media=
=20
  routing etc. You do not want to disallow=20
  that.<o:p></o:p></SPAN></FONT></P></DIV>
  <BLOCKQUOTE=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: mediu=
m none; PADDING-LEFT: 6pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 4.8pt; BORDER-=
LEFT: #cccccc 1pt solid; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM=
: medium none">
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT face=3DCalibri=
=20
    size=3D2><SPAN style=3D"FONT-SIZE: 11pt">[JRE] I thought this question =
had been=20
    answered earlier. Where there is an SBC, for example, on the boundary o=
f the=20
    enterprise network, this would represent the PBX. Typically it is that=
=20
    device that will initiate the REGISTER request, for example. So the edg=
e=20
    device IS the SIP-PBX - the fact that it might not be the complete PBX,=
 but=20
    just an edge device, does not seem to=20
  matter.<o:p></o:p></SPAN></FONT></P></BLOCKQUOTE>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DCalibri size=3D2><SPAN=20
  style=3D"FONT-SIZE: 11pt"><BR></SPAN></FONT><FONT face=3D"Times New Roman=
"=20
  size=3D3><SPAN style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'">=
<LINK=20
  href=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtm=
lclip1%5C01%5Cclip_themedata.thmx"=20
  rel=3DthemeData><LINK=20
  href=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtm=
lclip1%5C01%5Cclip_colorschememapping.xml"=20
  rel=3DcolorSchemeMapping>[HE] I do think it is an unnecessary scoping, wh=
y=20
  distinguish whether intermediary SIP entities belong to the SSPs or the=20
  enterprise? Saying that an enterprise SBC shall do the registration on be=
half=20
  of the PBX is unnecessarily narrowing down the set of deployments too.=20
  <BR><BR><LINK=20
  href=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtm=
lclip1%5C01%5Cclip_themedata.thmx"=20
  rel=3DthemeData><LINK=20
  href=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtm=
lclip1%5C01%5Cclip_colorschememapping.xml"=20
  rel=3DcolorSchemeMapping>Suggest to rewrite the requirement as:<BR><B><SP=
AN=20
  style=3D"FONT-WEIGHT: bold"><BR>"REQ10 - The mechanism MUST work in the p=
resence=20
  of a sequence of intermediate SIP entities on the SIP-PBX-to-SSP interfac=
e=20
  (i.e., between the SIP-PBX and the SSP's domain proxy), where those=20
  intermediate SIP entities indicated during registration they wished to be=
 on=20
  the path for future requests towards the registering UA (SIP-PBX)."</SPAN=
></B>=20
  <B><SPAN style=3D"FONT-WEIGHT: bold"><BR></SPAN></B><BR>This is completel=
y OK,=20
  as the martini charter is explicit about that it is working an a registra=
tion=20
  based solution. This is also reflected in REQ3.<BR><BR>BR,<BR>/Hans=20
  Erik<o:p></o:p></SPAN></FONT></P></DIV></DIV></DIV></DIV></BLOCKQUOTE></B=
ODY></HTML>

--_000_A444A0F8084434499206E78C106220CADE09ABF7MCHP058Aglobala_--

From HKaplan@acmepacket.com  Thu Mar 25 14:05:32 2010
Return-Path: <HKaplan@acmepacket.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 A5CB23A69B0 for <martini@core3.amsl.com>; Thu, 25 Mar 2010 14:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.426
X-Spam-Level: 
X-Spam-Status: No, score=-0.426 tagged_above=-999 required=5 tests=[AWL=1.043,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 Dba6cUXSDL-Q for <martini@core3.amsl.com>; Thu, 25 Mar 2010 14:05:31 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 87C7D3A6ADD for <martini@ietf.org>; Thu, 25 Mar 2010 14:05:30 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Thu, 25 Mar 2010 17:05:50 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Thu, 25 Mar 2010 17:05:50 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Date: Thu, 25 Mar 2010 17:05:13 -0400
Thread-Topic: [martini] #23: 3.3 unlear whether mentioned issues are tackled or not
Thread-Index: AcrMWxTkBeHyRjJjT56kmXBW3+w0DwAACIAAAACNa9A=
Message-ID: <430FC6BDED356B4C8498F634416644A91A79E923E5@mail>
References: <A444A0F8084434499206E78C106220CADE09ABF2@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CADE09ABF2@MCHP058A.global-ad.net>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #23: 3.3 unlear whether mentioned issues are tackled or not
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: Thu, 25 Mar 2010 21:05:32 -0000

You mean section 3.3.1 and 3.3.2 (not 3.2.1 and 3.2.2).

As section 3.3 says:
   A mechanism for solving the SIP-PBX registration problem
   will not solve these policy issues directly, although when specifying
   the mechanism the opportunity can be taken to highlight the impact of
   such policies.

What we really meant was the Martini was not going to solve the policy issu=
es, but we would document the impact of such policies.

So I recommend we add the following Requirement:
REQ19 - the mechanism's specification SHOULD give guidance or warnings abou=
t how authorization policies may be affected by the mechanism, to address t=
he problems described in section 3.3.

OK?

-hadriel

> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Thursday, March 25, 2010 4:42 PM
> To: Hadriel Kaplan
> Cc: martini@ietf.org
> Subject: FW: [martini] #23: 3.3 unlear whether mentioned issues are
> tackled or not
>=20
> Hadriel,
>=20
> I am forwarding this, as you are not explicitly addressed on the tracker
> message. Please give your opinion on this matter. The issue is that
> sections 3.2.1 and 3.2.2 do not seem relevant to the MARTINI question, an=
d
> are not even backed up by any requirements in section 4 or by any
> mechanism in the gin draft.
>=20
> Thanks,
>=20
> John
>=20
> > -----Original Message-----
> > From: martini issue tracker [mailto:trac@tools.ietf.org]
> > Sent: 25 March 2010 13:38
> > To: Elwell, John
> > Cc: martini@ietf.org
> > Subject: Re: [martini] #23: 3.3 unlear whether mentioned
> > issues are tackled or not
> >
> > #23: 3.3 unlear whether mentioned issues are tackled or not
> > -------------------------------------+------------------------
> > --------------
> >  Reporter:  ietf.hanserik@...          |       Owner:
> > john.elwell@...
> >      Type:  defect                   |      Status:  assigned
> >
> >  Priority:  minor                    |   Milestone:
> > milestone1
> > Component:  reqs                     |     Version:  1.0
> >
> >  Severity:  In WG Last Call          |    Keywords:
> >
> > -------------------------------------+------------------------
> > --------------
> > Changes (by john.elwell@...):
> >
> >   * owner:  =3D> john.elwell@...
> >   * status:  new =3D> assigned
> >
> >
> > Comment:
> >
> >  I am inclined to accept this comment, but the text came from Hadriel
> >  orginally. Hadriel, can you give an opinion whether we should delete
> >  sections 3.3.1 and 3.3.2 (and hence 3.3)?
> >
> > --
> > Ticket URL:
> > <http://trac.tools.ietf.org/wg/martini/trac/ticket/23#comment:1>
> > martini <http://tools.ietf.org/martini/>
> >
> >

From john.elwell@siemens-enterprise.com  Thu Mar 25 14:07:53 2010
Return-Path: <john.elwell@siemens-enterprise.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 94E3B3A6D29 for <martini@core3.amsl.com>; Thu, 25 Mar 2010 14:07:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.271
X-Spam-Level: 
X-Spam-Status: No, score=-0.271 tagged_above=-999 required=5 tests=[AWL=1.198,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 tjtBQ9BS3xAF for <martini@core3.amsl.com>; Thu, 25 Mar 2010 14:07:52 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 40CFC3A6D2B for <martini@ietf.org>; Thu, 25 Mar 2010 14:07:51 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1349419; Thu, 25 Mar 2010 22:08:13 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id CDB7A1EB82AE; Thu, 25 Mar 2010 22:08:13 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Thu, 25 Mar 2010 22:08:14 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Date: Thu, 25 Mar 2010 22:08:07 +0100
Thread-Topic: [martini] #23: 3.3 unlear whether mentioned issues are tackled or not
Thread-Index: AcrMWxTkBeHyRjJjT56kmXBW3+w0DwAACIAAAACNa9AAAG6lsA==
Message-ID: <A444A0F8084434499206E78C106220CADE09AC17@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CADE09ABF2@MCHP058A.global-ad.net> <430FC6BDED356B4C8498F634416644A91A79E923E5@mail>
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79E923E5@mail>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #23: 3.3 unlear whether mentioned issues are tackled or not
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: Thu, 25 Mar 2010 21:07:53 -0000

Yes, I meant 3.3.1 and 3.3.2 (its getting late in the week).

If we say "SHOULD", it would be a desirable, not a requirement, right?

John=20

> -----Original Message-----
> From: Hadriel Kaplan [mailto:HKaplan@acmepacket.com]=20
> Sent: 25 March 2010 14:05
> To: Elwell, John
> Cc: martini@ietf.org
> Subject: RE: [martini] #23: 3.3 unlear whether mentioned=20
> issues are tackled or not
>=20
>=20
> You mean section 3.3.1 and 3.3.2 (not 3.2.1 and 3.2.2).
>=20
> As section 3.3 says:
>    A mechanism for solving the SIP-PBX registration problem
>    will not solve these policy issues directly, although when=20
> specifying
>    the mechanism the opportunity can be taken to highlight=20
> the impact of
>    such policies.
>=20
> What we really meant was the Martini was not going to solve=20
> the policy issues, but we would document the impact of such policies.
>=20
> So I recommend we add the following Requirement:
> REQ19 - the mechanism's specification SHOULD give guidance or=20
> warnings about how authorization policies may be affected by=20
> the mechanism, to address the problems described in section 3.3.
>=20
> OK?
>=20
> -hadriel
>=20
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > Sent: Thursday, March 25, 2010 4:42 PM
> > To: Hadriel Kaplan
> > Cc: martini@ietf.org
> > Subject: FW: [martini] #23: 3.3 unlear whether mentioned issues are
> > tackled or not
> >=20
> > Hadriel,
> >=20
> > I am forwarding this, as you are not explicitly addressed=20
> on the tracker
> > message. Please give your opinion on this matter. The issue is that
> > sections 3.2.1 and 3.2.2 do not seem relevant to the=20
> MARTINI question, and
> > are not even backed up by any requirements in section 4 or by any
> > mechanism in the gin draft.
> >=20
> > Thanks,
> >=20
> > John
> >=20
> > > -----Original Message-----
> > > From: martini issue tracker [mailto:trac@tools.ietf.org]
> > > Sent: 25 March 2010 13:38
> > > To: Elwell, John
> > > Cc: martini@ietf.org
> > > Subject: Re: [martini] #23: 3.3 unlear whether mentioned
> > > issues are tackled or not
> > >
> > > #23: 3.3 unlear whether mentioned issues are tackled or not
> > > -------------------------------------+------------------------
> > > --------------
> > >  Reporter:  ietf.hanserik@...          |       Owner:
> > > john.elwell@...
> > >      Type:  defect                   |      Status:  assigned
> > >
> > >  Priority:  minor                    |   Milestone:
> > > milestone1
> > > Component:  reqs                     |     Version:  1.0
> > >
> > >  Severity:  In WG Last Call          |    Keywords:
> > >
> > > -------------------------------------+------------------------
> > > --------------
> > > Changes (by john.elwell@...):
> > >
> > >   * owner:  =3D> john.elwell@...
> > >   * status:  new =3D> assigned
> > >
> > >
> > > Comment:
> > >
> > >  I am inclined to accept this comment, but the text came=20
> from Hadriel
> > >  orginally. Hadriel, can you give an opinion whether we=20
> should delete
> > >  sections 3.3.1 and 3.3.2 (and hence 3.3)?
> > >
> > > --
> > > Ticket URL:
> > > <http://trac.tools.ietf.org/wg/martini/trac/ticket/23#comment:1>
> > > martini <http://tools.ietf.org/martini/>
> > >
> > >
> =

From root@core3.amsl.com  Thu Mar 25 15:00:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: martini@ietf.org
Delivered-To: martini@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 455993A6944; Thu, 25 Mar 2010 15:00:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100325220002.455993A6944@core3.amsl.com>
Date: Thu, 25 Mar 2010 15:00:02 -0700 (PDT)
Cc: martini@ietf.org
Subject: [martini] I-D Action:draft-ietf-martini-reqs-03.txt
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: Thu, 25 Mar 2010 22:00:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiple AoR reachabiliTy InformatioN Indication Working Group of the IETF.


	Title           : Requirements for multiple address of record (AOR) reachability information in the Session Initiation Protocol (SIP)
	Author(s)       : J. Elwell, H. Kaplan
	Filename        : draft-ietf-martini-reqs-03.txt
	Pages           : 13
	Date            : 2010-03-25

This document states requirements for a standardized SIP registration
mechanism for multiple addresses of record, the mechanism being
suitable for deployment by SIP service providers on a large scale in
support of small to medium sized PBXs.  The requirements are for a
solution that can, as a minimum, support AORs based on E.164 numbers.

This work is being discussed on the martini@ietf.org mailing list.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-martini-reqs-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-martini-reqs-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-03-25144749.I-D@ietf.org>


--NextPart--

From john.elwell@siemens-enterprise.com  Thu Mar 25 15:39:32 2010
Return-Path: <john.elwell@siemens-enterprise.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 57D243A685E for <martini@core3.amsl.com>; Thu, 25 Mar 2010 15:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.257
X-Spam-Level: 
X-Spam-Status: No, score=-0.257 tagged_above=-999 required=5 tests=[AWL=0.985,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 hG7KJdKkpOAz for <martini@core3.amsl.com>; Thu, 25 Mar 2010 15:39:31 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 312FD3A67EF for <martini@ietf.org>; Thu, 25 Mar 2010 15:39:30 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1349926 for martini@ietf.org; Thu, 25 Mar 2010 23:39:49 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id D1B191EB82AB for <martini@ietf.org>; Thu, 25 Mar 2010 23:39:49 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Thu, 25 Mar 2010 23:39:49 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "martini@ietf.org" <martini@ietf.org>
Date: Thu, 25 Mar 2010 23:39:47 +0100
Thread-Topic: [martini] I-D Action:draft-ietf-martini-reqs-03.txt
Thread-Index: AcrMZp1jNBxAYS4/TO6sLAgE8OeAOAABMF5g
Message-ID: <A444A0F8084434499206E78C106220CADE09AC6C@MCHP058A.global-ad.net>
References: <20100325220002.455993A6944@core3.amsl.com>
In-Reply-To: <20100325220002.455993A6944@core3.amsl.com>
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
Subject: Re: [martini] I-D Action:draft-ietf-martini-reqs-03.txt
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: Thu, 25 Mar 2010 22:39:32 -0000

Changes from 02:

- Addition of explanation to section 1 as to why we focus on E.164-based AO=
Rs
- Rewording in REQ10
- Deletion of REQ17
- Deletion of old DES4 (text moved, with slight changes, to start of that s=
ection)

John

> -----Original Message-----
> From: martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] On Behalf Of=20
> Internet-Drafts@ietf.org
> Sent: 25 March 2010 15:00
> To: i-d-announce@ietf.org
> Cc: martini@ietf.org
> Subject: [martini] I-D Action:draft-ietf-martini-reqs-03.txt
>=20
> A New Internet-Draft is available from the on-line=20
> Internet-Drafts directories.
> This draft is a work item of the Multiple AoR reachabiliTy=20
> InformatioN Indication Working Group of the IETF.
>=20
>=20
> 	Title           : Requirements for multiple address of=20
> record (AOR) reachability information in the Session=20
> Initiation Protocol (SIP)
> 	Author(s)       : J. Elwell, H. Kaplan
> 	Filename        : draft-ietf-martini-reqs-03.txt
> 	Pages           : 13
> 	Date            : 2010-03-25
>=20
> This document states requirements for a standardized SIP registration
> mechanism for multiple addresses of record, the mechanism being
> suitable for deployment by SIP service providers on a large scale in
> support of small to medium sized PBXs.  The requirements are for a
> solution that can, as a minimum, support AORs based on E.164 numbers.
>=20
> This work is being discussed on the martini@ietf.org mailing list.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-martini-reqs-03.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> =

From ietf.hanserik@gmail.com  Fri Mar 26 01:54:18 2010
Return-Path: <ietf.hanserik@gmail.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 700C73A689B for <martini@core3.amsl.com>; Fri, 26 Mar 2010 01:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.021
X-Spam-Level: 
X-Spam-Status: No, score=0.021 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 Tj8Yk4m6-mPl for <martini@core3.amsl.com>; Fri, 26 Mar 2010 01:54:16 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by core3.amsl.com (Postfix) with ESMTP id B1AE33A677C for <martini@ietf.org>; Fri, 26 Mar 2010 01:54:12 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 4so869476eyf.51 for <martini@ietf.org>; Fri, 26 Mar 2010 01:54:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=tYzZ1q8FHRua0QoYcq7HKdRq8oz7mKH7ju2prqya+Js=; b=IFlll+QWGiiWhUkMRuI0sDmRpf3XERG7fJnLPlv+/kmNPZhH48na+M4N66D1wUaxR2 g04YUH/eW8HEuXMangp2gsybWFNDOruUt3VowfZUuk0QnB3+FNyWO+f7jWnezY4wKaNl 4BqFfVfVAn1wyvleiR8JUKMzOrPQY+Pob9j4g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=uVzcJ0M9IeaVJLWe6whCjMd1zc4Z+RFjWxhu/vyWz4jeCu435I1I28YtqUp525vPrM ZLJgY8ejFc7nxOWOtDY6iZC6stfuempC1oY8EpRvGY0HnHeRPebuzDRswZP7o9s24zV3 VhAWngpwnC2fE+vO+9xTlhghOnvKuxHHe5T+M=
MIME-Version: 1.0
Received: by 10.213.6.193 with HTTP; Fri, 26 Mar 2010 01:54:32 -0700 (PDT)
In-Reply-To: <074.d5b79c9d002d1d9a8fbdcbdc4568c32c@tools.ietf.org>
References: <065.606d2b6083a21b5a6fdc3bf7754c2d3e@tools.ietf.org> <074.d5b79c9d002d1d9a8fbdcbdc4568c32c@tools.ietf.org>
Date: Fri, 26 Mar 2010 09:54:32 +0100
Received: by 10.213.44.137 with SMTP id a9mr50808ebf.67.1269593672764; Fri, 26  Mar 2010 01:54:32 -0700 (PDT)
Message-ID: <x2w9ae56b1e1003260154v9200814eqdd5d79912df08704@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: trac@localhost.amsl.com
Content-Type: multipart/alternative; boundary=0014852f124adfcf270482b04fb7
Cc: martini@ietf.org
Subject: Re: [martini] #20: Section 3.1.2 does not decscribe an issue
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: Fri, 26 Mar 2010 08:54:18 -0000

--0014852f124adfcf270482b04fb7
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

As far as I understand the reason why PAU was important is that the
edge-proxy can use this information when verifying P-Preferred-Identity,
P-Asserted-Identity.

I dont see what the PBX should do with this information. And no use for the
pbx has been specified anywhere. And I guess that nobody stumbled over this
as an issue in practical solutions.

So it is not an issue. I agree to disagree.

/Hans Erik van Elburg


On Thu, Mar 25, 2010 at 9:14 PM, martini issue tracker
<trac@tools.ietf.org>wrote:

> #20: Section 3.1.2 does not decscribe an issue
>
> -------------------------------------+-----------------------------------=
---
>  Reporter:  ietf.hanserik@=85          |       Owner:  john.elwell@=85
>     Type:  defect                   |      Status:  assigned
>  Priority:  minor                    |   Milestone:  milestone1
> Component:  reqs                     |     Version:  1.0
>  Severity:  In WG Last Call          |    Keywords:
>
> -------------------------------------+-----------------------------------=
---
> Changes (by john.elwell@=85):
>
>  * owner:  =3D> john.elwell@=85
>  * status:  new =3D> assigned
>
>
> Comment:
>
>  I disagree that it is not an issue if you receive unexpected PAU. If the
>  PBX receives unexpected values, what does it do with them? They clearly
>  will not map to any PBX extensions. Even worse, if the PAU omits certain
>  values the PBX expects, what action does the PBX take? Unless others spe=
ak
>  up soon in favour of making any change to 3.1.2, I will close this as
>  'won't fix'.
>
> --
> Ticket URL: <
> http://trac.tools.ietf.org/wg/martini/trac/ticket/20#comment:1>
> martini <http://tools.ietf.org/martini/>
>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>

--0014852f124adfcf270482b04fb7
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

As far as I understand the reason why PAU was important is that the edge-pr=
oxy can use this information when verifying P-Preferred-Identity, P-Asserte=
d-Identity.<br><br>I dont see what the PBX should do with this information.=
 And no use for the pbx has been specified anywhere. And I guess that nobod=
y stumbled over this as an issue in practical solutions.<br>
<br>So it is not an issue. I agree to disagree.<br><br clear=3D"all">/Hans =
Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Thu, Mar 25, 2010 at 9:14 PM, martini=
 issue tracker <span dir=3D"ltr">&lt;<a href=3D"mailto:trac@tools.ietf.org"=
>trac@tools.ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 20=
4, 204); padding-left: 1ex;">
<div class=3D"im">#20: Section 3.1.2 does not decscribe an issue<br>
-------------------------------------+-------------------------------------=
-<br>
</div>=A0Reporter: =A0ietf.hanserik@=85 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0 Ow=
ner: =A0john.elwell@=85<br>
 =A0 =A0 Type: =A0defect =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 =A0S=
tatus: =A0assigned<br>
<div class=3D"im">=A0Priority: =A0minor =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0| =A0 Milestone: =A0milestone1<br>
Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 Versio=
n: =A01.0<br>
=A0Severity: =A0In WG Last Call =A0 =A0 =A0 =A0 =A0| =A0 =A0Keywords:<br>
-------------------------------------+-------------------------------------=
-<br>
</div><div class=3D"im">Changes (by john.elwell@=85):<br>
<br>
 =A0* owner: =A0=3D&gt; john.elwell@=85<br>
 =A0* status: =A0new =3D&gt; assigned<br>
<br>
<br>
Comment:<br>
<br>
</div>=A0I disagree that it is not an issue if you receive unexpected PAU. =
If the<br>
=A0PBX receives unexpected values, what does it do with them? They clearly<=
br>
=A0will not map to any PBX extensions. Even worse, if the PAU omits certain=
<br>
=A0values the PBX expects, what action does the PBX take? Unless others spe=
ak<br>
=A0up soon in favour of making any change to 3.1.2, I will close this as<br=
>
=A0&#39;won&#39;t fix&#39;.<br>
<font color=3D"#888888"><br>
--<br>
Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticke=
t/20#comment:1" target=3D"_blank">http://trac.tools.ietf.org/wg/martini/tra=
c/ticket/20#comment:1</a>&gt;<br>
</font><div class=3D"im">martini &lt;<a href=3D"http://tools.ietf.org/marti=
ni/" target=3D"_blank">http://tools.ietf.org/martini/</a>&gt;<br>
<br>
</div><div><div></div><div class=3D"h5">___________________________________=
____________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
</div></div></blockquote></div><br>

--0014852f124adfcf270482b04fb7--

From ietf.hanserik@gmail.com  Fri Mar 26 02:20:48 2010
Return-Path: <ietf.hanserik@gmail.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 D3EAE3A677C for <martini@core3.amsl.com>; Fri, 26 Mar 2010 02:20:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.055
X-Spam-Level: 
X-Spam-Status: No, score=-0.055 tagged_above=-999 required=5 tests=[AWL=1.413,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 rP8yd1Vd16sL for <martini@core3.amsl.com>; Fri, 26 Mar 2010 02:20:44 -0700 (PDT)
Received: from mail-ew0-f221.google.com (mail-ew0-f221.google.com [209.85.219.221]) by core3.amsl.com (Postfix) with ESMTP id C8CAE3A67B3 for <martini@ietf.org>; Fri, 26 Mar 2010 02:20:43 -0700 (PDT)
Received: by ewy21 with SMTP id 21so2091909ewy.5 for <martini@ietf.org>; Fri, 26 Mar 2010 02:21:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=77xQ+lrkt4VnCJ8LYjT68uFjgyzXi90bOsZr8DpAnZo=; b=mp8bBmuctcjEqv8pG9QJQR42SOvA0BIKyK1rgH3pvQ+3eQyU+80S3m3pr6s6JGyRJw C5gqSSeBD19MMBUYETCUuQI3hpckSGjpOL4xcf9yHnx1q6SR2SRepeayvJd61c7kMHlx Xdtl/ORcA++XR9G1c7RbuxV6oCaqDtmDCyv44=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=HcD0LnNKpDN48+yYfuDY01PwNakMrUILxHQUrL8A2gLT8QDIaHVmaD049R4Be6jSKm ztudXqBJXq1Rofc4eszAO9BENA7FNIpw3RLuJw0DLxkgOmP1xDC+/BHtVjvuygeSnTIH D1kIr32MV2zs/WqrKHNaVERBiBlN1ch4nCA3w=
MIME-Version: 1.0
Received: by 10.213.6.193 with HTTP; Fri, 26 Mar 2010 02:21:03 -0700 (PDT)
In-Reply-To: <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org>
Date: Fri, 26 Mar 2010 10:21:03 +0100
Received: by 10.213.37.142 with SMTP id x14mr467035ebd.16.1269595263601; Fri,  26 Mar 2010 02:21:03 -0700 (PDT)
Message-ID: <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: trac@localhost.amsl.com
Content-Type: multipart/alternative; boundary=0016362571d1b20f5f0482b0aee6
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Fri, 26 Mar 2010 09:20:48 -0000

--0016362571d1b20f5f0482b0aee6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Then you should rephrase to what the real issue is:
"

Request-URI vs. loose-route acceptance

Some IP-PBX do not implement international standards or SIP profiles for SI=
P
trunking. As a consequence some SIP-PBXs expect that inbound SIP requests
from the SSP will have the registered Contact-URI in the Request-URI, and
thus not interoperate with the loose-route scheme of 3GPP and ETSI. Other
SIP-PBXs are fine with the Request-URI being the intended target, but canno=
t
handle receiving a Route header field identifying their registered
Contact-URI as a loose-route entry."


Is this an issue, yes. Does introducing yet another profile help? No.

/Hans Erik van Elburg

On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
<trac@tools.ietf.org>wrote:

> #21: 3.2.2 describes an issue with some PBX
>
> -------------------------------------+-----------------------------------=
---
>  Reporter:  ietf.hanserik@=85          |        Owner:
>      Type:  defect                   |       Status:  closed
>  Priority:  minor                    |    Milestone:  milestone1
> Component:  reqs                     |      Version:  1.0
>  Severity:  In WG Last Call          |   Resolution:  invalid
>  Keywords:                           |
>
> -------------------------------------+-----------------------------------=
---
> Changes (by john.elwell@=85):
>
>  * status:  new =3D> closed
>  * resolution:  =3D> invalid
>
>
> Comment:
>
>  The text of 3.2.2 just underlines the fact that there are different
>  implementations around. A PBX that expects the loose route mechanism to =
be
>  used would fail to interwork with SSPs using a different mechanism (e.g.=
,
>  SIPconnect 1.0), and a PBX not expecting the loose route mechanism to be
>  used would fail to interwork with a loose route implementation (e.g.,
>  ETSI/3GPP). Hence the urgent need for a standard.
>
> --
> Ticket URL: <
> http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
> martini <http://tools.ietf.org/martini/>
>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>

--0016362571d1b20f5f0482b0aee6
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<br>Then you should rephrase to what the real issue is:<br>&quot;<br><meta =
http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8"><meta na=
me=3D"ProgId" content=3D"Word.Document"><meta name=3D"Generator" content=3D=
"Microsoft Word 12"><meta name=3D"Originator" content=3D"Microsoft Word 12"=
><link rel=3D"File-List" href=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOC=
ALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link rel=3D"themeD=
ata" href=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5CTemp%5Cmso=
htmlclip1%5C01%5Cclip_themedata.thmx"><link rel=3D"colorSchemeMapping" href=
=3D"file:///C:%5CDOCUME%7E1%5CDTC102%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1=
%5C01%5Cclip_colorschememapping.xml"><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-alt:"Calisto MT";
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-1610611985 1107304683 0 0 159 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-alt:"Arial Rounded MT Bold";
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1610611985 1073750139 0 0 159 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;
	mso-fareast-language:EN-US;}
span.EmailStyle15
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Arial","sans-serif";
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;
	mso-fareast-language:EN-US;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; font-family: &quot;A=
rial&quot;,&quot;sans-serif&quot;;">Request-URI vs. loose-route acceptance<=
/span></p>

<br>Some IP-PBX do not implement international standards or SIP profiles fo=
r SIP trunking. As a consequence some SIP-PBXs expect that inbound SIP requ=
ests from the SSP will have the registered Contact-URI in the Request-URI, =
and thus not interoperate with the loose-route scheme of 3GPP and ETSI.  Ot=
her SIP-PBXs are fine with the Request-URI being the intended target, but c=
annot handle receiving a Route header field identifying their registered Co=
ntact-URI as a loose-route entry.&quot;<br>
<br><br>Is this an issue, yes. Does introducing yet another profile help? N=
o.<br><br>/Hans Erik van Elburg<br>
<br><div class=3D"gmail_quote">On Thu, Mar 25, 2010 at 9:22 PM, martini iss=
ue tracker <span dir=3D"ltr">&lt;<a href=3D"mailto:trac@tools.ietf.org">tra=
c@tools.ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 2=
04); padding-left: 1ex;">
<div class=3D"im">#21: 3.2.2 describes an issue with some PBX<br>
-------------------------------------+-------------------------------------=
-<br>
=A0Reporter: =A0ietf.hanserik@=85 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0Owner=
:<br>
</div> =A0 =A0 Type: =A0defect =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =
=A0 =A0 Status: =A0closed<br>
<div class=3D"im">=A0Priority: =A0minor =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0| =A0 =A0Milestone: =A0milestone1<br>
Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 =A0Ver=
sion: =A01.0<br>
</div><div class=3D"im">=A0Severity: =A0In WG Last Call =A0 =A0 =A0 =A0 =A0=
| =A0 Resolution: =A0invalid<br>
=A0Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
-------------------------------------+-------------------------------------=
-<br>
Changes (by john.elwell@=85):<br>
<br>
 =A0* status: =A0new =3D&gt; closed<br>
 =A0* resolution: =A0=3D&gt; invalid<br>
<br>
<br>
Comment:<br>
<br>
</div>=A0The text of 3.2.2 just underlines the fact that there are differen=
t<br>
=A0implementations around. A PBX that expects the loose route mechanism to =
be<br>
=A0used would fail to interwork with SSPs using a different mechanism (e.g.=
,<br>
=A0SIPconnect 1.0), and a PBX not expecting the loose route mechanism to be=
<br>
=A0used would fail to interwork with a loose route implementation (e.g.,<br=
>
=A0ETSI/3GPP). Hence the urgent need for a standard.<br>
<font color=3D"#888888"><br>
--<br>
Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticke=
t/21#comment:1" target=3D"_blank">http://trac.tools.ietf.org/wg/martini/tra=
c/ticket/21#comment:1</a>&gt;<br>
</font><div class=3D"im">martini &lt;<a href=3D"http://tools.ietf.org/marti=
ni/" target=3D"_blank">http://tools.ietf.org/martini/</a>&gt;<br>
<br>
</div><div><div></div><div class=3D"h5">___________________________________=
____________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
</div></div></blockquote></div><br>

--0016362571d1b20f5f0482b0aee6--

From ietf.hanserik@gmail.com  Fri Mar 26 02:30:59 2010
Return-Path: <ietf.hanserik@gmail.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 595403A676A for <martini@core3.amsl.com>; Fri, 26 Mar 2010 02:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.408
X-Spam-Level: 
X-Spam-Status: No, score=-0.408 tagged_above=-999 required=5 tests=[AWL=1.060,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 LBjwY9wQZxzA for <martini@core3.amsl.com>; Fri, 26 Mar 2010 02:30:58 -0700 (PDT)
Received: from mail-ew0-f221.google.com (mail-ew0-f221.google.com [209.85.219.221]) by core3.amsl.com (Postfix) with ESMTP id 3523A3A6A3F for <martini@ietf.org>; Fri, 26 Mar 2010 02:30:45 -0700 (PDT)
Received: by ewy21 with SMTP id 21so2094683ewy.5 for <martini@ietf.org>; Fri, 26 Mar 2010 02:31:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=0FjqsW7MFKgG33djUBnYqIXpjG6HZnsANcj9dB2scc0=; b=ijTYcw9+g0HmVa7duSGy00uTlqIayJzyt0rGkmCFsnO3PyKryKOXt5KdEkC91AoUgV /na9EyIFNz3RhYbtZkAkyJ+XWYigF/daUNGpombjbxdFRPbA+UX8LLRnThnDMkLpKZdJ uKbEfADl3jcHPi7sSaOn/MX7b5Wezt1ZsHi4c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=jXA/4eFjfwd7FMBaBCkEhWEcH1jRqmPfX6eHeb8bDljaxfyHzxr5vB1mNhS5D7lko/ WUc6JICHTAYh98EV5eisOxr3EFTF+hM8Bv+3rKYYA/hKAnEj/yULlL+AEgC7ah0ucEk2 pZz/pxQiYAXhqv7wX7pWZFZK2GqSz4tLRCbhU=
MIME-Version: 1.0
Received: by 10.213.6.193 with HTTP; Fri, 26 Mar 2010 02:31:04 -0700 (PDT)
In-Reply-To: <A444A0F8084434499206E78C106220CADE09AC17@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CADE09ABF2@MCHP058A.global-ad.net> <430FC6BDED356B4C8498F634416644A91A79E923E5@mail> <A444A0F8084434499206E78C106220CADE09AC17@MCHP058A.global-ad.net>
Date: Fri, 26 Mar 2010 10:31:04 +0100
Received: by 10.213.81.204 with SMTP id y12mr81629ebk.47.1269595864818; Fri,  26 Mar 2010 02:31:04 -0700 (PDT)
Message-ID: <g2o9ae56b1e1003260231ld26d7f5bm215ac11d6241580b@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Content-Type: multipart/alternative; boundary=00c09f8c225087e8ca0482b0d209
Cc: "martini@ietf.org" <martini@ietf.org>, Hadriel Kaplan <HKaplan@acmepacket.com>
Subject: Re: [martini] #23: 3.3 unlear whether mentioned issues are tackled or not
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: Fri, 26 Mar 2010 09:30:59 -0000

--00c09f8c225087e8ca0482b0d209
Content-Type: text/plain; charset=ISO-8859-1

It is a requirement, that you MUST have really good reasons for not to
comply with. See RFC2119. If you keep the issues in the doc and hence agree
that they are issues then I think it will be hard to find a good reason.

I think that it is good to have a requirement like that. But does this mean
that the specification should also describe impacts on PBX outbound calls to
the SSP over the SIP trunk? Is it only authentication/identification that
need to be looked at?

BR,
/Hans Erik van Elburg

On Thu, Mar 25, 2010 at 10:08 PM, Elwell, John <
john.elwell@siemens-enterprise.com> wrote:

> Yes, I meant 3.3.1 and 3.3.2 (its getting late in the week).
>
> If we say "SHOULD", it would be a desirable, not a requirement, right?
>
> John
>
> > -----Original Message-----
> > From: Hadriel Kaplan [mailto:HKaplan@acmepacket.com]
> > Sent: 25 March 2010 14:05
> > To: Elwell, John
> > Cc: martini@ietf.org
> > Subject: RE: [martini] #23: 3.3 unlear whether mentioned
> > issues are tackled or not
> >
> >
> > You mean section 3.3.1 and 3.3.2 (not 3.2.1 and 3.2.2).
> >
> > As section 3.3 says:
> >    A mechanism for solving the SIP-PBX registration problem
> >    will not solve these policy issues directly, although when
> > specifying
> >    the mechanism the opportunity can be taken to highlight
> > the impact of
> >    such policies.
> >
> > What we really meant was the Martini was not going to solve
> > the policy issues, but we would document the impact of such policies.
> >
> > So I recommend we add the following Requirement:
> > REQ19 - the mechanism's specification SHOULD give guidance or
> > warnings about how authorization policies may be affected by
> > the mechanism, to address the problems described in section 3.3.
> >
> > OK?
> >
> > -hadriel
> >
> > > -----Original Message-----
> > > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > > Sent: Thursday, March 25, 2010 4:42 PM
> > > To: Hadriel Kaplan
> > > Cc: martini@ietf.org
> > > Subject: FW: [martini] #23: 3.3 unlear whether mentioned issues are
> > > tackled or not
> > >
> > > Hadriel,
> > >
> > > I am forwarding this, as you are not explicitly addressed
> > on the tracker
> > > message. Please give your opinion on this matter. The issue is that
> > > sections 3.2.1 and 3.2.2 do not seem relevant to the
> > MARTINI question, and
> > > are not even backed up by any requirements in section 4 or by any
> > > mechanism in the gin draft.
> > >
> > > Thanks,
> > >
> > > John
> > >
> > > > -----Original Message-----
> > > > From: martini issue tracker [mailto:trac@tools.ietf.org]
> > > > Sent: 25 March 2010 13:38
> > > > To: Elwell, John
> > > > Cc: martini@ietf.org
> > > > Subject: Re: [martini] #23: 3.3 unlear whether mentioned
> > > > issues are tackled or not
> > > >
> > > > #23: 3.3 unlear whether mentioned issues are tackled or not
> > > > -------------------------------------+------------------------
> > > > --------------
> > > >  Reporter:  ietf.hanserik@...          |       Owner:
> > > > john.elwell@...
> > > >      Type:  defect                   |      Status:  assigned
> > > >
> > > >  Priority:  minor                    |   Milestone:
> > > > milestone1
> > > > Component:  reqs                     |     Version:  1.0
> > > >
> > > >  Severity:  In WG Last Call          |    Keywords:
> > > >
> > > > -------------------------------------+------------------------
> > > > --------------
> > > > Changes (by john.elwell@...):
> > > >
> > > >   * owner:  => john.elwell@...
> > > >   * status:  new => assigned
> > > >
> > > >
> > > > Comment:
> > > >
> > > >  I am inclined to accept this comment, but the text came
> > from Hadriel
> > > >  orginally. Hadriel, can you give an opinion whether we
> > should delete
> > > >  sections 3.3.1 and 3.3.2 (and hence 3.3)?
> > > >
> > > > --
> > > > Ticket URL:
> > > > <http://trac.tools.ietf.org/wg/martini/trac/ticket/23#comment:1>
> > > > martini <http://tools.ietf.org/martini/>
> > > >
> > > >
> >
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>

--00c09f8c225087e8ca0482b0d209
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It is a requirement, that you MUST have really good reasons for not to comp=
ly with. See RFC2119. If you keep the issues in the doc and hence agree tha=
t they are issues then I think it will be hard to find a good reason.<br>
<br>I think that it is good to have a requirement like that. But does this =
mean that the specification should also describe impacts on PBX outbound ca=
lls to the SSP over the SIP trunk? Is it only authentication/identification=
 that need to be looked at?<br>
<br>BR,<br clear=3D"all">/Hans Erik van Elburg<br><br><div class=3D"gmail_q=
uote">On Thu, Mar 25, 2010 at 10:08 PM, Elwell, John <span dir=3D"ltr">&lt;=
<a href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-e=
nterprise.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Yes, I meant 3.3.=
1 and 3.3.2 (its getting late in the week).<br>
<br>
If we say &quot;SHOULD&quot;, it would be a desirable, not a requirement, r=
ight?<br>
<font color=3D"#888888"><br>
John<br>
</font><div class=3D"im"><br>
&gt; -----Original Message-----<br>
&gt; From: Hadriel Kaplan [mailto:<a href=3D"mailto:HKaplan@acmepacket.com"=
>HKaplan@acmepacket.com</a>]<br>
&gt; Sent: 25 March 2010 14:05<br>
&gt; To: Elwell, John<br>
&gt; Cc: <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
</div><div><div></div><div class=3D"h5">&gt; Subject: RE: [martini] #23: 3.=
3 unlear whether mentioned<br>
&gt; issues are tackled or not<br>
&gt;<br>
&gt;<br>
&gt; You mean section 3.3.1 and 3.3.2 (not 3.2.1 and 3.2.2).<br>
&gt;<br>
&gt; As section 3.3 says:<br>
&gt; =A0 =A0A mechanism for solving the SIP-PBX registration problem<br>
&gt; =A0 =A0will not solve these policy issues directly, although when<br>
&gt; specifying<br>
&gt; =A0 =A0the mechanism the opportunity can be taken to highlight<br>
&gt; the impact of<br>
&gt; =A0 =A0such policies.<br>
&gt;<br>
&gt; What we really meant was the Martini was not going to solve<br>
&gt; the policy issues, but we would document the impact of such policies.<=
br>
&gt;<br>
&gt; So I recommend we add the following Requirement:<br>
&gt; REQ19 - the mechanism&#39;s specification SHOULD give guidance or<br>
&gt; warnings about how authorization policies may be affected by<br>
&gt; the mechanism, to address the problems described in section 3.3.<br>
&gt;<br>
&gt; OK?<br>
&gt;<br>
&gt; -hadriel<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: Elwell, John [mailto:<a href=3D"mailto:john.elwell@siemens-=
enterprise.com">john.elwell@siemens-enterprise.com</a>]<br>
&gt; &gt; Sent: Thursday, March 25, 2010 4:42 PM<br>
&gt; &gt; To: Hadriel Kaplan<br>
&gt; &gt; Cc: <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; &gt; Subject: FW: [martini] #23: 3.3 unlear whether mentioned issues a=
re<br>
&gt; &gt; tackled or not<br>
&gt; &gt;<br>
&gt; &gt; Hadriel,<br>
&gt; &gt;<br>
&gt; &gt; I am forwarding this, as you are not explicitly addressed<br>
&gt; on the tracker<br>
&gt; &gt; message. Please give your opinion on this matter. The issue is th=
at<br>
&gt; &gt; sections 3.2.1 and 3.2.2 do not seem relevant to the<br>
&gt; MARTINI question, and<br>
&gt; &gt; are not even backed up by any requirements in section 4 or by any=
<br>
&gt; &gt; mechanism in the gin draft.<br>
&gt; &gt;<br>
&gt; &gt; Thanks,<br>
&gt; &gt;<br>
&gt; &gt; John<br>
&gt; &gt;<br>
&gt; &gt; &gt; -----Original Message-----<br>
&gt; &gt; &gt; From: martini issue tracker [mailto:<a href=3D"mailto:trac@t=
ools.ietf.org">trac@tools.ietf.org</a>]<br>
&gt; &gt; &gt; Sent: 25 March 2010 13:38<br>
&gt; &gt; &gt; To: Elwell, John<br>
&gt; &gt; &gt; Cc: <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a>=
<br>
&gt; &gt; &gt; Subject: Re: [martini] #23: 3.3 unlear whether mentioned<br>
&gt; &gt; &gt; issues are tackled or not<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; #23: 3.3 unlear whether mentioned issues are tackled or not<=
br>
&gt; &gt; &gt; -------------------------------------+----------------------=
--<br>
&gt; &gt; &gt; --------------<br>
&gt; &gt; &gt; =A0Reporter: =A0ietf.hanserik@... =A0 =A0 =A0 =A0 =A0| =A0 =
=A0 =A0 Owner:<br>
&gt; &gt; &gt; john.elwell@...<br>
&gt; &gt; &gt; =A0 =A0 =A0Type: =A0defect =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 | =A0 =A0 =A0Status: =A0assigned<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; =A0Priority: =A0minor =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0| =A0 Milestone:<br>
&gt; &gt; &gt; milestone1<br>
&gt; &gt; &gt; Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |=
 =A0 =A0 Version: =A01.0<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; =A0Severity: =A0In WG Last Call =A0 =A0 =A0 =A0 =A0| =A0 =A0=
Keywords:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; -------------------------------------+----------------------=
--<br>
&gt; &gt; &gt; --------------<br>
&gt; &gt; &gt; Changes (by john.elwell@...):<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; =A0 * owner: =A0=3D&gt; john.elwell@...<br>
&gt; &gt; &gt; =A0 * status: =A0new =3D&gt; assigned<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Comment:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; =A0I am inclined to accept this comment, but the text came<b=
r>
&gt; from Hadriel<br>
&gt; &gt; &gt; =A0orginally. Hadriel, can you give an opinion whether we<br=
>
&gt; should delete<br>
&gt; &gt; &gt; =A0sections 3.3.1 and 3.3.2 (and hence 3.3)?<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; --<br>
&gt; &gt; &gt; Ticket URL:<br>
&gt; &gt; &gt; &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/trac/ti=
cket/23#comment:1" target=3D"_blank">http://trac.tools.ietf.org/wg/martini/=
trac/ticket/23#comment:1</a>&gt;<br>
&gt; &gt; &gt; martini &lt;<a href=3D"http://tools.ietf.org/martini/" targe=
t=3D"_blank">http://tools.ietf.org/martini/</a>&gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt;<br>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
</div></div></blockquote></div><br>

--00c09f8c225087e8ca0482b0d209--

From john.elwell@siemens-enterprise.com  Fri Mar 26 12:59:25 2010
Return-Path: <john.elwell@siemens-enterprise.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 EAD7D3A6B65 for <martini@core3.amsl.com>; Fri, 26 Mar 2010 12:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.406
X-Spam-Level: 
X-Spam-Status: No, score=-0.406 tagged_above=-999 required=5 tests=[AWL=1.062,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 7FqCPpPuxFnB for <martini@core3.amsl.com>; Fri, 26 Mar 2010 12:59:24 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id E22BD3A68B3 for <martini@ietf.org>; Fri, 26 Mar 2010 12:59:23 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1363865; Fri, 26 Mar 2010 20:59:46 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id 7C02723F0296; Fri, 26 Mar 2010 20:59:46 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Fri, 26 Mar 2010 20:59:47 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>
Date: Fri, 26 Mar 2010 20:59:44 +0100
Thread-Topic: [martini] #23: 3.3 unlear whether mentioned issues are tackled or 	not
Thread-Index: AcrMxw7rJ0fOWA97Ty6qT/s8772ukgAV8Hzg
Message-ID: <A444A0F8084434499206E78C106220CADE11B373@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CADE09ABF2@MCHP058A.global-ad.net> <430FC6BDED356B4C8498F634416644A91A79E923E5@mail> <A444A0F8084434499206E78C106220CADE09AC17@MCHP058A.global-ad.net> <g2o9ae56b1e1003260231ld26d7f5bm215ac11d6241580b@mail.gmail.com>
In-Reply-To: <g2o9ae56b1e1003260231ld26d7f5bm215ac11d6241580b@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A444A0F8084434499206E78C106220CADE11B373MCHP058Aglobala_"
MIME-Version: 1.0
Cc: "martini@ietf.org" <martini@ietf.org>, Hadriel Kaplan <HKaplan@acmepacket.com>
Subject: Re: [martini] #23: 3.3 unlear whether mentioned issues are tackled or not
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: Fri, 26 Mar 2010 19:59:26 -0000

--_000_A444A0F8084434499206E78C106220CADE11B373MCHP058Aglobala_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I can accept MUST ( a requirement) or SHOULD (a desirable). Other opinions?

John

________________________________
From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
Sent: 26 March 2010 02:31
To: Elwell, John
Cc: Hadriel Kaplan; martini@ietf.org
Subject: Re: [martini] #23: 3.3 unlear whether mentioned issues are tackled=
 or not

It is a requirement, that you MUST have really good reasons for not to comp=
ly with. See RFC2119. If you keep the issues in the doc and hence agree tha=
t they are issues then I think it will be hard to find a good reason.

I think that it is good to have a requirement like that. But does this mean=
 that the specification should also describe impacts on PBX outbound calls =
to the SSP over the SIP trunk? Is it only authentication/identification tha=
t need to be looked at?

BR,
/Hans Erik van Elburg

On Thu, Mar 25, 2010 at 10:08 PM, Elwell, John <john.elwell@siemens-enterpr=
ise.com<mailto:john.elwell@siemens-enterprise.com>> wrote:
Yes, I meant 3.3.1 and 3.3.2 (its getting late in the week).

If we say "SHOULD", it would be a desirable, not a requirement, right?

John

> -----Original Message-----
> From: Hadriel Kaplan [mailto:HKaplan@acmepacket.com<mailto:HKaplan@acmepa=
cket.com>]
> Sent: 25 March 2010 14:05
> To: Elwell, John
> Cc: martini@ietf.org<mailto:martini@ietf.org>
> Subject: RE: [martini] #23: 3.3 unlear whether mentioned
> issues are tackled or not
>
>
> You mean section 3.3.1 and 3.3.2 (not 3.2.1 and 3.2.2).
>
> As section 3.3 says:
>    A mechanism for solving the SIP-PBX registration problem
>    will not solve these policy issues directly, although when
> specifying
>    the mechanism the opportunity can be taken to highlight
> the impact of
>    such policies.
>
> What we really meant was the Martini was not going to solve
> the policy issues, but we would document the impact of such policies.
>
> So I recommend we add the following Requirement:
> REQ19 - the mechanism's specification SHOULD give guidance or
> warnings about how authorization policies may be affected by
> the mechanism, to address the problems described in section 3.3.
>
> OK?
>
> -hadriel
>
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com<mailto:jo=
hn.elwell@siemens-enterprise.com>]
> > Sent: Thursday, March 25, 2010 4:42 PM
> > To: Hadriel Kaplan
> > Cc: martini@ietf.org<mailto:martini@ietf.org>
> > Subject: FW: [martini] #23: 3.3 unlear whether mentioned issues are
> > tackled or not
> >
> > Hadriel,
> >
> > I am forwarding this, as you are not explicitly addressed
> on the tracker
> > message. Please give your opinion on this matter. The issue is that
> > sections 3.2.1 and 3.2.2 do not seem relevant to the
> MARTINI question, and
> > are not even backed up by any requirements in section 4 or by any
> > mechanism in the gin draft.
> >
> > Thanks,
> >
> > John
> >
> > > -----Original Message-----
> > > From: martini issue tracker [mailto:trac@tools.ietf.org<mailto:trac@t=
ools.ietf.org>]
> > > Sent: 25 March 2010 13:38
> > > To: Elwell, John
> > > Cc: martini@ietf.org<mailto:martini@ietf.org>
> > > Subject: Re: [martini] #23: 3.3 unlear whether mentioned
> > > issues are tackled or not
> > >
> > > #23: 3.3 unlear whether mentioned issues are tackled or not
> > > -------------------------------------+------------------------
> > > --------------
> > >  Reporter:  ietf.hanserik@...          |       Owner:
> > > john.elwell@...
> > >      Type:  defect                   |      Status:  assigned
> > >
> > >  Priority:  minor                    |   Milestone:
> > > milestone1
> > > Component:  reqs                     |     Version:  1.0
> > >
> > >  Severity:  In WG Last Call          |    Keywords:
> > >
> > > -------------------------------------+------------------------
> > > --------------
> > > Changes (by john.elwell@...):
> > >
> > >   * owner:  =3D> john.elwell@...
> > >   * status:  new =3D> assigned
> > >
> > >
> > > Comment:
> > >
> > >  I am inclined to accept this comment, but the text came
> from Hadriel
> > >  orginally. Hadriel, can you give an opinion whether we
> should delete
> > >  sections 3.3.1 and 3.3.2 (and hence 3.3)?
> > >
> > > --
> > > Ticket URL:
> > > <http://trac.tools.ietf.org/wg/martini/trac/ticket/23#comment:1>
> > > martini <http://tools.ietf.org/martini/>
> > >
> > >
>
_______________________________________________
martini mailing list
martini@ietf.org<mailto:martini@ietf.org>
https://www.ietf.org/mailman/listinfo/martini


--_000_A444A0F8084434499206E78C106220CADE11B373MCHP058Aglobala_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.5921" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D061175919-26032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I can accept MUST ( a requirement) or SHOULD (a de=
sirable).=20
Other opinions?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D061175919-26032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D061175919-26032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>John</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Hans Erik van Elburg=20
  [mailto:ietf.hanserik@gmail.com] <BR><B>Sent:</B> 26 March 2010=20
  02:31<BR><B>To:</B> Elwell, John<BR><B>Cc:</B> Hadriel Kaplan;=20
  martini@ietf.org<BR><B>Subject:</B> Re: [martini] #23: 3.3 unlear whether=
=20
  mentioned issues are tackled or not<BR></FONT><BR></DIV>
  <DIV></DIV>It is a requirement, that you MUST have really good reasons fo=
r not=20
  to comply with. See RFC2119. If you keep the issues in the doc and hence =
agree=20
  that they are issues then I think it will be hard to find a good=20
  reason.<BR><BR>I think that it is good to have a requirement like that. B=
ut=20
  does this mean that the specification should also describe impacts on PBX=
=20
  outbound calls to the SSP over the SIP trunk? Is it only=20
  authentication/identification that need to be looked at?<BR><BR>BR,<BR=20
  clear=3Dall>/Hans Erik van Elburg<BR><BR>
  <DIV class=3Dgmail_quote>On Thu, Mar 25, 2010 at 10:08 PM, Elwell, John <=
SPAN=20
  dir=3Dltr>&lt;<A=20
  href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-en=
terprise.com</A>&gt;</SPAN>=20
  wrote:<BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(2=
04,204,204) 1px solid">Yes,=20
    I meant 3.3.1 and 3.3.2 (its getting late in the week).<BR><BR>If we sa=
y=20
    "SHOULD", it would be a desirable, not a requirement, right?<BR><FONT=20
    color=3D#888888><BR>John<BR></FONT>
    <DIV class=3Dim><BR>&gt; -----Original Message-----<BR>&gt; From: Hadri=
el=20
    Kaplan [mailto:<A=20
    href=3D"mailto:HKaplan@acmepacket.com">HKaplan@acmepacket.com</A>]<BR>&=
gt;=20
    Sent: 25 March 2010 14:05<BR>&gt; To: Elwell, John<BR>&gt; Cc: <A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR></DIV>
    <DIV>
    <DIV></DIV>
    <DIV class=3Dh5>&gt; Subject: RE: [martini] #23: 3.3 unlear whether=20
    mentioned<BR>&gt; issues are tackled or not<BR>&gt;<BR>&gt;<BR>&gt; You=
 mean=20
    section 3.3.1 and 3.3.2 (not 3.2.1 and 3.2.2).<BR>&gt;<BR>&gt; As secti=
on=20
    3.3 says:<BR>&gt; &nbsp; &nbsp;A mechanism for solving the SIP-PBX=20
    registration problem<BR>&gt; &nbsp; &nbsp;will not solve these policy i=
ssues=20
    directly, although when<BR>&gt; specifying<BR>&gt; &nbsp; &nbsp;the=20
    mechanism the opportunity can be taken to highlight<BR>&gt; the impact=
=20
    of<BR>&gt; &nbsp; &nbsp;such policies.<BR>&gt;<BR>&gt; What we really m=
eant=20
    was the Martini was not going to solve<BR>&gt; the policy issues, but w=
e=20
    would document the impact of such policies.<BR>&gt;<BR>&gt; So I recomm=
end=20
    we add the following Requirement:<BR>&gt; REQ19 - the mechanism's=20
    specification SHOULD give guidance or<BR>&gt; warnings about how=20
    authorization policies may be affected by<BR>&gt; the mechanism, to add=
ress=20
    the problems described in section 3.3.<BR>&gt;<BR>&gt; OK?<BR>&gt;<BR>&=
gt;=20
    -hadriel<BR>&gt;<BR>&gt; &gt; -----Original Message-----<BR>&gt; &gt; F=
rom:=20
    Elwell, John [mailto:<A=20
    href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-=
enterprise.com</A>]<BR>&gt;=20
    &gt; Sent: Thursday, March 25, 2010 4:42 PM<BR>&gt; &gt; To: Hadriel=20
    Kaplan<BR>&gt; &gt; Cc: <A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; &gt; Subj=
ect:=20
    FW: [martini] #23: 3.3 unlear whether mentioned issues are<BR>&gt; &gt;=
=20
    tackled or not<BR>&gt; &gt;<BR>&gt; &gt; Hadriel,<BR>&gt; &gt;<BR>&gt; =
&gt;=20
    I am forwarding this, as you are not explicitly addressed<BR>&gt; on th=
e=20
    tracker<BR>&gt; &gt; message. Please give your opinion on this matter. =
The=20
    issue is that<BR>&gt; &gt; sections 3.2.1 and 3.2.2 do not seem relevan=
t to=20
    the<BR>&gt; MARTINI question, and<BR>&gt; &gt; are not even backed up b=
y any=20
    requirements in section 4 or by any<BR>&gt; &gt; mechanism in the gin=20
    draft.<BR>&gt; &gt;<BR>&gt; &gt; Thanks,<BR>&gt; &gt;<BR>&gt; &gt;=20
    John<BR>&gt; &gt;<BR>&gt; &gt; &gt; -----Original Message-----<BR>&gt; =
&gt;=20
    &gt; From: martini issue tracker [mailto:<A=20
    href=3D"mailto:trac@tools.ietf.org">trac@tools.ietf.org</A>]<BR>&gt; &g=
t; &gt;=20
    Sent: 25 March 2010 13:38<BR>&gt; &gt; &gt; To: Elwell, John<BR>&gt; &g=
t;=20
    &gt; Cc: <A href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&g=
t; &gt;=20
    &gt; Subject: Re: [martini] #23: 3.3 unlear whether mentioned<BR>&gt; &=
gt;=20
    &gt; issues are tackled or not<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; #23:=
 3.3=20
    unlear whether mentioned issues are tackled or not<BR>&gt; &gt; &gt;=20
    -------------------------------------+------------------------<BR>&gt; =
&gt;=20
    &gt; --------------<BR>&gt; &gt; &gt; &nbsp;Reporter:=20
    &nbsp;ietf.hanserik@... &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbs=
p;=20
    &nbsp; Owner:<BR>&gt; &gt; &gt; john.elwell@...<BR>&gt; &gt; &gt; &nbsp=
;=20
    &nbsp; &nbsp;Type: &nbsp;defect &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
    &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp;Status: &nbsp;assigned<BR>&g=
t;=20
    &gt; &gt;<BR>&gt; &gt; &gt; &nbsp;Priority: &nbsp;minor &nbsp; &nbsp; &=
nbsp;=20
    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; Milestone:<BR>=
&gt;=20
    &gt; &gt; milestone1<BR>&gt; &gt; &gt; Component: &nbsp;reqs &nbsp; &nb=
sp;=20
    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp;=
=20
    Version: &nbsp;1.0<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; &nbsp;Severity:=
=20
    &nbsp;In WG Last Call &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;=20
    &nbsp;Keywords:<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt;=20
    -------------------------------------+------------------------<BR>&gt; =
&gt;=20
    &gt; --------------<BR>&gt; &gt; &gt; Changes (by john.elwell@...):<BR>=
&gt;=20
    &gt; &gt;<BR>&gt; &gt; &gt; &nbsp; * owner: &nbsp;=3D&gt;=20
    john.elwell@...<BR>&gt; &gt; &gt; &nbsp; * status: &nbsp;new =3D&gt;=20
    assigned<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt;=20
    Comment:<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; &nbsp;I am inclined to acc=
ept=20
    this comment, but the text came<BR>&gt; from Hadriel<BR>&gt; &gt; &gt;=
=20
    &nbsp;orginally. Hadriel, can you give an opinion whether we<BR>&gt; sh=
ould=20
    delete<BR>&gt; &gt; &gt; &nbsp;sections 3.3.1 and 3.3.2 (and hence=20
    3.3)?<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; --<BR>&gt; &gt; &gt; Ticket=20
    URL:<BR>&gt; &gt; &gt; &lt;<A=20
    href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/23#comment:1"=
=20
    target=3D_blank>http://trac.tools.ietf.org/wg/martini/trac/ticket/23#co=
mment:1</A>&gt;<BR>&gt;=20
    &gt; &gt; martini &lt;<A href=3D"http://tools.ietf.org/martini/"=20
    target=3D_blank>http://tools.ietf.org/martini/</A>&gt;<BR>&gt; &gt;=20
    &gt;<BR>&gt; &gt;=20
    &gt;<BR>&gt;<BR>_______________________________________________<BR>mart=
ini=20
    mailing list<BR><A href=3D"mailto:martini@ietf.org">martini@ietf.org</A=
><BR><A=20
    href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
    target=3D_blank>https://www.ietf.org/mailman/listinfo/martini</A><BR></=
DIV></DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>

--_000_A444A0F8084434499206E78C106220CADE11B373MCHP058Aglobala_--

From john.elwell@siemens-enterprise.com  Fri Mar 26 13:03:34 2010
Return-Path: <john.elwell@siemens-enterprise.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 3B5E53A6B65 for <martini@core3.amsl.com>; Fri, 26 Mar 2010 13:03:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.469
X-Spam-Level: 
X-Spam-Status: No, score=-0.469 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 Hxyfxm0HK49h for <martini@core3.amsl.com>; Fri, 26 Mar 2010 13:03:33 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 077D23A68B3 for <martini@ietf.org>; Fri, 26 Mar 2010 13:03:32 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1365113; Fri, 26 Mar 2010 21:03:55 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id AF4B11EB82AE; Fri, 26 Mar 2010 21:03:55 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Fri, 26 Mar 2010 21:03:55 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>, "trac@localhost.amsl.com" <trac@localhost.amsl.com>
Date: Fri, 26 Mar 2010 21:03:52 +0100
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrMxahgHaIP1krgT0mtHsopfXP8wgAWY1Fw
Message-ID: <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org> <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com>
In-Reply-To: <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Fri, 26 Mar 2010 20:03:34 -0000

The IETF does not have a mechanism, and that is the reason for the MARTINI =
work. In particular, the IETF has not published the so-called loose-route m=
echanism. Hence the reason for the IETF, as owner of SIP, to publish a mech=
anism for bulk registrations.

John

> -----Original Message-----
> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]=20
> Sent: 26 March 2010 02:21
> To: trac@localhost.amsl.com
> Cc: Elwell, John; martini@ietf.org
> Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>=20
>=20
> Then you should rephrase to what the real issue is:
> "
>=20
>=20
> Request-URI vs. loose-route acceptance
>=20
>=20
> Some IP-PBX do not implement international standards or SIP=20
> profiles for SIP trunking. As a consequence some SIP-PBXs=20
> expect that inbound SIP requests from the SSP will have the=20
> registered Contact-URI in the Request-URI, and thus not=20
> interoperate with the loose-route scheme of 3GPP and ETSI.=20
> Other SIP-PBXs are fine with the Request-URI being the=20
> intended target, but cannot handle receiving a Route header=20
> field identifying their registered Contact-URI as a=20
> loose-route entry."
>=20
>=20
> Is this an issue, yes. Does introducing yet another profile help? No.
>=20
> /Hans Erik van Elburg
>=20
>=20
> On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker=20
> <trac@tools.ietf.org> wrote:
>=20
>=20
> 	#21: 3.2.2 describes an issue with some PBX
> =09
> -------------------------------------+------------------------
> --------------
> 	 Reporter:  ietf.hanserik@...          |        Owner:
> =09
> 	    Type:  defect                   |       Status:  closed
> =09
> 	 Priority:  minor                    |    Milestone:  milestone1
> 	Component:  reqs                     |      Version:  1.0
> =09
> 	 Severity:  In WG Last Call          |   Resolution:  invalid
> 	 Keywords:                           |
> =09
> -------------------------------------+------------------------
> --------------
> 	Changes (by john.elwell@...):
> =09
> 	 * status:  new =3D> closed
> 	 * resolution:  =3D> invalid
> =09
> =09
> 	Comment:
> =09
> =09
> 	 The text of 3.2.2 just underlines the fact that there=20
> are different
> 	 implementations around. A PBX that expects the loose=20
> route mechanism to be
> 	 used would fail to interwork with SSPs using a=20
> different mechanism (e.g.,
> 	 SIPconnect 1.0), and a PBX not expecting the loose=20
> route mechanism to be
> 	 used would fail to interwork with a loose route=20
> implementation (e.g.,
> 	 ETSI/3GPP). Hence the urgent need for a standard.
> =09
> 	--
> 	Ticket URL:=20
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
> =09
> 	martini <http://tools.ietf.org/martini/>
> =09
> =09
> 	_______________________________________________
> 	martini mailing list
> 	martini@ietf.org
> 	https://www.ietf.org/mailman/listinfo/martini
> =09
>=20
>=20
> =

From HKaplan@acmepacket.com  Fri Mar 26 14:46:33 2010
Return-Path: <HKaplan@acmepacket.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 C2D553A6B69 for <martini@core3.amsl.com>; Fri, 26 Mar 2010 14:46:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.758
X-Spam-Level: 
X-Spam-Status: No, score=0.758 tagged_above=-999 required=5 tests=[AWL=-0.187,  BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13]
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 GxxBpXEyWq2y for <martini@core3.amsl.com>; Fri, 26 Mar 2010 14:46:33 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id D13D73A63EC for <martini@ietf.org>; Fri, 26 Mar 2010 14:46:32 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 26 Mar 2010 17:46:56 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Fri, 26 Mar 2010 17:46:55 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "martini@ietf.org" <martini@ietf.org>
Date: Fri, 26 Mar 2010 17:46:54 -0400
Thread-Topic: Requiring Path
Thread-Index: AcrNLdnseydB91xQRrSlhpKjHejRgQ==
Message-ID: <430FC6BDED356B4C8498F634416644A91A79E92672@mail>
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
Subject: [martini] Requiring Path
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: Fri, 26 Mar 2010 21:46:33 -0000

At the first meeting of martini this week, one of the presentations discuss=
ed that if the IP-PBX needs to get certain info in SIP Requests routed to i=
t, it can use the Path mechanism in the Registration to the SSP.  In order =
for that to work, though, the SSP/registrar has to support the Path mechani=
sm.  We've also talked about middleboxes needing the SSP/Registrar to suppo=
rt Path, for a similar reason.

Therefore, I propose that the Martini mechanism REQUIRE Path support for de=
vices implementing Martini. =20

>From a customer's perspective, this will mean when a vendor says "I support=
 [martini-spec]", they're required to have also implemented RFC 3327.

-hadriel

From D.Hancock@CableLabs.com  Fri Mar 26 14:51:04 2010
Return-Path: <D.Hancock@CableLabs.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 963B93A6B45 for <martini@core3.amsl.com>; Fri, 26 Mar 2010 14:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.868
X-Spam-Level: ***
X-Spam-Status: No, score=3.868 tagged_above=-999 required=5 tests=[AWL=0.600,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_MODEMCABLE=0.768,  HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001]
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 EUXtQRP3euYY for <martini@core3.amsl.com>; Fri, 26 Mar 2010 14:51:00 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 8B5933A6A92 for <martini@ietf.org>; Fri, 26 Mar 2010 14:51:00 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o2QLpNi6005719 for <martini@ietf.org>; Fri, 26 Mar 2010 15:51:23 -0600
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Fri, 26 Mar 2010 15:51:23 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Fri, 26 Mar 2010 15:51:24 -0600
From: David Hancock <D.Hancock@CableLabs.com>
To: "martini@ietf.org" <martini@ietf.org>
Date: Fri, 26 Mar 2010 15:51:22 -0600
Thread-Topic: Very rough notes for Friday MARTINI meeting @ IETF#77
Thread-Index: AcrNLnnIgvUAasGyRRuSuLGYHZjYyw==
Message-ID: <76AC5FEF83F1E64491446437EA81A61F7CD4E31133@srvxchg>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_76AC5FEF83F1E64491446437EA81A61F7CD4E31133srvxchg_"
MIME-Version: 1.0
X-Approved: ondar
Subject: [martini] Very rough notes for Friday MARTINI meeting @ IETF#77
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: Fri, 26 Mar 2010 21:51:04 -0000

--_000_76AC5FEF83F1E64491446437EA81A61F7CD4E31133srvxchg_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Adam Roach's presentation of new version of GIN draft:
-          Provided summary of updates
-          No comments received

Dean Willis' presentation on security considerations on Path and Service-Ro=
ute
-          There may be an issue between Service Route and Outbound

Keith Drage: Service Route works for IMS implicit registration, which is di=
fferent than the registration procedure proposed by GIN.

Hadriel Kaplan: Although IMS and GIN registration procedures differ, they a=
re the same w.r.t. Service Route; i.e., they are both registering multiple =
AORs with a single REGISER transaction.

John Elwell's presentation on MARTINI requirements draft:

Christer Holmberg: Has a problem with REQ16 - the RU requirement.

Dale Worley: Clarified this requirement - which is that the solution should=
 not constrain the PBX from assigning GRUUs to its UAs in the usual way.

Paul Kyzivat: This requirement is also about addressing the fact that the S=
IP-PBX doesn't itself have a globally unique address, and therefore must ge=
t some help from the SSP network to provide a globally unique address.

Dale Worley must allow the SIP-PBX it's UAs GRUUs as defined in the GRUU RF=
C.

John Elwell: Please post clarifying updates to the list.


End of notes - had to leave early...

David








--_000_76AC5FEF83F1E64491446437EA81A61F7CD4E31133srvxchg_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:st1=3D"urn:schemas-microsoft-com:off=
ice:smarttags" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"Street"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.Comment-blue, li.Comment-blue, div.Comment-blue
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Times New Roman";
	font-weight:bold;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:659620150;
	mso-list-type:hybrid;
	mso-list-template-ids:788946226 613574682 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:3;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:21.0pt;
	mso-level-number-position:left;
	margin-left:21.0pt;
	text-indent:-.25in;
	font-family:Arial;
	mso-fareast-font-family:"Times New Roman";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Adam Roach&#8217;s presentation of new version of GIN dr=
aft:<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:21.0pt;text-indent:-.25in;mso-lis=
t:l0 level1 lfo1'><![if !supportLists]><font
size=3D2 face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'><s=
pan
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 face=3DArial><s=
pan
style=3D'font-size:10.0pt;font-family:Arial'>Provided summary of updates<o:=
p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:21.0pt;text-indent:-.25in;mso-lis=
t:l0 level1 lfo1'><![if !supportLists]><font
size=3D2 face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'><s=
pan
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 face=3DArial><s=
pan
style=3D'font-size:10.0pt;font-family:Arial'>No comments received<o:p></o:p=
></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Dean Willis&#8217; presentation on security consideratio=
ns
on Path and Service-Route<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:21.0pt;text-indent:-.25in;mso-lis=
t:l0 level1 lfo1'><![if !supportLists]><font
size=3D2 face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'><s=
pan
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 face=3DArial><s=
pan
style=3D'font-size:10.0pt;font-family:Arial'>There may be an issue between =
<st1:Street
w:st=3D"on"><st1:address w:st=3D"on">Service Route</st1:address></st1:Stree=
t> and
Outbound<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Keith Drage: <st1:Street w:st=3D"on"><st1:address w:st=
=3D"on">Service
  Route</st1:address></st1:Street> works for IMS implicit registration, whi=
ch
is different than the registration procedure proposed by GIN.<o:p></o:p></s=
pan></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Hadriel Kaplan: Although IMS and GIN registration proced=
ures
differ, they are the same w.r.t. <st1:Street w:st=3D"on"><st1:address w:st=
=3D"on">Service
  Route</st1:address></st1:Street>; i.e., they are both registering multipl=
e AORs
with a single REGISER transaction.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>John Elwell&#8217;s presentation on MARTINI requirements
draft:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Christer Holmberg: Has a problem with REQ16 &#8211; the =
RU
requirement.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Dale Worley: Clarified this requirement &#8211; which is
that the solution should not constrain the PBX from assigning GRUUs to its =
UAs in
the usual way.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Paul Kyzivat: This requirement is also about addressing =
the
fact that the SIP-PBX doesn&#8217;t itself have a globally unique address, =
and
therefore must get some help from the SSP network to provide a globally uni=
que address.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Dale Worley must allow the SIP-PBX it&#8217;s UAs GRUUs =
as
defined in the GRUU RFC.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>John Elwell: Please post clarifying updates to the list.=
<o:p></o:p></span></font></p>

<div style=3D'mso-element:para-border-div;border:none;border-bottom:solid w=
indowtext 1.0pt;
padding:0in 0in 1.0pt 0in'>

<p class=3DMsoNormal style=3D'border:none;padding:0in'><font size=3D2 face=
=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font=
></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>End of notes &#8211; had to leave early&#8230;<o:p></o:p=
></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>David<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--_000_76AC5FEF83F1E64491446437EA81A61F7CD4E31133srvxchg_--

From pkyzivat@cisco.com  Fri Mar 26 15:12:38 2010
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 A814C3A6C43 for <martini@core3.amsl.com>; Fri, 26 Mar 2010 15:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.351
X-Spam-Level: 
X-Spam-Status: No, score=-8.351 tagged_above=-999 required=5 tests=[AWL=1.118,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_HI=-8]
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 KdwaS8qc9klY for <martini@core3.amsl.com>; Fri, 26 Mar 2010 15:12:37 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 29ADD3A6C54 for <martini@ietf.org>; Fri, 26 Mar 2010 15:12:34 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al4gANLNrEurR7H+/2dsb2JhbACKOJByc6YsjxuJeoR+BA
X-IronPort-AV: E=Sophos;i="4.51,316,1267401600"; d="scan'208";a="106427339"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-4.cisco.com with ESMTP; 26 Mar 2010 22:12:58 +0000
Received: from [10.21.78.47] ([10.21.78.47]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o2QMCvmU018202; Fri, 26 Mar 2010 22:12:57 GMT
Message-ID: <4BAD3169.9090500@cisco.com>
Date: Fri, 26 Mar 2010 18:12:57 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <430FC6BDED356B4C8498F634416644A91A79E92672@mail>
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79E92672@mail>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Requiring Path
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: Fri, 26 Mar 2010 22:12:38 -0000

Hadriel,

You are expecting the registrar in the SP to support Path, right?
(And not that the pbx and any registrar it might contain must do so.)

	Thanks,
	Paul

Hadriel Kaplan wrote:
> At the first meeting of martini this week, one of the presentations discussed that if the IP-PBX needs to get certain info in SIP Requests routed to it, it can use the Path mechanism in the Registration to the SSP.  In order for that to work, though, the SSP/registrar has to support the Path mechanism.  We've also talked about middleboxes needing the SSP/Registrar to support Path, for a similar reason.
> 
> Therefore, I propose that the Martini mechanism REQUIRE Path support for devices implementing Martini.  
> 
>>From a customer's perspective, this will mean when a vendor says "I support [martini-spec]", they're required to have also implemented RFC 3327.
> 
> -hadriel
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
> 

From ietf.hanserik@gmail.com  Fri Mar 26 16:02:56 2010
Return-Path: <ietf.hanserik@gmail.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 82BCE3A6934 for <martini@core3.amsl.com>; Fri, 26 Mar 2010 16:02:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.724
X-Spam-Level: 
X-Spam-Status: No, score=-0.724 tagged_above=-999 required=5 tests=[AWL=0.744,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 zw5QfQOjufPr for <martini@core3.amsl.com>; Fri, 26 Mar 2010 16:02:55 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 01A333A68D6 for <martini@ietf.org>; Fri, 26 Mar 2010 16:02:54 -0700 (PDT)
Received: by wwb17 with SMTP id 17so238169wwb.31 for <martini@ietf.org>; Fri, 26 Mar 2010 16:03:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=fyLQvJB4xd5b1OQQqtm+XHAtWbRzVb0uc3dcQHBZN6E=; b=AfM/lquHrl7jPasxFhi/zomhQxtea5Fbi2Nu7hg4UX+6ppuROY0EQK9nk+YWHlTEno qOWYxbwhUax0LG4HVmO4LV27OEF2XLXWpnH9/0FvJUZEpra+vEF8eUxsiiEGruv9m91y 1Szudb0DckJ2I9cjGHZiE3+hd5PTSuq6VrssI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=K5wIdVbThzW9BoGP9n2PxBNL3hSREEyaoQsBhwvu/WIM7sdJ65EHatwn3avesEY1lO qXYSlQ5g6+/sjMObHFDHvYSu4u7FKcGPVAPvJOxAWh2IAKUq9VLo2KpUTXOYmEEKzSy6 jYuDJ7QcWp9G+gtULuiGsbzLEm+2ROb2VewV8=
MIME-Version: 1.0
Received: by 10.216.180.130 with HTTP; Fri, 26 Mar 2010 16:03:13 -0700 (PDT)
In-Reply-To: <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org> <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net>
Date: Sat, 27 Mar 2010 00:03:13 +0100
Received: by 10.216.86.16 with SMTP id v16mr914334wee.162.1269644593549; Fri,  26 Mar 2010 16:03:13 -0700 (PDT)
Message-ID: <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Content-Type: multipart/alternative; boundary=0016e6d588b9fd517d0482bc2aa2
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Fri, 26 Mar 2010 23:02:56 -0000

--0016e6d588b9fd517d0482bc2aa2
Content-Type: text/plain; charset=ISO-8859-1

I will not argue with you about the validity of that argument.

Can you agree to the modified text?

"Request-URI vs. loose-route acceptance
Some IP-PBX do not implement international standards or SIP profiles for SIP
trunking. As a consequence some SIP-PBXs expect that inbound SIP requests
from the SSP will have the registered Contact-URI in the Request-URI, and
thus not interoperate with the loose-route scheme of 3GPP and ETSI. Other
SIP-PBXs are fine with the Request-URI being the intended target, but cannot
handle receiving a Route header field identifying their registered
Contact-URI as a loose-route entry."

BR,
/Hans Erik van Elburg

On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John <
john.elwell@siemens-enterprise.com> wrote:

> The IETF does not have a mechanism, and that is the reason for the MARTINI
> work. In particular, the IETF has not published the so-called loose-route
> mechanism. Hence the reason for the IETF, as owner of SIP, to publish a
> mechanism for bulk registrations.
>
> John
>
> > -----Original Message-----
> > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
> > Sent: 26 March 2010 02:21
> > To: trac@localhost.amsl.com
> > Cc: Elwell, John; martini@ietf.org
> > Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
> >
> >
> > Then you should rephrase to what the real issue is:
> > "
> >
> >
> > Request-URI vs. loose-route acceptance
> >
> >
> > Some IP-PBX do not implement international standards or SIP
> > profiles for SIP trunking. As a consequence some SIP-PBXs
> > expect that inbound SIP requests from the SSP will have the
> > registered Contact-URI in the Request-URI, and thus not
> > interoperate with the loose-route scheme of 3GPP and ETSI.
> > Other SIP-PBXs are fine with the Request-URI being the
> > intended target, but cannot handle receiving a Route header
> > field identifying their registered Contact-URI as a
> > loose-route entry."
> >
> >
> > Is this an issue, yes. Does introducing yet another profile help? No.
> >
> > /Hans Erik van Elburg
> >
> >
> > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
> > <trac@tools.ietf.org> wrote:
> >
> >
> >       #21: 3.2.2 describes an issue with some PBX
> >
> > -------------------------------------+------------------------
> > --------------
> >        Reporter:  ietf.hanserik@...          |        Owner:
> >
> >           Type:  defect                   |       Status:  closed
> >
> >        Priority:  minor                    |    Milestone:  milestone1
> >       Component:  reqs                     |      Version:  1.0
> >
> >        Severity:  In WG Last Call          |   Resolution:  invalid
> >        Keywords:                           |
> >
> > -------------------------------------+------------------------
> > --------------
> >       Changes (by john.elwell@...):
> >
> >        * status:  new => closed
> >        * resolution:  => invalid
> >
> >
> >       Comment:
> >
> >
> >        The text of 3.2.2 just underlines the fact that there
> > are different
> >        implementations around. A PBX that expects the loose
> > route mechanism to be
> >        used would fail to interwork with SSPs using a
> > different mechanism (e.g.,
> >        SIPconnect 1.0), and a PBX not expecting the loose
> > route mechanism to be
> >        used would fail to interwork with a loose route
> > implementation (e.g.,
> >        ETSI/3GPP). Hence the urgent need for a standard.
> >
> >       --
> >       Ticket URL:
> > <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
> >
> >       martini <http://tools.ietf.org/martini/>
> >
> >
> >       _______________________________________________
> >       martini mailing list
> >       martini@ietf.org
> >       https://www.ietf.org/mailman/listinfo/martini
> >
> >
> >
> >
>

--0016e6d588b9fd517d0482bc2aa2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I will not argue with you about the validity of that argument. <br><br>Can =
you agree to the modified text?<br><br>&quot;<span style=3D"font-size: 10pt=
;">Request-URI vs.=20
loose-route acceptance</span>

<br>Some IP-PBX do not implement international standards or SIP profiles
 for SIP trunking. As a consequence some SIP-PBXs expect that inbound=20
SIP requests from the SSP will have the registered Contact-URI in the=20
Request-URI, and thus not interoperate with the loose-route scheme of=20
3GPP and ETSI.  Other SIP-PBXs are fine with the Request-URI being the=20
intended target, but cannot handle receiving a Route header field=20
identifying their registered Contact-URI as a loose-route entry.&quot;<br><=
br>BR,<br clear=3D"all">/Hans Erik van Elburg<br><br><div class=3D"gmail_qu=
ote">On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-ent=
erprise.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">The IETF does not=
 have a mechanism, and that is the reason for the MARTINI work. In particul=
ar, the IETF has not published the so-called loose-route mechanism. Hence t=
he reason for the IETF, as owner of SIP, to publish a mechanism for bulk re=
gistrations.<br>

<font color=3D"#888888"><br>
John<br>
</font><div><div></div><div class=3D"h5"><br>
&gt; -----Original Message-----<br>
&gt; From: Hans Erik van Elburg [mailto:<a href=3D"mailto:ietf.hanserik@gma=
il.com">ietf.hanserik@gmail.com</a>]<br>
&gt; Sent: 26 March 2010 02:21<br>
&gt; To: <a href=3D"mailto:trac@localhost.amsl.com">trac@localhost.amsl.com=
</a><br>
&gt; Cc: Elwell, John; <a href=3D"mailto:martini@ietf.org">martini@ietf.org=
</a><br>
&gt; Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX<br>
&gt;<br>
&gt;<br>
&gt; Then you should rephrase to what the real issue is:<br>
&gt; &quot;<br>
&gt;<br>
&gt;<br>
&gt; Request-URI vs. loose-route acceptance<br>
&gt;<br>
&gt;<br>
&gt; Some IP-PBX do not implement international standards or SIP<br>
&gt; profiles for SIP trunking. As a consequence some SIP-PBXs<br>
&gt; expect that inbound SIP requests from the SSP will have the<br>
&gt; registered Contact-URI in the Request-URI, and thus not<br>
&gt; interoperate with the loose-route scheme of 3GPP and ETSI.<br>
&gt; Other SIP-PBXs are fine with the Request-URI being the<br>
&gt; intended target, but cannot handle receiving a Route header<br>
&gt; field identifying their registered Contact-URI as a<br>
&gt; loose-route entry.&quot;<br>
&gt;<br>
&gt;<br>
&gt; Is this an issue, yes. Does introducing yet another profile help? No.<=
br>
&gt;<br>
&gt; /Hans Erik van Elburg<br>
&gt;<br>
&gt;<br>
&gt; On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker<br>
&gt; &lt;<a href=3D"mailto:trac@tools.ietf.org">trac@tools.ietf.org</a>&gt;=
 wrote:<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 #21: 3.2.2 describes an issue with some PBX<br>
&gt;<br>
&gt; -------------------------------------+------------------------<br>
&gt; --------------<br>
&gt; =A0 =A0 =A0 =A0Reporter: =A0ietf.hanserik@... =A0 =A0 =A0 =A0 =A0| =A0=
 =A0 =A0 =A0Owner:<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 Type: =A0defect =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 | =A0 =A0 =A0 Status: =A0closed<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0Priority: =A0minor =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0| =A0 =A0Milestone: =A0milestone1<br>
&gt; =A0 =A0 =A0 Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 | =A0 =A0 =A0Version: =A01.0<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0Severity: =A0In WG Last Call =A0 =A0 =A0 =A0 =A0| =A0 R=
esolution: =A0invalid<br>
&gt; =A0 =A0 =A0 =A0Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 |<br>
&gt;<br>
&gt; -------------------------------------+------------------------<br>
&gt; --------------<br>
&gt; =A0 =A0 =A0 Changes (by john.elwell@...):<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0* status: =A0new =3D&gt; closed<br>
&gt; =A0 =A0 =A0 =A0* resolution: =A0=3D&gt; invalid<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 Comment:<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0The text of 3.2.2 just underlines the fact that there<b=
r>
&gt; are different<br>
&gt; =A0 =A0 =A0 =A0implementations around. A PBX that expects the loose<br=
>
&gt; route mechanism to be<br>
&gt; =A0 =A0 =A0 =A0used would fail to interwork with SSPs using a<br>
&gt; different mechanism (e.g.,<br>
&gt; =A0 =A0 =A0 =A0SIPconnect 1.0), and a PBX not expecting the loose<br>
&gt; route mechanism to be<br>
&gt; =A0 =A0 =A0 =A0used would fail to interwork with a loose route<br>
&gt; implementation (e.g.,<br>
&gt; =A0 =A0 =A0 =A0ETSI/3GPP). Hence the urgent need for a standard.<br>
&gt;<br>
&gt; =A0 =A0 =A0 --<br>
&gt; =A0 =A0 =A0 Ticket URL:<br>
&gt; &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/21#co=
mment:1" target=3D"_blank">http://trac.tools.ietf.org/wg/martini/trac/ticke=
t/21#comment:1</a>&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 martini &lt;<a href=3D"http://tools.ietf.org/martini/" tar=
get=3D"_blank">http://tools.ietf.org/martini/</a>&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 _______________________________________________<br>
&gt; =A0 =A0 =A0 martini mailing list<br>
&gt; =A0 =A0 =A0 <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><b=
r>
&gt; =A0 =A0 =A0 <a href=3D"https://www.ietf.org/mailman/listinfo/martini" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/martini</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; </div></div></blockquote></div><br>

--0016e6d588b9fd517d0482bc2aa2--

From ietf.hanserik@gmail.com  Fri Mar 26 16:06:42 2010
Return-Path: <ietf.hanserik@gmail.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 CA2FB3A6A30 for <martini@core3.amsl.com>; Fri, 26 Mar 2010 16:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.096
X-Spam-Level: 
X-Spam-Status: No, score=-1.096 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 z9egtVdf9ABw for <martini@core3.amsl.com>; Fri, 26 Mar 2010 16:06:42 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 8D99F3A693E for <martini@ietf.org>; Fri, 26 Mar 2010 16:06:41 -0700 (PDT)
Received: by wwb17 with SMTP id 17so240278wwb.31 for <martini@ietf.org>; Fri, 26 Mar 2010 16:07:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=4yAZVh9Bfq93TIjxgCZjVIfyZxVnhXEl6LxQXMgXm0Y=; b=wS3i6mQLQtkElFHV5xBpUWtRQw4OVVSz6HBzY+lHie6/o/vDDmg2cIrMza8Y+UMEtX ea8a2L9eX4ODJhvUphuiCk+VlVqMtZqs43dB5PDDlpOGSWjHIbYULM+gEb2w5UcDghSC Kt3/f48bGEfHfMwYRFuqz9H8GOqGVTmIoiwlY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=tOuqX3zWHxn7ipUolPIKWR8Jlvjtoo2AlijsGXHfckFL9xvEhQGGkpGbT5R9+Was88 DmzVZN3e7WZ+rcEcf5n/28NNhvgn2pXJx8QTbjHRFmee4yOuv3evYx3zZ65ukHgkYGl4 2ykQtY6KEbxQQtpTrPezT7Ii/LY7zqlve/ZO0=
MIME-Version: 1.0
Received: by 10.216.180.130 with HTTP; Fri, 26 Mar 2010 16:07:02 -0700 (PDT)
In-Reply-To: <4BAD3169.9090500@cisco.com>
References: <430FC6BDED356B4C8498F634416644A91A79E92672@mail> <4BAD3169.9090500@cisco.com>
Date: Sat, 27 Mar 2010 00:07:02 +0100
Received: by 10.216.93.68 with SMTP id k46mr905673wef.104.1269644822509; Fri,  26 Mar 2010 16:07:02 -0700 (PDT)
Message-ID: <9ae56b1e1003261607s2a5343aaod495f6159eb23371@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Content-Type: multipart/alternative; boundary=0016e6d64441a2fd8b0482bc38e9
Cc: "martini@ietf.org" <martini@ietf.org>, Hadriel Kaplan <HKaplan@acmepacket.com>
Subject: Re: [martini] Requiring Path
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: Fri, 26 Mar 2010 23:06:42 -0000

--0016e6d64441a2fd8b0482bc38e9
Content-Type: text/plain; charset=ISO-8859-1

And SIP entities that wish to be on the path to the PBX.

/Hans Erik van Elburg


On Fri, Mar 26, 2010 at 11:12 PM, Paul Kyzivat <pkyzivat@cisco.com> wrote:

> Hadriel,
>
> You are expecting the registrar in the SP to support Path, right?
> (And not that the pbx and any registrar it might contain must do so.)
>
>        Thanks,
>        Paul
>
>
> Hadriel Kaplan wrote:
>
>> At the first meeting of martini this week, one of the presentations
>> discussed that if the IP-PBX needs to get certain info in SIP Requests
>> routed to it, it can use the Path mechanism in the Registration to the SSP.
>>  In order for that to work, though, the SSP/registrar has to support the
>> Path mechanism.  We've also talked about middleboxes needing the
>> SSP/Registrar to support Path, for a similar reason.
>>
>> Therefore, I propose that the Martini mechanism REQUIRE Path support for
>> devices implementing Martini.
>>
>>> From a customer's perspective, this will mean when a vendor says "I
>>> support [martini-spec]", they're required to have also implemented RFC 3327.
>>>
>>
>> -hadriel
>> _______________________________________________
>> martini mailing list
>> martini@ietf.org
>> https://www.ietf.org/mailman/listinfo/martini
>>
>>  _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>

--0016e6d64441a2fd8b0482bc38e9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

And SIP entities that wish to be on the path to the PBX.<br><br clear=3D"al=
l">/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Fri, Mar 26, 2010 at 11:12 PM, Paul K=
yzivat <span dir=3D"ltr">&lt;<a href=3D"mailto:pkyzivat@cisco.com">pkyzivat=
@cisco.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); p=
adding-left: 1ex;">
Hadriel,<br>
<br>
You are expecting the registrar in the SP to support Path, right?<br>
(And not that the pbx and any registrar it might contain must do so.)<br>
<br>
 =A0 =A0 =A0 =A0Thanks,<br><font color=3D"#888888">
 =A0 =A0 =A0 =A0Paul</font><div><div></div><div class=3D"h5"><br>
<br>
Hadriel Kaplan wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
At the first meeting of martini this week, one of the presentations discuss=
ed that if the IP-PBX needs to get certain info in SIP Requests routed to i=
t, it can use the Path mechanism in the Registration to the SSP. =A0In orde=
r for that to work, though, the SSP/registrar has to support the Path mecha=
nism. =A0We&#39;ve also talked about middleboxes needing the SSP/Registrar =
to support Path, for a similar reason.<br>

<br>
Therefore, I propose that the Martini mechanism REQUIRE Path support for de=
vices implementing Martini. =A0<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
>From a customer&#39;s perspective, this will mean when a vendor says &quot;=
I support [martini-spec]&quot;, they&#39;re required to have also implement=
ed RFC 3327.<br>
</blockquote>
<br>
-hadriel<br>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
<br>
</blockquote>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
</div></div></blockquote></div><br>

--0016e6d64441a2fd8b0482bc38e9--

From HKaplan@acmepacket.com  Fri Mar 26 19:39:22 2010
Return-Path: <HKaplan@acmepacket.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 BAE513A6C4C for <martini@core3.amsl.com>; Fri, 26 Mar 2010 19:39:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.441
X-Spam-Level: 
X-Spam-Status: No, score=-0.441 tagged_above=-999 required=5 tests=[AWL=1.028,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 Jfo0mXCQgjZF for <martini@core3.amsl.com>; Fri, 26 Mar 2010 19:39:22 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id C726C3A68D1 for <martini@ietf.org>; Fri, 26 Mar 2010 19:39:21 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 26 Mar 2010 22:39:45 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Fri, 26 Mar 2010 22:39:37 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Date: Fri, 26 Mar 2010 22:39:30 -0400
Thread-Topic: [martini] Requiring Path
Thread-Index: AcrNMYSozOehi5RIRqKtEk9baAp7PwAJEBkw
Message-ID: <430FC6BDED356B4C8498F634416644A91A79E92697@mail>
References: <430FC6BDED356B4C8498F634416644A91A79E92672@mail> <4BAD3169.9090500@cisco.com>
In-Reply-To: <4BAD3169.9090500@cisco.com>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Requiring Path
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: Sat, 27 Mar 2010 02:39:22 -0000

In theory RFC 3327 is written such that a proxy can only insert a Path head=
er if the UAC inserted a 'path' option-tag in a Supported header of the REG=
ISTER (it's a SHOULD/SHOULD-NOT level).  So my preference would be that the=
 IP-PBX actually put the option-tag in its Supported header.  Obviously it =
doesn't have to insert an actual Path header or care about them in the resp=
onse, if it doesn't want to.

But yeah the big one would be the Registrar supporting it, such that the PB=
X or Proxy can put a 'path' option-tag in a Require header.

-hadriel

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Friday, March 26, 2010 6:13 PM
> To: Hadriel Kaplan
> Cc: martini@ietf.org
> Subject: Re: [martini] Requiring Path
>=20
> Hadriel,
>=20
> You are expecting the registrar in the SP to support Path, right?
> (And not that the pbx and any registrar it might contain must do so.)
>=20
> 	Thanks,
> 	Paul
>=20
> Hadriel Kaplan wrote:
> > At the first meeting of martini this week, one of the presentations
> discussed that if the IP-PBX needs to get certain info in SIP Requests
> routed to it, it can use the Path mechanism in the Registration to the SS=
P.
> In order for that to work, though, the SSP/registrar has to support the
> Path mechanism.  We've also talked about middleboxes needing the
> SSP/Registrar to support Path, for a similar reason.
> >
> > Therefore, I propose that the Martini mechanism REQUIRE Path support fo=
r
> devices implementing Martini.
> >
> >>From a customer's perspective, this will mean when a vendor says "I
> support [martini-spec]", they're required to have also implemented RFC
> 3327.
> >
> > -hadriel
> > _______________________________________________
> > martini mailing list
> > martini@ietf.org
> > https://www.ietf.org/mailman/listinfo/martini
> >

From HKaplan@acmepacket.com  Fri Mar 26 20:09:39 2010
Return-Path: <HKaplan@acmepacket.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 CABA43A6C4F for <martini@core3.amsl.com>; Fri, 26 Mar 2010 20:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.819
X-Spam-Level: 
X-Spam-Status: No, score=0.819 tagged_above=-999 required=5 tests=[AWL=-0.313,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 UPJMa3K-Vqeh for <martini@core3.amsl.com>; Fri, 26 Mar 2010 20:09:32 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 2BFD83A67A2 for <martini@ietf.org>; Fri, 26 Mar 2010 20:09:32 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 26 Mar 2010 23:09:55 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Fri, 26 Mar 2010 23:09:55 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
Date: Fri, 26 Mar 2010 23:09:23 -0400
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrNOKKruSWVU7NTTICUz2KnC67voQAHlb6w
Message-ID: <430FC6BDED356B4C8498F634416644A91A79E9269A@mail>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org> <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net> <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com>
In-Reply-To: <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_430FC6BDED356B4C8498F634416644A91A79E9269Amail_"
MIME-Version: 1.0
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Sat, 27 Mar 2010 03:09:39 -0000

--_000_430FC6BDED356B4C8498F634416644A91A79E9269Amail_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Actually that's not really the problem, or the motivation for the work, imh=
o.

Prroblem-1 is there is absolutely no way the SSP's equipment will know whet=
her the IP-PBX does international standard X, Y or Z from the REGISTER requ=
est in those international standards.  And there is no way for the IP-PBX t=
o know what international standard the SSP does.  Now obviously you can hav=
e the operator provision every single trunk with X, Y or Z mode, based on s=
ome big list of every IP-PBX vendor's product and version number and whethe=
r it supports mode X, Y or Z.  For medium-to-large Enterprise trunks that's=
 ok - manual configuration and such is perfectly reasonable/justified for t=
hem.  But for the small-business market with high- volume and low margin pe=
r sale, it's a barrier to deployment.

But that's only problem-1.  Problem-2 is the 3GPP/ETSI specs say "loose-rou=
ting", but if that's followed verbatim then the PBX will get a request-URI =
with a domain of the SSP, which again some support and some don't. (and I t=
hink even ETSI would admit was a mistake, if they wanted the signaling to a=
ct the same as a peering model)  Some PBX's are ok with "loose-routing", bu=
t expect their own domain; others are ok getting the SSP's domain.  So that=
's mode X.a and X.b to provision.  And that provisioning is often not done =
in the HSS, but rather in the border proxy that "fixes" it, and that's anot=
her barrier to deployment.

And I don't think anyone's blaming 3GPP or ETSI for this, by the way - the =
IETF doesn't have a perfect record by a long shot either on this type of st=
uff, and really this all started in SIP-Forum in SIP-Connect 1.0 years ago =
when we punted on truly specifying Registration mode and thereby caused a l=
ot more interop issues. (at least it seems to me it all started there)  We'=
re trying to fix our mistakes, not ETSI's, but with the benefit of experien=
ce gained from all of the international standards.

-hadriel

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Hans Erik van Elburg
Sent: Friday, March 26, 2010 7:03 PM
To: Elwell, John
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

I will not argue with you about the validity of that argument.

Can you agree to the modified text?

"Request-URI vs. loose-route acceptance
Some IP-PBX do not implement international standards or SIP profiles for SI=
P trunking. As a consequence some SIP-PBXs expect that inbound SIP requests=
 from the SSP will have the registered Contact-URI in the Request-URI, and =
thus not interoperate with the loose-route scheme of 3GPP and ETSI. Other S=
IP-PBXs are fine with the Request-URI being the intended target, but cannot=
 handle receiving a Route header field identifying their registered Contact=
-URI as a loose-route entry."

BR,
/Hans Erik van Elburg
On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John <john.elwell@siemens-enterpri=
se.com<mailto:john.elwell@siemens-enterprise.com>> wrote:
The IETF does not have a mechanism, and that is the reason for the MARTINI =
work. In particular, the IETF has not published the so-called loose-route m=
echanism. Hence the reason for the IETF, as owner of SIP, to publish a mech=
anism for bulk registrations.

John

> -----Original Message-----
> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto:ietf.ha=
nserik@gmail.com>]
> Sent: 26 March 2010 02:21
> To: trac@localhost.amsl.com<mailto:trac@localhost.amsl.com>
> Cc: Elwell, John; martini@ietf.org<mailto:martini@ietf.org>
> Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>
>
> Then you should rephrase to what the real issue is:
> "
>
>
> Request-URI vs. loose-route acceptance
>
>
> Some IP-PBX do not implement international standards or SIP
> profiles for SIP trunking. As a consequence some SIP-PBXs
> expect that inbound SIP requests from the SSP will have the
> registered Contact-URI in the Request-URI, and thus not
> interoperate with the loose-route scheme of 3GPP and ETSI.
> Other SIP-PBXs are fine with the Request-URI being the
> intended target, but cannot handle receiving a Route header
> field identifying their registered Contact-URI as a
> loose-route entry."
>
>
> Is this an issue, yes. Does introducing yet another profile help? No.
>
> /Hans Erik van Elburg
>
>
> On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
> <trac@tools.ietf.org<mailto:trac@tools.ietf.org>> wrote:
>
>
>       #21: 3.2.2 describes an issue with some PBX
>
> -------------------------------------+------------------------
> --------------
>        Reporter:  ietf.hanserik@...          |        Owner:
>
>           Type:  defect                   |       Status:  closed
>
>        Priority:  minor                    |    Milestone:  milestone1
>       Component:  reqs                     |      Version:  1.0
>
>        Severity:  In WG Last Call          |   Resolution:  invalid
>        Keywords:                           |
>
> -------------------------------------+------------------------
> --------------
>       Changes (by john.elwell@...):
>
>        * status:  new =3D> closed
>        * resolution:  =3D> invalid
>
>
>       Comment:
>
>
>        The text of 3.2.2 just underlines the fact that there
> are different
>        implementations around. A PBX that expects the loose
> route mechanism to be
>        used would fail to interwork with SSPs using a
> different mechanism (e.g.,
>        SIPconnect 1.0), and a PBX not expecting the loose
> route mechanism to be
>        used would fail to interwork with a loose route
> implementation (e.g.,
>        ETSI/3GPP). Hence the urgent need for a standard.
>
>       --
>       Ticket URL:
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
>
>       martini <http://tools.ietf.org/martini/>
>
>
>       _______________________________________________
>       martini mailing list
>       martini@ietf.org<mailto:martini@ietf.org>
>       https://www.ietf.org/mailman/listinfo/martini
>
>
>
>


--_000_430FC6BDED356B4C8498F634416644A91A79E9269Amail_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:st1=3D"urn:sch=
emas-microsoft-com:office:smarttags" xmlns=3D"http://www.w3.org/TR/REC-html=
40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"City"/=
>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Actually that&#8217;s not really the
problem, or the motivation for the work, imho.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Prroblem-1 is there is absolutely no w=
ay
the SSP&#8217;s equipment will know whether the IP-PBX does international s=
tandard
X, Y or Z from the REGISTER request in those international standards.&nbsp;=
 And
there is no way for the IP-PBX to know what international standard the SSP
does.&nbsp; Now obviously you can have the operator provision every single
trunk with X, Y or Z mode, based on some big list of every IP-PBX vendor&#8=
217;s
product and version number and whether it supports mode X, Y or Z.&nbsp; Fo=
r
medium-to-large <st1:City w:st=3D"on"><st1:place w:st=3D"on">Enterprise</st=
1:place></st1:City>
trunks that&#8217;s ok &#8211; manual configuration and such is perfectly
reasonable/justified for them. &nbsp;But for the small-business market with
high- volume and low margin per sale, it&#8217;s a barrier to deployment.<o=
:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>But that&#8217;s only problem-1.&nbsp;
Problem-2 is the 3GPP/ETSI specs say &#8220;loose-routing&#8221;, but if th=
at&#8217;s
followed verbatim then the PBX will get a request-URI with a domain of the =
SSP,
which again some support and some don&#8217;t. (and I think even ETSI would
admit was a mistake, if they wanted the signaling to act the same as a peer=
ing
model)&nbsp; Some PBX&#8217;s are ok with &#8220;loose-routing&#8221;, but =
expect
their own domain; others are ok getting the SSP&#8217;s domain.&nbsp; So th=
at&#8217;s
mode X.a and X.b to provision. &nbsp;And that provisioning is often <i><spa=
n
style=3D'font-style:italic'>not </span></i>done in the HSS, but rather in t=
he border
proxy that &#8220;fixes&#8221; it, and that&#8217;s another barrier to
deployment.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>And I don&#8217;t think anyone&#8217;s
blaming 3GPP or ETSI for this, by the way &#8211; the IETF doesn&#8217;t ha=
ve a
perfect record by a long shot either on this type of stuff, and really this=
 all
started in SIP-Forum in SIP-Connect 1.0 years ago when we punted on truly s=
pecifying
Registration mode and thereby caused a lot more interop issues. (at least i=
t
seems to me it all started there)&nbsp; We&#8217;re trying to fix <i><span
style=3D'font-style:italic'>our</span></i> mistakes, not ETSI&#8217;s, but =
with
the benefit of experience gained from all of the international standards.<o=
:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>-hadriel<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b><st1:PersonName w:st=3D"=
on">Hans
 Erik van Elburg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, March 26, 2010=
 7:03
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Elwell, John<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> martini@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [martini] #21: =
3.2.2
describes an issue with some PBX</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>I will not argue =
with you
about the validity of that argument. <br>
<br>
Can you agree to the modified text?<br>
<br>
&quot;</span></font><font size=3D2><span style=3D'font-size:10.0pt'>Request=
-URI vs.
loose-route acceptance</span></font> <br>
Some IP-PBX do not implement international standards or SIP profiles for SI=
P
trunking. As a consequence some SIP-PBXs expect that inbound SIP requests f=
rom
the SSP will have the registered Contact-URI in the Request-URI, and thus n=
ot
interoperate with the loose-route scheme of 3GPP and ETSI. Other SIP-PBXs a=
re
fine with the Request-URI being the intended target, but cannot handle
receiving a Route header field identifying their registered Contact-URI as =
a
loose-route entry.&quot;<br>
<br>
BR,<br clear=3Dall>
/<st1:PersonName w:st=3D"on">Hans Erik van Elburg</st1:PersonName><o:p></o:=
p></p>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John &lt;<a
href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-ente=
rprise.com</a>&gt;
wrote:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>The IETF does not have a mechanism, and that is the reason for the
MARTINI work. In particular, the IETF has not published the so-called
loose-route mechanism. Hence the reason for the IETF, as owner of SIP, to
publish a mechanism for bulk registrations.<br>
<font color=3D"#888888"><span style=3D'color:#888888'><br>
John</span></font><o:p></o:p></span></font></p>

<div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><br>
&gt; -----Original Message-----<br>
&gt; From: <st1:PersonName w:st=3D"on">Hans Erik van Elburg</st1:PersonName=
>
[mailto:<a href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com<=
/a>]<br>
&gt; Sent: 26 March 2010 02:21<br>
&gt; To: <a href=3D"mailto:trac@localhost.amsl.com">trac@localhost.amsl.com=
</a><br>
&gt; Cc: Elwell, John; <a href=3D"mailto:martini@ietf.org">martini@ietf.org=
</a><br>
&gt; Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX<br>
&gt;<br>
&gt;<br>
&gt; Then you should rephrase to what the real issue is:<br>
&gt; &quot;<br>
&gt;<br>
&gt;<br>
&gt; Request-URI vs. loose-route acceptance<br>
&gt;<br>
&gt;<br>
&gt; Some IP-PBX do not implement international standards or SIP<br>
&gt; profiles for SIP trunking. As a consequence some SIP-PBXs<br>
&gt; expect that inbound SIP requests from the SSP will have the<br>
&gt; registered Contact-URI in the Request-URI, and thus not<br>
&gt; interoperate with the loose-route scheme of 3GPP and ETSI.<br>
&gt; Other SIP-PBXs are fine with the Request-URI being the<br>
&gt; intended target, but cannot handle receiving a Route header<br>
&gt; field identifying their registered Contact-URI as a<br>
&gt; loose-route entry.&quot;<br>
&gt;<br>
&gt;<br>
&gt; Is this an issue, yes. Does introducing yet another profile help? No.<=
br>
&gt;<br>
&gt; /<st1:PersonName w:st=3D"on">Hans Erik van Elburg</st1:PersonName><br>
&gt;<br>
&gt;<br>
&gt; On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker<br>
&gt; &lt;<a href=3D"mailto:trac@tools.ietf.org">trac@tools.ietf.org</a>&gt;
wrote:<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; #21: 3.2.2 describes an issue with some PBX<br>
&gt;<br>
&gt; -------------------------------------+------------------------<br>
&gt; --------------<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;Reporter: &nbsp;ietf.hanserik@... &nbsp; &n=
bsp;
&nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;Owner:<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Type: &nbsp;defect &nbsp; &nbsp; &n=
bsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; Status:
&nbsp;closed<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;Priority: &nbsp;minor &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp;Milestone:
&nbsp;milestone1<br>
&gt; &nbsp; &nbsp; &nbsp; Component: &nbsp;reqs &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp;Version:
&nbsp;1.0<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;Severity: &nbsp;In WG Last Call &nbsp; &nbs=
p;
&nbsp; &nbsp; &nbsp;| &nbsp; Resolution: &nbsp;invalid<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;Keywords: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;<br>
&gt; -------------------------------------+------------------------<br>
&gt; --------------<br>
&gt; &nbsp; &nbsp; &nbsp; Changes (by john.elwell@...):<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;* status: &nbsp;new =3D&gt; closed<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;* resolution: &nbsp;=3D&gt; invalid<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; Comment:<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;The text of 3.2.2 just underlines the fact =
that
there<br>
&gt; are different<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;implementations around. A PBX that expects =
the
loose<br>
&gt; route mechanism to be<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;used would fail to interwork with SSPs usin=
g a<br>
&gt; different mechanism (e.g.,<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;SIPconnect 1.0), and a PBX not expecting th=
e
loose<br>
&gt; route mechanism to be<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;used would fail to interwork with a loose r=
oute<br>
&gt; implementation (e.g.,<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;ETSI/3GPP). Hence the urgent need for a
standard.<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; --<br>
&gt; &nbsp; &nbsp; &nbsp; Ticket URL:<br>
&gt; &lt;<a
href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1"
target=3D"_blank">http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comm=
ent:1</a>&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; martini &lt;<a href=3D"http://tools.ietf.org/mart=
ini/"
target=3D"_blank">http://tools.ietf.org/martini/</a>&gt;<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; _______________________________________________<b=
r>
&gt; &nbsp; &nbsp; &nbsp; martini mailing list<br>
&gt; &nbsp; &nbsp; &nbsp; <a href=3D"mailto:martini@ietf.org">martini@ietf.=
org</a><br>
&gt; &nbsp; &nbsp; &nbsp; <a
href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/martini</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; <o:p></o:p></span></font></p>

</div>

</div>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>

</body>

</html>

--_000_430FC6BDED356B4C8498F634416644A91A79E9269Amail_--

From adam@nostrum.com  Mon Mar 29 08:17:11 2010
Return-Path: <adam@nostrum.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 EFD3E3A6A90 for <martini@core3.amsl.com>; Mon, 29 Mar 2010 08:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.47
X-Spam-Level: 
X-Spam-Status: No, score=-1.47 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, SPF_PASS=-0.001]
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 e9-VzN5R8gwF for <martini@core3.amsl.com>; Mon, 29 Mar 2010 08:17:09 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 2A4CC3A6A7D for <martini@ietf.org>; Mon, 29 Mar 2010 08:16:55 -0700 (PDT)
Received: from [172.16.3.231] (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o2TFHI5f020819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Mar 2010 10:17:18 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4BB0C47E.6020805@nostrum.com>
Date: Mon, 29 Mar 2010 10:17:18 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <430FC6BDED356B4C8498F634416644A91A79E92672@mail>	<4BAD3169.9090500@cisco.com> <430FC6BDED356B4C8498F634416644A91A79E92697@mail>
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79E92697@mail>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Requiring Path
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, 29 Mar 2010 15:17:11 -0000

Everyone:

I'm agnostic on this point, but would like to see some kind of rapid 
consensus resolution so I can update the GIN document appropriately. 
Please weigh in.

/a

On 3/26/10 9:39 PM, Hadriel Kaplan wrote:
> In theory RFC 3327 is written such that a proxy can only insert a Path header if the UAC inserted a 'path' option-tag in a Supported header of the REGISTER (it's a SHOULD/SHOULD-NOT level).  So my preference would be that the IP-PBX actually put the option-tag in its Supported header.  Obviously it doesn't have to insert an actual Path header or care about them in the response, if it doesn't want to.
>
> But yeah the big one would be the Registrar supporting it, such that the PBX or Proxy can put a 'path' option-tag in a Require header.
>
> -hadriel
>
>    
>> -----Original Message-----
>> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
>> Sent: Friday, March 26, 2010 6:13 PM
>> To: Hadriel Kaplan
>> Cc: martini@ietf.org
>> Subject: Re: [martini] Requiring Path
>>
>> Hadriel,
>>
>> You are expecting the registrar in the SP to support Path, right?
>> (And not that the pbx and any registrar it might contain must do so.)
>>
>> 	Thanks,
>> 	Paul
>>
>> Hadriel Kaplan wrote:
>>      
>>> At the first meeting of martini this week, one of the presentations
>>>        
>> discussed that if the IP-PBX needs to get certain info in SIP Requests
>> routed to it, it can use the Path mechanism in the Registration to the SSP.
>> In order for that to work, though, the SSP/registrar has to support the
>> Path mechanism.  We've also talked about middleboxes needing the
>> SSP/Registrar to support Path, for a similar reason.
>>      
>>> Therefore, I propose that the Martini mechanism REQUIRE Path support for
>>>        
>> devices implementing Martini.
>>      
>>> > From a customer's perspective, this will mean when a vendor says "I
>>>        
>> support [martini-spec]", they're required to have also implemented RFC
>> 3327.
>>      
>>> -hadriel
>>> _______________________________________________
>>> martini mailing list
>>> martini@ietf.org
>>> https://www.ietf.org/mailman/listinfo/martini
>>>
>>>        
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>    


From john.elwell@siemens-enterprise.com  Mon Mar 29 08:31:13 2010
Return-Path: <john.elwell@siemens-enterprise.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 4A21A3A6A79 for <martini@core3.amsl.com>; Mon, 29 Mar 2010 08:31:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.683
X-Spam-Level: 
X-Spam-Status: No, score=0.683 tagged_above=-999 required=5 tests=[AWL=-0.262,  BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13]
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 X3-AGdlVrBVb for <martini@core3.amsl.com>; Mon, 29 Mar 2010 08:31:12 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 6CEAE3A6A8E for <martini@ietf.org>; Mon, 29 Mar 2010 08:31:05 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1381356; Mon, 29 Mar 2010 17:31:31 +0200
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id E12A423F0278; Mon, 29 Mar 2010 17:31:31 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 29 Mar 2010 17:31:31 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Adam Roach <adam@nostrum.com>, Hadriel Kaplan <HKaplan@acmepacket.com>
Date: Mon, 29 Mar 2010 17:31:30 +0200
Thread-Topic: [martini] Requiring Path
Thread-Index: AcrPUvvKVSoHPXtuRxSGl2fb3nTibwAAdVng
Message-ID: <A444A0F8084434499206E78C106220CADE11B8F5@MCHP058A.global-ad.net>
References: <430FC6BDED356B4C8498F634416644A91A79E92672@mail> <4BAD3169.9090500@cisco.com> <430FC6BDED356B4C8498F634416644A91A79E92697@mail> <4BB0C47E.6020805@nostrum.com>
In-Reply-To: <4BB0C47E.6020805@nostrum.com>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Requiring Path
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, 29 Mar 2010 15:31:13 -0000

I have no objection if the only requirement on the PBX is to insert the opt=
ion tag.

John=20

> -----Original Message-----
> From: martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] On Behalf Of Adam Roach
> Sent: 29 March 2010 16:17
> To: Hadriel Kaplan
> Cc: martini@ietf.org
> Subject: Re: [martini] Requiring Path
>=20
> Everyone:
>=20
> I'm agnostic on this point, but would like to see some kind of rapid=20
> consensus resolution so I can update the GIN document appropriately.=20
> Please weigh in.
>=20
> /a
>=20
> On 3/26/10 9:39 PM, Hadriel Kaplan wrote:
> > In theory RFC 3327 is written such that a proxy can only=20
> insert a Path header if the UAC inserted a 'path' option-tag=20
> in a Supported header of the REGISTER (it's a=20
> SHOULD/SHOULD-NOT level).  So my preference would be that the=20
> IP-PBX actually put the option-tag in its Supported header. =20
> Obviously it doesn't have to insert an actual Path header or=20
> care about them in the response, if it doesn't want to.
> >
> > But yeah the big one would be the Registrar supporting it,=20
> such that the PBX or Proxy can put a 'path' option-tag in a=20
> Require header.
> >
> > -hadriel
> >
> >   =20
> >> -----Original Message-----
> >> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> >> Sent: Friday, March 26, 2010 6:13 PM
> >> To: Hadriel Kaplan
> >> Cc: martini@ietf.org
> >> Subject: Re: [martini] Requiring Path
> >>
> >> Hadriel,
> >>
> >> You are expecting the registrar in the SP to support Path, right?
> >> (And not that the pbx and any registrar it might contain=20
> must do so.)
> >>
> >> 	Thanks,
> >> 	Paul
> >>
> >> Hadriel Kaplan wrote:
> >>     =20
> >>> At the first meeting of martini this week, one of the=20
> presentations
> >>>       =20
> >> discussed that if the IP-PBX needs to get certain info in=20
> SIP Requests
> >> routed to it, it can use the Path mechanism in the=20
> Registration to the SSP.
> >> In order for that to work, though, the SSP/registrar has=20
> to support the
> >> Path mechanism.  We've also talked about middleboxes needing the
> >> SSP/Registrar to support Path, for a similar reason.
> >>     =20
> >>> Therefore, I propose that the Martini mechanism REQUIRE=20
> Path support for
> >>>       =20
> >> devices implementing Martini.
> >>     =20
> >>> > From a customer's perspective, this will mean when a=20
> vendor says "I
> >>>       =20
> >> support [martini-spec]", they're required to have also=20
> implemented RFC
> >> 3327.
> >>     =20
> >>> -hadriel
> >>> _______________________________________________
> >>> martini mailing list
> >>> martini@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/martini
> >>>
> >>>       =20
> > _______________________________________________
> > martini mailing list
> > martini@ietf.org
> > https://www.ietf.org/mailman/listinfo/martini
> >   =20
>=20
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
> =

From ietf.hanserik@gmail.com  Mon Mar 29 08:45:26 2010
Return-Path: <ietf.hanserik@gmail.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 23F063A6A7E for <martini@core3.amsl.com>; Mon, 29 Mar 2010 08:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.29
X-Spam-Level: 
X-Spam-Status: No, score=-0.29 tagged_above=-999 required=5 tests=[AWL=-0.681,  BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 7wA8G2EM+mSx for <martini@core3.amsl.com>; Mon, 29 Mar 2010 08:45:25 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by core3.amsl.com (Postfix) with ESMTP id 6A2883A6A75 for <martini@ietf.org>; Mon, 29 Mar 2010 08:45:22 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 4so1027481eyf.51 for <martini@ietf.org>; Mon, 29 Mar 2010 08:45:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=GhXBitbtIDtVwded58tDys3IYUxc97btRgbuk0m9giE=; b=lQqRttX590R38ivyFEaGL56oZKeBrd3ol6M3aBt9cb9kl5zdHgczm0cLL353YwUwZc HF8IXGQ9GSfpjDOpdR9swKsHrca+ObZzE8KfVKvG8TvnAySu72wnoPMtdnm5gzce6NSK KC3ZHSutj2yGCGZ+6mmAgKTm1mZja/nycQ4DM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=MqzIZzdRG6bfLhfedb4IqPyZB88fdf+IOed1nHTdWQG3oDdpIln5Xl8dFy+zm0TSQa 9w7NSpFh3qOIB8+idKxraWiQb84mzCOEmAnwCa4qZ6pLuuCZ82tYDPyW2atiWEaByteE 4iiblp8PMks2luhSoJ7e/Ey47TifIgPAm6qJY=
MIME-Version: 1.0
Received: by 10.213.15.138 with HTTP; Mon, 29 Mar 2010 08:45:46 -0700 (PDT)
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79E92697@mail>
References: <430FC6BDED356B4C8498F634416644A91A79E92672@mail> <4BAD3169.9090500@cisco.com> <430FC6BDED356B4C8498F634416644A91A79E92697@mail>
Date: Mon, 29 Mar 2010 17:45:46 +0200
Received: by 10.213.41.10 with SMTP id m10mr2582103ebe.79.1269877546985; Mon,  29 Mar 2010 08:45:46 -0700 (PDT)
Message-ID: <h2t9ae56b1e1003290845k20f95d97m47707f965eaff068@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Content-Type: multipart/alternative; boundary=0014852ea4bb18aee90482f268a0
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Requiring Path
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, 29 Mar 2010 15:45:26 -0000

--0014852ea4bb18aee90482f268a0
Content-Type: text/plain; charset=ISO-8859-1

Sounds like a good idea.

/Hans Erik van Elburg


On Sat, Mar 27, 2010 at 3:39 AM, Hadriel Kaplan <HKaplan@acmepacket.com>wrote:

>
> In theory RFC 3327 is written such that a proxy can only insert a Path
> header if the UAC inserted a 'path' option-tag in a Supported header of the
> REGISTER (it's a SHOULD/SHOULD-NOT level).  So my preference would be that
> the IP-PBX actually put the option-tag in its Supported header.  Obviously
> it doesn't have to insert an actual Path header or care about them in the
> response, if it doesn't want to.
>
> But yeah the big one would be the Registrar supporting it, such that the
> PBX or Proxy can put a 'path' option-tag in a Require header.
>
> -hadriel
>
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > Sent: Friday, March 26, 2010 6:13 PM
> > To: Hadriel Kaplan
> > Cc: martini@ietf.org
> > Subject: Re: [martini] Requiring Path
> >
> > Hadriel,
> >
> > You are expecting the registrar in the SP to support Path, right?
> > (And not that the pbx and any registrar it might contain must do so.)
> >
> >       Thanks,
> >       Paul
> >
> > Hadriel Kaplan wrote:
> > > At the first meeting of martini this week, one of the presentations
> > discussed that if the IP-PBX needs to get certain info in SIP Requests
> > routed to it, it can use the Path mechanism in the Registration to the
> SSP.
> > In order for that to work, though, the SSP/registrar has to support the
> > Path mechanism.  We've also talked about middleboxes needing the
> > SSP/Registrar to support Path, for a similar reason.
> > >
> > > Therefore, I propose that the Martini mechanism REQUIRE Path support
> for
> > devices implementing Martini.
> > >
> > >>From a customer's perspective, this will mean when a vendor says "I
> > support [martini-spec]", they're required to have also implemented RFC
> > 3327.
> > >
> > > -hadriel
> > > _______________________________________________
> > > martini mailing list
> > > martini@ietf.org
> > > https://www.ietf.org/mailman/listinfo/martini
> > >
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>

--0014852ea4bb18aee90482f268a0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Sounds like a good idea.<br><br clear=3D"all">/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Sat, Mar 27, 2010 at 3:39 AM, Hadriel=
 Kaplan <span dir=3D"ltr">&lt;<a href=3D"mailto:HKaplan@acmepacket.com">HKa=
plan@acmepacket.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204=
, 204); padding-left: 1ex;">
<br>
In theory RFC 3327 is written such that a proxy can only insert a Path head=
er if the UAC inserted a &#39;path&#39; option-tag in a Supported header of=
 the REGISTER (it&#39;s a SHOULD/SHOULD-NOT level). =A0So my preference wou=
ld be that the IP-PBX actually put the option-tag in its Supported header. =
=A0Obviously it doesn&#39;t have to insert an actual Path header or care ab=
out them in the response, if it doesn&#39;t want to.<br>

<br>
But yeah the big one would be the Registrar supporting it, such that the PB=
X or Proxy can put a &#39;path&#39; option-tag in a Require header.<br>
<font color=3D"#888888"><br>
-hadriel<br>
</font><div><div></div><div class=3D"h5"><br>
&gt; -----Original Message-----<br>
&gt; From: Paul Kyzivat [mailto:<a href=3D"mailto:pkyzivat@cisco.com">pkyzi=
vat@cisco.com</a>]<br>
&gt; Sent: Friday, March 26, 2010 6:13 PM<br>
&gt; To: Hadriel Kaplan<br>
&gt; Cc: <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; Subject: Re: [martini] Requiring Path<br>
&gt;<br>
&gt; Hadriel,<br>
&gt;<br>
&gt; You are expecting the registrar in the SP to support Path, right?<br>
&gt; (And not that the pbx and any registrar it might contain must do so.)<=
br>
&gt;<br>
&gt; =A0 =A0 =A0 Thanks,<br>
&gt; =A0 =A0 =A0 Paul<br>
&gt;<br>
&gt; Hadriel Kaplan wrote:<br>
&gt; &gt; At the first meeting of martini this week, one of the presentatio=
ns<br>
&gt; discussed that if the IP-PBX needs to get certain info in SIP Requests=
<br>
&gt; routed to it, it can use the Path mechanism in the Registration to the=
 SSP.<br>
&gt; In order for that to work, though, the SSP/registrar has to support th=
e<br>
&gt; Path mechanism. =A0We&#39;ve also talked about middleboxes needing the=
<br>
&gt; SSP/Registrar to support Path, for a similar reason.<br>
&gt; &gt;<br>
&gt; &gt; Therefore, I propose that the Martini mechanism REQUIRE Path supp=
ort for<br>
&gt; devices implementing Martini.<br>
&gt; &gt;<br>
&gt; &gt;&gt;From a customer&#39;s perspective, this will mean when a vendo=
r says &quot;I<br>
&gt; support [martini-spec]&quot;, they&#39;re required to have also implem=
ented RFC<br>
&gt; 3327.<br>
&gt; &gt;<br>
&gt; &gt; -hadriel<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; martini mailing list<br>
&gt; &gt; <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/martini</a><br>
&gt; &gt;<br>
_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
</div></div></blockquote></div><br>

--0014852ea4bb18aee90482f268a0--

From john.elwell@siemens-enterprise.com  Mon Mar 29 08:56:22 2010
Return-Path: <john.elwell@siemens-enterprise.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 A16D33A6A7E for <martini@core3.amsl.com>; Mon, 29 Mar 2010 08:56:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.419
X-Spam-Level: 
X-Spam-Status: No, score=0.419 tagged_above=-999 required=5 tests=[AWL=0.029,  BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13]
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 dCgNS0-U2DK9 for <martini@core3.amsl.com>; Mon, 29 Mar 2010 08:56:21 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id C77013A6A96 for <martini@ietf.org>; Mon, 29 Mar 2010 08:56:11 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1380720; Mon, 29 Mar 2010 17:56:38 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id DA7EB1EB82AB; Mon, 29 Mar 2010 17:56:38 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Mon, 29 Mar 2010 17:56:39 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>
Date: Mon, 29 Mar 2010 17:56:37 +0200
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrNOIQr02jTaJPdT5OTW131lROc3QCHVBNw
Message-ID: <A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org> <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net> <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com>
In-Reply-To: <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 29 Mar 2010 15:56:22 -0000

Hans Erik,

As an individual, I disagree with the proposed text, since it is misleading=
. The "international standards" to which you prefer are standards specific =
to an IMS environment. The implication of the wording as proposed is that S=
IP-PBXs ought to implement IMS specifications. And as Hadriel points out, i=
mplementing those IMS specifications does not eliminate the problems that t=
he SIPconnect people are trying to solve. I believe the existing text in dr=
aft-03 is sufficient.

John

> -----Original Message-----
> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]=20
> Sent: 26 March 2010 23:03
> To: Elwell, John
> Cc: martini@ietf.org
> Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>=20
> I will not argue with you about the validity of that argument.=20
>=20
> Can you agree to the modified text?
>=20
> "Request-URI vs. loose-route acceptance=20
> Some IP-PBX do not implement international standards or SIP=20
> profiles for SIP trunking. As a consequence some SIP-PBXs=20
> expect that inbound SIP requests from the SSP will have the=20
> registered Contact-URI in the Request-URI, and thus not=20
> interoperate with the loose-route scheme of 3GPP and ETSI.=20
> Other SIP-PBXs are fine with the Request-URI being the=20
> intended target, but cannot handle receiving a Route header=20
> field identifying their registered Contact-URI as a=20
> loose-route entry."
>=20
> BR,
> /Hans Erik van Elburg
>=20
>=20
> On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John=20
> <john.elwell@siemens-enterprise.com> wrote:
>=20
>=20
> 	The IETF does not have a mechanism, and that is the=20
> reason for the MARTINI work. In particular, the IETF has not=20
> published the so-called loose-route mechanism. Hence the=20
> reason for the IETF, as owner of SIP, to publish a mechanism=20
> for bulk registrations.
> =09
> 	John
> =09
>=20
> 	> -----Original Message-----
> 	> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
> 	> Sent: 26 March 2010 02:21
> 	> To: trac@localhost.amsl.com
> 	> Cc: Elwell, John; martini@ietf.org
> 	> Subject: Re: [martini] #21: 3.2.2 describes an issue=20
> with some PBX
> 	>
> 	>
> 	> Then you should rephrase to what the real issue is:
> 	> "
> 	>
> 	>
> 	> Request-URI vs. loose-route acceptance
> 	>
> 	>
> 	> Some IP-PBX do not implement international standards or SIP
> 	> profiles for SIP trunking. As a consequence some SIP-PBXs
> 	> expect that inbound SIP requests from the SSP will have the
> 	> registered Contact-URI in the Request-URI, and thus not
> 	> interoperate with the loose-route scheme of 3GPP and ETSI.
> 	> Other SIP-PBXs are fine with the Request-URI being the
> 	> intended target, but cannot handle receiving a Route header
> 	> field identifying their registered Contact-URI as a
> 	> loose-route entry."
> 	>
> 	>
> 	> Is this an issue, yes. Does introducing yet another=20
> profile help? No.
> 	>
> 	> /Hans Erik van Elburg
> 	>
> 	>
> 	> On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
> 	> <trac@tools.ietf.org> wrote:
> 	>
> 	>
> 	>       #21: 3.2.2 describes an issue with some PBX
> 	>
> 	> -------------------------------------+------------------------
> 	> --------------
> 	>        Reporter:  ietf.hanserik@...          |        Owner:
> 	>
> 	>           Type:  defect                   |      =20
> Status:  closed
> 	>
> 	>        Priority:  minor                    |   =20
> Milestone:  milestone1
> 	>       Component:  reqs                     |     =20
> Version:  1.0
> 	>
> 	>        Severity:  In WG Last Call          |  =20
> Resolution:  invalid
> 	>        Keywords:                           |
> 	>
> 	> -------------------------------------+------------------------
> 	> --------------
> 	>       Changes (by john.elwell@...):
> 	>
> 	>        * status:  new =3D> closed
> 	>        * resolution:  =3D> invalid
> 	>
> 	>
> 	>       Comment:
> 	>
> 	>
> 	>        The text of 3.2.2 just underlines the fact that there
> 	> are different
> 	>        implementations around. A PBX that expects the loose
> 	> route mechanism to be
> 	>        used would fail to interwork with SSPs using a
> 	> different mechanism (e.g.,
> 	>        SIPconnect 1.0), and a PBX not expecting the loose
> 	> route mechanism to be
> 	>        used would fail to interwork with a loose route
> 	> implementation (e.g.,
> 	>        ETSI/3GPP). Hence the urgent need for a standard.
> 	>
> 	>       --
> 	>       Ticket URL:
> 	>=20
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
> 	>
> 	>       martini <http://tools.ietf.org/martini/>
> 	>
> 	>
> 	>       _______________________________________________
> 	>       martini mailing list
> 	>       martini@ietf.org
> 	>       https://www.ietf.org/mailman/listinfo/martini
> 	>
> 	>
> 	>
> 	>=20
>=20
>=20
> =

From ietf.hanserik@gmail.com  Mon Mar 29 09:27:34 2010
Return-Path: <ietf.hanserik@gmail.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 8E8DA3A6AC5 for <martini@core3.amsl.com>; Mon, 29 Mar 2010 09:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.68
X-Spam-Level: 
X-Spam-Status: No, score=0.68 tagged_above=-999 required=5 tests=[AWL=-0.452,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 HkvNGEPe2fR9 for <martini@core3.amsl.com>; Mon, 29 Mar 2010 09:27:33 -0700 (PDT)
Received: from mail-ew0-f224.google.com (mail-ew0-f224.google.com [209.85.219.224]) by core3.amsl.com (Postfix) with ESMTP id A59853A68F7 for <martini@ietf.org>; Mon, 29 Mar 2010 09:26:38 -0700 (PDT)
Received: by ewy24 with SMTP id 24so824584ewy.13 for <martini@ietf.org>; Mon, 29 Mar 2010 09:27:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=XoTunIkmj9CuKlTSymSbLQAvlDcECKgqYxewErOaYeE=; b=LjQXSiDvAi8k8oH2u47owHnEUHYQ6yZUAGBbs1OnJgGQuPcMag2KOeE8svsbTGzUlS w4LLh/JNDpIG5Yg1siqlLIVQR04ekdHqLhav1STPW6wFNGyUhCzZAE1aNdyabujtVuHV wK8E3hIb4Prry09QDq3A0kOQEH005Fy8dZhuc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=qu5fUU0Tfl7zspfSraN3XqMNONCN2y/ycWj8nFMG5+Q+/W1ihvFGlHzHWeOtVkBZwy 55qCKLGNywl/92d8JITr7V+f1sBM1UUo6FQIJee4lKF64bHNxsF1ZU0YviebRL8VWX9V C9GGqa524hd3fpr6KCl0uvKk0KmR+psi9uRFc=
MIME-Version: 1.0
Received: by 10.213.15.138 with HTTP; Mon, 29 Mar 2010 09:27:02 -0700 (PDT)
In-Reply-To: <A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org> <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net> <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net>
Date: Mon, 29 Mar 2010 18:27:02 +0200
Received: by 10.213.100.140 with SMTP id y12mr478569ebn.11.1269880022419; Mon,  29 Mar 2010 09:27:02 -0700 (PDT)
Message-ID: <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Content-Type: multipart/alternative; boundary=001636c5a7faa4c88c0482f2fbfd
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 29 Mar 2010 16:27:34 -0000

--001636c5a7faa4c88c0482f2fbfd
Content-Type: text/plain; charset=ISO-8859-1

Hi John,

I was just trying to find a text that describes the issue.

But now the issue reads like "some PBX like apples, some like bananas". To
me that does not sound like a usefull issue to describe in an RFC.

So I think one or two more sentence would make clear why this is an issue.

I think there is multiple underlying issues here:
- PBX have different SIP profiles or all SIP-PBX are different
- PBX support SIP trunking flavour A, or support SIP trunking flavour B
- SSP systems don't know what mechanism the PBX support (can be resolved
with explicit indicator, this draft proposes an indicator for flavour B but
for another purpose it seems)
- PBX do not know what SIP trunking flavour the SSP supports (not addressed
it seems)

I don't seem to have a lucky hand with proposing an improved text, so maybe
you should have a go at it.

BR,
/Hans Erik van Elburg

p.s. I never said or implied that a SIP-PBX shall implement IMS. But it
would be really, really, really good if they would interwork on the UNI with
the IMS business trunking.  I think that should also be in your interest and
in fact you have been part of that work...


On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John <
john.elwell@siemens-enterprise.com> wrote:

> Hans Erik,
>
> As an individual, I disagree with the proposed text, since it is
> misleading. The "international standards" to which you prefer are standards
> specific to an IMS environment. The implication of the wording as proposed
> is that SIP-PBXs ought to implement IMS specifications. And as Hadriel
> points out, implementing those IMS specifications does not eliminate the
> problems that the SIPconnect people are trying to solve. I believe the
> existing text in draft-03 is sufficient.
>
> John
>
> > -----Original Message-----
> > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
> > Sent: 26 March 2010 23:03
> > To: Elwell, John
> > Cc: martini@ietf.org
> > Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
> >
> > I will not argue with you about the validity of that argument.
> >
> > Can you agree to the modified text?
> >
> > "Request-URI vs. loose-route acceptance
> > Some IP-PBX do not implement international standards or SIP
> > profiles for SIP trunking. As a consequence some SIP-PBXs
> > expect that inbound SIP requests from the SSP will have the
> > registered Contact-URI in the Request-URI, and thus not
> > interoperate with the loose-route scheme of 3GPP and ETSI.
> > Other SIP-PBXs are fine with the Request-URI being the
> > intended target, but cannot handle receiving a Route header
> > field identifying their registered Contact-URI as a
> > loose-route entry."
> >
> > BR,
> > /Hans Erik van Elburg
> >
> >
> > On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
> > <john.elwell@siemens-enterprise.com> wrote:
> >
> >
> >       The IETF does not have a mechanism, and that is the
> > reason for the MARTINI work. In particular, the IETF has not
> > published the so-called loose-route mechanism. Hence the
> > reason for the IETF, as owner of SIP, to publish a mechanism
> > for bulk registrations.
> >
> >       John
> >
> >
> >       > -----Original Message-----
> >       > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
> >       > Sent: 26 March 2010 02:21
> >       > To: trac@localhost.amsl.com
> >       > Cc: Elwell, John; martini@ietf.org
> >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
> > with some PBX
> >       >
> >       >
> >       > Then you should rephrase to what the real issue is:
> >       > "
> >       >
> >       >
> >       > Request-URI vs. loose-route acceptance
> >       >
> >       >
> >       > Some IP-PBX do not implement international standards or SIP
> >       > profiles for SIP trunking. As a consequence some SIP-PBXs
> >       > expect that inbound SIP requests from the SSP will have the
> >       > registered Contact-URI in the Request-URI, and thus not
> >       > interoperate with the loose-route scheme of 3GPP and ETSI.
> >       > Other SIP-PBXs are fine with the Request-URI being the
> >       > intended target, but cannot handle receiving a Route header
> >       > field identifying their registered Contact-URI as a
> >       > loose-route entry."
> >       >
> >       >
> >       > Is this an issue, yes. Does introducing yet another
> > profile help? No.
> >       >
> >       > /Hans Erik van Elburg
> >       >
> >       >
> >       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
> >       > <trac@tools.ietf.org> wrote:
> >       >
> >       >
> >       >       #21: 3.2.2 describes an issue with some PBX
> >       >
> >       > -------------------------------------+------------------------
> >       > --------------
> >       >        Reporter:  ietf.hanserik@...          |        Owner:
> >       >
> >       >           Type:  defect                   |
> > Status:  closed
> >       >
> >       >        Priority:  minor                    |
> > Milestone:  milestone1
> >       >       Component:  reqs                     |
> > Version:  1.0
> >       >
> >       >        Severity:  In WG Last Call          |
> > Resolution:  invalid
> >       >        Keywords:                           |
> >       >
> >       > -------------------------------------+------------------------
> >       > --------------
> >       >       Changes (by john.elwell@...):
> >       >
> >       >        * status:  new => closed
> >       >        * resolution:  => invalid
> >       >
> >       >
> >       >       Comment:
> >       >
> >       >
> >       >        The text of 3.2.2 just underlines the fact that there
> >       > are different
> >       >        implementations around. A PBX that expects the loose
> >       > route mechanism to be
> >       >        used would fail to interwork with SSPs using a
> >       > different mechanism (e.g.,
> >       >        SIPconnect 1.0), and a PBX not expecting the loose
> >       > route mechanism to be
> >       >        used would fail to interwork with a loose route
> >       > implementation (e.g.,
> >       >        ETSI/3GPP). Hence the urgent need for a standard.
> >       >
> >       >       --
> >       >       Ticket URL:
> >       >
> > <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
> >       >
> >       >       martini <http://tools.ietf.org/martini/>
> >       >
> >       >
> >       >       _______________________________________________
> >       >       martini mailing list
> >       >       martini@ietf.org
> >       >       https://www.ietf.org/mailman/listinfo/martini
> >       >
> >       >
> >       >
> >       >
> >
> >
> >
>

--001636c5a7faa4c88c0482f2fbfd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi John,<br><br>I was just trying to find a text that describes the issue. =
<br><br>But now the issue reads like &quot;some PBX like apples, some like =
bananas&quot;. To me that does not sound like a usefull issue to describe i=
n an RFC.<br>
<br>So I think one or two more sentence would make clear why this is an iss=
ue.<br><br>I think there is multiple underlying issues here:<br>- PBX have =
different SIP profiles or all SIP-PBX are different<br>- PBX support SIP tr=
unking flavour A, or support SIP trunking flavour B<br>
- SSP systems don&#39;t know what mechanism the PBX support (can be resolve=
d with explicit indicator, this draft proposes an indicator for flavour B b=
ut for another purpose it seems)<br>- PBX do not know what SIP trunking fla=
vour the SSP supports (not addressed it seems)<br>
<br>I don&#39;t seem to have a lucky hand with proposing an improved text, =
so maybe you should have a go at it.<br><br>BR,<br>/Hans Erik van Elburg<br=
>
<br>p.s. I never said or implied that a SIP-PBX shall implement IMS. But it=
 would be really, really, really good if they would interwork on the UNI wi=
th the IMS business trunking.=A0 I think that should also be in your intere=
st and in fact you have been part of that work...<br>
<br><br><div class=3D"gmail_quote">On Mon, Mar 29, 2010 at 5:56 PM, Elwell,=
 John <span dir=3D"ltr">&lt;<a href=3D"mailto:john.elwell@siemens-enterpris=
e.com">john.elwell@siemens-enterprise.com</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: =
1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hans Erik,<br>
<br>
As an individual, I disagree with the proposed text, since it is misleading=
. The &quot;international standards&quot; to which you prefer are standards=
 specific to an IMS environment. The implication of the wording as proposed=
 is that SIP-PBXs ought to implement IMS specifications. And as Hadriel poi=
nts out, implementing those IMS specifications does not eliminate the probl=
ems that the SIPconnect people are trying to solve. I believe the existing =
text in draft-03 is sufficient.<br>

<div class=3D"im"><br>
John<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Hans Erik van Elburg [mailto:<a href=3D"mailto:ietf.hanserik@gma=
il.com">ietf.hanserik@gmail.com</a>]<br>
</div><div><div></div><div class=3D"h5">&gt; Sent: 26 March 2010 23:03<br>
&gt; To: Elwell, John<br>
&gt; Cc: <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX<br>
&gt;<br>
&gt; I will not argue with you about the validity of that argument.<br>
&gt;<br>
&gt; Can you agree to the modified text?<br>
&gt;<br>
&gt; &quot;Request-URI vs. loose-route acceptance<br>
&gt; Some IP-PBX do not implement international standards or SIP<br>
&gt; profiles for SIP trunking. As a consequence some SIP-PBXs<br>
&gt; expect that inbound SIP requests from the SSP will have the<br>
&gt; registered Contact-URI in the Request-URI, and thus not<br>
&gt; interoperate with the loose-route scheme of 3GPP and ETSI.<br>
&gt; Other SIP-PBXs are fine with the Request-URI being the<br>
&gt; intended target, but cannot handle receiving a Route header<br>
&gt; field identifying their registered Contact-URI as a<br>
&gt; loose-route entry.&quot;<br>
&gt;<br>
&gt; BR,<br>
&gt; /Hans Erik van Elburg<br>
&gt;<br>
&gt;<br>
&gt; On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John<br>
&gt; &lt;<a href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@=
siemens-enterprise.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 The IETF does not have a mechanism, and that is the<br>
&gt; reason for the MARTINI work. In particular, the IETF has not<br>
&gt; published the so-called loose-route mechanism. Hence the<br>
&gt; reason for the IETF, as owner of SIP, to publish a mechanism<br>
&gt; for bulk registrations.<br>
&gt;<br>
&gt; =A0 =A0 =A0 John<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 &gt; -----Original Message-----<br>
&gt; =A0 =A0 =A0 &gt; From: Hans Erik van Elburg [mailto:<a href=3D"mailto:=
ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</a>]<br>
&gt; =A0 =A0 =A0 &gt; Sent: 26 March 2010 02:21<br>
&gt; =A0 =A0 =A0 &gt; To: <a href=3D"mailto:trac@localhost.amsl.com">trac@l=
ocalhost.amsl.com</a><br>
&gt; =A0 =A0 =A0 &gt; Cc: Elwell, John; <a href=3D"mailto:martini@ietf.org"=
>martini@ietf.org</a><br>
&gt; =A0 =A0 =A0 &gt; Subject: Re: [martini] #21: 3.2.2 describes an issue<=
br>
&gt; with some PBX<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; Then you should rephrase to what the real issue is:<b=
r>
&gt; =A0 =A0 =A0 &gt; &quot;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; Request-URI vs. loose-route acceptance<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; Some IP-PBX do not implement international standards =
or SIP<br>
&gt; =A0 =A0 =A0 &gt; profiles for SIP trunking. As a consequence some SIP-=
PBXs<br>
&gt; =A0 =A0 =A0 &gt; expect that inbound SIP requests from the SSP will ha=
ve the<br>
&gt; =A0 =A0 =A0 &gt; registered Contact-URI in the Request-URI, and thus n=
ot<br>
&gt; =A0 =A0 =A0 &gt; interoperate with the loose-route scheme of 3GPP and =
ETSI.<br>
&gt; =A0 =A0 =A0 &gt; Other SIP-PBXs are fine with the Request-URI being th=
e<br>
&gt; =A0 =A0 =A0 &gt; intended target, but cannot handle receiving a Route =
header<br>
&gt; =A0 =A0 =A0 &gt; field identifying their registered Contact-URI as a<b=
r>
&gt; =A0 =A0 =A0 &gt; loose-route entry.&quot;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; Is this an issue, yes. Does introducing yet another<b=
r>
&gt; profile help? No.<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; /Hans Erik van Elburg<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracke=
r<br>
&gt; =A0 =A0 =A0 &gt; &lt;<a href=3D"mailto:trac@tools.ietf.org">trac@tools=
.ietf.org</a>&gt; wrote:<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 #21: 3.2.2 describes an issue with some P=
BX<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; -------------------------------------+---------------=
---------<br>
&gt; =A0 =A0 =A0 &gt; --------------<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Reporter: =A0ietf.hanserik@... =A0 =A0=
 =A0 =A0 =A0| =A0 =A0 =A0 =A0Owner:<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0 =A0 Type: =A0defect =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 |<br>
&gt; Status: =A0closed<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Priority: =A0minor =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0|<br>
&gt; Milestone: =A0milestone1<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 Component: =A0reqs =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 |<br>
&gt; Version: =A01.0<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Severity: =A0In WG Last Call =A0 =A0 =
=A0 =A0 =A0|<br>
&gt; Resolution: =A0invalid<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; -------------------------------------+---------------=
---------<br>
&gt; =A0 =A0 =A0 &gt; --------------<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 Changes (by john.elwell@...):<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0* status: =A0new =3D&gt; closed<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0* resolution: =A0=3D&gt; invalid<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 Comment:<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0The text of 3.2.2 just underlines the =
fact that there<br>
&gt; =A0 =A0 =A0 &gt; are different<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0implementations around. A PBX that exp=
ects the loose<br>
&gt; =A0 =A0 =A0 &gt; route mechanism to be<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0used would fail to interwork with SSPs=
 using a<br>
&gt; =A0 =A0 =A0 &gt; different mechanism (e.g.,<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0SIPconnect 1.0), and a PBX not expecti=
ng the loose<br>
&gt; =A0 =A0 =A0 &gt; route mechanism to be<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0used would fail to interwork with a lo=
ose route<br>
&gt; =A0 =A0 =A0 &gt; implementation (e.g.,<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0ETSI/3GPP). Hence the urgent need for =
a standard.<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 --<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 Ticket URL:<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/21#co=
mment:1" target=3D"_blank">http://trac.tools.ietf.org/wg/martini/trac/ticke=
t/21#comment:1</a>&gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 martini &lt;<a href=3D"http://tools.ietf.=
org/martini/" target=3D"_blank">http://tools.ietf.org/martini/</a>&gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 _________________________________________=
______<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 martini mailing list<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 <a href=3D"mailto:martini@ietf.org">marti=
ni@ietf.org</a><br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 <a href=3D"https://www.ietf.org/mailman/l=
istinfo/martini" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ma=
rtini</a><br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt;<br>
&gt;<br>
&gt; </div></div></blockquote></div><br>

--001636c5a7faa4c88c0482f2fbfd--

From bruno.chatras@orange-ftgroup.com  Mon Mar 29 09:34:39 2010
Return-Path: <bruno.chatras@orange-ftgroup.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 92FB13A6A9A for <martini@core3.amsl.com>; Mon, 29 Mar 2010 09:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.482
X-Spam-Level: 
X-Spam-Status: No, score=0.482 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 SnF24588g5u3 for <martini@core3.amsl.com>; Mon, 29 Mar 2010 09:34:38 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id 80FBB3A6A75 for <martini@ietf.org>; Mon, 29 Mar 2010 09:34:31 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 7A263768010; Mon, 29 Mar 2010 18:34:59 +0200 (CEST)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id 6FC8B76800F; Mon, 29 Mar 2010 18:34:59 +0200 (CEST)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 29 Mar 2010 18:34:36 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CACF5D.B8EA5E2B"
Date: Mon, 29 Mar 2010 18:34:34 +0200
Message-ID: <9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNg
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com>
From: <bruno.chatras@orange-ftgroup.com>
To: <ietf.hanserik@gmail.com>, <john.elwell@siemens-enterprise.com>
X-OriginalArrivalTime: 29 Mar 2010 16:34:36.0984 (UTC) FILETIME=[B89F5B80:01CACF5D]
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 29 Mar 2010 16:34:39 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CACF5D.B8EA5E2B
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I fully agree with what Hans Erik has said in the Postscriptum "it would =
be really, really, really good if they (the IP PBX) would interwork on =
the UNI with the IMS business trunking". I believe that most operators =
share the same view... and presumably some vendors as well...
=20
________________________________

De : martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] De la =
part de Hans Erik van Elburg
Envoy=E9 : lundi 29 mars 2010 18:27
=C0 : Elwell, John
Cc : martini@ietf.org
Objet : Re: [martini] #21: 3.2.2 describes an issue with some PBX



	Hi John,
=09
	I was just trying to find a text that describes the issue.=20
=09
	But now the issue reads like "some PBX like apples, some like bananas". =
To me that does not sound like a usefull issue to describe in an RFC.
=09
	So I think one or two more sentence would make clear why this is an =
issue.
=09
	I think there is multiple underlying issues here:
	- PBX have different SIP profiles or all SIP-PBX are different
	- PBX support SIP trunking flavour A, or support SIP trunking flavour B
	- SSP systems don't know what mechanism the PBX support (can be =
resolved with explicit indicator, this draft proposes an indicator for =
flavour B but for another purpose it seems)
	- PBX do not know what SIP trunking flavour the SSP supports (not =
addressed it seems)
=09
	I don't seem to have a lucky hand with proposing an improved text, so =
maybe you should have a go at it.
=09
	BR,
	/Hans Erik van Elburg
=09
	p.s. I never said or implied that a SIP-PBX shall implement IMS. But it =
would be really, really, really good if they would interwork on the UNI =
with the IMS business trunking.  I think that should also be in your =
interest and in fact you have been part of that work...
=09
=09
=09
	On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John =
<john.elwell@siemens-enterprise.com> wrote:
=09

		Hans Erik,
	=09
		As an individual, I disagree with the proposed text, since it is =
misleading. The "international standards" to which you prefer are =
standards specific to an IMS environment. The implication of the wording =
as proposed is that SIP-PBXs ought to implement IMS specifications. And =
as Hadriel points out, implementing those IMS specifications does not =
eliminate the problems that the SIPconnect people are trying to solve. I =
believe the existing text in draft-03 is sufficient.
	=09

		John
	=09
		> -----Original Message-----
		> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
	=09
		> Sent: 26 March 2010 23:03
		> To: Elwell, John
		> Cc: martini@ietf.org
		> Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
		>
		> I will not argue with you about the validity of that argument.
		>
		> Can you agree to the modified text?
		>
		> "Request-URI vs. loose-route acceptance
		> Some IP-PBX do not implement international standards or SIP
		> profiles for SIP trunking. As a consequence some SIP-PBXs
		> expect that inbound SIP requests from the SSP will have the
		> registered Contact-URI in the Request-URI, and thus not
		> interoperate with the loose-route scheme of 3GPP and ETSI.
		> Other SIP-PBXs are fine with the Request-URI being the
		> intended target, but cannot handle receiving a Route header
		> field identifying their registered Contact-URI as a
		> loose-route entry."
		>
		> BR,
		> /Hans Erik van Elburg
		>
		>
		> On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
		> <john.elwell@siemens-enterprise.com> wrote:
		>
		>
		>       The IETF does not have a mechanism, and that is the
		> reason for the MARTINI work. In particular, the IETF has not
		> published the so-called loose-route mechanism. Hence the
		> reason for the IETF, as owner of SIP, to publish a mechanism
		> for bulk registrations.
		>
		>       John
		>
		>
		>       > -----Original Message-----
		>       > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
		>       > Sent: 26 March 2010 02:21
		>       > To: trac@localhost.amsl.com
		>       > Cc: Elwell, John; martini@ietf.org
		>       > Subject: Re: [martini] #21: 3.2.2 describes an issue
		> with some PBX
		>       >
		>       >
		>       > Then you should rephrase to what the real issue is:
		>       > "
		>       >
		>       >
		>       > Request-URI vs. loose-route acceptance
		>       >
		>       >
		>       > Some IP-PBX do not implement international standards or SIP
		>       > profiles for SIP trunking. As a consequence some SIP-PBXs
		>       > expect that inbound SIP requests from the SSP will have the
		>       > registered Contact-URI in the Request-URI, and thus not
		>       > interoperate with the loose-route scheme of 3GPP and ETSI.
		>       > Other SIP-PBXs are fine with the Request-URI being the
		>       > intended target, but cannot handle receiving a Route header
		>       > field identifying their registered Contact-URI as a
		>       > loose-route entry."
		>       >
		>       >
		>       > Is this an issue, yes. Does introducing yet another
		> profile help? No.
		>       >
		>       > /Hans Erik van Elburg
		>       >
		>       >
		>       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
		>       > <trac@tools.ietf.org> wrote:
		>       >
		>       >
		>       >       #21: 3.2.2 describes an issue with some PBX
		>       >
		>       > =
-------------------------------------+------------------------
		>       > --------------
		>       >        Reporter:  ietf.hanserik@...          |        Owner:
		>       >
		>       >           Type:  defect                   |
		> Status:  closed
		>       >
		>       >        Priority:  minor                    |
		> Milestone:  milestone1
		>       >       Component:  reqs                     |
		> Version:  1.0
		>       >
		>       >        Severity:  In WG Last Call          |
		> Resolution:  invalid
		>       >        Keywords:                           |
		>       >
		>       > =
-------------------------------------+------------------------
		>       > --------------
		>       >       Changes (by john.elwell@...):
		>       >
		>       >        * status:  new =3D> closed
		>       >        * resolution:  =3D> invalid
		>       >
		>       >
		>       >       Comment:
		>       >
		>       >
		>       >        The text of 3.2.2 just underlines the fact that there
		>       > are different
		>       >        implementations around. A PBX that expects the loose
		>       > route mechanism to be
		>       >        used would fail to interwork with SSPs using a
		>       > different mechanism (e.g.,
		>       >        SIPconnect 1.0), and a PBX not expecting the loose
		>       > route mechanism to be
		>       >        used would fail to interwork with a loose route
		>       > implementation (e.g.,
		>       >        ETSI/3GPP). Hence the urgent need for a standard.
		>       >
		>       >       --
		>       >       Ticket URL:
		>       >
		> <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
		>       >
		>       >       martini <http://tools.ietf.org/martini/>
		>       >
		>       >
		>       >       _______________________________________________
		>       >       martini mailing list
		>       >       martini@ietf.org
		>       >       https://www.ietf.org/mailman/listinfo/martini
		>       >
		>       >
		>       >
		>       >
		>
		>
		>=20



------_=_NextPart_001_01CACF5D.B8EA5E2B
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D260352916-29032010><FONT =
face=3DArial size=3D2>I=20
fully agree with what Hans Erik has said in the Postscriptum&nbsp;"it =
would be=20
really, really, really good if they (the IP PBX) would interwork on the =
UNI with=20
the IMS business trunking".&nbsp;I believe that most operators share the =
same=20
view... and presumably some vendors as well...</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D260352916-29032010><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DTahoma =
size=3D2><B>De&nbsp;:</B>=20
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <B>De la part =
de</B>=20
Hans Erik van Elburg<BR><B>Envoy=E9&nbsp;:</B> lundi 29 mars 2010=20
18:27<BR><B>=C0&nbsp;:</B> Elwell, John<BR><B>Cc&nbsp;:</B>=20
martini@ietf.org<BR><B>Objet&nbsp;:</B> Re: [martini] #21: 3.2.2 =
describes an=20
issue with some PBX<BR></FONT><BR></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>Hi John,<BR><BR>I was just trying to find a text that =
describes the=20
  issue. <BR><BR>But now the issue reads like "some PBX like apples, =
some like=20
  bananas". To me that does not sound like a usefull issue to describe =
in an=20
  RFC.<BR><BR>So I think one or two more sentence would make clear why =
this is=20
  an issue.<BR><BR>I think there is multiple underlying issues =
here:<BR>- PBX=20
  have different SIP profiles or all SIP-PBX are different<BR>- PBX =
support SIP=20
  trunking flavour A, or support SIP trunking flavour B<BR>- SSP systems =
don't=20
  know what mechanism the PBX support (can be resolved with explicit =
indicator,=20
  this draft proposes an indicator for flavour B but for another purpose =
it=20
  seems)<BR>- PBX do not know what SIP trunking flavour the SSP supports =
(not=20
  addressed it seems)<BR><BR>I don't seem to have a lucky hand with =
proposing an=20
  improved text, so maybe you should have a go at =
it.<BR><BR>BR,<BR>/Hans Erik=20
  van Elburg<BR><BR>p.s. I never said or implied that a SIP-PBX shall =
implement=20
  IMS. But it would be really, really, really good if they would =
interwork on=20
  the UNI with the IMS business trunking.&nbsp; I think that should also =
be in=20
  your interest and in fact you have been part of that =
work...<BR><BR><BR>
  <DIV class=3Dgmail_quote>On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John =
<SPAN=20
  dir=3Dltr>&lt;<A=20
  =
href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-en=
terprise.com</A>&gt;</SPAN>=20
  wrote:<BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">Hans=20
    Erik,<BR><BR>As an individual, I disagree with the proposed text, =
since it=20
    is misleading. The "international standards" to which you prefer are =

    standards specific to an IMS environment. The implication of the =
wording as=20
    proposed is that SIP-PBXs ought to implement IMS specifications. And =
as=20
    Hadriel points out, implementing those IMS specifications does not =
eliminate=20
    the problems that the SIPconnect people are trying to solve. I =
believe the=20
    existing text in draft-03 is sufficient.<BR>
    <DIV class=3Dim><BR>John<BR><BR>&gt; -----Original =
Message-----<BR>&gt; From:=20
    Hans Erik van Elburg [mailto:<A=20
    =
href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</A>]<BR><=
/DIV>
    <DIV>
    <DIV></DIV>
    <DIV class=3Dh5>&gt; Sent: 26 March 2010 23:03<BR>&gt; To: Elwell,=20
    John<BR>&gt; Cc: <A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; =
Subject: Re:=20
    [martini] #21: 3.2.2 describes an issue with some =
PBX<BR>&gt;<BR>&gt; I will=20
    not argue with you about the validity of that =
argument.<BR>&gt;<BR>&gt; Can=20
    you agree to the modified text?<BR>&gt;<BR>&gt; "Request-URI vs. =
loose-route=20
    acceptance<BR>&gt; Some IP-PBX do not implement international =
standards or=20
    SIP<BR>&gt; profiles for SIP trunking. As a consequence some=20
    SIP-PBXs<BR>&gt; expect that inbound SIP requests from the SSP will =
have=20
    the<BR>&gt; registered Contact-URI in the Request-URI, and thus =
not<BR>&gt;=20
    interoperate with the loose-route scheme of 3GPP and ETSI.<BR>&gt; =
Other=20
    SIP-PBXs are fine with the Request-URI being the<BR>&gt; intended =
target,=20
    but cannot handle receiving a Route header<BR>&gt; field identifying =
their=20
    registered Contact-URI as a<BR>&gt; loose-route =
entry."<BR>&gt;<BR>&gt;=20
    BR,<BR>&gt; /Hans Erik van Elburg<BR>&gt;<BR>&gt;<BR>&gt; On Fri, =
Mar 26,=20
    2010 at 9:03 PM, Elwell, John<BR>&gt; &lt;<A=20
    =
href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-en=
terprise.com</A>&gt;=20
    wrote:<BR>&gt;<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; The IETF does =
not have a=20
    mechanism, and that is the<BR>&gt; reason for the MARTINI work. In=20
    particular, the IETF has not<BR>&gt; published the so-called =
loose-route=20
    mechanism. Hence the<BR>&gt; reason for the IETF, as owner of SIP, =
to=20
    publish a mechanism<BR>&gt; for bulk registrations.<BR>&gt;<BR>&gt; =
&nbsp;=20
    &nbsp; &nbsp; John<BR>&gt;<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; =

    -----Original Message-----<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; From: =
Hans Erik=20
    van Elburg [mailto:<A=20
    =
href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</A>]<BR>&=
gt;=20
    &nbsp; &nbsp; &nbsp; &gt; Sent: 26 March 2010 02:21<BR>&gt; &nbsp; =
&nbsp;=20
    &nbsp; &gt; To: <A=20
    =
href=3D"mailto:trac@localhost.amsl.com">trac@localhost.amsl.com</A><BR>&g=
t;=20
    &nbsp; &nbsp; &nbsp; &gt; Cc: Elwell, John; <A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; &nbsp; =
&nbsp;=20
    &nbsp; &gt; Subject: Re: [martini] #21: 3.2.2 describes an =
issue<BR>&gt;=20
    with some PBX<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; =
&nbsp; &nbsp;=20
    &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Then you should rephrase to =
what the=20
    real issue is:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; "<BR>&gt; &nbsp; =
&nbsp;=20
    &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; =
&nbsp;=20
    &gt; Request-URI vs. loose-route acceptance<BR>&gt; &nbsp; &nbsp; =
&nbsp;=20
    &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; =
&gt;=20
    Some IP-PBX do not implement international standards or SIP<BR>&gt; =
&nbsp;=20
    &nbsp; &nbsp; &gt; profiles for SIP trunking. As a consequence some=20
    SIP-PBXs<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; expect that inbound SIP =
requests=20
    from the SSP will have the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; =
registered=20
    Contact-URI in the Request-URI, and thus not<BR>&gt; &nbsp; &nbsp; =
&nbsp;=20
    &gt; interoperate with the loose-route scheme of 3GPP and =
ETSI.<BR>&gt;=20
    &nbsp; &nbsp; &nbsp; &gt; Other SIP-PBXs are fine with the =
Request-URI being=20
    the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; intended target, but cannot =
handle=20
    receiving a Route header<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; field =
identifying=20
    their registered Contact-URI as a<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=20
    loose-route entry."<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; =
&nbsp;=20
    &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Is this an issue, yes. =
Does=20
    introducing yet another<BR>&gt; profile help? No.<BR>&gt; &nbsp; =
&nbsp;=20
    &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; /Hans Erik van =
Elburg<BR>&gt;=20
    &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; =
&nbsp;=20
    &nbsp; &nbsp; &gt; On Thu, Mar 25, 2010 at 9:22 PM, martini issue=20
    tracker<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &lt;<A=20
    href=3D"mailto:trac@tools.ietf.org">trac@tools.ietf.org</A>&gt; =
wrote:<BR>&gt;=20
    &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; =
&nbsp;=20
    &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; #21: 3.2.2 describes an =
issue with=20
    some PBX<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; =
&nbsp; &gt;=20
    =
-------------------------------------+------------------------<BR>&gt;=20
    &nbsp; &nbsp; &nbsp; &gt; --------------<BR>&gt; &nbsp; &nbsp; =
&nbsp; &gt;=20
    &nbsp; &nbsp; &nbsp; &nbsp;Reporter: &nbsp;ietf.hanserik@... &nbsp; =
&nbsp;=20
    &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;Owner:<BR>&gt; =
&nbsp;=20
    &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; =
&nbsp;=20
    &nbsp; &nbsp; Type: &nbsp;defect &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=20
    &nbsp; &nbsp; &nbsp; |<BR>&gt; Status: &nbsp;closed<BR>&gt; &nbsp; =
&nbsp;=20
    &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
    &nbsp;Priority: &nbsp;minor &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;=20
    &nbsp; &nbsp; &nbsp;|<BR>&gt; Milestone: &nbsp;milestone1<BR>&gt; =
&nbsp;=20
    &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; Component: &nbsp;reqs &nbsp; =
&nbsp;=20
    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<BR>&gt; =
Version:=20
    &nbsp;1.0<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; =
&nbsp;=20
    &gt; &nbsp; &nbsp; &nbsp; &nbsp;Severity: &nbsp;In WG Last Call =
&nbsp;=20
    &nbsp; &nbsp; &nbsp; &nbsp;|<BR>&gt; Resolution: =
&nbsp;invalid<BR>&gt;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Keywords: =
&nbsp; &nbsp;=20
    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;=20
    |<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; =
&gt;=20
    =
-------------------------------------+------------------------<BR>&gt;=20
    &nbsp; &nbsp; &nbsp; &gt; --------------<BR>&gt; &nbsp; &nbsp; =
&nbsp; &gt;=20
    &nbsp; &nbsp; &nbsp; Changes (by john.elwell@...):<BR>&gt; &nbsp; =
&nbsp;=20
    &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; =
&nbsp;*=20
    status: &nbsp;new =3D&gt; closed<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; =
&nbsp;=20
    &nbsp; &nbsp; &nbsp;* resolution: &nbsp;=3D&gt; invalid<BR>&gt; =
&nbsp; &nbsp;=20
    &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; =
&nbsp;=20
    &gt; &nbsp; &nbsp; &nbsp; Comment:<BR>&gt; &nbsp; &nbsp; &nbsp; =
&gt;<BR>&gt;=20
    &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; =
&nbsp;=20
    &nbsp; &nbsp;The text of 3.2.2 just underlines the fact that =
there<BR>&gt;=20
    &nbsp; &nbsp; &nbsp; &gt; are different<BR>&gt; &nbsp; &nbsp; &nbsp; =
&gt;=20
    &nbsp; &nbsp; &nbsp; &nbsp;implementations around. A PBX that =
expects the=20
    loose<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; route mechanism to =
be<BR>&gt; &nbsp;=20
    &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;used would fail to =
interwork=20
    with SSPs using a<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; different =
mechanism=20
    (e.g.,<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
    &nbsp;SIPconnect 1.0), and a PBX not expecting the loose<BR>&gt; =
&nbsp;=20
    &nbsp; &nbsp; &gt; route mechanism to be<BR>&gt; &nbsp; &nbsp; =
&nbsp; &gt;=20
    &nbsp; &nbsp; &nbsp; &nbsp;used would fail to interwork with a loose =

    route<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; implementation =
(e.g.,<BR>&gt; &nbsp;=20
    &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;ETSI/3GPP). Hence the =
urgent=20
    need for a standard.<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; =
&nbsp; &nbsp;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; --<BR>&gt; &nbsp; &nbsp; &nbsp; =
&gt; &nbsp;=20
    &nbsp; &nbsp; Ticket URL:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; =
&lt;<A=20
    =
href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1"=20
    =
target=3D_blank>http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comm=
ent:1</A>&gt;<BR>&gt;=20
    &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; =
&nbsp;=20
    &nbsp; martini &lt;<A href=3D"http://tools.ietf.org/martini/"=20
    target=3D_blank>http://tools.ietf.org/martini/</A>&gt;<BR>&gt; =
&nbsp; &nbsp;=20
    &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; =
&nbsp;=20
    &gt; &nbsp; &nbsp; &nbsp;=20
    _______________________________________________<BR>&gt; &nbsp; =
&nbsp; &nbsp;=20
    &gt; &nbsp; &nbsp; &nbsp; martini mailing list<BR>&gt; &nbsp; &nbsp; =
&nbsp;=20
    &gt; &nbsp; &nbsp; &nbsp; <A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; &nbsp; =
&nbsp;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; <A=20
    href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
    =
target=3D_blank>https://www.ietf.org/mailman/listinfo/martini</A><BR>&gt;=
=20
    &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; =
&nbsp;=20
    &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; =
&gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
    </DIV></DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CACF5D.B8EA5E2B--

From richard@shockey.us  Mon Mar 29 10:07:14 2010
Return-Path: <richard@shockey.us>
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 C1C303A6AF1 for <martini@core3.amsl.com>; Mon, 29 Mar 2010 10:07:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.131
X-Spam-Level: *
X-Spam-Status: No, score=1.131 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 6MM5cKQtatB1 for <martini@core3.amsl.com>; Mon, 29 Mar 2010 10:07:13 -0700 (PDT)
Received: from outbound-mail-360.bluehost.com (outbound-mail-360.bluehost.com [66.147.249.254]) by core3.amsl.com (Postfix) with SMTP id D2EE93A6AEB for <martini@ietf.org>; Mon, 29 Mar 2010 10:07:12 -0700 (PDT)
Received: (qmail 5790 invoked by uid 0); 29 Mar 2010 17:07:41 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy2.bluehost.com with SMTP; 29 Mar 2010 17:07:41 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=YdmYWsQeWgrPm93VM2B5qtVIvpQ6mq8M6mUBgNu21rxNX95HIGiODtHxzkrMUrB/aUi00U1lPZsfjJkSSvJx2eBgzP+x/YJH1jxS9ApN99hiZcxyrAR9nAHfJcnvdcM4;
Received: from pool-173-66-69-79.washdc.fios.verizon.net ([173.66.69.79] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from <richard@shockey.us>) id 1NwIRA-0002jU-HZ; Mon, 29 Mar 2010 11:07:41 -0600
From: "Richard Shockey" <richard@shockey.us>
To: <bruno.chatras@orange-ftgroup.com>, <ietf.hanserik@gmail.com>, <john.elwell@siemens-enterprise.com>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net>	<g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com> <9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr>
Date: Mon, 29 Mar 2010 13:07:36 -0400
Message-ID: <011a01cacf62$55509710$fff1c530$@us>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_011B_01CACF40.CE3EF710"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNgAAFPnSA=
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.66.69.79 authed with richard@shockey.us}
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 29 Mar 2010 17:07:14 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_011B_01CACF40.CE3EF710
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Has any of this IMS business trunking stuff actually deployed?

=20

From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On =
Behalf
Of bruno.chatras@orange-ftgroup.com
Sent: Monday, March 29, 2010 12:35 PM
To: ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

=20

I fully agree with what Hans Erik has said in the Postscriptum "it would =
be
really, really, really good if they (the IP PBX) would interwork on the =
UNI
with the IMS business trunking". I believe that most operators share the
same view... and presumably some vendors as well...

=20

  _____ =20

De : martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] De la =
part
de Hans Erik van Elburg
Envoy=E9 : lundi 29 mars 2010 18:27
=C0 : Elwell, John
Cc : martini@ietf.org
Objet : Re: [martini] #21: 3.2.2 describes an issue with some PBX

Hi John,

I was just trying to find a text that describes the issue.=20

But now the issue reads like "some PBX like apples, some like bananas". =
To
me that does not sound like a usefull issue to describe in an RFC.

So I think one or two more sentence would make clear why this is an =
issue.

I think there is multiple underlying issues here:
- PBX have different SIP profiles or all SIP-PBX are different
- PBX support SIP trunking flavour A, or support SIP trunking flavour B
- SSP systems don't know what mechanism the PBX support (can be resolved
with explicit indicator, this draft proposes an indicator for flavour B =
but
for another purpose it seems)
- PBX do not know what SIP trunking flavour the SSP supports (not =
addressed
it seems)

I don't seem to have a lucky hand with proposing an improved text, so =
maybe
you should have a go at it.

BR,
/Hans Erik van Elburg

p.s. I never said or implied that a SIP-PBX shall implement IMS. But it
would be really, really, really good if they would interwork on the UNI =
with
the IMS business trunking.  I think that should also be in your interest =
and
in fact you have been part of that work...



On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John
<john.elwell@siemens-enterprise.com> wrote:

Hans Erik,

As an individual, I disagree with the proposed text, since it is =
misleading.
The "international standards" to which you prefer are standards specific =
to
an IMS environment. The implication of the wording as proposed is that
SIP-PBXs ought to implement IMS specifications. And as Hadriel points =
out,
implementing those IMS specifications does not eliminate the problems =
that
the SIPconnect people are trying to solve. I believe the existing text =
in
draft-03 is sufficient.


John

> -----Original Message-----
> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]

> Sent: 26 March 2010 23:03
> To: Elwell, John
> Cc: martini@ietf.org
> Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>
> I will not argue with you about the validity of that argument.
>
> Can you agree to the modified text?
>
> "Request-URI vs. loose-route acceptance
> Some IP-PBX do not implement international standards or SIP
> profiles for SIP trunking. As a consequence some SIP-PBXs
> expect that inbound SIP requests from the SSP will have the
> registered Contact-URI in the Request-URI, and thus not
> interoperate with the loose-route scheme of 3GPP and ETSI.
> Other SIP-PBXs are fine with the Request-URI being the
> intended target, but cannot handle receiving a Route header
> field identifying their registered Contact-URI as a
> loose-route entry."
>
> BR,
> /Hans Erik van Elburg
>
>
> On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
> <john.elwell@siemens-enterprise.com> wrote:
>
>
>       The IETF does not have a mechanism, and that is the
> reason for the MARTINI work. In particular, the IETF has not
> published the so-called loose-route mechanism. Hence the
> reason for the IETF, as owner of SIP, to publish a mechanism
> for bulk registrations.
>
>       John
>
>
>       > -----Original Message-----
>       > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
>       > Sent: 26 March 2010 02:21
>       > To: trac@localhost.amsl.com
>       > Cc: Elwell, John; martini@ietf.org
>       > Subject: Re: [martini] #21: 3.2.2 describes an issue
> with some PBX
>       >
>       >
>       > Then you should rephrase to what the real issue is:
>       > "
>       >
>       >
>       > Request-URI vs. loose-route acceptance
>       >
>       >
>       > Some IP-PBX do not implement international standards or SIP
>       > profiles for SIP trunking. As a consequence some SIP-PBXs
>       > expect that inbound SIP requests from the SSP will have the
>       > registered Contact-URI in the Request-URI, and thus not
>       > interoperate with the loose-route scheme of 3GPP and ETSI.
>       > Other SIP-PBXs are fine with the Request-URI being the
>       > intended target, but cannot handle receiving a Route header
>       > field identifying their registered Contact-URI as a
>       > loose-route entry."
>       >
>       >
>       > Is this an issue, yes. Does introducing yet another
> profile help? No.
>       >
>       > /Hans Erik van Elburg
>       >
>       >
>       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
>       > <trac@tools.ietf.org> wrote:
>       >
>       >
>       >       #21: 3.2.2 describes an issue with some PBX
>       >
>       > -------------------------------------+------------------------
>       > --------------
>       >        Reporter:  ietf.hanserik@...          |        Owner:
>       >
>       >           Type:  defect                   |
> Status:  closed
>       >
>       >        Priority:  minor                    |
> Milestone:  milestone1
>       >       Component:  reqs                     |
> Version:  1.0
>       >
>       >        Severity:  In WG Last Call          |
> Resolution:  invalid
>       >        Keywords:                           |
>       >
>       > -------------------------------------+------------------------
>       > --------------
>       >       Changes (by john.elwell@...):
>       >
>       >        * status:  new =3D> closed
>       >        * resolution:  =3D> invalid
>       >
>       >
>       >       Comment:
>       >
>       >
>       >        The text of 3.2.2 just underlines the fact that there
>       > are different
>       >        implementations around. A PBX that expects the loose
>       > route mechanism to be
>       >        used would fail to interwork with SSPs using a
>       > different mechanism (e.g.,
>       >        SIPconnect 1.0), and a PBX not expecting the loose
>       > route mechanism to be
>       >        used would fail to interwork with a loose route
>       > implementation (e.g.,
>       >        ETSI/3GPP). Hence the urgent need for a standard.
>       >
>       >       --
>       >       Ticket URL:
>       >
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
>       >
>       >       martini <http://tools.ietf.org/martini/>
>       >
>       >
>       >       _______________________________________________
>       >       martini mailing list
>       >       martini@ietf.org
>       >       https://www.ietf.org/mailman/listinfo/martini
>       >
>       >
>       >
>       >
>
>
>=20

=20


------=_NextPart_000_011B_01CACF40.CE3EF710
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>

<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Has any of this IMS business trunking stuff actually =
deployed?<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <b>On Behalf =
Of </b>bruno.chatras@orange-ftgroup.com<br>
<b>Sent:</b> Monday, March 29, 2010 12:35 PM<br>
<b>To:</b> ietf.hanserik@gmail.com; =
john.elwell@siemens-enterprise.com<br>
<b>Cc:</b> martini@ietf.org<br>
<b>Subject:</b> Re: [martini] #21: 3.2.2 describes an issue with some =
PBX<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>I
fully agree with what Hans Erik has said in the =
Postscriptum&nbsp;&quot;it
would be really, really, really good if they (the IP PBX) would =
interwork on
the UNI with the IMS business trunking&quot;.&nbsp;I believe that most
operators share the same view... and presumably some vendors as =
well...</span><o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D3 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><span =
style=3D'font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>De&nbsp;:</span></b><span =
style=3D'font-size:
10.0pt;font-family:"Tahoma","sans-serif"'> martini-bounces@ietf.org
[mailto:martini-bounces@ietf.org] <b>De la part de</b> Hans Erik van =
Elburg<br>
<b>Envoy=E9&nbsp;:</b> lundi 29 mars 2010 18:27<br>
<b>=C0&nbsp;:</b> Elwell, John<br>
<b>Cc&nbsp;:</b> martini@ietf.org<br>
<b>Objet&nbsp;:</b> Re: [martini] #21: 3.2.2 describes an issue with =
some PBX</span><o:p></o:p></p>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 3.0pt;
margin-left:3.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>=


<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Hi John,<br>
<br>
I was just trying to find a text that describes the issue. <br>
<br>
But now the issue reads like &quot;some PBX like apples, some like
bananas&quot;. To me that does not sound like a usefull issue to =
describe in an
RFC.<br>
<br>
So I think one or two more sentence would make clear why this is an =
issue.<br>
<br>
I think there is multiple underlying issues here:<br>
- PBX have different SIP profiles or all SIP-PBX are different<br>
- PBX support SIP trunking flavour A, or support SIP trunking flavour =
B<br>
- SSP systems don't know what mechanism the PBX support (can be resolved =
with
explicit indicator, this draft proposes an indicator for flavour B but =
for
another purpose it seems)<br>
- PBX do not know what SIP trunking flavour the SSP supports (not =
addressed it
seems)<br>
<br>
I don't seem to have a lucky hand with proposing an improved text, so =
maybe you
should have a go at it.<br>
<br>
BR,<br>
/Hans Erik van Elburg<br>
<br>
p.s. I never said or implied that a SIP-PBX shall implement IMS. But it =
would
be really, really, really good if they would interwork on the UNI with =
the IMS
business trunking.&nbsp; I think that should also be in your interest =
and in
fact you have been part of that work...<br>
<br>
<o:p></o:p></p>

<div>

<p class=3DMsoNormal>On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John =
&lt;<a
href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-en=
terprise.com</a>&gt;
wrote:<o:p></o:p></p>

<p class=3DMsoNormal>Hans Erik,<br>
<br>
As an individual, I disagree with the proposed text, since it is =
misleading.
The &quot;international standards&quot; to which you prefer are =
standards
specific to an IMS environment. The implication of the wording as =
proposed is
that SIP-PBXs ought to implement IMS specifications. And as Hadriel =
points out,
implementing those IMS specifications does not eliminate the problems =
that the
SIPconnect people are trying to solve. I believe the existing text in =
draft-03
is sufficient.<o:p></o:p></p>

<div>

<p class=3DMsoNormal><br>
John<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Hans Erik van Elburg [mailto:<a =
href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</a>]<o:p>=
</o:p></p>

</div>

<div>

<div>

<p class=3DMsoNormal>&gt; Sent: 26 March 2010 23:03<br>
&gt; To: Elwell, John<br>
&gt; Cc: <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; Subject: Re: [martini] #21: 3.2.2 describes an issue with some =
PBX<br>
&gt;<br>
&gt; I will not argue with you about the validity of that argument.<br>
&gt;<br>
&gt; Can you agree to the modified text?<br>
&gt;<br>
&gt; &quot;Request-URI vs. loose-route acceptance<br>
&gt; Some IP-PBX do not implement international standards or SIP<br>
&gt; profiles for SIP trunking. As a consequence some SIP-PBXs<br>
&gt; expect that inbound SIP requests from the SSP will have the<br>
&gt; registered Contact-URI in the Request-URI, and thus not<br>
&gt; interoperate with the loose-route scheme of 3GPP and ETSI.<br>
&gt; Other SIP-PBXs are fine with the Request-URI being the<br>
&gt; intended target, but cannot handle receiving a Route header<br>
&gt; field identifying their registered Contact-URI as a<br>
&gt; loose-route entry.&quot;<br>
&gt;<br>
&gt; BR,<br>
&gt; /Hans Erik van Elburg<br>
&gt;<br>
&gt;<br>
&gt; On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John<br>
&gt; &lt;<a =
href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-en=
terprise.com</a>&gt;
wrote:<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; The IETF does not have a mechanism, and that =
is the<br>
&gt; reason for the MARTINI work. In particular, the IETF has not<br>
&gt; published the so-called loose-route mechanism. Hence the<br>
&gt; reason for the IETF, as owner of SIP, to publish a mechanism<br>
&gt; for bulk registrations.<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; John<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; -----Original Message-----<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; From: Hans Erik van Elburg [mailto:<a
href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</a>]<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; Sent: 26 March 2010 02:21<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; To: <a =
href=3D"mailto:trac@localhost.amsl.com">trac@localhost.amsl.com</a><br>
&gt; &nbsp; &nbsp; &nbsp; &gt; Cc: Elwell, John; <a
href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; &nbsp; &nbsp; &nbsp; &gt; Subject: Re: [martini] #21: 3.2.2 =
describes an
issue<br>
&gt; with some PBX<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; Then you should rephrase to what the real =
issue
is:<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &quot;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; Request-URI vs. loose-route =
acceptance<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; Some IP-PBX do not implement =
international
standards or SIP<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; profiles for SIP trunking. As a =
consequence some
SIP-PBXs<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; expect that inbound SIP requests from the =
SSP
will have the<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; registered Contact-URI in the =
Request-URI, and
thus not<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; interoperate with the loose-route scheme =
of 3GPP
and ETSI.<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; Other SIP-PBXs are fine with the =
Request-URI
being the<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; intended target, but cannot handle =
receiving a
Route header<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; field identifying their registered =
Contact-URI
as a<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; loose-route entry.&quot;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; Is this an issue, yes. Does introducing =
yet
another<br>
&gt; profile help? No.<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; /Hans Erik van Elburg<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; On Thu, Mar 25, 2010 at 9:22 PM, martini =
issue
tracker<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &lt;<a =
href=3D"mailto:trac@tools.ietf.org">trac@tools.ietf.org</a>&gt;
wrote:<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; #21: 3.2.2 describes =
an
issue with some PBX<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;
-------------------------------------+------------------------<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; --------------<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Reporter:
&nbsp;ietf.hanserik@... &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; =
&nbsp;
&nbsp; &nbsp;Owner:<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Type:
&nbsp;defect &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; |<br>
&gt; Status: &nbsp;closed<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Priority: =
&nbsp;minor
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;|<br>
&gt; Milestone: &nbsp;milestone1<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; Component: =
&nbsp;reqs
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
|<br>
&gt; Version: &nbsp;1.0<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Severity: =
&nbsp;In WG
Last Call &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|<br>
&gt; Resolution: &nbsp;invalid<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Keywords: =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; |<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; =
-------------------------------------+------------------------<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; --------------<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; Changes (by
john.elwell@...):<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;* status: =
&nbsp;new
=3D&gt; closed<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;* resolution:
&nbsp;=3D&gt; invalid<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; Comment:<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;The text of =
3.2.2
just underlines the fact that there<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; are different<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; =
&nbsp;implementations
around. A PBX that expects the loose<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; route mechanism to be<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;used would =
fail to
interwork with SSPs using a<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; different mechanism (e.g.,<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;SIPconnect =
1.0), and
a PBX not expecting the loose<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; route mechanism to be<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;used would =
fail to
interwork with a loose route<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; implementation (e.g.,<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;ETSI/3GPP). =
Hence the
urgent need for a standard.<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; --<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; Ticket URL:<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &lt;<a
href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1"
target=3D"_blank">http://trac.tools.ietf.org/wg/martini/trac/ticket/21#co=
mment:1</a>&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; martini &lt;<a
href=3D"http://tools.ietf.org/martini/" =
target=3D"_blank">http://tools.ietf.org/martini/</a>&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;
_______________________________________________<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; martini mailing =
list<br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; <a
href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; <a
href=3D"https://www.ietf.org/mailman/listinfo/martini" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/martini</a><br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &gt;<br>
&gt;<br>
&gt;<br>
&gt; <o:p></o:p></p>

</div>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</blockquote>

</div>

</body>

</html>

------=_NextPart_000_011B_01CACF40.CE3EF710--


From ietf.hanserik@gmail.com  Mon Mar 29 10:17:57 2010
Return-Path: <ietf.hanserik@gmail.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 F31263A6AF6 for <martini@core3.amsl.com>; Mon, 29 Mar 2010 10:17:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.755
X-Spam-Level: 
X-Spam-Status: No, score=0.755 tagged_above=-999 required=5 tests=[AWL=-0.377,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 jza299mlWmbu for <martini@core3.amsl.com>; Mon, 29 Mar 2010 10:17:55 -0700 (PDT)
Received: from mail-ew0-f224.google.com (mail-ew0-f224.google.com [209.85.219.224]) by core3.amsl.com (Postfix) with ESMTP id 57E3D3A6ACA for <martini@ietf.org>; Mon, 29 Mar 2010 10:17:45 -0700 (PDT)
Received: by ewy24 with SMTP id 24so840907ewy.13 for <martini@ietf.org>; Mon, 29 Mar 2010 10:18:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=Mqr+D48FMbAn3vv+yBJQ19y5ErRAs7c/zo6YUNsm7Rc=; b=AV+eTGmMD6Q1uoKEZ4Pb+3xNe9jLgYm+B4akiKPMIpXvALgqRUBsyG9YHH3oBWo3Qh sVFNmVhA6vaWD04L9j3rOhtRjZkfThYRjzGdrb/kGfCdsISbRS9oNbNzcFBD61S3b5Xj p6xM0rQ6rCLCNz3uABncfgMcHCaK8Xz/gPKe4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LAdTLqKY/2+LSLJazvvnzrxPR0I9BB4YUPQYeuxdbboNQRGHDbWyr32lG82kS2fA9z 1qDd1hPYZp059Hc9PvC9nmprpodjmHPil8kY8ZLAD/N5ZtNhpnO6F/b/BGJ/DKPFDsZP 5P6uqP7tO+EwlssJDl9antiwzcB1JMsoecXBI=
MIME-Version: 1.0
Received: by 10.213.15.138 with HTTP; Mon, 29 Mar 2010 10:18:09 -0700 (PDT)
In-Reply-To: <011a01cacf62$55509710$fff1c530$@us>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org> <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net> <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com> <9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr> <011a01cacf62$55509710$fff1c530$@us>
Date: Mon, 29 Mar 2010 19:18:09 +0200
Received: by 10.213.37.133 with SMTP id x5mr498891ebd.24.1269883089297; Mon,  29 Mar 2010 10:18:09 -0700 (PDT)
Message-ID: <s2w9ae56b1e1003291018r36429fbby26fc05d74e7d887f@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: Richard Shockey <richard@shockey.us>
Content-Type: multipart/alternative; boundary=00148530ad9f71a1cb0482f3b2ee
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 29 Mar 2010 17:17:57 -0000

--00148530ad9f71a1cb0482f3b2ee
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Yes, there exist IMS business trunking solutions in several countries.

/Hans Erik van Elburg

On Mon, Mar 29, 2010 at 7:07 PM, Richard Shockey <richard@shockey.us> wrote=
:

>  Has any of this IMS business trunking stuff actually deployed?
>
>
>
> *From:* martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] *On
> Behalf Of *bruno.chatras@orange-ftgroup.com
> *Sent:* Monday, March 29, 2010 12:35 PM
> *To:* ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com
>
> *Cc:* martini@ietf.org
> *Subject:* Re: [martini] #21: 3.2.2 describes an issue with some PBX
>
>
>
> I fully agree with what Hans Erik has said in the Postscriptum "it would =
be
> really, really, really good if they (the IP PBX) would interwork on the U=
NI
> with the IMS business trunking". I believe that most operators share the
> same view... and presumably some vendors as well...
>
>
>  ------------------------------
>
> *De :* martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] *De la
> part de* Hans Erik van Elburg
> *Envoy=E9 :* lundi 29 mars 2010 18:27
> *=C0 :* Elwell, John
> *Cc :* martini@ietf.org
> *Objet :* Re: [martini] #21: 3.2.2 describes an issue with some PBX
>
> Hi John,
>
> I was just trying to find a text that describes the issue.
>
> But now the issue reads like "some PBX like apples, some like bananas". T=
o
> me that does not sound like a usefull issue to describe in an RFC.
>
> So I think one or two more sentence would make clear why this is an issue=
.
>
> I think there is multiple underlying issues here:
> - PBX have different SIP profiles or all SIP-PBX are different
> - PBX support SIP trunking flavour A, or support SIP trunking flavour B
> - SSP systems don't know what mechanism the PBX support (can be resolved
> with explicit indicator, this draft proposes an indicator for flavour B b=
ut
> for another purpose it seems)
> - PBX do not know what SIP trunking flavour the SSP supports (not address=
ed
> it seems)
>
> I don't seem to have a lucky hand with proposing an improved text, so may=
be
> you should have a go at it.
>
> BR,
> /Hans Erik van Elburg
>
> p.s. I never said or implied that a SIP-PBX shall implement IMS. But it
> would be really, really, really good if they would interwork on the UNI w=
ith
> the IMS business trunking.  I think that should also be in your interest =
and
> in fact you have been part of that work...
>
>  On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John <
> john.elwell@siemens-enterprise.com> wrote:
>
> Hans Erik,
>
> As an individual, I disagree with the proposed text, since it is
> misleading. The "international standards" to which you prefer are standar=
ds
> specific to an IMS environment. The implication of the wording as propose=
d
> is that SIP-PBXs ought to implement IMS specifications. And as Hadriel
> points out, implementing those IMS specifications does not eliminate the
> problems that the SIPconnect people are trying to solve. I believe the
> existing text in draft-03 is sufficient.
>
>
> John
>
> > -----Original Message-----
> > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
>
> > Sent: 26 March 2010 23:03
> > To: Elwell, John
> > Cc: martini@ietf.org
> > Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
> >
> > I will not argue with you about the validity of that argument.
> >
> > Can you agree to the modified text?
> >
> > "Request-URI vs. loose-route acceptance
> > Some IP-PBX do not implement international standards or SIP
> > profiles for SIP trunking. As a consequence some SIP-PBXs
> > expect that inbound SIP requests from the SSP will have the
> > registered Contact-URI in the Request-URI, and thus not
> > interoperate with the loose-route scheme of 3GPP and ETSI.
> > Other SIP-PBXs are fine with the Request-URI being the
> > intended target, but cannot handle receiving a Route header
> > field identifying their registered Contact-URI as a
> > loose-route entry."
> >
> > BR,
> > /Hans Erik van Elburg
> >
> >
> > On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
> > <john.elwell@siemens-enterprise.com> wrote:
> >
> >
> >       The IETF does not have a mechanism, and that is the
> > reason for the MARTINI work. In particular, the IETF has not
> > published the so-called loose-route mechanism. Hence the
> > reason for the IETF, as owner of SIP, to publish a mechanism
> > for bulk registrations.
> >
> >       John
> >
> >
> >       > -----Original Message-----
> >       > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
> >       > Sent: 26 March 2010 02:21
> >       > To: trac@localhost.amsl.com
> >       > Cc: Elwell, John; martini@ietf.org
> >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
> > with some PBX
> >       >
> >       >
> >       > Then you should rephrase to what the real issue is:
> >       > "
> >       >
> >       >
> >       > Request-URI vs. loose-route acceptance
> >       >
> >       >
> >       > Some IP-PBX do not implement international standards or SIP
> >       > profiles for SIP trunking. As a consequence some SIP-PBXs
> >       > expect that inbound SIP requests from the SSP will have the
> >       > registered Contact-URI in the Request-URI, and thus not
> >       > interoperate with the loose-route scheme of 3GPP and ETSI.
> >       > Other SIP-PBXs are fine with the Request-URI being the
> >       > intended target, but cannot handle receiving a Route header
> >       > field identifying their registered Contact-URI as a
> >       > loose-route entry."
> >       >
> >       >
> >       > Is this an issue, yes. Does introducing yet another
> > profile help? No.
> >       >
> >       > /Hans Erik van Elburg
> >       >
> >       >
> >       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
> >       > <trac@tools.ietf.org> wrote:
> >       >
> >       >
> >       >       #21: 3.2.2 describes an issue with some PBX
> >       >
> >       > -------------------------------------+------------------------
> >       > --------------
> >       >        Reporter:  ietf.hanserik@...          |        Owner:
> >       >
> >       >           Type:  defect                   |
> > Status:  closed
> >       >
> >       >        Priority:  minor                    |
> > Milestone:  milestone1
> >       >       Component:  reqs                     |
> > Version:  1.0
> >       >
> >       >        Severity:  In WG Last Call          |
> > Resolution:  invalid
> >       >        Keywords:                           |
> >       >
> >       > -------------------------------------+------------------------
> >       > --------------
> >       >       Changes (by john.elwell@...):
> >       >
> >       >        * status:  new =3D> closed
> >       >        * resolution:  =3D> invalid
> >       >
> >       >
> >       >       Comment:
> >       >
> >       >
> >       >        The text of 3.2.2 just underlines the fact that there
> >       > are different
> >       >        implementations around. A PBX that expects the loose
> >       > route mechanism to be
> >       >        used would fail to interwork with SSPs using a
> >       > different mechanism (e.g.,
> >       >        SIPconnect 1.0), and a PBX not expecting the loose
> >       > route mechanism to be
> >       >        used would fail to interwork with a loose route
> >       > implementation (e.g.,
> >       >        ETSI/3GPP). Hence the urgent need for a standard.
> >       >
> >       >       --
> >       >       Ticket URL:
> >       >
> > <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
> >       >
> >       >       martini <http://tools.ietf.org/martini/>
> >       >
> >       >
> >       >       _______________________________________________
> >       >       martini mailing list
> >       >       martini@ietf.org
> >       >       https://www.ietf.org/mailman/listinfo/martini
> >       >
> >       >
> >       >
> >       >
> >
> >
> >
>
>
>
>

--00148530ad9f71a1cb0482f3b2ee
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Yes, there exist IMS business trunking solutions in several countries.<br><=
br clear=3D"all">/Hans Erik van Elburg<br><br><div class=3D"gmail_quote">On=
 Mon, Mar 29, 2010 at 7:07 PM, Richard Shockey <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:richard@shockey.us">richard@shockey.us</a>&gt;</span> wrote:<br=
>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">










<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">

<div>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">Has any of this IMS business trunking stuff actually deployed?</span>=
</p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">=A0</span></p>

<div>

<div style=3D"border-width: 1pt medium medium; border-style: solid none non=
e; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color=
; padding: 3pt 0in 0in;">

<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt;">From:</span></b>=
<span style=3D"font-size: 10pt;">
<a href=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">martini-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:martini-bounces@ietf.org" target=
=3D"_blank">martini-bounces@ietf.org</a>] <b>On Behalf Of </b><a href=3D"ma=
ilto:bruno.chatras@orange-ftgroup.com" target=3D"_blank">bruno.chatras@oran=
ge-ftgroup.com</a><br>

<b>Sent:</b> Monday, March 29, 2010 12:35 PM<br>
<b>To:</b> <a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">iet=
f.hanserik@gmail.com</a>; <a href=3D"mailto:john.elwell@siemens-enterprise.=
com" target=3D"_blank">john.elwell@siemens-enterprise.com</a><div><div></di=
v><div class=3D"h5">
<br>
<b>Cc:</b> <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ie=
tf.org</a><br>
<b>Subject:</b> Re: [martini] #21: 3.2.2 describes an issue with some PBX</=
div></div></span></p>

</div>

</div><div><div></div><div class=3D"h5">

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal"><span style=3D"font-size: 10pt;">I
fully agree with what Hans Erik has said in the Postscriptum=A0&quot;it
would be really, really, really good if they (the IP PBX) would interwork o=
n
the UNI with the IMS business trunking&quot;.=A0I believe that most
operators share the same view... and presumably some vendors as well...</sp=
an></p>

<p class=3D"MsoNormal">=A0</p>

<div class=3D"MsoNormal" style=3D"text-align: center;" align=3D"center">

<hr width=3D"100%" align=3D"center" size=3D"3">

</div>

<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;"><b><span style=3D"fon=
t-size: 10pt;">De=A0:</span></b><span style=3D"font-size: 10pt;"> <a href=
=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">martini-bounces@ietf=
.org</a>
[mailto:<a href=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">marti=
ni-bounces@ietf.org</a>] <b>De la part de</b> Hans Erik van Elburg<br>
<b>Envoy=E9=A0:</b> lundi 29 mars 2010 18:27<br>
<b>=C0=A0:</b> Elwell, John<br>
<b>Cc=A0:</b> <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini=
@ietf.org</a><br>
<b>Objet=A0:</b> Re: [martini] #21: 3.2.2 describes an issue with some PBX<=
/span></p>

<blockquote style=3D"border-width: medium medium medium 1.5pt; border-style=
: none none none solid; border-color: -moz-use-text-color -moz-use-text-col=
or -moz-use-text-color blue; padding: 0in 0in 0in 3pt; margin: 5pt 0in 5pt =
3pt;">


<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;">Hi John,<br>
<br>
I was just trying to find a text that describes the issue. <br>
<br>
But now the issue reads like &quot;some PBX like apples, some like
bananas&quot;. To me that does not sound like a usefull issue to describe i=
n an
RFC.<br>
<br>
So I think one or two more sentence would make clear why this is an issue.<=
br>
<br>
I think there is multiple underlying issues here:<br>
- PBX have different SIP profiles or all SIP-PBX are different<br>
- PBX support SIP trunking flavour A, or support SIP trunking flavour B<br>
- SSP systems don&#39;t know what mechanism the PBX support (can be resolve=
d with
explicit indicator, this draft proposes an indicator for flavour B but for
another purpose it seems)<br>
- PBX do not know what SIP trunking flavour the SSP supports (not addressed=
 it
seems)<br>
<br>
I don&#39;t seem to have a lucky hand with proposing an improved text, so m=
aybe you
should have a go at it.<br>
<br>
BR,<br>
/Hans Erik van Elburg<br>
<br>
p.s. I never said or implied that a SIP-PBX shall implement IMS. But it wou=
ld
be really, really, really good if they would interwork on the UNI with the =
IMS
business trunking.=A0 I think that should also be in your interest and in
fact you have been part of that work...<br>
<br>
</p>

<div>

<p class=3D"MsoNormal">On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John &lt;<a=
 href=3D"mailto:john.elwell@siemens-enterprise.com" target=3D"_blank">john.=
elwell@siemens-enterprise.com</a>&gt;
wrote:</p>

<p class=3D"MsoNormal">Hans Erik,<br>
<br>
As an individual, I disagree with the proposed text, since it is misleading=
.
The &quot;international standards&quot; to which you prefer are standards
specific to an IMS environment. The implication of the wording as proposed =
is
that SIP-PBXs ought to implement IMS specifications. And as Hadriel points =
out,
implementing those IMS specifications does not eliminate the problems that =
the
SIPconnect people are trying to solve. I believe the existing text in draft=
-03
is sufficient.</p>

<div>

<p class=3D"MsoNormal"><br>
John<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Hans Erik van Elburg [mailto:<a href=3D"mailto:ietf.hanserik@gma=
il.com" target=3D"_blank">ietf.hanserik@gmail.com</a>]</p>

</div>

<div>

<div>

<p class=3D"MsoNormal">&gt; Sent: 26 March 2010 23:03<br>
&gt; To: Elwell, John<br>
&gt; Cc: <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf=
.org</a><br>
&gt; Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX<br>
&gt;<br>
&gt; I will not argue with you about the validity of that argument.<br>
&gt;<br>
&gt; Can you agree to the modified text?<br>
&gt;<br>
&gt; &quot;Request-URI vs. loose-route acceptance<br>
&gt; Some IP-PBX do not implement international standards or SIP<br>
&gt; profiles for SIP trunking. As a consequence some SIP-PBXs<br>
&gt; expect that inbound SIP requests from the SSP will have the<br>
&gt; registered Contact-URI in the Request-URI, and thus not<br>
&gt; interoperate with the loose-route scheme of 3GPP and ETSI.<br>
&gt; Other SIP-PBXs are fine with the Request-URI being the<br>
&gt; intended target, but cannot handle receiving a Route header<br>
&gt; field identifying their registered Contact-URI as a<br>
&gt; loose-route entry.&quot;<br>
&gt;<br>
&gt; BR,<br>
&gt; /Hans Erik van Elburg<br>
&gt;<br>
&gt;<br>
&gt; On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John<br>
&gt; &lt;<a href=3D"mailto:john.elwell@siemens-enterprise.com" target=3D"_b=
lank">john.elwell@siemens-enterprise.com</a>&gt;
wrote:<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 The IETF does not have a mechanism, and that is the<br>
&gt; reason for the MARTINI work. In particular, the IETF has not<br>
&gt; published the so-called loose-route mechanism. Hence the<br>
&gt; reason for the IETF, as owner of SIP, to publish a mechanism<br>
&gt; for bulk registrations.<br>
&gt;<br>
&gt; =A0 =A0 =A0 John<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 &gt; -----Original Message-----<br>
&gt; =A0 =A0 =A0 &gt; From: Hans Erik van Elburg [mailto:<a href=3D"mailto:=
ietf.hanserik@gmail.com" target=3D"_blank">ietf.hanserik@gmail.com</a>]<br>
&gt; =A0 =A0 =A0 &gt; Sent: 26 March 2010 02:21<br>
&gt; =A0 =A0 =A0 &gt; To: <a href=3D"mailto:trac@localhost.amsl.com" target=
=3D"_blank">trac@localhost.amsl.com</a><br>
&gt; =A0 =A0 =A0 &gt; Cc: Elwell, John; <a href=3D"mailto:martini@ietf.org"=
 target=3D"_blank">martini@ietf.org</a><br>
&gt; =A0 =A0 =A0 &gt; Subject: Re: [martini] #21: 3.2.2 describes an
issue<br>
&gt; with some PBX<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; Then you should rephrase to what the real issue
is:<br>
&gt; =A0 =A0 =A0 &gt; &quot;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; Request-URI vs. loose-route acceptance<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; Some IP-PBX do not implement international
standards or SIP<br>
&gt; =A0 =A0 =A0 &gt; profiles for SIP trunking. As a consequence some
SIP-PBXs<br>
&gt; =A0 =A0 =A0 &gt; expect that inbound SIP requests from the SSP
will have the<br>
&gt; =A0 =A0 =A0 &gt; registered Contact-URI in the Request-URI, and
thus not<br>
&gt; =A0 =A0 =A0 &gt; interoperate with the loose-route scheme of 3GPP
and ETSI.<br>
&gt; =A0 =A0 =A0 &gt; Other SIP-PBXs are fine with the Request-URI
being the<br>
&gt; =A0 =A0 =A0 &gt; intended target, but cannot handle receiving a
Route header<br>
&gt; =A0 =A0 =A0 &gt; field identifying their registered Contact-URI
as a<br>
&gt; =A0 =A0 =A0 &gt; loose-route entry.&quot;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; Is this an issue, yes. Does introducing yet
another<br>
&gt; profile help? No.<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; /Hans Erik van Elburg<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; On Thu, Mar 25, 2010 at 9:22 PM, martini issue
tracker<br>
&gt; =A0 =A0 =A0 &gt; &lt;<a href=3D"mailto:trac@tools.ietf.org" target=3D"=
_blank">trac@tools.ietf.org</a>&gt;
wrote:<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 #21: 3.2.2 describes an
issue with some PBX<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;
-------------------------------------+------------------------<br>
&gt; =A0 =A0 =A0 &gt; --------------<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Reporter:
=A0ietf.hanserik@... =A0 =A0 =A0 =A0 =A0| =A0 =A0
=A0 =A0Owner:<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0 =A0 Type:
=A0defect =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; Status: =A0closed<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Priority: =A0minor
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0|<br>
&gt; Milestone: =A0milestone1<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 Component: =A0reqs
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; Version: =A01.0<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Severity: =A0In WG
Last Call =A0 =A0 =A0 =A0 =A0|<br>
&gt; Resolution: =A0invalid<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Keywords: =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 |<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; -------------------------------------+---------------=
---------<br>
&gt; =A0 =A0 =A0 &gt; --------------<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 Changes (by
john.elwell@...):<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0* status: =A0new
=3D&gt; closed<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0* resolution:
=A0=3D&gt; invalid<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 Comment:<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0The text of 3.2.2
just underlines the fact that there<br>
&gt; =A0 =A0 =A0 &gt; are different<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0implementations
around. A PBX that expects the loose<br>
&gt; =A0 =A0 =A0 &gt; route mechanism to be<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0used would fail to
interwork with SSPs using a<br>
&gt; =A0 =A0 =A0 &gt; different mechanism (e.g.,<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0SIPconnect 1.0), and
a PBX not expecting the loose<br>
&gt; =A0 =A0 =A0 &gt; route mechanism to be<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0used would fail to
interwork with a loose route<br>
&gt; =A0 =A0 =A0 &gt; implementation (e.g.,<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0ETSI/3GPP). Hence the
urgent need for a standard.<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 --<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 Ticket URL:<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/21#co=
mment:1" target=3D"_blank">http://trac.tools.ietf.org/wg/martini/trac/ticke=
t/21#comment:1</a>&gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 martini &lt;<a href=3D"http://tools.ietf.=
org/martini/" target=3D"_blank">http://tools.ietf.org/martini/</a>&gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0
_______________________________________________<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 martini mailing list<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 <a href=3D"mailto:martini@ietf.org" targe=
t=3D"_blank">martini@ietf.org</a><br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 <a href=3D"https://www.ietf.org/mailman/l=
istinfo/martini" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ma=
rtini</a><br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt;<br>
&gt;<br>
&gt; </p>

</div>

</div>

</div>

<p class=3D"MsoNormal">=A0</p>

</blockquote>

</div></div></div>

</div>


</blockquote></div><br>

--00148530ad9f71a1cb0482f3b2ee--

From bernard_aboba@hotmail.com  Mon Mar 29 11:41:23 2010
Return-Path: <bernard_aboba@hotmail.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 AC20A3A68E6 for <martini@core3.amsl.com>; Mon, 29 Mar 2010 11:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.375
X-Spam-Level: *
X-Spam-Status: No, score=1.375 tagged_above=-999 required=5 tests=[AWL=0.243,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 I501YugTIWhG for <martini@core3.amsl.com>; Mon, 29 Mar 2010 11:41:18 -0700 (PDT)
Received: from blu0-omc2-s24.blu0.hotmail.com (blu0-omc2-s24.blu0.hotmail.com [65.55.111.99]) by core3.amsl.com (Postfix) with ESMTP id 106CE3A6858 for <martini@ietf.org>; Mon, 29 Mar 2010 11:41:17 -0700 (PDT)
Received: from BLU137-DS3 ([65.55.111.73]) by blu0-omc2-s24.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 29 Mar 2010 11:41:45 -0700
X-Originating-IP: [131.107.0.77]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS31CBF24CD9D273DD7E19693200@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <martini@ietf.org>
Date: Mon, 29 Mar 2010 11:41:44 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B5_01CACF34.CF1AA780"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcrPUnRcGktM7C6cTIGWL7ZvfakGvAADy6EgAALPxkA=
Content-Language: en-us
X-OriginalArrivalTime: 29 Mar 2010 18:41:45.0872 (UTC) FILETIME=[7BCB4900:01CACF6F]
Subject: [martini] Summary of Call for Adoption of "Registration for Multiple Phone Numbers in the SIP"
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, 29 Mar 2010 18:41:23 -0000

------=_NextPart_000_00B5_01CACF34.CF1AA780
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

The MARTINI WG Call for Adoption of "Registration for Multiple Phone Numbers
in the SIP" concluded on March 19, 2010.  

 

The Call for Adoption announcement is available here:
http://www.ietf.org/mail-archive/web/martini/current/msg00916.html

 

8 issues were raised in the Call for Adoption (details below).  The current
status of the  issues is available from TRAC:
http://trac.tools.ietf.org/wg/martini/trac/report/6

 

16 individuals responded to the Call for Adoption, with 11 favoring adoption
of the document, and 5 weighing in against adoption. 

 

In the judgment of the chairs, this represents "rough consensus" for
adoption of GIN as a MARTINI WG Work item.  

 

The draft may be submitted as draft-ietf-martini-gin-00.txt at the editor's
earliest convenience. 

 

Issues Submitted

 


Ticket

Summary

Created


#9 <http://trac.tools.ietf.org/wg/martini/trac/ticket/9> 

IANA <http://trac.tools.ietf.org/wg/martini/trac/ticket/9>  considerations

3/10/2010


#10 <http://trac.tools.ietf.org/wg/martini/trac/ticket/10> 

Section 9: Issues Solved
<http://trac.tools.ietf.org/wg/martini/trac/ticket/10> 

3/10/2010


#11 <http://trac.tools.ietf.org/wg/martini/trac/ticket/11> 

Section 7.3: Outbound Analysis
<http://trac.tools.ietf.org/wg/martini/trac/ticket/11> 

3/10/2010


#12 <http://trac.tools.ietf.org/wg/martini/trac/ticket/12> 

Section 7.4: Path <http://trac.tools.ietf.org/wg/martini/trac/ticket/12> 

3/10/2010


#13 <http://trac.tools.ietf.org/wg/martini/trac/ticket/13> 

Section 7.5: Service Route
<http://trac.tools.ietf.org/wg/martini/trac/ticket/13> 

3/10/2010


#7 <http://trac.tools.ietf.org/wg/martini/trac/ticket/7> 

GIN <http://trac.tools.ietf.org/wg/martini/trac/ticket/7>  idnits

3/10/2010


#14 <http://trac.tools.ietf.org/wg/martini/trac/ticket/14> 

Section 8: Examples <http://trac.tools.ietf.org/wg/martini/trac/ticket/14> 

3/10/2010


#8 <http://trac.tools.ietf.org/wg/martini/trac/ticket/8> 

GIN <http://trac.tools.ietf.org/wg/martini/trac/ticket/8>  editorial issues

3/10/2010

 

MARTINI Consensus Call Summary

 


Name

Opinion

URL


Keith Drage

No

http://www.ietf.org/mail-archive/web/martini/current/msg00918.html


John Elwell

Yes

http://www.ietf.org/mail-archive/web/martini/current/msg00919.html


Alan Johnston

Yes

http://www.ietf.org/mail-archive/web/martini/current/msg00920.html


Hadriel Kaplan

Yes

http://www.ietf.org/mail-archive/web/martini/current/msg00921.html


Bernard Aboba

Yes

http://www.ietf.org/mail-archive/web/martini/current/msg00922.html


Richard Shockey

Yes

http://www.ietf.org/mail-archive/web/martini/current/msg00923.html


Victor Pascual Avila

Yes

http://www.ietf.org/mail-archive/web/martini/current/msg00924.html


Dean Willis

Yes

http://www.ietf.org/mail-archive/web/martini/current/msg00925.html


Jack Burton

Yes

http://www.ietf.org/mail-archive/web/martini/current/msg00926.html


Bruno Chatras

No

http://www.ietf.org/mail-archive/web/martini/current/msg00932.html


Hans Erik van Elburg

No

http://www.ietf.org/mail-archive/web/martini/current/msg00941.html


Kevin Smith

Yes

http://www.ietf.org/mail-archive/web/martini/current/msg00952.html


Brian Lindsay

No

http://www.ietf.org/mail-archive/web/martini/current/msg00954.html


Ben Campbell

Yes

http://www.ietf.org/mail-archive/web/martini/current/msg00956.html


Jan Van Geel

No

http://www.ietf.org/mail-archive/web/martini/current/msg00957.html


David Hancock

Yes

http://www.ietf.org/mail-archive/web/martini/current/msg00994.html

 


------=_NextPart_000_00B5_01CACF34.CF1AA780
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>The MARTINI WG Call for Adoption of =
&#8220;Registration for
Multiple Phone Numbers in the SIP&#8221; concluded on March 19, 2010. =
<span
style=3D'color:#1F497D'>&nbsp;</span><span =
style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'>The Call for Adoption =
announcement
is available</span><span style=3D'color:black'> here:</span><span
style=3D'color:#1F497D'> &nbsp;<a
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00916.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00916.html</a>=
<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal>8 issues were raised in the Call for Adoption =
(details
below). <span style=3D'color:#1F497D'>&nbsp;</span><span =
style=3D'color:black'>The current
status of the &nbsp;issues is available from TRAC: =
&nbsp;http://trac.tools.ietf.org/wg/martini/trac/report/6<o:p></o:p></spa=
n></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>16 individuals responded to the Call for Adoption, =
with 11
favoring adoption of the document, and 5 weighing in against adoption. =
<span
style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>In the judgment of the chairs, this represents =
&#8220;rough
consensus&#8221; for adoption of GIN as a MARTINI WG Work item. =
&nbsp;<span
style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>The draft may be submitted as =
draft-ietf-martini-gin-00.txt
at the editor&#8217;s earliest convenience. <o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><b>Issues Submitted<o:p></o:p></b></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D374
 style=3D'width:280.4pt;border-collapse:collapse'>
 <tr style=3D'height:15.0pt'>
  <td width=3D65 nowrap valign=3Dbottom =
style=3D'width:48.8pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal><b><span =
style=3D'color:black'>Ticket<o:p></o:p></span></b></p>
  </td>
  <td width=3D225 nowrap valign=3Dbottom =
style=3D'width:168.8pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal><b><span =
style=3D'color:black'>Summary<o:p></o:p></span></b></p>
  </td>
  <td width=3D84 nowrap valign=3Dbottom =
style=3D'width:62.8pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal><b><span =
style=3D'color:black'>Created<o:p></o:p></span></b></p>
  </td>
 </tr>
 <tr style=3D'height:18.75pt'>
  <td width=3D65 valign=3Dtop style=3D'width:48.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:18.75pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/9" =
title=3D"View ticket">#9</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D225 valign=3Dtop style=3D'width:168.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:18.75pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/9" =
title=3D"View ticket">IANA
  considerations</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D84 valign=3Dtop style=3D'width:62.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:18.75pt'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
  style=3D'font-size:9.0pt;font-family:"Courier =
New";color:black'>3/10/2010<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:18.75pt'>
  <td width=3D65 valign=3Dtop style=3D'width:48.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:18.75pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/10"
  title=3D"View ticket">#10</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D225 valign=3Dtop style=3D'width:168.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:18.75pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/10"
  title=3D"View ticket">Section 9: Issues =
Solved</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D84 valign=3Dtop style=3D'width:62.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:18.75pt'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
  style=3D'font-size:9.0pt;font-family:"Courier =
New";color:black'>3/10/2010<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:20.25pt'>
  <td width=3D65 valign=3Dtop style=3D'width:48.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:20.25pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/11"
  title=3D"View ticket">#11</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D225 valign=3Dtop style=3D'width:168.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:20.25pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/11"
  title=3D"View ticket">Section 7.3: Outbound =
Analysis</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D84 valign=3Dtop style=3D'width:62.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:20.25pt'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
  style=3D'font-size:9.0pt;font-family:"Courier =
New";color:black'>3/10/2010<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D65 valign=3Dtop style=3D'width:48.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/12"
  title=3D"View ticket">#12</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D225 valign=3Dtop style=3D'width:168.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/12"
  title=3D"View ticket">Section 7.4: Path</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D84 valign=3Dtop style=3D'width:62.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
  style=3D'font-size:9.0pt;font-family:"Courier =
New";color:black'>3/10/2010<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:22.5pt'>
  <td width=3D65 valign=3Dtop style=3D'width:48.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:22.5pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/13"
  title=3D"View ticket">#13</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D225 valign=3Dtop style=3D'width:168.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:22.5pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/13"
  title=3D"View ticket">Section 7.5: Service =
Route</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D84 valign=3Dtop style=3D'width:62.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:22.5pt'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
  style=3D'font-size:9.0pt;font-family:"Courier =
New";color:black'>3/10/2010<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D65 valign=3Dtop style=3D'width:48.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/7" =
title=3D"View ticket">#7</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D225 valign=3Dtop style=3D'width:168.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/7" =
title=3D"View ticket">GIN
  idnits</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D84 valign=3Dtop style=3D'width:62.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
  style=3D'font-size:9.0pt;font-family:"Courier =
New";color:black'>3/10/2010<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:19.5pt'>
  <td width=3D65 valign=3Dtop style=3D'width:48.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:19.5pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/14"
  title=3D"View ticket">#14</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D225 valign=3Dtop style=3D'width:168.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:19.5pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/14"
  title=3D"View ticket">Section 8: =
Examples</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D84 valign=3Dtop style=3D'width:62.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:19.5pt'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
  style=3D'font-size:9.0pt;font-family:"Courier =
New";color:black'>3/10/2010<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D65 valign=3Dtop style=3D'width:48.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/8" =
title=3D"View ticket">#8</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D225 valign=3Dtop style=3D'width:168.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal><u><span style=3D'color:blue'><a
  href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/8" =
title=3D"View ticket">GIN
  editorial issues</a><o:p></o:p></span></u></p>
  </td>
  <td width=3D84 valign=3Dtop style=3D'width:62.8pt;padding:0in 5.4pt =
0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span
  style=3D'font-size:9.0pt;font-family:"Courier =
New";color:black'>3/10/2010<o:p></o:p></span></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'color:black'>MARTINI Consensus =
Call Summary<o:p></o:p></span></b></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D659
 style=3D'width:494.0pt;margin-left:-.75pt;border-collapse:collapse'>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><b><span =
style=3D'color:black'>Name<o:p></o:p></span></b></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><b><span =
style=3D'color:black'>Opinion<o:p></o:p></span></b></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><b><span =
style=3D'color:black'>URL<o:p></o:p></span></b></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Keith
  Drage<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>No<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00918.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00918.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>John
  Elwell<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Yes<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00919.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00919.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Alan
  Johnston<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Yes<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00920.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00920.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Hadriel
  Kaplan<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Yes<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00921.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00921.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Bernard
  Aboba<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Yes<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00922.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00922.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Richard
  Shockey<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Yes<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00923.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00923.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Victor
  Pascual Avila<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Yes<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00924.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00924.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Dean
  Willis<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Yes<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><u><span =
style=3D'color:blue'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00925.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00925.html</a>=
<o:p></o:p></span></u></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Jack
  Burton<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Yes<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00926.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00926.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Bruno
  Chatras<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>No<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00932.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00932.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Hans
  Erik van Elburg<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>No<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00941.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00941.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Kevin
  Smith<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Yes<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00952.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00952.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Brian
  Lindsay<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>No<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00954.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00954.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Ben
  Campbell<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Yes<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00956.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00956.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Jan Van
  Geel<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>No<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00957.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00957.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style=3D'height:15.0pt'>
  <td width=3D132 nowrap valign=3Dbottom =
style=3D'width:99.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>David
  Hancock<o:p></o:p></span></p>
  </td>
  <td width=3D64 nowrap valign=3Dbottom =
style=3D'width:48.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'>Yes<o:p></o:p></span></p>
  </td>
  <td width=3D463 nowrap valign=3Dbottom =
style=3D'width:347.0pt;padding:0in 5.4pt 0in 5.4pt;
  height:15.0pt'>
  <p class=3DMsoNormal style=3D'line-height:115%'><span =
style=3D'color:black'><a
  =
href=3D"http://www.ietf.org/mail-archive/web/martini/current/msg00994.htm=
l">http://www.ietf.org/mail-archive/web/martini/current/msg00994.html</a>=
<o:p></o:p></span></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_00B5_01CACF34.CF1AA780--

From HKaplan@acmepacket.com  Mon Mar 29 11:59:31 2010
Return-Path: <HKaplan@acmepacket.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 DD77F3A6960 for <martini@core3.amsl.com>; Mon, 29 Mar 2010 11:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.503
X-Spam-Level: 
X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[AWL=0.965,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 HDMVasLN9Epd for <martini@core3.amsl.com>; Mon, 29 Mar 2010 11:59:28 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 2526A3A68D5 for <martini@ietf.org>; Mon, 29 Mar 2010 11:59:28 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Mon, 29 Mar 2010 14:59:53 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Mon, 29 Mar 2010 14:59:52 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Richard Shockey <richard@shockey.us>, "bruno.chatras@orange-ftgroup.com" <bruno.chatras@orange-ftgroup.com>, "ietf.hanserik@gmail.com" <ietf.hanserik@gmail.com>, "john.elwell@siemens-enterprise.com" <john.elwell@siemens-enterprise.com>
Date: Mon, 29 Mar 2010 14:59:53 -0400
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNgAAFPnSAAA9iCcA==
Message-ID: <430FC6BDED356B4C8498F634416644A91A79E928E3@mail>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com> <9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr> <011a01cacf62$55509710$fff1c530$@us>
In-Reply-To: <011a01cacf62$55509710$fff1c530$@us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_430FC6BDED356B4C8498F634416644A91A79E928E3mail_"
MIME-Version: 1.0
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 29 Mar 2010 18:59:32 -0000

--_000_430FC6BDED356B4C8498F634416644A91A79E928E3mail_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Yes, in several large IMS deployments.  That's where we discovered some of =
the problems identified in the drafts.
-hadriel

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Richard Shockey
Sent: Monday, March 29, 2010 1:08 PM
To: bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com; john.elwell@=
siemens-enterprise.com
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

Has any of this IMS business trunking stuff actually deployed?

--_000_430FC6BDED356B4C8498F634416644A91A79E928E3mail_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40"
xmlns:ns6=3D"http://schemas.microsoft.com/office/2004/12/omml">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"Person=
Name"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Calibri;
	color:#1F497D;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Yes, in several large IMS deployments.=
 &nbsp;That&#8217;s
where we discovered some of the problems identified in the drafts.<o:p></o:=
p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>-hadriel<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> martini-=
bounces@ietf.org
[mailto:martini-bounces@ietf.org] <b><span style=3D'font-weight:bold'>On Be=
half
Of </span></b>Richard Shockey<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, March 29, 2010=
 1:08
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b>
bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com;
john.elwell@siemens-enterprise.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName w:st=3D"=
on">martini@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [martini] #21: =
3.2.2
describes an issue with some PBX</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>Has any of thi=
s IMS
business trunking stuff actually deployed?<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

--_000_430FC6BDED356B4C8498F634416644A91A79E928E3mail_--

From HKaplan@acmepacket.com  Mon Mar 29 12:16:36 2010
Return-Path: <HKaplan@acmepacket.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 10B493A6B4A for <martini@core3.amsl.com>; Mon, 29 Mar 2010 12:16:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.767
X-Spam-Level: 
X-Spam-Status: No, score=0.767 tagged_above=-999 required=5 tests=[AWL=-0.365,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 3nxFeB90KsRT for <martini@core3.amsl.com>; Mon, 29 Mar 2010 12:16:33 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 8DE153A6B4C for <martini@ietf.org>; Mon, 29 Mar 2010 12:15:21 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Mon, 29 Mar 2010 15:15:49 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Mon, 29 Mar 2010 15:15:48 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "bruno.chatras@orange-ftgroup.com" <bruno.chatras@orange-ftgroup.com>, "ietf.hanserik@gmail.com" <ietf.hanserik@gmail.com>, "john.elwell@siemens-enterprise.com" <john.elwell@siemens-enterprise.com>
Date: Mon, 29 Mar 2010 15:15:49 -0400
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNgAAVBprA=
Message-ID: <430FC6BDED356B4C8498F634416644A91A79E928EE@mail>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com> <9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_430FC6BDED356B4C8498F634416644A91A79E928EEmail_"
MIME-Version: 1.0
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 29 Mar 2010 19:16:38 -0000

--_000_430FC6BDED356B4C8498F634416644A91A79E928EEmail_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Absolutely - that's one of the advantages of the Martini mechanism having a=
n options-tag.  If the IP-PBX indicates the option-tag but the REGISTER res=
ponse does not (i.e., is rejected with 420), then the IP-PBX would revert t=
o doing whatever it is it "normally" does.  Unfortunately there was no expl=
icit indicator of the ETSI nor SIP-Connect 1.0 models, so how the IP-PBX be=
haves "normally" is unknown a priori.

And of course the IP-PBX could always be configured to just do ETSI or SIP-=
Connect 1.0 models, as has previously been the case; and the nice thing wit=
h Martini is if the SSP only supports Martini then it can indicate the opti=
on-tag is required in its response (by responding to the REGISTER with a 42=
1).

-hadriel

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of bruno.chatras@orange-ftgroup.com
Sent: Monday, March 29, 2010 12:35 PM
To: ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

I fully agree with what Hans Erik has said in the Postscriptum "it would be=
 really, really, really good if they (the IP PBX) would interwork on the UN=
I with the IMS business trunking". I believe that most operators share the =
same view... and presumably some vendors as well...


--_000_430FC6BDED356B4C8498F634416644A91A79E928EEmail_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"Person=
Name"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Absolutely &#8211; that&#8217;s one of=
 the
advantages of the Martini mechanism having an options-tag. &nbsp;If the IP-=
PBX
indicates the option-tag but the REGISTER response does not (i.e., is rejec=
ted with
420), then the IP-PBX would revert to doing whatever it is it &#8220;normal=
ly&#8221;
does.&nbsp; Unfortunately there was no explicit indicator of the ETSI nor
SIP-Connect 1.0 models, so how the IP-PBX behaves &#8220;normally&#8221; is
unknown a priori.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>And of course the IP-PBX could always =
be
configured to just do ETSI or SIP-Connect 1.0 models, as has previously bee=
n
the case; and the nice thing with Martini is if the SSP only supports Marti=
ni
then it can indicate the option-tag is required in its response (by respond=
ing to
the REGISTER with a 421).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>-hadriel<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>bruno.chatras@orange-ftg=
roup.com<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, March 29, 2010=
 12:35
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> ietf.hanserik@gmail.com;
john.elwell@siemens-enterprise.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName w:st=3D"=
on">martini@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [martini] #21: =
3.2.2
describes an issue with some PBX</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>I fully agree with what Hans Erik has said in the
Postscriptum&nbsp;&quot;it would be really, really, really good if they (th=
e IP
PBX) would interwork on the UNI with the IMS business trunking&quot;.&nbsp;=
I
believe that most operators share the same view... and presumably some vend=
ors
as well...</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

--_000_430FC6BDED356B4C8498F634416644A91A79E928EEmail_--

From HKaplan@acmepacket.com  Mon Mar 29 12:21:45 2010
Return-Path: <HKaplan@acmepacket.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 6C7103A681C for <martini@core3.amsl.com>; Mon, 29 Mar 2010 12:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.778
X-Spam-Level: 
X-Spam-Status: No, score=0.778 tagged_above=-999 required=5 tests=[AWL=-0.354,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 8e+7NGrbhUhk for <martini@core3.amsl.com>; Mon, 29 Mar 2010 12:21:41 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id A14813A6B49 for <martini@ietf.org>; Mon, 29 Mar 2010 12:21:25 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Mon, 29 Mar 2010 15:21:53 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Mon, 29 Mar 2010 15:21:52 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
Date: Mon, 29 Mar 2010 15:21:54 -0400
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXNpErRaGMWcDTpW2XTevMll6EQAF2zww
Message-ID: <430FC6BDED356B4C8498F634416644A91A79E928F2@mail>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org> <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net> <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com>
In-Reply-To: <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_430FC6BDED356B4C8498F634416644A91A79E928F2mail_"
MIME-Version: 1.0
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 29 Mar 2010 19:21:45 -0000

--_000_430FC6BDED356B4C8498F634416644A91A79E928F2mail_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable



________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Hans Erik van Elburg
Sent: Monday, March 29, 2010 12:27 PM
To: Elwell, John

I think there is multiple underlying issues here:
- PBX have different SIP profiles or all SIP-PBX are different
- PBX support SIP trunking flavour A, or support SIP trunking flavour B
- SSP systems don't know what mechanism the PBX support (can be resolved wi=
th explicit indicator, this draft proposes an indicator for flavour B but f=
or another purpose it seems)
Actually I did assume the use of the options-tag would indicate to the SSP =
"this is what I do". (as well as "this is what I need you to do too", hence=
 in Require and Proxy-Require headers)
That was one of the main drivers for the options-tag - we needed to know th=
e IP-PBX implemented Martini.

- PBX do not know what SIP trunking flavour the SSP supports (not addressed=
 it seems)
There was no way to indicate the SSP supports SIP Connect 1.0 or ETSI, but =
for Martini the SSP would respond with a 421 with the options-tag, if it ne=
eds/expects Martini.
-hadriel

--_000_430FC6BDED356B4C8498F634416644A91A79E928F2mail_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"Person=
Name"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 face=
=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span>=
</font></b><font
size=3D2 face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b><st1:PersonName w:st=3D"=
on">Hans
 Erik van Elburg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, March 29, 2010=
 12:27
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Elwell, John<br>
</span></font><br>
I think there is multiple underlying issues here:<br>
- PBX have different SIP profiles or all SIP-PBX are different<br>
- PBX support SIP trunking flavour A, or support SIP trunking flavour B<br>
- SSP systems don't know what mechanism the PBX support (can be resolved wi=
th
explicit indicator, this draft proposes an indicator for flavour B but for
another purpose it seems)<font color=3Dnavy><span style=3D'color:navy'><o:p=
></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 color=3D=
navy
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial;color:navy'>=
Actually
I did assume the use of the options-tag would indicate to the SSP &#8220;th=
is
is what I do&#8221;. (as well as &#8220;this is what I need you to do too&#=
8221;,
hence in Require and Proxy-Require headers)<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 color=3D=
navy
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial;color:navy'>=
That was
one of the main drivers for the options-tag &#8211; we needed to know the
IP-PBX implemented Martini.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'><br>
- PBX do not know what SIP trunking flavour the SSP supports (not addressed=
 it
seems)<font color=3Dnavy><span style=3D'color:navy'><o:p></o:p></span></fon=
t></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 color=3D=
navy
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial;color:navy'>=
There
was no way to indicate the SSP supports SIP Connect 1.0 or ETSI, but for
Martini the SSP would respond with a 421 with the options-tag, if it needs/=
expects
Martini.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 color=3D=
navy
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial;color:navy'>=
-hadriel<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

--_000_430FC6BDED356B4C8498F634416644A91A79E928F2mail_--

From john.elwell@siemens-enterprise.com  Mon Mar 29 12:55:30 2010
Return-Path: <john.elwell@siemens-enterprise.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 EEF273A694E for <martini@core3.amsl.com>; Mon, 29 Mar 2010 12:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.788
X-Spam-Level: 
X-Spam-Status: No, score=0.788 tagged_above=-999 required=5 tests=[AWL=-0.343,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
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 uKuvOe6XZXAa for <martini@core3.amsl.com>; Mon, 29 Mar 2010 12:55:29 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id B43333A6945 for <martini@ietf.org>; Mon, 29 Mar 2010 12:55:27 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1383474; Mon, 29 Mar 2010 21:55:55 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 5D9E11EB82AE; Mon, 29 Mar 2010 21:55:55 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Mon, 29 Mar 2010 21:55:55 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>
Date: Mon, 29 Mar 2010 21:55:53 +0200
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXKoTJ+BPYbWCR5i7AlrfHUe/XwAG3PDw
Message-ID: <A444A0F8084434499206E78C106220CADE11BA34@MCHP058A.global-ad.net>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org> <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net> <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com>
In-Reply-To: <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 29 Mar 2010 19:55:31 -0000

Hans Erik,

I think the point you are trying to make is that it is not one-sided. The f=
act is, each side has different ways of working, and you need to have the t=
wo sides operating in compatible manners for it to work. In practice, I thi=
nk there are other variants, besides the two cited in the present 3.2.2. I =
would suggest:

        <t>Even where all information needed by the SIP-PBX is provided, in=
 some deployments inbound SIP requests from the SSP have the registered Con=
tact URI in the Request-URI, whereas in other deployments inbound SIP reque=
sts have the intended target (AOR) in the Request-URI and the Contact URI i=
n the Route header field. There are other variants too. Interoperability pr=
oblems arise when a PBX designed for or configured for one variant attempts=
 to interwork with an SSP designed for or configured for another variant.</=
t>

To accompany this, I think the title of the section should be changed too: =
"Inconsistent placement of information in inbound requests"

John=20

> -----Original Message-----
> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]=20
> Sent: 29 March 2010 17:27
> To: Elwell, John
> Cc: martini@ietf.org
> Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>=20
> Hi John,
>=20
> I was just trying to find a text that describes the issue.=20
>=20
> But now the issue reads like "some PBX like apples, some like=20
> bananas". To me that does not sound like a usefull issue to=20
> describe in an RFC.
>=20
> So I think one or two more sentence would make clear why this=20
> is an issue.
>=20
> I think there is multiple underlying issues here:
> - PBX have different SIP profiles or all SIP-PBX are different
> - PBX support SIP trunking flavour A, or support SIP trunking=20
> flavour B
> - SSP systems don't know what mechanism the PBX support (can=20
> be resolved with explicit indicator, this draft proposes an=20
> indicator for flavour B but for another purpose it seems)
> - PBX do not know what SIP trunking flavour the SSP supports=20
> (not addressed it seems)
>=20
> I don't seem to have a lucky hand with proposing an improved=20
> text, so maybe you should have a go at it.
>=20
> BR,
> /Hans Erik van Elburg
>=20
> p.s. I never said or implied that a SIP-PBX shall implement=20
> IMS. But it would be really, really, really good if they=20
> would interwork on the UNI with the IMS business trunking.  I=20
> think that should also be in your interest and in fact you=20
> have been part of that work...
>=20
>=20
>=20
> On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John=20
> <john.elwell@siemens-enterprise.com> wrote:
>=20
>=20
> 	Hans Erik,
> =09
> 	As an individual, I disagree with the proposed text,=20
> since it is misleading. The "international standards" to=20
> which you prefer are standards specific to an IMS=20
> environment. The implication of the wording as proposed is=20
> that SIP-PBXs ought to implement IMS specifications. And as=20
> Hadriel points out, implementing those IMS specifications=20
> does not eliminate the problems that the SIPconnect people=20
> are trying to solve. I believe the existing text in draft-03=20
> is sufficient.
> =09
>=20
> 	John
> =09
> 	> -----Original Message-----
> 	> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
> =09
> 	> Sent: 26 March 2010 23:03
> 	> To: Elwell, John
> 	> Cc: martini@ietf.org
> 	> Subject: Re: [martini] #21: 3.2.2 describes an issue=20
> with some PBX
> 	>
> 	> I will not argue with you about the validity of that argument.
> 	>
> 	> Can you agree to the modified text?
> 	>
> 	> "Request-URI vs. loose-route acceptance
> 	> Some IP-PBX do not implement international standards or SIP
> 	> profiles for SIP trunking. As a consequence some SIP-PBXs
> 	> expect that inbound SIP requests from the SSP will have the
> 	> registered Contact-URI in the Request-URI, and thus not
> 	> interoperate with the loose-route scheme of 3GPP and ETSI.
> 	> Other SIP-PBXs are fine with the Request-URI being the
> 	> intended target, but cannot handle receiving a Route header
> 	> field identifying their registered Contact-URI as a
> 	> loose-route entry."
> 	>
> 	> BR,
> 	> /Hans Erik van Elburg
> 	>
> 	>
> 	> On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
> 	> <john.elwell@siemens-enterprise.com> wrote:
> 	>
> 	>
> 	>       The IETF does not have a mechanism, and that is the
> 	> reason for the MARTINI work. In particular, the IETF has not
> 	> published the so-called loose-route mechanism. Hence the
> 	> reason for the IETF, as owner of SIP, to publish a mechanism
> 	> for bulk registrations.
> 	>
> 	>       John
> 	>
> 	>
> 	>       > -----Original Message-----
> 	>       > From: Hans Erik van Elburg=20
> [mailto:ietf.hanserik@gmail.com]
> 	>       > Sent: 26 March 2010 02:21
> 	>       > To: trac@localhost.amsl.com
> 	>       > Cc: Elwell, John; martini@ietf.org
> 	>       > Subject: Re: [martini] #21: 3.2.2 describes an issue
> 	> with some PBX
> 	>       >
> 	>       >
> 	>       > Then you should rephrase to what the real issue is:
> 	>       > "
> 	>       >
> 	>       >
> 	>       > Request-URI vs. loose-route acceptance
> 	>       >
> 	>       >
> 	>       > Some IP-PBX do not implement international=20
> standards or SIP
> 	>       > profiles for SIP trunking. As a consequence=20
> some SIP-PBXs
> 	>       > expect that inbound SIP requests from the SSP=20
> will have the
> 	>       > registered Contact-URI in the Request-URI,=20
> and thus not
> 	>       > interoperate with the loose-route scheme of=20
> 3GPP and ETSI.
> 	>       > Other SIP-PBXs are fine with the Request-URI being the
> 	>       > intended target, but cannot handle receiving=20
> a Route header
> 	>       > field identifying their registered Contact-URI as a
> 	>       > loose-route entry."
> 	>       >
> 	>       >
> 	>       > Is this an issue, yes. Does introducing yet another
> 	> profile help? No.
> 	>       >
> 	>       > /Hans Erik van Elburg
> 	>       >
> 	>       >
> 	>       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
> 	>       > <trac@tools.ietf.org> wrote:
> 	>       >
> 	>       >
> 	>       >       #21: 3.2.2 describes an issue with some PBX
> 	>       >
> 	>       >=20
> -------------------------------------+------------------------
> 	>       > --------------
> 	>       >        Reporter:  ietf.hanserik@...         =20
> |        Owner:
> 	>       >
> 	>       >           Type:  defect                   |
> 	> Status:  closed
> 	>       >
> 	>       >        Priority:  minor                    |
> 	> Milestone:  milestone1
> 	>       >       Component:  reqs                     |
> 	> Version:  1.0
> 	>       >
> 	>       >        Severity:  In WG Last Call          |
> 	> Resolution:  invalid
> 	>       >        Keywords:                           |
> 	>       >
> 	>       >=20
> -------------------------------------+------------------------
> 	>       > --------------
> 	>       >       Changes (by john.elwell@...):
> 	>       >
> 	>       >        * status:  new =3D> closed
> 	>       >        * resolution:  =3D> invalid
> 	>       >
> 	>       >
> 	>       >       Comment:
> 	>       >
> 	>       >
> 	>       >        The text of 3.2.2 just underlines the=20
> fact that there
> 	>       > are different
> 	>       >        implementations around. A PBX that=20
> expects the loose
> 	>       > route mechanism to be
> 	>       >        used would fail to interwork with SSPs using a
> 	>       > different mechanism (e.g.,
> 	>       >        SIPconnect 1.0), and a PBX not=20
> expecting the loose
> 	>       > route mechanism to be
> 	>       >        used would fail to interwork with a loose route
> 	>       > implementation (e.g.,
> 	>       >        ETSI/3GPP). Hence the urgent need for=20
> a standard.
> 	>       >
> 	>       >       --
> 	>       >       Ticket URL:
> 	>       >
> 	>=20
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
> 	>       >
> 	>       >       martini <http://tools.ietf.org/martini/>
> 	>       >
> 	>       >
> 	>       >       _______________________________________________
> 	>       >       martini mailing list
> 	>       >       martini@ietf.org
> 	>       >       https://www.ietf.org/mailman/listinfo/martini
> 	>       >
> 	>       >
> 	>       >
> 	>       >
> 	>
> 	>
> 	>=20
>=20
>=20
> =

From john.elwell@siemens-enterprise.com  Mon Mar 29 13:08:58 2010
Return-Path: <john.elwell@siemens-enterprise.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 445E93A68F9 for <martini@core3.amsl.com>; Mon, 29 Mar 2010 13:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.804
X-Spam-Level: 
X-Spam-Status: No, score=0.804 tagged_above=-999 required=5 tests=[AWL=-0.327,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
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 EvJAs1t52XtS for <martini@core3.amsl.com>; Mon, 29 Mar 2010 13:08:57 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 1393B3A680F for <martini@ietf.org>; Mon, 29 Mar 2010 13:08:56 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1383625; Mon, 29 Mar 2010 22:09:24 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id B0E7223F0278; Mon, 29 Mar 2010 22:09:24 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Mon, 29 Mar 2010 22:09:25 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>
Date: Mon, 29 Mar 2010 22:09:23 +0200
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXKoTJ+BPYbWCR5i7AlrfHUe/XwAHWZSQ
Message-ID: <A444A0F8084434499206E78C106220CADE11BA3F@MCHP058A.global-ad.net>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org> <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net> <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com>
In-Reply-To: <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 29 Mar 2010 20:08:58 -0000

> p.s. I never said or implied that a SIP-PBX shall implement=20
> IMS. But it would be really, really, really good if they=20
> would interwork on the UNI with the IMS business trunking.  I=20
> think that should also be in your interest and in fact you=20
> have been part of that work...
[JRE] Yes, I was part of that work. We based it on the loose route mechanis=
m, which was never adopted by the IETF, and furthermore some of the issues =
I had at the time with domain names and routing were never properly answere=
d by TISPAN. TISPAN's working method was to adopt only what 3GPP adopted fo=
r IMS, and I understood that 3GPP's working method was to adopt only protoc=
ol specified by the IETF. Something went wrong at some stage, and the TISPA=
N work has turned out not to be IETF compliant. At least that is how many o=
f the IETF SIP experts view it - if you can convince them otherwise, fine, =
but unfortunately that is the situation.

I just want to see a solution coming out of MARTINI that works and does not=
 have too much impact on SIP-PBXs. The gin- proposal is in fact quite close=
 to some of our existing deployments (with non-IMS SSPs, I guess) so I don'=
t have a problem with that, and that seems to be the direction the WG is go=
ing.

John


From christer.holmberg@ericsson.com  Mon Mar 29 20:40:12 2010
Return-Path: <christer.holmberg@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 A9A363A684D for <martini@core3.amsl.com>; Mon, 29 Mar 2010 20:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.91
X-Spam-Level: 
X-Spam-Status: No, score=-0.91 tagged_above=-999 required=5 tests=[AWL=-2.042,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 pMyxMTGkwa7e for <martini@core3.amsl.com>; Mon, 29 Mar 2010 20:40:06 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id F3A5F3A67FF for <martini@ietf.org>; Mon, 29 Mar 2010 20:40:05 -0700 (PDT)
X-AuditID: c1b4fb39-b7b85ae000005cbc-f1-4bb172b12cf0
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 92.EF.23740.1B271BB4; Tue, 30 Mar 2010 05:40:33 +0200 (CEST)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.2.223]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Tue, 30 Mar 2010 05:40:32 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: 'Hadriel Kaplan' <HKaplan@acmepacket.com>, "bruno.chatras@orange-ftgroup.com" <bruno.chatras@orange-ftgroup.com>,  "ietf.hanserik@gmail.com" <ietf.hanserik@gmail.com>, "john.elwell@siemens-enterprise.com" <john.elwell@siemens-enterprise.com>
Date: Tue, 30 Mar 2010 05:40:31 +0200
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNgAAVBprAAEgqT0A==
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC745E21B5A8EC@ESESSCMS0354.eemea.ericsson.se>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com> <9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr> <430FC6BDED356B4C8498F634416644A91A79E928EE@mail>
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79E928EE@mail>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_FF84A09F50A6DC48ACB6714F4666CC745E21B5A8ECESESSCMS0354e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 30 Mar 2010 03:40:12 -0000

--_000_FF84A09F50A6DC48ACB6714F4666CC745E21B5A8ECESESSCMS0354e_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Having an option-tag is fine, but it will only help for negotiation, and to=
 figure out what is supported. You are still going to end up having two dif=
ferent solutions that do not interwork with each other.

Regards,

Christer

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Hadriel Kaplan
Sent: 29. maaliskuuta 2010 22:16
To: bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com; john.elwell@=
siemens-enterprise.com
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

Absolutely - that's one of the advantages of the Martini mechanism having a=
n options-tag.  If the IP-PBX indicates the option-tag but the REGISTER res=
ponse does not (i.e., is rejected with 420), then the IP-PBX would revert t=
o doing whatever it is it "normally" does.  Unfortunately there was no expl=
icit indicator of the ETSI nor SIP-Connect 1.0 models, so how the IP-PBX be=
haves "normally" is unknown a priori.

And of course the IP-PBX could always be configured to just do ETSI or SIP-=
Connect 1.0 models, as has previously been the case; and the nice thing wit=
h Martini is if the SSP only supports Martini then it can indicate the opti=
on-tag is required in its response (by responding to the REGISTER with a 42=
1).

-hadriel

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of bruno.chatras@orange-ftgroup.com
Sent: Monday, March 29, 2010 12:35 PM
To: ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

I fully agree with what Hans Erik has said in the Postscriptum "it would be=
 really, really, really good if they (the IP PBX) would interwork on the UN=
I with the IMS business trunking". I believe that most operators share the =
same view... and presumably some vendors as well...


--_000_FF84A09F50A6DC48ACB6714F4666CC745E21B5A8ECESESSCMS0354e_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.3790.4639" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagTyp=
e><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: MS Mincho;
}
@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: @MS Mincho;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dblue link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D464403603-30032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D464403603-30032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D464403603-30032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Having an option-tag is fine, but it will only hel=
p for=20
negotiation, and to figure out what is supported. You are still going to en=
d up=20
having two different solutions that do not interwork with each=20
other.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D464403603-30032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D464403603-30032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D464403603-30032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D464403603-30032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Christer</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> martini-bounces@ietf.org=20
[mailto:martini-bounces@ietf.org] <B>On Behalf Of </B>Hadriel=20
Kaplan<BR><B>Sent:</B> 29. maaliskuuta 2010 22:16<BR><B>To:</B>=20
bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com;=20
john.elwell@siemens-enterprise.com<BR><B>Cc:</B>=20
martini@ietf.org<BR><B>Subject:</B> Re: [martini] #21: 3.2.2 describes an i=
ssue=20
with some PBX<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Absolutely &#821=
1; that&#8217;s one=20
of the advantages of the Martini mechanism having an options-tag. &nbsp;If =
the=20
IP-PBX indicates the option-tag but the REGISTER response does not (i.e., i=
s=20
rejected with 420), then the IP-PBX would revert to doing whatever it is it=
=20
&#8220;normally&#8221; does.&nbsp; Unfortunately there was no explicit indi=
cator of the ETSI=20
nor SIP-Connect 1.0 models, so how the IP-PBX behaves &#8220;normally&#8221=
; is unknown a=20
priori.&nbsp; <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p=
></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">And of course th=
e=20
IP-PBX could always be configured to just do ETSI or SIP-Connect 1.0 models=
, as=20
has previously been the case; and the nice thing with Martini is if the SSP=
 only=20
supports Martini then it can indicate the option-tag is required in its res=
ponse=20
(by responding to the REGISTER with a 421).<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p=
></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">-hadriel<o:p></o=
:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p=
></SPAN></FONT></P>
<DIV=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium =
none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt solid=
; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT=20
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SP=
AN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"=
>=20
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <B><SPAN=20
style=3D"FONT-WEIGHT: bold">On Behalf Of=20
</SPAN></B>bruno.chatras@orange-ftgroup.com<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, March 29, 2010 12:35=20
PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> ietf.hanserik@gma=
il.com;=20
john.elwell@siemens-enterprise.com<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> <st1:PersonName=20
w:st=3D"on">martini@ietf.org</st1:PersonName><BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [martini] #21: 3.2.2 de=
scribes=20
an issue with some PBX</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I fully agree with what Hans =
Erik=20
has said in the Postscriptum&nbsp;"it would be really, really, really good =
if=20
they (the IP PBX) would interwork on the UNI with the IMS business=20
trunking".&nbsp;I believe that most operators share the same view... and=20
presumably some vendors as well...</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV></DIV></=
BODY></HTML>

--_000_FF84A09F50A6DC48ACB6714F4666CC745E21B5A8ECESESSCMS0354e_--

From bruno.chatras@orange-ftgroup.com  Tue Mar 30 00:38:26 2010
Return-Path: <bruno.chatras@orange-ftgroup.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 C23FA3A6974 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 00:38:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.482
X-Spam-Level: *
X-Spam-Status: No, score=1.482 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
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 qxzxmWu-9J9N for <martini@core3.amsl.com>; Tue, 30 Mar 2010 00:38:25 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by core3.amsl.com (Postfix) with ESMTP id 5F7AF3A6838 for <martini@ietf.org>; Tue, 30 Mar 2010 00:38:24 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 42A83A00650; Tue, 30 Mar 2010 09:36:38 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail2.rd.francetelecom.com (Postfix) with ESMTP id 9D75EA0066B; Tue, 30 Mar 2010 09:32:44 +0200 (CEST)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 30 Mar 2010 09:32:24 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CACFDB.238599B2"
Date: Tue, 30 Mar 2010 09:32:23 +0200
Message-ID: <9ECCF01B52E7AB408A7EB853526421410146361C@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79E928E3@mail>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNgAAFPnSAAA9iCcAAaSjUQ
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net><g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com><9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr> <011a01cacf62$55509710$fff1c530$@us> <430FC6BDED356B4C8498F634416644A91A79E928E3@mail>
From: <bruno.chatras@orange-ftgroup.com>
To: <HKaplan@acmepacket.com>, <richard@shockey.us>, <ietf.hanserik@gmail.com>, <john.elwell@siemens-enterprise.com>
X-OriginalArrivalTime: 30 Mar 2010 07:32:24.0102 (UTC) FILETIME=[23ED4460:01CACFDB]
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 30 Mar 2010 07:38:26 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CACFDB.238599B2
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I guess the large IMS deployments where you discovered the problems =
identified in the drafts were based on versions of the IMS that did not =
include the "loose-route" mechanism (e.g. Release 7) and/or were using =
IP PBX that were not compliant to IMS Release 8. Right?
=20


________________________________

	De : Hadriel Kaplan [mailto:HKaplan@acmepacket.com]=20
	Envoy=E9 : lundi 29 mars 2010 21:00
	=C0 : Richard Shockey; CHATRAS Bruno RD-CORE-ISS; =
ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com
	Cc : martini@ietf.org
	Objet : RE: [martini] #21: 3.2.2 describes an issue with some PBX
=09
=09

	Yes, in several large IMS deployments.  That's where we discovered some =
of the problems identified in the drafts.

	-hadriel

	=20

=09
________________________________


	From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On =
Behalf Of Richard Shockey
	Sent: Monday, March 29, 2010 1:08 PM
	To: bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com; =
john.elwell@siemens-enterprise.com
	Cc: martini@ietf.org
	Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

	=20

	Has any of this IMS business trunking stuff actually deployed?


------_=_NextPart_001_01CACFDB.238599B2
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags" xmlns:ns6 =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: MS Mincho;
}
@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: @MS Mincho;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
A:link {
	mso-style-priority: 99
}
SPAN.MSOHYPERLINK {
	mso-style-priority: 99
}
A:visited {
	mso-style-priority: 99
}
SPAN.MSOHYPERLINKFOLLOWED {
	mso-style-priority: 99
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: #1f497d; FONT-FAMILY: Calibri; mso-style-type: personal
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D119003007-30032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I guess the large IMS deployments where you =
discovered the=20
problems identified in the drafts were based on versions of the IMS that =
did not=20
include the "loose-route" mechanism (e.g. Release 7) and/or were using =
IP PBX=20
that were not compliant to&nbsp;IMS Release 8. =
Right?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D119003007-30032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Dfr dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>De&nbsp;:</B> Hadriel Kaplan=20
  [mailto:HKaplan@acmepacket.com] <BR><B>Envoy=E9&nbsp;:</B> lundi 29 =
mars 2010=20
  21:00<BR><B>=C0&nbsp;:</B> Richard Shockey; CHATRAS Bruno RD-CORE-ISS; =

  ietf.hanserik@gmail.com;=20
  john.elwell@siemens-enterprise.com<BR><B>Cc&nbsp;:</B>=20
  martini@ietf.org<BR><B>Objet&nbsp;:</B> RE: [martini] #21: 3.2.2 =
describes an=20
  issue with some PBX<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Yes, in =
several large=20
  IMS deployments. &nbsp;That=92s where we discovered some of the =
problems=20
  identified in the drafts.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">-hadriel<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <DIV>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
  martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <B><SPAN=20
  style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Richard =
Shockey<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, March 29, 2010 =
1:08=20
  PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
  bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com;=20
  john.elwell@siemens-enterprise.com<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> <st1:PersonName=20
  w:st=3D"on">martini@ietf.org</st1:PersonName><BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [martini] #21: =
3.2.2=20
  describes an issue with some PBX</SPAN></FONT><o:p></o:p></P></DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DCalibri color=3D#1f497d =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: Calibri">Has =
any of this=20
  IMS business trunking stuff actually=20
  =
deployed?<o:p></o:p></SPAN></FONT></P></DIV></DIV></BLOCKQUOTE></BODY></H=
TML>

------_=_NextPart_001_01CACFDB.238599B2--

From ietf.hanserik@gmail.com  Tue Mar 30 03:48:42 2010
Return-Path: <ietf.hanserik@gmail.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 D63AC3A698C for <martini@core3.amsl.com>; Tue, 30 Mar 2010 03:48:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.809
X-Spam-Level: 
X-Spam-Status: No, score=0.809 tagged_above=-999 required=5 tests=[AWL=-0.323,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 zmeLWudBqSCk for <martini@core3.amsl.com>; Tue, 30 Mar 2010 03:48:41 -0700 (PDT)
Received: from mail-ew0-f224.google.com (mail-ew0-f224.google.com [209.85.219.224]) by core3.amsl.com (Postfix) with ESMTP id 7BF2B3A6835 for <martini@ietf.org>; Tue, 30 Mar 2010 03:48:40 -0700 (PDT)
Received: by ewy24 with SMTP id 24so1207228ewy.13 for <martini@ietf.org>; Tue, 30 Mar 2010 03:49:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=KJVJ63WpCKX0865EFnb8dA1M8SqlP/EU4L28EVqQRAs=; b=aUJxTf+HLulM3hcyJtp/+FI7tZRVO6xv+Ri552POuckapYmkC6xB0u8yq907QE3Ssi GS4XNeMowVUBfC9gtBeGulaz1NYez4uAnX+UlCnXNb2MLxX7ssconYlkWHNsCYhpksjZ wsZ0SkaZD0lGd0lyxC58m8dC1plC7iE4VAbKs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=sNLi1269ppMKJf3tocXx+FSUy2WNrTAQ69W5qyr6lOp+KkBO8PgqQr0jw2PKElJruj kwj8fBWFBRGO5nWboDlrlFI+4T3N+sePK+JJihaafS+2ahUniLSftbdBCcBAu2g+AjjS Nljudfb17AkCR/LZddaphdyVcOjZF8+5+5I+E=
MIME-Version: 1.0
Received: by 10.213.15.138 with HTTP; Tue, 30 Mar 2010 03:49:06 -0700 (PDT)
In-Reply-To: <A444A0F8084434499206E78C106220CADE11BA34@MCHP058A.global-ad.net>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org> <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net> <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11BA34@MCHP058A.global-ad.net>
Date: Tue, 30 Mar 2010 12:49:06 +0200
Received: by 10.213.0.212 with SMTP id 20mr1995715ebc.43.1269946146320; Tue,  30 Mar 2010 03:49:06 -0700 (PDT)
Message-ID: <x2y9ae56b1e1003300349gc3ec82c7o449ba7554b7740b3@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Content-Type: multipart/alternative; boundary=000e0ce04002ef71e504830260af
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 30 Mar 2010 10:48:42 -0000

--000e0ce04002ef71e504830260af
Content-Type: text/plain; charset=ISO-8859-1

Hi John,

Inline...

/Hans Erik van Elburg

On Mon, Mar 29, 2010 at 9:55 PM, Elwell, John <
john.elwell@siemens-enterprise.com> wrote:

> Hans Erik,
>
> I think the point you are trying to make is that it is not one-sided. The
> fact is, each side has different ways of working, and you need to have the
> two sides operating in compatible manners for it to work. In practice, I
> think there are other variants, besides the two cited in the present 3.2.2.

Yes. And there is no objective way to automatically determine what variant
the PBX or the SSP is supporting. Which is what an options tag could
resolve.


> I would suggest:
>
>        <t>Even where all information needed by the SIP-PBX is provided, in
> some deployments inbound SIP requests from the SSP have the registered
> Contact URI in the Request-URI, whereas in other deployments inbound SIP
> requests have the intended target (AOR) in the Request-URI and the Contact
> URI in the Route header field. There are other variants too.
> Interoperability problems arise when a PBX designed for or configured for
> one variant attempts to interwork with an SSP designed for or configured for
> another variant.</t>
>
Yes, slightly modified to add the objective means issue:
 <t>Even where all information needed by the SIP-PBX is provided, in some
deployments inbound SIP requests from the SSP have the registered PBX
Contact URI in the Request-URI, whereas in other deployments inbound SIP
requests have the intended target PBX user (AOR) in the Request-URI and the
Contact URI in the Route header field. There are other variants too.
Interoperability problems arise when a PBX designed for or configured for
one variant attempts to interwork with an SSP designed for or configured for
another variant. There is currently no objective means in the signalling
during registration for either party to discover what mechanism the other
side supports.</t>


> To accompany this, I think the title of the section should be changed too:
> "Inconsistent placement of information in inbound requests"
>
> Yes, slightly modified to make it more specific: "Inconsistent placement of
target URI information in inbound requests".


> John
>
> > -----Original Message-----
> > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
> > Sent: 29 March 2010 17:27
> > To: Elwell, John
> > Cc: martini@ietf.org
> > Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
> >
> > Hi John,
> >
> > I was just trying to find a text that describes the issue.
> >
> > But now the issue reads like "some PBX like apples, some like
> > bananas". To me that does not sound like a usefull issue to
> > describe in an RFC.
> >
> > So I think one or two more sentence would make clear why this
> > is an issue.
> >
> > I think there is multiple underlying issues here:
> > - PBX have different SIP profiles or all SIP-PBX are different
> > - PBX support SIP trunking flavour A, or support SIP trunking
> > flavour B
> > - SSP systems don't know what mechanism the PBX support (can
> > be resolved with explicit indicator, this draft proposes an
> > indicator for flavour B but for another purpose it seems)
> > - PBX do not know what SIP trunking flavour the SSP supports
> > (not addressed it seems)
> >
> > I don't seem to have a lucky hand with proposing an improved
> > text, so maybe you should have a go at it.
> >
> > BR,
> > /Hans Erik van Elburg
> >
> > p.s. I never said or implied that a SIP-PBX shall implement
> > IMS. But it would be really, really, really good if they
> > would interwork on the UNI with the IMS business trunking.  I
> > think that should also be in your interest and in fact you
> > have been part of that work...
> >
> >
> >
> > On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John
> > <john.elwell@siemens-enterprise.com> wrote:
> >
> >
> >       Hans Erik,
> >
> >       As an individual, I disagree with the proposed text,
> > since it is misleading. The "international standards" to
> > which you prefer are standards specific to an IMS
> > environment. The implication of the wording as proposed is
> > that SIP-PBXs ought to implement IMS specifications. And as
> > Hadriel points out, implementing those IMS specifications
> > does not eliminate the problems that the SIPconnect people
> > are trying to solve. I believe the existing text in draft-03
> > is sufficient.
> >
> >
> >       John
> >
> >       > -----Original Message-----
> >       > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
> >
> >       > Sent: 26 March 2010 23:03
> >       > To: Elwell, John
> >       > Cc: martini@ietf.org
> >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
> > with some PBX
> >       >
> >       > I will not argue with you about the validity of that argument.
> >       >
> >       > Can you agree to the modified text?
> >       >
> >       > "Request-URI vs. loose-route acceptance
> >       > Some IP-PBX do not implement international standards or SIP
> >       > profiles for SIP trunking. As a consequence some SIP-PBXs
> >       > expect that inbound SIP requests from the SSP will have the
> >       > registered Contact-URI in the Request-URI, and thus not
> >       > interoperate with the loose-route scheme of 3GPP and ETSI.
> >       > Other SIP-PBXs are fine with the Request-URI being the
> >       > intended target, but cannot handle receiving a Route header
> >       > field identifying their registered Contact-URI as a
> >       > loose-route entry."
> >       >
> >       > BR,
> >       > /Hans Erik van Elburg
> >       >
> >       >
> >       > On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
> >       > <john.elwell@siemens-enterprise.com> wrote:
> >       >
> >       >
> >       >       The IETF does not have a mechanism, and that is the
> >       > reason for the MARTINI work. In particular, the IETF has not
> >       > published the so-called loose-route mechanism. Hence the
> >       > reason for the IETF, as owner of SIP, to publish a mechanism
> >       > for bulk registrations.
> >       >
> >       >       John
> >       >
> >       >
> >       >       > -----Original Message-----
> >       >       > From: Hans Erik van Elburg
> > [mailto:ietf.hanserik@gmail.com]
> >       >       > Sent: 26 March 2010 02:21
> >       >       > To: trac@localhost.amsl.com
> >       >       > Cc: Elwell, John; martini@ietf.org
> >       >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
> >       > with some PBX
> >       >       >
> >       >       >
> >       >       > Then you should rephrase to what the real issue is:
> >       >       > "
> >       >       >
> >       >       >
> >       >       > Request-URI vs. loose-route acceptance
> >       >       >
> >       >       >
> >       >       > Some IP-PBX do not implement international
> > standards or SIP
> >       >       > profiles for SIP trunking. As a consequence
> > some SIP-PBXs
> >       >       > expect that inbound SIP requests from the SSP
> > will have the
> >       >       > registered Contact-URI in the Request-URI,
> > and thus not
> >       >       > interoperate with the loose-route scheme of
> > 3GPP and ETSI.
> >       >       > Other SIP-PBXs are fine with the Request-URI being the
> >       >       > intended target, but cannot handle receiving
> > a Route header
> >       >       > field identifying their registered Contact-URI as a
> >       >       > loose-route entry."
> >       >       >
> >       >       >
> >       >       > Is this an issue, yes. Does introducing yet another
> >       > profile help? No.
> >       >       >
> >       >       > /Hans Erik van Elburg
> >       >       >
> >       >       >
> >       >       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
> >       >       > <trac@tools.ietf.org> wrote:
> >       >       >
> >       >       >
> >       >       >       #21: 3.2.2 describes an issue with some PBX
> >       >       >
> >       >       >
> > -------------------------------------+------------------------
> >       >       > --------------
> >       >       >        Reporter:  ietf.hanserik@...
> > |        Owner:
> >       >       >
> >       >       >           Type:  defect                   |
> >       > Status:  closed
> >       >       >
> >       >       >        Priority:  minor                    |
> >       > Milestone:  milestone1
> >       >       >       Component:  reqs                     |
> >       > Version:  1.0
> >       >       >
> >       >       >        Severity:  In WG Last Call          |
> >       > Resolution:  invalid
> >       >       >        Keywords:                           |
> >       >       >
> >       >       >
> > -------------------------------------+------------------------
> >       >       > --------------
> >       >       >       Changes (by john.elwell@...):
> >       >       >
> >       >       >        * status:  new => closed
> >       >       >        * resolution:  => invalid
> >       >       >
> >       >       >
> >       >       >       Comment:
> >       >       >
> >       >       >
> >       >       >        The text of 3.2.2 just underlines the
> > fact that there
> >       >       > are different
> >       >       >        implementations around. A PBX that
> > expects the loose
> >       >       > route mechanism to be
> >       >       >        used would fail to interwork with SSPs using a
> >       >       > different mechanism (e.g.,
> >       >       >        SIPconnect 1.0), and a PBX not
> > expecting the loose
> >       >       > route mechanism to be
> >       >       >        used would fail to interwork with a loose route
> >       >       > implementation (e.g.,
> >       >       >        ETSI/3GPP). Hence the urgent need for
> > a standard.
> >       >       >
> >       >       >       --
> >       >       >       Ticket URL:
> >       >       >
> >       >
> > <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
> >       >       >
> >       >       >       martini <http://tools.ietf.org/martini/>
> >       >       >
> >       >       >
> >       >       >       _______________________________________________
> >       >       >       martini mailing list
> >       >       >       martini@ietf.org
> >       >       >       https://www.ietf.org/mailman/listinfo/martini
> >       >       >
> >       >       >
> >       >       >
> >       >       >
> >       >
> >       >
> >       >
> >
> >
> >
>

--000e0ce04002ef71e504830260af
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi John,<br><br>Inline... <br clear=3D"all"><br>/Hans Erik van Elburg<br>
<br><div class=3D"gmail_quote">On Mon, Mar 29, 2010 at 9:55 PM, Elwell, Joh=
n <span dir=3D"ltr">&lt;<a href=3D"mailto:john.elwell@siemens-enterprise.co=
m">john.elwell@siemens-enterprise.com</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px =
solid rgb(204, 204, 204); padding-left: 1ex;">
Hans Erik,<br>
<br>
I think the point you are trying to make is that it is not one-sided. The f=
act is, each side has different ways of working, and you need to have the t=
wo sides operating in compatible manners for it to work. In practice, I thi=
nk there are other variants, besides the two cited in the present 3.2.2.</b=
lockquote>
<div>Yes. And there is no objective way to automatically determine what var=
iant the PBX or the SSP is supporting. Which is what an options tag could r=
esolve.<br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt =
0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex=
;">
 I would suggest:<br>
<br>
 =A0 =A0 =A0 =A0&lt;t&gt;Even where all information needed by the SIP-PBX i=
s provided, in some deployments inbound SIP requests from the SSP have the =
registered Contact URI in the Request-URI, whereas in other deployments inb=
ound SIP requests have the intended target (AOR) in the Request-URI and the=
 Contact URI in the Route header field. There are other variants too. Inter=
operability problems arise when a PBX designed for or configured for one va=
riant attempts to interwork with an SSP designed for or configured for anot=
her variant.&lt;/t&gt;<br>
</blockquote><div>Yes, slightly modified to add the objective means issue:<=
br>=A0&lt;t&gt;Even where all information needed by the SIP-PBX is provided=
,=20
in some deployments inbound SIP requests from the SSP have the=20
registered PBX Contact URI in the Request-URI, whereas in other deployments=
=20
inbound SIP requests have the intended target PBX user (AOR) in the Request=
-URI=20
and the Contact URI in the Route header field. There are other variants=20
too. Interoperability problems arise when a PBX designed for or=20
configured for one variant attempts to interwork with an SSP designed=20
for or configured for another variant. There is currently no objective mean=
s in the signalling during registration for either party to discover what m=
echanism the other side supports.&lt;/t&gt;<br>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid=
 rgb(204, 204, 204); padding-left: 1ex;">

To accompany this, I think the title of the section should be changed too: =
&quot;Inconsistent placement of information in inbound requests&quot;<br>
<div class=3D"im"><br></div></blockquote><div>Yes, slightly modified to mak=
e it more specific: &quot;Inconsistent placement of target URI information =
in inbound requests&quot;.<br>=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204)=
; padding-left: 1ex;">
<div class=3D"im">
John<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Hans Erik van Elburg [mailto:<a href=3D"mailto:ietf.hanserik@gma=
il.com">ietf.hanserik@gmail.com</a>]<br>
</div><div><div></div><div class=3D"h5">&gt; Sent: 29 March 2010 17:27<br>
&gt; To: Elwell, John<br>
&gt; Cc: <a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
&gt; Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX<br>
&gt;<br>
&gt; Hi John,<br>
&gt;<br>
&gt; I was just trying to find a text that describes the issue.<br>
&gt;<br>
&gt; But now the issue reads like &quot;some PBX like apples, some like<br>
&gt; bananas&quot;. To me that does not sound like a usefull issue to<br>
&gt; describe in an RFC.<br>
&gt;<br>
&gt; So I think one or two more sentence would make clear why this<br>
&gt; is an issue.<br>
&gt;<br>
&gt; I think there is multiple underlying issues here:<br>
&gt; - PBX have different SIP profiles or all SIP-PBX are different<br>
&gt; - PBX support SIP trunking flavour A, or support SIP trunking<br>
&gt; flavour B<br>
&gt; - SSP systems don&#39;t know what mechanism the PBX support (can<br>
&gt; be resolved with explicit indicator, this draft proposes an<br>
&gt; indicator for flavour B but for another purpose it seems)<br>
&gt; - PBX do not know what SIP trunking flavour the SSP supports<br>
&gt; (not addressed it seems)<br>
&gt;<br>
&gt; I don&#39;t seem to have a lucky hand with proposing an improved<br>
&gt; text, so maybe you should have a go at it.<br>
&gt;<br>
&gt; BR,<br>
&gt; /Hans Erik van Elburg<br>
&gt;<br>
&gt; p.s. I never said or implied that a SIP-PBX shall implement<br>
&gt; IMS. But it would be really, really, really good if they<br>
&gt; would interwork on the UNI with the IMS business trunking. =A0I<br>
&gt; think that should also be in your interest and in fact you<br>
&gt; have been part of that work...<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John<br>
&gt; &lt;<a href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@=
siemens-enterprise.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 Hans Erik,<br>
&gt;<br>
&gt; =A0 =A0 =A0 As an individual, I disagree with the proposed text,<br>
&gt; since it is misleading. The &quot;international standards&quot; to<br>
&gt; which you prefer are standards specific to an IMS<br>
&gt; environment. The implication of the wording as proposed is<br>
&gt; that SIP-PBXs ought to implement IMS specifications. And as<br>
&gt; Hadriel points out, implementing those IMS specifications<br>
&gt; does not eliminate the problems that the SIPconnect people<br>
&gt; are trying to solve. I believe the existing text in draft-03<br>
&gt; is sufficient.<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 John<br>
&gt;<br>
&gt; =A0 =A0 =A0 &gt; -----Original Message-----<br>
&gt; =A0 =A0 =A0 &gt; From: Hans Erik van Elburg [mailto:<a href=3D"mailto:=
ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</a>]<br>
&gt;<br>
&gt; =A0 =A0 =A0 &gt; Sent: 26 March 2010 23:03<br>
&gt; =A0 =A0 =A0 &gt; To: Elwell, John<br>
&gt; =A0 =A0 =A0 &gt; Cc: <a href=3D"mailto:martini@ietf.org">martini@ietf.=
org</a><br>
&gt; =A0 =A0 =A0 &gt; Subject: Re: [martini] #21: 3.2.2 describes an issue<=
br>
&gt; with some PBX<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; I will not argue with you about the validity of that =
argument.<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; Can you agree to the modified text?<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; &quot;Request-URI vs. loose-route acceptance<br>
&gt; =A0 =A0 =A0 &gt; Some IP-PBX do not implement international standards =
or SIP<br>
&gt; =A0 =A0 =A0 &gt; profiles for SIP trunking. As a consequence some SIP-=
PBXs<br>
&gt; =A0 =A0 =A0 &gt; expect that inbound SIP requests from the SSP will ha=
ve the<br>
&gt; =A0 =A0 =A0 &gt; registered Contact-URI in the Request-URI, and thus n=
ot<br>
&gt; =A0 =A0 =A0 &gt; interoperate with the loose-route scheme of 3GPP and =
ETSI.<br>
&gt; =A0 =A0 =A0 &gt; Other SIP-PBXs are fine with the Request-URI being th=
e<br>
&gt; =A0 =A0 =A0 &gt; intended target, but cannot handle receiving a Route =
header<br>
&gt; =A0 =A0 =A0 &gt; field identifying their registered Contact-URI as a<b=
r>
&gt; =A0 =A0 =A0 &gt; loose-route entry.&quot;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; BR,<br>
&gt; =A0 =A0 =A0 &gt; /Hans Erik van Elburg<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John<br>
&gt; =A0 =A0 =A0 &gt; &lt;<a href=3D"mailto:john.elwell@siemens-enterprise.=
com">john.elwell@siemens-enterprise.com</a>&gt; wrote:<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 The IETF does not have a mechanism, and t=
hat is the<br>
&gt; =A0 =A0 =A0 &gt; reason for the MARTINI work. In particular, the IETF =
has not<br>
&gt; =A0 =A0 =A0 &gt; published the so-called loose-route mechanism. Hence =
the<br>
&gt; =A0 =A0 =A0 &gt; reason for the IETF, as owner of SIP, to publish a me=
chanism<br>
&gt; =A0 =A0 =A0 &gt; for bulk registrations.<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 John<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; -----Original Message-----<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; From: Hans Erik van Elburg<br>
&gt; [mailto:<a href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail=
.com</a>]<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; Sent: 26 March 2010 02:21<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; To: <a href=3D"mailto:trac@localhost=
.amsl.com">trac@localhost.amsl.com</a><br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; Cc: Elwell, John; <a href=3D"mailto:=
martini@ietf.org">martini@ietf.org</a><br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; Subject: Re: [martini] #21: 3.2.2 de=
scribes an issue<br>
&gt; =A0 =A0 =A0 &gt; with some PBX<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; Then you should rephrase to what the=
 real issue is:<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; &quot;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; Request-URI vs. loose-route acceptan=
ce<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; Some IP-PBX do not implement interna=
tional<br>
&gt; standards or SIP<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; profiles for SIP trunking. As a cons=
equence<br>
&gt; some SIP-PBXs<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; expect that inbound SIP requests fro=
m the SSP<br>
&gt; will have the<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; registered Contact-URI in the Reques=
t-URI,<br>
&gt; and thus not<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; interoperate with the loose-route sc=
heme of<br>
&gt; 3GPP and ETSI.<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; Other SIP-PBXs are fine with the Req=
uest-URI being the<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; intended target, but cannot handle r=
eceiving<br>
&gt; a Route header<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; field identifying their registered C=
ontact-URI as a<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; loose-route entry.&quot;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; Is this an issue, yes. Does introduc=
ing yet another<br>
&gt; =A0 =A0 =A0 &gt; profile help? No.<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; /Hans Erik van Elburg<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; On Thu, Mar 25, 2010 at 9:22 PM, mar=
tini issue tracker<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; &lt;<a href=3D"mailto:trac@tools.iet=
f.org">trac@tools.ietf.org</a>&gt; wrote:<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 #21: 3.2.2 describes an =
issue with some PBX<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; -------------------------------------+------------------------<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; --------------<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Reporter: =A0ietf.han=
serik@...<br>
&gt; | =A0 =A0 =A0 =A0Owner:<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0 =A0 Type: =A0defect =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; =A0 =A0 =A0 &gt; Status: =A0closed<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Priority: =A0minor =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0|<br>
&gt; =A0 =A0 =A0 &gt; Milestone: =A0milestone1<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 Component: =A0reqs =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; =A0 =A0 =A0 &gt; Version: =A01.0<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Severity: =A0In WG La=
st Call =A0 =A0 =A0 =A0 =A0|<br>
&gt; =A0 =A0 =A0 &gt; Resolution: =A0invalid<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Keywords: =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; -------------------------------------+------------------------<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; --------------<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 Changes (by john.elwell@=
...):<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0* status: =A0new =3D&=
gt; closed<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0* resolution: =A0=3D&=
gt; invalid<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 Comment:<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0The text of 3.2.2 jus=
t underlines the<br>
&gt; fact that there<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; are different<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0implementations aroun=
d. A PBX that<br>
&gt; expects the loose<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; route mechanism to be<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0used would fail to in=
terwork with SSPs using a<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; different mechanism (e.g.,<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0SIPconnect 1.0), and =
a PBX not<br>
&gt; expecting the loose<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; route mechanism to be<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0used would fail to in=
terwork with a loose route<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; implementation (e.g.,<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0ETSI/3GPP). Hence the=
 urgent need for<br>
&gt; a standard.<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 --<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 Ticket URL:<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/21#co=
mment:1" target=3D"_blank">http://trac.tools.ietf.org/wg/martini/trac/ticke=
t/21#comment:1</a>&gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 martini &lt;<a href=3D"h=
ttp://tools.ietf.org/martini/" target=3D"_blank">http://tools.ietf.org/mart=
ini/</a>&gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 ________________________=
_______________________<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 martini mailing list<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 <a href=3D"mailto:martin=
i@ietf.org">martini@ietf.org</a><br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 <a href=3D"https://www.i=
etf.org/mailman/listinfo/martini" target=3D"_blank">https://www.ietf.org/ma=
ilman/listinfo/martini</a><br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt; =A0 =A0 =A0 &gt;<br>
&gt;<br>
&gt;<br>
&gt; </div></div></blockquote></div><br>

--000e0ce04002ef71e504830260af--

From HKaplan@acmepacket.com  Tue Mar 30 10:02:54 2010
Return-Path: <HKaplan@acmepacket.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 70EA43A6940 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 10:02:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.724
X-Spam-Level: 
X-Spam-Status: No, score=0.724 tagged_above=-999 required=5 tests=[AWL=-0.408,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 VR6HxQcmwKxd for <martini@core3.amsl.com>; Tue, 30 Mar 2010 10:02:49 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 8C80E3A68E5 for <martini@ietf.org>; Tue, 30 Mar 2010 10:02:49 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Tue, 30 Mar 2010 13:03:18 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Tue, 30 Mar 2010 13:03:18 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "bruno.chatras@orange-ftgroup.com" <bruno.chatras@orange-ftgroup.com>, "richard@shockey.us" <richard@shockey.us>, "ietf.hanserik@gmail.com" <ietf.hanserik@gmail.com>, "john.elwell@siemens-enterprise.com" <john.elwell@siemens-enterprise.com>
Date: Tue, 30 Mar 2010 13:03:17 -0400
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNgAAFPnSAAA9iCcAAaSjUQABPeQdA=
Message-ID: <430FC6BDED356B4C8498F634416644A91A79E92ADB@mail>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net><g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com><9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr> <011a01cacf62$55509710$fff1c530$@us> <430FC6BDED356B4C8498F634416644A91A79E928E3@mail> <9ECCF01B52E7AB408A7EB853526421410146361C@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <9ECCF01B52E7AB408A7EB853526421410146361C@ftrdmel0.rd.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_430FC6BDED356B4C8498F634416644A91A79E92ADBmail_"
MIME-Version: 1.0
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 30 Mar 2010 17:02:54 -0000

--_000_430FC6BDED356B4C8498F634416644A91A79E92ADBmail_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Some of them must have included the loose-route, because we had to go fix o=
ur own behavior for that mode (we previously expected the registered contac=
t to be the req-uri).
Whether the IP-PBX's are compliant or not I don't know - I just know we hav=
e to modify/fix the req-uri on a case-by-case basis, requiring per-trunk co=
nfig/behavior.

-hadriel

________________________________
From: bruno.chatras@orange-ftgroup.com [mailto:bruno.chatras@orange-ftgroup=
.com]
Sent: Tuesday, March 30, 2010 3:32 AM
To: Hadriel Kaplan; richard@shockey.us; ietf.hanserik@gmail.com; john.elwel=
l@siemens-enterprise.com
Cc: martini@ietf.org
Subject: RE: [martini] #21: 3.2.2 describes an issue with some PBX

I guess the large IMS deployments where you discovered the problems identif=
ied in the drafts were based on versions of the IMS that did not include th=
e "loose-route" mechanism (e.g. Release 7) and/or were using IP PBX that we=
re not compliant to IMS Release 8. Right?


________________________________
De : Hadriel Kaplan [mailto:HKaplan@acmepacket.com]
Envoy=E9 : lundi 29 mars 2010 21:00
=C0 : Richard Shockey; CHATRAS Bruno RD-CORE-ISS; ietf.hanserik@gmail.com; =
john.elwell@siemens-enterprise.com
Cc : martini@ietf.org
Objet : RE: [martini] #21: 3.2.2 describes an issue with some PBX
Yes, in several large IMS deployments.  That's where we discovered some of =
the problems identified in the drafts.
-hadriel

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Richard Shockey
Sent: Monday, March 29, 2010 1:08 PM
To: bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com; john.elwell@=
siemens-enterprise.com
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

Has any of this IMS business trunking stuff actually deployed?

--_000_430FC6BDED356B4C8498F634416644A91A79E92ADBmail_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40"
xmlns:ns6=3D"http://schemas.microsoft.com/office/2004/12/omml">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"Person=
Name"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
	{mso-style-priority: 99
;}
span.MSOHYPERLINK
	{mso-style-priority: 99
;}
a:visited
	{mso-style-priority: 99
;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority: 99
;}

 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Calibri;
	color:#1F497D;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Some of them must have included the
loose-route, because we had to go fix our own behavior for that mode (we
previously expected the registered contact to be the req-uri).<o:p></o:p></=
span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Whether the IP-PBX&#8217;s are complia=
nt
or not I don&#8217;t know &#8211; I just know we have to modify/fix the req=
-uri
on a case-by-case basis, requiring per-trunk config/behavior.<o:p></o:p></s=
pan></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>-hadriel<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
bruno.chatras@orange-ftgroup.com [mailto:bruno.chatras@orange-ftgroup.com] =
<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, March 30, 201=
0 3:32
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName w:st=3D"=
on">Hadriel
 Kaplan</st1:PersonName>; richard@shockey.us; ietf.hanserik@gmail.com;
john.elwell@siemens-enterprise.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName w:st=3D"=
on">martini@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [martini] #21: =
3.2.2
describes an issue with some PBX</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>I guess the large IMS deployments wher=
e
you discovered the problems identified in the drafts were based on versions=
 of
the IMS that did not include the &quot;loose-route&quot; mechanism (e.g.
Release 7) and/or were using IP PBX that were not compliant to&nbsp;IMS Rel=
ease
8. Right?</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<blockquote style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0=
in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span lang=3DFR style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 face=
=3DTahoma><span
lang=3DFR style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>De=
&nbsp;:</span></font></b><font
size=3D2 face=3DTahoma><span lang=3DFR style=3D'font-size:10.0pt;font-famil=
y:Tahoma'> <st1:PersonName
w:st=3D"on">Hadriel Kaplan</st1:PersonName> [mailto:HKaplan@acmepacket.com]=
 <br>
<b><span style=3D'font-weight:bold'>Envoy=E9&nbsp;:</span></b> lundi 29 mar=
s 2010
21:00<br>
<b><span style=3D'font-weight:bold'>=C0&nbsp;:</span></b> Richard Shockey; =
CHATRAS
Bruno RD-CORE-ISS; ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.=
com<br>
<b><span style=3D'font-weight:bold'>Cc&nbsp;:</span></b> <st1:PersonName w:=
st=3D"on">martini@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Objet&nbsp;:</span></b> RE: [martini] #=
21:
3.2.2 describes an issue with some PBX</span></font><span lang=3DFR><o:p></=
o:p></span></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Yes, in several large IMS deployments.
&nbsp;That&#8217;s where we discovered some of the problems identified in t=
he
drafts.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>-hadriel<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>Richard Shockey<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, March 29, 2010=
 1:08
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b>
bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com;
john.elwell@siemens-enterprise.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName w:st=3D"=
on">martini@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [martini] #21: =
3.2.2
describes an issue with some PBX</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>Has any of thi=
s IMS
business trunking stuff actually deployed?<o:p></o:p></span></font></p>

</div>

</blockquote>

</div>

</div>

</body>

</html>

--_000_430FC6BDED356B4C8498F634416644A91A79E92ADBmail_--

From HKaplan@acmepacket.com  Tue Mar 30 10:09:38 2010
Return-Path: <HKaplan@acmepacket.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 B2DBD3A6836 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 10:09:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.733
X-Spam-Level: 
X-Spam-Status: No, score=0.733 tagged_above=-999 required=5 tests=[AWL=-0.399,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 ax-WhdgAV8g8 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 10:09:33 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 379143A67A5 for <martini@ietf.org>; Tue, 30 Mar 2010 10:09:32 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Tue, 30 Mar 2010 13:10:01 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Tue, 30 Mar 2010 13:10:01 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "bruno.chatras@orange-ftgroup.com" <bruno.chatras@orange-ftgroup.com>,  "ietf.hanserik@gmail.com" <ietf.hanserik@gmail.com>, "john.elwell@siemens-enterprise.com" <john.elwell@siemens-enterprise.com>
Date: Tue, 30 Mar 2010 13:10:00 -0400
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNgAAVBprAAEgqT0AAcL71g
Message-ID: <430FC6BDED356B4C8498F634416644A91A79E92ADF@mail>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com> <9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr> <430FC6BDED356B4C8498F634416644A91A79E928EE@mail> <FF84A09F50A6DC48ACB6714F4666CC745E21B5A8EC@ESESSCMS0354.eemea.ericsson.se>
In-Reply-To: <FF84A09F50A6DC48ACB6714F4666CC745E21B5A8EC@ESESSCMS0354.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_430FC6BDED356B4C8498F634416644A91A79E92ADFmail_"
MIME-Version: 1.0
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 30 Mar 2010 17:09:38 -0000

--_000_430FC6BDED356B4C8498F634416644A91A79E92ADFmail_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Sure, if you have a box that can only do X, and another than can only do Y,=
 you've got a problem.
You're already in that situation now, if you have a SIP-Connect 1.0 PBX and=
 an IMS network, or a SIP-Connect 1.0 network and an IMS IP-PBX.  Heck, SIP=
-Connect 1.0 talking to itself has problems, since the registration mechani=
sm was so under-specified in it.
There's not much we can do about that, is there?

-hadriel

________________________________
From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Sent: Monday, March 29, 2010 11:41 PM
To: Hadriel Kaplan; bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.c=
om; john.elwell@siemens-enterprise.com
Cc: martini@ietf.org
Subject: RE: [martini] #21: 3.2.2 describes an issue with some PBX

Hi,

Having an option-tag is fine, but it will only help for negotiation, and to=
 figure out what is supported. You are still going to end up having two dif=
ferent solutions that do not interwork with each other.

Regards,

Christer

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Hadriel Kaplan
Sent: 29. maaliskuuta 2010 22:16
To: bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com; john.elwell@=
siemens-enterprise.com
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
Absolutely - that's one of the advantages of the Martini mechanism having a=
n options-tag.  If the IP-PBX indicates the option-tag but the REGISTER res=
ponse does not (i.e., is rejected with 420), then the IP-PBX would revert t=
o doing whatever it is it "normally" does.  Unfortunately there was no expl=
icit indicator of the ETSI nor SIP-Connect 1.0 models, so how the IP-PBX be=
haves "normally" is unknown a priori.

And of course the IP-PBX could always be configured to just do ETSI or SIP-=
Connect 1.0 models, as has previously been the case; and the nice thing wit=
h Martini is if the SSP only supports Martini then it can indicate the opti=
on-tag is required in its response (by responding to the REGISTER with a 42=
1).

-hadriel

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of bruno.chatras@orange-ftgroup.com
Sent: Monday, March 29, 2010 12:35 PM
To: ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

I fully agree with what Hans Erik has said in the Postscriptum "it would be=
 really, really, really good if they (the IP PBX) would interwork on the UN=
I with the IMS business trunking". I believe that most operators share the =
same view... and presumably some vendors as well...


--_000_430FC6BDED356B4C8498F634416644A91A79E92ADFmail_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"Person=
Name"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Sure, if you have a box that can only =
do
X, and another than can only do Y, you&#8217;ve got a problem.<o:p></o:p></=
span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>You&#8217;re already in that situation=
 now,
if you have a SIP-Connect 1.0 PBX and an IMS network, or a SIP-Connect 1.0
network and an IMS IP-PBX.&nbsp; Heck, SIP-Connect 1.0 talking to itself ha=
s
problems, since the registration mechanism was so under-specified in it.<o:=
p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>There&#8217;s not much we can do about
that, is there?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>-hadriel<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> <st1:Per=
sonName
w:st=3D"on">Christer Holmberg</st1:PersonName>
[mailto:christer.holmberg@ericsson.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, March 29, 2010=
 11:41
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName w:st=3D"=
on">Hadriel
 Kaplan</st1:PersonName>; bruno.chatras@orange-ftgroup.com;
ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName w:st=3D"=
on">martini@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [martini] #21: =
3.2.2
describes an issue with some PBX</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Hi,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Having an option-tag is fine, but it w=
ill
only help for negotiation, and to figure out what is supported. You are sti=
ll
going to end up having two different solutions that do not interwork with e=
ach
other.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Regards,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Christer</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 face=
=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span>=
</font></b><font
size=3D2 face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>=
 martini-bounces@ietf.org
[mailto:martini-bounces@ietf.org] <b><span style=3D'font-weight:bold'>On Be=
half
Of </span></b><st1:PersonName w:st=3D"on">Hadriel Kaplan</st1:PersonName><b=
r>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 29. maaliskuuta 2010 2=
2:16<br>
<b><span style=3D'font-weight:bold'>To:</span></b>
bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com;
john.elwell@siemens-enterprise.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName w:st=3D"=
on">martini@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [martini] #21: =
3.2.2
describes an issue with some PBX</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Absolutely &#8211; that&#8217;s one of=
 the
advantages of the Martini mechanism having an options-tag. &nbsp;If the IP-=
PBX
indicates the option-tag but the REGISTER response does not (i.e., is rejec=
ted
with 420), then the IP-PBX would revert to doing whatever it is it
&#8220;normally&#8221; does.&nbsp; Unfortunately there was no explicit
indicator of the ETSI nor SIP-Connect 1.0 models, so how the IP-PBX behaves
&#8220;normally&#8221; is unknown a priori.&nbsp; <o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>And of course the IP-PBX could always =
be
configured to just do ETSI or SIP-Connect 1.0 models, as has previously bee=
n
the case; and the nice thing with Martini is if the SSP only supports Marti=
ni
then it can indicate the option-tag is required in its response (by respond=
ing
to the REGISTER with a 421).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>-hadriel<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>bruno.chatras@orange-ftg=
roup.com<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, March 29, 2010=
 12:35
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> ietf.hanserik@gmail.com;
john.elwell@siemens-enterprise.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName w:st=3D"=
on">martini@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [martini] #21: =
3.2.2
describes an issue with some PBX</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>I fully agree with what Hans Erik has said in the
Postscriptum&nbsp;&quot;it would be really, really, really good if they (th=
e IP
PBX) would interwork on the UNI with the IMS business trunking&quot;.&nbsp;=
I
believe that most operators share the same view... and presumably some vend=
ors
as well...</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

</div>

</div>

</body>

</html>

--_000_430FC6BDED356B4C8498F634416644A91A79E92ADFmail_--

From john.elwell@siemens-enterprise.com  Tue Mar 30 10:10:59 2010
Return-Path: <john.elwell@siemens-enterprise.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 BEF893A6896 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 10:10:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.82
X-Spam-Level: 
X-Spam-Status: No, score=0.82 tagged_above=-999 required=5 tests=[AWL=-0.312,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 9M8CiP4JImWs for <martini@core3.amsl.com>; Tue, 30 Mar 2010 10:10:57 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 941433A6781 for <martini@ietf.org>; Tue, 30 Mar 2010 10:10:56 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1396454; Tue, 30 Mar 2010 19:11:25 +0200
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 8039B1EB82AB; Tue, 30 Mar 2010 19:11:25 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Tue, 30 Mar 2010 19:11:25 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>
Date: Tue, 30 Mar 2010 19:11:23 +0200
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrP+MFnIq24ETOlSXOXI8bY3L6MeAAMzzdQ
Message-ID: <A444A0F8084434499206E78C106220CADE11BF8E@MCHP058A.global-ad.net>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org> <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net> <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11BA34@MCHP058A.global-ad.net> <x2y9ae56b1e1003300349gc3ec82c7o449ba7554b7740b3@mail.gmail.com>
In-Reply-To: <x2y9ae56b1e1003300349gc3ec82c7o449ba7554b7740b3@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A444A0F8084434499206E78C106220CADE11BF8EMCHP058Aglobala_"
MIME-Version: 1.0
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 30 Mar 2010 17:11:00 -0000

--_000_A444A0F8084434499206E78C106220CADE11BF8EMCHP058Aglobala_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

OK, fixed in my working copy.

John

________________________________
From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
Sent: 30 March 2010 11:49
To: Elwell, John
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

Hi John,

Inline...

/Hans Erik van Elburg

On Mon, Mar 29, 2010 at 9:55 PM, Elwell, John <john.elwell@siemens-enterpri=
se.com<mailto:john.elwell@siemens-enterprise.com>> wrote:
Hans Erik,

I think the point you are trying to make is that it is not one-sided. The f=
act is, each side has different ways of working, and you need to have the t=
wo sides operating in compatible manners for it to work. In practice, I thi=
nk there are other variants, besides the two cited in the present 3.2.2.
Yes. And there is no objective way to automatically determine what variant =
the PBX or the SSP is supporting. Which is what an options tag could resolv=
e.

I would suggest:

       <t>Even where all information needed by the SIP-PBX is provided, in =
some deployments inbound SIP requests from the SSP have the registered Cont=
act URI in the Request-URI, whereas in other deployments inbound SIP reques=
ts have the intended target (AOR) in the Request-URI and the Contact URI in=
 the Route header field. There are other variants too. Interoperability pro=
blems arise when a PBX designed for or configured for one variant attempts =
to interwork with an SSP designed for or configured for another variant.</t=
>
Yes, slightly modified to add the objective means issue:
 <t>Even where all information needed by the SIP-PBX is provided, in some d=
eployments inbound SIP requests from the SSP have the registered PBX Contac=
t URI in the Request-URI, whereas in other deployments inbound SIP requests=
 have the intended target PBX user (AOR) in the Request-URI and the Contact=
 URI in the Route header field. There are other variants too. Interoperabil=
ity problems arise when a PBX designed for or configured for one variant at=
tempts to interwork with an SSP designed for or configured for another vari=
ant. There is currently no objective means in the signalling during registr=
ation for either party to discover what mechanism the other side supports.<=
/t>

To accompany this, I think the title of the section should be changed too: =
"Inconsistent placement of information in inbound requests"

Yes, slightly modified to make it more specific: "Inconsistent placement of=
 target URI information in inbound requests".

John

> -----Original Message-----
> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto:ietf.ha=
nserik@gmail.com>]
> Sent: 29 March 2010 17:27
> To: Elwell, John
> Cc: martini@ietf.org<mailto:martini@ietf.org>
> Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>
> Hi John,
>
> I was just trying to find a text that describes the issue.
>
> But now the issue reads like "some PBX like apples, some like
> bananas". To me that does not sound like a usefull issue to
> describe in an RFC.
>
> So I think one or two more sentence would make clear why this
> is an issue.
>
> I think there is multiple underlying issues here:
> - PBX have different SIP profiles or all SIP-PBX are different
> - PBX support SIP trunking flavour A, or support SIP trunking
> flavour B
> - SSP systems don't know what mechanism the PBX support (can
> be resolved with explicit indicator, this draft proposes an
> indicator for flavour B but for another purpose it seems)
> - PBX do not know what SIP trunking flavour the SSP supports
> (not addressed it seems)
>
> I don't seem to have a lucky hand with proposing an improved
> text, so maybe you should have a go at it.
>
> BR,
> /Hans Erik van Elburg
>
> p.s. I never said or implied that a SIP-PBX shall implement
> IMS. But it would be really, really, really good if they
> would interwork on the UNI with the IMS business trunking.  I
> think that should also be in your interest and in fact you
> have been part of that work...
>
>
>
> On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John
> <john.elwell@siemens-enterprise.com<mailto:john.elwell@siemens-enterprise=
.com>> wrote:
>
>
>       Hans Erik,
>
>       As an individual, I disagree with the proposed text,
> since it is misleading. The "international standards" to
> which you prefer are standards specific to an IMS
> environment. The implication of the wording as proposed is
> that SIP-PBXs ought to implement IMS specifications. And as
> Hadriel points out, implementing those IMS specifications
> does not eliminate the problems that the SIPconnect people
> are trying to solve. I believe the existing text in draft-03
> is sufficient.
>
>
>       John
>
>       > -----Original Message-----
>       > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto=
:ietf.hanserik@gmail.com>]
>
>       > Sent: 26 March 2010 23:03
>       > To: Elwell, John
>       > Cc: martini@ietf.org<mailto:martini@ietf.org>
>       > Subject: Re: [martini] #21: 3.2.2 describes an issue
> with some PBX
>       >
>       > I will not argue with you about the validity of that argument.
>       >
>       > Can you agree to the modified text?
>       >
>       > "Request-URI vs. loose-route acceptance
>       > Some IP-PBX do not implement international standards or SIP
>       > profiles for SIP trunking. As a consequence some SIP-PBXs
>       > expect that inbound SIP requests from the SSP will have the
>       > registered Contact-URI in the Request-URI, and thus not
>       > interoperate with the loose-route scheme of 3GPP and ETSI.
>       > Other SIP-PBXs are fine with the Request-URI being the
>       > intended target, but cannot handle receiving a Route header
>       > field identifying their registered Contact-URI as a
>       > loose-route entry."
>       >
>       > BR,
>       > /Hans Erik van Elburg
>       >
>       >
>       > On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
>       > <john.elwell@siemens-enterprise.com<mailto:john.elwell@siemens-en=
terprise.com>> wrote:
>       >
>       >
>       >       The IETF does not have a mechanism, and that is the
>       > reason for the MARTINI work. In particular, the IETF has not
>       > published the so-called loose-route mechanism. Hence the
>       > reason for the IETF, as owner of SIP, to publish a mechanism
>       > for bulk registrations.
>       >
>       >       John
>       >
>       >
>       >       > -----Original Message-----
>       >       > From: Hans Erik van Elburg
> [mailto:ietf.hanserik@gmail.com<mailto:ietf.hanserik@gmail.com>]
>       >       > Sent: 26 March 2010 02:21
>       >       > To: trac@localhost.amsl.com<mailto:trac@localhost.amsl.co=
m>
>       >       > Cc: Elwell, John; martini@ietf.org<mailto:martini@ietf.or=
g>
>       >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
>       > with some PBX
>       >       >
>       >       >
>       >       > Then you should rephrase to what the real issue is:
>       >       > "
>       >       >
>       >       >
>       >       > Request-URI vs. loose-route acceptance
>       >       >
>       >       >
>       >       > Some IP-PBX do not implement international
> standards or SIP
>       >       > profiles for SIP trunking. As a consequence
> some SIP-PBXs
>       >       > expect that inbound SIP requests from the SSP
> will have the
>       >       > registered Contact-URI in the Request-URI,
> and thus not
>       >       > interoperate with the loose-route scheme of
> 3GPP and ETSI.
>       >       > Other SIP-PBXs are fine with the Request-URI being the
>       >       > intended target, but cannot handle receiving
> a Route header
>       >       > field identifying their registered Contact-URI as a
>       >       > loose-route entry."
>       >       >
>       >       >
>       >       > Is this an issue, yes. Does introducing yet another
>       > profile help? No.
>       >       >
>       >       > /Hans Erik van Elburg
>       >       >
>       >       >
>       >       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
>       >       > <trac@tools.ietf.org<mailto:trac@tools.ietf.org>> wrote:
>       >       >
>       >       >
>       >       >       #21: 3.2.2 describes an issue with some PBX
>       >       >
>       >       >
> -------------------------------------+------------------------
>       >       > --------------
>       >       >        Reporter:  ietf.hanserik@...
> |        Owner:
>       >       >
>       >       >           Type:  defect                   |
>       > Status:  closed
>       >       >
>       >       >        Priority:  minor                    |
>       > Milestone:  milestone1
>       >       >       Component:  reqs                     |
>       > Version:  1.0
>       >       >
>       >       >        Severity:  In WG Last Call          |
>       > Resolution:  invalid
>       >       >        Keywords:                           |
>       >       >
>       >       >
> -------------------------------------+------------------------
>       >       > --------------
>       >       >       Changes (by john.elwell@...):
>       >       >
>       >       >        * status:  new =3D> closed
>       >       >        * resolution:  =3D> invalid
>       >       >
>       >       >
>       >       >       Comment:
>       >       >
>       >       >
>       >       >        The text of 3.2.2 just underlines the
> fact that there
>       >       > are different
>       >       >        implementations around. A PBX that
> expects the loose
>       >       > route mechanism to be
>       >       >        used would fail to interwork with SSPs using a
>       >       > different mechanism (e.g.,
>       >       >        SIPconnect 1.0), and a PBX not
> expecting the loose
>       >       > route mechanism to be
>       >       >        used would fail to interwork with a loose route
>       >       > implementation (e.g.,
>       >       >        ETSI/3GPP). Hence the urgent need for
> a standard.
>       >       >
>       >       >       --
>       >       >       Ticket URL:
>       >       >
>       >
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
>       >       >
>       >       >       martini <http://tools.ietf.org/martini/>
>       >       >
>       >       >
>       >       >       _______________________________________________
>       >       >       martini mailing list
>       >       >       martini@ietf.org<mailto:martini@ietf.org>
>       >       >       https://www.ietf.org/mailman/listinfo/martini
>       >       >
>       >       >
>       >       >
>       >       >
>       >
>       >
>       >
>
>
>


--_000_A444A0F8084434499206E78C106220CADE11BF8EMCHP058Aglobala_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.5921" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186101117-30032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>OK, fixed in my working copy.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186101117-30032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186101117-30032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>John</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Hans Erik van Elburg=20
  [mailto:ietf.hanserik@gmail.com] <BR><B>Sent:</B> 30 March 2010=20
  11:49<BR><B>To:</B> Elwell, John<BR><B>Cc:</B>=20
  martini@ietf.org<BR><B>Subject:</B> Re: [martini] #21: 3.2.2 describes an=
=20
  issue with some PBX<BR></FONT><BR></DIV>
  <DIV></DIV>Hi John,<BR><BR>Inline... <BR clear=3Dall><BR>/Hans Erik van=20
  Elburg<BR><BR>
  <DIV class=3Dgmail_quote>On Mon, Mar 29, 2010 at 9:55 PM, Elwell, John <S=
PAN=20
  dir=3Dltr>&lt;<A=20
  href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-en=
terprise.com</A>&gt;</SPAN>=20
  wrote:<BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(2=
04,204,204) 1px solid">Hans=20
    Erik,<BR><BR>I think the point you are trying to make is that it is not=
=20
    one-sided. The fact is, each side has different ways of working, and yo=
u=20
    need to have the two sides operating in compatible manners for it to wo=
rk.=20
    In practice, I think there are other variants, besides the two cited in=
 the=20
    present 3.2.2.</BLOCKQUOTE>
  <DIV>Yes. And there is no objective way to automatically determine what=20
  variant the PBX or the SSP is supporting. Which is what an options tag co=
uld=20
  resolve.<BR>&nbsp;</DIV>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(2=
04,204,204) 1px solid">I=20
    would suggest:<BR><BR>&nbsp; &nbsp; &nbsp; &nbsp;&lt;t&gt;Even where al=
l=20
    information needed by the SIP-PBX is provided, in some deployments inbo=
und=20
    SIP requests from the SSP have the registered Contact URI in the=20
    Request-URI, whereas in other deployments inbound SIP requests have the=
=20
    intended target (AOR) in the Request-URI and the Contact URI in the Rou=
te=20
    header field. There are other variants too. Interoperability problems a=
rise=20
    when a PBX designed for or configured for one variant attempts to inter=
work=20
    with an SSP designed for or configured for another=20
  variant.&lt;/t&gt;<BR></BLOCKQUOTE>
  <DIV>Yes, slightly modified to add the objective means=20
  issue:<BR>&nbsp;&lt;t&gt;Even where all information needed by the SIP-PBX=
 is=20
  provided, in some deployments inbound SIP requests from the SSP have the=
=20
  registered PBX Contact URI in the Request-URI, whereas in other deploymen=
ts=20
  inbound SIP requests have the intended target PBX user (AOR) in the=20
  Request-URI and the Contact URI in the Route header field. There are othe=
r=20
  variants too. Interoperability problems arise when a PBX designed for or=
=20
  configured for one variant attempts to interwork with an SSP designed for=
 or=20
  configured for another variant. There is currently no objective means in =
the=20
  signalling during registration for either party to discover what mechanis=
m the=20
  other side supports.&lt;/t&gt;<BR>&nbsp;</DIV>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(2=
04,204,204) 1px solid">To=20
    accompany this, I think the title of the section should be changed too:=
=20
    "Inconsistent placement of information in inbound requests"<BR>
    <DIV class=3Dim><BR></DIV></BLOCKQUOTE>
  <DIV>Yes, slightly modified to make it more specific: "Inconsistent place=
ment=20
  of target URI information in inbound requests".<BR>&nbsp;</DIV>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(2=
04,204,204) 1px solid">
    <DIV class=3Dim>John<BR><BR>&gt; -----Original Message-----<BR>&gt; Fro=
m: Hans=20
    Erik van Elburg [mailto:<A=20
    href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</A>]<BR=
></DIV>
    <DIV>
    <DIV></DIV>
    <DIV class=3Dh5>&gt; Sent: 29 March 2010 17:27<BR>&gt; To: Elwell,=20
    John<BR>&gt; Cc: <A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; Subject: =
Re:=20
    [martini] #21: 3.2.2 describes an issue with some PBX<BR>&gt;<BR>&gt; H=
i=20
    John,<BR>&gt;<BR>&gt; I was just trying to find a text that describes t=
he=20
    issue.<BR>&gt;<BR>&gt; But now the issue reads like "some PBX like appl=
es,=20
    some like<BR>&gt; bananas". To me that does not sound like a usefull is=
sue=20
    to<BR>&gt; describe in an RFC.<BR>&gt;<BR>&gt; So I think one or two mo=
re=20
    sentence would make clear why this<BR>&gt; is an issue.<BR>&gt;<BR>&gt;=
 I=20
    think there is multiple underlying issues here:<BR>&gt; - PBX have diff=
erent=20
    SIP profiles or all SIP-PBX are different<BR>&gt; - PBX support SIP tru=
nking=20
    flavour A, or support SIP trunking<BR>&gt; flavour B<BR>&gt; - SSP syst=
ems=20
    don't know what mechanism the PBX support (can<BR>&gt; be resolved with=
=20
    explicit indicator, this draft proposes an<BR>&gt; indicator for flavou=
r B=20
    but for another purpose it seems)<BR>&gt; - PBX do not know what SIP=20
    trunking flavour the SSP supports<BR>&gt; (not addressed it=20
    seems)<BR>&gt;<BR>&gt; I don't seem to have a lucky hand with proposing=
 an=20
    improved<BR>&gt; text, so maybe you should have a go at it.<BR>&gt;<BR>=
&gt;=20
    BR,<BR>&gt; /Hans Erik van Elburg<BR>&gt;<BR>&gt; p.s. I never said or=
=20
    implied that a SIP-PBX shall implement<BR>&gt; IMS. But it would be rea=
lly,=20
    really, really good if they<BR>&gt; would interwork on the UNI with the=
 IMS=20
    business trunking. &nbsp;I<BR>&gt; think that should also be in your=20
    interest and in fact you<BR>&gt; have been part of that=20
    work...<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; On Mon, Mar 29, 2010 at 5:56 PM=
,=20
    Elwell, John<BR>&gt; &lt;<A=20
    href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-=
enterprise.com</A>&gt;=20
    wrote:<BR>&gt;<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; Hans=20
    Erik,<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; As an individual, I disagree=
 with=20
    the proposed text,<BR>&gt; since it is misleading. The "international=20
    standards" to<BR>&gt; which you prefer are standards specific to an=20
    IMS<BR>&gt; environment. The implication of the wording as proposed=20
    is<BR>&gt; that SIP-PBXs ought to implement IMS specifications. And=20
    as<BR>&gt; Hadriel points out, implementing those IMS specifications<BR=
>&gt;=20
    does not eliminate the problems that the SIPconnect people<BR>&gt; are=
=20
    trying to solve. I believe the existing text in draft-03<BR>&gt; is=20
    sufficient.<BR>&gt;<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp;=20
    John<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; -----Original=20
    Message-----<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; From: Hans Erik van Elbu=
rg=20
    [mailto:<A=20
    href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</A>]<BR=
>&gt;<BR>&gt;=20
    &nbsp; &nbsp; &nbsp; &gt; Sent: 26 March 2010 23:03<BR>&gt; &nbsp; &nbs=
p;=20
    &nbsp; &gt; To: Elwell, John<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Cc: <A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; &nbsp; &n=
bsp;=20
    &nbsp; &gt; Subject: Re: [martini] #21: 3.2.2 describes an issue<BR>&gt=
;=20
    with some PBX<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
    &gt; I will not argue with you about the validity of that argument.<BR>=
&gt;=20
    &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Can you agr=
ee to=20
    the modified text?<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nb=
sp;=20
    &nbsp; &gt; "Request-URI vs. loose-route acceptance<BR>&gt; &nbsp; &nbs=
p;=20
    &nbsp; &gt; Some IP-PBX do not implement international standards or=20
    SIP<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; profiles for SIP trunking. As a=20
    consequence some SIP-PBXs<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; expect that=
=20
    inbound SIP requests from the SSP will have the<BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
    &gt; registered Contact-URI in the Request-URI, and thus not<BR>&gt; &n=
bsp;=20
    &nbsp; &nbsp; &gt; interoperate with the loose-route scheme of 3GPP and=
=20
    ETSI.<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Other SIP-PBXs are fine with th=
e=20
    Request-URI being the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; intended target=
, but=20
    cannot handle receiving a Route header<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
    field identifying their registered Contact-URI as a<BR>&gt; &nbsp; &nbs=
p;=20
    &nbsp; &gt; loose-route entry."<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&g=
t;=20
    &nbsp; &nbsp; &nbsp; &gt; BR,<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; /Hans E=
rik=20
    van Elburg<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbs=
p;=20
    &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; On Fri, Mar 26, 2010 at 9:03 PM,=
=20
    Elwell, John<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &lt;<A=20
    href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-=
enterprise.com</A>&gt;=20
    wrote:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp;=20
    &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; The IETF do=
es=20
    not have a mechanism, and that is the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
    reason for the MARTINI work. In particular, the IETF has not<BR>&gt; &n=
bsp;=20
    &nbsp; &nbsp; &gt; published the so-called loose-route mechanism. Hence=
=20
    the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; reason for the IETF, as owner of =
SIP,=20
    to publish a mechanism<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; for bulk=20
    registrations.<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp;=
=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; John<BR>&gt; &nbsp; &nbsp; &nbsp;=20
    &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
    &nbsp; &nbsp; &nbsp; &gt; -----Original Message-----<BR>&gt; &nbsp; &nb=
sp;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; From: Hans Erik van Elburg<BR>&gt=
;=20
    [mailto:<A=20
    href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</A>]<BR=
>&gt;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Sent: 26 March 2010=
=20
    02:21<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; To: <=
A=20
    href=3D"mailto:trac@localhost.amsl.com">trac@localhost.amsl.com</A><BR>=
&gt;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Cc: Elwell, John; <=
A=20
    href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; &nbsp; &n=
bsp;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Subject: Re: [martini] #21: 3.2.2=
=20
    describes an issue<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; with some PBX<BR>&=
gt;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbs=
p;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
    &nbsp; &nbsp; &nbsp; &gt; Then you should rephrase to what the real iss=
ue=20
    is:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; "<BR>&g=
t;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbs=
p;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
    &nbsp; &nbsp; &nbsp; &gt; Request-URI vs. loose-route acceptance<BR>&gt=
;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbs=
p;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
    &nbsp; &nbsp; &nbsp; &gt; Some IP-PBX do not implement international<BR=
>&gt;=20
    standards or SIP<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
 &gt;=20
    profiles for SIP trunking. As a consequence<BR>&gt; some SIP-PBXs<BR>&g=
t;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; expect that inbound=
 SIP=20
    requests from the SSP<BR>&gt; will have the<BR>&gt; &nbsp; &nbsp; &nbsp=
;=20
    &gt; &nbsp; &nbsp; &nbsp; &gt; registered Contact-URI in the=20
    Request-URI,<BR>&gt; and thus not<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nb=
sp;=20
    &nbsp; &nbsp; &gt; interoperate with the loose-route scheme of<BR>&gt; =
3GPP=20
    and ETSI.<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; O=
ther=20
    SIP-PBXs are fine with the Request-URI being the<BR>&gt; &nbsp; &nbsp;=
=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; intended target, but cannot handl=
e=20
    receiving<BR>&gt; a Route header<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbs=
p;=20
    &nbsp; &nbsp; &gt; field identifying their registered Contact-URI as=20
    a<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; loose-rou=
te=20
    entry."<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>=
&gt;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbs=
p;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Is this an issue, yes. Does=20
    introducing yet another<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; profile help?=
=20
    No.<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; /Hans Erik van=20
    Elburg<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&=
gt;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbs=
p;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; On Thu, Mar 25, 2010 at 9:22 PM,=
=20
    martini issue tracker<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &=
nbsp;=20
    &gt; &lt;<A href=3D"mailto:trac@tools.ietf.org">trac@tools.ietf.org</A>=
&gt;=20
    wrote:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&=
gt;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbs=
p;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; #21: 3.2.2=20
    describes an issue with some PBX<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbs=
p;=20
    &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbs=
p;=20
    &gt;<BR>&gt;=20
    -------------------------------------+------------------------<BR>&gt;=
=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; --------------<BR>&=
gt;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp=
;=20
    &nbsp;Reporter: &nbsp;ietf.hanserik@...<BR>&gt; | &nbsp; &nbsp; &nbsp;=
=20
    &nbsp;Owner:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
    &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
    &nbsp; &nbsp; &nbsp; &nbsp; Type: &nbsp;defect &nbsp; &nbsp; &nbsp; &nb=
sp;=20
    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
    Status: &nbsp;closed<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &n=
bsp;=20
    &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
    &nbsp; &nbsp; &nbsp;Priority: &nbsp;minor &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp;=20
    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=20
    Milestone: &nbsp;milestone1<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &n=
bsp;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; Component: &nbsp;reqs &nbsp; &nbsp; &n=
bsp;=20
    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<BR>&gt; &nbsp; &nbsp=
;=20
    &nbsp; &gt; Version: &nbsp;1.0<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
    &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbs=
p;=20
    &gt; &nbsp; &nbsp; &nbsp; &nbsp;Severity: &nbsp;In WG Last Call &nbsp;=
=20
    &nbsp; &nbsp; &nbsp; &nbsp;|<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Resoluti=
on:=20
    &nbsp;invalid<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
    &nbsp; &nbsp; &nbsp; &nbsp;Keywords: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
=20
    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<BR>&gt; &nbsp=
;=20
    &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbs=
p;=20
    &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=20
    -------------------------------------+------------------------<BR>&gt;=
=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; --------------<BR>&=
gt;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp=
;=20
    Changes (by john.elwell@...):<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
    &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbs=
p;=20
    &gt; &nbsp; &nbsp; &nbsp; &nbsp;* status: &nbsp;new =3D&gt; closed<BR>&=
gt;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp=
;=20
    &nbsp;* resolution: &nbsp;=3D&gt; invalid<BR>&gt; &nbsp; &nbsp; &nbsp; =
&gt;=20
    &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbs=
p;=20
    &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
    &nbsp; &nbsp; &nbsp; Comment:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
    &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbs=
p;=20
    &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
    &nbsp; &nbsp; &nbsp;The text of 3.2.2 just underlines the<BR>&gt; fact =
that=20
    there<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; are=20
    different<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &=
nbsp;=20
    &nbsp; &nbsp; &nbsp;implementations around. A PBX that<BR>&gt; expects =
the=20
    loose<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; route=
=20
    mechanism to be<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; =
&gt;=20
    &nbsp; &nbsp; &nbsp; &nbsp;used would fail to interwork with SSPs using=
=20
    a<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; different=
=20
    mechanism (e.g.,<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
 &gt;=20
    &nbsp; &nbsp; &nbsp; &nbsp;SIPconnect 1.0), and a PBX not<BR>&gt; expec=
ting=20
    the loose<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; r=
oute=20
    mechanism to be<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; =
&gt;=20
    &nbsp; &nbsp; &nbsp; &nbsp;used would fail to interwork with a loose=20
    route<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;=20
    implementation (e.g.,<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &=
nbsp;=20
    &gt; &nbsp; &nbsp; &nbsp; &nbsp;ETSI/3GPP). Hence the urgent need=20
    for<BR>&gt; a standard.<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
    &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
    &nbsp; &nbsp; &nbsp; --<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; Ticket URL:<BR>&gt; &nbsp; &nbsp; &nbs=
p;=20
    &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt=
;=20
    &lt;<A href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/21#com=
ment:1"=20
    target=3D_blank>http://trac.tools.ietf.org/wg/martini/trac/ticket/21#co=
mment:1</A>&gt;<BR>&gt;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbs=
p;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; martini &lt;=
<A=20
    href=3D"http://tools.ietf.org/martini/"=20
    target=3D_blank>http://tools.ietf.org/martini/</A>&gt;<BR>&gt; &nbsp; &=
nbsp;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
    &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbs=
p;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
    _______________________________________________<BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
    &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; martini mailing=20
    list<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
    &nbsp; &nbsp; <A href=3D"mailto:martini@ietf.org">martini@ietf.org</A><=
BR>&gt;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp=
; <A=20
    href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
    target=3D_blank>https://www.ietf.org/mailman/listinfo/martini</A><BR>&g=
t;=20
    &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbs=
p;=20
    &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
    &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbs=
p;=20
    &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nb=
sp;=20
    &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
  </DIV></DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>

--_000_A444A0F8084434499206E78C106220CADE11BF8EMCHP058Aglobala_--

From bruno.chatras@orange-ftgroup.com  Tue Mar 30 10:26:39 2010
Return-Path: <bruno.chatras@orange-ftgroup.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 20FAE3A6999 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 10:26:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.482
X-Spam-Level: *
X-Spam-Status: No, score=1.482 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
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 BhDB5lBSsAbg for <martini@core3.amsl.com>; Tue, 30 Mar 2010 10:26:36 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by core3.amsl.com (Postfix) with ESMTP id 497D33A6850 for <martini@ietf.org>; Tue, 30 Mar 2010 10:26:35 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 37F40A005F5; Tue, 30 Mar 2010 19:16:03 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail2.rd.francetelecom.com (Postfix) with ESMTP id 24975A005FF; Tue, 30 Mar 2010 19:16:03 +0200 (CEST)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 30 Mar 2010 19:15:55 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAD02C.A81E2591"
Date: Tue, 30 Mar 2010 19:15:52 +0200
Message-ID: <9ECCF01B52E7AB408A7EB853526421410148E713@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79E92ADB@mail>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNgAAFPnSAAA9iCcAAaSjUQABPeQdAAAE/sIA==
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net><g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com><9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr> <011a01cacf62$55509710$fff1c530$@us> <430FC6BDED356B4C8498F634416644A91A79E928E3@mail> <9ECCF01B52E7AB408A7EB853526421410146361C@ftrdmel0.rd.francetelecom.fr> <430FC6BDED356B4C8498F634416644A91A79E92ADB@mail>
From: <bruno.chatras@orange-ftgroup.com>
To: <HKaplan@acmepacket.com>, <richard@shockey.us>, <ietf.hanserik@gmail.com>, <john.elwell@siemens-enterprise.com>
X-OriginalArrivalTime: 30 Mar 2010 17:15:55.0610 (UTC) FILETIME=[A8696BA0:01CAD02C]
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 30 Mar 2010 17:26:39 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CAD02C.A81E2591
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

OK. If loose-route was implemented in some of these IMS networks (I =
guess I know at least one of them) and you had to modify the R-URI on a =
per-trunk basis, it just means that some of the IP-PBXs connected to =
them were not IMS-compliant. Quite predictable as this loose-route =
mechanism is relatively new and therefore not yet available on all =
systems. Similarly, if a network implements the GIN solution, you will =
have to modify the R-URI on per-trunk basis because some of the IP-PBXs =
will be loose-route compliant and will therefore not be GIN-compliant. =
Where is the improvement compared to the current situation?
=20
________________________________

De : Hadriel Kaplan [mailto:HKaplan@acmepacket.com]=20
Envoy=E9 : mardi 30 mars 2010 19:03
=C0 : CHATRAS Bruno RD-CORE-ISS; richard@shockey.us; =
ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com
Cc : martini@ietf.org
Objet : RE: [martini] #21: 3.2.2 describes an issue with some PBX



	Some of them must have included the loose-route, because we had to go =
fix our own behavior for that mode (we previously expected the =
registered contact to be the req-uri).

	Whether the IP-PBX's are compliant or not I don't know - I just know we =
have to modify/fix the req-uri on a case-by-case basis, requiring =
per-trunk config/behavior.

	=20

	-hadriel

	=20

=09
________________________________


	From: bruno.chatras@orange-ftgroup.com =
[mailto:bruno.chatras@orange-ftgroup.com]=20
	Sent: Tuesday, March 30, 2010 3:32 AM
	To: Hadriel Kaplan; richard@shockey.us; ietf.hanserik@gmail.com; =
john.elwell@siemens-enterprise.com
	Cc: martini@ietf.org
	Subject: RE: [martini] #21: 3.2.2 describes an issue with some PBX

	=20

	I guess the large IMS deployments where you discovered the problems =
identified in the drafts were based on versions of the IMS that did not =
include the "loose-route" mechanism (e.g. Release 7) and/or were using =
IP PBX that were not compliant to IMS Release 8. Right?

	=20

		=20

	=09
________________________________


		De : Hadriel Kaplan [mailto:HKaplan@acmepacket.com]=20
		Envoy=E9 : lundi 29 mars 2010 21:00
		=C0 : Richard Shockey; CHATRAS Bruno RD-CORE-ISS; =
ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com
		Cc : martini@ietf.org
		Objet : RE: [martini] #21: 3.2.2 describes an issue with some PBX

		Yes, in several large IMS deployments.  That's where we discovered =
some of the problems identified in the drafts.

		-hadriel

		=20

	=09
________________________________


		From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On =
Behalf Of Richard Shockey
		Sent: Monday, March 29, 2010 1:08 PM
		To: bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com; =
john.elwell@siemens-enterprise.com
		Cc: martini@ietf.org
		Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

		=20

		Has any of this IMS business trunking stuff actually deployed?


------_=_NextPart_001_01CAD02C.A81E2591
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags" xmlns:ns6 =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: MS Mincho;
}
@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: @MS Mincho;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
A:link {
	mso-style-priority: 99
}
SPAN.MSOHYPERLINK {
	mso-style-priority: 99
}
A:visited {
	mso-style-priority: 99
}
SPAN.MSOHYPERLINKFOLLOWED {
	mso-style-priority: 99
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: #1f497d; FONT-FAMILY: Calibri; mso-style-type: personal
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle19 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D918490717-30032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>OK. If loose-route was implemented in some of =
these IMS=20
networks (I guess I know at least one of them) and you had to modify the =
R-URI=20
on a per-trunk basis, it just&nbsp;means that some of the IP-PBXs =
connected to=20
them were not IMS-compliant. Quite predictable as this loose-route =
mechanism is=20
relatively new and therefore not yet available on all systems. =
Similarly, if a=20
network implements the GIN solution, you will have to modify the R-URI =
on=20
per-trunk basis because some of the IP-PBXs will be loose-route =
compliant and=20
will therefore not be GIN-compliant. Where is the improvement compared =
to the=20
current situation?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D918490717-30032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DTahoma =
size=3D2><B>De&nbsp;:</B> Hadriel Kaplan=20
[mailto:HKaplan@acmepacket.com] <BR><B>Envoy=E9&nbsp;:</B> mardi 30 mars =
2010=20
19:03<BR><B>=C0&nbsp;:</B> CHATRAS Bruno RD-CORE-ISS; =
richard@shockey.us;=20
ietf.hanserik@gmail.com; =
john.elwell@siemens-enterprise.com<BR><B>Cc&nbsp;:</B>=20
martini@ietf.org<BR><B>Objet&nbsp;:</B> RE: [martini] #21: 3.2.2 =
describes an=20
issue with some PBX<BR></FONT><BR></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Some of =
them must=20
  have included the loose-route, because we had to go fix our own =
behavior for=20
  that mode (we previously expected the registered contact to be the=20
  req-uri).<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Whether the =
IP-PBX=92s=20
  are compliant or not I don=92t know =96 I just know we have to =
modify/fix the=20
  req-uri on a case-by-case basis, requiring per-trunk=20
  config/behavior.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">-hadriel<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <DIV>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
  bruno.chatras@orange-ftgroup.com =
[mailto:bruno.chatras@orange-ftgroup.com]=20
  <BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, =
March 30,=20
  2010 3:32 AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
  <st1:PersonName w:st=3D"on">Hadriel Kaplan</st1:PersonName>; =
richard@shockey.us;=20
  ietf.hanserik@gmail.com; =
john.elwell@siemens-enterprise.com<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> <st1:PersonName=20
  w:st=3D"on">martini@ietf.org</st1:PersonName><BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [martini] #21: =
3.2.2=20
  describes an issue with some PBX</SPAN></FONT><o:p></o:p></P></DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I guess the =
large IMS=20
  deployments where you discovered the problems identified in the drafts =
were=20
  based on versions of the IMS that did not include the "loose-route" =
mechanism=20
  (e.g. Release 7) and/or were using IP PBX that were not compliant =
to&nbsp;IMS=20
  Release 8. Right?</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <BLOCKQUOTE=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN lang=3DFR =
style=3D"FONT-SIZE: 12pt">
    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></FONT></DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
    size=3D2><SPAN lang=3DFR=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">De&nbsp;:</SPAN></FONT></B><FONT=20
    face=3DTahoma size=3D2><SPAN lang=3DFR=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> <st1:PersonName=20
    w:st=3D"on">Hadriel Kaplan</st1:PersonName> =
[mailto:HKaplan@acmepacket.com]=20
    <BR><B><SPAN style=3D"FONT-WEIGHT: bold">Envoy=E9&nbsp;:</SPAN></B> =
lundi 29=20
    mars 2010 21:00<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">=C0&nbsp;:</SPAN></B>=20
    Richard Shockey; CHATRAS Bruno RD-CORE-ISS; ietf.hanserik@gmail.com; =

    john.elwell@siemens-enterprise.com<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Cc&nbsp;:</SPAN></B> <st1:PersonName=20
    w:st=3D"on">martini@ietf.org</st1:PersonName><BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Objet&nbsp;:</SPAN></B> RE: [martini] =
#21: 3.2.2=20
    describes an issue with some PBX</SPAN></FONT><SPAN=20
    lang=3DFR><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Yes, in =
several=20
    large IMS deployments. &nbsp;That=92s where we discovered some of =
the problems=20
    identified in the drafts.<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">-hadriel<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <DIV=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
    <DIV>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></FONT></DIV>
    <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
    face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
    martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <B><SPAN=20
    style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Richard=20
    Shockey<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> =
Monday, March=20
    29, 2010 1:08 PM<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B>=20
    bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com;=20
    john.elwell@siemens-enterprise.com<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> <st1:PersonName=20
    w:st=3D"on">martini@ietf.org</st1:PersonName><BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [martini] #21: =
3.2.2=20
    describes an issue with some PBX</SPAN></FONT><o:p></o:p></P></DIV>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DCalibri color=3D#1f497d =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: Calibri">Has =
any of=20
    this IMS business trunking stuff actually=20
    =
deployed?<o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></DIV></DIV></BL=
OCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CAD02C.A81E2591--

From richard@shockey.us  Tue Mar 30 10:27:50 2010
Return-Path: <richard@shockey.us>
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 9DF5C3A6A7D for <martini@core3.amsl.com>; Tue, 30 Mar 2010 10:27:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.132
X-Spam-Level: *
X-Spam-Status: No, score=1.132 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 BNFQtgFPWo39 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 10:27:43 -0700 (PDT)
Received: from outbound-mail-359.bluehost.com (outbound-mail-359.bluehost.com [66.147.249.253]) by core3.amsl.com (Postfix) with SMTP id 244EE3A6850 for <martini@ietf.org>; Tue, 30 Mar 2010 10:27:43 -0700 (PDT)
Received: (qmail 15499 invoked by uid 0); 30 Mar 2010 17:28:12 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy1.bluehost.com.bluehost.com with SMTP; 30 Mar 2010 17:28:12 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=TkmSGX50Su3ba5/SOiqyg7bAQrDhVQ2Uzl6o0tW2uleM+aA+VCD0410yvBwNSOa7DkfqCszAT+Ja4DREZKpdnTkgkRwZnSWdIol8/6B/o+jt8AMLzcxJmXgKGIxBxdgt;
Received: from pool-173-66-69-79.washdc.fios.verizon.net ([173.66.69.79] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from <richard@shockey.us>) id 1NwfEa-0002iD-Ak; Tue, 30 Mar 2010 11:28:12 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Christer Holmberg'" <christer.holmberg@ericsson.com>, "'Hadriel Kaplan'" <HKaplan@acmepacket.com>, <bruno.chatras@orange-ftgroup.com>, <ietf.hanserik@gmail.com>, <john.elwell@siemens-enterprise.com>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net>	<g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com>	<9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr>	<430FC6BDED356B4C8498F634416644A91A79E928EE@mail> <FF84A09F50A6DC48ACB6714F4666CC745E21B5A8EC@ESESSCMS0354.eemea.ericsson.se>
In-Reply-To: <FF84A09F50A6DC48ACB6714F4666CC745E21B5A8EC@ESESSCMS0354.eemea.ericsson.se>
Date: Tue, 30 Mar 2010 13:28:08 -0400
Message-ID: <00b101cad02e$5e1a37d0$1a4ea770$@us>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B2_01CAD00C.D70897D0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNgAAVBprAAEgqT0AAc5mFw
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.66.69.79 authed with richard@shockey.us}
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 30 Mar 2010 17:27:50 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_00B2_01CAD00C.D70897D0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

So ..what your point??  

 

I'm not a great fan of one size fits all or "there can only be one"
solution. Its why you have markets.

 

The Option Tag IMHO is the real key here as you correctly point out the
problem is figuring out what is supported and returning an appropriate
response. That is the issue with both the IMS and SIP Connect 1.0
implementations.

 

From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf
Of Christer Holmberg
Sent: Monday, March 29, 2010 11:41 PM
To: 'Hadriel Kaplan'; bruno.chatras@orange-ftgroup.com;
ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

 

Hi,

 

Having an option-tag is fine, but it will only help for negotiation, and to
figure out what is supported. You are still going to end up having two
different solutions that do not interwork with each other.

 

Regards,

 

Christer

 

  _____  

From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf
Of Hadriel Kaplan
Sent: 29. maaliskuuta 2010 22:16
To: bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com;
john.elwell@siemens-enterprise.com
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

Absolutely - that's one of the advantages of the Martini mechanism having an
options-tag.  If the IP-PBX indicates the option-tag but the REGISTER
response does not (i.e., is rejected with 420), then the IP-PBX would revert
to doing whatever it is it "normally" does.  Unfortunately there was no
explicit indicator of the ETSI nor SIP-Connect 1.0 models, so how the IP-PBX
behaves "normally" is unknown a priori.  

 

And of course the IP-PBX could always be configured to just do ETSI or
SIP-Connect 1.0 models, as has previously been the case; and the nice thing
with Martini is if the SSP only supports Martini then it can indicate the
option-tag is required in its response (by responding to the REGISTER with a
421).

 

-hadriel

 

  _____  

From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf
Of bruno.chatras@orange-ftgroup.com
Sent: Monday, March 29, 2010 12:35 PM
To: ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

 

I fully agree with what Hans Erik has said in the Postscriptum "it would be
really, really, really good if they (the IP PBX) would interwork on the UNI
with the IMS business trunking". I believe that most operators share the
same view... and presumably some vendors as well...

 


------=_NextPart_000_00B2_01CAD00C.D70897D0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:navy;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>So ..what your point??&nbsp; <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I&#8217;m not a great fan of one size fits all or =
&#8220;there
can only be one&#8221; solution. Its why you have =
markets.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The Option Tag IMHO is the real key here as you correctly =
point
out the problem is figuring out what is supported and returning an =
appropriate
response. That is the issue with both the IMS and SIP Connect 1.0 =
implementations.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <b>On Behalf =
Of </b>Christer
Holmberg<br>
<b>Sent:</b> Monday, March 29, 2010 11:41 PM<br>
<b>To:</b> 'Hadriel Kaplan'; bruno.chatras@orange-ftgroup.com;
ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com<br>
<b>Cc:</b> martini@ietf.org<br>
<b>Subject:</b> Re: [martini] #21: 3.2.2 describes an issue with some =
PBX<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Hi,</span><o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Having an option-tag is fine, but it will only help for
negotiation, and to figure out what is supported. You are still going to =
end up
having two different solutions that do not interwork with each =
other.</span><o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Regards,</span><o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Christer</span><o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D3 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><span =
style=3D'font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span =
style=3D'font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> martini-bounces@ietf.org
[mailto:martini-bounces@ietf.org] <b>On Behalf Of </b>Hadriel Kaplan<br>
<b>Sent:</b> 29. maaliskuuta 2010 22:16<br>
<b>To:</b> bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com;
john.elwell@siemens-enterprise.com<br>
<b>Cc:</b> martini@ietf.org<br>
<b>Subject:</b> Re: [martini] #21: 3.2.2 describes an issue with some =
PBX</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Absolutely &#8211; that&#8217;s one of the advantages of the
Martini mechanism having an options-tag. &nbsp;If the IP-PBX indicates =
the
option-tag but the REGISTER response does not (i.e., is rejected with =
420),
then the IP-PBX would revert to doing whatever it is it =
&#8220;normally&#8221;
does.&nbsp; Unfortunately there was no explicit indicator of the ETSI =
nor
SIP-Connect 1.0 models, so how the IP-PBX behaves &#8220;normally&#8221; =
is
unknown a priori.&nbsp; <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>And of course the IP-PBX could always be configured to just =
do ETSI
or SIP-Connect 1.0 models, as has previously been the case; and the nice =
thing
with Martini is if the SSP only supports Martini then it can indicate =
the
option-tag is required in its response (by responding to the REGISTER =
with a
421).<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>-hadriel<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <b>On Behalf =
Of </b>bruno.chatras@orange-ftgroup.com<br>
<b>Sent:</b> Monday, March 29, 2010 12:35 PM<br>
<b>To:</b> ietf.hanserik@gmail.com; =
john.elwell@siemens-enterprise.com<br>
<b>Cc:</b> martini@ietf.org<br>
<b>Subject:</b> Re: [martini] #21: 3.2.2 describes an issue with some =
PBX</span><o:p></o:p></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>I
fully agree with what Hans Erik has said in the =
Postscriptum&nbsp;&quot;it
would be really, really, really good if they (the IP PBX) would =
interwork on
the UNI with the IMS business trunking&quot;.&nbsp;I believe that most
operators share the same view... and presumably some vendors as =
well...</span><o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_00B2_01CAD00C.D70897D0--


From HKaplan@acmepacket.com  Tue Mar 30 11:35:13 2010
Return-Path: <HKaplan@acmepacket.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 C50823A6A75 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 11:35:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.741
X-Spam-Level: 
X-Spam-Status: No, score=0.741 tagged_above=-999 required=5 tests=[AWL=-0.391,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 3o5gPkAzjyGm for <martini@core3.amsl.com>; Tue, 30 Mar 2010 11:35:07 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 8C11C3A659C for <martini@ietf.org>; Tue, 30 Mar 2010 11:35:02 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Tue, 30 Mar 2010 14:35:31 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Tue, 30 Mar 2010 14:35:31 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "bruno.chatras@orange-ftgroup.com" <bruno.chatras@orange-ftgroup.com>, "richard@shockey.us" <richard@shockey.us>, "ietf.hanserik@gmail.com" <ietf.hanserik@gmail.com>, "john.elwell@siemens-enterprise.com" <john.elwell@siemens-enterprise.com>
Date: Tue, 30 Mar 2010 14:35:29 -0400
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNgAAFPnSAAA9iCcAAaSjUQABPeQdAAAE/sIAABZMwA
Message-ID: <430FC6BDED356B4C8498F634416644A91A79E92B2D@mail>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net><g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com><9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr> <011a01cacf62$55509710$fff1c530$@us> <430FC6BDED356B4C8498F634416644A91A79E928E3@mail> <9ECCF01B52E7AB408A7EB853526421410146361C@ftrdmel0.rd.francetelecom.fr> <430FC6BDED356B4C8498F634416644A91A79E92ADB@mail> <9ECCF01B52E7AB408A7EB853526421410148E713@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <9ECCF01B52E7AB408A7EB853526421410148E713@ftrdmel0.rd.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_430FC6BDED356B4C8498F634416644A91A79E92B2Dmail_"
MIME-Version: 1.0
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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, 30 Mar 2010 18:35:13 -0000

--_000_430FC6BDED356B4C8498F634416644A91A79E92B2Dmail_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


________________________________
From: bruno.chatras@orange-ftgroup.com [mailto:bruno.chatras@orange-ftgroup=
.com]
Sent: Tuesday, March 30, 2010 1:16 PM
To: Hadriel Kaplan; richard@shockey.us; ietf.hanserik@gmail.com; john.elwel=
l@siemens-enterprise.com
Cc: martini@ietf.org
Subject: RE: [martini] #21: 3.2.2 describes an issue with some PBX

OK. If loose-route was implemented in some of these IMS networks (I guess I=
 know at least one of them) and you had to modify the R-URI on a per-trunk =
basis, it just means that some of the IP-PBXs connected to them were not IM=
S-compliant. Quite predictable as this loose-route mechanism is relatively =
new and therefore not yet available on all systems. Similarly, if a network=
 implements the GIN solution, you will have to modify the R-URI on per-trun=
k basis because some of the IP-PBXs will be loose-route compliant and will =
therefore not be GIN-compliant. Where is the improvement compared to the cu=
rrent situation?

Because then for the GIN-compliant devices you know they're GIN compliant f=
rom their signaling.  There is no per-trunk guessing/config for the GIN-com=
pliant case.  It's true that some operators will have legacy IP-PBX's, but =
now they'll know which ones are not legacy anymore - right now they don't. =
 They don't know when an IP-PBX gets upgraded to support IMS, and they don'=
t know whether it is IMS to begin with.

The current situation isn't that bad, when dealing with medium-to-large Ent=
erprise trunks.  Provisioning is fine for that.  But in SIP-Connect 1.1 we =
were faced with trying to handle/support the large-volume small-business tr=
unk case, and for that we're trying to keep provisioning as low as possible=
, in as few systems as possible.  And we needed the tools to help find mism=
atches.  Hence the option-tag.

Personally I was hoping to just take IMS/ETSI and add the option-tag and mi=
nor tweaks - that was the "shaken" draft in essence, but the WG was split a=
nd we needed to move forward.  And GIN really isn't that much different eit=
her - is there something you'd like to see in GIN to make it more like the =
ETSI/IMS mechanism?

-hadriel
p.s. Actually my guess is that even if all sides think they're IMS complian=
t, that we'd have to re-write the req-uri on a case-by-case basis.  Because=
 it's not clear what it should be.  Is the domain-portion the PBX gets supp=
osed to be "ssp.com", or "pbx.com"?  Is it either/both?  Could it be "ims.s=
sp.com", or even "s-cscf.ssp.com"?  Because those last two type/forms of ho=
st/domain names appear in the request-uri of requests received at the S-CSC=
F all the time in some IMS networks, so if IMS "loose-route" literally mean=
s "do-not-touch-the-request-uri", it will be fraught with issues.


--_000_430FC6BDED356B4C8498F634416644A91A79E92B2Dmail_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40"
xmlns:ns6=3D"http://schemas.microsoft.com/office/2004/12/omml">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"place"=
/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
	{mso-style-priority: 99
;}
span.MSOHYPERLINK
	{mso-style-priority: 99
;}
a:visited
	{mso-style-priority: 99
;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority: 99
;}

 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Calibri;
	color:#1F497D;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
bruno.chatras@orange-ftgroup.com [mailto:bruno.chatras@orange-ftgroup.com] =
<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, March 30, 201=
0 1:16
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName w:st=3D"=
on">Hadriel
 Kaplan</st1:PersonName>; richard@shockey.us; ietf.hanserik@gmail.com;
john.elwell@siemens-enterprise.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName w:st=3D"=
on">martini@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [martini] #21: =
3.2.2
describes an issue with some PBX</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>OK. If loose-route was implemented in =
some
of these IMS networks (I guess I know at least one of them) and you had to
modify the R-URI on a per-trunk basis, it just&nbsp;means that some of the
IP-PBXs connected to them were not IMS-compliant. Quite predictable as this
loose-route mechanism is relatively new and therefore not yet available on =
all
systems. Similarly, if a network implements the GIN solution, you will have=
 to
modify the R-URI on per-trunk basis because some of the IP-PBXs will be
loose-route compliant and will therefore not be GIN-compliant. Where is the
improvement compared to the current situation?</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New Roman"><=
span
style=3D'font-size:12.0pt;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Because then for the GIN-compliant dev=
ices
you know they&#8217;re GIN compliant from their signaling.&nbsp; There is n=
o
per-trunk guessing/config for the GIN-compliant case. &nbsp;It&#8217;s true
that some operators will have legacy IP-PBX&#8217;s, but now they&#8217;ll =
know
which ones are <i><span style=3D'font-style:italic'>not</span></i> legacy a=
nymore
&#8211; right now they don&#8217;t.&nbsp; They don&#8217;t know when an IP-=
PBX
gets upgraded to support IMS, and they don&#8217;t know whether it is IMS t=
o
begin with.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>The current situation isn&#8217;t that
bad, when dealing with medium-to-large <st1:City w:st=3D"on"><st1:place w:s=
t=3D"on">Enterprise</st1:place></st1:City>
trunks.&nbsp; Provisioning is fine for that.&nbsp; But in SIP-Connect 1.1 w=
e
were faced with trying to handle/support the large-volume small-business tr=
unk case,
and for that we&#8217;re trying to keep provisioning as low as possible, in=
 as few
systems as possible.&nbsp; And we needed the tools to help find
mismatches.&nbsp; Hence the option-tag.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Personally I was hoping to just take I=
MS/ETSI
and add the option-tag and minor tweaks &#8211; that was the &#8220;shaken&=
#8221;
draft in essence, but the WG was split and we needed to move forward. &nbsp=
;And
GIN really isn&#8217;t that much different either &#8211; is there somethin=
g
you&#8217;d like to see in GIN to make it more like the ETSI/IMS mechanism?=
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>-hadriel<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>p.s. Actually my guess is that even if=
 all
sides think they&#8217;re IMS compliant, that we&#8217;d have to re-write t=
he
req-uri on a case-by-case basis.&nbsp; Because it&#8217;s not clear what it
should be.&nbsp; Is the domain-portion the PBX gets supposed to be &#8220;s=
sp.com&#8221;,
or &#8220;pbx.com&#8221;?&nbsp; Is it either/both?&nbsp; Could it be &#8220=
;ims.ssp.com&#8221;,
or even &#8220;s-cscf.ssp.com&#8221;?&nbsp; Because those last two type/for=
ms
of host/domain names appear in the request-uri of requests received at the
S-CSCF all the time in some IMS networks, so if IMS &#8220;loose-route&#822=
1;
literally means &#8220;do-not-touch-the-request-uri&#8221;, it will be frau=
ght
with issues.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>

</body>

</html>

--_000_430FC6BDED356B4C8498F634416644A91A79E92B2Dmail_--

From root@core3.amsl.com  Tue Mar 30 15:15:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: martini@ietf.org
Delivered-To: martini@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id BA4B93A69A6; Tue, 30 Mar 2010 15:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100330221501.BA4B93A69A6@core3.amsl.com>
Date: Tue, 30 Mar 2010 15:15:01 -0700 (PDT)
Cc: martini@ietf.org
Subject: [martini] I-D Action:draft-ietf-martini-gin-00.txt
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, 30 Mar 2010 22:15:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiple AoR reachabiliTy InformatioN Indication Working Group of the IETF.


	Title           : Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)
	Author(s)       : A. Roach
	Filename        : draft-ietf-martini-gin-00.txt
	Pages           : 21
	Date            : 2010-03-30

This document defines a mechanism by which a SIP server acting as a
traditional Private Branch Exchange (PBX) can register with a SIP
Service Provider (SSP) to receive phone calls for extensions
designated by phone numbers.  In order to function properly, this
mechanism relies on the fact that the phone numbers are fully
qualified and globally unique.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-martini-gin-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-martini-gin-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-03-30150038.I-D@ietf.org>


--NextPart--

From trac@tools.ietf.org  Tue Mar 30 15:36:09 2010
Return-Path: <trac@tools.ietf.org>
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 E51C13A6BE6 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 15:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.038
X-Spam-Level: 
X-Spam-Status: No, score=-100.038 tagged_above=-999 required=5 tests=[AWL=-0.427, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 lxKe9J6vqQjp for <martini@core3.amsl.com>; Tue, 30 Mar 2010 15:36:09 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 55D083A6A5C for <martini@ietf.org>; Tue, 30 Mar 2010 15:36:09 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nwk35-0002FT-Hv; Tue, 30 Mar 2010 15:36:39 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com
X-Trac-Project: martini
Date: Tue, 30 Mar 2010 22:36:39 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/9#comment:1
Message-ID: <076.c63624ffbd1e05e348cf7233a2f96506@tools.ietf.org>
References: <067.b617480425ee58bf2cf3e04cd7c88604@tools.ietf.org>
X-Trac-Ticket-ID: 9
In-Reply-To: <067.b617480425ee58bf2cf3e04cd7c88604@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #9: IANA considerations
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 30 Mar 2010 22:36:10 -0000

#9: IANA considerations
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:  adam@…          
     Type:  defect                     |       Status:  closed          
 Priority:  major                      |    Milestone:  milestone1      
Component:  gin                        |      Version:  1.0             
 Severity:  Candidate WG Document      |   Resolution:  fixed           
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by adam@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Fixed in draft-roach-martini-gin-01

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/9#comment:1>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Tue Mar 30 15:37:34 2010
Return-Path: <trac@tools.ietf.org>
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 B2AD03A6BE6 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 15:37:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.745
X-Spam-Level: 
X-Spam-Status: No, score=-99.745 tagged_above=-999 required=5 tests=[AWL=-0.689, BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 eAvD-kbtUebu for <martini@core3.amsl.com>; Tue, 30 Mar 2010 15:37:33 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id BDA6D3A6BD2 for <martini@ietf.org>; Tue, 30 Mar 2010 15:37:33 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nwk4S-0002GP-2k; Tue, 30 Mar 2010 15:38:04 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com
X-Trac-Project: martini
Date: Tue, 30 Mar 2010 22:38:04 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/10#comment:1
Message-ID: <076.2836c49370da2a41a48232d3f3e7084e@tools.ietf.org>
References: <067.2a49b7034245fef91ad2ddf7b60f2826@tools.ietf.org>
X-Trac-Ticket-ID: 10
In-Reply-To: <067.2a49b7034245fef91ad2ddf7b60f2826@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #10: Section 9: Issues Solved
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 30 Mar 2010 22:37:34 -0000

#10: Section 9: Issues Solved
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:  adam@…          
     Type:  defect                     |       Status:  closed          
 Priority:  major                      |    Milestone:  milestone1      
Component:  gin                        |      Version:  1.0             
 Severity:  Candidate WG Document      |   Resolution:  fixed           
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by adam@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Fixed in draft-roach-martini-gin-01

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/10#comment:1>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Tue Mar 30 15:38:29 2010
Return-Path: <trac@tools.ietf.org>
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 77CFE3A6AC0 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 15:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.184
X-Spam-Level: 
X-Spam-Status: No, score=-100.184 tagged_above=-999 required=5 tests=[AWL=-0.203, BAYES_05=-1.11, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 27AMcHVY7Qq1 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 15:38:28 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id DE7B13A6BD0 for <martini@ietf.org>; Tue, 30 Mar 2010 15:38:27 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nwk5K-0002Gi-6t; Tue, 30 Mar 2010 15:38:58 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com
X-Trac-Project: martini
Date: Tue, 30 Mar 2010 22:38:58 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/8#comment:1
Message-ID: <076.906367b1a662959df9ddfe070db82445@tools.ietf.org>
References: <067.b839f4a9e00d234c0d2b7572017d3dc0@tools.ietf.org>
X-Trac-Ticket-ID: 8
In-Reply-To: <067.b839f4a9e00d234c0d2b7572017d3dc0@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #8: GIN editorial issues
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 30 Mar 2010 22:38:29 -0000

#8: GIN editorial issues
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:  adam@…          
     Type:  defect                     |       Status:  closed          
 Priority:  trivial                    |    Milestone:  milestone1      
Component:  gin                        |      Version:  1.0             
 Severity:  Candidate WG Document      |   Resolution:  fixed           
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by adam@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 All comments accepted. Fixed in draft-roach-martini-gin-01

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/8#comment:1>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Tue Mar 30 15:39:24 2010
Return-Path: <trac@tools.ietf.org>
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 304EB3A6BD0 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 15:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.992
X-Spam-Level: 
X-Spam-Status: No, score=-99.992 tagged_above=-999 required=5 tests=[AWL=-0.381, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 tnIpdGcvEhkt for <martini@core3.amsl.com>; Tue, 30 Mar 2010 15:39:23 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 8EC563A6AA8 for <martini@ietf.org>; Tue, 30 Mar 2010 15:39:23 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nwk6D-0002Hi-TB; Tue, 30 Mar 2010 15:39:53 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com
X-Trac-Project: martini
Date: Tue, 30 Mar 2010 22:39:53 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/12#comment:1
Message-ID: <076.d18184247850c179da0a3db474959ec6@tools.ietf.org>
References: <067.324dd7e58954de0f0f6b28cbec329648@tools.ietf.org>
X-Trac-Ticket-ID: 12
In-Reply-To: <067.324dd7e58954de0f0f6b28cbec329648@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #12: Section 7.4:  Path
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 30 Mar 2010 22:39:24 -0000

#12: Section 7.4:  Path
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:  adam@…          
     Type:  defect                     |       Status:  closed          
 Priority:  major                      |    Milestone:  milestone1      
Component:  gin                        |      Version:  1.0             
 Severity:  Candidate WG Document      |   Resolution:  fixed           
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by adam@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Fixed in draft-ietf-martini-gin-00

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/12#comment:1>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Tue Mar 30 15:39:55 2010
Return-Path: <trac@tools.ietf.org>
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 CDF343A6BE6 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 15:39:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.98
X-Spam-Level: 
X-Spam-Status: No, score=-99.98 tagged_above=-999 required=5 tests=[AWL=-0.369, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 TGZC1xE2YaPI for <martini@core3.amsl.com>; Tue, 30 Mar 2010 15:39:55 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id B06B43A6BE9 for <martini@ietf.org>; Tue, 30 Mar 2010 15:39:54 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nwk6j-0002Kw-1K; Tue, 30 Mar 2010 15:40:25 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com
X-Trac-Project: martini
Date: Tue, 30 Mar 2010 22:40:25 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/13#comment:1
Message-ID: <076.206b18fff217de91933ba1563d4b4d58@tools.ietf.org>
References: <067.2daab1a0eeaadd6fa805c57ed66f0b7e@tools.ietf.org>
X-Trac-Ticket-ID: 13
In-Reply-To: <067.2daab1a0eeaadd6fa805c57ed66f0b7e@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #13: Section 7.5:  Service Route
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 30 Mar 2010 22:39:55 -0000

#13: Section 7.5:  Service Route
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:  adam@…          
     Type:  defect                     |       Status:  closed          
 Priority:  major                      |    Milestone:  milestone1      
Component:  gin                        |      Version:  1.0             
 Severity:  Candidate WG Document      |   Resolution:  fixed           
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by adam@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Fixed in draft-ietf-martini-gin-00

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/13#comment:1>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Tue Mar 30 15:42:01 2010
Return-Path: <trac@tools.ietf.org>
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 B257A3A6BF7 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 15:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.898
X-Spam-Level: 
X-Spam-Status: No, score=-100.898 tagged_above=-999 required=5 tests=[AWL=0.572, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 LSXbA8P+G6-R for <martini@core3.amsl.com>; Tue, 30 Mar 2010 15:42:01 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 00A0B3A6B07 for <martini@ietf.org>; Tue, 30 Mar 2010 15:42:01 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1Nwk8l-0002PD-9k; Tue, 30 Mar 2010 15:42:31 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com
X-Trac-Project: martini
Date: Tue, 30 Mar 2010 22:42:31 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/24
Message-ID: <058.de3f68c3042d5b4ea78b5da154dfecd3@tools.ietf.org>
X-Trac-Ticket-ID: 24
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini]  #24: Security Considerations
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 30 Mar 2010 22:42:01 -0000

#24: Security Considerations
--------------------------------+-------------------------------------------
 Reporter:  adam@…              |       Owner:  adam@…          
     Type:  defect              |      Status:  new             
 Priority:  major               |   Milestone:                  
Component:  gin                 |     Version:                  
 Severity:  Active WG Document  |    Keywords:                  
--------------------------------+-------------------------------------------
 The document needs to include a section that talks about the security
 implications of re-purposing REGISTER to apply to more than one AOR.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/24>
martini <http://tools.ietf.org/martini/>


From trac@tools.ietf.org  Tue Mar 30 15:47:42 2010
Return-Path: <trac@tools.ietf.org>
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 E4FBC3A6951 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 15:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.171
X-Spam-Level: 
X-Spam-Status: No, score=-100.171 tagged_above=-999 required=5 tests=[AWL=-0.190, BAYES_05=-1.11, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 c3K1z27cAwnb for <martini@core3.amsl.com>; Tue, 30 Mar 2010 15:47:42 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 55EFD3A6917 for <martini@ietf.org>; Tue, 30 Mar 2010 15:47:42 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NwkEG-0003cA-Kr; Tue, 30 Mar 2010 15:48:12 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: adam@nostrum.com
X-Trac-Project: martini
Date: Tue, 30 Mar 2010 22:48:12 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/7#comment:1
Message-ID: <076.0e36bcd7a6c7ae781602a81586e6b577@tools.ietf.org>
References: <067.5ec62977838b8c119ef7c4f9e3e654c6@tools.ietf.org>
X-Trac-Ticket-ID: 7
In-Reply-To: <067.5ec62977838b8c119ef7c4f9e3e654c6@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #7: GIN idnits
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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, 30 Mar 2010 22:47:43 -0000

#7: GIN idnits
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  adam@…          
     Type:  defect                     |      Status:  assigned        
 Priority:  minor                      |   Milestone:  milestone1      
Component:  gin                        |     Version:  1.0             
 Severity:  Candidate WG Document      |    Keywords:                  
---------------------------------------+------------------------------------
Changes (by adam@…):

  * status:  new => assigned


Comment:

 These issues have been addressed, except for the security issue (which has
 been moved into its own issue) and the boilerplate issue (which will be
 resolved when the xml2rfc tools are updated). I'm leaving this open to
 remind me of the tools/boilerplate issue.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/7#comment:1>
martini <http://tools.ietf.org/martini/>


From christer.holmberg@ericsson.com  Tue Mar 30 22:50:16 2010
Return-Path: <christer.holmberg@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 613883A6958 for <martini@core3.amsl.com>; Tue, 30 Mar 2010 22:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.987
X-Spam-Level: 
X-Spam-Status: No, score=-3.987 tagged_above=-999 required=5 tests=[AWL=1.482,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 KYHJ9oBZ1-0w for <martini@core3.amsl.com>; Tue, 30 Mar 2010 22:50:15 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 79B293A69C7 for <martini@ietf.org>; Tue, 30 Mar 2010 22:50:10 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bf6ae000005bec-6a-4bb2e2aed9d9
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 34.6C.23532.EA2E2BB4; Wed, 31 Mar 2010 07:50:39 +0200 (CEST)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.2.223]) by esessmw0247.eemea.ericsson.se ([10.2.3.116]) with mapi; Wed, 31 Mar 2010 07:50:38 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: 'Richard Shockey' <richard@shockey.us>, 'Hadriel Kaplan' <HKaplan@acmepacket.com>, "bruno.chatras@orange-ftgroup.com" <bruno.chatras@orange-ftgroup.com>, "ietf.hanserik@gmail.com" <ietf.hanserik@gmail.com>, "john.elwell@siemens-enterprise.com" <john.elwell@siemens-enterprise.com>
Date: Wed, 31 Mar 2010 07:50:37 +0200
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNgAAVBprAAEgqT0AAc5mFwABRadzA=
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC745E21BEF4E4@ESESSCMS0354.eemea.ericsson.se>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com> <9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr> <430FC6BDED356B4C8498F634416644A91A79E928EE@mail> <FF84A09F50A6DC48ACB6714F4666CC745E21B5A8EC@ESESSCMS0354.eemea.ericsson.se> <00b101cad02e$5e1a37d0$1a4ea770$@us>
In-Reply-To: <00b101cad02e$5e1a37d0$1a4ea770$@us>
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==
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 05:50:16 -0000

Hi,=20

>So ..what your point?? =20
>
>I'm not a great fan of one size fits all or "there can only be one" soluti=
on. Its why you have markets.

That is true, if you have fundamentally different requirements, use-cases e=
tc.=20

But, is that really the case here? The only thing I've heard is that "the I=
MS solution cannot be made to work", and that we therefor need a different =
solution.

And, if people are ok with two solutions, why was there a suggestion to sen=
d an LS to 3GPP and ask them to adopt the IETF solution?

Regards,

Christer


=20

From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Christer Holmberg
Sent: Monday, March 29, 2010 11:41 PM
To: 'Hadriel Kaplan'; bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail=
.com; john.elwell@siemens-enterprise.com
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

=20

Hi,

=20

Having an option-tag is fine, but it will only help for negotiation, and to=
 figure out what is supported. You are still going to end up having two dif=
ferent solutions that do not interwork with each other.

=20

Regards,

=20

Christer

=20

________________________________

From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Hadriel Kaplan
Sent: 29. maaliskuuta 2010 22:16
To: bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com; john.elwell@=
siemens-enterprise.com
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

Absolutely - that's one of the advantages of the Martini mechanism having a=
n options-tag.  If the IP-PBX indicates the option-tag but the REGISTER res=
ponse does not (i.e., is rejected with 420), then the IP-PBX would revert t=
o doing whatever it is it "normally" does.  Unfortunately there was no expl=
icit indicator of the ETSI nor SIP-Connect 1.0 models, so how the IP-PBX be=
haves "normally" is unknown a priori. =20

=20

And of course the IP-PBX could always be configured to just do ETSI or SIP-=
Connect 1.0 models, as has previously been the case; and the nice thing wit=
h Martini is if the SSP only supports Martini then it can indicate the opti=
on-tag is required in its response (by responding to the REGISTER with a 42=
1).

=20

-hadriel

=20

________________________________

From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of bruno.chatras@orange-ftgroup.com
Sent: Monday, March 29, 2010 12:35 PM
To: ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

=20

I fully agree with what Hans Erik has said in the Postscriptum "it would be=
 really, really, really good if they (the IP PBX) would interwork on the UN=
I with the IMS business trunking". I believe that most operators share the =
same view... and presumably some vendors as well...

=20


From bruno.chatras@orange-ftgroup.com  Wed Mar 31 00:26:47 2010
Return-Path: <bruno.chatras@orange-ftgroup.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 A25113A699F for <martini@core3.amsl.com>; Wed, 31 Mar 2010 00:26:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.389
X-Spam-Level: *
X-Spam-Status: No, score=1.389 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
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 ma0hntQnrIJH for <martini@core3.amsl.com>; Wed, 31 Mar 2010 00:26:45 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by core3.amsl.com (Postfix) with ESMTP id 011F63A6A0A for <martini@ietf.org>; Wed, 31 Mar 2010 00:26:45 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 11991A005F5; Wed, 31 Mar 2010 09:26:30 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail2.rd.francetelecom.com (Postfix) with ESMTP id 01C1CA005FE; Wed, 31 Mar 2010 09:26:29 +0200 (CEST)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 31 Mar 2010 09:26:13 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAD0A3.713D1DFB"
Date: Wed, 31 Mar 2010 09:26:13 +0200
Message-ID: <9ECCF01B52E7AB408A7EB853526421410148E7EA@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79E92B2D@mail>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNgAAFPnSAAA9iCcAAaSjUQABPeQdAAAE/sIAABZMwAABvYUrA=
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net><g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com><9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr> <011a01cacf62$55509710$fff1c530$@us> <430FC6BDED356B4C8498F634416644A91A79E928E3@mail> <9ECCF01B52E7AB408A7EB853526421410146361C@ftrdmel0.rd.francetelecom.fr> <430FC6BDED356B4C8498F634416644A91A79E92ADB@mail> <9ECCF01B52E7AB408A7EB853526421410148E713@ftrdmel0.rd.francetelecom.fr> <430FC6BDED356B4C8498F634416644A91A79E92B2D@mail>
From: <bruno.chatras@orange-ftgroup.com>
To: <HKaplan@acmepacket.com>, <richard@shockey.us>, <ietf.hanserik@gmail.com>, <john.elwell@siemens-enterprise.com>
X-OriginalArrivalTime: 31 Mar 2010 07:26:13.0996 (UTC) FILETIME=[71BD52C0:01CAD0A3]
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 07:26:47 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CAD0A3.713D1DFB
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

=20


________________________________

	De : Hadriel Kaplan [mailto:HKaplan@acmepacket.com]=20
	Envoy=E9 : mardi 30 mars 2010 20:35
	=C0 : CHATRAS Bruno RD-CORE-ISS; richard@shockey.us; =
ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com
	Cc : martini@ietf.org
	Objet : RE: [martini] #21: 3.2.2 describes an issue with some PBX
=09
=09

	=20

=09
________________________________


	From: bruno.chatras@orange-ftgroup.com =
[mailto:bruno.chatras@orange-ftgroup.com]=20
	Sent: Tuesday, March 30, 2010 1:16 PM
	To: Hadriel Kaplan; richard@shockey.us; ietf.hanserik@gmail.com; =
john.elwell@siemens-enterprise.com
	Cc: martini@ietf.org
	Subject: RE: [martini] #21: 3.2.2 describes an issue with some PBX

	=20

	OK. If loose-route was implemented in some of these IMS networks (I =
guess I know at least one of them) and you had to modify the R-URI on a =
per-trunk basis, it just means that some of the IP-PBXs connected to =
them were not IMS-compliant. Quite predictable as this loose-route =
mechanism is relatively new and therefore not yet available on all =
systems. Similarly, if a network implements the GIN solution, you will =
have to modify the R-URI on per-trunk basis because some of the IP-PBXs =
will be loose-route compliant and will therefore not be GIN-compliant. =
Where is the improvement compared to the current situation?

	=20

	Because then for the GIN-compliant devices you know they're GIN =
compliant from their signaling.  There is no per-trunk guessing/config =
for the GIN-compliant case.  It's true that some operators will have =
legacy IP-PBX's, but now they'll know which ones are not legacy anymore =
- right now they don't.  They don't know when an IP-PBX gets upgraded to =
support IMS, and they don't know whether it is IMS to begin with. =20

	=20

	The current situation isn't that bad, when dealing with medium-to-large =
Enterprise trunks.  Provisioning is fine for that.  But in SIP-Connect =
1.1 we were faced with trying to handle/support the large-volume =
small-business trunk case, and for that we're trying to keep =
provisioning as low as possible, in as few systems as possible.  And we =
needed the tools to help find mismatches.  Hence the option-tag.
=09

	=20

	Personally I was hoping to just take IMS/ETSI and add the option-tag =
and minor tweaks - that was the "shaken" draft in essence
	[=3D=3D>BC:] Yes I remember that and would have preferred going down =
this route.

	 , but the WG was split and we needed to move forward.  And GIN really =
isn't that much different either - is there something you'd like to see =
in GIN to make it more like the ETSI/IMS mechanism?
	[=3D=3D>BC:] Of course. I would like the R-URI to contain the initial =
target identity rather than this special contact address.=20

	=20

	-hadriel

	p.s. Actually my guess is that even if all sides think they're IMS =
compliant, that we'd have to re-write the req-uri on a case-by-case =
basis.  Because it's not clear what it should be.  Is the domain-portion =
the PBX gets supposed to be "ssp.com", or "pbx.com"?  Is it either/both? =
 Could it be "ims.ssp.com", or even "s-cscf.ssp.com"? =20
	[=3D=3D>BC:] The domain portion can be "xxx.ssp.com" or =
"xxx.entreprise.com" with the understanding that the DNS maps =
"xxx.entreprise.com" to the SSP's network entry point.

	=20

	 Because those last two type/forms of host/domain names appear in the =
request-uri of requests received at the S-CSCF all the time in some IMS =
networks, so if IMS "loose-route" literally means =
"do-not-touch-the-request-uri", it will be fraught with issues.

	=20


------_=_NextPart_001_01CAD0A3.713D1DFB
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags" xmlns:ns6 =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"place"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><o:SmartTagType=20
name=3D"City"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><o:SmartTagType=20
name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: MS Mincho;
}
@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: @MS Mincho;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
A:link {
	mso-style-priority: 99
}
SPAN.MSOHYPERLINK {
	mso-style-priority: 99
}
A:visited {
	mso-style-priority: 99
}
SPAN.MSOHYPERLINKFOLLOWED {
	mso-style-priority: 99
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: #1f497d; FONT-FAMILY: Calibri; mso-style-type: personal
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle19 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle20 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Dfr dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>De&nbsp;:</B> Hadriel Kaplan=20
  [mailto:HKaplan@acmepacket.com] <BR><B>Envoy=E9&nbsp;:</B> mardi 30 =
mars 2010=20
  20:35<BR><B>=C0&nbsp;:</B> CHATRAS Bruno RD-CORE-ISS; =
richard@shockey.us;=20
  ietf.hanserik@gmail.com;=20
  john.elwell@siemens-enterprise.com<BR><B>Cc&nbsp;:</B>=20
  martini@ietf.org<BR><B>Objet&nbsp;:</B> RE: [martini] #21: 3.2.2 =
describes an=20
  issue with some PBX<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <DIV>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
  bruno.chatras@orange-ftgroup.com =
[mailto:bruno.chatras@orange-ftgroup.com]=20
  <BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, =
March 30,=20
  2010 1:16 PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
  <st1:PersonName w:st=3D"on">Hadriel Kaplan</st1:PersonName>; =
richard@shockey.us;=20
  ietf.hanserik@gmail.com; =
john.elwell@siemens-enterprise.com<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> <st1:PersonName=20
  w:st=3D"on">martini@ietf.org</st1:PersonName><BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [martini] #21: =
3.2.2=20
  describes an issue with some PBX</SPAN></FONT><o:p></o:p></P></DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">OK. If =
loose-route=20
  was implemented in some of these IMS networks (I guess I know at least =
one of=20
  them) and you had to modify the R-URI on a per-trunk basis, it =
just&nbsp;means=20
  that some of the IP-PBXs connected to them were not IMS-compliant. =
Quite=20
  predictable as this loose-route mechanism is relatively new and =
therefore not=20
  yet available on all systems. Similarly, if a network implements the =
GIN=20
  solution, you will have to modify the R-URI on per-trunk basis because =
some of=20
  the IP-PBXs will be loose-route compliant and will therefore not be=20
  GIN-compliant. Where is the improvement compared to the current=20
  situation?</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: =
navy"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Because =
then for the=20
  GIN-compliant devices you know they=92re GIN compliant from their=20
  signaling.&nbsp; There is no per-trunk guessing/config for the =
GIN-compliant=20
  case. &nbsp;It=92s true that some operators will have legacy =
IP-PBX=92s, but now=20
  they=92ll know which ones are <I><SPAN style=3D"FONT-STYLE: =
italic">not</SPAN></I>=20
  legacy anymore =96 right now they don=92t.&nbsp; They don=92t know =
when an IP-PBX=20
  gets upgraded to support IMS, and they don=92t know whether it is IMS =
to begin=20
  with.&nbsp; <o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dnavy><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">The current =
situation=20
  isn=92t that bad, when dealing with medium-to-large <st1:City=20
  w:st=3D"on"><st1:place w:st=3D"on">Enterprise</st1:place></st1:City> =
trunks.&nbsp;=20
  Provisioning is fine for that.&nbsp; But in SIP-Connect 1.1 we were =
faced with=20
  trying to handle/support the large-volume small-business trunk case, =
and for=20
  that we=92re trying to keep provisioning as low as possible, in as few =
systems=20
  as possible.&nbsp; And we needed the tools to help find =
mismatches.&nbsp;=20
  Hence the option-tag.<BR></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dnavy><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Personally =
I was=20
  hoping to just take IMS/ETSI and add the option-tag and minor tweaks =
=96 that=20
  was the =93shaken=94 draft in essence<BR><SPAN =
class=3D551010507-31032010><FONT=20
  color=3D#0000ff>[=3D=3D&gt;BC:]&nbsp;Yes I remember that and would =
have preferred=20
  going down this route.</FONT></SPAN></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dnavy><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
  class=3D551010507-31032010>&nbsp;</SPAN>, but the WG was split and we =
needed to=20
  move forward. &nbsp;And GIN really isn=92t that much different either =
=96 is there=20
  something you=92d like to see in GIN to make it more like the ETSI/IMS =

  mechanism?<BR><FONT color=3D#0000ff><SPAN=20
  class=3D551010507-31032010>[=3D=3D&gt;BC:]&nbsp;Of course. I would =
like the R-URI to=20
  contain the initial target identity rather than this special contact=20
  address.&nbsp;</SPAN><o:p></o:p></FONT></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">-hadriel<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dnavy><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">p.s. =
Actually my=20
  guess is that even if all sides think they=92re IMS compliant, that =
we=92d have to=20
  re-write the req-uri on a case-by-case basis.&nbsp; Because it=92s not =
clear=20
  what it should be.&nbsp; Is the domain-portion the PBX gets supposed =
to be=20
  =93ssp.com=94, or =93pbx.com=94?&nbsp; Is it either/both?&nbsp; Could =
it be=20
  =93ims.ssp.com=94, or even =93s-cscf.ssp.com=94?&nbsp; <BR><SPAN=20
  class=3D551010507-31032010><FONT =
color=3D#0000ff>[=3D=3D&gt;BC:]&nbsp;The domain=20
  portion can be "xxx.ssp.com" or "xxx.entreprise.com" with the =
understanding=20
  that the DNS maps "xxx.entreprise.com" to the SSP's network entry=20
  point.</FONT></SPAN></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3D#0000ff><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
  class=3D551010507-31032010></SPAN></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT color=3Dnavy><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
  class=3D551010507-31032010>&nbsp;</SPAN>Because those last two =
type/forms of=20
  host/domain names appear in the request-uri of requests received at =
the S-CSCF=20
  all the time in some IMS networks, so if IMS =93loose-route=94 =
literally means=20
  =93do-not-touch-the-request-uri=94, it will be fraught with=20
  issues.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV></DIV></BLOCKQUOTE></BODY=
></HTML>

------_=_NextPart_001_01CAD0A3.713D1DFB--

From ietf.hanserik@gmail.com  Wed Mar 31 02:34:41 2010
Return-Path: <ietf.hanserik@gmail.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 CCB683A6974 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 02:34:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.85
X-Spam-Level: 
X-Spam-Status: No, score=0.85 tagged_above=-999 required=5 tests=[AWL=-0.282,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 8yfit2-i8x5y for <martini@core3.amsl.com>; Wed, 31 Mar 2010 02:34:39 -0700 (PDT)
Received: from mail-ew0-f224.google.com (mail-ew0-f224.google.com [209.85.219.224]) by core3.amsl.com (Postfix) with ESMTP id 217303A6452 for <martini@ietf.org>; Wed, 31 Mar 2010 02:34:38 -0700 (PDT)
Received: by ewy24 with SMTP id 24so1888968ewy.13 for <martini@ietf.org>; Wed, 31 Mar 2010 02:35:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:received:message-id :subject:from:to:cc:content-type; bh=3HQy4J8ikTSObIVRkFaD6vIj2KTbbPbsJ1zVDwGEDzE=; b=GRNw1A8HQrd4y0ECxGzXNHnH9e3fckOyd/CpNrGssJ/LQikc8FtGEyPbx0gOlAACPZ EmmywYi+RgEvF4E1L+owINPT/pwwiQl3V/IN+0S4yQDMljvxsO+qKKf7ww1Qjuiu1dIX KnNdxn8Qbui2UeqDj1ZyiNoGOrr4FZ9LdZ8qQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=msrVtUe3XiitDnyDLqx7GaNfVl8Jp6EbAfUUlYfmItVa39IgYu03WGONexIJ8NH39z lB/wePojj1NUIe835STpsYNL1vly5w3SseDT4uDfp1Ija/P3vdBYgNMojUraaOcWNxHW +oygtZ+ywY1RAs4bAfxDdxLOEEMirnuxfjkg0=
MIME-Version: 1.0
Received: by 10.213.15.138 with HTTP; Wed, 31 Mar 2010 02:35:05 -0700 (PDT)
Date: Wed, 31 Mar 2010 11:35:05 +0200
Received: by 10.213.65.204 with SMTP id k12mr2115396ebi.15.1270028105602; Wed,  31 Mar 2010 02:35:05 -0700 (PDT)
Message-ID: <p2i9ae56b1e1003310235hbbecb059r8b9b84bd91cad1f@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: bruno.chatras@orange-ftgroup.com
Content-Type: multipart/alternative; boundary=00c09f8c1c7916db170483157655
Cc: martini@ietf.org, HKaplan@acmepacket.com
Subject: [martini] Issue with existing SIP trunking solutions, was Re:  #21: 	3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 09:34:41 -0000

--00c09f8c1c7916db170483157655
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Hadriel,

(Changed the thread name.)

Is your point that the use of a loose-route to the PBX as such is not so
much of a problem, but that SSP's would use it to deliver Request-URI's
containing the SSP's domain to the IP-PBX?

BR,
/Hans Erik van Elburg

On Wed, Mar 31, 2010 at 9:26 AM, <bruno.chatras@orange-ftgroup.com> wrote:

>
>
>  ------------------------------
> *De :* Hadriel Kaplan [mailto:HKaplan@acmepacket.com]
> *Envoy=E9 :* mardi 30 mars 2010 20:35
> *=C0 :* CHATRAS Bruno RD-CORE-ISS; richard@shockey.us;
> ietf.hanserik@gmail.com; john.elwell@siemens-enterprise.com
> *Cc :* martini@ietf.org
> *Objet :* RE: [martini] #21: 3.2.2 describes an issue with some PBX
>
>
>   ------------------------------
>
> *From:* bruno.chatras@orange-ftgroup.com [mailto:
> bruno.chatras@orange-ftgroup.com]
> *Sent:* Tuesday, March 30, 2010 1:16 PM
> *To:* Hadriel Kaplan; richard@shockey.us; ietf.hanserik@gmail.com;
> john.elwell@siemens-enterprise.com
> *Cc:* martini@ietf.org
> *Subject:* RE: [martini] #21: 3.2.2 describes an issue with some PBX
>
>
>
> OK. If loose-route was implemented in some of these IMS networks (I guess=
 I
> know at least one of them) and you had to modify the R-URI on a per-trunk
> basis, it just means that some of the IP-PBXs connected to them were not
> IMS-compliant. Quite predictable as this loose-route mechanism is relativ=
ely
> new and therefore not yet available on all systems. Similarly, if a netwo=
rk
> implements the GIN solution, you will have to modify the R-URI on per-tru=
nk
> basis because some of the IP-PBXs will be loose-route compliant and will
> therefore not be GIN-compliant. Where is the improvement compared to the
> current situation?
>
>
>
> Because then for the GIN-compliant devices you know they=92re GIN complia=
nt
> from their signaling.  There is no per-trunk guessing/config for the
> GIN-compliant case.  It=92s true that some operators will have legacy
> IP-PBX=92s, but now they=92ll know which ones are *not* legacy anymore =
=96 right
> now they don=92t.  They don=92t know when an IP-PBX gets upgraded to supp=
ort
> IMS, and they don=92t know whether it is IMS to begin with.
>
>
>
> The current situation isn=92t that bad, when dealing with medium-to-large
> Enterprise trunks.  Provisioning is fine for that.  But in SIP-Connect 1.=
1
> we were faced with trying to handle/support the large-volume small-busine=
ss
> trunk case, and for that we=92re trying to keep provisioning as low as
> possible, in as few systems as possible.  And we needed the tools to help
> find mismatches.  Hence the option-tag.
>
>
>
> Personally I was hoping to just take IMS/ETSI and add the option-tag and
> minor tweaks =96 that was the =93shaken=94 draft in essence
> [=3D=3D>BC:] Yes I remember that and would have preferred going down this
> route.
>
>  , but the WG was split and we needed to move forward.  And GIN really
> isn=92t that much different either =96 is there something you=92d like to=
 see in
> GIN to make it more like the ETSI/IMS mechanism?
> [=3D=3D>BC:] Of course. I would like the R-URI to contain the initial tar=
get
> identity rather than this special contact address.
>
>
>
> -hadriel
>
> p.s. Actually my guess is that even if all sides think they=92re IMS
> compliant, that we=92d have to re-write the req-uri on a case-by-case bas=
is.
> Because it=92s not clear what it should be.  Is the domain-portion the PB=
X
> gets supposed to be =93ssp.com=94, or =93pbx.com=94?  Is it either/both? =
 Could it
> be =93ims.ssp.com=94, or even =93s-cscf.ssp.com=94?
> [=3D=3D>BC:] The domain portion can be "xxx.ssp.com" or "xxx.entreprise.c=
om"
> with the understanding that the DNS maps "xxx.entreprise.com" to the SSP'=
s
> network entry point.
>
>
>
>  Because those last two type/forms of host/domain names appear in the
> request-uri of requests received at the S-CSCF all the time in some IMS
> networks, so if IMS =93loose-route=94 literally means
> =93do-not-touch-the-request-uri=94, it will be fraught with issues.
>
>
>
>

--00c09f8c1c7916db170483157655
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Hadriel,<br>
<br>
(Changed the thread name.)<br>
<br>
Is your point that the use of a loose-route to the PBX as=20
such is not so much of a problem, but that SSP&#39;s would use it to delive=
r
 Request-URI&#39;s containing the SSP&#39;s domain to the IP-PBX?<br>
<br>
BR,<br clear=3D"all">/Hans Erik van Elburg<br><br><div class=3D"gmail_quote=
">On Wed, Mar 31, 2010 at 9:26 AM,  <span dir=3D"ltr">&lt;<a href=3D"mailto=
:bruno.chatras@orange-ftgroup.com">bruno.chatras@orange-ftgroup.com</a>&gt;=
</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">





<div vlink=3D"purple" link=3D"blue" lang=3D"EN-US">
<div dir=3D"ltr" align=3D"left"><font color=3D"#0000ff" face=3D"Arial" size=
=3D"2"></font>=A0</div><br>
<blockquote dir=3D"ltr" style=3D"padding-left: 5px; margin-left: 5px; borde=
r-left: 2px solid rgb(0, 0, 255); margin-right: 0px;">
  <div dir=3D"ltr" align=3D"left" lang=3D"fr">
  <hr>
  <font face=3D"Tahoma" size=3D"2"><div class=3D"im"><b>De=A0:</b> Hadriel =
Kaplan=20
  [mailto:<a href=3D"mailto:HKaplan@acmepacket.com" target=3D"_blank">HKapl=
an@acmepacket.com</a>] <br></div><b>Envoy=E9=A0:</b> mardi 30 mars 2010=20
  20:35<br><b>=C0=A0:</b> CHATRAS Bruno RD-CORE-ISS; <a href=3D"mailto:rich=
ard@shockey.us" target=3D"_blank">richard@shockey.us</a>;=20
  <a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">ietf.hanseri=
k@gmail.com</a>;=20
  <a href=3D"mailto:john.elwell@siemens-enterprise.com" target=3D"_blank">j=
ohn.elwell@siemens-enterprise.com</a><br><b>Cc=A0:</b>=20
  <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a=
><br><b>Objet=A0:</b> RE: [martini] #21: 3.2.2 describes an=20
  issue with some PBX<br></font><br></div>
  <div></div>
  <div>
  <p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><sp=
an style=3D"font-size: 10pt; color: navy; font-family: Arial;">=A0</span></=
font></p>
  <div style=3D"padding: 0in 0in 0in 4pt; border-width: medium medium mediu=
m 1.5pt; border-style: none none none solid; border-color: -moz-use-text-co=
lor -moz-use-text-color -moz-use-text-color blue;"><div class=3D"im">
  <div>
  <div class=3D"MsoNormal" style=3D"text-align: center;" align=3D"center"><=
font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size: 12pt;">
  <hr width=3D"100%" align=3D"center" size=3D"2">
  </span></font></div>
  <p class=3D"MsoNormal"><b><font face=3D"Tahoma" size=3D"2"><span style=3D=
"font-weight: bold; font-size: 10pt; font-family: Tahoma;">From:</span></fo=
nt></b><font face=3D"Tahoma" size=3D"2"><span style=3D"font-size: 10pt; fon=
t-family: Tahoma;">=20
  <a href=3D"mailto:bruno.chatras@orange-ftgroup.com" target=3D"_blank">bru=
no.chatras@orange-ftgroup.com</a> [mailto:<a href=3D"mailto:bruno.chatras@o=
range-ftgroup.com" target=3D"_blank">bruno.chatras@orange-ftgroup.com</a>]=
=20
  <br><b><span style=3D"font-weight: bold;">Sent:</span></b> Tuesday, March=
 30,=20
  2010 1:16 PM<br><b><span style=3D"font-weight: bold;">To:</span></b>=20
  Hadriel Kaplan; <a href=3D"mailto:richard@shockey.us" target=3D"_blank">r=
ichard@shockey.us</a>;=20
  <a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">ietf.hanseri=
k@gmail.com</a>; <a href=3D"mailto:john.elwell@siemens-enterprise.com" targ=
et=3D"_blank">john.elwell@siemens-enterprise.com</a><br><b><span style=3D"f=
ont-weight: bold;">Cc:</span></b> <a href=3D"mailto:martini@ietf.org" targe=
t=3D"_blank">martini@ietf.org</a><br>
<b><span style=3D"font-weight: bold;">Subject:</span></b> RE: [martini] #21=
: 3.2.2=20
  describes an issue with some PBX</span></font></p></div>
  <p class=3D"MsoNormal"><font face=3D"Times New Roman" size=3D"3"><span st=
yle=3D"font-size: 12pt;">=A0</span></font></p>
  <p class=3D"MsoNormal"><font color=3D"blue" face=3D"Arial" size=3D"2"><sp=
an style=3D"font-size: 10pt; color: blue; font-family: Arial;">OK. If loose=
-route=20
  was implemented in some of these IMS networks (I guess I know at least on=
e of=20
  them) and you had to modify the R-URI on a per-trunk basis, it just=A0mea=
ns=20
  that some of the IP-PBXs connected to them were not IMS-compliant. Quite=
=20
  predictable as this loose-route mechanism is relatively new and therefore=
 not=20
  yet available on all systems. Similarly, if a network implements the GIN=
=20
  solution, you will have to modify the R-URI on per-trunk basis because so=
me of=20
  the IP-PBXs will be loose-route compliant and will therefore not be=20
  GIN-compliant. Where is the improvement compared to the current=20
  situation?</span></font></p>
  <p class=3D"MsoNormal"><font color=3D"navy" face=3D"Times New Roman" size=
=3D"3"><span style=3D"font-size: 12pt; color: navy;">=A0</span></font></p>
  <p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><sp=
an style=3D"font-size: 10pt; color: navy; font-family: Arial;">Because then=
 for the=20
  GIN-compliant devices you know they=92re GIN compliant from their=20
  signaling.=A0 There is no per-trunk guessing/config for the GIN-compliant=
=20
  case. =A0It=92s true that some operators will have legacy IP-PBX=92s, but=
 now=20
  they=92ll know which ones are <i><span style=3D"font-style: italic;">not<=
/span></i>=20
  legacy anymore =96 right now they don=92t.=A0 They don=92t know when an I=
P-PBX=20
  gets upgraded to support IMS, and they don=92t know whether it is IMS to =
begin=20
  with.=A0 </span></font></p>
  <p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><sp=
an style=3D"font-size: 10pt; color: navy; font-family: Arial;">=A0</span></=
font></p>
  <p class=3D"MsoNormal"><font color=3D"navy"><span style=3D"font-size: 10p=
t; color: navy; font-family: Arial;">The current situation=20
  isn=92t that bad, when dealing with medium-to-large Enterprise trunks.=A0=
=20
  Provisioning is fine for that.=A0 But in SIP-Connect 1.1 we were faced wi=
th=20
  trying to handle/support the large-volume small-business trunk case, and =
for=20
  that we=92re trying to keep provisioning as low as possible, in as few sy=
stems=20
  as possible.=A0 And we needed the tools to help find mismatches.=A0=20
  Hence the option-tag.<br></span></font></p>
  <p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><sp=
an style=3D"font-size: 10pt; color: navy; font-family: Arial;">=A0</span></=
font></p>
  </div><p class=3D"MsoNormal"><font color=3D"navy"><span style=3D"font-siz=
e: 10pt; color: navy; font-family: Arial;"><div class=3D"im">Personally I w=
as=20
  hoping to just take IMS/ETSI and add the option-tag and minor tweaks =96 =
that=20
  was the =93shaken=94 draft in essence<br></div><span><font color=3D"#0000=
ff">[=3D=3D&gt;BC:]=A0Yes I remember that and would have preferred=20
  going down this route.</font></span></span></font></p>
  <p class=3D"MsoNormal"><font color=3D"navy"><span style=3D"font-size: 10p=
t; color: navy; font-family: Arial;"><div class=3D"im"><span>=A0</span>, bu=
t the WG was split and we needed to=20
  move forward. =A0And GIN really isn=92t that much different either =96 is=
 there=20
  something you=92d like to see in GIN to make it more like the ETSI/IMS=20
  mechanism?<br></div><font color=3D"#0000ff"><span>[=3D=3D&gt;BC:]=A0Of co=
urse. I would like the R-URI to=20
  contain the initial target identity rather than this special contact=20
  address.=A0</span></font></span></font></p>
  <p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><sp=
an style=3D"font-size: 10pt; color: navy; font-family: Arial;">=A0</span></=
font></p>
  <p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><sp=
an style=3D"font-size: 10pt; color: navy; font-family: Arial;">-hadriel</sp=
an></font></p>
  <p class=3D"MsoNormal"><font color=3D"navy"><span style=3D"font-size: 10p=
t; color: navy; font-family: Arial;"><div class=3D"im">p.s. Actually my=20
  guess is that even if all sides think they=92re IMS compliant, that we=92=
d have to=20
  re-write the req-uri on a case-by-case basis.=A0 Because it=92s not clear=
=20
  what it should be.=A0 Is the domain-portion the PBX gets supposed to be=
=20
  =93<a href=3D"http://ssp.com" target=3D"_blank">ssp.com</a>=94, or =93<a =
href=3D"http://pbx.com" target=3D"_blank">pbx.com</a>=94?=A0 Is it either/b=
oth?=A0 Could it be=20
  =93<a href=3D"http://ims.ssp.com" target=3D"_blank">ims.ssp.com</a>=94, o=
r even =93<a href=3D"http://s-cscf.ssp.com" target=3D"_blank">s-cscf.ssp.co=
m</a>=94?=A0 <br></div><span><font color=3D"#0000ff">[=3D=3D&gt;BC:]=A0The =
domain=20
  portion can be &quot;<a href=3D"http://xxx.ssp.com" target=3D"_blank">xxx=
.ssp.com</a>&quot; or &quot;<a href=3D"http://xxx.entreprise.com" target=3D=
"_blank">xxx.entreprise.com</a>&quot; with the understanding=20
  that the DNS maps &quot;<a href=3D"http://xxx.entreprise.com" target=3D"_=
blank">xxx.entreprise.com</a>&quot; to the SSP&#39;s network entry=20
  point.</font></span></span></font></p><div class=3D"im">
  <p class=3D"MsoNormal"><font color=3D"#0000ff"><span style=3D"font-size: =
10pt; color: navy; font-family: Arial;"><span></span></span></font>=A0</p>
  <p class=3D"MsoNormal"><font color=3D"navy"><span style=3D"font-size: 10p=
t; color: navy; font-family: Arial;"><span>=A0</span>Because those last two=
 type/forms of=20
  host/domain names appear in the request-uri of requests received at the S=
-CSCF=20
  all the time in some IMS networks, so if IMS =93loose-route=94 literally =
means=20
  =93do-not-touch-the-request-uri=94, it will be fraught with=20
  issues.</span></font></p>
  <p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><sp=
an style=3D"font-size: 10pt; color: navy; font-family: Arial;">=A0</span></=
font></p></div></div></div></blockquote></div>
</blockquote></div><br>

--00c09f8c1c7916db170483157655--

From keith.drage@alcatel-lucent.com  Wed Mar 31 04:18:13 2010
Return-Path: <keith.drage@alcatel-lucent.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 963AD3A6943 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 04:18:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.006
X-Spam-Level: 
X-Spam-Status: No, score=-4.006 tagged_above=-999 required=5 tests=[AWL=1.112,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, HTML_MESSAGE=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 zeyd1Bq13o-q for <martini@core3.amsl.com>; Wed, 31 Mar 2010 04:18:07 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id A963B3A67B6 for <martini@ietf.org>; Wed, 31 Mar 2010 04:18:05 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o2VBIVF9008128 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 31 Mar 2010 13:18:31 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Wed, 31 Mar 2010 13:18:31 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, Hans Erik van Elburg <ietf.hanserik@gmail.com>
Date: Wed, 31 Mar 2010 13:18:30 +0200
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrP+MFnIq24ETOlSXOXI8bY3L6MeAAMzzdQACXNMpA=
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE20D1C8238@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org> <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net> <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11BA34@MCHP058A.global-ad.net> <x2y9ae56b1e1003300349gc3ec82c7o449ba7554b7740b3@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11BF8E@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CADE11BF8E@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_EDC0A1AE77C57744B664A310A0B23AE20D1C8238FRMRSSXCHMBSC3d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.13
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 11:18:13 -0000

--_000_EDC0A1AE77C57744B664A310A0B23AE20D1C8238FRMRSSXCHMBSC3d_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

So assuming that this text is accepted, I guess the key argument of providi=
ng this distinction is not that both behaviours are non-standard, but that =
some means is needed to distinguish the two.

While I do not have a problem with that specifically, I still have an issue=
 that providing some signalling to do this solves all the issues. There are=
 all sorts of other issues associated with what the PBX "expects" that also=
 cause all sorts of issues, such as whether it expects a tel URI in tel URI=
 format or SIP URI format, and so on, that are not signalled.

Therefore at the end of the day, one is still going to end up with configur=
ation information at either end of this interface that is not explicitly si=
gnalled, and in the absence of both sides having preconfigured knowledge of=
 that information, the interface is not going to work.

regards

Keith

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Elwell, John
Sent: Tuesday, March 30, 2010 6:11 PM
To: Hans Erik van Elburg
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

OK, fixed in my working copy.

John

________________________________
From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
Sent: 30 March 2010 11:49
To: Elwell, John
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

Hi John,

Inline...

/Hans Erik van Elburg

On Mon, Mar 29, 2010 at 9:55 PM, Elwell, John <john.elwell@siemens-enterpri=
se.com<mailto:john.elwell@siemens-enterprise.com>> wrote:
Hans Erik,

I think the point you are trying to make is that it is not one-sided. The f=
act is, each side has different ways of working, and you need to have the t=
wo sides operating in compatible manners for it to work. In practice, I thi=
nk there are other variants, besides the two cited in the present 3.2.2.
Yes. And there is no objective way to automatically determine what variant =
the PBX or the SSP is supporting. Which is what an options tag could resolv=
e.

I would suggest:

       <t>Even where all information needed by the SIP-PBX is provided, in =
some deployments inbound SIP requests from the SSP have the registered Cont=
act URI in the Request-URI, whereas in other deployments inbound SIP reques=
ts have the intended target (AOR) in the Request-URI and the Contact URI in=
 the Route header field. There are other variants too. Interoperability pro=
blems arise when a PBX designed for or configured for one variant attempts =
to interwork with an SSP designed for or configured for another variant.</t=
>
Yes, slightly modified to add the objective means issue:
 <t>Even where all information needed by the SIP-PBX is provided, in some d=
eployments inbound SIP requests from the SSP have the registered PBX Contac=
t URI in the Request-URI, whereas in other deployments inbound SIP requests=
 have the intended target PBX user (AOR) in the Request-URI and the Contact=
 URI in the Route header field. There are other variants too. Interoperabil=
ity problems arise when a PBX designed for or configured for one variant at=
tempts to interwork with an SSP designed for or configured for another vari=
ant. There is currently no objective means in the signalling during registr=
ation for either party to discover what mechanism the other side supports.<=
/t>

To accompany this, I think the title of the section should be changed too: =
"Inconsistent placement of information in inbound requests"

Yes, slightly modified to make it more specific: "Inconsistent placement of=
 target URI information in inbound requests".

John

> -----Original Message-----
> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto:ietf.ha=
nserik@gmail.com>]
> Sent: 29 March 2010 17:27
> To: Elwell, John
> Cc: martini@ietf.org<mailto:martini@ietf.org>
> Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>
> Hi John,
>
> I was just trying to find a text that describes the issue.
>
> But now the issue reads like "some PBX like apples, some like
> bananas". To me that does not sound like a usefull issue to
> describe in an RFC.
>
> So I think one or two more sentence would make clear why this
> is an issue.
>
> I think there is multiple underlying issues here:
> - PBX have different SIP profiles or all SIP-PBX are different
> - PBX support SIP trunking flavour A, or support SIP trunking
> flavour B
> - SSP systems don't know what mechanism the PBX support (can
> be resolved with explicit indicator, this draft proposes an
> indicator for flavour B but for another purpose it seems)
> - PBX do not know what SIP trunking flavour the SSP supports
> (not addressed it seems)
>
> I don't seem to have a lucky hand with proposing an improved
> text, so maybe you should have a go at it.
>
> BR,
> /Hans Erik van Elburg
>
> p.s. I never said or implied that a SIP-PBX shall implement
> IMS. But it would be really, really, really good if they
> would interwork on the UNI with the IMS business trunking.  I
> think that should also be in your interest and in fact you
> have been part of that work...
>
>
>
> On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John
> <john.elwell@siemens-enterprise.com<mailto:john.elwell@siemens-enterprise=
.com>> wrote:
>
>
>       Hans Erik,
>
>       As an individual, I disagree with the proposed text,
> since it is misleading. The "international standards" to
> which you prefer are standards specific to an IMS
> environment. The implication of the wording as proposed is
> that SIP-PBXs ought to implement IMS specifications. And as
> Hadriel points out, implementing those IMS specifications
> does not eliminate the problems that the SIPconnect people
> are trying to solve. I believe the existing text in draft-03
> is sufficient.
>
>
>       John
>
>       > -----Original Message-----
>       > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto=
:ietf.hanserik@gmail.com>]
>
>       > Sent: 26 March 2010 23:03
>       > To: Elwell, John
>       > Cc: martini@ietf.org<mailto:martini@ietf.org>
>       > Subject: Re: [martini] #21: 3.2.2 describes an issue
> with some PBX
>       >
>       > I will not argue with you about the validity of that argument.
>       >
>       > Can you agree to the modified text?
>       >
>       > "Request-URI vs. loose-route acceptance
>       > Some IP-PBX do not implement international standards or SIP
>       > profiles for SIP trunking. As a consequence some SIP-PBXs
>       > expect that inbound SIP requests from the SSP will have the
>       > registered Contact-URI in the Request-URI, and thus not
>       > interoperate with the loose-route scheme of 3GPP and ETSI.
>       > Other SIP-PBXs are fine with the Request-URI being the
>       > intended target, but cannot handle receiving a Route header
>       > field identifying their registered Contact-URI as a
>       > loose-route entry."
>       >
>       > BR,
>       > /Hans Erik van Elburg
>       >
>       >
>       > On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
>       > <john.elwell@siemens-enterprise.com<mailto:john.elwell@siemens-en=
terprise.com>> wrote:
>       >
>       >
>       >       The IETF does not have a mechanism, and that is the
>       > reason for the MARTINI work. In particular, the IETF has not
>       > published the so-called loose-route mechanism. Hence the
>       > reason for the IETF, as owner of SIP, to publish a mechanism
>       > for bulk registrations.
>       >
>       >       John
>       >
>       >
>       >       > -----Original Message-----
>       >       > From: Hans Erik van Elburg
> [mailto:ietf.hanserik@gmail.com<mailto:ietf.hanserik@gmail.com>]
>       >       > Sent: 26 March 2010 02:21
>       >       > To: trac@localhost.amsl.com<mailto:trac@localhost.amsl.co=
m>
>       >       > Cc: Elwell, John; martini@ietf.org<mailto:martini@ietf.or=
g>
>       >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
>       > with some PBX
>       >       >
>       >       >
>       >       > Then you should rephrase to what the real issue is:
>       >       > "
>       >       >
>       >       >
>       >       > Request-URI vs. loose-route acceptance
>       >       >
>       >       >
>       >       > Some IP-PBX do not implement international
> standards or SIP
>       >       > profiles for SIP trunking. As a consequence
> some SIP-PBXs
>       >       > expect that inbound SIP requests from the SSP
> will have the
>       >       > registered Contact-URI in the Request-URI,
> and thus not
>       >       > interoperate with the loose-route scheme of
> 3GPP and ETSI.
>       >       > Other SIP-PBXs are fine with the Request-URI being the
>       >       > intended target, but cannot handle receiving
> a Route header
>       >       > field identifying their registered Contact-URI as a
>       >       > loose-route entry."
>       >       >
>       >       >
>       >       > Is this an issue, yes. Does introducing yet another
>       > profile help? No.
>       >       >
>       >       > /Hans Erik van Elburg
>       >       >
>       >       >
>       >       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
>       >       > <trac@tools.ietf.org<mailto:trac@tools.ietf.org>> wrote:
>       >       >
>       >       >
>       >       >       #21: 3.2.2 describes an issue with some PBX
>       >       >
>       >       >
> -------------------------------------+------------------------
>       >       > --------------
>       >       >        Reporter:  ietf.hanserik@...
> |        Owner:
>       >       >
>       >       >           Type:  defect                   |
>       > Status:  closed
>       >       >
>       >       >        Priority:  minor                    |
>       > Milestone:  milestone1
>       >       >       Component:  reqs                     |
>       > Version:  1.0
>       >       >
>       >       >        Severity:  In WG Last Call          |
>       > Resolution:  invalid
>       >       >        Keywords:                           |
>       >       >
>       >       >
> -------------------------------------+------------------------
>       >       > --------------
>       >       >       Changes (by john.elwell@...):
>       >       >
>       >       >        * status:  new =3D> closed
>       >       >        * resolution:  =3D> invalid
>       >       >
>       >       >
>       >       >       Comment:
>       >       >
>       >       >
>       >       >        The text of 3.2.2 just underlines the
> fact that there
>       >       > are different
>       >       >        implementations around. A PBX that
> expects the loose
>       >       > route mechanism to be
>       >       >        used would fail to interwork with SSPs using a
>       >       > different mechanism (e.g.,
>       >       >        SIPconnect 1.0), and a PBX not
> expecting the loose
>       >       > route mechanism to be
>       >       >        used would fail to interwork with a loose route
>       >       > implementation (e.g.,
>       >       >        ETSI/3GPP). Hence the urgent need for
> a standard.
>       >       >
>       >       >       --
>       >       >       Ticket URL:
>       >       >
>       >
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
>       >       >
>       >       >       martini <http://tools.ietf.org/martini/>
>       >       >
>       >       >
>       >       >       _______________________________________________
>       >       >       martini mailing list
>       >       >       martini@ietf.org<mailto:martini@ietf.org>
>       >       >       https://www.ietf.org/mailman/listinfo/martini
>       >       >
>       >       >
>       >       >
>       >       >
>       >
>       >
>       >
>
>
>


--_000_EDC0A1AE77C57744B664A310A0B23AE20D1C8238FRMRSSXCHMBSC3d_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D756321311-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>So assuming that this text is accepted, I guess th=
e key=20
argument of providing this distinction is not that both behaviours are=20
non-standard, but that some means is needed to distinguish the=20
two.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D756321311-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D756321311-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>While I do not have a problem with that specifical=
ly, I=20
still have an issue that providing some signalling to do this solves all th=
e=20
issues. There are all sorts of other issues associated with what the PBX=20
"expects" that also cause all sorts of issues, such as whether it expects a=
 tel=20
URI in tel URI format or SIP URI format, and so on, that are not signalled.=
=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D756321311-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D756321311-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Therefore at the end of the day, one is still goin=
g to end=20
up with configuration information at either end of this interface that is n=
ot=20
explicitly signalled, and in the absence of both sides having preconfigured=
=20
knowledge of that information, the interface is not going to=20
work.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D756321311-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D756321311-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>regards</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D756321311-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D756321311-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Keith</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D756321311-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DTahoma size=3D2><B>From:</B>=20
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <B>On Behalf Of=
=20
</B>Elwell, John<BR><B>Sent:</B> Tuesday, March 30, 2010 6:11 PM<BR><B>To:<=
/B>=20
Hans Erik van Elburg<BR><B>Cc:</B> martini@ietf.org<BR><B>Subject:</B> Re:=
=20
[martini] #21: 3.2.2 describes an issue with some PBX<BR></FONT><BR></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D186101117-30032010><FONT face=
=3DArial=20
  color=3D#0000ff size=3D2>OK, fixed in my working copy.</FONT></SPAN></DIV=
>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D186101117-30032010><FONT face=
=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D186101117-30032010><FONT face=
=3DArial=20
  color=3D#0000ff size=3D2>John</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px so=
lid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Hans Erik van Elburg=20
    [mailto:ietf.hanserik@gmail.com] <BR><B>Sent:</B> 30 March 2010=20
    11:49<BR><B>To:</B> Elwell, John<BR><B>Cc:</B>=20
    martini@ietf.org<BR><B>Subject:</B> Re: [martini] #21: 3.2.2 describes =
an=20
    issue with some PBX<BR></FONT><BR></DIV>
    <DIV></DIV>Hi John,<BR><BR>Inline... <BR clear=3Dall><BR>/Hans Erik van=
=20
    Elburg<BR><BR>
    <DIV class=3Dgmail_quote>On Mon, Mar 29, 2010 at 9:55 PM, Elwell, John =
<SPAN=20
    dir=3Dltr>&lt;<A=20
    href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemens-=
enterprise.com</A>&gt;</SPAN>=20
    wrote:<BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb=
(204,204,204) 1px solid">Hans=20
      Erik,<BR><BR>I think the point you are trying to make is that it is n=
ot=20
      one-sided. The fact is, each side has different ways of working, and =
you=20
      need to have the two sides operating in compatible manners for it to =
work.=20
      In practice, I think there are other variants, besides the two cited =
in=20
      the present 3.2.2.</BLOCKQUOTE>
    <DIV>Yes. And there is no objective way to automatically determine what=
=20
    variant the PBX or the SSP is supporting. Which is what an options tag =
could=20
    resolve.<BR>&nbsp;</DIV>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb=
(204,204,204) 1px solid">I=20
      would suggest:<BR><BR>&nbsp; &nbsp; &nbsp; &nbsp;&lt;t&gt;Even where =
all=20
      information needed by the SIP-PBX is provided, in some deployments in=
bound=20
      SIP requests from the SSP have the registered Contact URI in the=20
      Request-URI, whereas in other deployments inbound SIP requests have t=
he=20
      intended target (AOR) in the Request-URI and the Contact URI in the R=
oute=20
      header field. There are other variants too. Interoperability problems=
=20
      arise when a PBX designed for or configured for one variant attempts =
to=20
      interwork with an SSP designed for or configured for another=20
      variant.&lt;/t&gt;<BR></BLOCKQUOTE>
    <DIV>Yes, slightly modified to add the objective means=20
    issue:<BR>&nbsp;&lt;t&gt;Even where all information needed by the SIP-P=
BX is=20
    provided, in some deployments inbound SIP requests from the SSP have th=
e=20
    registered PBX Contact URI in the Request-URI, whereas in other deploym=
ents=20
    inbound SIP requests have the intended target PBX user (AOR) in the=20
    Request-URI and the Contact URI in the Route header field. There are ot=
her=20
    variants too. Interoperability problems arise when a PBX designed for o=
r=20
    configured for one variant attempts to interwork with an SSP designed f=
or or=20
    configured for another variant. There is currently no objective means i=
n the=20
    signalling during registration for either party to discover what mechan=
ism=20
    the other side supports.&lt;/t&gt;<BR>&nbsp;</DIV>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb=
(204,204,204) 1px solid">To=20
      accompany this, I think the title of the section should be changed to=
o:=20
      "Inconsistent placement of information in inbound requests"<BR>
      <DIV class=3Dim><BR></DIV></BLOCKQUOTE>
    <DIV>Yes, slightly modified to make it more specific: "Inconsistent=20
    placement of target URI information in inbound requests".<BR>&nbsp;</DI=
V>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb=
(204,204,204) 1px solid">
      <DIV class=3Dim>John<BR><BR>&gt; -----Original Message-----<BR>&gt; F=
rom:=20
      Hans Erik van Elburg [mailto:<A=20
      href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</A>]<=
BR></DIV>
      <DIV>
      <DIV></DIV>
      <DIV class=3Dh5>&gt; Sent: 29 March 2010 17:27<BR>&gt; To: Elwell,=20
      John<BR>&gt; Cc: <A=20
      href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; Subject=
: Re:=20
      [martini] #21: 3.2.2 describes an issue with some PBX<BR>&gt;<BR>&gt;=
 Hi=20
      John,<BR>&gt;<BR>&gt; I was just trying to find a text that describes=
 the=20
      issue.<BR>&gt;<BR>&gt; But now the issue reads like "some PBX like ap=
ples,=20
      some like<BR>&gt; bananas". To me that does not sound like a usefull =
issue=20
      to<BR>&gt; describe in an RFC.<BR>&gt;<BR>&gt; So I think one or two =
more=20
      sentence would make clear why this<BR>&gt; is an issue.<BR>&gt;<BR>&g=
t; I=20
      think there is multiple underlying issues here:<BR>&gt; - PBX have=20
      different SIP profiles or all SIP-PBX are different<BR>&gt; - PBX sup=
port=20
      SIP trunking flavour A, or support SIP trunking<BR>&gt; flavour B<BR>=
&gt;=20
      - SSP systems don't know what mechanism the PBX support (can<BR>&gt; =
be=20
      resolved with explicit indicator, this draft proposes an<BR>&gt; indi=
cator=20
      for flavour B but for another purpose it seems)<BR>&gt; - PBX do not =
know=20
      what SIP trunking flavour the SSP supports<BR>&gt; (not addressed it=
=20
      seems)<BR>&gt;<BR>&gt; I don't seem to have a lucky hand with proposi=
ng an=20
      improved<BR>&gt; text, so maybe you should have a go at=20
      it.<BR>&gt;<BR>&gt; BR,<BR>&gt; /Hans Erik van Elburg<BR>&gt;<BR>&gt;=
 p.s.=20
      I never said or implied that a SIP-PBX shall implement<BR>&gt; IMS. B=
ut it=20
      would be really, really, really good if they<BR>&gt; would interwork =
on=20
      the UNI with the IMS business trunking. &nbsp;I<BR>&gt; think that sh=
ould=20
      also be in your interest and in fact you<BR>&gt; have been part of th=
at=20
      work...<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; On Mon, Mar 29, 2010 at 5:56 =
PM,=20
      Elwell, John<BR>&gt; &lt;<A=20
      href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemen=
s-enterprise.com</A>&gt;=20
      wrote:<BR>&gt;<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; Hans=20
      Erik,<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; As an individual, I disagr=
ee=20
      with the proposed text,<BR>&gt; since it is misleading. The "internat=
ional=20
      standards" to<BR>&gt; which you prefer are standards specific to an=20
      IMS<BR>&gt; environment. The implication of the wording as proposed=20
      is<BR>&gt; that SIP-PBXs ought to implement IMS specifications. And=20
      as<BR>&gt; Hadriel points out, implementing those IMS=20
      specifications<BR>&gt; does not eliminate the problems that the SIPco=
nnect=20
      people<BR>&gt; are trying to solve. I believe the existing text in=20
      draft-03<BR>&gt; is sufficient.<BR>&gt;<BR>&gt;<BR>&gt; &nbsp; &nbsp;=
=20
      &nbsp; John<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; -----Original=20
      Message-----<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; From: Hans Erik van El=
burg=20
      [mailto:<A=20
      href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</A>]<=
BR>&gt;<BR>&gt;=20
      &nbsp; &nbsp; &nbsp; &gt; Sent: 26 March 2010 23:03<BR>&gt; &nbsp; &n=
bsp;=20
      &nbsp; &gt; To: Elwell, John<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Cc: <A=
=20
      href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; &nbsp; =
&nbsp;=20
      &nbsp; &gt; Subject: Re: [martini] #21: 3.2.2 describes an issue<BR>&=
gt;=20
      with some PBX<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp;=
=20
      &nbsp; &gt; I will not argue with you about the validity of that=20
      argument.<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nb=
sp;=20
      &gt; Can you agree to the modified text?<BR>&gt; &nbsp; &nbsp; &nbsp;=
=20
      &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; "Request-URI vs. loose-route=20
      acceptance<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Some IP-PBX do not imple=
ment=20
      international standards or SIP<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; prof=
iles=20
      for SIP trunking. As a consequence some SIP-PBXs<BR>&gt; &nbsp; &nbsp=
;=20
      &nbsp; &gt; expect that inbound SIP requests from the SSP will have=20
      the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; registered Contact-URI in the=20
      Request-URI, and thus not<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; interoper=
ate=20
      with the loose-route scheme of 3GPP and ETSI.<BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
      &gt; Other SIP-PBXs are fine with the Request-URI being the<BR>&gt; &=
nbsp;=20
      &nbsp; &nbsp; &gt; intended target, but cannot handle receiving a Rou=
te=20
      header<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; field identifying their=20
      registered Contact-URI as a<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; loose-r=
oute=20
      entry."<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp=
;=20
      &gt; BR,<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; /Hans Erik van Elburg<BR>&=
gt;=20
      &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &=
nbsp;=20
      &nbsp; &nbsp; &gt; On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John<BR>&=
gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &lt;<A=20
      href=3D"mailto:john.elwell@siemens-enterprise.com">john.elwell@siemen=
s-enterprise.com</A>&gt;=20
      wrote:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp;=
=20
      &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; The IETF =
does=20
      not have a mechanism, and that is the<BR>&gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
      reason for the MARTINI work. In particular, the IETF has not<BR>&gt;=
=20
      &nbsp; &nbsp; &nbsp; &gt; published the so-called loose-route mechani=
sm.=20
      Hence the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; reason for the IETF, as o=
wner=20
      of SIP, to publish a mechanism<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; for =
bulk=20
      registrations.<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp=
;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; John<BR>&gt; &nbsp; &nbsp; &nbsp;=20
      &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &=
gt;=20
      &nbsp; &nbsp; &nbsp; &gt; -----Original Message-----<BR>&gt; &nbsp; &=
nbsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; From: Hans Erik van Elburg<BR>&=
gt;=20
      [mailto:<A=20
      href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</A>]<=
BR>&gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Sent: 26 March 20=
10=20
      02:21<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; To:=
 <A=20
      href=3D"mailto:trac@localhost.amsl.com">trac@localhost.amsl.com</A><B=
R>&gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Cc: Elwell, John;=
 <A=20
      href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; &nbsp; =
&nbsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Subject: Re: [martini] #21: 3.2=
.2=20
      describes an issue<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; with some PBX<BR=
>&gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &n=
bsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
      &nbsp; &nbsp; &nbsp; &gt; Then you should rephrase to what the real i=
ssue=20
      is:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; "<BR>=
&gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &n=
bsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
      &nbsp; &nbsp; &nbsp; &gt; Request-URI vs. loose-route acceptance<BR>&=
gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &n=
bsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
      &nbsp; &nbsp; &nbsp; &gt; Some IP-PBX do not implement=20
      international<BR>&gt; standards or SIP<BR>&gt; &nbsp; &nbsp; &nbsp; &=
gt;=20
      &nbsp; &nbsp; &nbsp; &gt; profiles for SIP trunking. As a=20
      consequence<BR>&gt; some SIP-PBXs<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &=
nbsp;=20
      &nbsp; &nbsp; &gt; expect that inbound SIP requests from the SSP<BR>&=
gt;=20
      will have the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; =
&gt;=20
      registered Contact-URI in the Request-URI,<BR>&gt; and thus not<BR>&g=
t;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; interoperate with=
 the=20
      loose-route scheme of<BR>&gt; 3GPP and ETSI.<BR>&gt; &nbsp; &nbsp; &n=
bsp;=20
      &gt; &nbsp; &nbsp; &nbsp; &gt; Other SIP-PBXs are fine with the=20
      Request-URI being the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
      &nbsp; &gt; intended target, but cannot handle receiving<BR>&gt; a Ro=
ute=20
      header<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; fi=
eld=20
      identifying their registered Contact-URI as a<BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
      &gt; &nbsp; &nbsp; &nbsp; &gt; loose-route entry."<BR>&gt; &nbsp; &nb=
sp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
      &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &n=
bsp;=20
      &nbsp; &gt; Is this an issue, yes. Does introducing yet another<BR>&g=
t;=20
      &nbsp; &nbsp; &nbsp; &gt; profile help? No.<BR>&gt; &nbsp; &nbsp; &nb=
sp;=20
      &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbs=
p;=20
      &nbsp; &nbsp; &gt; /Hans Erik van Elburg<BR>&gt; &nbsp; &nbsp; &nbsp;=
 &gt;=20
      &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &n=
bsp;=20
      &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &g=
t; On=20
      Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker<BR>&gt; &nbsp; &n=
bsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &lt;<A=20
      href=3D"mailto:trac@tools.ietf.org">trac@tools.ietf.org</A>&gt;=20
      wrote:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR=
>&gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &n=
bsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; #21: 3.2.2=
=20
      describes an issue with some PBX<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &n=
bsp;=20
      &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &n=
bsp;=20
      &gt;<BR>&gt;=20
      -------------------------------------+------------------------<BR>&gt=
;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; --------------<BR=
>&gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nb=
sp;=20
      &nbsp;Reporter: &nbsp;ietf.hanserik@...<BR>&gt; | &nbsp; &nbsp; &nbsp=
;=20
      &nbsp;Owner:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
      &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbs=
p;=20
      &nbsp; &nbsp; &nbsp; &nbsp; Type: &nbsp;defect &nbsp; &nbsp; &nbsp; &=
nbsp;=20
      &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
      Status: &nbsp;closed<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
      &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
      &nbsp; &nbsp; &nbsp; &nbsp;Priority: &nbsp;minor &nbsp; &nbsp; &nbsp;=
=20
      &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|<BR>&gt; &nbsp; &nbs=
p;=20
      &nbsp; &gt; Milestone: &nbsp;milestone1<BR>&gt; &nbsp; &nbsp; &nbsp; =
&gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; Component: &nbsp;reqs=
=20
      &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
=20
      |<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Version: &nbsp;1.0<BR>&gt; &nbsp;=
=20
      &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &n=
bsp;=20
      &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Severity:=20
      &nbsp;In WG Last Call &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|<BR>&gt; &nb=
sp;=20
      &nbsp; &nbsp; &gt; Resolution: &nbsp;invalid<BR>&gt; &nbsp; &nbsp; &n=
bsp;=20
      &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Keywords: &=
nbsp;=20
      &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
=20
      &nbsp; &nbsp; |<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp=
;=20
      &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&=
gt;=20
      -------------------------------------+------------------------<BR>&gt=
;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; --------------<BR=
>&gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nb=
sp;=20
      Changes (by john.elwell@...):<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp=
;=20
      &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &n=
bsp;=20
      &gt; &nbsp; &nbsp; &nbsp; &nbsp;* status: &nbsp;new =3D&gt; closed<BR=
>&gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nb=
sp;=20
      &nbsp;* resolution: &nbsp;=3D&gt; invalid<BR>&gt; &nbsp; &nbsp; &nbsp=
; &gt;=20
      &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &n=
bsp;=20
      &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
      &nbsp; &nbsp; &nbsp; Comment:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp=
;=20
      &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &n=
bsp;=20
      &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbs=
p;=20
      &nbsp; &nbsp; &nbsp;The text of 3.2.2 just underlines the<BR>&gt; fac=
t=20
      that there<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt=
; are=20
      different<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
      &nbsp; &nbsp; &nbsp; &nbsp;implementations around. A PBX that<BR>&gt;=
=20
      expects the loose<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nb=
sp;=20
      &gt; route mechanism to be<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &=
nbsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;used would fail to interwork w=
ith=20
      SSPs using a<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &=
gt;=20
      different mechanism (e.g.,<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &=
nbsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;SIPconnect 1.0), and a PBX=20
      not<BR>&gt; expecting the loose<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nb=
sp;=20
      &nbsp; &nbsp; &gt; route mechanism to be<BR>&gt; &nbsp; &nbsp; &nbsp;=
 &gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;used would fail =
to=20
      interwork with a loose route<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
      &nbsp; &nbsp; &gt; implementation (e.g.,<BR>&gt; &nbsp; &nbsp; &nbsp;=
 &gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;ETSI/3GPP). Henc=
e the=20
      urgent need for<BR>&gt; a standard.<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
      &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &n=
bsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; --<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; Ticket URL:<BR>&gt; &n=
bsp;=20
      &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &n=
bsp;=20
      &gt;<BR>&gt; &lt;<A=20
      href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:=
1"=20
      target=3D_blank>http://trac.tools.ietf.org/wg/martini/trac/ticket/21#=
comment:1</A>&gt;<BR>&gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &n=
bsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; martini &l=
t;<A=20
      href=3D"http://tools.ietf.org/martini/"=20
      target=3D_blank>http://tools.ietf.org/martini/</A>&gt;<BR>&gt; &nbsp;=
 &nbsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
      &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &n=
bsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
      _______________________________________________<BR>&gt; &nbsp; &nbsp;=
=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; martini ma=
iling=20
      list<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbs=
p;=20
      &nbsp; &nbsp; <A=20
      href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR>&gt; &nbsp; =
&nbsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; <A=20
      href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
      target=3D_blank>https://www.ietf.org/mailman/listinfo/martini</A><BR>=
&gt;=20
      &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &n=
bsp;=20
      &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
      &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &n=
bsp;=20
      &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
      &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
    </DIV></DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BLOCKQUOTE></BODY></H=
TML>

--_000_EDC0A1AE77C57744B664A310A0B23AE20D1C8238FRMRSSXCHMBSC3d_--

From ietf.hanserik@gmail.com  Wed Mar 31 04:28:18 2010
Return-Path: <ietf.hanserik@gmail.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 AE4EC3A687D for <martini@core3.amsl.com>; Wed, 31 Mar 2010 04:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.419
X-Spam-Level: 
X-Spam-Status: No, score=-0.419 tagged_above=-999 required=5 tests=[AWL=1.049,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 NJ5n4lxDe1EA for <martini@core3.amsl.com>; Wed, 31 Mar 2010 04:28:16 -0700 (PDT)
Received: from mail-ew0-f224.google.com (mail-ew0-f224.google.com [209.85.219.224]) by core3.amsl.com (Postfix) with ESMTP id 9DBD83A6846 for <martini@ietf.org>; Wed, 31 Mar 2010 04:28:15 -0700 (PDT)
Received: by ewy24 with SMTP id 24so1919086ewy.13 for <martini@ietf.org>; Wed, 31 Mar 2010 04:28:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:received:message-id :subject:from:to:cc:content-type; bh=OeI0pKULXZUa+Ih+Ibxa1Tw3yK+s8McRN3cdyUkwbX4=; b=eiymGNCB3XcA7/JX/yYmVtJD2gcxU+j52u96QwyB/m5Kv1Ds7TzyovBKbBgkTh5G/u YjNbAIDDjXWFnIMMPBl1m0PA2YRNEnw5jaqZ0OO6fLlMQPD9TwUONgVf83rFDQIze8bA vnZOvaeTQRSDsrPikXOEXNApPVM1QxF+j4jbA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=Iyfk26vN7VPKGpq2Jodic2W3AEk7r8YvkFxd9yJYfPJ7oDwHLhud+RKhSkUBDwq+s3 yHSKiwgbn4bmMqV0HMg2S0VQ9zfLwFLPf9KUSuLKmkdTZ7zcgGGqGHRUnvUgE44qFcdg 0ief+0tlMNOrnf5+ty9wFYHhzDbBNZgyTgnRU=
MIME-Version: 1.0
Received: by 10.213.15.138 with HTTP; Wed, 31 Mar 2010 04:28:42 -0700 (PDT)
Date: Wed, 31 Mar 2010 13:28:42 +0200
Received: by 10.213.46.133 with SMTP id j5mr2207051ebf.32.1270034923013; Wed,  31 Mar 2010 04:28:43 -0700 (PDT)
Message-ID: <w2v9ae56b1e1003310428o6fc07243j294b603eec953a1a@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=00148531b7e5704aad0483170cc1
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: [martini] Need for a SIP/SDP profile for SIP trunking , was Re:  #21: 	3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 11:28:18 -0000

--00148531b7e5704aad0483170cc1
Content-Type: text/plain; charset=ISO-8859-1

Yes, I agree with that observation.

Only solving the routing issue does not solve the overall problem. For that
a minimum SIP/SDP profile needs to be agreed upon. Also what are common
denominator as codec for voice, fax, dtmf etc.

The question rises if there should be an option tag to signal support for a
profile instead of only signalling what routing method is preferred.

BR,
/Hans Erik van Elburg


On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, Keith (Keith) <
keith.drage@alcatel-lucent.com> wrote:

>  So assuming that this text is accepted, I guess the key argument of
> providing this distinction is not that both behaviours are non-standard, but
> that some means is needed to distinguish the two.
>
> While I do not have a problem with that specifically, I still have an issue
> that providing some signalling to do this solves all the issues. There are
> all sorts of other issues associated with what the PBX "expects" that also
> cause all sorts of issues, such as whether it expects a tel URI in tel URI
> format or SIP URI format, and so on, that are not signalled.
>
> Therefore at the end of the day, one is still going to end up with
> configuration information at either end of this interface that is not
> explicitly signalled, and in the absence of both sides having preconfigured
> knowledge of that information, the interface is not going to work.
>
> regards
>
> Keith
>
>  ------------------------------
>  *From:* martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] *On
> Behalf Of *Elwell, John
> *Sent:* Tuesday, March 30, 2010 6:11 PM
> *To:* Hans Erik van Elburg
>
> *Cc:* martini@ietf.org
> *Subject:* Re: [martini] #21: 3.2.2 describes an issue with some PBX
>
>  OK, fixed in my working copy.
>
> John
>
>  ------------------------------
> *From:* Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
> *Sent:* 30 March 2010 11:49
> *To:* Elwell, John
> *Cc:* martini@ietf.org
> *Subject:* Re: [martini] #21: 3.2.2 describes an issue with some PBX
>
> Hi John,
>
> Inline...
>
> /Hans Erik van Elburg
>
> On Mon, Mar 29, 2010 at 9:55 PM, Elwell, John <
> john.elwell@siemens-enterprise.com> wrote:
>
>> Hans Erik,
>>
>> I think the point you are trying to make is that it is not one-sided. The
>> fact is, each side has different ways of working, and you need to have the
>> two sides operating in compatible manners for it to work. In practice, I
>> think there are other variants, besides the two cited in the present 3.2.2.
>
> Yes. And there is no objective way to automatically determine what variant
> the PBX or the SSP is supporting. Which is what an options tag could
> resolve.
>
>
>> I would suggest:
>>
>>        <t>Even where all information needed by the SIP-PBX is provided, in
>> some deployments inbound SIP requests from the SSP have the registered
>> Contact URI in the Request-URI, whereas in other deployments inbound SIP
>> requests have the intended target (AOR) in the Request-URI and the Contact
>> URI in the Route header field. There are other variants too.
>> Interoperability problems arise when a PBX designed for or configured for
>> one variant attempts to interwork with an SSP designed for or configured for
>> another variant.</t>
>>
> Yes, slightly modified to add the objective means issue:
>  <t>Even where all information needed by the SIP-PBX is provided, in some
> deployments inbound SIP requests from the SSP have the registered PBX
> Contact URI in the Request-URI, whereas in other deployments inbound SIP
> requests have the intended target PBX user (AOR) in the Request-URI and the
> Contact URI in the Route header field. There are other variants too.
> Interoperability problems arise when a PBX designed for or configured for
> one variant attempts to interwork with an SSP designed for or configured for
> another variant. There is currently no objective means in the signalling
> during registration for either party to discover what mechanism the other
> side supports.</t>
>
>
>> To accompany this, I think the title of the section should be changed too:
>> "Inconsistent placement of information in inbound requests"
>>
>> Yes, slightly modified to make it more specific: "Inconsistent placement
> of target URI information in inbound requests".
>
>
>> John
>>
>> > -----Original Message-----
>> > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
>>  > Sent: 29 March 2010 17:27
>> > To: Elwell, John
>> > Cc: martini@ietf.org
>> > Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>> >
>> > Hi John,
>> >
>> > I was just trying to find a text that describes the issue.
>> >
>> > But now the issue reads like "some PBX like apples, some like
>> > bananas". To me that does not sound like a usefull issue to
>> > describe in an RFC.
>> >
>> > So I think one or two more sentence would make clear why this
>> > is an issue.
>> >
>> > I think there is multiple underlying issues here:
>> > - PBX have different SIP profiles or all SIP-PBX are different
>> > - PBX support SIP trunking flavour A, or support SIP trunking
>> > flavour B
>> > - SSP systems don't know what mechanism the PBX support (can
>> > be resolved with explicit indicator, this draft proposes an
>> > indicator for flavour B but for another purpose it seems)
>> > - PBX do not know what SIP trunking flavour the SSP supports
>> > (not addressed it seems)
>> >
>> > I don't seem to have a lucky hand with proposing an improved
>> > text, so maybe you should have a go at it.
>> >
>> > BR,
>> > /Hans Erik van Elburg
>> >
>> > p.s. I never said or implied that a SIP-PBX shall implement
>> > IMS. But it would be really, really, really good if they
>> > would interwork on the UNI with the IMS business trunking.  I
>> > think that should also be in your interest and in fact you
>> > have been part of that work...
>> >
>> >
>> >
>> > On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John
>> > <john.elwell@siemens-enterprise.com> wrote:
>> >
>> >
>> >       Hans Erik,
>> >
>> >       As an individual, I disagree with the proposed text,
>> > since it is misleading. The "international standards" to
>> > which you prefer are standards specific to an IMS
>> > environment. The implication of the wording as proposed is
>> > that SIP-PBXs ought to implement IMS specifications. And as
>> > Hadriel points out, implementing those IMS specifications
>> > does not eliminate the problems that the SIPconnect people
>> > are trying to solve. I believe the existing text in draft-03
>> > is sufficient.
>> >
>> >
>> >       John
>> >
>> >       > -----Original Message-----
>> >       > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
>> >
>> >       > Sent: 26 March 2010 23:03
>> >       > To: Elwell, John
>> >       > Cc: martini@ietf.org
>> >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
>> > with some PBX
>> >       >
>> >       > I will not argue with you about the validity of that argument.
>> >       >
>> >       > Can you agree to the modified text?
>> >       >
>> >       > "Request-URI vs. loose-route acceptance
>> >       > Some IP-PBX do not implement international standards or SIP
>> >       > profiles for SIP trunking. As a consequence some SIP-PBXs
>> >       > expect that inbound SIP requests from the SSP will have the
>> >       > registered Contact-URI in the Request-URI, and thus not
>> >       > interoperate with the loose-route scheme of 3GPP and ETSI.
>> >       > Other SIP-PBXs are fine with the Request-URI being the
>> >       > intended target, but cannot handle receiving a Route header
>> >       > field identifying their registered Contact-URI as a
>> >       > loose-route entry."
>> >       >
>> >       > BR,
>> >       > /Hans Erik van Elburg
>> >       >
>> >       >
>> >       > On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
>> >       > <john.elwell@siemens-enterprise.com> wrote:
>> >       >
>> >       >
>> >       >       The IETF does not have a mechanism, and that is the
>> >       > reason for the MARTINI work. In particular, the IETF has not
>> >       > published the so-called loose-route mechanism. Hence the
>> >       > reason for the IETF, as owner of SIP, to publish a mechanism
>> >       > for bulk registrations.
>> >       >
>> >       >       John
>> >       >
>> >       >
>> >       >       > -----Original Message-----
>> >       >       > From: Hans Erik van Elburg
>> > [mailto:ietf.hanserik@gmail.com]
>> >       >       > Sent: 26 March 2010 02:21
>> >       >       > To: trac@localhost.amsl.com
>> >       >       > Cc: Elwell, John; martini@ietf.org
>> >       >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
>> >       > with some PBX
>> >       >       >
>> >       >       >
>> >       >       > Then you should rephrase to what the real issue is:
>> >       >       > "
>> >       >       >
>> >       >       >
>> >       >       > Request-URI vs. loose-route acceptance
>> >       >       >
>> >       >       >
>> >       >       > Some IP-PBX do not implement international
>> > standards or SIP
>> >       >       > profiles for SIP trunking. As a consequence
>> > some SIP-PBXs
>> >       >       > expect that inbound SIP requests from the SSP
>> > will have the
>> >       >       > registered Contact-URI in the Request-URI,
>> > and thus not
>> >       >       > interoperate with the loose-route scheme of
>> > 3GPP and ETSI.
>> >       >       > Other SIP-PBXs are fine with the Request-URI being the
>> >       >       > intended target, but cannot handle receiving
>> > a Route header
>> >       >       > field identifying their registered Contact-URI as a
>> >       >       > loose-route entry."
>> >       >       >
>> >       >       >
>> >       >       > Is this an issue, yes. Does introducing yet another
>> >       > profile help? No.
>> >       >       >
>> >       >       > /Hans Erik van Elburg
>> >       >       >
>> >       >       >
>> >       >       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
>> >       >       > <trac@tools.ietf.org> wrote:
>> >       >       >
>> >       >       >
>> >       >       >       #21: 3.2.2 describes an issue with some PBX
>> >       >       >
>> >       >       >
>> > -------------------------------------+------------------------
>> >       >       > --------------
>> >       >       >        Reporter:  ietf.hanserik@...
>> > |        Owner:
>> >       >       >
>> >       >       >           Type:  defect                   |
>> >       > Status:  closed
>> >       >       >
>> >       >       >        Priority:  minor                    |
>> >       > Milestone:  milestone1
>> >       >       >       Component:  reqs                     |
>> >       > Version:  1.0
>> >       >       >
>> >       >       >        Severity:  In WG Last Call          |
>> >       > Resolution:  invalid
>> >       >       >        Keywords:                           |
>> >       >       >
>> >       >       >
>> > -------------------------------------+------------------------
>> >       >       > --------------
>> >       >       >       Changes (by john.elwell@...):
>> >       >       >
>> >       >       >        * status:  new => closed
>> >       >       >        * resolution:  => invalid
>> >       >       >
>> >       >       >
>> >       >       >       Comment:
>> >       >       >
>> >       >       >
>> >       >       >        The text of 3.2.2 just underlines the
>> > fact that there
>> >       >       > are different
>> >       >       >        implementations around. A PBX that
>> > expects the loose
>> >       >       > route mechanism to be
>> >       >       >        used would fail to interwork with SSPs using a
>> >       >       > different mechanism (e.g.,
>> >       >       >        SIPconnect 1.0), and a PBX not
>> > expecting the loose
>> >       >       > route mechanism to be
>> >       >       >        used would fail to interwork with a loose route
>> >       >       > implementation (e.g.,
>> >       >       >        ETSI/3GPP). Hence the urgent need for
>> > a standard.
>> >       >       >
>> >       >       >       --
>> >       >       >       Ticket URL:
>> >       >       >
>> >       >
>> > <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
>> >       >       >
>> >       >       >       martini <http://tools.ietf.org/martini/>
>> >       >       >
>> >       >       >
>> >       >       >       _______________________________________________
>> >       >       >       martini mailing list
>> >       >       >       martini@ietf.org
>> >       >       >       https://www.ietf.org/mailman/listinfo/martini
>> >       >       >
>> >       >       >
>> >       >       >
>> >       >       >
>> >       >
>> >       >
>> >       >
>> >
>> >
>> >
>>
>
>

--00148531b7e5704aad0483170cc1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Yes, I agree with that observation.<br><br>Only solving the routing issue d=
oes not solve the overall problem. For that a minimum SIP/SDP profile needs=
 to be agreed upon. Also what are common denominator as codec for voice, fa=
x, dtmf etc. <br>
<br>The question rises if there should be an option tag to signal support f=
or a profile instead of only signalling what routing method is preferred.<b=
r><br>BR,<br clear=3D"all">/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, =
Keith (Keith) <span dir=3D"ltr">&lt;<a href=3D"mailto:keith.drage@alcatel-l=
ucent.com">keith.drage@alcatel-lucent.com</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: =
1px solid rgb(204, 204, 204); padding-left: 1ex;">




<div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">So assuming that this text is accepted, I guess the key=20
argument of providing this distinction is not that both behaviours are=20
non-standard, but that some means is needed to distinguish the=20
two.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">While I do not have a problem with that specifically, I=20
still have an issue that providing some signalling to do this solves all th=
e=20
issues. There are all sorts of other issues associated with what the PBX=20
&quot;expects&quot; that also cause all sorts of issues, such as whether it=
 expects a tel=20
URI in tel URI format or SIP URI format, and so on, that are not signalled.=
=20
</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">Therefore at the end of the day, one is still going to end=20
up with configuration information at either end of this interface that is n=
ot=20
explicitly signalled, and in the absence of both sides having preconfigured=
=20
knowledge of that information, the interface is not going to=20
work.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">regards</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">Keith</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left">
<hr>
</div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Tahoma" size=3D"2"><b>From:</=
b>=20
<a href=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">martini-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:martini-bounces@ietf.org" target=
=3D"_blank">martini-bounces@ietf.org</a>] <b>On Behalf Of=20
</b>Elwell, John<br><b>Sent:</b> Tuesday, March 30, 2010 6:11 PM<br><b>To:<=
/b>=20
Hans Erik van Elburg<div><div></div><div class=3D"h5"><br><b>Cc:</b> <a hre=
f=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><br><b>=
Subject:</b> Re:=20
[martini] #21: 3.2.2 describes an issue with some PBX<br></div></div></font=
><br></div><div><div></div><div class=3D"h5">
<blockquote dir=3D"ltr" style=3D"padding-left: 5px; margin-left: 5px; borde=
r-left: 2px solid rgb(0, 0, 255); margin-right: 0px;">
  <div></div>
  <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Ari=
al" size=3D"2">OK, fixed in my working copy.</font></span></div>
  <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Ari=
al" size=3D"2"></font></span>=A0</div>
  <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Ari=
al" size=3D"2">John</font></span></div><br>
  <blockquote style=3D"padding-left: 5px; margin-left: 5px; border-left: 2p=
x solid rgb(0, 0, 255); margin-right: 0px;">
    <div dir=3D"ltr" align=3D"left" lang=3D"en-us">
    <hr>
    <font face=3D"Tahoma" size=3D"2"><b>From:</b> Hans Erik van Elburg=20
    [mailto:<a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">ie=
tf.hanserik@gmail.com</a>] <br><b>Sent:</b> 30 March 2010=20
    11:49<br><b>To:</b> Elwell, John<br><b>Cc:</b>=20
    <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org<=
/a><br><b>Subject:</b> Re: [martini] #21: 3.2.2 describes an=20
    issue with some PBX<br></font><br></div>
    <div></div>Hi John,<br><br>Inline... <br clear=3D"all"><br>/Hans Erik v=
an=20
    Elburg<br><br>
    <div class=3D"gmail_quote">On Mon, Mar 29, 2010 at 9:55 PM, Elwell, Joh=
n <span dir=3D"ltr">&lt;<a href=3D"mailto:john.elwell@siemens-enterprise.co=
m" target=3D"_blank">john.elwell@siemens-enterprise.com</a>&gt;</span>=20
    wrote:<br>
    <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; margin: 0=
pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">Hans=20
      Erik,<br><br>I think the point you are trying to make is that it is n=
ot=20
      one-sided. The fact is, each side has different ways of working, and =
you=20
      need to have the two sides operating in compatible manners for it to =
work.=20
      In practice, I think there are other variants, besides the two cited =
in=20
      the present 3.2.2.</blockquote>
    <div>Yes. And there is no objective way to automatically determine what=
=20
    variant the PBX or the SSP is supporting. Which is what an options tag =
could=20
    resolve.<br>=A0</div>
    <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; margin: 0=
pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">I=20
      would suggest:<br><br>=A0 =A0 =A0 =A0&lt;t&gt;Even where all=20
      information needed by the SIP-PBX is provided, in some deployments in=
bound=20
      SIP requests from the SSP have the registered Contact URI in the=20
      Request-URI, whereas in other deployments inbound SIP requests have t=
he=20
      intended target (AOR) in the Request-URI and the Contact URI in the R=
oute=20
      header field. There are other variants too. Interoperability problems=
=20
      arise when a PBX designed for or configured for one variant attempts =
to=20
      interwork with an SSP designed for or configured for another=20
      variant.&lt;/t&gt;<br></blockquote>
    <div>Yes, slightly modified to add the objective means=20
    issue:<br>=A0&lt;t&gt;Even where all information needed by the SIP-PBX =
is=20
    provided, in some deployments inbound SIP requests from the SSP have th=
e=20
    registered PBX Contact URI in the Request-URI, whereas in other deploym=
ents=20
    inbound SIP requests have the intended target PBX user (AOR) in the=20
    Request-URI and the Contact URI in the Route header field. There are ot=
her=20
    variants too. Interoperability problems arise when a PBX designed for o=
r=20
    configured for one variant attempts to interwork with an SSP designed f=
or or=20
    configured for another variant. There is currently no objective means i=
n the=20
    signalling during registration for either party to discover what mechan=
ism=20
    the other side supports.&lt;/t&gt;<br>=A0</div>
    <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; margin: 0=
pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">To=20
      accompany this, I think the title of the section should be changed to=
o:=20
      &quot;Inconsistent placement of information in inbound requests&quot;=
<br>
      <div><br></div></blockquote>
    <div>Yes, slightly modified to make it more specific: &quot;Inconsisten=
t=20
    placement of target URI information in inbound requests&quot;.<br>=A0</=
div>
    <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; margin: 0=
pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">
      <div>John<br><br>&gt; -----Original Message-----<br>&gt; From:=20
      Hans Erik van Elburg [mailto:<a href=3D"mailto:ietf.hanserik@gmail.co=
m" target=3D"_blank">ietf.hanserik@gmail.com</a>]<br></div>
      <div>
      <div></div>
      <div>&gt; Sent: 29 March 2010 17:27<br>&gt; To: Elwell,=20
      John<br>&gt; Cc: <a href=3D"mailto:martini@ietf.org" target=3D"_blank=
">martini@ietf.org</a><br>&gt; Subject: Re:=20
      [martini] #21: 3.2.2 describes an issue with some PBX<br>&gt;<br>&gt;=
 Hi=20
      John,<br>&gt;<br>&gt; I was just trying to find a text that describes=
 the=20
      issue.<br>&gt;<br>&gt; But now the issue reads like &quot;some PBX li=
ke apples,=20
      some like<br>&gt; bananas&quot;. To me that does not sound like a use=
full issue=20
      to<br>&gt; describe in an RFC.<br>&gt;<br>&gt; So I think one or two =
more=20
      sentence would make clear why this<br>&gt; is an issue.<br>&gt;<br>&g=
t; I=20
      think there is multiple underlying issues here:<br>&gt; - PBX have=20
      different SIP profiles or all SIP-PBX are different<br>&gt; - PBX sup=
port=20
      SIP trunking flavour A, or support SIP trunking<br>&gt; flavour B<br>=
&gt;=20
      - SSP systems don&#39;t know what mechanism the PBX support (can<br>&=
gt; be=20
      resolved with explicit indicator, this draft proposes an<br>&gt; indi=
cator=20
      for flavour B but for another purpose it seems)<br>&gt; - PBX do not =
know=20
      what SIP trunking flavour the SSP supports<br>&gt; (not addressed it=
=20
      seems)<br>&gt;<br>&gt; I don&#39;t seem to have a lucky hand with pro=
posing an=20
      improved<br>&gt; text, so maybe you should have a go at=20
      it.<br>&gt;<br>&gt; BR,<br>&gt; /Hans Erik van Elburg<br>&gt;<br>&gt;=
 p.s.=20
      I never said or implied that a SIP-PBX shall implement<br>&gt; IMS. B=
ut it=20
      would be really, really, really good if they<br>&gt; would interwork =
on=20
      the UNI with the IMS business trunking. =A0I<br>&gt; think that shoul=
d=20
      also be in your interest and in fact you<br>&gt; have been part of th=
at=20
      work...<br>&gt;<br>&gt;<br>&gt;<br>&gt; On Mon, Mar 29, 2010 at 5:56 =
PM,=20
      Elwell, John<br>&gt; &lt;<a href=3D"mailto:john.elwell@siemens-enterp=
rise.com" target=3D"_blank">john.elwell@siemens-enterprise.com</a>&gt;=20
      wrote:<br>&gt;<br>&gt;<br>&gt; =A0 =A0 =A0 Hans=20
      Erik,<br>&gt;<br>&gt; =A0 =A0 =A0 As an individual, I disagree=20
      with the proposed text,<br>&gt; since it is misleading. The &quot;int=
ernational=20
      standards&quot; to<br>&gt; which you prefer are standards specific to=
 an=20
      IMS<br>&gt; environment. The implication of the wording as proposed=
=20
      is<br>&gt; that SIP-PBXs ought to implement IMS specifications. And=
=20
      as<br>&gt; Hadriel points out, implementing those IMS=20
      specifications<br>&gt; does not eliminate the problems that the SIPco=
nnect=20
      people<br>&gt; are trying to solve. I believe the existing text in=20
      draft-03<br>&gt; is sufficient.<br>&gt;<br>&gt;<br>&gt; =A0 =A0=20
      =A0 John<br>&gt;<br>&gt; =A0 =A0 =A0 &gt; -----Original=20
      Message-----<br>&gt; =A0 =A0 =A0 &gt; From: Hans Erik van Elburg=20
      [mailto:<a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">=
ietf.hanserik@gmail.com</a>]<br>&gt;<br>&gt;=20
      =A0 =A0 =A0 &gt; Sent: 26 March 2010 23:03<br>&gt; =A0 =A0=20
      =A0 &gt; To: Elwell, John<br>&gt; =A0 =A0 =A0 &gt; Cc: <a href=3D"mai=
lto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><br>&gt; =A0 =
=A0=20
      =A0 &gt; Subject: Re: [martini] #21: 3.2.2 describes an issue<br>&gt;=
=20
      with some PBX<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; I will not argue with you about the validity of that=20
      argument.<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
      &gt; Can you agree to the modified text?<br>&gt; =A0 =A0 =A0=20
      &gt;<br>&gt; =A0 =A0 =A0 &gt; &quot;Request-URI vs. loose-route=20
      acceptance<br>&gt; =A0 =A0 =A0 &gt; Some IP-PBX do not implement=20
      international standards or SIP<br>&gt; =A0 =A0 =A0 &gt; profiles=20
      for SIP trunking. As a consequence some SIP-PBXs<br>&gt; =A0 =A0=20
      =A0 &gt; expect that inbound SIP requests from the SSP will have=20
      the<br>&gt; =A0 =A0 =A0 &gt; registered Contact-URI in the=20
      Request-URI, and thus not<br>&gt; =A0 =A0 =A0 &gt; interoperate=20
      with the loose-route scheme of 3GPP and ETSI.<br>&gt; =A0 =A0 =A0=20
      &gt; Other SIP-PBXs are fine with the Request-URI being the<br>&gt; =
=A0=20
      =A0 =A0 &gt; intended target, but cannot handle receiving a Route=20
      header<br>&gt; =A0 =A0 =A0 &gt; field identifying their=20
      registered Contact-URI as a<br>&gt; =A0 =A0 =A0 &gt; loose-route=20
      entry.&quot;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
      &gt; BR,<br>&gt; =A0 =A0 =A0 &gt; /Hans Erik van Elburg<br>&gt;=20
      =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0=20
      =A0 =A0 &gt; On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John<br>&gt;=20
      =A0 =A0 =A0 &gt; &lt;<a href=3D"mailto:john.elwell@siemens-enterprise=
.com" target=3D"_blank">john.elwell@siemens-enterprise.com</a>&gt;=20
      wrote:<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
      &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 The IETF does=20
      not have a mechanism, and that is the<br>&gt; =A0 =A0 =A0 &gt;=20
      reason for the MARTINI work. In particular, the IETF has not<br>&gt;=
=20
      =A0 =A0 =A0 &gt; published the so-called loose-route mechanism.=20
      Hence the<br>&gt; =A0 =A0 =A0 &gt; reason for the IETF, as owner=20
      of SIP, to publish a mechanism<br>&gt; =A0 =A0 =A0 &gt; for bulk=20
      registrations.<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 John<br>&gt; =A0 =A0 =A0=20
      &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; -----Original Message-----<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt; From: Hans Erik van Elburg<br>&gt;=20
      [mailto:<a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">=
ietf.hanserik@gmail.com</a>]<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; Sent: 26 March 2010=20
      02:21<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; To: <a href=3D"mailto=
:trac@localhost.amsl.com" target=3D"_blank">trac@localhost.amsl.com</a><br>=
&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; Cc: Elwell, John; <a href=3D"mailto=
:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><br>&gt; =A0 =A0=
=20
      =A0 &gt; =A0 =A0 =A0 &gt; Subject: Re: [martini] #21: 3.2.2=20
      describes an issue<br>&gt; =A0 =A0 =A0 &gt; with some PBX<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; Then you should rephrase to what the real issue=20
      is:<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; &quot;<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; Request-URI vs. loose-route acceptance<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; Some IP-PBX do not implement=20
      international<br>&gt; standards or SIP<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; profiles for SIP trunking. As a=20
      consequence<br>&gt; some SIP-PBXs<br>&gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 &gt; expect that inbound SIP requests from the SSP<br>&gt;=20
      will have the<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
      registered Contact-URI in the Request-URI,<br>&gt; and thus not<br>&g=
t;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; interoperate with the=20
      loose-route scheme of<br>&gt; 3GPP and ETSI.<br>&gt; =A0 =A0 =A0=20
      &gt; =A0 =A0 =A0 &gt; Other SIP-PBXs are fine with the=20
      Request-URI being the<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt; intended target, but cannot handle receiving<br>&gt; a Route=
=20
      header<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; field=20
      identifying their registered Contact-URI as a<br>&gt; =A0 =A0 =A0=20
      &gt; =A0 =A0 =A0 &gt; loose-route entry.&quot;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt; Is this an issue, yes. Does introducing yet another<br>&gt;=
=20
      =A0 =A0 =A0 &gt; profile help? No.<br>&gt; =A0 =A0 =A0=20
      &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 &gt; /Hans Erik van Elburg<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; On=20
      Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker<br>&gt; =A0 =A0=
=20
      =A0 &gt; =A0 =A0 =A0 &gt; &lt;<a href=3D"mailto:trac@tools.ietf.org" =
target=3D"_blank">trac@tools.ietf.org</a>&gt;=20
      wrote:<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 #21: 3.2.2=20
      describes an issue with some PBX<br>&gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      &gt;<br>&gt;=20
      -------------------------------------+------------------------<br>&gt=
;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; --------------<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      =A0Reporter: =A0ietf.hanserik@...<br>&gt; | =A0 =A0 =A0=20
      =A0Owner:<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 =A0 =A0 Type: =A0defect =A0 =A0 =A0 =A0=20
      =A0 =A0 =A0 =A0 =A0 |<br>&gt; =A0 =A0 =A0 &gt;=20
      Status: =A0closed<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 =A0Priority: =A0minor =A0 =A0 =A0=20
      =A0 =A0 =A0 =A0 =A0 =A0 =A0|<br>&gt; =A0 =A0=20
      =A0 &gt; Milestone: =A0milestone1<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 Component: =A0reqs=20
      =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=20
      |<br>&gt; =A0 =A0 =A0 &gt; Version: =A01.0<br>&gt; =A0=20
      =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
      &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Severity:=20
      =A0In WG Last Call =A0 =A0 =A0 =A0 =A0|<br>&gt; =A0=20
      =A0 =A0 &gt; Resolution: =A0invalid<br>&gt; =A0 =A0 =A0=20
      &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Keywords: =A0=20
      =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=20
      =A0 =A0 |<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt;=20
      -------------------------------------+------------------------<br>&gt=
;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; --------------<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      Changes (by john.elwell@...):<br>&gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      &gt; =A0 =A0 =A0 =A0* status: =A0new =3D&gt; closed<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      =A0* resolution: =A0=3D&gt; invalid<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 Comment:<br>&gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 =A0The text of 3.2.2 just underlines the<br>&gt; fact=20
      that there<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; are=20
      different<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 =A0implementations around. A PBX that<br>&gt;=20
      expects the loose<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      &gt; route mechanism to be<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 =A0used would fail to interwork with=20
      SSPs using a<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
      different mechanism (e.g.,<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 =A0SIPconnect 1.0), and a PBX=20
      not<br>&gt; expecting the loose<br>&gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 &gt; route mechanism to be<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0used would fail to=20
      interwork with a loose route<br>&gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 &gt; implementation (e.g.,<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0ETSI/3GPP). Hence the=20
      urgent need for<br>&gt; a standard.<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 --<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 Ticket URL:<br>&gt; =A0=20
      =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
      &gt;<br>&gt; &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/tra=
c/ticket/21#comment:1" target=3D"_blank">http://trac.tools.ietf.org/wg/mart=
ini/trac/ticket/21#comment:1</a>&gt;<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 martini &lt;<a href=3D"http://t=
ools.ietf.org/martini/" target=3D"_blank">http://tools.ietf.org/martini/</a=
>&gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0=20
      _______________________________________________<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 martini mailing=20
      list<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini=
@ietf.org</a><br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 <a href=3D"https://www.ietf.org=
/mailman/listinfo/martini" target=3D"_blank">https://www.ietf.org/mailman/l=
istinfo/martini</a><br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
      &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt;<br>&gt;<br>&gt;=20
    </div></div></blockquote></div><br></blockquote></blockquote></div></di=
v></div>
</blockquote></div><br>

--00148531b7e5704aad0483170cc1--

From ietf.hanserik@gmail.com  Wed Mar 31 05:23:34 2010
Return-Path: <ietf.hanserik@gmail.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 B3B0B3A694F for <martini@core3.amsl.com>; Wed, 31 Mar 2010 05:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.05
X-Spam-Level: 
X-Spam-Status: No, score=-1.05 tagged_above=-999 required=5 tests=[AWL=0.418,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 E1unfqFxzxr6 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 05:23:32 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by core3.amsl.com (Postfix) with ESMTP id 62A7C3A692C for <martini@ietf.org>; Wed, 31 Mar 2010 05:23:19 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 9so143155eyd.5 for <martini@ietf.org>; Wed, 31 Mar 2010 05:23:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type; bh=v/slqODWSfD4k1FUw69gYXBd4TxinfmOXc1qH2kIHw8=; b=G82KXTRKEPHkvDRiKoF5OffKyM3iL29aXh3ZRUEBs1jvyi4Pe10ajglxgXB7e96sdc kLDUtrLmAXz/j6/xWIoHDn6waYatrsNZLJz2QwV5xp/l8NQy0imsoJPOJS58d5yW7XgO 9/Q28A4aKvhKVyh0PjyupiBFZID/EJjv4LN+Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=IvtlsiVaCV/laA1tUQu1GL8GkM9GwMLefhFKmpjWSL1jPwUPPhAgNouLlTrRfSVXe+ ua9zPR+uU/8JygLqH+D9o2VrvPWtPfDyvkyk2Y19CqU/yT15ntQHlwhWGV4u+JrarnH8 MX9kg1ZmRkHUbzn9uWow0NT80hxlIWGTDInKM=
MIME-Version: 1.0
Received: by 10.213.15.138 with HTTP; Wed, 31 Mar 2010 05:23:44 -0700 (PDT)
In-Reply-To: <w2v9ae56b1e1003310428o6fc07243j294b603eec953a1a@mail.gmail.com>
References: <w2v9ae56b1e1003310428o6fc07243j294b603eec953a1a@mail.gmail.com>
Date: Wed, 31 Mar 2010 14:23:44 +0200
Received: by 10.213.67.13 with SMTP id p13mr2241936ebi.17.1270038224995; Wed,  31 Mar 2010 05:23:44 -0700 (PDT)
Message-ID: <m2k9ae56b1e1003310523zc70f6a83ub0e5b1bdaeddd5ce@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "martini@ietf.org" <martini@ietf.org>
Content-Type: multipart/alternative; boundary=00c09f7d633e4087f5048317d154
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re: 	#21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 12:23:34 -0000

--00c09f7d633e4087f5048317d154
Content-Type: text/plain; charset=ISO-8859-1

I should have said "explicit indication" instead of "option tag". Feature
tags maybe more appropriate, when talking about a profile.

/Hans Erik van Elburg


On Wed, Mar 31, 2010 at 1:28 PM, Hans Erik van Elburg <
ietf.hanserik@gmail.com> wrote:

> Yes, I agree with that observation.
>
> Only solving the routing issue does not solve the overall problem. For that
> a minimum SIP/SDP profile needs to be agreed upon. Also what are common
> denominator as codec for voice, fax, dtmf etc.
>
> The question rises if there should be an option tag to signal support for a
> profile instead of only signalling what routing method is preferred.
>
> BR,
> /Hans Erik van Elburg
>
>
> On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, Keith (Keith) <
> keith.drage@alcatel-lucent.com> wrote:
>
>>  So assuming that this text is accepted, I guess the key argument of
>> providing this distinction is not that both behaviours are non-standard, but
>> that some means is needed to distinguish the two.
>>
>> While I do not have a problem with that specifically, I still have an
>> issue that providing some signalling to do this solves all the issues. There
>> are all sorts of other issues associated with what the PBX "expects" that
>> also cause all sorts of issues, such as whether it expects a tel URI in tel
>> URI format or SIP URI format, and so on, that are not signalled.
>>
>> Therefore at the end of the day, one is still going to end up with
>> configuration information at either end of this interface that is not
>> explicitly signalled, and in the absence of both sides having preconfigured
>> knowledge of that information, the interface is not going to work.
>>
>> regards
>>
>> Keith
>>
>>  ------------------------------
>>  *From:* martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] *On
>> Behalf Of *Elwell, John
>> *Sent:* Tuesday, March 30, 2010 6:11 PM
>> *To:* Hans Erik van Elburg
>>
>> *Cc:* martini@ietf.org
>> *Subject:* Re: [martini] #21: 3.2.2 describes an issue with some PBX
>>
>>  OK, fixed in my working copy.
>>
>> John
>>
>>  ------------------------------
>> *From:* Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
>> *Sent:* 30 March 2010 11:49
>> *To:* Elwell, John
>> *Cc:* martini@ietf.org
>> *Subject:* Re: [martini] #21: 3.2.2 describes an issue with some PBX
>>
>> Hi John,
>>
>> Inline...
>>
>> /Hans Erik van Elburg
>>
>> On Mon, Mar 29, 2010 at 9:55 PM, Elwell, John <
>> john.elwell@siemens-enterprise.com> wrote:
>>
>>> Hans Erik,
>>>
>>> I think the point you are trying to make is that it is not one-sided. The
>>> fact is, each side has different ways of working, and you need to have the
>>> two sides operating in compatible manners for it to work. In practice, I
>>> think there are other variants, besides the two cited in the present 3.2.2.
>>
>> Yes. And there is no objective way to automatically determine what variant
>> the PBX or the SSP is supporting. Which is what an options tag could
>> resolve.
>>
>>
>>> I would suggest:
>>>
>>>        <t>Even where all information needed by the SIP-PBX is provided,
>>> in some deployments inbound SIP requests from the SSP have the registered
>>> Contact URI in the Request-URI, whereas in other deployments inbound SIP
>>> requests have the intended target (AOR) in the Request-URI and the Contact
>>> URI in the Route header field. There are other variants too.
>>> Interoperability problems arise when a PBX designed for or configured for
>>> one variant attempts to interwork with an SSP designed for or configured for
>>> another variant.</t>
>>>
>> Yes, slightly modified to add the objective means issue:
>>  <t>Even where all information needed by the SIP-PBX is provided, in some
>> deployments inbound SIP requests from the SSP have the registered PBX
>> Contact URI in the Request-URI, whereas in other deployments inbound SIP
>> requests have the intended target PBX user (AOR) in the Request-URI and the
>> Contact URI in the Route header field. There are other variants too.
>> Interoperability problems arise when a PBX designed for or configured for
>> one variant attempts to interwork with an SSP designed for or configured for
>> another variant. There is currently no objective means in the signalling
>> during registration for either party to discover what mechanism the other
>> side supports.</t>
>>
>>
>>> To accompany this, I think the title of the section should be changed
>>> too: "Inconsistent placement of information in inbound requests"
>>>
>>> Yes, slightly modified to make it more specific: "Inconsistent placement
>> of target URI information in inbound requests".
>>
>>
>>> John
>>>
>>> > -----Original Message-----
>>> > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
>>>  > Sent: 29 March 2010 17:27
>>> > To: Elwell, John
>>> > Cc: martini@ietf.org
>>> > Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>>> >
>>> > Hi John,
>>> >
>>> > I was just trying to find a text that describes the issue.
>>> >
>>> > But now the issue reads like "some PBX like apples, some like
>>> > bananas". To me that does not sound like a usefull issue to
>>> > describe in an RFC.
>>> >
>>> > So I think one or two more sentence would make clear why this
>>> > is an issue.
>>> >
>>> > I think there is multiple underlying issues here:
>>> > - PBX have different SIP profiles or all SIP-PBX are different
>>> > - PBX support SIP trunking flavour A, or support SIP trunking
>>> > flavour B
>>> > - SSP systems don't know what mechanism the PBX support (can
>>> > be resolved with explicit indicator, this draft proposes an
>>> > indicator for flavour B but for another purpose it seems)
>>> > - PBX do not know what SIP trunking flavour the SSP supports
>>> > (not addressed it seems)
>>> >
>>> > I don't seem to have a lucky hand with proposing an improved
>>> > text, so maybe you should have a go at it.
>>> >
>>> > BR,
>>> > /Hans Erik van Elburg
>>> >
>>> > p.s. I never said or implied that a SIP-PBX shall implement
>>> > IMS. But it would be really, really, really good if they
>>> > would interwork on the UNI with the IMS business trunking.  I
>>> > think that should also be in your interest and in fact you
>>> > have been part of that work...
>>> >
>>> >
>>> >
>>> > On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John
>>> > <john.elwell@siemens-enterprise.com> wrote:
>>> >
>>> >
>>> >       Hans Erik,
>>> >
>>> >       As an individual, I disagree with the proposed text,
>>> > since it is misleading. The "international standards" to
>>> > which you prefer are standards specific to an IMS
>>> > environment. The implication of the wording as proposed is
>>> > that SIP-PBXs ought to implement IMS specifications. And as
>>> > Hadriel points out, implementing those IMS specifications
>>> > does not eliminate the problems that the SIPconnect people
>>> > are trying to solve. I believe the existing text in draft-03
>>> > is sufficient.
>>> >
>>> >
>>> >       John
>>> >
>>> >       > -----Original Message-----
>>> >       > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
>>> >
>>> >       > Sent: 26 March 2010 23:03
>>> >       > To: Elwell, John
>>> >       > Cc: martini@ietf.org
>>> >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
>>> > with some PBX
>>> >       >
>>> >       > I will not argue with you about the validity of that argument.
>>> >       >
>>> >       > Can you agree to the modified text?
>>> >       >
>>> >       > "Request-URI vs. loose-route acceptance
>>> >       > Some IP-PBX do not implement international standards or SIP
>>> >       > profiles for SIP trunking. As a consequence some SIP-PBXs
>>> >       > expect that inbound SIP requests from the SSP will have the
>>> >       > registered Contact-URI in the Request-URI, and thus not
>>> >       > interoperate with the loose-route scheme of 3GPP and ETSI.
>>> >       > Other SIP-PBXs are fine with the Request-URI being the
>>> >       > intended target, but cannot handle receiving a Route header
>>> >       > field identifying their registered Contact-URI as a
>>> >       > loose-route entry."
>>> >       >
>>> >       > BR,
>>> >       > /Hans Erik van Elburg
>>> >       >
>>> >       >
>>> >       > On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
>>> >       > <john.elwell@siemens-enterprise.com> wrote:
>>> >       >
>>> >       >
>>> >       >       The IETF does not have a mechanism, and that is the
>>> >       > reason for the MARTINI work. In particular, the IETF has not
>>> >       > published the so-called loose-route mechanism. Hence the
>>> >       > reason for the IETF, as owner of SIP, to publish a mechanism
>>> >       > for bulk registrations.
>>> >       >
>>> >       >       John
>>> >       >
>>> >       >
>>> >       >       > -----Original Message-----
>>> >       >       > From: Hans Erik van Elburg
>>> > [mailto:ietf.hanserik@gmail.com]
>>> >       >       > Sent: 26 March 2010 02:21
>>> >       >       > To: trac@localhost.amsl.com
>>> >       >       > Cc: Elwell, John; martini@ietf.org
>>> >       >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
>>> >       > with some PBX
>>> >       >       >
>>> >       >       >
>>> >       >       > Then you should rephrase to what the real issue is:
>>> >       >       > "
>>> >       >       >
>>> >       >       >
>>> >       >       > Request-URI vs. loose-route acceptance
>>> >       >       >
>>> >       >       >
>>> >       >       > Some IP-PBX do not implement international
>>> > standards or SIP
>>> >       >       > profiles for SIP trunking. As a consequence
>>> > some SIP-PBXs
>>> >       >       > expect that inbound SIP requests from the SSP
>>> > will have the
>>> >       >       > registered Contact-URI in the Request-URI,
>>> > and thus not
>>> >       >       > interoperate with the loose-route scheme of
>>> > 3GPP and ETSI.
>>> >       >       > Other SIP-PBXs are fine with the Request-URI being the
>>> >       >       > intended target, but cannot handle receiving
>>> > a Route header
>>> >       >       > field identifying their registered Contact-URI as a
>>> >       >       > loose-route entry."
>>> >       >       >
>>> >       >       >
>>> >       >       > Is this an issue, yes. Does introducing yet another
>>> >       > profile help? No.
>>> >       >       >
>>> >       >       > /Hans Erik van Elburg
>>> >       >       >
>>> >       >       >
>>> >       >       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
>>> >       >       > <trac@tools.ietf.org> wrote:
>>> >       >       >
>>> >       >       >
>>> >       >       >       #21: 3.2.2 describes an issue with some PBX
>>> >       >       >
>>> >       >       >
>>> > -------------------------------------+------------------------
>>> >       >       > --------------
>>> >       >       >        Reporter:  ietf.hanserik@...
>>> > |        Owner:
>>> >       >       >
>>> >       >       >           Type:  defect                   |
>>> >       > Status:  closed
>>> >       >       >
>>> >       >       >        Priority:  minor                    |
>>> >       > Milestone:  milestone1
>>> >       >       >       Component:  reqs                     |
>>> >       > Version:  1.0
>>> >       >       >
>>> >       >       >        Severity:  In WG Last Call          |
>>> >       > Resolution:  invalid
>>> >       >       >        Keywords:                           |
>>> >       >       >
>>> >       >       >
>>> > -------------------------------------+------------------------
>>> >       >       > --------------
>>> >       >       >       Changes (by john.elwell@...):
>>> >       >       >
>>> >       >       >        * status:  new => closed
>>> >       >       >        * resolution:  => invalid
>>> >       >       >
>>> >       >       >
>>> >       >       >       Comment:
>>> >       >       >
>>> >       >       >
>>> >       >       >        The text of 3.2.2 just underlines the
>>> > fact that there
>>> >       >       > are different
>>> >       >       >        implementations around. A PBX that
>>> > expects the loose
>>> >       >       > route mechanism to be
>>> >       >       >        used would fail to interwork with SSPs using a
>>> >       >       > different mechanism (e.g.,
>>> >       >       >        SIPconnect 1.0), and a PBX not
>>> > expecting the loose
>>> >       >       > route mechanism to be
>>> >       >       >        used would fail to interwork with a loose route
>>> >       >       > implementation (e.g.,
>>> >       >       >        ETSI/3GPP). Hence the urgent need for
>>> > a standard.
>>> >       >       >
>>> >       >       >       --
>>> >       >       >       Ticket URL:
>>> >       >       >
>>> >       >
>>> > <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
>>> >       >       >
>>> >       >       >       martini <http://tools.ietf.org/martini/>
>>> >       >       >
>>> >       >       >
>>> >       >       >       _______________________________________________
>>> >       >       >       martini mailing list
>>> >       >       >       martini@ietf.org
>>> >       >       >       https://www.ietf.org/mailman/listinfo/martini
>>> >       >       >
>>> >       >       >
>>> >       >       >
>>> >       >       >
>>> >       >
>>> >       >
>>> >       >
>>> >
>>> >
>>> >
>>>
>>
>>
>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
>
>

--00c09f7d633e4087f5048317d154
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I should have said &quot;explicit indication&quot; instead of &quot;option =
tag&quot;. Feature tags maybe more appropriate, when talking about a profil=
e.<br><br clear=3D"all">/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Wed, Mar 31, 2010 at 1:28 PM, Hans Er=
ik van Elburg <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf.hanserik@gmail.c=
om">ietf.hanserik@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(=
204, 204, 204); padding-left: 1ex;">
Yes, I agree with that observation.<br><br>Only solving the routing issue d=
oes not solve the overall problem. For that a minimum SIP/SDP profile needs=
 to be agreed upon. Also what are common denominator as codec for voice, fa=
x, dtmf etc. <br>

<br>The question rises if there should be an option tag to signal support f=
or a profile instead of only signalling what routing method is preferred.<b=
r><br>BR,<br clear=3D"all">/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, =
Keith (Keith) <span dir=3D"ltr">&lt;<a href=3D"mailto:keith.drage@alcatel-l=
ucent.com" target=3D"_blank">keith.drage@alcatel-lucent.com</a>&gt;</span> =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">




<div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">So assuming that this text is accepted, I guess the key=20
argument of providing this distinction is not that both behaviours are=20
non-standard, but that some means is needed to distinguish the=20
two.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">While I do not have a problem with that specifically, I=20
still have an issue that providing some signalling to do this solves all th=
e=20
issues. There are all sorts of other issues associated with what the PBX=20
&quot;expects&quot; that also cause all sorts of issues, such as whether it=
 expects a tel=20
URI in tel URI format or SIP URI format, and so on, that are not signalled.=
=20
</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">Therefore at the end of the day, one is still going to end=20
up with configuration information at either end of this interface that is n=
ot=20
explicitly signalled, and in the absence of both sides having preconfigured=
=20
knowledge of that information, the interface is not going to=20
work.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">regards</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">Keith</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left">
<hr>
</div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Tahoma" size=3D"2"><b>From:</=
b>=20
<a href=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">martini-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:martini-bounces@ietf.org" target=
=3D"_blank">martini-bounces@ietf.org</a>] <b>On Behalf Of=20
</b>Elwell, John<br><b>Sent:</b> Tuesday, March 30, 2010 6:11 PM<br><b>To:<=
/b>=20
Hans Erik van Elburg<div><div></div><div><br><b>Cc:</b> <a href=3D"mailto:m=
artini@ietf.org" target=3D"_blank">martini@ietf.org</a><br><b>Subject:</b> =
Re:=20
[martini] #21: 3.2.2 describes an issue with some PBX<br></div></div></font=
><br></div><div><div></div><div>
<blockquote dir=3D"ltr" style=3D"padding-left: 5px; margin-left: 5px; borde=
r-left: 2px solid rgb(0, 0, 255); margin-right: 0px;">
  <div></div>
  <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Ari=
al" size=3D"2">OK, fixed in my working copy.</font></span></div>
  <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Ari=
al" size=3D"2"></font></span>=A0</div>
  <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Ari=
al" size=3D"2">John</font></span></div><br>
  <blockquote style=3D"padding-left: 5px; margin-left: 5px; border-left: 2p=
x solid rgb(0, 0, 255); margin-right: 0px;">
    <div dir=3D"ltr" align=3D"left" lang=3D"en-us">
    <hr>
    <font face=3D"Tahoma" size=3D"2"><b>From:</b> Hans Erik van Elburg=20
    [mailto:<a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">ie=
tf.hanserik@gmail.com</a>] <br><b>Sent:</b> 30 March 2010=20
    11:49<br><b>To:</b> Elwell, John<br><b>Cc:</b>=20
    <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org<=
/a><br><b>Subject:</b> Re: [martini] #21: 3.2.2 describes an=20
    issue with some PBX<br></font><br></div>
    <div></div>Hi John,<br><br>Inline... <br clear=3D"all"><br>/Hans Erik v=
an=20
    Elburg<br><br>
    <div class=3D"gmail_quote">On Mon, Mar 29, 2010 at 9:55 PM, Elwell, Joh=
n <span dir=3D"ltr">&lt;<a href=3D"mailto:john.elwell@siemens-enterprise.co=
m" target=3D"_blank">john.elwell@siemens-enterprise.com</a>&gt;</span>=20
    wrote:<br>
    <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; margin: 0=
pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">Hans=20
      Erik,<br><br>I think the point you are trying to make is that it is n=
ot=20
      one-sided. The fact is, each side has different ways of working, and =
you=20
      need to have the two sides operating in compatible manners for it to =
work.=20
      In practice, I think there are other variants, besides the two cited =
in=20
      the present 3.2.2.</blockquote>
    <div>Yes. And there is no objective way to automatically determine what=
=20
    variant the PBX or the SSP is supporting. Which is what an options tag =
could=20
    resolve.<br>=A0</div>
    <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; margin: 0=
pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">I=20
      would suggest:<br><br>=A0 =A0 =A0 =A0&lt;t&gt;Even where all=20
      information needed by the SIP-PBX is provided, in some deployments in=
bound=20
      SIP requests from the SSP have the registered Contact URI in the=20
      Request-URI, whereas in other deployments inbound SIP requests have t=
he=20
      intended target (AOR) in the Request-URI and the Contact URI in the R=
oute=20
      header field. There are other variants too. Interoperability problems=
=20
      arise when a PBX designed for or configured for one variant attempts =
to=20
      interwork with an SSP designed for or configured for another=20
      variant.&lt;/t&gt;<br></blockquote>
    <div>Yes, slightly modified to add the objective means=20
    issue:<br>=A0&lt;t&gt;Even where all information needed by the SIP-PBX =
is=20
    provided, in some deployments inbound SIP requests from the SSP have th=
e=20
    registered PBX Contact URI in the Request-URI, whereas in other deploym=
ents=20
    inbound SIP requests have the intended target PBX user (AOR) in the=20
    Request-URI and the Contact URI in the Route header field. There are ot=
her=20
    variants too. Interoperability problems arise when a PBX designed for o=
r=20
    configured for one variant attempts to interwork with an SSP designed f=
or or=20
    configured for another variant. There is currently no objective means i=
n the=20
    signalling during registration for either party to discover what mechan=
ism=20
    the other side supports.&lt;/t&gt;<br>=A0</div>
    <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; margin: 0=
pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">To=20
      accompany this, I think the title of the section should be changed to=
o:=20
      &quot;Inconsistent placement of information in inbound requests&quot;=
<br>
      <div><br></div></blockquote>
    <div>Yes, slightly modified to make it more specific: &quot;Inconsisten=
t=20
    placement of target URI information in inbound requests&quot;.<br>=A0</=
div>
    <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; margin: 0=
pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">
      <div>John<br><br>&gt; -----Original Message-----<br>&gt; From:=20
      Hans Erik van Elburg [mailto:<a href=3D"mailto:ietf.hanserik@gmail.co=
m" target=3D"_blank">ietf.hanserik@gmail.com</a>]<br></div>
      <div>
      <div></div>
      <div>&gt; Sent: 29 March 2010 17:27<br>&gt; To: Elwell,=20
      John<br>&gt; Cc: <a href=3D"mailto:martini@ietf.org" target=3D"_blank=
">martini@ietf.org</a><br>&gt; Subject: Re:=20
      [martini] #21: 3.2.2 describes an issue with some PBX<br>&gt;<br>&gt;=
 Hi=20
      John,<br>&gt;<br>&gt; I was just trying to find a text that describes=
 the=20
      issue.<br>&gt;<br>&gt; But now the issue reads like &quot;some PBX li=
ke apples,=20
      some like<br>&gt; bananas&quot;. To me that does not sound like a use=
full issue=20
      to<br>&gt; describe in an RFC.<br>&gt;<br>&gt; So I think one or two =
more=20
      sentence would make clear why this<br>&gt; is an issue.<br>&gt;<br>&g=
t; I=20
      think there is multiple underlying issues here:<br>&gt; - PBX have=20
      different SIP profiles or all SIP-PBX are different<br>&gt; - PBX sup=
port=20
      SIP trunking flavour A, or support SIP trunking<br>&gt; flavour B<br>=
&gt;=20
      - SSP systems don&#39;t know what mechanism the PBX support (can<br>&=
gt; be=20
      resolved with explicit indicator, this draft proposes an<br>&gt; indi=
cator=20
      for flavour B but for another purpose it seems)<br>&gt; - PBX do not =
know=20
      what SIP trunking flavour the SSP supports<br>&gt; (not addressed it=
=20
      seems)<br>&gt;<br>&gt; I don&#39;t seem to have a lucky hand with pro=
posing an=20
      improved<br>&gt; text, so maybe you should have a go at=20
      it.<br>&gt;<br>&gt; BR,<br>&gt; /Hans Erik van Elburg<br>&gt;<br>&gt;=
 p.s.=20
      I never said or implied that a SIP-PBX shall implement<br>&gt; IMS. B=
ut it=20
      would be really, really, really good if they<br>&gt; would interwork =
on=20
      the UNI with the IMS business trunking. =A0I<br>&gt; think that shoul=
d=20
      also be in your interest and in fact you<br>&gt; have been part of th=
at=20
      work...<br>&gt;<br>&gt;<br>&gt;<br>&gt; On Mon, Mar 29, 2010 at 5:56 =
PM,=20
      Elwell, John<br>&gt; &lt;<a href=3D"mailto:john.elwell@siemens-enterp=
rise.com" target=3D"_blank">john.elwell@siemens-enterprise.com</a>&gt;=20
      wrote:<br>&gt;<br>&gt;<br>&gt; =A0 =A0 =A0 Hans=20
      Erik,<br>&gt;<br>&gt; =A0 =A0 =A0 As an individual, I disagree=20
      with the proposed text,<br>&gt; since it is misleading. The &quot;int=
ernational=20
      standards&quot; to<br>&gt; which you prefer are standards specific to=
 an=20
      IMS<br>&gt; environment. The implication of the wording as proposed=
=20
      is<br>&gt; that SIP-PBXs ought to implement IMS specifications. And=
=20
      as<br>&gt; Hadriel points out, implementing those IMS=20
      specifications<br>&gt; does not eliminate the problems that the SIPco=
nnect=20
      people<br>&gt; are trying to solve. I believe the existing text in=20
      draft-03<br>&gt; is sufficient.<br>&gt;<br>&gt;<br>&gt; =A0 =A0=20
      =A0 John<br>&gt;<br>&gt; =A0 =A0 =A0 &gt; -----Original=20
      Message-----<br>&gt; =A0 =A0 =A0 &gt; From: Hans Erik van Elburg=20
      [mailto:<a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">=
ietf.hanserik@gmail.com</a>]<br>&gt;<br>&gt;=20
      =A0 =A0 =A0 &gt; Sent: 26 March 2010 23:03<br>&gt; =A0 =A0=20
      =A0 &gt; To: Elwell, John<br>&gt; =A0 =A0 =A0 &gt; Cc: <a href=3D"mai=
lto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><br>&gt; =A0 =
=A0=20
      =A0 &gt; Subject: Re: [martini] #21: 3.2.2 describes an issue<br>&gt;=
=20
      with some PBX<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; I will not argue with you about the validity of that=20
      argument.<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
      &gt; Can you agree to the modified text?<br>&gt; =A0 =A0 =A0=20
      &gt;<br>&gt; =A0 =A0 =A0 &gt; &quot;Request-URI vs. loose-route=20
      acceptance<br>&gt; =A0 =A0 =A0 &gt; Some IP-PBX do not implement=20
      international standards or SIP<br>&gt; =A0 =A0 =A0 &gt; profiles=20
      for SIP trunking. As a consequence some SIP-PBXs<br>&gt; =A0 =A0=20
      =A0 &gt; expect that inbound SIP requests from the SSP will have=20
      the<br>&gt; =A0 =A0 =A0 &gt; registered Contact-URI in the=20
      Request-URI, and thus not<br>&gt; =A0 =A0 =A0 &gt; interoperate=20
      with the loose-route scheme of 3GPP and ETSI.<br>&gt; =A0 =A0 =A0=20
      &gt; Other SIP-PBXs are fine with the Request-URI being the<br>&gt; =
=A0=20
      =A0 =A0 &gt; intended target, but cannot handle receiving a Route=20
      header<br>&gt; =A0 =A0 =A0 &gt; field identifying their=20
      registered Contact-URI as a<br>&gt; =A0 =A0 =A0 &gt; loose-route=20
      entry.&quot;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
      &gt; BR,<br>&gt; =A0 =A0 =A0 &gt; /Hans Erik van Elburg<br>&gt;=20
      =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0=20
      =A0 =A0 &gt; On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John<br>&gt;=20
      =A0 =A0 =A0 &gt; &lt;<a href=3D"mailto:john.elwell@siemens-enterprise=
.com" target=3D"_blank">john.elwell@siemens-enterprise.com</a>&gt;=20
      wrote:<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
      &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 The IETF does=20
      not have a mechanism, and that is the<br>&gt; =A0 =A0 =A0 &gt;=20
      reason for the MARTINI work. In particular, the IETF has not<br>&gt;=
=20
      =A0 =A0 =A0 &gt; published the so-called loose-route mechanism.=20
      Hence the<br>&gt; =A0 =A0 =A0 &gt; reason for the IETF, as owner=20
      of SIP, to publish a mechanism<br>&gt; =A0 =A0 =A0 &gt; for bulk=20
      registrations.<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 John<br>&gt; =A0 =A0 =A0=20
      &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; -----Original Message-----<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt; From: Hans Erik van Elburg<br>&gt;=20
      [mailto:<a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">=
ietf.hanserik@gmail.com</a>]<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; Sent: 26 March 2010=20
      02:21<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; To: <a href=3D"mailto=
:trac@localhost.amsl.com" target=3D"_blank">trac@localhost.amsl.com</a><br>=
&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; Cc: Elwell, John; <a href=3D"mailto=
:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><br>&gt; =A0 =A0=
=20
      =A0 &gt; =A0 =A0 =A0 &gt; Subject: Re: [martini] #21: 3.2.2=20
      describes an issue<br>&gt; =A0 =A0 =A0 &gt; with some PBX<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; Then you should rephrase to what the real issue=20
      is:<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; &quot;<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; Request-URI vs. loose-route acceptance<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; Some IP-PBX do not implement=20
      international<br>&gt; standards or SIP<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; profiles for SIP trunking. As a=20
      consequence<br>&gt; some SIP-PBXs<br>&gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 &gt; expect that inbound SIP requests from the SSP<br>&gt;=20
      will have the<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
      registered Contact-URI in the Request-URI,<br>&gt; and thus not<br>&g=
t;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; interoperate with the=20
      loose-route scheme of<br>&gt; 3GPP and ETSI.<br>&gt; =A0 =A0 =A0=20
      &gt; =A0 =A0 =A0 &gt; Other SIP-PBXs are fine with the=20
      Request-URI being the<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt; intended target, but cannot handle receiving<br>&gt; a Route=
=20
      header<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; field=20
      identifying their registered Contact-URI as a<br>&gt; =A0 =A0 =A0=20
      &gt; =A0 =A0 =A0 &gt; loose-route entry.&quot;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt; Is this an issue, yes. Does introducing yet another<br>&gt;=
=20
      =A0 =A0 =A0 &gt; profile help? No.<br>&gt; =A0 =A0 =A0=20
      &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 &gt; /Hans Erik van Elburg<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; On=20
      Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker<br>&gt; =A0 =A0=
=20
      =A0 &gt; =A0 =A0 =A0 &gt; &lt;<a href=3D"mailto:trac@tools.ietf.org" =
target=3D"_blank">trac@tools.ietf.org</a>&gt;=20
      wrote:<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 #21: 3.2.2=20
      describes an issue with some PBX<br>&gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      &gt;<br>&gt;=20
      -------------------------------------+------------------------<br>&gt=
;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; --------------<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      =A0Reporter: =A0ietf.hanserik@...<br>&gt; | =A0 =A0 =A0=20
      =A0Owner:<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 =A0 =A0 Type: =A0defect =A0 =A0 =A0 =A0=20
      =A0 =A0 =A0 =A0 =A0 |<br>&gt; =A0 =A0 =A0 &gt;=20
      Status: =A0closed<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 =A0Priority: =A0minor =A0 =A0 =A0=20
      =A0 =A0 =A0 =A0 =A0 =A0 =A0|<br>&gt; =A0 =A0=20
      =A0 &gt; Milestone: =A0milestone1<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 Component: =A0reqs=20
      =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=20
      |<br>&gt; =A0 =A0 =A0 &gt; Version: =A01.0<br>&gt; =A0=20
      =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
      &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Severity:=20
      =A0In WG Last Call =A0 =A0 =A0 =A0 =A0|<br>&gt; =A0=20
      =A0 =A0 &gt; Resolution: =A0invalid<br>&gt; =A0 =A0 =A0=20
      &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Keywords: =A0=20
      =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=20
      =A0 =A0 |<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt;=20
      -------------------------------------+------------------------<br>&gt=
;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; --------------<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      Changes (by john.elwell@...):<br>&gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      &gt; =A0 =A0 =A0 =A0* status: =A0new =3D&gt; closed<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      =A0* resolution: =A0=3D&gt; invalid<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 Comment:<br>&gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 =A0The text of 3.2.2 just underlines the<br>&gt; fact=20
      that there<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; are=20
      different<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 =A0implementations around. A PBX that<br>&gt;=20
      expects the loose<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
      &gt; route mechanism to be<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 =A0used would fail to interwork with=20
      SSPs using a<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
      different mechanism (e.g.,<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 =A0SIPconnect 1.0), and a PBX=20
      not<br>&gt; expecting the loose<br>&gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 &gt; route mechanism to be<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0used would fail to=20
      interwork with a loose route<br>&gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 &gt; implementation (e.g.,<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0ETSI/3GPP). Hence the=20
      urgent need for<br>&gt; a standard.<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 --<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 Ticket URL:<br>&gt; =A0=20
      =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
      &gt;<br>&gt; &lt;<a href=3D"http://trac.tools.ietf.org/wg/martini/tra=
c/ticket/21#comment:1" target=3D"_blank">http://trac.tools.ietf.org/wg/mart=
ini/trac/ticket/21#comment:1</a>&gt;<br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 martini &lt;<a href=3D"http://t=
ools.ietf.org/martini/" target=3D"_blank">http://tools.ietf.org/martini/</a=
>&gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0=20
      _______________________________________________<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 martini mailing=20
      list<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0=20
      =A0 =A0 <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini=
@ietf.org</a><br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 <a href=3D"https://www.ietf.org=
/mailman/listinfo/martini" target=3D"_blank">https://www.ietf.org/mailman/l=
istinfo/martini</a><br>&gt;=20
      =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
      =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
      =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
      =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
      &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt;<br>&gt;<br>&gt;=20
    </div></div></blockquote></div><br></blockquote></blockquote></div></di=
v></div>
</blockquote></div><br>
<br>_______________________________________________<br>
martini mailing list<br>
<a href=3D"mailto:martini@ietf.org">martini@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/martini" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/martini</a><br>
<br></blockquote></div><br>

--00c09f7d633e4087f5048317d154--

From keith.drage@alcatel-lucent.com  Wed Mar 31 05:33:19 2010
Return-Path: <keith.drage@alcatel-lucent.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 47A1B3A67B1 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 05:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.046
X-Spam-Level: 
X-Spam-Status: No, score=-4.046 tagged_above=-999 required=5 tests=[AWL=1.072,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, HTML_MESSAGE=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 5yIWVS-EYL8b for <martini@core3.amsl.com>; Wed, 31 Mar 2010 05:33:17 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by core3.amsl.com (Postfix) with ESMTP id 45B543A677C for <martini@ietf.org>; Wed, 31 Mar 2010 05:33:15 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o2VBnKYE020047 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 31 Mar 2010 14:33:38 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Wed, 31 Mar 2010 14:32:52 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>, "martini@ietf.org" <martini@ietf.org>
Date: Wed, 31 Mar 2010 14:32:51 +0200
Thread-Topic: [martini] Need for a SIP/SDP profile for SIP trunking ,	was Re: 	#21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrQzR503WVZ3VCqQO6ZfYYB/kWU5gAAQv5g
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE20D1C8293@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <w2v9ae56b1e1003310428o6fc07243j294b603eec953a1a@mail.gmail.com> <m2k9ae56b1e1003310523zc70f6a83ub0e5b1bdaeddd5ce@mail.gmail.com>
In-Reply-To: <m2k9ae56b1e1003310523zc70f6a83ub0e5b1bdaeddd5ce@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_EDC0A1AE77C57744B664A310A0B23AE20D1C8293FRMRSSXCHMBSC3d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re: 	#21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 12:33:19 -0000

--_000_EDC0A1AE77C57744B664A310A0B23AE20D1C8293FRMRSSXCHMBSC3d_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The problem is that I suspect noone is going to agree what that profile is =
to be sufficiently useful.

regards

Keith

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Hans Erik van Elburg
Sent: Wednesday, March 31, 2010 1:24 PM
To: martini@ietf.org
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re=
: #21: 3.2.2 describes an issue with some PBX

I should have said "explicit indication" instead of "option tag". Feature t=
ags maybe more appropriate, when talking about a profile.

/Hans Erik van Elburg


On Wed, Mar 31, 2010 at 1:28 PM, Hans Erik van Elburg <ietf.hanserik@gmail.=
com<mailto:ietf.hanserik@gmail.com>> wrote:
Yes, I agree with that observation.

Only solving the routing issue does not solve the overall problem. For that=
 a minimum SIP/SDP profile needs to be agreed upon. Also what are common de=
nominator as codec for voice, fax, dtmf etc.

The question rises if there should be an option tag to signal support for a=
 profile instead of only signalling what routing method is preferred.

BR,
/Hans Erik van Elburg


On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, Keith (Keith) <keith.drage@alcatel-=
lucent.com<mailto:keith.drage@alcatel-lucent.com>> wrote:
So assuming that this text is accepted, I guess the key argument of providi=
ng this distinction is not that both behaviours are non-standard, but that =
some means is needed to distinguish the two.

While I do not have a problem with that specifically, I still have an issue=
 that providing some signalling to do this solves all the issues. There are=
 all sorts of other issues associated with what the PBX "expects" that also=
 cause all sorts of issues, such as whether it expects a tel URI in tel URI=
 format or SIP URI format, and so on, that are not signalled.

Therefore at the end of the day, one is still going to end up with configur=
ation information at either end of this interface that is not explicitly si=
gnalled, and in the absence of both sides having preconfigured knowledge of=
 that information, the interface is not going to work.

regards

Keith

________________________________
From: martini-bounces@ietf.org<mailto:martini-bounces@ietf.org> [mailto:mar=
tini-bounces@ietf.org<mailto:martini-bounces@ietf.org>] On Behalf Of Elwell=
, John
Sent: Tuesday, March 30, 2010 6:11 PM
To: Hans Erik van Elburg

Cc: martini@ietf.org<mailto:martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

OK, fixed in my working copy.

John

________________________________
From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto:ietf.hans=
erik@gmail.com>]
Sent: 30 March 2010 11:49
To: Elwell, John
Cc: martini@ietf.org<mailto:martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

Hi John,

Inline...

/Hans Erik van Elburg

On Mon, Mar 29, 2010 at 9:55 PM, Elwell, John <john.elwell@siemens-enterpri=
se.com<mailto:john.elwell@siemens-enterprise.com>> wrote:
Hans Erik,

I think the point you are trying to make is that it is not one-sided. The f=
act is, each side has different ways of working, and you need to have the t=
wo sides operating in compatible manners for it to work. In practice, I thi=
nk there are other variants, besides the two cited in the present 3.2.2.
Yes. And there is no objective way to automatically determine what variant =
the PBX or the SSP is supporting. Which is what an options tag could resolv=
e.

I would suggest:

       <t>Even where all information needed by the SIP-PBX is provided, in =
some deployments inbound SIP requests from the SSP have the registered Cont=
act URI in the Request-URI, whereas in other deployments inbound SIP reques=
ts have the intended target (AOR) in the Request-URI and the Contact URI in=
 the Route header field. There are other variants too. Interoperability pro=
blems arise when a PBX designed for or configured for one variant attempts =
to interwork with an SSP designed for or configured for another variant.</t=
>
Yes, slightly modified to add the objective means issue:
 <t>Even where all information needed by the SIP-PBX is provided, in some d=
eployments inbound SIP requests from the SSP have the registered PBX Contac=
t URI in the Request-URI, whereas in other deployments inbound SIP requests=
 have the intended target PBX user (AOR) in the Request-URI and the Contact=
 URI in the Route header field. There are other variants too. Interoperabil=
ity problems arise when a PBX designed for or configured for one variant at=
tempts to interwork with an SSP designed for or configured for another vari=
ant. There is currently no objective means in the signalling during registr=
ation for either party to discover what mechanism the other side supports.<=
/t>

To accompany this, I think the title of the section should be changed too: =
"Inconsistent placement of information in inbound requests"

Yes, slightly modified to make it more specific: "Inconsistent placement of=
 target URI information in inbound requests".

John

> -----Original Message-----
> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto:ietf.ha=
nserik@gmail.com>]
> Sent: 29 March 2010 17:27
> To: Elwell, John
> Cc: martini@ietf.org<mailto:martini@ietf.org>
> Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>
> Hi John,
>
> I was just trying to find a text that describes the issue.
>
> But now the issue reads like "some PBX like apples, some like
> bananas". To me that does not sound like a usefull issue to
> describe in an RFC.
>
> So I think one or two more sentence would make clear why this
> is an issue.
>
> I think there is multiple underlying issues here:
> - PBX have different SIP profiles or all SIP-PBX are different
> - PBX support SIP trunking flavour A, or support SIP trunking
> flavour B
> - SSP systems don't know what mechanism the PBX support (can
> be resolved with explicit indicator, this draft proposes an
> indicator for flavour B but for another purpose it seems)
> - PBX do not know what SIP trunking flavour the SSP supports
> (not addressed it seems)
>
> I don't seem to have a lucky hand with proposing an improved
> text, so maybe you should have a go at it.
>
> BR,
> /Hans Erik van Elburg
>
> p.s. I never said or implied that a SIP-PBX shall implement
> IMS. But it would be really, really, really good if they
> would interwork on the UNI with the IMS business trunking.  I
> think that should also be in your interest and in fact you
> have been part of that work...
>
>
>
> On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John
> <john.elwell@siemens-enterprise.com<mailto:john.elwell@siemens-enterprise=
.com>> wrote:
>
>
>       Hans Erik,
>
>       As an individual, I disagree with the proposed text,
> since it is misleading. The "international standards" to
> which you prefer are standards specific to an IMS
> environment. The implication of the wording as proposed is
> that SIP-PBXs ought to implement IMS specifications. And as
> Hadriel points out, implementing those IMS specifications
> does not eliminate the problems that the SIPconnect people
> are trying to solve. I believe the existing text in draft-03
> is sufficient.
>
>
>       John
>
>       > -----Original Message-----
>       > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto=
:ietf.hanserik@gmail.com>]
>
>       > Sent: 26 March 2010 23:03
>       > To: Elwell, John
>       > Cc: martini@ietf.org<mailto:martini@ietf.org>
>       > Subject: Re: [martini] #21: 3.2.2 describes an issue
> with some PBX
>       >
>       > I will not argue with you about the validity of that argument.
>       >
>       > Can you agree to the modified text?
>       >
>       > "Request-URI vs. loose-route acceptance
>       > Some IP-PBX do not implement international standards or SIP
>       > profiles for SIP trunking. As a consequence some SIP-PBXs
>       > expect that inbound SIP requests from the SSP will have the
>       > registered Contact-URI in the Request-URI, and thus not
>       > interoperate with the loose-route scheme of 3GPP and ETSI.
>       > Other SIP-PBXs are fine with the Request-URI being the
>       > intended target, but cannot handle receiving a Route header
>       > field identifying their registered Contact-URI as a
>       > loose-route entry."
>       >
>       > BR,
>       > /Hans Erik van Elburg
>       >
>       >
>       > On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
>       > <john.elwell@siemens-enterprise.com<mailto:john.elwell@siemens-en=
terprise.com>> wrote:
>       >
>       >
>       >       The IETF does not have a mechanism, and that is the
>       > reason for the MARTINI work. In particular, the IETF has not
>       > published the so-called loose-route mechanism. Hence the
>       > reason for the IETF, as owner of SIP, to publish a mechanism
>       > for bulk registrations.
>       >
>       >       John
>       >
>       >
>       >       > -----Original Message-----
>       >       > From: Hans Erik van Elburg
> [mailto:ietf.hanserik@gmail.com<mailto:ietf.hanserik@gmail.com>]
>       >       > Sent: 26 March 2010 02:21
>       >       > To: trac@localhost.amsl.com<mailto:trac@localhost.amsl.co=
m>
>       >       > Cc: Elwell, John; martini@ietf.org<mailto:martini@ietf.or=
g>
>       >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
>       > with some PBX
>       >       >
>       >       >
>       >       > Then you should rephrase to what the real issue is:
>       >       > "
>       >       >
>       >       >
>       >       > Request-URI vs. loose-route acceptance
>       >       >
>       >       >
>       >       > Some IP-PBX do not implement international
> standards or SIP
>       >       > profiles for SIP trunking. As a consequence
> some SIP-PBXs
>       >       > expect that inbound SIP requests from the SSP
> will have the
>       >       > registered Contact-URI in the Request-URI,
> and thus not
>       >       > interoperate with the loose-route scheme of
> 3GPP and ETSI.
>       >       > Other SIP-PBXs are fine with the Request-URI being the
>       >       > intended target, but cannot handle receiving
> a Route header
>       >       > field identifying their registered Contact-URI as a
>       >       > loose-route entry."
>       >       >
>       >       >
>       >       > Is this an issue, yes. Does introducing yet another
>       > profile help? No.
>       >       >
>       >       > /Hans Erik van Elburg
>       >       >
>       >       >
>       >       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
>       >       > <trac@tools.ietf.org<mailto:trac@tools.ietf.org>> wrote:
>       >       >
>       >       >
>       >       >       #21: 3.2.2 describes an issue with some PBX
>       >       >
>       >       >
> -------------------------------------+------------------------
>       >       > --------------
>       >       >        Reporter:  ietf.hanserik@...
> |        Owner:
>       >       >
>       >       >           Type:  defect                   |
>       > Status:  closed
>       >       >
>       >       >        Priority:  minor                    |
>       > Milestone:  milestone1
>       >       >       Component:  reqs                     |
>       > Version:  1.0
>       >       >
>       >       >        Severity:  In WG Last Call          |
>       > Resolution:  invalid
>       >       >        Keywords:                           |
>       >       >
>       >       >
> -------------------------------------+------------------------
>       >       > --------------
>       >       >       Changes (by john.elwell@...):
>       >       >
>       >       >        * status:  new =3D> closed
>       >       >        * resolution:  =3D> invalid
>       >       >
>       >       >
>       >       >       Comment:
>       >       >
>       >       >
>       >       >        The text of 3.2.2 just underlines the
> fact that there
>       >       > are different
>       >       >        implementations around. A PBX that
> expects the loose
>       >       > route mechanism to be
>       >       >        used would fail to interwork with SSPs using a
>       >       > different mechanism (e.g.,
>       >       >        SIPconnect 1.0), and a PBX not
> expecting the loose
>       >       > route mechanism to be
>       >       >        used would fail to interwork with a loose route
>       >       > implementation (e.g.,
>       >       >        ETSI/3GPP). Hence the urgent need for
> a standard.
>       >       >
>       >       >       --
>       >       >       Ticket URL:
>       >       >
>       >
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
>       >       >
>       >       >       martini <http://tools.ietf.org/martini/>
>       >       >
>       >       >
>       >       >       _______________________________________________
>       >       >       martini mailing list
>       >       >       martini@ietf.org<mailto:martini@ietf.org>
>       >       >       https://www.ietf.org/mailman/listinfo/martini
>       >       >
>       >       >
>       >       >
>       >       >
>       >
>       >
>       >
>
>
>



_______________________________________________
martini mailing list
martini@ietf.org<mailto:martini@ietf.org>
https://www.ietf.org/mailman/listinfo/martini



--_000_EDC0A1AE77C57744B664A310A0B23AE20D1C8293FRMRSSXCHMBSC3d_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D802023212-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>The problem is that I suspect noone is going to ag=
ree what=20
that profile is to be sufficiently useful.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D802023212-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D802023212-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>regards</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D802023212-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D802023212-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Keith</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> martini-bounces@ietf.org=20
  [mailto:martini-bounces@ietf.org] <B>On Behalf Of </B>Hans Erik van=20
  Elburg<BR><B>Sent:</B> Wednesday, March 31, 2010 1:24 PM<BR><B>To:</B>=20
  martini@ietf.org<BR><B>Subject:</B> Re: [martini] Need for a SIP/SDP prof=
ile=20
  for SIP trunking , was Re: #21: 3.2.2 describes an issue with some=20
  PBX<BR></FONT><BR></DIV>
  <DIV></DIV>I should have said "explicit indication" instead of "option ta=
g".=20
  Feature tags maybe more appropriate, when talking about a profile.<BR><BR=
=20
  clear=3Dall>/Hans Erik van Elburg<BR><BR><BR>
  <DIV class=3Dgmail_quote>On Wed, Mar 31, 2010 at 1:28 PM, Hans Erik van E=
lburg=20
  <SPAN dir=3Dltr>&lt;<A=20
  href=3D"mailto:ietf.hanserik@gmail.com">ietf.hanserik@gmail.com</A>&gt;</=
SPAN>=20
  wrote:<BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(2=
04,204,204) 1px solid">Yes,=20
    I agree with that observation.<BR><BR>Only solving the routing issue do=
es=20
    not solve the overall problem. For that a minimum SIP/SDP profile needs=
 to=20
    be agreed upon. Also what are common denominator as codec for voice, fa=
x,=20
    dtmf etc. <BR><BR>The question rises if there should be an option tag t=
o=20
    signal support for a profile instead of only signalling what routing me=
thod=20
    is preferred.<BR><BR>BR,<BR clear=3Dall>/Hans Erik van Elburg<BR><BR><B=
R>
    <DIV class=3Dgmail_quote>On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, Keith =
(Keith)=20
    <SPAN dir=3Dltr>&lt;<A href=3D"mailto:keith.drage@alcatel-lucent.com"=20
    target=3D_blank>keith.drage@alcatel-lucent.com</A>&gt;</SPAN> wrote:<BR=
>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb=
(204,204,204) 1px solid">
      <DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff =
size=3D2>So=20
      assuming that this text is accepted, I guess the key argument of prov=
iding=20
      this distinction is not that both behaviours are non-standard, but th=
at=20
      some means is needed to distinguish the two.</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=
=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff =
size=3D2>While=20
      I do not have a problem with that specifically, I still have an issue=
 that=20
      providing some signalling to do this solves all the issues. There are=
 all=20
      sorts of other issues associated with what the PBX "expects" that als=
o=20
      cause all sorts of issues, such as whether it expects a tel URI in te=
l URI=20
      format or SIP URI format, and so on, that are not signalled.=20
      </FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=
=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=
=20
      size=3D2>Therefore at the end of the day, one is still going to end u=
p with=20
      configuration information at either end of this interface that is not=
=20
      explicitly signalled, and in the absence of both sides having=20
      preconfigured knowledge of that information, the interface is not goi=
ng to=20
      work.</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=
=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=
=20
      size=3D2>regards</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=
=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=
=20
      size=3D2>Keith</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=
=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft>
      <HR>
      </DIV>
      <DIV dir=3Dltr align=3Dleft><FONT face=3DTahoma size=3D2><B>From:</B>=
 <A=20
      href=3D"mailto:martini-bounces@ietf.org"=20
      target=3D_blank>martini-bounces@ietf.org</A> [mailto:<A=20
      href=3D"mailto:martini-bounces@ietf.org"=20
      target=3D_blank>martini-bounces@ietf.org</A>] <B>On Behalf Of </B>Elw=
ell,=20
      John<BR><B>Sent:</B> Tuesday, March 30, 2010 6:11 PM<BR><B>To:</B> Ha=
ns=20
      Erik van Elburg
      <DIV>
      <DIV></DIV>
      <DIV><BR><B>Cc:</B> <A href=3D"mailto:martini@ietf.org"=20
      target=3D_blank>martini@ietf.org</A><BR><B>Subject:</B> Re: [martini]=
 #21:=20
      3.2.2 describes an issue with some PBX<BR></DIV></DIV></FONT><BR></DI=
V>
      <DIV>
      <DIV></DIV>
      <DIV>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,0,25=
5) 2px solid; MARGIN-RIGHT: 0px">
        <DIV></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000f=
f size=3D2>OK,=20
        fixed in my working copy.</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000f=
f=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000f=
f=20
        size=3D2>John</FONT></SPAN></DIV><BR>
        <BLOCKQUOTE=20
        style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,0,=
255) 2px solid; MARGIN-RIGHT: 0px">
          <DIV lang=3Den-us dir=3Dltr align=3Dleft>
          <HR>
          <FONT face=3DTahoma size=3D2><B>From:</B> Hans Erik van Elburg [m=
ailto:<A=20
          href=3D"mailto:ietf.hanserik@gmail.com"=20
          target=3D_blank>ietf.hanserik@gmail.com</A>] <BR><B>Sent:</B> 30 =
March=20
          2010 11:49<BR><B>To:</B> Elwell, John<BR><B>Cc:</B> <A=20
          href=3D"mailto:martini@ietf.org"=20
          target=3D_blank>martini@ietf.org</A><BR><B>Subject:</B> Re: [mart=
ini]=20
          #21: 3.2.2 describes an issue with some PBX<BR></FONT><BR></DIV>
          <DIV></DIV>Hi John,<BR><BR>Inline... <BR clear=3Dall><BR>/Hans Er=
ik van=20
          Elburg<BR><BR>
          <DIV class=3Dgmail_quote>On Mon, Mar 29, 2010 at 9:55 PM, Elwell,=
 John=20
          <SPAN dir=3Dltr>&lt;<A href=3D"mailto:john.elwell@siemens-enterpr=
ise.com"=20
          target=3D_blank>john.elwell@siemens-enterprise.com</A>&gt;</SPAN>=
=20
          wrote:<BR>
          <BLOCKQUOTE class=3Dgmail_quote=20
          style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEF=
T: rgb(204,204,204) 1px solid">Hans=20
            Erik,<BR><BR>I think the point you are trying to make is that i=
t is=20
            not one-sided. The fact is, each side has different ways of wor=
king,=20
            and you need to have the two sides operating in compatible mann=
ers=20
            for it to work. In practice, I think there are other variants,=
=20
            besides the two cited in the present 3.2.2.</BLOCKQUOTE>
          <DIV>Yes. And there is no objective way to automatically determin=
e=20
          what variant the PBX or the SSP is supporting. Which is what an=20
          options tag could resolve.<BR>&nbsp;</DIV>
          <BLOCKQUOTE class=3Dgmail_quote=20
          style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEF=
T: rgb(204,204,204) 1px solid">I=20
            would suggest:<BR><BR>&nbsp; &nbsp; &nbsp; &nbsp;&lt;t&gt;Even =
where=20
            all information needed by the SIP-PBX is provided, in some=20
            deployments inbound SIP requests from the SSP have the register=
ed=20
            Contact URI in the Request-URI, whereas in other deployments in=
bound=20
            SIP requests have the intended target (AOR) in the Request-URI =
and=20
            the Contact URI in the Route header field. There are other vari=
ants=20
            too. Interoperability problems arise when a PBX designed for or=
=20
            configured for one variant attempts to interwork with an SSP=20
            designed for or configured for another=20
          variant.&lt;/t&gt;<BR></BLOCKQUOTE>
          <DIV>Yes, slightly modified to add the objective means=20
          issue:<BR>&nbsp;&lt;t&gt;Even where all information needed by the=
=20
          SIP-PBX is provided, in some deployments inbound SIP requests fro=
m the=20
          SSP have the registered PBX Contact URI in the Request-URI, where=
as in=20
          other deployments inbound SIP requests have the intended target P=
BX=20
          user (AOR) in the Request-URI and the Contact URI in the Route he=
ader=20
          field. There are other variants too. Interoperability problems ar=
ise=20
          when a PBX designed for or configured for one variant attempts to=
=20
          interwork with an SSP designed for or configured for another vari=
ant.=20
          There is currently no objective means in the signalling during=20
          registration for either party to discover what mechanism the othe=
r=20
          side supports.&lt;/t&gt;<BR>&nbsp;</DIV>
          <BLOCKQUOTE class=3Dgmail_quote=20
          style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEF=
T: rgb(204,204,204) 1px solid">To=20
            accompany this, I think the title of the section should be chan=
ged=20
            too: "Inconsistent placement of information in inbound requests=
"<BR>
            <DIV><BR></DIV></BLOCKQUOTE>
          <DIV>Yes, slightly modified to make it more specific: "Inconsiste=
nt=20
          placement of target URI information in inbound=20
          requests".<BR>&nbsp;</DIV>
          <BLOCKQUOTE class=3Dgmail_quote=20
          style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEF=
T: rgb(204,204,204) 1px solid">
            <DIV>John<BR><BR>&gt; -----Original Message-----<BR>&gt; From: =
Hans=20
            Erik van Elburg [mailto:<A href=3D"mailto:ietf.hanserik@gmail.c=
om"=20
            target=3D_blank>ietf.hanserik@gmail.com</A>]<BR></DIV>
            <DIV>
            <DIV></DIV>
            <DIV>&gt; Sent: 29 March 2010 17:27<BR>&gt; To: Elwell, John<BR=
>&gt;=20
            Cc: <A href=3D"mailto:martini@ietf.org"=20
            target=3D_blank>martini@ietf.org</A><BR>&gt; Subject: Re: [mart=
ini]=20
            #21: 3.2.2 describes an issue with some PBX<BR>&gt;<BR>&gt; Hi=
=20
            John,<BR>&gt;<BR>&gt; I was just trying to find a text that=20
            describes the issue.<BR>&gt;<BR>&gt; But now the issue reads li=
ke=20
            "some PBX like apples, some like<BR>&gt; bananas". To me that d=
oes=20
            not sound like a usefull issue to<BR>&gt; describe in an=20
            RFC.<BR>&gt;<BR>&gt; So I think one or two more sentence would =
make=20
            clear why this<BR>&gt; is an issue.<BR>&gt;<BR>&gt; I think the=
re is=20
            multiple underlying issues here:<BR>&gt; - PBX have different S=
IP=20
            profiles or all SIP-PBX are different<BR>&gt; - PBX support SIP=
=20
            trunking flavour A, or support SIP trunking<BR>&gt; flavour=20
            B<BR>&gt; - SSP systems don't know what mechanism the PBX suppo=
rt=20
            (can<BR>&gt; be resolved with explicit indicator, this draft=20
            proposes an<BR>&gt; indicator for flavour B but for another pur=
pose=20
            it seems)<BR>&gt; - PBX do not know what SIP trunking flavour t=
he=20
            SSP supports<BR>&gt; (not addressed it seems)<BR>&gt;<BR>&gt; I=
=20
            don't seem to have a lucky hand with proposing an improved<BR>&=
gt;=20
            text, so maybe you should have a go at it.<BR>&gt;<BR>&gt;=20
            BR,<BR>&gt; /Hans Erik van Elburg<BR>&gt;<BR>&gt; p.s. I never =
said=20
            or implied that a SIP-PBX shall implement<BR>&gt; IMS. But it w=
ould=20
            be really, really, really good if they<BR>&gt; would interwork =
on=20
            the UNI with the IMS business trunking. &nbsp;I<BR>&gt; think t=
hat=20
            should also be in your interest and in fact you<BR>&gt; have be=
en=20
            part of that work...<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; On Mon, Ma=
r 29,=20
            2010 at 5:56 PM, Elwell, John<BR>&gt; &lt;<A=20
            href=3D"mailto:john.elwell@siemens-enterprise.com"=20
            target=3D_blank>john.elwell@siemens-enterprise.com</A>&gt;=20
            wrote:<BR>&gt;<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; Hans=20
            Erik,<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; As an individual, I=
=20
            disagree with the proposed text,<BR>&gt; since it is misleading=
. The=20
            "international standards" to<BR>&gt; which you prefer are stand=
ards=20
            specific to an IMS<BR>&gt; environment. The implication of the=
=20
            wording as proposed is<BR>&gt; that SIP-PBXs ought to implement=
 IMS=20
            specifications. And as<BR>&gt; Hadriel points out, implementing=
=20
            those IMS specifications<BR>&gt; does not eliminate the problem=
s=20
            that the SIPconnect people<BR>&gt; are trying to solve. I belie=
ve=20
            the existing text in draft-03<BR>&gt; is=20
            sufficient.<BR>&gt;<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp;=20
            John<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; -----Original=20
            Message-----<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; From: Hans Erik =
van=20
            Elburg [mailto:<A href=3D"mailto:ietf.hanserik@gmail.com"=20
            target=3D_blank>ietf.hanserik@gmail.com</A>]<BR>&gt;<BR>&gt; &n=
bsp;=20
            &nbsp; &nbsp; &gt; Sent: 26 March 2010 23:03<BR>&gt; &nbsp; &nb=
sp;=20
            &nbsp; &gt; To: Elwell, John<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; =
Cc:=20
            <A href=3D"mailto:martini@ietf.org"=20
            target=3D_blank>martini@ietf.org</A><BR>&gt; &nbsp; &nbsp; &nbs=
p; &gt;=20
            Subject: Re: [martini] #21: 3.2.2 describes an issue<BR>&gt; wi=
th=20
            some PBX<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp=
;=20
            &nbsp; &gt; I will not argue with you about the validity of tha=
t=20
            argument.<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbs=
p;=20
            &nbsp; &gt; Can you agree to the modified text?<BR>&gt; &nbsp;=
=20
            &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; "Request-U=
RI=20
            vs. loose-route acceptance<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; So=
me=20
            IP-PBX do not implement international standards or SIP<BR>&gt;=
=20
            &nbsp; &nbsp; &nbsp; &gt; profiles for SIP trunking. As a=20
            consequence some SIP-PBXs<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; exp=
ect=20
            that inbound SIP requests from the SSP will have the<BR>&gt; &n=
bsp;=20
            &nbsp; &nbsp; &gt; registered Contact-URI in the Request-URI, a=
nd=20
            thus not<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; interoperate with th=
e=20
            loose-route scheme of 3GPP and ETSI.<BR>&gt; &nbsp; &nbsp; &nbs=
p;=20
            &gt; Other SIP-PBXs are fine with the Request-URI being the<BR>=
&gt;=20
            &nbsp; &nbsp; &nbsp; &gt; intended target, but cannot handle=20
            receiving a Route header<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; fiel=
d=20
            identifying their registered Contact-URI as a<BR>&gt; &nbsp; &n=
bsp;=20
            &nbsp; &gt; loose-route entry."<BR>&gt; &nbsp; &nbsp; &nbsp;=20
            &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; BR,<BR>&gt; &nbsp; &nbsp=
;=20
            &nbsp; &gt; /Hans Erik van Elburg<BR>&gt; &nbsp; &nbsp; &nbsp;=
=20
            &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &n=
bsp;=20
            &gt; On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John<BR>&gt; &nbs=
p;=20
            &nbsp; &nbsp; &gt; &lt;<A=20
            href=3D"mailto:john.elwell@siemens-enterprise.com"=20
            target=3D_blank>john.elwell@siemens-enterprise.com</A>&gt;=20
            wrote:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp;=
=20
            &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nb=
sp;=20
            The IETF does not have a mechanism, and that is the<BR>&gt; &nb=
sp;=20
            &nbsp; &nbsp; &gt; reason for the MARTINI work. In particular, =
the=20
            IETF has not<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; published the=20
            so-called loose-route mechanism. Hence the<BR>&gt; &nbsp; &nbsp=
;=20
            &nbsp; &gt; reason for the IETF, as owner of SIP, to publish a=
=20
            mechanism<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; for bulk=20
            registrations.<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp;=
=20
            &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; John<BR>&gt; &nbsp; &nb=
sp;=20
            &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &n=
bsp;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; -----Original=20
            Message-----<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &n=
bsp;=20
            &gt; From: Hans Erik van Elburg<BR>&gt; [mailto:<A=20
            href=3D"mailto:ietf.hanserik@gmail.com"=20
            target=3D_blank>ietf.hanserik@gmail.com</A>]<BR>&gt; &nbsp; &nb=
sp;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Sent: 26 March 2010=20
            02:21<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
            To: <A href=3D"mailto:trac@localhost.amsl.com"=20
            target=3D_blank>trac@localhost.amsl.com</A><BR>&gt; &nbsp; &nbs=
p;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Cc: Elwell, John; <A=20
            href=3D"mailto:martini@ietf.org"=20
            target=3D_blank>martini@ietf.org</A><BR>&gt; &nbsp; &nbsp; &nbs=
p; &gt;=20
            &nbsp; &nbsp; &nbsp; &gt; Subject: Re: [martini] #21: 3.2.2=20
            describes an issue<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; with some=
=20
            PBX<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
            &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
            &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
            Then you should rephrase to what the real issue is:<BR>&gt; &nb=
sp;=20
            &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; "<BR>&gt; &nbsp; &=
nbsp;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nb=
sp;=20
            &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
            &nbsp; &nbsp; &nbsp; &gt; Request-URI vs. loose-route=20
            acceptance<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbs=
p;=20
            &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
            &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
            Some IP-PBX do not implement international<BR>&gt; standards or=
=20
            SIP<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
            profiles for SIP trunking. As a consequence<BR>&gt; some=20
            SIP-PBXs<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
 &gt;=20
            expect that inbound SIP requests from the SSP<BR>&gt; will have=
=20
            the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
            registered Contact-URI in the Request-URI,<BR>&gt; and thus=20
            not<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
            interoperate with the loose-route scheme of<BR>&gt; 3GPP and=20
            ETSI.<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
            Other SIP-PBXs are fine with the Request-URI being the<BR>&gt;=
=20
            &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; intended ta=
rget,=20
            but cannot handle receiving<BR>&gt; a Route header<BR>&gt; &nbs=
p;=20
            &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; field identifying =
their=20
            registered Contact-URI as a<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &=
nbsp;=20
            &nbsp; &nbsp; &gt; loose-route entry."<BR>&gt; &nbsp; &nbsp; &n=
bsp;=20
            &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
            &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nb=
sp;=20
            &nbsp; &nbsp; &gt; Is this an issue, yes. Does introducing yet=
=20
            another<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; profile help? No.<BR>=
&gt;=20
            &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nb=
sp;=20
            &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; /Hans Erik van=20
            Elburg<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
            &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
            &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt=
; On=20
            Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker<BR>&gt; &nb=
sp;=20
            &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &lt;<A=20
            href=3D"mailto:trac@tools.ietf.org"=20
            target=3D_blank>trac@tools.ietf.org</A>&gt; wrote:<BR>&gt; &nbs=
p;=20
            &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nb=
sp;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nb=
sp;=20
            &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; #21: 3.2.2=
=20
            describes an issue with some PBX<BR>&gt; &nbsp; &nbsp; &nbsp; &=
gt;=20
            &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nb=
sp;=20
            &nbsp; &nbsp; &gt;<BR>&gt;=20
            -------------------------------------+------------------------<=
BR>&gt;=20
            &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;=20
            --------------<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Reporter:=20
            &nbsp;ietf.hanserik@...<BR>&gt; | &nbsp; &nbsp; &nbsp;=20
            &nbsp;Owner:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &n=
bsp;=20
            &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
            &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Type: &nbsp;defect &nbsp; &n=
bsp;=20
            &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<BR>&gt; &nbs=
p;=20
            &nbsp; &nbsp; &gt; Status: &nbsp;closed<BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
            &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
            &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Priority:=
=20
            &nbsp;minor &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp;=20
            &nbsp; &nbsp;|<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Milestone:=20
            &nbsp;milestone1<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp=
;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; Component: &nbsp;reqs &nbsp; &=
nbsp;=20
            &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<BR>&g=
t;=20
            &nbsp; &nbsp; &nbsp; &gt; Version: &nbsp;1.0<BR>&gt; &nbsp; &nb=
sp;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nb=
sp;=20
            &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Sever=
ity:=20
            &nbsp;In WG Last Call &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|<BR>&g=
t;=20
            &nbsp; &nbsp; &nbsp; &gt; Resolution: &nbsp;invalid<BR>&gt; &nb=
sp;=20
            &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbs=
p;=20
            &nbsp;Keywords: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
            &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<BR>&gt; &nbsp; &nbs=
p;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nb=
sp;=20
            &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=20
            -------------------------------------+------------------------<=
BR>&gt;=20
            &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;=20
            --------------<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; Changes (by=20
            john.elwell@...):<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbs=
p;=20
            &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nb=
sp;=20
            &gt; &nbsp; &nbsp; &nbsp; &nbsp;* status: &nbsp;new =3D&gt;=20
            closed<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &=
gt;=20
            &nbsp; &nbsp; &nbsp; &nbsp;* resolution: &nbsp;=3D&gt; invalid<=
BR>&gt;=20
            &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nb=
sp;=20
            &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nb=
sp;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
            Comment:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
=20
            &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
            &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
            &nbsp; &nbsp; &nbsp; &nbsp;The text of 3.2.2 just underlines=20
            the<BR>&gt; fact that there<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &=
nbsp;=20
            &nbsp; &nbsp; &gt; are different<BR>&gt; &nbsp; &nbsp; &nbsp; &=
gt;=20
            &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;implementa=
tions=20
            around. A PBX that<BR>&gt; expects the loose<BR>&gt; &nbsp; &nb=
sp;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; route mechanism to be<BR>=
&gt;=20
            &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbs=
p;=20
            &nbsp; &nbsp;used would fail to interwork with SSPs using a<BR>=
&gt;=20
            &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; different=20
            mechanism (e.g.,<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp=
;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;SIPconnect 1.0), and a P=
BX=20
            not<BR>&gt; expecting the loose<BR>&gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
            &nbsp; &nbsp; &nbsp; &gt; route mechanism to be<BR>&gt; &nbsp;=
=20
            &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbs=
p;=20
            &nbsp;used would fail to interwork with a loose route<BR>&gt; &=
nbsp;=20
            &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; implementation=20
            (e.g.,<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &=
gt;=20
            &nbsp; &nbsp; &nbsp; &nbsp;ETSI/3GPP). Hence the urgent need=20
            for<BR>&gt; a standard.<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp=
;=20
            &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nb=
sp;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; --<BR>&gt; &nbsp; &nbsp; &nbsp=
;=20
            &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; Ticket=20
            URL:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
            &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &lt;<A=20
            href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/21#co=
mment:1"=20
            target=3D_blank>http://trac.tools.ietf.org/wg/martini/trac/tick=
et/21#comment:1</A>&gt;<BR>&gt;=20
            &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nb=
sp;=20
            &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbs=
p;=20
            martini &lt;<A href=3D"http://tools.ietf.org/martini/"=20
            target=3D_blank>http://tools.ietf.org/martini/</A>&gt;<BR>&gt; =
&nbsp;=20
            &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nb=
sp;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nb=
sp;=20
            &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
            _______________________________________________<BR>&gt; &nbsp;=
=20
            &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbs=
p;=20
            martini mailing list<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &=
nbsp;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; <A href=3D"mailto:martini@ietf=
.org"=20
            target=3D_blank>martini@ietf.org</A><BR>&gt; &nbsp; &nbsp; &nbs=
p; &gt;=20
            &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; <A=20
            href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
            target=3D_blank>https://www.ietf.org/mailman/listinfo/martini</=
A><BR>&gt;=20
            &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nb=
sp;=20
            &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nb=
sp;=20
            &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nb=
sp;=20
            &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp;=20
            &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &n=
bsp;=20
            &gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
        </DIV></DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BLOCKQUOTE></DIV>=
</DIV></DIV></BLOCKQUOTE></DIV><BR><BR>____________________________________=
___________<BR>martini=20
    mailing list<BR><A href=3D"mailto:martini@ietf.org">martini@ietf.org</A=
><BR><A=20
    href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
    target=3D_blank>https://www.ietf.org/mailman/listinfo/martini</A><BR><B=
R></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>

--_000_EDC0A1AE77C57744B664A310A0B23AE20D1C8293FRMRSSXCHMBSC3d_--

From ietf.hanserik@gmail.com  Wed Mar 31 05:48:24 2010
Return-Path: <ietf.hanserik@gmail.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 074A53A6784 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 05:48:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.524
X-Spam-Level: 
X-Spam-Status: No, score=-0.524 tagged_above=-999 required=5 tests=[AWL=0.944,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 jfkzuJR2b-HZ for <martini@core3.amsl.com>; Wed, 31 Mar 2010 05:48:21 -0700 (PDT)
Received: from mail-ew0-f224.google.com (mail-ew0-f224.google.com [209.85.219.224]) by core3.amsl.com (Postfix) with ESMTP id D2DDB3A6821 for <martini@ietf.org>; Wed, 31 Mar 2010 05:48:20 -0700 (PDT)
Received: by ewy24 with SMTP id 24so18270ewy.13 for <martini@ietf.org>; Wed, 31 Mar 2010 05:48:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=897cfRnZ50GE3a6BymZYVdqHfIN9YFyLmLLDmISLP/M=; b=L0N9kRqbXkdS2agc6BSFxzVyN70LoI8PyAxnAC0OeyHm0GXXAbXVWnFxTjvY5RX4o5 5M0R2p8dtCfUexyqhQSefObdDatdl4YfB+lsMjM0FBCVg9U6FYBJVpznLRS9wY6Hm3wL emZnSKylLnENcg0ObTg8h2LZgCGpaZppgXVtg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=rbYYe4JZO366cQhoG0aJB/FF1AIt8Y7e72lnkGZu97odCA3fDx2ppRvigXJJ8IGAyi uYAo/cL4081Nld8gPPNBvjmQRSaKSlT83m+5ndBdA+z4yXccAQtCfMALw8tfTKlmVtWz DflMf3a8c3zOkorY3zjQS4ck3NR/ymoUT/BgE=
MIME-Version: 1.0
Received: by 10.213.15.138 with HTTP; Wed, 31 Mar 2010 05:48:47 -0700 (PDT)
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE20D1C8293@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <w2v9ae56b1e1003310428o6fc07243j294b603eec953a1a@mail.gmail.com> <m2k9ae56b1e1003310523zc70f6a83ub0e5b1bdaeddd5ce@mail.gmail.com> <EDC0A1AE77C57744B664A310A0B23AE20D1C8293@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Wed, 31 Mar 2010 14:48:47 +0200
Received: by 10.213.76.141 with SMTP id c13mr2252321ebk.33.1270039727693; Wed,  31 Mar 2010 05:48:47 -0700 (PDT)
Message-ID: <m2v9ae56b1e1003310548i739c29c1t8080612ae5b4eea7@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=00c09f801791d1e08e0483182ae5
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re: 	#21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 12:48:24 -0000

--00c09f801791d1e08e0483182ae5
Content-Type: text/plain; charset=ISO-8859-1

Now that is pessimistic...

I thought that largely people should be able to agree on some common
denominator between ETSI and SIP connect profile, but maybe that is my
overly optimistic naive stagnant mindset.

/Hans Erik van Elburg


On Wed, Mar 31, 2010 at 2:32 PM, DRAGE, Keith (Keith) <
keith.drage@alcatel-lucent.com> wrote:

>  The problem is that I suspect noone is going to agree what that profile
> is to be sufficiently useful.
>
> regards
>
> Keith
>
>  ------------------------------
> *From:* martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] *On
> Behalf Of *Hans Erik van Elburg
> *Sent:* Wednesday, March 31, 2010 1:24 PM
> *To:* martini@ietf.org
> *Subject:* Re: [martini] Need for a SIP/SDP profile for SIP trunking , was
> Re: #21: 3.2.2 describes an issue with some PBX
>
> I should have said "explicit indication" instead of "option tag". Feature
> tags maybe more appropriate, when talking about a profile.
>
> /Hans Erik van Elburg
>
>
> On Wed, Mar 31, 2010 at 1:28 PM, Hans Erik van Elburg <
> ietf.hanserik@gmail.com> wrote:
>
>> Yes, I agree with that observation.
>>
>> Only solving the routing issue does not solve the overall problem. For
>> that a minimum SIP/SDP profile needs to be agreed upon. Also what are common
>> denominator as codec for voice, fax, dtmf etc.
>>
>> The question rises if there should be an option tag to signal support for
>> a profile instead of only signalling what routing method is preferred.
>>
>> BR,
>> /Hans Erik van Elburg
>>
>>
>> On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, Keith (Keith) <
>> keith.drage@alcatel-lucent.com> wrote:
>>
>>>  So assuming that this text is accepted, I guess the key argument of
>>> providing this distinction is not that both behaviours are non-standard, but
>>> that some means is needed to distinguish the two.
>>>
>>> While I do not have a problem with that specifically, I still have an
>>> issue that providing some signalling to do this solves all the issues. There
>>> are all sorts of other issues associated with what the PBX "expects" that
>>> also cause all sorts of issues, such as whether it expects a tel URI in tel
>>> URI format or SIP URI format, and so on, that are not signalled.
>>>
>>> Therefore at the end of the day, one is still going to end up with
>>> configuration information at either end of this interface that is not
>>> explicitly signalled, and in the absence of both sides having preconfigured
>>> knowledge of that information, the interface is not going to work.
>>>
>>> regards
>>>
>>> Keith
>>>
>>>  ------------------------------
>>>  *From:* martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] *On
>>> Behalf Of *Elwell, John
>>> *Sent:* Tuesday, March 30, 2010 6:11 PM
>>> *To:* Hans Erik van Elburg
>>>
>>> *Cc:* martini@ietf.org
>>> *Subject:* Re: [martini] #21: 3.2.2 describes an issue with some PBX
>>>
>>>    OK, fixed in my working copy.
>>>
>>> John
>>>
>>>  ------------------------------
>>> *From:* Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
>>> *Sent:* 30 March 2010 11:49
>>> *To:* Elwell, John
>>> *Cc:* martini@ietf.org
>>> *Subject:* Re: [martini] #21: 3.2.2 describes an issue with some PBX
>>>
>>> Hi John,
>>>
>>> Inline...
>>>
>>> /Hans Erik van Elburg
>>>
>>> On Mon, Mar 29, 2010 at 9:55 PM, Elwell, John <
>>> john.elwell@siemens-enterprise.com> wrote:
>>>
>>>> Hans Erik,
>>>>
>>>> I think the point you are trying to make is that it is not one-sided.
>>>> The fact is, each side has different ways of working, and you need to have
>>>> the two sides operating in compatible manners for it to work. In practice, I
>>>> think there are other variants, besides the two cited in the present 3.2.2.
>>>
>>> Yes. And there is no objective way to automatically determine what
>>> variant the PBX or the SSP is supporting. Which is what an options tag could
>>> resolve.
>>>
>>>
>>>> I would suggest:
>>>>
>>>>        <t>Even where all information needed by the SIP-PBX is provided,
>>>> in some deployments inbound SIP requests from the SSP have the registered
>>>> Contact URI in the Request-URI, whereas in other deployments inbound SIP
>>>> requests have the intended target (AOR) in the Request-URI and the Contact
>>>> URI in the Route header field. There are other variants too.
>>>> Interoperability problems arise when a PBX designed for or configured for
>>>> one variant attempts to interwork with an SSP designed for or configured for
>>>> another variant.</t>
>>>>
>>> Yes, slightly modified to add the objective means issue:
>>>  <t>Even where all information needed by the SIP-PBX is provided, in some
>>> deployments inbound SIP requests from the SSP have the registered PBX
>>> Contact URI in the Request-URI, whereas in other deployments inbound SIP
>>> requests have the intended target PBX user (AOR) in the Request-URI and the
>>> Contact URI in the Route header field. There are other variants too.
>>> Interoperability problems arise when a PBX designed for or configured for
>>> one variant attempts to interwork with an SSP designed for or configured for
>>> another variant. There is currently no objective means in the signalling
>>> during registration for either party to discover what mechanism the other
>>> side supports.</t>
>>>
>>>
>>>> To accompany this, I think the title of the section should be changed
>>>> too: "Inconsistent placement of information in inbound requests"
>>>>
>>>> Yes, slightly modified to make it more specific: "Inconsistent placement
>>> of target URI information in inbound requests".
>>>
>>>
>>>> John
>>>>
>>>> > -----Original Message-----
>>>> > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
>>>>  > Sent: 29 March 2010 17:27
>>>> > To: Elwell, John
>>>> > Cc: martini@ietf.org
>>>> > Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>>>> >
>>>> > Hi John,
>>>> >
>>>> > I was just trying to find a text that describes the issue.
>>>> >
>>>> > But now the issue reads like "some PBX like apples, some like
>>>> > bananas". To me that does not sound like a usefull issue to
>>>> > describe in an RFC.
>>>> >
>>>> > So I think one or two more sentence would make clear why this
>>>> > is an issue.
>>>> >
>>>> > I think there is multiple underlying issues here:
>>>> > - PBX have different SIP profiles or all SIP-PBX are different
>>>> > - PBX support SIP trunking flavour A, or support SIP trunking
>>>> > flavour B
>>>> > - SSP systems don't know what mechanism the PBX support (can
>>>> > be resolved with explicit indicator, this draft proposes an
>>>> > indicator for flavour B but for another purpose it seems)
>>>> > - PBX do not know what SIP trunking flavour the SSP supports
>>>> > (not addressed it seems)
>>>> >
>>>> > I don't seem to have a lucky hand with proposing an improved
>>>> > text, so maybe you should have a go at it.
>>>> >
>>>> > BR,
>>>> > /Hans Erik van Elburg
>>>> >
>>>> > p.s. I never said or implied that a SIP-PBX shall implement
>>>> > IMS. But it would be really, really, really good if they
>>>> > would interwork on the UNI with the IMS business trunking.  I
>>>> > think that should also be in your interest and in fact you
>>>> > have been part of that work...
>>>> >
>>>> >
>>>> >
>>>> > On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John
>>>> > <john.elwell@siemens-enterprise.com> wrote:
>>>> >
>>>> >
>>>> >       Hans Erik,
>>>> >
>>>> >       As an individual, I disagree with the proposed text,
>>>> > since it is misleading. The "international standards" to
>>>> > which you prefer are standards specific to an IMS
>>>> > environment. The implication of the wording as proposed is
>>>> > that SIP-PBXs ought to implement IMS specifications. And as
>>>> > Hadriel points out, implementing those IMS specifications
>>>> > does not eliminate the problems that the SIPconnect people
>>>> > are trying to solve. I believe the existing text in draft-03
>>>> > is sufficient.
>>>> >
>>>> >
>>>> >       John
>>>> >
>>>> >       > -----Original Message-----
>>>> >       > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
>>>> >
>>>> >       > Sent: 26 March 2010 23:03
>>>> >       > To: Elwell, John
>>>> >       > Cc: martini@ietf.org
>>>> >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
>>>> > with some PBX
>>>> >       >
>>>> >       > I will not argue with you about the validity of that argument.
>>>> >       >
>>>> >       > Can you agree to the modified text?
>>>> >       >
>>>> >       > "Request-URI vs. loose-route acceptance
>>>> >       > Some IP-PBX do not implement international standards or SIP
>>>> >       > profiles for SIP trunking. As a consequence some SIP-PBXs
>>>> >       > expect that inbound SIP requests from the SSP will have the
>>>> >       > registered Contact-URI in the Request-URI, and thus not
>>>> >       > interoperate with the loose-route scheme of 3GPP and ETSI.
>>>> >       > Other SIP-PBXs are fine with the Request-URI being the
>>>> >       > intended target, but cannot handle receiving a Route header
>>>> >       > field identifying their registered Contact-URI as a
>>>> >       > loose-route entry."
>>>> >       >
>>>> >       > BR,
>>>> >       > /Hans Erik van Elburg
>>>> >       >
>>>> >       >
>>>> >       > On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
>>>> >       > <john.elwell@siemens-enterprise.com> wrote:
>>>> >       >
>>>> >       >
>>>> >       >       The IETF does not have a mechanism, and that is the
>>>> >       > reason for the MARTINI work. In particular, the IETF has not
>>>> >       > published the so-called loose-route mechanism. Hence the
>>>> >       > reason for the IETF, as owner of SIP, to publish a mechanism
>>>> >       > for bulk registrations.
>>>> >       >
>>>> >       >       John
>>>> >       >
>>>> >       >
>>>> >       >       > -----Original Message-----
>>>> >       >       > From: Hans Erik van Elburg
>>>> > [mailto:ietf.hanserik@gmail.com]
>>>> >       >       > Sent: 26 March 2010 02:21
>>>> >       >       > To: trac@localhost.amsl.com
>>>> >       >       > Cc: Elwell, John; martini@ietf.org
>>>> >       >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
>>>> >       > with some PBX
>>>> >       >       >
>>>> >       >       >
>>>> >       >       > Then you should rephrase to what the real issue is:
>>>> >       >       > "
>>>> >       >       >
>>>> >       >       >
>>>> >       >       > Request-URI vs. loose-route acceptance
>>>> >       >       >
>>>> >       >       >
>>>> >       >       > Some IP-PBX do not implement international
>>>> > standards or SIP
>>>> >       >       > profiles for SIP trunking. As a consequence
>>>> > some SIP-PBXs
>>>> >       >       > expect that inbound SIP requests from the SSP
>>>> > will have the
>>>> >       >       > registered Contact-URI in the Request-URI,
>>>> > and thus not
>>>> >       >       > interoperate with the loose-route scheme of
>>>> > 3GPP and ETSI.
>>>> >       >       > Other SIP-PBXs are fine with the Request-URI being the
>>>> >       >       > intended target, but cannot handle receiving
>>>> > a Route header
>>>> >       >       > field identifying their registered Contact-URI as a
>>>> >       >       > loose-route entry."
>>>> >       >       >
>>>> >       >       >
>>>> >       >       > Is this an issue, yes. Does introducing yet another
>>>> >       > profile help? No.
>>>> >       >       >
>>>> >       >       > /Hans Erik van Elburg
>>>> >       >       >
>>>> >       >       >
>>>> >       >       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
>>>> >       >       > <trac@tools.ietf.org> wrote:
>>>> >       >       >
>>>> >       >       >
>>>> >       >       >       #21: 3.2.2 describes an issue with some PBX
>>>> >       >       >
>>>> >       >       >
>>>> > -------------------------------------+------------------------
>>>> >       >       > --------------
>>>> >       >       >        Reporter:  ietf.hanserik@...
>>>> > |        Owner:
>>>> >       >       >
>>>> >       >       >           Type:  defect                   |
>>>> >       > Status:  closed
>>>> >       >       >
>>>> >       >       >        Priority:  minor                    |
>>>> >       > Milestone:  milestone1
>>>> >       >       >       Component:  reqs                     |
>>>> >       > Version:  1.0
>>>> >       >       >
>>>> >       >       >        Severity:  In WG Last Call          |
>>>> >       > Resolution:  invalid
>>>> >       >       >        Keywords:                           |
>>>> >       >       >
>>>> >       >       >
>>>> > -------------------------------------+------------------------
>>>> >       >       > --------------
>>>> >       >       >       Changes (by john.elwell@...):
>>>> >       >       >
>>>> >       >       >        * status:  new => closed
>>>> >       >       >        * resolution:  => invalid
>>>> >       >       >
>>>> >       >       >
>>>> >       >       >       Comment:
>>>> >       >       >
>>>> >       >       >
>>>> >       >       >        The text of 3.2.2 just underlines the
>>>> > fact that there
>>>> >       >       > are different
>>>> >       >       >        implementations around. A PBX that
>>>> > expects the loose
>>>> >       >       > route mechanism to be
>>>> >       >       >        used would fail to interwork with SSPs using a
>>>> >       >       > different mechanism (e.g.,
>>>> >       >       >        SIPconnect 1.0), and a PBX not
>>>> > expecting the loose
>>>> >       >       > route mechanism to be
>>>> >       >       >        used would fail to interwork with a loose route
>>>> >       >       > implementation (e.g.,
>>>> >       >       >        ETSI/3GPP). Hence the urgent need for
>>>> > a standard.
>>>> >       >       >
>>>> >       >       >       --
>>>> >       >       >       Ticket URL:
>>>> >       >       >
>>>> >       >
>>>> > <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
>>>> >       >       >
>>>> >       >       >       martini <http://tools.ietf.org/martini/>
>>>> >       >       >
>>>> >       >       >
>>>> >       >       >       _______________________________________________
>>>> >       >       >       martini mailing list
>>>> >       >       >       martini@ietf.org
>>>> >       >       >       https://www.ietf.org/mailman/listinfo/martini
>>>> >       >       >
>>>> >       >       >
>>>> >       >       >
>>>> >       >       >
>>>> >       >
>>>> >       >
>>>> >       >
>>>> >
>>>> >
>>>> >
>>>>
>>>
>>>
>>
>> _______________________________________________
>> martini mailing list
>> martini@ietf.org
>> https://www.ietf.org/mailman/listinfo/martini
>>
>>
>

--00c09f801791d1e08e0483182ae5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Now that is pessimistic...<br><br>I thought that largely people should be a=
ble to agree on some common denominator between ETSI and SIP connect profil=
e, but maybe that is my overly optimistic naive stagnant mindset. <br><br c=
lear=3D"all">
/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Wed, Mar 31, 2010 at 2:32 PM, DRAGE, =
Keith (Keith) <span dir=3D"ltr">&lt;<a href=3D"mailto:keith.drage@alcatel-l=
ucent.com">keith.drage@alcatel-lucent.com</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: =
1px solid rgb(204, 204, 204); padding-left: 1ex;">




<div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">The problem is that I suspect noone is going to agree what=20
that profile is to be sufficiently useful.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">regards</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">Keith</font></span></div><br>
<blockquote style=3D"padding-left: 5px; margin-left: 5px; border-left: 2px =
solid rgb(0, 0, 255); margin-right: 0px;">
  <div dir=3D"ltr" align=3D"left" lang=3D"en-us">
  <hr>
  <font face=3D"Tahoma" size=3D"2"><div class=3D"im"><b>From:</b> <a href=
=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">martini-bounces@ietf=
.org</a>=20
  [mailto:<a href=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">mar=
tini-bounces@ietf.org</a>] <b>On Behalf Of </b>Hans Erik van=20
  Elburg<br></div><b>Sent:</b> Wednesday, March 31, 2010 1:24 PM<br><b>To:<=
/b>=20
  <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a=
><br><b>Subject:</b> Re: [martini] Need for a SIP/SDP profile=20
  for SIP trunking , was Re: #21: 3.2.2 describes an issue with some=20
  PBX<br></font><br></div><div><div></div><div class=3D"h5">
  <div></div>I should have said &quot;explicit indication&quot; instead of =
&quot;option tag&quot;.=20
  Feature tags maybe more appropriate, when talking about a profile.<br><br=
 clear=3D"all">/Hans Erik van Elburg<br><br><br>
  <div class=3D"gmail_quote">On Wed, Mar 31, 2010 at 1:28 PM, Hans Erik van=
 Elburg=20
  <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf.hanserik@gmail.com" target=
=3D"_blank">ietf.hanserik@gmail.com</a>&gt;</span>=20
  wrote:<br>
  <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; margin: 0pt=
 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">Yes,=20
    I agree with that observation.<br><br>Only solving the routing issue do=
es=20
    not solve the overall problem. For that a minimum SIP/SDP profile needs=
 to=20
    be agreed upon. Also what are common denominator as codec for voice, fa=
x,=20
    dtmf etc. <br><br>The question rises if there should be an option tag t=
o=20
    signal support for a profile instead of only signalling what routing me=
thod=20
    is preferred.<br><br>BR,<br clear=3D"all">/Hans Erik van Elburg<br><br>=
<br>
    <div class=3D"gmail_quote">On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, Keit=
h (Keith)=20
    <span dir=3D"ltr">&lt;<a href=3D"mailto:keith.drage@alcatel-lucent.com"=
 target=3D"_blank">keith.drage@alcatel-lucent.com</a>&gt;</span> wrote:<br>
    <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; margin: 0=
pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">
      <div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2">So=20
      assuming that this text is accepted, I guess the key argument of prov=
iding=20
      this distinction is not that both behaviours are non-standard, but th=
at=20
      some means is needed to distinguish the two.</font></span></div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2"></font></span>=A0</div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2">While=20
      I do not have a problem with that specifically, I still have an issue=
 that=20
      providing some signalling to do this solves all the issues. There are=
 all=20
      sorts of other issues associated with what the PBX &quot;expects&quot=
; that also=20
      cause all sorts of issues, such as whether it expects a tel URI in te=
l URI=20
      format or SIP URI format, and so on, that are not signalled.=20
      </font></span></div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2"></font></span>=A0</div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2">Therefore at the end of the day, one is still going to e=
nd up with=20
      configuration information at either end of this interface that is not=
=20
      explicitly signalled, and in the absence of both sides having=20
      preconfigured knowledge of that information, the interface is not goi=
ng to=20
      work.</font></span></div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2"></font></span>=A0</div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2">regards</font></span></div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2"></font></span>=A0</div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2">Keith</font></span></div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2"></font></span>=A0</div>
      <div dir=3D"ltr" align=3D"left">
      <hr>
      </div>
      <div dir=3D"ltr" align=3D"left"><font face=3D"Tahoma" size=3D"2"><b>F=
rom:</b> <a href=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">mart=
ini-bounces@ietf.org</a> [mailto:<a href=3D"mailto:martini-bounces@ietf.org=
" target=3D"_blank">martini-bounces@ietf.org</a>] <b>On Behalf Of </b>Elwel=
l,=20
      John<br><b>Sent:</b> Tuesday, March 30, 2010 6:11 PM<br><b>To:</b> Ha=
ns=20
      Erik van Elburg
      <div>
      <div></div>
      <div><br><b>Cc:</b> <a href=3D"mailto:martini@ietf.org" target=3D"_bl=
ank">martini@ietf.org</a><br><b>Subject:</b> Re: [martini] #21:=20
      3.2.2 describes an issue with some PBX<br></div></div></font><br></di=
v>
      <div>
      <div></div>
      <div>
      <blockquote dir=3D"ltr" style=3D"padding-left: 5px; margin-left: 5px;=
 border-left: 2px solid rgb(0, 0, 255); margin-right: 0px;">
        <div></div>
        <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=
=3D"Arial" size=3D"2">OK,=20
        fixed in my working copy.</font></span></div>
        <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=
=3D"Arial" size=3D"2"></font></span>=A0</div>
        <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=
=3D"Arial" size=3D"2">John</font></span></div><br>
        <blockquote style=3D"padding-left: 5px; margin-left: 5px; border-le=
ft: 2px solid rgb(0, 0, 255); margin-right: 0px;">
          <div dir=3D"ltr" align=3D"left" lang=3D"en-us">
          <hr>
          <font face=3D"Tahoma" size=3D"2"><b>From:</b> Hans Erik van Elbur=
g [mailto:<a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">ietf=
.hanserik@gmail.com</a>] <br><b>Sent:</b> 30 March=20
          2010 11:49<br><b>To:</b> Elwell, John<br><b>Cc:</b> <a href=3D"ma=
ilto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><br><b>Subject=
:</b> Re: [martini]=20
          #21: 3.2.2 describes an issue with some PBX<br></font><br></div>
          <div></div>Hi John,<br><br>Inline... <br clear=3D"all"><br>/Hans =
Erik van=20
          Elburg<br><br>
          <div class=3D"gmail_quote">On Mon, Mar 29, 2010 at 9:55 PM, Elwel=
l, John=20
          <span dir=3D"ltr">&lt;<a href=3D"mailto:john.elwell@siemens-enter=
prise.com" target=3D"_blank">john.elwell@siemens-enterprise.com</a>&gt;</sp=
an>=20
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; mar=
gin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">Hans=20
            Erik,<br><br>I think the point you are trying to make is that i=
t is=20
            not one-sided. The fact is, each side has different ways of wor=
king,=20
            and you need to have the two sides operating in compatible mann=
ers=20
            for it to work. In practice, I think there are other variants,=
=20
            besides the two cited in the present 3.2.2.</blockquote>
          <div>Yes. And there is no objective way to automatically determin=
e=20
          what variant the PBX or the SSP is supporting. Which is what an=
=20
          options tag could resolve.<br>=A0</div>
          <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; mar=
gin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">I=20
            would suggest:<br><br>=A0 =A0 =A0 =A0&lt;t&gt;Even where=20
            all information needed by the SIP-PBX is provided, in some=20
            deployments inbound SIP requests from the SSP have the register=
ed=20
            Contact URI in the Request-URI, whereas in other deployments in=
bound=20
            SIP requests have the intended target (AOR) in the Request-URI =
and=20
            the Contact URI in the Route header field. There are other vari=
ants=20
            too. Interoperability problems arise when a PBX designed for or=
=20
            configured for one variant attempts to interwork with an SSP=20
            designed for or configured for another=20
          variant.&lt;/t&gt;<br></blockquote>
          <div>Yes, slightly modified to add the objective means=20
          issue:<br>=A0&lt;t&gt;Even where all information needed by the=20
          SIP-PBX is provided, in some deployments inbound SIP requests fro=
m the=20
          SSP have the registered PBX Contact URI in the Request-URI, where=
as in=20
          other deployments inbound SIP requests have the intended target P=
BX=20
          user (AOR) in the Request-URI and the Contact URI in the Route he=
ader=20
          field. There are other variants too. Interoperability problems ar=
ise=20
          when a PBX designed for or configured for one variant attempts to=
=20
          interwork with an SSP designed for or configured for another vari=
ant.=20
          There is currently no objective means in the signalling during=20
          registration for either party to discover what mechanism the othe=
r=20
          side supports.&lt;/t&gt;<br>=A0</div>
          <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; mar=
gin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">To=20
            accompany this, I think the title of the section should be chan=
ged=20
            too: &quot;Inconsistent placement of information in inbound req=
uests&quot;<br>
            <div><br></div></blockquote>
          <div>Yes, slightly modified to make it more specific: &quot;Incon=
sistent=20
          placement of target URI information in inbound=20
          requests&quot;.<br>=A0</div>
          <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; mar=
gin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">
            <div>John<br><br>&gt; -----Original Message-----<br>&gt; From: =
Hans=20
            Erik van Elburg [mailto:<a href=3D"mailto:ietf.hanserik@gmail.c=
om" target=3D"_blank">ietf.hanserik@gmail.com</a>]<br></div>
            <div>
            <div></div>
            <div>&gt; Sent: 29 March 2010 17:27<br>&gt; To: Elwell, John<br=
>&gt;=20
            Cc: <a href=3D"mailto:martini@ietf.org" target=3D"_blank">marti=
ni@ietf.org</a><br>&gt; Subject: Re: [martini]=20
            #21: 3.2.2 describes an issue with some PBX<br>&gt;<br>&gt; Hi=
=20
            John,<br>&gt;<br>&gt; I was just trying to find a text that=20
            describes the issue.<br>&gt;<br>&gt; But now the issue reads li=
ke=20
            &quot;some PBX like apples, some like<br>&gt; bananas&quot;. To=
 me that does=20
            not sound like a usefull issue to<br>&gt; describe in an=20
            RFC.<br>&gt;<br>&gt; So I think one or two more sentence would =
make=20
            clear why this<br>&gt; is an issue.<br>&gt;<br>&gt; I think the=
re is=20
            multiple underlying issues here:<br>&gt; - PBX have different S=
IP=20
            profiles or all SIP-PBX are different<br>&gt; - PBX support SIP=
=20
            trunking flavour A, or support SIP trunking<br>&gt; flavour=20
            B<br>&gt; - SSP systems don&#39;t know what mechanism the PBX s=
upport=20
            (can<br>&gt; be resolved with explicit indicator, this draft=20
            proposes an<br>&gt; indicator for flavour B but for another pur=
pose=20
            it seems)<br>&gt; - PBX do not know what SIP trunking flavour t=
he=20
            SSP supports<br>&gt; (not addressed it seems)<br>&gt;<br>&gt; I=
=20
            don&#39;t seem to have a lucky hand with proposing an improved<=
br>&gt;=20
            text, so maybe you should have a go at it.<br>&gt;<br>&gt;=20
            BR,<br>&gt; /Hans Erik van Elburg<br>&gt;<br>&gt; p.s. I never =
said=20
            or implied that a SIP-PBX shall implement<br>&gt; IMS. But it w=
ould=20
            be really, really, really good if they<br>&gt; would interwork =
on=20
            the UNI with the IMS business trunking. =A0I<br>&gt; think that=
=20
            should also be in your interest and in fact you<br>&gt; have be=
en=20
            part of that work...<br>&gt;<br>&gt;<br>&gt;<br>&gt; On Mon, Ma=
r 29,=20
            2010 at 5:56 PM, Elwell, John<br>&gt; &lt;<a href=3D"mailto:joh=
n.elwell@siemens-enterprise.com" target=3D"_blank">john.elwell@siemens-ente=
rprise.com</a>&gt;=20
            wrote:<br>&gt;<br>&gt;<br>&gt; =A0 =A0 =A0 Hans=20
            Erik,<br>&gt;<br>&gt; =A0 =A0 =A0 As an individual, I=20
            disagree with the proposed text,<br>&gt; since it is misleading=
. The=20
            &quot;international standards&quot; to<br>&gt; which you prefer=
 are standards=20
            specific to an IMS<br>&gt; environment. The implication of the=
=20
            wording as proposed is<br>&gt; that SIP-PBXs ought to implement=
 IMS=20
            specifications. And as<br>&gt; Hadriel points out, implementing=
=20
            those IMS specifications<br>&gt; does not eliminate the problem=
s=20
            that the SIPconnect people<br>&gt; are trying to solve. I belie=
ve=20
            the existing text in draft-03<br>&gt; is=20
            sufficient.<br>&gt;<br>&gt;<br>&gt; =A0 =A0 =A0=20
            John<br>&gt;<br>&gt; =A0 =A0 =A0 &gt; -----Original=20
            Message-----<br>&gt; =A0 =A0 =A0 &gt; From: Hans Erik van=20
            Elburg [mailto:<a href=3D"mailto:ietf.hanserik@gmail.com" targe=
t=3D"_blank">ietf.hanserik@gmail.com</a>]<br>&gt;<br>&gt; =A0=20
            =A0 =A0 &gt; Sent: 26 March 2010 23:03<br>&gt; =A0 =A0=20
            =A0 &gt; To: Elwell, John<br>&gt; =A0 =A0 =A0 &gt; Cc:=20
            <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@i=
etf.org</a><br>&gt; =A0 =A0 =A0 &gt;=20
            Subject: Re: [martini] #21: 3.2.2 describes an issue<br>&gt; wi=
th=20
            some PBX<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt; I will not argue with you about the validity of that=
=20
            argument.<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt; Can you agree to the modified text?<br>&gt; =A0=20
            =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; &quot;Request-URI=20
            vs. loose-route acceptance<br>&gt; =A0 =A0 =A0 &gt; Some=20
            IP-PBX do not implement international standards or SIP<br>&gt;=
=20
            =A0 =A0 =A0 &gt; profiles for SIP trunking. As a=20
            consequence some SIP-PBXs<br>&gt; =A0 =A0 =A0 &gt; expect=20
            that inbound SIP requests from the SSP will have the<br>&gt; =
=A0=20
            =A0 =A0 &gt; registered Contact-URI in the Request-URI, and=20
            thus not<br>&gt; =A0 =A0 =A0 &gt; interoperate with the=20
            loose-route scheme of 3GPP and ETSI.<br>&gt; =A0 =A0 =A0=20
            &gt; Other SIP-PBXs are fine with the Request-URI being the<br>=
&gt;=20
            =A0 =A0 =A0 &gt; intended target, but cannot handle=20
            receiving a Route header<br>&gt; =A0 =A0 =A0 &gt; field=20
            identifying their registered Contact-URI as a<br>&gt; =A0 =A0=
=20
            =A0 &gt; loose-route entry.&quot;<br>&gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; BR,<br>&gt; =A0 =A0=20
            =A0 &gt; /Hans Erik van Elburg<br>&gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt; On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John<br>&gt; =A0=
=20
            =A0 =A0 &gt; &lt;<a href=3D"mailto:john.elwell@siemens-enterpri=
se.com" target=3D"_blank">john.elwell@siemens-enterprise.com</a>&gt;=20
            wrote:<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            The IETF does not have a mechanism, and that is the<br>&gt; =A0=
=20
            =A0 =A0 &gt; reason for the MARTINI work. In particular, the=20
            IETF has not<br>&gt; =A0 =A0 =A0 &gt; published the=20
            so-called loose-route mechanism. Hence the<br>&gt; =A0 =A0=20
            =A0 &gt; reason for the IETF, as owner of SIP, to publish a=20
            mechanism<br>&gt; =A0 =A0 =A0 &gt; for bulk=20
            registrations.<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 John<br>&gt; =A0 =A0=20
            =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt; -----Original=20
            Message-----<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt; From: Hans Erik van Elburg<br>&gt; [mailto:<a href=3D"mail=
to:ietf.hanserik@gmail.com" target=3D"_blank">ietf.hanserik@gmail.com</a>]<=
br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt; Sent: 26 March 2010=20
            02:21<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            To: <a href=3D"mailto:trac@localhost.amsl.com" target=3D"_blank=
">trac@localhost.amsl.com</a><br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt; Cc: Elwell, John; <a href=3D"mailto:m=
artini@ietf.org" target=3D"_blank">martini@ietf.org</a><br>&gt; =A0 =A0 =A0=
 &gt;=20
            =A0 =A0 =A0 &gt; Subject: Re: [martini] #21: 3.2.2=20
            describes an issue<br>&gt; =A0 =A0 =A0 &gt; with some=20
            PBX<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            Then you should rephrase to what the real issue is:<br>&gt; =A0=
=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; &quot;<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 &gt; Request-URI vs. loose-route=20
            acceptance<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            Some IP-PBX do not implement international<br>&gt; standards or=
=20
            SIP<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            profiles for SIP trunking. As a consequence<br>&gt; some=20
            SIP-PBXs<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            expect that inbound SIP requests from the SSP<br>&gt; will have=
=20
            the<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            registered Contact-URI in the Request-URI,<br>&gt; and thus=20
            not<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            interoperate with the loose-route scheme of<br>&gt; 3GPP and=20
            ETSI.<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            Other SIP-PBXs are fine with the Request-URI being the<br>&gt;=
=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; intended target,=20
            but cannot handle receiving<br>&gt; a Route header<br>&gt; =A0=
=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; field identifying their=20
            registered Contact-URI as a<br>&gt; =A0 =A0 =A0 &gt; =A0=20
            =A0 =A0 &gt; loose-route entry.&quot;<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0=20
            =A0 =A0 &gt; Is this an issue, yes. Does introducing yet=20
            another<br>&gt; =A0 =A0 =A0 &gt; profile help? No.<br>&gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; /Hans Erik van=20
            Elburg<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; On=20
            Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker<br>&gt; =A0=
=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; &lt;<a href=3D"mailto:trac@tools.=
ietf.org" target=3D"_blank">trac@tools.ietf.org</a>&gt; wrote:<br>&gt; =A0=
=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 #21: 3.2.2=20
            describes an issue with some PBX<br>&gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0=20
            =A0 =A0 &gt;<br>&gt;=20
            -------------------------------------+------------------------<=
br>&gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            --------------<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 =A0Reporter:=20
            =A0ietf.hanserik@...<br>&gt; | =A0 =A0 =A0=20
            =A0Owner:<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 =A0 =A0 Type: =A0defect =A0 =A0=20
            =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>&gt; =A0=20
            =A0 =A0 &gt; Status: =A0closed<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Priority:=20
            =A0minor =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=20
            =A0 =A0|<br>&gt; =A0 =A0 =A0 &gt; Milestone:=20
            =A0milestone1<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 Component: =A0reqs =A0 =A0=20
            =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>&gt;=20
            =A0 =A0 =A0 &gt; Version: =A01.0<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Severity:=20
            =A0In WG Last Call =A0 =A0 =A0 =A0 =A0|<br>&gt;=20
            =A0 =A0 =A0 &gt; Resolution: =A0invalid<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            =A0Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0=20
            =A0 =A0 =A0 =A0 =A0 =A0 |<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt;<br>&gt;=20
            -------------------------------------+------------------------<=
br>&gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            --------------<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 Changes (by=20
            john.elwell@...):<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 =A0* status: =A0new =3D&gt;=20
            closed<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 =A0* resolution: =A0=3D&gt; invalid<br>&gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            Comment:<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 =A0The text of 3.2.2 just underlines=20
            the<br>&gt; fact that there<br>&gt; =A0 =A0 =A0 &gt; =A0=20
            =A0 =A0 &gt; are different<br>&gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0implementations=20
            around. A PBX that<br>&gt; expects the loose<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt; route mechanism to be<br>&gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 =A0used would fail to interwork with SSPs using a<br>&gt;=
=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; different=20
            mechanism (e.g.,<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 =A0SIPconnect 1.0), and a PBX=20
            not<br>&gt; expecting the loose<br>&gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 &gt; route mechanism to be<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            =A0used would fail to interwork with a loose route<br>&gt; =A0=
=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; implementation=20
            (e.g.,<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 =A0ETSI/3GPP). Hence the urgent need=20
            for<br>&gt; a standard.<br>&gt; =A0 =A0 =A0 &gt; =A0=20
            =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 --<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 Ticket=20
            URL:<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; &lt;<a href=3D"http://tra=
c.tools.ietf.org/wg/martini/trac/ticket/21#comment:1" target=3D"_blank">htt=
p://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1</a>&gt;<br>&gt;=
=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            martini &lt;<a href=3D"http://tools.ietf.org/martini/" target=
=3D"_blank">http://tools.ietf.org/martini/</a>&gt;<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            _______________________________________________<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            martini mailing list<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 <a href=3D"mailto:martini@ietf.org" target=
=3D"_blank">martini@ietf.org</a><br>&gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 <a href=3D"https://www.ietf.org/ma=
ilman/listinfo/martini" target=3D"_blank">https://www.ietf.org/mailman/list=
info/martini</a><br>&gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt;<br>&gt;<br>&gt;<br>&gt;=20
        </div></div></blockquote></div><br></blockquote></blockquote></div>=
</div></div></blockquote></div><br><br>____________________________________=
___________<br>martini=20
    mailing list<br><a href=3D"mailto:martini@ietf.org" target=3D"_blank">m=
artini@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/mar=
tini" target=3D"_blank">https://www.ietf.org/mailman/listinfo/martini</a><b=
r><br>
</blockquote></div><br></div></div></blockquote></div>
</blockquote></div><br>

--00c09f801791d1e08e0483182ae5--

From ietf.hanserik@gmail.com  Wed Mar 31 05:58:05 2010
Return-Path: <ietf.hanserik@gmail.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 76DCB3A68F7 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 05:58:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.61
X-Spam-Level: 
X-Spam-Status: No, score=-0.61 tagged_above=-999 required=5 tests=[AWL=0.858,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 NKCL9wFSkJ7j for <martini@core3.amsl.com>; Wed, 31 Mar 2010 05:58:03 -0700 (PDT)
Received: from mail-ew0-f224.google.com (mail-ew0-f224.google.com [209.85.219.224]) by core3.amsl.com (Postfix) with ESMTP id 7AA2C3A68EF for <martini@ietf.org>; Wed, 31 Mar 2010 05:58:02 -0700 (PDT)
Received: by ewy24 with SMTP id 24so21113ewy.13 for <martini@ietf.org>; Wed, 31 Mar 2010 05:58:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=hd9+/7G89w4kWhmb77ldIiwU66KE3ECNW2yTpHuc8Z4=; b=NPDCEgRVrELTuLeWj4vM3kPqFxP3P5VXZ1/tYjiLy4d3WbeXIVv57+T3HqXbfv1sdn kpdvEYtEiDGRpfulrojYqHpTuSbfwjqeSOetoRz4ze9+sHZvMS/XX+BZMeRxYLv56YfD 73TGjCTN4tk7dTVdH+//UPfPp4dXUt9f0nyhU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=g3fNxNUN8aUmmZbesJNO3MzZP0y2VEPGs82JYU5kBmySalty52JkE4dPPwF0Hn7JDN G9DlVE0F2jpU/mOzKbSwEpl8fEfMdyRmEgdrK+HSwqpg99fx0urNBMhBg/aZHlZSW227 mpQIPo+nQxuhtpBJTd8ihemYSGAu3Sspms77o=
MIME-Version: 1.0
Received: by 10.213.15.138 with HTTP; Wed, 31 Mar 2010 05:58:28 -0700 (PDT)
In-Reply-To: <m2v9ae56b1e1003310548i739c29c1t8080612ae5b4eea7@mail.gmail.com>
References: <w2v9ae56b1e1003310428o6fc07243j294b603eec953a1a@mail.gmail.com> <m2k9ae56b1e1003310523zc70f6a83ub0e5b1bdaeddd5ce@mail.gmail.com> <EDC0A1AE77C57744B664A310A0B23AE20D1C8293@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <m2v9ae56b1e1003310548i739c29c1t8080612ae5b4eea7@mail.gmail.com>
Date: Wed, 31 Mar 2010 14:58:28 +0200
Received: by 10.213.46.133 with SMTP id j5mr2278246ebf.32.1270040308973; Wed,  31 Mar 2010 05:58:28 -0700 (PDT)
Message-ID: <w2h9ae56b1e1003310558i331f2094x922639cde5677afb@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=00148531b7e57787100483184da2
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re: 	#21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 12:58:05 -0000

--00148531b7e57787100483184da2
Content-Type: text/plain; charset=ISO-8859-1

Maybe that is indeed asking for to much.

In that case it would still be usefull to be able to distinguish between the
profiles, so that means you would need an indicator per profile.

/Hans Erik van Elburg

On Wed, Mar 31, 2010 at 2:48 PM, Hans Erik van Elburg <
ietf.hanserik@gmail.com> wrote:

> Now that is pessimistic...
>
> I thought that largely people should be able to agree on some common
> denominator between ETSI and SIP connect profile, but maybe that is my
> overly optimistic naive stagnant mindset.
>
> /Hans Erik van Elburg
>
>
>
> On Wed, Mar 31, 2010 at 2:32 PM, DRAGE, Keith (Keith) <
> keith.drage@alcatel-lucent.com> wrote:
>
>>  The problem is that I suspect noone is going to agree what that profile
>> is to be sufficiently useful.
>>
>> regards
>>
>> Keith
>>
>>  ------------------------------
>> *From:* martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] *On
>> Behalf Of *Hans Erik van Elburg
>> *Sent:* Wednesday, March 31, 2010 1:24 PM
>> *To:* martini@ietf.org
>> *Subject:* Re: [martini] Need for a SIP/SDP profile for SIP trunking ,
>> was Re: #21: 3.2.2 describes an issue with some PBX
>>
>> I should have said "explicit indication" instead of "option tag". Feature
>> tags maybe more appropriate, when talking about a profile.
>>
>> /Hans Erik van Elburg
>>
>>
>> On Wed, Mar 31, 2010 at 1:28 PM, Hans Erik van Elburg <
>> ietf.hanserik@gmail.com> wrote:
>>
>>> Yes, I agree with that observation.
>>>
>>> Only solving the routing issue does not solve the overall problem. For
>>> that a minimum SIP/SDP profile needs to be agreed upon. Also what are common
>>> denominator as codec for voice, fax, dtmf etc.
>>>
>>> The question rises if there should be an option tag to signal support for
>>> a profile instead of only signalling what routing method is preferred.
>>>
>>> BR,
>>> /Hans Erik van Elburg
>>>
>>>
>>> On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, Keith (Keith) <
>>> keith.drage@alcatel-lucent.com> wrote:
>>>
>>>>  So assuming that this text is accepted, I guess the key argument of
>>>> providing this distinction is not that both behaviours are non-standard, but
>>>> that some means is needed to distinguish the two.
>>>>
>>>> While I do not have a problem with that specifically, I still have an
>>>> issue that providing some signalling to do this solves all the issues. There
>>>> are all sorts of other issues associated with what the PBX "expects" that
>>>> also cause all sorts of issues, such as whether it expects a tel URI in tel
>>>> URI format or SIP URI format, and so on, that are not signalled.
>>>>
>>>> Therefore at the end of the day, one is still going to end up with
>>>> configuration information at either end of this interface that is not
>>>> explicitly signalled, and in the absence of both sides having preconfigured
>>>> knowledge of that information, the interface is not going to work.
>>>>
>>>> regards
>>>>
>>>> Keith
>>>>
>>>>  ------------------------------
>>>>  *From:* martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] *On
>>>> Behalf Of *Elwell, John
>>>> *Sent:* Tuesday, March 30, 2010 6:11 PM
>>>> *To:* Hans Erik van Elburg
>>>>
>>>> *Cc:* martini@ietf.org
>>>> *Subject:* Re: [martini] #21: 3.2.2 describes an issue with some PBX
>>>>
>>>>    OK, fixed in my working copy.
>>>>
>>>> John
>>>>
>>>>  ------------------------------
>>>> *From:* Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
>>>> *Sent:* 30 March 2010 11:49
>>>> *To:* Elwell, John
>>>> *Cc:* martini@ietf.org
>>>> *Subject:* Re: [martini] #21: 3.2.2 describes an issue with some PBX
>>>>
>>>> Hi John,
>>>>
>>>> Inline...
>>>>
>>>> /Hans Erik van Elburg
>>>>
>>>> On Mon, Mar 29, 2010 at 9:55 PM, Elwell, John <
>>>> john.elwell@siemens-enterprise.com> wrote:
>>>>
>>>>> Hans Erik,
>>>>>
>>>>> I think the point you are trying to make is that it is not one-sided.
>>>>> The fact is, each side has different ways of working, and you need to have
>>>>> the two sides operating in compatible manners for it to work. In practice, I
>>>>> think there are other variants, besides the two cited in the present 3.2.2.
>>>>
>>>> Yes. And there is no objective way to automatically determine what
>>>> variant the PBX or the SSP is supporting. Which is what an options tag could
>>>> resolve.
>>>>
>>>>
>>>>> I would suggest:
>>>>>
>>>>>        <t>Even where all information needed by the SIP-PBX is provided,
>>>>> in some deployments inbound SIP requests from the SSP have the registered
>>>>> Contact URI in the Request-URI, whereas in other deployments inbound SIP
>>>>> requests have the intended target (AOR) in the Request-URI and the Contact
>>>>> URI in the Route header field. There are other variants too.
>>>>> Interoperability problems arise when a PBX designed for or configured for
>>>>> one variant attempts to interwork with an SSP designed for or configured for
>>>>> another variant.</t>
>>>>>
>>>> Yes, slightly modified to add the objective means issue:
>>>>  <t>Even where all information needed by the SIP-PBX is provided, in
>>>> some deployments inbound SIP requests from the SSP have the registered PBX
>>>> Contact URI in the Request-URI, whereas in other deployments inbound SIP
>>>> requests have the intended target PBX user (AOR) in the Request-URI and the
>>>> Contact URI in the Route header field. There are other variants too.
>>>> Interoperability problems arise when a PBX designed for or configured for
>>>> one variant attempts to interwork with an SSP designed for or configured for
>>>> another variant. There is currently no objective means in the signalling
>>>> during registration for either party to discover what mechanism the other
>>>> side supports.</t>
>>>>
>>>>
>>>>> To accompany this, I think the title of the section should be changed
>>>>> too: "Inconsistent placement of information in inbound requests"
>>>>>
>>>>> Yes, slightly modified to make it more specific: "Inconsistent
>>>> placement of target URI information in inbound requests".
>>>>
>>>>
>>>>> John
>>>>>
>>>>> > -----Original Message-----
>>>>> > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
>>>>>  > Sent: 29 March 2010 17:27
>>>>> > To: Elwell, John
>>>>> > Cc: martini@ietf.org
>>>>> > Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>>>>> >
>>>>> > Hi John,
>>>>> >
>>>>> > I was just trying to find a text that describes the issue.
>>>>> >
>>>>> > But now the issue reads like "some PBX like apples, some like
>>>>> > bananas". To me that does not sound like a usefull issue to
>>>>> > describe in an RFC.
>>>>> >
>>>>> > So I think one or two more sentence would make clear why this
>>>>> > is an issue.
>>>>> >
>>>>> > I think there is multiple underlying issues here:
>>>>> > - PBX have different SIP profiles or all SIP-PBX are different
>>>>> > - PBX support SIP trunking flavour A, or support SIP trunking
>>>>> > flavour B
>>>>> > - SSP systems don't know what mechanism the PBX support (can
>>>>> > be resolved with explicit indicator, this draft proposes an
>>>>> > indicator for flavour B but for another purpose it seems)
>>>>> > - PBX do not know what SIP trunking flavour the SSP supports
>>>>> > (not addressed it seems)
>>>>> >
>>>>> > I don't seem to have a lucky hand with proposing an improved
>>>>> > text, so maybe you should have a go at it.
>>>>> >
>>>>> > BR,
>>>>> > /Hans Erik van Elburg
>>>>> >
>>>>> > p.s. I never said or implied that a SIP-PBX shall implement
>>>>> > IMS. But it would be really, really, really good if they
>>>>> > would interwork on the UNI with the IMS business trunking.  I
>>>>> > think that should also be in your interest and in fact you
>>>>> > have been part of that work...
>>>>> >
>>>>> >
>>>>> >
>>>>> > On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John
>>>>> > <john.elwell@siemens-enterprise.com> wrote:
>>>>> >
>>>>> >
>>>>> >       Hans Erik,
>>>>> >
>>>>> >       As an individual, I disagree with the proposed text,
>>>>> > since it is misleading. The "international standards" to
>>>>> > which you prefer are standards specific to an IMS
>>>>> > environment. The implication of the wording as proposed is
>>>>> > that SIP-PBXs ought to implement IMS specifications. And as
>>>>> > Hadriel points out, implementing those IMS specifications
>>>>> > does not eliminate the problems that the SIPconnect people
>>>>> > are trying to solve. I believe the existing text in draft-03
>>>>> > is sufficient.
>>>>> >
>>>>> >
>>>>> >       John
>>>>> >
>>>>> >       > -----Original Message-----
>>>>> >       > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
>>>>> >
>>>>> >       > Sent: 26 March 2010 23:03
>>>>> >       > To: Elwell, John
>>>>> >       > Cc: martini@ietf.org
>>>>> >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
>>>>> > with some PBX
>>>>> >       >
>>>>> >       > I will not argue with you about the validity of that
>>>>> argument.
>>>>> >       >
>>>>> >       > Can you agree to the modified text?
>>>>> >       >
>>>>> >       > "Request-URI vs. loose-route acceptance
>>>>> >       > Some IP-PBX do not implement international standards or SIP
>>>>> >       > profiles for SIP trunking. As a consequence some SIP-PBXs
>>>>> >       > expect that inbound SIP requests from the SSP will have the
>>>>> >       > registered Contact-URI in the Request-URI, and thus not
>>>>> >       > interoperate with the loose-route scheme of 3GPP and ETSI.
>>>>> >       > Other SIP-PBXs are fine with the Request-URI being the
>>>>> >       > intended target, but cannot handle receiving a Route header
>>>>> >       > field identifying their registered Contact-URI as a
>>>>> >       > loose-route entry."
>>>>> >       >
>>>>> >       > BR,
>>>>> >       > /Hans Erik van Elburg
>>>>> >       >
>>>>> >       >
>>>>> >       > On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
>>>>> >       > <john.elwell@siemens-enterprise.com> wrote:
>>>>> >       >
>>>>> >       >
>>>>> >       >       The IETF does not have a mechanism, and that is the
>>>>> >       > reason for the MARTINI work. In particular, the IETF has not
>>>>> >       > published the so-called loose-route mechanism. Hence the
>>>>> >       > reason for the IETF, as owner of SIP, to publish a mechanism
>>>>> >       > for bulk registrations.
>>>>> >       >
>>>>> >       >       John
>>>>> >       >
>>>>> >       >
>>>>> >       >       > -----Original Message-----
>>>>> >       >       > From: Hans Erik van Elburg
>>>>> > [mailto:ietf.hanserik@gmail.com]
>>>>> >       >       > Sent: 26 March 2010 02:21
>>>>> >       >       > To: trac@localhost.amsl.com
>>>>> >       >       > Cc: Elwell, John; martini@ietf.org
>>>>> >       >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
>>>>> >       > with some PBX
>>>>> >       >       >
>>>>> >       >       >
>>>>> >       >       > Then you should rephrase to what the real issue is:
>>>>> >       >       > "
>>>>> >       >       >
>>>>> >       >       >
>>>>> >       >       > Request-URI vs. loose-route acceptance
>>>>> >       >       >
>>>>> >       >       >
>>>>> >       >       > Some IP-PBX do not implement international
>>>>> > standards or SIP
>>>>> >       >       > profiles for SIP trunking. As a consequence
>>>>> > some SIP-PBXs
>>>>> >       >       > expect that inbound SIP requests from the SSP
>>>>> > will have the
>>>>> >       >       > registered Contact-URI in the Request-URI,
>>>>> > and thus not
>>>>> >       >       > interoperate with the loose-route scheme of
>>>>> > 3GPP and ETSI.
>>>>> >       >       > Other SIP-PBXs are fine with the Request-URI being
>>>>> the
>>>>> >       >       > intended target, but cannot handle receiving
>>>>> > a Route header
>>>>> >       >       > field identifying their registered Contact-URI as a
>>>>> >       >       > loose-route entry."
>>>>> >       >       >
>>>>> >       >       >
>>>>> >       >       > Is this an issue, yes. Does introducing yet another
>>>>> >       > profile help? No.
>>>>> >       >       >
>>>>> >       >       > /Hans Erik van Elburg
>>>>> >       >       >
>>>>> >       >       >
>>>>> >       >       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue
>>>>> tracker
>>>>> >       >       > <trac@tools.ietf.org> wrote:
>>>>> >       >       >
>>>>> >       >       >
>>>>> >       >       >       #21: 3.2.2 describes an issue with some PBX
>>>>> >       >       >
>>>>> >       >       >
>>>>> > -------------------------------------+------------------------
>>>>> >       >       > --------------
>>>>> >       >       >        Reporter:  ietf.hanserik@...
>>>>> > |        Owner:
>>>>> >       >       >
>>>>> >       >       >           Type:  defect                   |
>>>>> >       > Status:  closed
>>>>> >       >       >
>>>>> >       >       >        Priority:  minor                    |
>>>>> >       > Milestone:  milestone1
>>>>> >       >       >       Component:  reqs                     |
>>>>> >       > Version:  1.0
>>>>> >       >       >
>>>>> >       >       >        Severity:  In WG Last Call          |
>>>>> >       > Resolution:  invalid
>>>>> >       >       >        Keywords:                           |
>>>>> >       >       >
>>>>> >       >       >
>>>>> > -------------------------------------+------------------------
>>>>> >       >       > --------------
>>>>> >       >       >       Changes (by john.elwell@...):
>>>>> >       >       >
>>>>> >       >       >        * status:  new => closed
>>>>> >       >       >        * resolution:  => invalid
>>>>> >       >       >
>>>>> >       >       >
>>>>> >       >       >       Comment:
>>>>> >       >       >
>>>>> >       >       >
>>>>> >       >       >        The text of 3.2.2 just underlines the
>>>>> > fact that there
>>>>> >       >       > are different
>>>>> >       >       >        implementations around. A PBX that
>>>>> > expects the loose
>>>>> >       >       > route mechanism to be
>>>>> >       >       >        used would fail to interwork with SSPs using a
>>>>> >       >       > different mechanism (e.g.,
>>>>> >       >       >        SIPconnect 1.0), and a PBX not
>>>>> > expecting the loose
>>>>> >       >       > route mechanism to be
>>>>> >       >       >        used would fail to interwork with a loose
>>>>> route
>>>>> >       >       > implementation (e.g.,
>>>>> >       >       >        ETSI/3GPP). Hence the urgent need for
>>>>> > a standard.
>>>>> >       >       >
>>>>> >       >       >       --
>>>>> >       >       >       Ticket URL:
>>>>> >       >       >
>>>>> >       >
>>>>> > <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
>>>>> >       >       >
>>>>> >       >       >       martini <http://tools.ietf.org/martini/>
>>>>> >       >       >
>>>>> >       >       >
>>>>> >       >       >       _______________________________________________
>>>>> >       >       >       martini mailing list
>>>>> >       >       >       martini@ietf.org
>>>>> >       >       >       https://www.ietf.org/mailman/listinfo/martini
>>>>> >       >       >
>>>>> >       >       >
>>>>> >       >       >
>>>>> >       >       >
>>>>> >       >
>>>>> >       >
>>>>> >       >
>>>>> >
>>>>> >
>>>>> >
>>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> martini mailing list
>>> martini@ietf.org
>>> https://www.ietf.org/mailman/listinfo/martini
>>>
>>>
>>
>

--00148531b7e57787100483184da2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Maybe that is indeed asking for to much.<br><br>In that case it would still=
 be usefull to be able to distinguish between the profiles, so that means y=
ou would need an indicator per profile.<br><br>/Hans Erik van Elburg<br>

<br><div class=3D"gmail_quote">On Wed, Mar 31, 2010 at 2:48 PM, Hans Erik v=
an Elburg <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf.hanserik@gmail.com">=
ietf.hanserik@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail=
_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204,=
 204, 204); padding-left: 1ex;">
Now that is pessimistic...<br><br>I thought that largely people should be a=
ble to agree on some common denominator between ETSI and SIP connect profil=
e, but maybe that is my overly optimistic naive stagnant mindset. <br><font=
 color=3D"#888888"><br clear=3D"all">

/Hans Erik van Elburg</font><div><div></div><div class=3D"h5"><br>
<br><br><div class=3D"gmail_quote">On Wed, Mar 31, 2010 at 2:32 PM, DRAGE, =
Keith (Keith) <span dir=3D"ltr">&lt;<a href=3D"mailto:keith.drage@alcatel-l=
ucent.com" target=3D"_blank">keith.drage@alcatel-lucent.com</a>&gt;</span> =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">




<div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">The problem is that I suspect noone is going to agree what=20
that profile is to be sufficiently useful.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">regards</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">Keith</font></span></div><br>
<blockquote style=3D"padding-left: 5px; margin-left: 5px; border-left: 2px =
solid rgb(0, 0, 255); margin-right: 0px;">
  <div dir=3D"ltr" align=3D"left" lang=3D"en-us">
  <hr>
  <font face=3D"Tahoma" size=3D"2"><div><b>From:</b> <a href=3D"mailto:mart=
ini-bounces@ietf.org" target=3D"_blank">martini-bounces@ietf.org</a>=20
  [mailto:<a href=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">mar=
tini-bounces@ietf.org</a>] <b>On Behalf Of </b>Hans Erik van=20
  Elburg<br></div><b>Sent:</b> Wednesday, March 31, 2010 1:24 PM<br><b>To:<=
/b>=20
  <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a=
><br><b>Subject:</b> Re: [martini] Need for a SIP/SDP profile=20
  for SIP trunking , was Re: #21: 3.2.2 describes an issue with some=20
  PBX<br></font><br></div><div><div></div><div>
  <div></div>I should have said &quot;explicit indication&quot; instead of =
&quot;option tag&quot;.=20
  Feature tags maybe more appropriate, when talking about a profile.<br><br=
 clear=3D"all">/Hans Erik van Elburg<br><br><br>
  <div class=3D"gmail_quote">On Wed, Mar 31, 2010 at 1:28 PM, Hans Erik van=
 Elburg=20
  <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf.hanserik@gmail.com" target=
=3D"_blank">ietf.hanserik@gmail.com</a>&gt;</span>=20
  wrote:<br>
  <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; margin: 0pt=
 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">Yes,=20
    I agree with that observation.<br><br>Only solving the routing issue do=
es=20
    not solve the overall problem. For that a minimum SIP/SDP profile needs=
 to=20
    be agreed upon. Also what are common denominator as codec for voice, fa=
x,=20
    dtmf etc. <br><br>The question rises if there should be an option tag t=
o=20
    signal support for a profile instead of only signalling what routing me=
thod=20
    is preferred.<br><br>BR,<br clear=3D"all">/Hans Erik van Elburg<br><br>=
<br>
    <div class=3D"gmail_quote">On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, Keit=
h (Keith)=20
    <span dir=3D"ltr">&lt;<a href=3D"mailto:keith.drage@alcatel-lucent.com"=
 target=3D"_blank">keith.drage@alcatel-lucent.com</a>&gt;</span> wrote:<br>
    <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; margin: 0=
pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">
      <div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2">So=20
      assuming that this text is accepted, I guess the key argument of prov=
iding=20
      this distinction is not that both behaviours are non-standard, but th=
at=20
      some means is needed to distinguish the two.</font></span></div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2"></font></span>=A0</div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2">While=20
      I do not have a problem with that specifically, I still have an issue=
 that=20
      providing some signalling to do this solves all the issues. There are=
 all=20
      sorts of other issues associated with what the PBX &quot;expects&quot=
; that also=20
      cause all sorts of issues, such as whether it expects a tel URI in te=
l URI=20
      format or SIP URI format, and so on, that are not signalled.=20
      </font></span></div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2"></font></span>=A0</div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2">Therefore at the end of the day, one is still going to e=
nd up with=20
      configuration information at either end of this interface that is not=
=20
      explicitly signalled, and in the absence of both sides having=20
      preconfigured knowledge of that information, the interface is not goi=
ng to=20
      work.</font></span></div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2"></font></span>=A0</div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2">regards</font></span></div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2"></font></span>=A0</div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2">Keith</font></span></div>
      <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=3D=
"Arial" size=3D"2"></font></span>=A0</div>
      <div dir=3D"ltr" align=3D"left">
      <hr>
      </div>
      <div dir=3D"ltr" align=3D"left"><font face=3D"Tahoma" size=3D"2"><b>F=
rom:</b> <a href=3D"mailto:martini-bounces@ietf.org" target=3D"_blank">mart=
ini-bounces@ietf.org</a> [mailto:<a href=3D"mailto:martini-bounces@ietf.org=
" target=3D"_blank">martini-bounces@ietf.org</a>] <b>On Behalf Of </b>Elwel=
l,=20
      John<br><b>Sent:</b> Tuesday, March 30, 2010 6:11 PM<br><b>To:</b> Ha=
ns=20
      Erik van Elburg
      <div>
      <div></div>
      <div><br><b>Cc:</b> <a href=3D"mailto:martini@ietf.org" target=3D"_bl=
ank">martini@ietf.org</a><br><b>Subject:</b> Re: [martini] #21:=20
      3.2.2 describes an issue with some PBX<br></div></div></font><br></di=
v>
      <div>
      <div></div>
      <div>
      <blockquote dir=3D"ltr" style=3D"padding-left: 5px; margin-left: 5px;=
 border-left: 2px solid rgb(0, 0, 255); margin-right: 0px;">
        <div></div>
        <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=
=3D"Arial" size=3D"2">OK,=20
        fixed in my working copy.</font></span></div>
        <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=
=3D"Arial" size=3D"2"></font></span>=A0</div>
        <div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" face=
=3D"Arial" size=3D"2">John</font></span></div><br>
        <blockquote style=3D"padding-left: 5px; margin-left: 5px; border-le=
ft: 2px solid rgb(0, 0, 255); margin-right: 0px;">
          <div dir=3D"ltr" align=3D"left" lang=3D"en-us">
          <hr>
          <font face=3D"Tahoma" size=3D"2"><b>From:</b> Hans Erik van Elbur=
g [mailto:<a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">ietf=
.hanserik@gmail.com</a>] <br><b>Sent:</b> 30 March=20
          2010 11:49<br><b>To:</b> Elwell, John<br><b>Cc:</b> <a href=3D"ma=
ilto:martini@ietf.org" target=3D"_blank">martini@ietf.org</a><br><b>Subject=
:</b> Re: [martini]=20
          #21: 3.2.2 describes an issue with some PBX<br></font><br></div>
          <div></div>Hi John,<br><br>Inline... <br clear=3D"all"><br>/Hans =
Erik van=20
          Elburg<br><br>
          <div class=3D"gmail_quote">On Mon, Mar 29, 2010 at 9:55 PM, Elwel=
l, John=20
          <span dir=3D"ltr">&lt;<a href=3D"mailto:john.elwell@siemens-enter=
prise.com" target=3D"_blank">john.elwell@siemens-enterprise.com</a>&gt;</sp=
an>=20
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; mar=
gin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">Hans=20
            Erik,<br><br>I think the point you are trying to make is that i=
t is=20
            not one-sided. The fact is, each side has different ways of wor=
king,=20
            and you need to have the two sides operating in compatible mann=
ers=20
            for it to work. In practice, I think there are other variants,=
=20
            besides the two cited in the present 3.2.2.</blockquote>
          <div>Yes. And there is no objective way to automatically determin=
e=20
          what variant the PBX or the SSP is supporting. Which is what an=
=20
          options tag could resolve.<br>=A0</div>
          <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; mar=
gin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">I=20
            would suggest:<br><br>=A0 =A0 =A0 =A0&lt;t&gt;Even where=20
            all information needed by the SIP-PBX is provided, in some=20
            deployments inbound SIP requests from the SSP have the register=
ed=20
            Contact URI in the Request-URI, whereas in other deployments in=
bound=20
            SIP requests have the intended target (AOR) in the Request-URI =
and=20
            the Contact URI in the Route header field. There are other vari=
ants=20
            too. Interoperability problems arise when a PBX designed for or=
=20
            configured for one variant attempts to interwork with an SSP=20
            designed for or configured for another=20
          variant.&lt;/t&gt;<br></blockquote>
          <div>Yes, slightly modified to add the objective means=20
          issue:<br>=A0&lt;t&gt;Even where all information needed by the=20
          SIP-PBX is provided, in some deployments inbound SIP requests fro=
m the=20
          SSP have the registered PBX Contact URI in the Request-URI, where=
as in=20
          other deployments inbound SIP requests have the intended target P=
BX=20
          user (AOR) in the Request-URI and the Contact URI in the Route he=
ader=20
          field. There are other variants too. Interoperability problems ar=
ise=20
          when a PBX designed for or configured for one variant attempts to=
=20
          interwork with an SSP designed for or configured for another vari=
ant.=20
          There is currently no objective means in the signalling during=20
          registration for either party to discover what mechanism the othe=
r=20
          side supports.&lt;/t&gt;<br>=A0</div>
          <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; mar=
gin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">To=20
            accompany this, I think the title of the section should be chan=
ged=20
            too: &quot;Inconsistent placement of information in inbound req=
uests&quot;<br>
            <div><br></div></blockquote>
          <div>Yes, slightly modified to make it more specific: &quot;Incon=
sistent=20
          placement of target URI information in inbound=20
          requests&quot;.<br>=A0</div>
          <blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; mar=
gin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">
            <div>John<br><br>&gt; -----Original Message-----<br>&gt; From: =
Hans=20
            Erik van Elburg [mailto:<a href=3D"mailto:ietf.hanserik@gmail.c=
om" target=3D"_blank">ietf.hanserik@gmail.com</a>]<br></div>
            <div>
            <div></div>
            <div>&gt; Sent: 29 March 2010 17:27<br>&gt; To: Elwell, John<br=
>&gt;=20
            Cc: <a href=3D"mailto:martini@ietf.org" target=3D"_blank">marti=
ni@ietf.org</a><br>&gt; Subject: Re: [martini]=20
            #21: 3.2.2 describes an issue with some PBX<br>&gt;<br>&gt; Hi=
=20
            John,<br>&gt;<br>&gt; I was just trying to find a text that=20
            describes the issue.<br>&gt;<br>&gt; But now the issue reads li=
ke=20
            &quot;some PBX like apples, some like<br>&gt; bananas&quot;. To=
 me that does=20
            not sound like a usefull issue to<br>&gt; describe in an=20
            RFC.<br>&gt;<br>&gt; So I think one or two more sentence would =
make=20
            clear why this<br>&gt; is an issue.<br>&gt;<br>&gt; I think the=
re is=20
            multiple underlying issues here:<br>&gt; - PBX have different S=
IP=20
            profiles or all SIP-PBX are different<br>&gt; - PBX support SIP=
=20
            trunking flavour A, or support SIP trunking<br>&gt; flavour=20
            B<br>&gt; - SSP systems don&#39;t know what mechanism the PBX s=
upport=20
            (can<br>&gt; be resolved with explicit indicator, this draft=20
            proposes an<br>&gt; indicator for flavour B but for another pur=
pose=20
            it seems)<br>&gt; - PBX do not know what SIP trunking flavour t=
he=20
            SSP supports<br>&gt; (not addressed it seems)<br>&gt;<br>&gt; I=
=20
            don&#39;t seem to have a lucky hand with proposing an improved<=
br>&gt;=20
            text, so maybe you should have a go at it.<br>&gt;<br>&gt;=20
            BR,<br>&gt; /Hans Erik van Elburg<br>&gt;<br>&gt; p.s. I never =
said=20
            or implied that a SIP-PBX shall implement<br>&gt; IMS. But it w=
ould=20
            be really, really, really good if they<br>&gt; would interwork =
on=20
            the UNI with the IMS business trunking. =A0I<br>&gt; think that=
=20
            should also be in your interest and in fact you<br>&gt; have be=
en=20
            part of that work...<br>&gt;<br>&gt;<br>&gt;<br>&gt; On Mon, Ma=
r 29,=20
            2010 at 5:56 PM, Elwell, John<br>&gt; &lt;<a href=3D"mailto:joh=
n.elwell@siemens-enterprise.com" target=3D"_blank">john.elwell@siemens-ente=
rprise.com</a>&gt;=20
            wrote:<br>&gt;<br>&gt;<br>&gt; =A0 =A0 =A0 Hans=20
            Erik,<br>&gt;<br>&gt; =A0 =A0 =A0 As an individual, I=20
            disagree with the proposed text,<br>&gt; since it is misleading=
. The=20
            &quot;international standards&quot; to<br>&gt; which you prefer=
 are standards=20
            specific to an IMS<br>&gt; environment. The implication of the=
=20
            wording as proposed is<br>&gt; that SIP-PBXs ought to implement=
 IMS=20
            specifications. And as<br>&gt; Hadriel points out, implementing=
=20
            those IMS specifications<br>&gt; does not eliminate the problem=
s=20
            that the SIPconnect people<br>&gt; are trying to solve. I belie=
ve=20
            the existing text in draft-03<br>&gt; is=20
            sufficient.<br>&gt;<br>&gt;<br>&gt; =A0 =A0 =A0=20
            John<br>&gt;<br>&gt; =A0 =A0 =A0 &gt; -----Original=20
            Message-----<br>&gt; =A0 =A0 =A0 &gt; From: Hans Erik van=20
            Elburg [mailto:<a href=3D"mailto:ietf.hanserik@gmail.com" targe=
t=3D"_blank">ietf.hanserik@gmail.com</a>]<br>&gt;<br>&gt; =A0=20
            =A0 =A0 &gt; Sent: 26 March 2010 23:03<br>&gt; =A0 =A0=20
            =A0 &gt; To: Elwell, John<br>&gt; =A0 =A0 =A0 &gt; Cc:=20
            <a href=3D"mailto:martini@ietf.org" target=3D"_blank">martini@i=
etf.org</a><br>&gt; =A0 =A0 =A0 &gt;=20
            Subject: Re: [martini] #21: 3.2.2 describes an issue<br>&gt; wi=
th=20
            some PBX<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt; I will not argue with you about the validity of that=
=20
            argument.<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt; Can you agree to the modified text?<br>&gt; =A0=20
            =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; &quot;Request-URI=20
            vs. loose-route acceptance<br>&gt; =A0 =A0 =A0 &gt; Some=20
            IP-PBX do not implement international standards or SIP<br>&gt;=
=20
            =A0 =A0 =A0 &gt; profiles for SIP trunking. As a=20
            consequence some SIP-PBXs<br>&gt; =A0 =A0 =A0 &gt; expect=20
            that inbound SIP requests from the SSP will have the<br>&gt; =
=A0=20
            =A0 =A0 &gt; registered Contact-URI in the Request-URI, and=20
            thus not<br>&gt; =A0 =A0 =A0 &gt; interoperate with the=20
            loose-route scheme of 3GPP and ETSI.<br>&gt; =A0 =A0 =A0=20
            &gt; Other SIP-PBXs are fine with the Request-URI being the<br>=
&gt;=20
            =A0 =A0 =A0 &gt; intended target, but cannot handle=20
            receiving a Route header<br>&gt; =A0 =A0 =A0 &gt; field=20
            identifying their registered Contact-URI as a<br>&gt; =A0 =A0=
=20
            =A0 &gt; loose-route entry.&quot;<br>&gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; BR,<br>&gt; =A0 =A0=20
            =A0 &gt; /Hans Erik van Elburg<br>&gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt; On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John<br>&gt; =A0=
=20
            =A0 =A0 &gt; &lt;<a href=3D"mailto:john.elwell@siemens-enterpri=
se.com" target=3D"_blank">john.elwell@siemens-enterprise.com</a>&gt;=20
            wrote:<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            The IETF does not have a mechanism, and that is the<br>&gt; =A0=
=20
            =A0 =A0 &gt; reason for the MARTINI work. In particular, the=20
            IETF has not<br>&gt; =A0 =A0 =A0 &gt; published the=20
            so-called loose-route mechanism. Hence the<br>&gt; =A0 =A0=20
            =A0 &gt; reason for the IETF, as owner of SIP, to publish a=20
            mechanism<br>&gt; =A0 =A0 =A0 &gt; for bulk=20
            registrations.<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 John<br>&gt; =A0 =A0=20
            =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt; -----Original=20
            Message-----<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt; From: Hans Erik van Elburg<br>&gt; [mailto:<a href=3D"mail=
to:ietf.hanserik@gmail.com" target=3D"_blank">ietf.hanserik@gmail.com</a>]<=
br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt; Sent: 26 March 2010=20
            02:21<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            To: <a href=3D"mailto:trac@localhost.amsl.com" target=3D"_blank=
">trac@localhost.amsl.com</a><br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt; Cc: Elwell, John; <a href=3D"mailto:m=
artini@ietf.org" target=3D"_blank">martini@ietf.org</a><br>&gt; =A0 =A0 =A0=
 &gt;=20
            =A0 =A0 =A0 &gt; Subject: Re: [martini] #21: 3.2.2=20
            describes an issue<br>&gt; =A0 =A0 =A0 &gt; with some=20
            PBX<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            Then you should rephrase to what the real issue is:<br>&gt; =A0=
=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; &quot;<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 &gt; Request-URI vs. loose-route=20
            acceptance<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            Some IP-PBX do not implement international<br>&gt; standards or=
=20
            SIP<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            profiles for SIP trunking. As a consequence<br>&gt; some=20
            SIP-PBXs<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            expect that inbound SIP requests from the SSP<br>&gt; will have=
=20
            the<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            registered Contact-URI in the Request-URI,<br>&gt; and thus=20
            not<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            interoperate with the loose-route scheme of<br>&gt; 3GPP and=20
            ETSI.<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            Other SIP-PBXs are fine with the Request-URI being the<br>&gt;=
=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; intended target,=20
            but cannot handle receiving<br>&gt; a Route header<br>&gt; =A0=
=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; field identifying their=20
            registered Contact-URI as a<br>&gt; =A0 =A0 =A0 &gt; =A0=20
            =A0 =A0 &gt; loose-route entry.&quot;<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0=20
            =A0 =A0 &gt; Is this an issue, yes. Does introducing yet=20
            another<br>&gt; =A0 =A0 =A0 &gt; profile help? No.<br>&gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; /Hans Erik van=20
            Elburg<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; On=20
            Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker<br>&gt; =A0=
=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; &lt;<a href=3D"mailto:trac@tools.=
ietf.org" target=3D"_blank">trac@tools.ietf.org</a>&gt; wrote:<br>&gt; =A0=
=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 #21: 3.2.2=20
            describes an issue with some PBX<br>&gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0=20
            =A0 =A0 &gt;<br>&gt;=20
            -------------------------------------+------------------------<=
br>&gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            --------------<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 =A0Reporter:=20
            =A0ietf.hanserik@...<br>&gt; | =A0 =A0 =A0=20
            =A0Owner:<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 =A0 =A0 Type: =A0defect =A0 =A0=20
            =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>&gt; =A0=20
            =A0 =A0 &gt; Status: =A0closed<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Priority:=20
            =A0minor =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=20
            =A0 =A0|<br>&gt; =A0 =A0 =A0 &gt; Milestone:=20
            =A0milestone1<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 Component: =A0reqs =A0 =A0=20
            =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>&gt;=20
            =A0 =A0 =A0 &gt; Version: =A01.0<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0Severity:=20
            =A0In WG Last Call =A0 =A0 =A0 =A0 =A0|<br>&gt;=20
            =A0 =A0 =A0 &gt; Resolution: =A0invalid<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            =A0Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0=20
            =A0 =A0 =A0 =A0 =A0 =A0 |<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt;<br>&gt;=20
            -------------------------------------+------------------------<=
br>&gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            --------------<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 Changes (by=20
            john.elwell@...):<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 =A0* status: =A0new =3D&gt;=20
            closed<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 =A0* resolution: =A0=3D&gt; invalid<br>&gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            Comment:<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 =A0The text of 3.2.2 just underlines=20
            the<br>&gt; fact that there<br>&gt; =A0 =A0 =A0 &gt; =A0=20
            =A0 =A0 &gt; are different<br>&gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 =A0implementations=20
            around. A PBX that<br>&gt; expects the loose<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt; route mechanism to be<br>&gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 =A0used would fail to interwork with SSPs using a<br>&gt;=
=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt; different=20
            mechanism (e.g.,<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 =A0SIPconnect 1.0), and a PBX=20
            not<br>&gt; expecting the loose<br>&gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 &gt; route mechanism to be<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            =A0used would fail to interwork with a loose route<br>&gt; =A0=
=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; implementation=20
            (e.g.,<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 =A0ETSI/3GPP). Hence the urgent need=20
            for<br>&gt; a standard.<br>&gt; =A0 =A0 =A0 &gt; =A0=20
            =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 --<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0 Ticket=20
            URL:<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; &lt;<a href=3D"http://tra=
c.tools.ietf.org/wg/martini/trac/ticket/21#comment:1" target=3D"_blank">htt=
p://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1</a>&gt;<br>&gt;=
=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            martini &lt;<a href=3D"http://tools.ietf.org/martini/" target=
=3D"_blank">http://tools.ietf.org/martini/</a>&gt;<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            _______________________________________________<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt; =A0 =A0 =A0=20
            martini mailing list<br>&gt; =A0 =A0 =A0 &gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 <a href=3D"mailto:martini@ietf.org" target=
=3D"_blank">martini@ietf.org</a><br>&gt; =A0 =A0 =A0 &gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 <a href=3D"https://www.ietf.org/ma=
ilman/listinfo/martini" target=3D"_blank">https://www.ietf.org/mailman/list=
info/martini</a><br>&gt;=20
            =A0 =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0=20
            =A0 =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0=20
            =A0 &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt;<br>&gt; =A0 =A0 =A0 &gt;<br>&gt; =A0 =A0 =A0=20
            &gt;<br>&gt;<br>&gt;<br>&gt;=20
        </div></div></blockquote></div><br></blockquote></blockquote></div>=
</div></div></blockquote></div><br><br>____________________________________=
___________<br>martini=20
    mailing list<br><a href=3D"mailto:martini@ietf.org" target=3D"_blank">m=
artini@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/mar=
tini" target=3D"_blank">https://www.ietf.org/mailman/listinfo/martini</a><b=
r><br>

</blockquote></div><br></div></div></blockquote></div>
</blockquote></div><br>
</div></div></blockquote></div><br>

--00148531b7e57787100483184da2--

From keith.drage@alcatel-lucent.com  Wed Mar 31 05:58:12 2010
Return-Path: <keith.drage@alcatel-lucent.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 9664D3A68EF for <martini@core3.amsl.com>; Wed, 31 Mar 2010 05:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.083
X-Spam-Level: 
X-Spam-Status: No, score=-2.083 tagged_above=-999 required=5 tests=[AWL=-0.965, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
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 TT4+CNP0hL4j for <martini@core3.amsl.com>; Wed, 31 Mar 2010 05:58:10 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 7AE533A68D5 for <martini@ietf.org>; Wed, 31 Mar 2010 05:58:09 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o2VCvDK0031073 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 31 Mar 2010 14:58:33 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Wed, 31 Mar 2010 14:57:37 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>
Date: Wed, 31 Mar 2010 14:57:36 +0200
Thread-Topic: [martini] Need for a SIP/SDP profile for SIP trunking ,	was Re: 	#21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrQ0I4ecygs8bZyRm6/KdOpapCuvQAAM93g
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE20D1C82B3@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <w2v9ae56b1e1003310428o6fc07243j294b603eec953a1a@mail.gmail.com> <m2k9ae56b1e1003310523zc70f6a83ub0e5b1bdaeddd5ce@mail.gmail.com> <EDC0A1AE77C57744B664A310A0B23AE20D1C8293@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <m2v9ae56b1e1003310548i739c29c1t8080612ae5b4eea7@mail.gmail.com>
In-Reply-To: <m2v9ae56b1e1003310548i739c29c1t8080612ae5b4eea7@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_EDC0A1AE77C57744B664A310A0B23AE20D1C82B3FRMRSSXCHMBSC3d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re: 	#21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 12:58:12 -0000

--_000_EDC0A1AE77C57744B664A310A0B23AE20D1C82B3FRMRSSXCHMBSC3d_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I wasn't trying to be pessimistic. It was more along the lines that no matt=
er how much we tie down in the profile, there will always be another bit of=
 configuration data that will need to be known at both ends.

We have already discussed significantly the set of numbers in use at both s=
ides of the interface, and decided that these are outside the scope of mart=
ini, but get these misconfigured and things will not work (neither will a p=
hone where I try and register a number that does not belong to me).

regards

Keith

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Hans Erik van Elburg
Sent: Wednesday, March 31, 2010 1:49 PM
To: DRAGE, Keith (Keith)
Cc: martini@ietf.org
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re=
: #21: 3.2.2 describes an issue with some PBX

Now that is pessimistic...

I thought that largely people should be able to agree on some common denomi=
nator between ETSI and SIP connect profile, but maybe that is my overly opt=
imistic naive stagnant mindset.

/Hans Erik van Elburg


On Wed, Mar 31, 2010 at 2:32 PM, DRAGE, Keith (Keith) <keith.drage@alcatel-=
lucent.com<mailto:keith.drage@alcatel-lucent.com>> wrote:
The problem is that I suspect noone is going to agree what that profile is =
to be sufficiently useful.

regards

Keith

________________________________
From: martini-bounces@ietf.org<mailto:martini-bounces@ietf.org> [mailto:mar=
tini-bounces@ietf.org<mailto:martini-bounces@ietf.org>] On Behalf Of Hans E=
rik van Elburg
Sent: Wednesday, March 31, 2010 1:24 PM
To: martini@ietf.org<mailto:martini@ietf.org>
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re=
: #21: 3.2.2 describes an issue with some PBX

I should have said "explicit indication" instead of "option tag". Feature t=
ags maybe more appropriate, when talking about a profile.

/Hans Erik van Elburg


On Wed, Mar 31, 2010 at 1:28 PM, Hans Erik van Elburg <ietf.hanserik@gmail.=
com<mailto:ietf.hanserik@gmail.com>> wrote:
Yes, I agree with that observation.

Only solving the routing issue does not solve the overall problem. For that=
 a minimum SIP/SDP profile needs to be agreed upon. Also what are common de=
nominator as codec for voice, fax, dtmf etc.

The question rises if there should be an option tag to signal support for a=
 profile instead of only signalling what routing method is preferred.

BR,
/Hans Erik van Elburg


On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, Keith (Keith) <keith.drage@alcatel-=
lucent.com<mailto:keith.drage@alcatel-lucent.com>> wrote:
So assuming that this text is accepted, I guess the key argument of providi=
ng this distinction is not that both behaviours are non-standard, but that =
some means is needed to distinguish the two.

While I do not have a problem with that specifically, I still have an issue=
 that providing some signalling to do this solves all the issues. There are=
 all sorts of other issues associated with what the PBX "expects" that also=
 cause all sorts of issues, such as whether it expects a tel URI in tel URI=
 format or SIP URI format, and so on, that are not signalled.

Therefore at the end of the day, one is still going to end up with configur=
ation information at either end of this interface that is not explicitly si=
gnalled, and in the absence of both sides having preconfigured knowledge of=
 that information, the interface is not going to work.

regards

Keith

________________________________
From: martini-bounces@ietf.org<mailto:martini-bounces@ietf.org> [mailto:mar=
tini-bounces@ietf.org<mailto:martini-bounces@ietf.org>] On Behalf Of Elwell=
, John
Sent: Tuesday, March 30, 2010 6:11 PM
To: Hans Erik van Elburg

Cc: martini@ietf.org<mailto:martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

OK, fixed in my working copy.

John

________________________________
From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto:ietf.hans=
erik@gmail.com>]
Sent: 30 March 2010 11:49
To: Elwell, John
Cc: martini@ietf.org<mailto:martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

Hi John,

Inline...

/Hans Erik van Elburg

On Mon, Mar 29, 2010 at 9:55 PM, Elwell, John <john.elwell@siemens-enterpri=
se.com<mailto:john.elwell@siemens-enterprise.com>> wrote:
Hans Erik,

I think the point you are trying to make is that it is not one-sided. The f=
act is, each side has different ways of working, and you need to have the t=
wo sides operating in compatible manners for it to work. In practice, I thi=
nk there are other variants, besides the two cited in the present 3.2.2.
Yes. And there is no objective way to automatically determine what variant =
the PBX or the SSP is supporting. Which is what an options tag could resolv=
e.

I would suggest:

       <t>Even where all information needed by the SIP-PBX is provided, in =
some deployments inbound SIP requests from the SSP have the registered Cont=
act URI in the Request-URI, whereas in other deployments inbound SIP reques=
ts have the intended target (AOR) in the Request-URI and the Contact URI in=
 the Route header field. There are other variants too. Interoperability pro=
blems arise when a PBX designed for or configured for one variant attempts =
to interwork with an SSP designed for or configured for another variant.</t=
>
Yes, slightly modified to add the objective means issue:
 <t>Even where all information needed by the SIP-PBX is provided, in some d=
eployments inbound SIP requests from the SSP have the registered PBX Contac=
t URI in the Request-URI, whereas in other deployments inbound SIP requests=
 have the intended target PBX user (AOR) in the Request-URI and the Contact=
 URI in the Route header field. There are other variants too. Interoperabil=
ity problems arise when a PBX designed for or configured for one variant at=
tempts to interwork with an SSP designed for or configured for another vari=
ant. There is currently no objective means in the signalling during registr=
ation for either party to discover what mechanism the other side supports.<=
/t>

To accompany this, I think the title of the section should be changed too: =
"Inconsistent placement of information in inbound requests"

Yes, slightly modified to make it more specific: "Inconsistent placement of=
 target URI information in inbound requests".

John

> -----Original Message-----
> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto:ietf.ha=
nserik@gmail.com>]
> Sent: 29 March 2010 17:27
> To: Elwell, John
> Cc: martini@ietf.org<mailto:martini@ietf.org>
> Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>
> Hi John,
>
> I was just trying to find a text that describes the issue.
>
> But now the issue reads like "some PBX like apples, some like
> bananas". To me that does not sound like a usefull issue to
> describe in an RFC.
>
> So I think one or two more sentence would make clear why this
> is an issue.
>
> I think there is multiple underlying issues here:
> - PBX have different SIP profiles or all SIP-PBX are different
> - PBX support SIP trunking flavour A, or support SIP trunking
> flavour B
> - SSP systems don't know what mechanism the PBX support (can
> be resolved with explicit indicator, this draft proposes an
> indicator for flavour B but for another purpose it seems)
> - PBX do not know what SIP trunking flavour the SSP supports
> (not addressed it seems)
>
> I don't seem to have a lucky hand with proposing an improved
> text, so maybe you should have a go at it.
>
> BR,
> /Hans Erik van Elburg
>
> p.s. I never said or implied that a SIP-PBX shall implement
> IMS. But it would be really, really, really good if they
> would interwork on the UNI with the IMS business trunking.  I
> think that should also be in your interest and in fact you
> have been part of that work...
>
>
>
> On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John
> <john.elwell@siemens-enterprise.com<mailto:john.elwell@siemens-enterprise=
.com>> wrote:
>
>
>       Hans Erik,
>
>       As an individual, I disagree with the proposed text,
> since it is misleading. The "international standards" to
> which you prefer are standards specific to an IMS
> environment. The implication of the wording as proposed is
> that SIP-PBXs ought to implement IMS specifications. And as
> Hadriel points out, implementing those IMS specifications
> does not eliminate the problems that the SIPconnect people
> are trying to solve. I believe the existing text in draft-03
> is sufficient.
>
>
>       John
>
>       > -----Original Message-----
>       > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto=
:ietf.hanserik@gmail.com>]
>
>       > Sent: 26 March 2010 23:03
>       > To: Elwell, John
>       > Cc: martini@ietf.org<mailto:martini@ietf.org>
>       > Subject: Re: [martini] #21: 3.2.2 describes an issue
> with some PBX
>       >
>       > I will not argue with you about the validity of that argument.
>       >
>       > Can you agree to the modified text?
>       >
>       > "Request-URI vs. loose-route acceptance
>       > Some IP-PBX do not implement international standards or SIP
>       > profiles for SIP trunking. As a consequence some SIP-PBXs
>       > expect that inbound SIP requests from the SSP will have the
>       > registered Contact-URI in the Request-URI, and thus not
>       > interoperate with the loose-route scheme of 3GPP and ETSI.
>       > Other SIP-PBXs are fine with the Request-URI being the
>       > intended target, but cannot handle receiving a Route header
>       > field identifying their registered Contact-URI as a
>       > loose-route entry."
>       >
>       > BR,
>       > /Hans Erik van Elburg
>       >
>       >
>       > On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
>       > <john.elwell@siemens-enterprise.com<mailto:john.elwell@siemens-en=
terprise.com>> wrote:
>       >
>       >
>       >       The IETF does not have a mechanism, and that is the
>       > reason for the MARTINI work. In particular, the IETF has not
>       > published the so-called loose-route mechanism. Hence the
>       > reason for the IETF, as owner of SIP, to publish a mechanism
>       > for bulk registrations.
>       >
>       >       John
>       >
>       >
>       >       > -----Original Message-----
>       >       > From: Hans Erik van Elburg
> [mailto:ietf.hanserik@gmail.com<mailto:ietf.hanserik@gmail.com>]
>       >       > Sent: 26 March 2010 02:21
>       >       > To: trac@localhost.amsl.com<mailto:trac@localhost.amsl.co=
m>
>       >       > Cc: Elwell, John; martini@ietf.org<mailto:martini@ietf.or=
g>
>       >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
>       > with some PBX
>       >       >
>       >       >
>       >       > Then you should rephrase to what the real issue is:
>       >       > "
>       >       >
>       >       >
>       >       > Request-URI vs. loose-route acceptance
>       >       >
>       >       >
>       >       > Some IP-PBX do not implement international
> standards or SIP
>       >       > profiles for SIP trunking. As a consequence
> some SIP-PBXs
>       >       > expect that inbound SIP requests from the SSP
> will have the
>       >       > registered Contact-URI in the Request-URI,
> and thus not
>       >       > interoperate with the loose-route scheme of
> 3GPP and ETSI.
>       >       > Other SIP-PBXs are fine with the Request-URI being the
>       >       > intended target, but cannot handle receiving
> a Route header
>       >       > field identifying their registered Contact-URI as a
>       >       > loose-route entry."
>       >       >
>       >       >
>       >       > Is this an issue, yes. Does introducing yet another
>       > profile help? No.
>       >       >
>       >       > /Hans Erik van Elburg
>       >       >
>       >       >
>       >       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
>       >       > <trac@tools.ietf.org<mailto:trac@tools.ietf.org>> wrote:
>       >       >
>       >       >
>       >       >       #21: 3.2.2 describes an issue with some PBX
>       >       >
>       >       >
> -------------------------------------+------------------------
>       >       > --------------
>       >       >        Reporter:  ietf.hanserik@...
> |        Owner:
>       >       >
>       >       >           Type:  defect                   |
>       > Status:  closed
>       >       >
>       >       >        Priority:  minor                    |
>       > Milestone:  milestone1
>       >       >       Component:  reqs                     |
>       > Version:  1.0
>       >       >
>       >       >        Severity:  In WG Last Call          |
>       > Resolution:  invalid
>       >       >        Keywords:                           |
>       >       >
>       >       >
> -------------------------------------+------------------------
>       >       > --------------
>       >       >       Changes (by john.elwell@...):
>       >       >
>       >       >        * status:  new =3D> closed
>       >       >        * resolution:  =3D> invalid
>       >       >
>       >       >
>       >       >       Comment:
>       >       >
>       >       >
>       >       >        The text of 3.2.2 just underlines the
> fact that there
>       >       > are different
>       >       >        implementations around. A PBX that
> expects the loose
>       >       > route mechanism to be
>       >       >        used would fail to interwork with SSPs using a
>       >       > different mechanism (e.g.,
>       >       >        SIPconnect 1.0), and a PBX not
> expecting the loose
>       >       > route mechanism to be
>       >       >        used would fail to interwork with a loose route
>       >       > implementation (e.g.,
>       >       >        ETSI/3GPP). Hence the urgent need for
> a standard.
>       >       >
>       >       >       --
>       >       >       Ticket URL:
>       >       >
>       >
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
>       >       >
>       >       >       martini <http://tools.ietf.org/martini/>
>       >       >
>       >       >
>       >       >       _______________________________________________
>       >       >       martini mailing list
>       >       >       martini@ietf.org<mailto:martini@ietf.org>
>       >       >       https://www.ietf.org/mailman/listinfo/martini
>       >       >
>       >       >
>       >       >
>       >       >
>       >
>       >
>       >
>
>
>



_______________________________________________
martini mailing list
martini@ietf.org<mailto:martini@ietf.org>
https://www.ietf.org/mailman/listinfo/martini




--_000_EDC0A1AE77C57744B664A310A0B23AE20D1C82B3FRMRSSXCHMBSC3d_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D092575412-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I wasn't trying to be pessimistic. It was more alo=
ng the=20
lines that no matter how much we tie down in the profile, there will always=
 be=20
another bit of configuration data that will need to be known at both=20
ends.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D092575412-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D092575412-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>We have already discussed significantly the set of=
 numbers=20
in use at both sides of the interface, and decided that these are outside t=
he=20
scope of martini, but get these misconfigured and things will not work (nei=
ther=20
will a phone where I try and register a number that does not belong to=20
me).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D092575412-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D092575412-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>regards</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D092575412-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D092575412-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Keith</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> martini-bounces@ietf.org=20
  [mailto:martini-bounces@ietf.org] <B>On Behalf Of </B>Hans Erik van=20
  Elburg<BR><B>Sent:</B> Wednesday, March 31, 2010 1:49 PM<BR><B>To:</B> DR=
AGE,=20
  Keith (Keith)<BR><B>Cc:</B> martini@ietf.org<BR><B>Subject:</B> Re: [mart=
ini]=20
  Need for a SIP/SDP profile for SIP trunking , was Re: #21: 3.2.2 describe=
s an=20
  issue with some PBX<BR></FONT><BR></DIV>
  <DIV></DIV>Now that is pessimistic...<BR><BR>I thought that largely peopl=
e=20
  should be able to agree on some common denominator between ETSI and SIP=20
  connect profile, but maybe that is my overly optimistic naive stagnant=20
  mindset. <BR><BR clear=3Dall>/Hans Erik van Elburg<BR><BR><BR>
  <DIV class=3Dgmail_quote>On Wed, Mar 31, 2010 at 2:32 PM, DRAGE, Keith (K=
eith)=20
  <SPAN dir=3Dltr>&lt;<A=20
  href=3D"mailto:keith.drage@alcatel-lucent.com">keith.drage@alcatel-lucent=
.com</A>&gt;</SPAN>=20
  wrote:<BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(2=
04,204,204) 1px solid">
    <DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff si=
ze=3D2>The=20
    problem is that I suspect noone is going to agree what that profile is =
to be=20
    sufficiently useful.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=20
    size=3D2>regards</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=20
    size=3D2>Keith</FONT></SPAN></DIV><BR>
    <BLOCKQUOTE=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,0,255)=
 2px solid; MARGIN-RIGHT: 0px">
      <DIV lang=3Den-us dir=3Dltr align=3Dleft>
      <HR>
      <FONT face=3DTahoma size=3D2>
      <DIV class=3Dim><B>From:</B> <A href=3D"mailto:martini-bounces@ietf.o=
rg"=20
      target=3D_blank>martini-bounces@ietf.org</A> [mailto:<A=20
      href=3D"mailto:martini-bounces@ietf.org"=20
      target=3D_blank>martini-bounces@ietf.org</A>] <B>On Behalf Of </B>Han=
s Erik=20
      van Elburg<BR></DIV><B>Sent:</B> Wednesday, March 31, 2010 1:24=20
      PM<BR><B>To:</B> <A href=3D"mailto:martini@ietf.org"=20
      target=3D_blank>martini@ietf.org</A><BR><B>Subject:</B> Re: [martini]=
 Need=20
      for a SIP/SDP profile for SIP trunking , was Re: #21: 3.2.2 describes=
 an=20
      issue with some PBX<BR></FONT><BR></DIV>
      <DIV>
      <DIV></DIV>
      <DIV class=3Dh5>
      <DIV></DIV>I should have said "explicit indication" instead of "optio=
n=20
      tag". Feature tags maybe more appropriate, when talking about a=20
      profile.<BR><BR clear=3Dall>/Hans Erik van Elburg<BR><BR><BR>
      <DIV class=3Dgmail_quote>On Wed, Mar 31, 2010 at 1:28 PM, Hans Erik v=
an=20
      Elburg <SPAN dir=3Dltr>&lt;<A href=3D"mailto:ietf.hanserik@gmail.com"=
=20
      target=3D_blank>ietf.hanserik@gmail.com</A>&gt;</SPAN> wrote:<BR>
      <BLOCKQUOTE class=3Dgmail_quote=20
      style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: r=
gb(204,204,204) 1px solid">Yes,=20
        I agree with that observation.<BR><BR>Only solving the routing issu=
e=20
        does not solve the overall problem. For that a minimum SIP/SDP prof=
ile=20
        needs to be agreed upon. Also what are common denominator as codec =
for=20
        voice, fax, dtmf etc. <BR><BR>The question rises if there should be=
 an=20
        option tag to signal support for a profile instead of only signalli=
ng=20
        what routing method is preferred.<BR><BR>BR,<BR clear=3Dall>/Hans E=
rik van=20
        Elburg<BR><BR><BR>
        <DIV class=3Dgmail_quote>On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, Ke=
ith=20
        (Keith) <SPAN dir=3Dltr>&lt;<A=20
        href=3D"mailto:keith.drage@alcatel-lucent.com"=20
        target=3D_blank>keith.drage@alcatel-lucent.com</A>&gt;</SPAN> wrote=
:<BR>
        <BLOCKQUOTE class=3Dgmail_quote=20
        style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT:=
 rgb(204,204,204) 1px solid">
          <DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff size=3D2>So=20
          assuming that this text is accepted, I guess the key argument of=
=20
          providing this distinction is not that both behaviours are=20
          non-standard, but that some means is needed to distinguish the=20
          two.</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2>While I do not have a problem with that specifically, I =
still=20
          have an issue that providing some signalling to do this solves al=
l the=20
          issues. There are all sorts of other issues associated with what =
the=20
          PBX "expects" that also cause all sorts of issues, such as whethe=
r it=20
          expects a tel URI in tel URI format or SIP URI format, and so on,=
 that=20
          are not signalled. </FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2>Therefore at the end of the day, one is still going to e=
nd up=20
          with configuration information at either end of this interface th=
at is=20
          not explicitly signalled, and in the absence of both sides having=
=20
          preconfigured knowledge of that information, the interface is not=
=20
          going to work.</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2>regards</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2>Keith</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft>
          <HR>
          </DIV>
          <DIV dir=3Dltr align=3Dleft><FONT face=3DTahoma size=3D2><B>From:=
</B> <A=20
          href=3D"mailto:martini-bounces@ietf.org"=20
          target=3D_blank>martini-bounces@ietf.org</A> [mailto:<A=20
          href=3D"mailto:martini-bounces@ietf.org"=20
          target=3D_blank>martini-bounces@ietf.org</A>] <B>On Behalf Of=20
          </B>Elwell, John<BR><B>Sent:</B> Tuesday, March 30, 2010 6:11=20
          PM<BR><B>To:</B> Hans Erik van Elburg=20
          <DIV>
          <DIV></DIV>
          <DIV><BR><B>Cc:</B> <A href=3D"mailto:martini@ietf.org"=20
          target=3D_blank>martini@ietf.org</A><BR><B>Subject:</B> Re: [mart=
ini]=20
          #21: 3.2.2 describes an issue with some=20
          PBX<BR></DIV></DIV></FONT><BR></DIV>
          <DIV>
          <DIV></DIV>
          <DIV>
          <BLOCKQUOTE dir=3Dltr=20
          style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,=
0,255) 2px solid; MARGIN-RIGHT: 0px">
            <DIV></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0=
000ff=20
            size=3D2>OK, fixed in my working copy.</FONT></SPAN></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0=
000ff=20
            size=3D2></FONT></SPAN>&nbsp;</DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0=
000ff=20
            size=3D2>John</FONT></SPAN></DIV><BR>
            <BLOCKQUOTE=20
            style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(=
0,0,255) 2px solid; MARGIN-RIGHT: 0px">
              <DIV lang=3Den-us dir=3Dltr align=3Dleft>
              <HR>
              <FONT face=3DTahoma size=3D2><B>From:</B> Hans Erik van Elbur=
g=20
              [mailto:<A href=3D"mailto:ietf.hanserik@gmail.com"=20
              target=3D_blank>ietf.hanserik@gmail.com</A>] <BR><B>Sent:</B>=
 30=20
              March 2010 11:49<BR><B>To:</B> Elwell, John<BR><B>Cc:</B> <A=
=20
              href=3D"mailto:martini@ietf.org"=20
              target=3D_blank>martini@ietf.org</A><BR><B>Subject:</B> Re:=20
              [martini] #21: 3.2.2 describes an issue with some=20
              PBX<BR></FONT><BR></DIV>
              <DIV></DIV>Hi John,<BR><BR>Inline... <BR clear=3Dall><BR>/Han=
s Erik=20
              van Elburg<BR><BR>
              <DIV class=3Dgmail_quote>On Mon, Mar 29, 2010 at 9:55 PM, Elw=
ell,=20
              John <SPAN dir=3Dltr>&lt;<A=20
              href=3D"mailto:john.elwell@siemens-enterprise.com"=20
              target=3D_blank>john.elwell@siemens-enterprise.com</A>&gt;</S=
PAN>=20
              wrote:<BR>
              <BLOCKQUOTE class=3Dgmail_quote=20
              style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER=
-LEFT: rgb(204,204,204) 1px solid">Hans=20
                Erik,<BR><BR>I think the point you are trying to make is th=
at it=20
                is not one-sided. The fact is, each side has different ways=
 of=20
                working, and you need to have the two sides operating in=20
                compatible manners for it to work. In practice, I think the=
re=20
                are other variants, besides the two cited in the present=20
              3.2.2.</BLOCKQUOTE>
              <DIV>Yes. And there is no objective way to automatically dete=
rmine=20
              what variant the PBX or the SSP is supporting. Which is what =
an=20
              options tag could resolve.<BR>&nbsp;</DIV>
              <BLOCKQUOTE class=3Dgmail_quote=20
              style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER=
-LEFT: rgb(204,204,204) 1px solid">I=20
                would suggest:<BR><BR>&nbsp; &nbsp; &nbsp; &nbsp;&lt;t&gt;E=
ven=20
                where all information needed by the SIP-PBX is provided, in=
 some=20
                deployments inbound SIP requests from the SSP have the=20
                registered Contact URI in the Request-URI, whereas in other=
=20
                deployments inbound SIP requests have the intended target (=
AOR)=20
                in the Request-URI and the Contact URI in the Route header=
=20
                field. There are other variants too. Interoperability probl=
ems=20
                arise when a PBX designed for or configured for one variant=
=20
                attempts to interwork with an SSP designed for or configure=
d for=20
                another variant.&lt;/t&gt;<BR></BLOCKQUOTE>
              <DIV>Yes, slightly modified to add the objective means=20
              issue:<BR>&nbsp;&lt;t&gt;Even where all information needed by=
 the=20
              SIP-PBX is provided, in some deployments inbound SIP requests=
 from=20
              the SSP have the registered PBX Contact URI in the Request-UR=
I,=20
              whereas in other deployments inbound SIP requests have the=20
              intended target PBX user (AOR) in the Request-URI and the Con=
tact=20
              URI in the Route header field. There are other variants too.=
=20
              Interoperability problems arise when a PBX designed for or=20
              configured for one variant attempts to interwork with an SSP=
=20
              designed for or configured for another variant. There is curr=
ently=20
              no objective means in the signalling during registration for=
=20
              either party to discover what mechanism the other side=20
              supports.&lt;/t&gt;<BR>&nbsp;</DIV>
              <BLOCKQUOTE class=3Dgmail_quote=20
              style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER=
-LEFT: rgb(204,204,204) 1px solid">To=20
                accompany this, I think the title of the section should be=
=20
                changed too: "Inconsistent placement of information in inbo=
und=20
                requests"<BR>
                <DIV><BR></DIV></BLOCKQUOTE>
              <DIV>Yes, slightly modified to make it more specific:=20
              "Inconsistent placement of target URI information in inbound=
=20
              requests".<BR>&nbsp;</DIV>
              <BLOCKQUOTE class=3Dgmail_quote=20
              style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER=
-LEFT: rgb(204,204,204) 1px solid">
                <DIV>John<BR><BR>&gt; -----Original Message-----<BR>&gt; Fr=
om:=20
                Hans Erik van Elburg [mailto:<A=20
                href=3D"mailto:ietf.hanserik@gmail.com"=20
                target=3D_blank>ietf.hanserik@gmail.com</A>]<BR></DIV>
                <DIV>
                <DIV></DIV>
                <DIV>&gt; Sent: 29 March 2010 17:27<BR>&gt; To: Elwell,=20
                John<BR>&gt; Cc: <A href=3D"mailto:martini@ietf.org"=20
                target=3D_blank>martini@ietf.org</A><BR>&gt; Subject: Re:=20
                [martini] #21: 3.2.2 describes an issue with some=20
                PBX<BR>&gt;<BR>&gt; Hi John,<BR>&gt;<BR>&gt; I was just try=
ing=20
                to find a text that describes the issue.<BR>&gt;<BR>&gt; Bu=
t now=20
                the issue reads like "some PBX like apples, some like<BR>&g=
t;=20
                bananas". To me that does not sound like a usefull issue=20
                to<BR>&gt; describe in an RFC.<BR>&gt;<BR>&gt; So I think o=
ne or=20
                two more sentence would make clear why this<BR>&gt; is an=20
                issue.<BR>&gt;<BR>&gt; I think there is multiple underlying=
=20
                issues here:<BR>&gt; - PBX have different SIP profiles or a=
ll=20
                SIP-PBX are different<BR>&gt; - PBX support SIP trunking fl=
avour=20
                A, or support SIP trunking<BR>&gt; flavour B<BR>&gt; - SSP=
=20
                systems don't know what mechanism the PBX support (can<BR>&=
gt;=20
                be resolved with explicit indicator, this draft proposes=20
                an<BR>&gt; indicator for flavour B but for another purpose =
it=20
                seems)<BR>&gt; - PBX do not know what SIP trunking flavour =
the=20
                SSP supports<BR>&gt; (not addressed it seems)<BR>&gt;<BR>&g=
t; I=20
                don't seem to have a lucky hand with proposing an=20
                improved<BR>&gt; text, so maybe you should have a go at=20
                it.<BR>&gt;<BR>&gt; BR,<BR>&gt; /Hans Erik van=20
                Elburg<BR>&gt;<BR>&gt; p.s. I never said or implied that a=
=20
                SIP-PBX shall implement<BR>&gt; IMS. But it would be really=
,=20
                really, really good if they<BR>&gt; would interwork on the =
UNI=20
                with the IMS business trunking. &nbsp;I<BR>&gt; think that=
=20
                should also be in your interest and in fact you<BR>&gt; hav=
e=20
                been part of that work...<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; O=
n=20
                Mon, Mar 29, 2010 at 5:56 PM, Elwell, John<BR>&gt; &lt;<A=20
                href=3D"mailto:john.elwell@siemens-enterprise.com"=20
                target=3D_blank>john.elwell@siemens-enterprise.com</A>&gt;=
=20
                wrote:<BR>&gt;<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; Hans=20
                Erik,<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; As an individual=
, I=20
                disagree with the proposed text,<BR>&gt; since it is mislea=
ding.=20
                The "international standards" to<BR>&gt; which you prefer a=
re=20
                standards specific to an IMS<BR>&gt; environment. The=20
                implication of the wording as proposed is<BR>&gt; that SIP-=
PBXs=20
                ought to implement IMS specifications. And as<BR>&gt; Hadri=
el=20
                points out, implementing those IMS specifications<BR>&gt; d=
oes=20
                not eliminate the problems that the SIPconnect people<BR>&g=
t;=20
                are trying to solve. I believe the existing text in=20
                draft-03<BR>&gt; is sufficient.<BR>&gt;<BR>&gt;<BR>&gt; &nb=
sp;=20
                &nbsp; &nbsp; John<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
                -----Original Message-----<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
                From: Hans Erik van Elburg [mailto:<A=20
                href=3D"mailto:ietf.hanserik@gmail.com"=20
                target=3D_blank>ietf.hanserik@gmail.com</A>]<BR>&gt;<BR>&gt=
;=20
                &nbsp; &nbsp; &nbsp; &gt; Sent: 26 March 2010 23:03<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; To: Elwell, John<BR>&gt; &nbsp; &=
nbsp;=20
                &nbsp; &gt; Cc: <A href=3D"mailto:martini@ietf.org"=20
                target=3D_blank>martini@ietf.org</A><BR>&gt; &nbsp; &nbsp; =
&nbsp;=20
                &gt; Subject: Re: [martini] #21: 3.2.2 describes an=20
                issue<BR>&gt; with some PBX<BR>&gt; &nbsp; &nbsp; &nbsp;=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; I will not argue wit=
h you=20
                about the validity of that argument.<BR>&gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Can you agree=
 to=20
                the modified text?<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt=
;=20
                &nbsp; &nbsp; &nbsp; &gt; "Request-URI vs. loose-route=20
                acceptance<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Some IP-PBX do=
 not=20
                implement international standards or SIP<BR>&gt; &nbsp; &nb=
sp;=20
                &nbsp; &gt; profiles for SIP trunking. As a consequence som=
e=20
                SIP-PBXs<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; expect that inbo=
und=20
                SIP requests from the SSP will have the<BR>&gt; &nbsp; &nbs=
p;=20
                &nbsp; &gt; registered Contact-URI in the Request-URI, and =
thus=20
                not<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; interoperate with the=
=20
                loose-route scheme of 3GPP and ETSI.<BR>&gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; Other SIP-PBXs are fine with the Request-URI be=
ing=20
                the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; intended target, but=
=20
                cannot handle receiving a Route header<BR>&gt; &nbsp; &nbsp=
;=20
                &nbsp; &gt; field identifying their registered Contact-URI =
as=20
                a<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; loose-route entry."<BR>=
&gt;=20
                &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
                BR,<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; /Hans Erik van=20
                Elburg<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nb=
sp;=20
                &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; On Fri, Mar 2=
6,=20
                2010 at 9:03 PM, Elwell, John<BR>&gt; &nbsp; &nbsp; &nbsp; =
&gt;=20
                &lt;<A href=3D"mailto:john.elwell@siemens-enterprise.com"=20
                target=3D_blank>john.elwell@siemens-enterprise.com</A>&gt;=
=20
                wrote:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nb=
sp;=20
                &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; The IETF does not have a mechanism, and that is=20
                the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; reason for the MARTIN=
I=20
                work. In particular, the IETF has not<BR>&gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; published the so-called loose-route mechanism. =
Hence=20
                the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; reason for the IETF, =
as=20
                owner of SIP, to publish a mechanism<BR>&gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; for bulk registrations.<BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
=20
                John<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp=
;=20
                &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; -----Original Message-----<BR>&gt; &nbsp; &nbsp=
;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; From: Hans Erik van=20
                Elburg<BR>&gt; [mailto:<A href=3D"mailto:ietf.hanserik@gmai=
l.com"=20
                target=3D_blank>ietf.hanserik@gmail.com</A>]<BR>&gt; &nbsp;=
 &nbsp;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Sent: 26 March 2010=20
                02:21<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp=
;=20
                &gt; To: <A href=3D"mailto:trac@localhost.amsl.com"=20
                target=3D_blank>trac@localhost.amsl.com</A><BR>&gt; &nbsp; =
&nbsp;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Cc: Elwell, John; <A=
=20
                href=3D"mailto:martini@ietf.org"=20
                target=3D_blank>martini@ietf.org</A><BR>&gt; &nbsp; &nbsp; =
&nbsp;=20
                &gt; &nbsp; &nbsp; &nbsp; &gt; Subject: Re: [martini] #21: =
3.2.2=20
                describes an issue<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; with s=
ome=20
                PBX<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
 &gt;=20
                Then you should rephrase to what the real issue is:<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; "<BR>&g=
t;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Request=
-URI=20
                vs. loose-route acceptance<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
                &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; Some IP-PBX do not implement=20
                international<BR>&gt; standards or SIP<BR>&gt; &nbsp; &nbsp=
;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; profiles for SIP trun=
king.=20
                As a consequence<BR>&gt; some SIP-PBXs<BR>&gt; &nbsp; &nbsp=
;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; expect that inbound S=
IP=20
                requests from the SSP<BR>&gt; will have the<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; registered=20
                Contact-URI in the Request-URI,<BR>&gt; and thus not<BR>&gt=
;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; interop=
erate=20
                with the loose-route scheme of<BR>&gt; 3GPP and ETSI.<BR>&g=
t;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Other=20
                SIP-PBXs are fine with the Request-URI being the<BR>&gt; &n=
bsp;=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; intended targe=
t,=20
                but cannot handle receiving<BR>&gt; a Route header<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; field=20
                identifying their registered Contact-URI as a<BR>&gt; &nbsp=
;=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; loose-route=20
                entry."<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nb=
sp;=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
 &gt;=20
                Is this an issue, yes. Does introducing yet another<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; profile help? No.<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; /Hans Erik van=
=20
                Elburg<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbs=
p;=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
 &gt;=20
                On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker<BR>&=
gt;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &lt;<A=
=20
                href=3D"mailto:trac@tools.ietf.org"=20
                target=3D_blank>trac@tools.ietf.org</A>&gt; wrote:<BR>&gt; =
&nbsp;=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; #21: 3.2.2 describes an issue with some PBX<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                -------------------------------------+---------------------=
---<BR>&gt;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;=20
                --------------<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nb=
sp;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Reporter:=20
                &nbsp;ietf.hanserik@...<BR>&gt; | &nbsp; &nbsp; &nbsp;=20
                &nbsp;Owner:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp=
;=20
                &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Type:=20
                &nbsp;defect &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
                &nbsp; &nbsp; |<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Status:=20
                &nbsp;closed<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp=
;=20
                &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Priority: &nbsp;mino=
r=20
                &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
                &nbsp;|<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Milestone:=20
                &nbsp;milestone1<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &=
nbsp;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; Component: &nbsp;reqs &nbs=
p;=20
                &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
                |<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Version: &nbsp;1.0<BR>&=
gt;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp; &nbsp;Severity: &nbsp;In WG Last Call &nbsp;=
=20
                &nbsp; &nbsp; &nbsp; &nbsp;|<BR>&gt; &nbsp; &nbsp; &nbsp; &=
gt;=20
                Resolution: &nbsp;invalid<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Keywor=
ds:=20
                &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
                &nbsp; &nbsp; &nbsp; &nbsp; |<BR>&gt; &nbsp; &nbsp; &nbsp; =
&gt;=20
                &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=20
                -------------------------------------+---------------------=
---<BR>&gt;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;=20
                --------------<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nb=
sp;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; Changes (by=20
                john.elwell@...):<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;* status:=20
                &nbsp;new =3D&gt; closed<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; =
&nbsp;=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;* resolution:=
=20
                &nbsp;=3D&gt; invalid<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nb=
sp;=20
                &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; Comment:<BR>&gt; &n=
bsp;=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; &nbsp;The text of 3.2.2 just underlines the<BR>&gt; =
fact=20
                that there<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; are different<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
                &nbsp;implementations around. A PBX that<BR>&gt; expects th=
e=20
                loose<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp=
;=20
                &gt; route mechanism to be<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;used w=
ould=20
                fail to interwork with SSPs using a<BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
                &gt; &nbsp; &nbsp; &nbsp; &gt; different mechanism=20
                (e.g.,<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbs=
p;=20
                &gt; &nbsp; &nbsp; &nbsp; &nbsp;SIPconnect 1.0), and a PBX=
=20
                not<BR>&gt; expecting the loose<BR>&gt; &nbsp; &nbsp; &nbsp=
;=20
                &gt; &nbsp; &nbsp; &nbsp; &gt; route mechanism to be<BR>&gt=
;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp; &nbsp;used would fail to interwork with a loo=
se=20
                route<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp=
;=20
                &gt; implementation (e.g.,<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;ETSI/3=
GPP).=20
                Hence the urgent need for<BR>&gt; a standard.<BR>&gt; &nbsp=
;=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; --<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &=
nbsp;=20
                &gt; &nbsp; &nbsp; &nbsp; Ticket URL:<BR>&gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt;<BR>&gt; &lt;<A=20
                href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/2=
1#comment:1"=20
                target=3D_blank>http://trac.tools.ietf.org/wg/martini/trac/=
ticket/21#comment:1</A>&gt;<BR>&gt;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp; martini &lt;<A=20
                href=3D"http://tools.ietf.org/martini/"=20
                target=3D_blank>http://tools.ietf.org/martini/</A>&gt;<BR>&=
gt;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp;=20
                _______________________________________________<BR>&gt; &nb=
sp;=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; martini mailing list<BR>&gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; <A=20
                href=3D"mailto:martini@ietf.org"=20
                target=3D_blank>martini@ietf.org</A><BR>&gt; &nbsp; &nbsp; =
&nbsp;=20
                &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; <A=20
                href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
                target=3D_blank>https://www.ietf.org/mailman/listinfo/marti=
ni</A><BR>&gt;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp;=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;<BR>&gt;<BR>&=
gt;=20
                </DIV></DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BLOCKQUOT=
E></DIV></DIV></DIV></BLOCKQUOTE></DIV><BR><BR>____________________________=
___________________<BR>martini=20
        mailing list<BR><A href=3D"mailto:martini@ietf.org"=20
        target=3D_blank>martini@ietf.org</A><BR><A=20
        href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
        target=3D_blank>https://www.ietf.org/mailman/listinfo/martini</A><B=
R><BR></BLOCKQUOTE></DIV><BR></DIV></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></=
DIV><BR></BLOCKQUOTE></BODY></HTML>

--_000_EDC0A1AE77C57744B664A310A0B23AE20D1C82B3FRMRSSXCHMBSC3d_--

From christer.holmberg@ericsson.com  Wed Mar 31 06:01:27 2010
Return-Path: <christer.holmberg@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 8C37A3A6980 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 06:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level: 
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[AWL=-0.594, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 gMAkKx-Wa0wY for <martini@core3.amsl.com>; Wed, 31 Mar 2010 06:01:25 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 82DFD3A696B for <martini@ietf.org>; Wed, 31 Mar 2010 06:01:21 -0700 (PDT)
X-AuditID: c1b4fb39-b7b85ae000005cbc-e4-4bb347bed8c2
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 48.C8.23740.EB743BB4; Wed, 31 Mar 2010 15:01:50 +0200 (CEST)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.2.223]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Wed, 31 Mar 2010 15:01:49 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Date: Wed, 31 Mar 2010 15:01:48 +0200
Thread-Topic: [martini] Need for a SIP/SDP profile for SIP trunking ,	was Re: 	#21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrQ0IjbWqIKe8o3R5KcBnC7cQbV5QAAPGSQ
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC745E21C25448@ESESSCMS0354.eemea.ericsson.se>
References: <w2v9ae56b1e1003310428o6fc07243j294b603eec953a1a@mail.gmail.com> <m2k9ae56b1e1003310523zc70f6a83ub0e5b1bdaeddd5ce@mail.gmail.com> <EDC0A1AE77C57744B664A310A0B23AE20D1C8293@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <m2v9ae56b1e1003310548i739c29c1t8080612ae5b4eea7@mail.gmail.com>
In-Reply-To: <m2v9ae56b1e1003310548i739c29c1t8080612ae5b4eea7@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_FF84A09F50A6DC48ACB6714F4666CC745E21C25448ESESSCMS0354e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re: 	#21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 13:01:27 -0000

--_000_FF84A09F50A6DC48ACB6714F4666CC745E21C25448ESESSCMS0354e_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

While I agree on the usefulness of such profiles, I doubt IETF is the corre=
ct place to define those. I also think that it is outside the scope of MART=
INI.

Different SDO/customers/vendors might have different requirements on the pr=
ofiles, but we could of course provide a mechanism (e.g. using a feature ta=
g) to indicate which profiles are supported/indicated.

>From a MARTINI perspective, I think the main issue is the difference in the=
 routing mechanims.

Now, regarding the option-tag to indicate the routing mechanism: since an o=
ption-tag requires an RFC, would MARTINI be the place to define such option=
-tag for the IMS solution (should the involved people choose to define one)=
?

Regards,

Christer

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Hans Erik van Elburg
Sent: 31. maaliskuuta 2010 15:49
To: DRAGE, Keith (Keith)
Cc: martini@ietf.org
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re=
: #21: 3.2.2 describes an issue with some PBX

Now that is pessimistic...

I thought that largely people should be able to agree on some common denomi=
nator between ETSI and SIP connect profile, but maybe that is my overly opt=
imistic naive stagnant mindset.

/Hans Erik van Elburg


On Wed, Mar 31, 2010 at 2:32 PM, DRAGE, Keith (Keith) <keith.drage@alcatel-=
lucent.com<mailto:keith.drage@alcatel-lucent.com>> wrote:
The problem is that I suspect noone is going to agree what that profile is =
to be sufficiently useful.

regards

Keith

________________________________
From: martini-bounces@ietf.org<mailto:martini-bounces@ietf.org> [mailto:mar=
tini-bounces@ietf.org<mailto:martini-bounces@ietf.org>] On Behalf Of Hans E=
rik van Elburg
Sent: Wednesday, March 31, 2010 1:24 PM
To: martini@ietf.org<mailto:martini@ietf.org>
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re=
: #21: 3.2.2 describes an issue with some PBX

I should have said "explicit indication" instead of "option tag". Feature t=
ags maybe more appropriate, when talking about a profile.

/Hans Erik van Elburg


On Wed, Mar 31, 2010 at 1:28 PM, Hans Erik van Elburg <ietf.hanserik@gmail.=
com<mailto:ietf.hanserik@gmail.com>> wrote:
Yes, I agree with that observation.

Only solving the routing issue does not solve the overall problem. For that=
 a minimum SIP/SDP profile needs to be agreed upon. Also what are common de=
nominator as codec for voice, fax, dtmf etc.

The question rises if there should be an option tag to signal support for a=
 profile instead of only signalling what routing method is preferred.

BR,
/Hans Erik van Elburg


On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, Keith (Keith) <keith.drage@alcatel-=
lucent.com<mailto:keith.drage@alcatel-lucent.com>> wrote:
So assuming that this text is accepted, I guess the key argument of providi=
ng this distinction is not that both behaviours are non-standard, but that =
some means is needed to distinguish the two.

While I do not have a problem with that specifically, I still have an issue=
 that providing some signalling to do this solves all the issues. There are=
 all sorts of other issues associated with what the PBX "expects" that also=
 cause all sorts of issues, such as whether it expects a tel URI in tel URI=
 format or SIP URI format, and so on, that are not signalled.

Therefore at the end of the day, one is still going to end up with configur=
ation information at either end of this interface that is not explicitly si=
gnalled, and in the absence of both sides having preconfigured knowledge of=
 that information, the interface is not going to work.

regards

Keith

________________________________
From: martini-bounces@ietf.org<mailto:martini-bounces@ietf.org> [mailto:mar=
tini-bounces@ietf.org<mailto:martini-bounces@ietf.org>] On Behalf Of Elwell=
, John
Sent: Tuesday, March 30, 2010 6:11 PM
To: Hans Erik van Elburg

Cc: martini@ietf.org<mailto:martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

OK, fixed in my working copy.

John

________________________________
From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto:ietf.hans=
erik@gmail.com>]
Sent: 30 March 2010 11:49
To: Elwell, John
Cc: martini@ietf.org<mailto:martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

Hi John,

Inline...

/Hans Erik van Elburg

On Mon, Mar 29, 2010 at 9:55 PM, Elwell, John <john.elwell@siemens-enterpri=
se.com<mailto:john.elwell@siemens-enterprise.com>> wrote:
Hans Erik,

I think the point you are trying to make is that it is not one-sided. The f=
act is, each side has different ways of working, and you need to have the t=
wo sides operating in compatible manners for it to work. In practice, I thi=
nk there are other variants, besides the two cited in the present 3.2.2.
Yes. And there is no objective way to automatically determine what variant =
the PBX or the SSP is supporting. Which is what an options tag could resolv=
e.

I would suggest:

       <t>Even where all information needed by the SIP-PBX is provided, in =
some deployments inbound SIP requests from the SSP have the registered Cont=
act URI in the Request-URI, whereas in other deployments inbound SIP reques=
ts have the intended target (AOR) in the Request-URI and the Contact URI in=
 the Route header field. There are other variants too. Interoperability pro=
blems arise when a PBX designed for or configured for one variant attempts =
to interwork with an SSP designed for or configured for another variant.</t=
>
Yes, slightly modified to add the objective means issue:
 <t>Even where all information needed by the SIP-PBX is provided, in some d=
eployments inbound SIP requests from the SSP have the registered PBX Contac=
t URI in the Request-URI, whereas in other deployments inbound SIP requests=
 have the intended target PBX user (AOR) in the Request-URI and the Contact=
 URI in the Route header field. There are other variants too. Interoperabil=
ity problems arise when a PBX designed for or configured for one variant at=
tempts to interwork with an SSP designed for or configured for another vari=
ant. There is currently no objective means in the signalling during registr=
ation for either party to discover what mechanism the other side supports.<=
/t>

To accompany this, I think the title of the section should be changed too: =
"Inconsistent placement of information in inbound requests"

Yes, slightly modified to make it more specific: "Inconsistent placement of=
 target URI information in inbound requests".

John

> -----Original Message-----
> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto:ietf.ha=
nserik@gmail.com>]
> Sent: 29 March 2010 17:27
> To: Elwell, John
> Cc: martini@ietf.org<mailto:martini@ietf.org>
> Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>
> Hi John,
>
> I was just trying to find a text that describes the issue.
>
> But now the issue reads like "some PBX like apples, some like
> bananas". To me that does not sound like a usefull issue to
> describe in an RFC.
>
> So I think one or two more sentence would make clear why this
> is an issue.
>
> I think there is multiple underlying issues here:
> - PBX have different SIP profiles or all SIP-PBX are different
> - PBX support SIP trunking flavour A, or support SIP trunking
> flavour B
> - SSP systems don't know what mechanism the PBX support (can
> be resolved with explicit indicator, this draft proposes an
> indicator for flavour B but for another purpose it seems)
> - PBX do not know what SIP trunking flavour the SSP supports
> (not addressed it seems)
>
> I don't seem to have a lucky hand with proposing an improved
> text, so maybe you should have a go at it.
>
> BR,
> /Hans Erik van Elburg
>
> p.s. I never said or implied that a SIP-PBX shall implement
> IMS. But it would be really, really, really good if they
> would interwork on the UNI with the IMS business trunking.  I
> think that should also be in your interest and in fact you
> have been part of that work...
>
>
>
> On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John
> <john.elwell@siemens-enterprise.com<mailto:john.elwell@siemens-enterprise=
.com>> wrote:
>
>
>       Hans Erik,
>
>       As an individual, I disagree with the proposed text,
> since it is misleading. The "international standards" to
> which you prefer are standards specific to an IMS
> environment. The implication of the wording as proposed is
> that SIP-PBXs ought to implement IMS specifications. And as
> Hadriel points out, implementing those IMS specifications
> does not eliminate the problems that the SIPconnect people
> are trying to solve. I believe the existing text in draft-03
> is sufficient.
>
>
>       John
>
>       > -----Original Message-----
>       > From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto=
:ietf.hanserik@gmail.com>]
>
>       > Sent: 26 March 2010 23:03
>       > To: Elwell, John
>       > Cc: martini@ietf.org<mailto:martini@ietf.org>
>       > Subject: Re: [martini] #21: 3.2.2 describes an issue
> with some PBX
>       >
>       > I will not argue with you about the validity of that argument.
>       >
>       > Can you agree to the modified text?
>       >
>       > "Request-URI vs. loose-route acceptance
>       > Some IP-PBX do not implement international standards or SIP
>       > profiles for SIP trunking. As a consequence some SIP-PBXs
>       > expect that inbound SIP requests from the SSP will have the
>       > registered Contact-URI in the Request-URI, and thus not
>       > interoperate with the loose-route scheme of 3GPP and ETSI.
>       > Other SIP-PBXs are fine with the Request-URI being the
>       > intended target, but cannot handle receiving a Route header
>       > field identifying their registered Contact-URI as a
>       > loose-route entry."
>       >
>       > BR,
>       > /Hans Erik van Elburg
>       >
>       >
>       > On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
>       > <john.elwell@siemens-enterprise.com<mailto:john.elwell@siemens-en=
terprise.com>> wrote:
>       >
>       >
>       >       The IETF does not have a mechanism, and that is the
>       > reason for the MARTINI work. In particular, the IETF has not
>       > published the so-called loose-route mechanism. Hence the
>       > reason for the IETF, as owner of SIP, to publish a mechanism
>       > for bulk registrations.
>       >
>       >       John
>       >
>       >
>       >       > -----Original Message-----
>       >       > From: Hans Erik van Elburg
> [mailto:ietf.hanserik@gmail.com<mailto:ietf.hanserik@gmail.com>]
>       >       > Sent: 26 March 2010 02:21
>       >       > To: trac@localhost.amsl.com<mailto:trac@localhost.amsl.co=
m>
>       >       > Cc: Elwell, John; martini@ietf.org<mailto:martini@ietf.or=
g>
>       >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
>       > with some PBX
>       >       >
>       >       >
>       >       > Then you should rephrase to what the real issue is:
>       >       > "
>       >       >
>       >       >
>       >       > Request-URI vs. loose-route acceptance
>       >       >
>       >       >
>       >       > Some IP-PBX do not implement international
> standards or SIP
>       >       > profiles for SIP trunking. As a consequence
> some SIP-PBXs
>       >       > expect that inbound SIP requests from the SSP
> will have the
>       >       > registered Contact-URI in the Request-URI,
> and thus not
>       >       > interoperate with the loose-route scheme of
> 3GPP and ETSI.
>       >       > Other SIP-PBXs are fine with the Request-URI being the
>       >       > intended target, but cannot handle receiving
> a Route header
>       >       > field identifying their registered Contact-URI as a
>       >       > loose-route entry."
>       >       >
>       >       >
>       >       > Is this an issue, yes. Does introducing yet another
>       > profile help? No.
>       >       >
>       >       > /Hans Erik van Elburg
>       >       >
>       >       >
>       >       > On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker
>       >       > <trac@tools.ietf.org<mailto:trac@tools.ietf.org>> wrote:
>       >       >
>       >       >
>       >       >       #21: 3.2.2 describes an issue with some PBX
>       >       >
>       >       >
> -------------------------------------+------------------------
>       >       > --------------
>       >       >        Reporter:  ietf.hanserik@...
> |        Owner:
>       >       >
>       >       >           Type:  defect                   |
>       > Status:  closed
>       >       >
>       >       >        Priority:  minor                    |
>       > Milestone:  milestone1
>       >       >       Component:  reqs                     |
>       > Version:  1.0
>       >       >
>       >       >        Severity:  In WG Last Call          |
>       > Resolution:  invalid
>       >       >        Keywords:                           |
>       >       >
>       >       >
> -------------------------------------+------------------------
>       >       > --------------
>       >       >       Changes (by john.elwell@...):
>       >       >
>       >       >        * status:  new =3D> closed
>       >       >        * resolution:  =3D> invalid
>       >       >
>       >       >
>       >       >       Comment:
>       >       >
>       >       >
>       >       >        The text of 3.2.2 just underlines the
> fact that there
>       >       > are different
>       >       >        implementations around. A PBX that
> expects the loose
>       >       > route mechanism to be
>       >       >        used would fail to interwork with SSPs using a
>       >       > different mechanism (e.g.,
>       >       >        SIPconnect 1.0), and a PBX not
> expecting the loose
>       >       > route mechanism to be
>       >       >        used would fail to interwork with a loose route
>       >       > implementation (e.g.,
>       >       >        ETSI/3GPP). Hence the urgent need for
> a standard.
>       >       >
>       >       >       --
>       >       >       Ticket URL:
>       >       >
>       >
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
>       >       >
>       >       >       martini <http://tools.ietf.org/martini/>
>       >       >
>       >       >
>       >       >       _______________________________________________
>       >       >       martini mailing list
>       >       >       martini@ietf.org<mailto:martini@ietf.org>
>       >       >       https://www.ietf.org/mailman/listinfo/martini
>       >       >
>       >       >
>       >       >
>       >       >
>       >
>       >
>       >
>
>
>



_______________________________________________
martini mailing list
martini@ietf.org<mailto:martini@ietf.org>
https://www.ietf.org/mailman/listinfo/martini




--_000_FF84A09F50A6DC48ACB6714F4666CC745E21C25448ESESSCMS0354e_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16982" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>While I agree on the usefulness of such profiles, =
I doubt=20
IETF is the correct place to define those. I also think that it is outside =
the=20
scope of MARTINI.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Different SDO/customers/vendors might have differe=
nt=20
requirements on the profiles,&nbsp;but we could of course provide a mechani=
sm=20
(e.g. using a feature tag) to indicate which profiles are=20
supported/indicated.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>From a MARTINI perspective, I think the main issue=
 is the=20
difference in the routing mechanims.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Now, regarding the option-tag to indicate the rout=
ing=20
mechanism: since an option-tag requires an RFC, would MARTINI be the place =
to=20
define such option-tag for the IMS solution (should the involved people cho=
ose=20
to define one)?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Christer</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> martini-bounces@ietf.org=20
  [mailto:martini-bounces@ietf.org] <B>On Behalf Of </B>Hans Erik van=20
  Elburg<BR><B>Sent:</B> 31. maaliskuuta 2010 15:49<BR><B>To:</B> DRAGE, Ke=
ith=20
  (Keith)<BR><B>Cc:</B> martini@ietf.org<BR><B>Subject:</B> Re: [martini] N=
eed=20
  for a SIP/SDP profile for SIP trunking , was Re: #21: 3.2.2 describes an =
issue=20
  with some PBX<BR></FONT><BR></DIV>
  <DIV></DIV>Now that is pessimistic...<BR><BR>I thought that largely peopl=
e=20
  should be able to agree on some common denominator between ETSI and SIP=20
  connect profile, but maybe that is my overly optimistic naive stagnant=20
  mindset. <BR><BR clear=3Dall>/Hans Erik van Elburg<BR><BR><BR>
  <DIV class=3Dgmail_quote>On Wed, Mar 31, 2010 at 2:32 PM, DRAGE, Keith (K=
eith)=20
  <SPAN dir=3Dltr>&lt;<A=20
  href=3D"mailto:keith.drage@alcatel-lucent.com">keith.drage@alcatel-lucent=
.com</A>&gt;</SPAN>=20
  wrote:<BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(2=
04,204,204) 1px solid">
    <DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff si=
ze=3D2>The=20
    problem is that I suspect noone is going to agree what that profile is =
to be=20
    sufficiently useful.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=20
    size=3D2>regards</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=20
    size=3D2>Keith</FONT></SPAN></DIV><BR>
    <BLOCKQUOTE=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,0,255)=
 2px solid; MARGIN-RIGHT: 0px">
      <DIV lang=3Den-us dir=3Dltr align=3Dleft>
      <HR>
      <FONT face=3DTahoma size=3D2>
      <DIV class=3Dim><B>From:</B> <A href=3D"mailto:martini-bounces@ietf.o=
rg"=20
      target=3D_blank>martini-bounces@ietf.org</A> [mailto:<A=20
      href=3D"mailto:martini-bounces@ietf.org"=20
      target=3D_blank>martini-bounces@ietf.org</A>] <B>On Behalf Of </B>Han=
s Erik=20
      van Elburg<BR></DIV><B>Sent:</B> Wednesday, March 31, 2010 1:24=20
      PM<BR><B>To:</B> <A href=3D"mailto:martini@ietf.org"=20
      target=3D_blank>martini@ietf.org</A><BR><B>Subject:</B> Re: [martini]=
 Need=20
      for a SIP/SDP profile for SIP trunking , was Re: #21: 3.2.2 describes=
 an=20
      issue with some PBX<BR></FONT><BR></DIV>
      <DIV>
      <DIV></DIV>
      <DIV class=3Dh5>
      <DIV></DIV>I should have said "explicit indication" instead of "optio=
n=20
      tag". Feature tags maybe more appropriate, when talking about a=20
      profile.<BR><BR clear=3Dall>/Hans Erik van Elburg<BR><BR><BR>
      <DIV class=3Dgmail_quote>On Wed, Mar 31, 2010 at 1:28 PM, Hans Erik v=
an=20
      Elburg <SPAN dir=3Dltr>&lt;<A href=3D"mailto:ietf.hanserik@gmail.com"=
=20
      target=3D_blank>ietf.hanserik@gmail.com</A>&gt;</SPAN> wrote:<BR>
      <BLOCKQUOTE class=3Dgmail_quote=20
      style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: r=
gb(204,204,204) 1px solid">Yes,=20
        I agree with that observation.<BR><BR>Only solving the routing issu=
e=20
        does not solve the overall problem. For that a minimum SIP/SDP prof=
ile=20
        needs to be agreed upon. Also what are common denominator as codec =
for=20
        voice, fax, dtmf etc. <BR><BR>The question rises if there should be=
 an=20
        option tag to signal support for a profile instead of only signalli=
ng=20
        what routing method is preferred.<BR><BR>BR,<BR clear=3Dall>/Hans E=
rik van=20
        Elburg<BR><BR><BR>
        <DIV class=3Dgmail_quote>On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, Ke=
ith=20
        (Keith) <SPAN dir=3Dltr>&lt;<A=20
        href=3D"mailto:keith.drage@alcatel-lucent.com"=20
        target=3D_blank>keith.drage@alcatel-lucent.com</A>&gt;</SPAN> wrote=
:<BR>
        <BLOCKQUOTE class=3Dgmail_quote=20
        style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT:=
 rgb(204,204,204) 1px solid">
          <DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff size=3D2>So=20
          assuming that this text is accepted, I guess the key argument of=
=20
          providing this distinction is not that both behaviours are=20
          non-standard, but that some means is needed to distinguish the=20
          two.</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2>While I do not have a problem with that specifically, I =
still=20
          have an issue that providing some signalling to do this solves al=
l the=20
          issues. There are all sorts of other issues associated with what =
the=20
          PBX "expects" that also cause all sorts of issues, such as whethe=
r it=20
          expects a tel URI in tel URI format or SIP URI format, and so on,=
 that=20
          are not signalled. </FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2>Therefore at the end of the day, one is still going to e=
nd up=20
          with configuration information at either end of this interface th=
at is=20
          not explicitly signalled, and in the absence of both sides having=
=20
          preconfigured knowledge of that information, the interface is not=
=20
          going to work.</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2>regards</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2>Keith</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#000=
0ff=20
          size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft>
          <HR>
          </DIV>
          <DIV dir=3Dltr align=3Dleft><FONT face=3DTahoma size=3D2><B>From:=
</B> <A=20
          href=3D"mailto:martini-bounces@ietf.org"=20
          target=3D_blank>martini-bounces@ietf.org</A> [mailto:<A=20
          href=3D"mailto:martini-bounces@ietf.org"=20
          target=3D_blank>martini-bounces@ietf.org</A>] <B>On Behalf Of=20
          </B>Elwell, John<BR><B>Sent:</B> Tuesday, March 30, 2010 6:11=20
          PM<BR><B>To:</B> Hans Erik van Elburg=20
          <DIV>
          <DIV></DIV>
          <DIV><BR><B>Cc:</B> <A href=3D"mailto:martini@ietf.org"=20
          target=3D_blank>martini@ietf.org</A><BR><B>Subject:</B> Re: [mart=
ini]=20
          #21: 3.2.2 describes an issue with some=20
          PBX<BR></DIV></DIV></FONT><BR></DIV>
          <DIV>
          <DIV></DIV>
          <DIV>
          <BLOCKQUOTE dir=3Dltr=20
          style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,=
0,255) 2px solid; MARGIN-RIGHT: 0px">
            <DIV></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0=
000ff=20
            size=3D2>OK, fixed in my working copy.</FONT></SPAN></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0=
000ff=20
            size=3D2></FONT></SPAN>&nbsp;</DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0=
000ff=20
            size=3D2>John</FONT></SPAN></DIV><BR>
            <BLOCKQUOTE=20
            style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(=
0,0,255) 2px solid; MARGIN-RIGHT: 0px">
              <DIV lang=3Den-us dir=3Dltr align=3Dleft>
              <HR>
              <FONT face=3DTahoma size=3D2><B>From:</B> Hans Erik van Elbur=
g=20
              [mailto:<A href=3D"mailto:ietf.hanserik@gmail.com"=20
              target=3D_blank>ietf.hanserik@gmail.com</A>] <BR><B>Sent:</B>=
 30=20
              March 2010 11:49<BR><B>To:</B> Elwell, John<BR><B>Cc:</B> <A=
=20
              href=3D"mailto:martini@ietf.org"=20
              target=3D_blank>martini@ietf.org</A><BR><B>Subject:</B> Re:=20
              [martini] #21: 3.2.2 describes an issue with some=20
              PBX<BR></FONT><BR></DIV>
              <DIV></DIV>Hi John,<BR><BR>Inline... <BR clear=3Dall><BR>/Han=
s Erik=20
              van Elburg<BR><BR>
              <DIV class=3Dgmail_quote>On Mon, Mar 29, 2010 at 9:55 PM, Elw=
ell,=20
              John <SPAN dir=3Dltr>&lt;<A=20
              href=3D"mailto:john.elwell@siemens-enterprise.com"=20
              target=3D_blank>john.elwell@siemens-enterprise.com</A>&gt;</S=
PAN>=20
              wrote:<BR>
              <BLOCKQUOTE class=3Dgmail_quote=20
              style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER=
-LEFT: rgb(204,204,204) 1px solid">Hans=20
                Erik,<BR><BR>I think the point you are trying to make is th=
at it=20
                is not one-sided. The fact is, each side has different ways=
 of=20
                working, and you need to have the two sides operating in=20
                compatible manners for it to work. In practice, I think the=
re=20
                are other variants, besides the two cited in the present=20
              3.2.2.</BLOCKQUOTE>
              <DIV>Yes. And there is no objective way to automatically dete=
rmine=20
              what variant the PBX or the SSP is supporting. Which is what =
an=20
              options tag could resolve.<BR>&nbsp;</DIV>
              <BLOCKQUOTE class=3Dgmail_quote=20
              style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER=
-LEFT: rgb(204,204,204) 1px solid">I=20
                would suggest:<BR><BR>&nbsp; &nbsp; &nbsp; &nbsp;&lt;t&gt;E=
ven=20
                where all information needed by the SIP-PBX is provided, in=
 some=20
                deployments inbound SIP requests from the SSP have the=20
                registered Contact URI in the Request-URI, whereas in other=
=20
                deployments inbound SIP requests have the intended target (=
AOR)=20
                in the Request-URI and the Contact URI in the Route header=
=20
                field. There are other variants too. Interoperability probl=
ems=20
                arise when a PBX designed for or configured for one variant=
=20
                attempts to interwork with an SSP designed for or configure=
d for=20
                another variant.&lt;/t&gt;<BR></BLOCKQUOTE>
              <DIV>Yes, slightly modified to add the objective means=20
              issue:<BR>&nbsp;&lt;t&gt;Even where all information needed by=
 the=20
              SIP-PBX is provided, in some deployments inbound SIP requests=
 from=20
              the SSP have the registered PBX Contact URI in the Request-UR=
I,=20
              whereas in other deployments inbound SIP requests have the=20
              intended target PBX user (AOR) in the Request-URI and the Con=
tact=20
              URI in the Route header field. There are other variants too.=
=20
              Interoperability problems arise when a PBX designed for or=20
              configured for one variant attempts to interwork with an SSP=
=20
              designed for or configured for another variant. There is curr=
ently=20
              no objective means in the signalling during registration for=
=20
              either party to discover what mechanism the other side=20
              supports.&lt;/t&gt;<BR>&nbsp;</DIV>
              <BLOCKQUOTE class=3Dgmail_quote=20
              style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER=
-LEFT: rgb(204,204,204) 1px solid">To=20
                accompany this, I think the title of the section should be=
=20
                changed too: "Inconsistent placement of information in inbo=
und=20
                requests"<BR>
                <DIV><BR></DIV></BLOCKQUOTE>
              <DIV>Yes, slightly modified to make it more specific:=20
              "Inconsistent placement of target URI information in inbound=
=20
              requests".<BR>&nbsp;</DIV>
              <BLOCKQUOTE class=3Dgmail_quote=20
              style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER=
-LEFT: rgb(204,204,204) 1px solid">
                <DIV>John<BR><BR>&gt; -----Original Message-----<BR>&gt; Fr=
om:=20
                Hans Erik van Elburg [mailto:<A=20
                href=3D"mailto:ietf.hanserik@gmail.com"=20
                target=3D_blank>ietf.hanserik@gmail.com</A>]<BR></DIV>
                <DIV>
                <DIV></DIV>
                <DIV>&gt; Sent: 29 March 2010 17:27<BR>&gt; To: Elwell,=20
                John<BR>&gt; Cc: <A href=3D"mailto:martini@ietf.org"=20
                target=3D_blank>martini@ietf.org</A><BR>&gt; Subject: Re:=20
                [martini] #21: 3.2.2 describes an issue with some=20
                PBX<BR>&gt;<BR>&gt; Hi John,<BR>&gt;<BR>&gt; I was just try=
ing=20
                to find a text that describes the issue.<BR>&gt;<BR>&gt; Bu=
t now=20
                the issue reads like "some PBX like apples, some like<BR>&g=
t;=20
                bananas". To me that does not sound like a usefull issue=20
                to<BR>&gt; describe in an RFC.<BR>&gt;<BR>&gt; So I think o=
ne or=20
                two more sentence would make clear why this<BR>&gt; is an=20
                issue.<BR>&gt;<BR>&gt; I think there is multiple underlying=
=20
                issues here:<BR>&gt; - PBX have different SIP profiles or a=
ll=20
                SIP-PBX are different<BR>&gt; - PBX support SIP trunking fl=
avour=20
                A, or support SIP trunking<BR>&gt; flavour B<BR>&gt; - SSP=
=20
                systems don't know what mechanism the PBX support (can<BR>&=
gt;=20
                be resolved with explicit indicator, this draft proposes=20
                an<BR>&gt; indicator for flavour B but for another purpose =
it=20
                seems)<BR>&gt; - PBX do not know what SIP trunking flavour =
the=20
                SSP supports<BR>&gt; (not addressed it seems)<BR>&gt;<BR>&g=
t; I=20
                don't seem to have a lucky hand with proposing an=20
                improved<BR>&gt; text, so maybe you should have a go at=20
                it.<BR>&gt;<BR>&gt; BR,<BR>&gt; /Hans Erik van=20
                Elburg<BR>&gt;<BR>&gt; p.s. I never said or implied that a=
=20
                SIP-PBX shall implement<BR>&gt; IMS. But it would be really=
,=20
                really, really good if they<BR>&gt; would interwork on the =
UNI=20
                with the IMS business trunking. &nbsp;I<BR>&gt; think that=
=20
                should also be in your interest and in fact you<BR>&gt; hav=
e=20
                been part of that work...<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; O=
n=20
                Mon, Mar 29, 2010 at 5:56 PM, Elwell, John<BR>&gt; &lt;<A=20
                href=3D"mailto:john.elwell@siemens-enterprise.com"=20
                target=3D_blank>john.elwell@siemens-enterprise.com</A>&gt;=
=20
                wrote:<BR>&gt;<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; Hans=20
                Erik,<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; As an individual=
, I=20
                disagree with the proposed text,<BR>&gt; since it is mislea=
ding.=20
                The "international standards" to<BR>&gt; which you prefer a=
re=20
                standards specific to an IMS<BR>&gt; environment. The=20
                implication of the wording as proposed is<BR>&gt; that SIP-=
PBXs=20
                ought to implement IMS specifications. And as<BR>&gt; Hadri=
el=20
                points out, implementing those IMS specifications<BR>&gt; d=
oes=20
                not eliminate the problems that the SIPconnect people<BR>&g=
t;=20
                are trying to solve. I believe the existing text in=20
                draft-03<BR>&gt; is sufficient.<BR>&gt;<BR>&gt;<BR>&gt; &nb=
sp;=20
                &nbsp; &nbsp; John<BR>&gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
                -----Original Message-----<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
                From: Hans Erik van Elburg [mailto:<A=20
                href=3D"mailto:ietf.hanserik@gmail.com"=20
                target=3D_blank>ietf.hanserik@gmail.com</A>]<BR>&gt;<BR>&gt=
;=20
                &nbsp; &nbsp; &nbsp; &gt; Sent: 26 March 2010 23:03<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; To: Elwell, John<BR>&gt; &nbsp; &=
nbsp;=20
                &nbsp; &gt; Cc: <A href=3D"mailto:martini@ietf.org"=20
                target=3D_blank>martini@ietf.org</A><BR>&gt; &nbsp; &nbsp; =
&nbsp;=20
                &gt; Subject: Re: [martini] #21: 3.2.2 describes an=20
                issue<BR>&gt; with some PBX<BR>&gt; &nbsp; &nbsp; &nbsp;=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; I will not argue wit=
h you=20
                about the validity of that argument.<BR>&gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Can you agree=
 to=20
                the modified text?<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt=
;=20
                &nbsp; &nbsp; &nbsp; &gt; "Request-URI vs. loose-route=20
                acceptance<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Some IP-PBX do=
 not=20
                implement international standards or SIP<BR>&gt; &nbsp; &nb=
sp;=20
                &nbsp; &gt; profiles for SIP trunking. As a consequence som=
e=20
                SIP-PBXs<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; expect that inbo=
und=20
                SIP requests from the SSP will have the<BR>&gt; &nbsp; &nbs=
p;=20
                &nbsp; &gt; registered Contact-URI in the Request-URI, and =
thus=20
                not<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; interoperate with the=
=20
                loose-route scheme of 3GPP and ETSI.<BR>&gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; Other SIP-PBXs are fine with the Request-URI be=
ing=20
                the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; intended target, but=
=20
                cannot handle receiving a Route header<BR>&gt; &nbsp; &nbsp=
;=20
                &nbsp; &gt; field identifying their registered Contact-URI =
as=20
                a<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; loose-route entry."<BR>=
&gt;=20
                &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
                BR,<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; /Hans Erik van=20
                Elburg<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nb=
sp;=20
                &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; On Fri, Mar 2=
6,=20
                2010 at 9:03 PM, Elwell, John<BR>&gt; &nbsp; &nbsp; &nbsp; =
&gt;=20
                &lt;<A href=3D"mailto:john.elwell@siemens-enterprise.com"=20
                target=3D_blank>john.elwell@siemens-enterprise.com</A>&gt;=
=20
                wrote:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nb=
sp;=20
                &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; The IETF does not have a mechanism, and that is=20
                the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; reason for the MARTIN=
I=20
                work. In particular, the IETF has not<BR>&gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; published the so-called loose-route mechanism. =
Hence=20
                the<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; reason for the IETF, =
as=20
                owner of SIP, to publish a mechanism<BR>&gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; for bulk registrations.<BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
=20
                John<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp=
;=20
                &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; -----Original Message-----<BR>&gt; &nbsp; &nbsp=
;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; From: Hans Erik van=20
                Elburg<BR>&gt; [mailto:<A href=3D"mailto:ietf.hanserik@gmai=
l.com"=20
                target=3D_blank>ietf.hanserik@gmail.com</A>]<BR>&gt; &nbsp;=
 &nbsp;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Sent: 26 March 2010=20
                02:21<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp=
;=20
                &gt; To: <A href=3D"mailto:trac@localhost.amsl.com"=20
                target=3D_blank>trac@localhost.amsl.com</A><BR>&gt; &nbsp; =
&nbsp;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Cc: Elwell, John; <A=
=20
                href=3D"mailto:martini@ietf.org"=20
                target=3D_blank>martini@ietf.org</A><BR>&gt; &nbsp; &nbsp; =
&nbsp;=20
                &gt; &nbsp; &nbsp; &nbsp; &gt; Subject: Re: [martini] #21: =
3.2.2=20
                describes an issue<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; with s=
ome=20
                PBX<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
 &gt;=20
                Then you should rephrase to what the real issue is:<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; "<BR>&g=
t;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Request=
-URI=20
                vs. loose-route acceptance<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
                &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; Some IP-PBX do not implement=20
                international<BR>&gt; standards or SIP<BR>&gt; &nbsp; &nbsp=
;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; profiles for SIP trun=
king.=20
                As a consequence<BR>&gt; some SIP-PBXs<BR>&gt; &nbsp; &nbsp=
;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; expect that inbound S=
IP=20
                requests from the SSP<BR>&gt; will have the<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; registered=20
                Contact-URI in the Request-URI,<BR>&gt; and thus not<BR>&gt=
;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; interop=
erate=20
                with the loose-route scheme of<BR>&gt; 3GPP and ETSI.<BR>&g=
t;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; Other=20
                SIP-PBXs are fine with the Request-URI being the<BR>&gt; &n=
bsp;=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; intended targe=
t,=20
                but cannot handle receiving<BR>&gt; a Route header<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; field=20
                identifying their registered Contact-URI as a<BR>&gt; &nbsp=
;=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; loose-route=20
                entry."<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nb=
sp;=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
 &gt;=20
                Is this an issue, yes. Does introducing yet another<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; profile help? No.<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; /Hans Erik van=
=20
                Elburg<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbs=
p;=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=
 &gt;=20
                On Thu, Mar 25, 2010 at 9:22 PM, martini issue tracker<BR>&=
gt;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &lt;<A=
=20
                href=3D"mailto:trac@tools.ietf.org"=20
                target=3D_blank>trac@tools.ietf.org</A>&gt; wrote:<BR>&gt; =
&nbsp;=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; #21: 3.2.2 describes an issue with some PBX<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                -------------------------------------+---------------------=
---<BR>&gt;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;=20
                --------------<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nb=
sp;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Reporter:=20
                &nbsp;ietf.hanserik@...<BR>&gt; | &nbsp; &nbsp; &nbsp;=20
                &nbsp;Owner:<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp=
;=20
                &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Type:=20
                &nbsp;defect &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;=20
                &nbsp; &nbsp; |<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Status:=20
                &nbsp;closed<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp=
;=20
                &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Priority: &nbsp;mino=
r=20
                &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
                &nbsp;|<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Milestone:=20
                &nbsp;milestone1<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &=
nbsp;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; Component: &nbsp;reqs &nbs=
p;=20
                &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
                |<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; Version: &nbsp;1.0<BR>&=
gt;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp; &nbsp;Severity: &nbsp;In WG Last Call &nbsp;=
=20
                &nbsp; &nbsp; &nbsp; &nbsp;|<BR>&gt; &nbsp; &nbsp; &nbsp; &=
gt;=20
                Resolution: &nbsp;invalid<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Keywor=
ds:=20
                &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
                &nbsp; &nbsp; &nbsp; &nbsp; |<BR>&gt; &nbsp; &nbsp; &nbsp; =
&gt;=20
                &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=20
                -------------------------------------+---------------------=
---<BR>&gt;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;=20
                --------------<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nb=
sp;=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; Changes (by=20
                john.elwell@...):<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;* status:=20
                &nbsp;new =3D&gt; closed<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; =
&nbsp;=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;* resolution:=
=20
                &nbsp;=3D&gt; invalid<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nb=
sp;=20
                &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; Comment:<BR>&gt; &n=
bsp;=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; &nbsp;The text of 3.2.2 just underlines the<BR>&gt; =
fact=20
                that there<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; are different<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp;=20
                &nbsp;implementations around. A PBX that<BR>&gt; expects th=
e=20
                loose<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp=
;=20
                &gt; route mechanism to be<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;used w=
ould=20
                fail to interwork with SSPs using a<BR>&gt; &nbsp; &nbsp; &=
nbsp;=20
                &gt; &nbsp; &nbsp; &nbsp; &gt; different mechanism=20
                (e.g.,<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbs=
p;=20
                &gt; &nbsp; &nbsp; &nbsp; &nbsp;SIPconnect 1.0), and a PBX=
=20
                not<BR>&gt; expecting the loose<BR>&gt; &nbsp; &nbsp; &nbsp=
;=20
                &gt; &nbsp; &nbsp; &nbsp; &gt; route mechanism to be<BR>&gt=
;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp; &nbsp;used would fail to interwork with a loo=
se=20
                route<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp=
;=20
                &gt; implementation (e.g.,<BR>&gt; &nbsp; &nbsp; &nbsp; &gt=
;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &nbsp;ETSI/3=
GPP).=20
                Hence the urgent need for<BR>&gt; a standard.<BR>&gt; &nbsp=
;=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp;=
=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; --<BR>&gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &=
nbsp;=20
                &gt; &nbsp; &nbsp; &nbsp; Ticket URL:<BR>&gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp;=
=20
                &nbsp; &gt;<BR>&gt; &lt;<A=20
                href=3D"http://trac.tools.ietf.org/wg/martini/trac/ticket/2=
1#comment:1"=20
                target=3D_blank>http://trac.tools.ietf.org/wg/martini/trac/=
ticket/21#comment:1</A>&gt;<BR>&gt;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp; martini &lt;<A=20
                href=3D"http://tools.ietf.org/martini/"=20
                target=3D_blank>http://tools.ietf.org/martini/</A>&gt;<BR>&=
gt;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp;=
=20
                &nbsp; &nbsp;=20
                _______________________________________________<BR>&gt; &nb=
sp;=20
                &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp;=
=20
                &nbsp; martini mailing list<BR>&gt; &nbsp; &nbsp; &nbsp; &g=
t;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; <A=20
                href=3D"mailto:martini@ietf.org"=20
                target=3D_blank>martini@ietf.org</A><BR>&gt; &nbsp; &nbsp; =
&nbsp;=20
                &gt; &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; <A=20
                href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
                target=3D_blank>https://www.ietf.org/mailman/listinfo/marti=
ni</A><BR>&gt;=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;=
=20
                &nbsp; &nbsp; &nbsp; &gt;<BR>&gt; &nbsp; &nbsp; &nbsp;=20
                &gt;<BR>&gt; &nbsp; &nbsp; &nbsp; &gt;<BR>&gt;<BR>&gt;<BR>&=
gt;=20
                </DIV></DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BLOCKQUOT=
E></DIV></DIV></DIV></BLOCKQUOTE></DIV><BR><BR>____________________________=
___________________<BR>martini=20
        mailing list<BR><A href=3D"mailto:martini@ietf.org"=20
        target=3D_blank>martini@ietf.org</A><BR><A=20
        href=3D"https://www.ietf.org/mailman/listinfo/martini"=20
        target=3D_blank>https://www.ietf.org/mailman/listinfo/martini</A><B=
R><BR></BLOCKQUOTE></DIV><BR></DIV></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></=
DIV><BR></BLOCKQUOTE></BODY></HTML>

--_000_FF84A09F50A6DC48ACB6714F4666CC745E21C25448ESESSCMS0354e_--

From spencer@wonderhamster.org  Wed Mar 31 06:42:05 2010
Return-Path: <spencer@wonderhamster.org>
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 A2FF53A67B6 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 06:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.132
X-Spam-Level: *
X-Spam-Status: No, score=1.132 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 GA+BWkq6dzrH for <martini@core3.amsl.com>; Wed, 31 Mar 2010 06:42:04 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 64AD23A691D for <martini@ietf.org>; Wed, 31 Mar 2010 06:42:01 -0700 (PDT)
Received: from S73602b (cpe-76-182-230-135.tx.res.rr.com [76.182.230.135]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MeyVl-1OC11Y2RKb-00OdYM; Wed, 31 Mar 2010 09:42:26 -0400
Message-ID: <EC41EF9AA5E140A381247657BA04C611@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>, "Hans Erik van Elburg" <ietf.hanserik@gmail.com>, "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>
References: <w2v9ae56b1e1003310428o6fc07243j294b603eec953a1a@mail.gmail.com><m2k9ae56b1e1003310523zc70f6a83ub0e5b1bdaeddd5ce@mail.gmail.com><EDC0A1AE77C57744B664A310A0B23AE20D1C8293@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com><m2v9ae56b1e1003310548i739c29c1t8080612ae5b4eea7@mail.gmail.com> <FF84A09F50A6DC48ACB6714F4666CC745E21C25448@ESESSCMS0354.eemea.ericsson.se>
Date: Wed, 31 Mar 2010 08:42:05 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_08E1_01CAD0AE.0A5BB670"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1+Q+m+AvJup0krrrtA8apgqeSbCWifX+FBPyxC 5S0U1RS8zNXHrKe4T7zOqTSYciVhMGHyHN284WDLRuZXGrPu6G 60+WQGvvPeYBM+HDCvb6y/phRZrjOg1/RygiX1G8i0=
Cc: martini@ietf.org
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re: 	#21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 13:42:05 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_08E1_01CAD0AE.0A5BB670
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Christer,

Speaking as chair, I can assure you that an overall SIP PBX profile is =
out of scope for MARTINI :-)

Speaking as an individual, I would expect that =
http://tools.ietf.org/html/rfc5727 would point to having a proposal for =
an IMS option tag going through DISPATCH, but DISPATCH can certainly =
send work to an existing working group, and if that happens, MARTINI =
would be an obvious candidate destination.

<out of scope for MARTINI mailing list>=20

Again, speaking as an individual - my understanding is that the =
SIPconnect guys were OK with an option tag for SIPconnect 1.1, because =
SIPconnect 1.0 was incredibly underspecified ("register one AOR and a =
miracle may occur"). SIPconnect really is ready to remove the earlier =
optionless mode of operation from SIPconnect 1.1.

Would ETSI/TISPAN/3GPP move to an optioned mode of operation for Release =
1N? Or would this be retained, so that IMS would have two modes of =
operation?=20

No reason to answer this question on the MARTINI mailing list, or even =
to discuss it here, but I think that would be good to know, if you're =
thinking about bringing a proposal to DISPATCH.

</out of scope for MARTINI mailing list>=20

Spencer
  ----- Original Message -----=20
  From: Christer Holmberg=20
  To: Hans Erik van Elburg ; DRAGE, Keith (Keith)=20
  Cc: martini@ietf.org=20
  Sent: Wednesday, March 31, 2010 8:01 AM
  Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , =
was Re: #21: 3.2.2 describes an issue with some PBX


  Hi,

  While I agree on the usefulness of such profiles, I doubt IETF is the =
correct place to define those. I also think that it is outside the scope =
of MARTINI.

  Now, regarding the option-tag to indicate the routing mechanism: since =
an option-tag requires an RFC, would MARTINI be the place to define such =
option-tag for the IMS solution (should the involved people choose to =
define one)?
------=_NextPart_000_08E1_01CAD0AE.0A5BB670
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18876">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Christer,</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Speaking as chair, I can assure you that an =
overall&nbsp;SIP=20
PBX profile is out of scope for MARTINI :-)</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Speaking as an individual, I would expect that <FONT =
size=3D3><A=20
href=3D"http://tools.ietf.org/html/rfc5727">http://tools.ietf.org/html/rf=
c5727</A>=20
would point to having a proposal for an IMS option tag going through =
DISPATCH,=20
but DISPATCH can certainly send work to an existing working =
group,&nbsp;and if=20
that happens, MARTINI would be an obvious candidate=20
destination.</FONT></FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>&lt;out of scope for MARTINI mailing list&gt; =
</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Again, speaking as an individual - my understanding =
is that=20
the SIPconnect guys were OK with an option tag for SIPconnect 1.1, =
because=20
SIPconnect 1.0 was incredibly underspecified ("register one AOR and a =
miracle=20
may occur"). SIPconnect really is ready to remove the earlier optionless =
mode of=20
operation from SIPconnect 1.1.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Would ETSI/TISPAN/3GPP move to an optioned mode of =
operation=20
for Release 1N? Or would this be retained, so that IMS would have two =
modes of=20
operation? </FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>No reason to answer this question on the MARTINI =
mailing list,=20
or even to discuss it here, but I think that would be good to know, if =
you're=20
thinking about bringing a proposal to DISPATCH.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>&lt;/out of scope for MARTINI mailing list&gt; =
</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Spencer</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; =
PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: =
black"><B>From:</B>=20
  <A title=3Dchrister.holmberg@ericsson.com=20
  href=3D"mailto:christer.holmberg@ericsson.com">Christer Holmberg</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dietf.hanserik@gmail.com=20
  href=3D"mailto:ietf.hanserik@gmail.com">Hans Erik van Elburg</A> ; <A=20
  title=3Dkeith.drage@alcatel-lucent.com=20
  href=3D"mailto:keith.drage@alcatel-lucent.com">DRAGE, Keith =
(Keith)</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A title=3Dmartini@ietf.org =

  href=3D"mailto:martini@ietf.org">martini@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, March 31, 2010 =
8:01=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [martini] Need for =
a SIP/SDP=20
  profile for SIP trunking , was Re: #21: 3.2.2 describes an issue with =
some=20
  PBX</DIV>
  <DIV><BR></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT =
color=3D#0000ff=20
  size=3D2 face=3DArial>Hi,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT =
color=3D#0000ff=20
  size=3D2 face=3DArial></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT =
color=3D#0000ff=20
  size=3D2 face=3DArial>While I agree on the usefulness of such =
profiles, I doubt=20
  IETF is the correct place to define those. I also think that it is =
outside the=20
  scope of MARTINI.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT =
color=3D#0000ff=20
  size=3D2 face=3DArial></FONT></SPAN><SPAN =
class=3D426455512-31032010><FONT=20
  color=3D#0000ff size=3D2 face=3DArial></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D426455512-31032010><FONT =
color=3D#0000ff=20
  size=3D2 face=3DArial>Now, regarding the option-tag to indicate the =
routing=20
  mechanism: since an option-tag requires an RFC, would MARTINI be the =
place to=20
  define such option-tag for the IMS solution (should the involved =
people choose=20
  to define one)?</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_08E1_01CAD0AE.0A5BB670--


From spencer@wonderhamster.org  Wed Mar 31 06:47:55 2010
Return-Path: <spencer@wonderhamster.org>
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 366CC3A67F2 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 06:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.132
X-Spam-Level: *
X-Spam-Status: No, score=1.132 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, STOX_REPLY_TYPE=0.001]
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 stQbbyazcBdK for <martini@core3.amsl.com>; Wed, 31 Mar 2010 06:47:51 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 39D0A3A67B6 for <martini@ietf.org>; Wed, 31 Mar 2010 06:47:50 -0700 (PDT)
Received: from S73602b (cpe-76-182-230-135.tx.res.rr.com [76.182.230.135]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0MYwFH-1O0Uff0cWR-00Vsbu; Wed, 31 Mar 2010 09:48:20 -0400
Message-ID: <15B5F406D2A547D7B89B16D312FCD3C6@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>, "'Richard Shockey'" <richard@shockey.us>, "'Hadriel Kaplan'" <HKaplan@acmepacket.com>, <bruno.chatras@orange-ftgroup.com>, <ietf.hanserik@gmail.com>, <john.elwell@siemens-enterprise.com>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net><g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com><9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr><430FC6BDED356B4C8498F634416644A91A79E928EE@mail><FF84A09F50A6DC48ACB6714F4666CC745E21B5A8EC@ESESSCMS0354.eemea.ericsson.se><00b101cad02e$5e1a37d0$1a4ea770$@us> <FF84A09F50A6DC48ACB6714F4666CC745E21BEF4E4@ESESSCMS0354.eemea.ericsson.se>
Date: Wed, 31 Mar 2010 08:47:55 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1879L0vjSX6746Go6SggfGE6jy26INxQmMPuOV BOVd+4iwk6jbUI3GqQiVQK1l2y2BKuABS/gw0VEpZ2oTcmi4lh chLzxr9q6hfEms0dZqar4gMnX2C7Heo42n2Mxyk0Zs=
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 13:47:55 -0000

Hi, Christer,

> And, if people are ok with two solutions, why was there a suggestion to 
> send an LS to 3GPP and ask them to adopt the IETF solution?

Speaking as chair, a lot of things get suggested in IETF working group 
meetings, especially the ones that happen after lunch on Friday, but I 
wouldn't read too much into the face that this suggestion was raised.

As of IETF 77, I'm now the IAB liaison shepherd for 3GPP, and Gonzalo is 
continuing as liaison for 3GPP. We talked after MARTINI broke up, and I 
don't think either one of us thought sending a liaison statement to 3GPP 
with this suggestion was on the list of action items after the meeting...

:D

Spencer 


From spencer@wonderhamster.org  Wed Mar 31 06:50:58 2010
Return-Path: <spencer@wonderhamster.org>
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 06FA93A68B0 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 06:50:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.131
X-Spam-Level: *
X-Spam-Status: No, score=1.131 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
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 fWPuSfdUvDo7 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 06:50:57 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 4E0843A68A7 for <martini@ietf.org>; Wed, 31 Mar 2010 06:50:57 -0700 (PDT)
Received: from S73602b (cpe-76-182-230-135.tx.res.rr.com [76.182.230.135]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0LaogC-1NHM7h1O5Q-00kNCr; Wed, 31 Mar 2010 09:51:25 -0400
Message-ID: <CA1D898DA1E7489F82A82CACE1B52AE9@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>, "'Richard Shockey'" <richard@shockey.us>, "'Hadriel Kaplan'" <HKaplan@acmepacket.com>, <bruno.chatras@orange-ftgroup.com>, <ietf.hanserik@gmail.com>, <john.elwell@siemens-enterprise.com>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net><g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com><9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr><430FC6BDED356B4C8498F634416644A91A79E928EE@mail><FF84A09F50A6DC48ACB6714F4666CC745E21B5A8EC@ESESSCMS0354.eemea.ericsson.se><00b101cad02e$5e1a37d0$1a4ea770$@us><FF84A09F50A6DC48ACB6714F4666CC745E21BEF4E4@ESESSCMS0354.eemea.ericsson.se> <15B5F406D2A547D7B89B16D312FCD3C6@china.huawei.com>
Date: Wed, 31 Mar 2010 08:51:00 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX19WzInlqjqBZuc3Zdz+UPcPRagtyztfjN/joVN 7Rqm/7RQYscDkAAZmxKNhXKm7NOlfr/b2rd8r7ngxM5Cdc+bAv 1uWP/+nEm/QBw8ZONkaNsMOGKJmTJ6X0JGrJV+nitY=
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 13:50:58 -0000

Just fixing a typo...

> Speaking as chair, a lot of things get suggested in IETF working group 
> meetings, especially the ones that happen after lunch on Friday, but I 
> wouldn't read too much into the face that this suggestion was raised.

"... the fact that ..."

Sorry!

Spencer

From HKaplan@acmepacket.com  Wed Mar 31 06:52:24 2010
Return-Path: <HKaplan@acmepacket.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 6D0DC3A68A7 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 06:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.251
X-Spam-Level: 
X-Spam-Status: No, score=-0.251 tagged_above=-999 required=5 tests=[AWL=0.617,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6]
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 dowFKo7I33Oo for <martini@core3.amsl.com>; Wed, 31 Mar 2010 06:52:20 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 768E83A6898 for <martini@ietf.org>; Wed, 31 Mar 2010 06:52:20 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Wed, 31 Mar 2010 09:52:50 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Wed, 31 Mar 2010 09:52:50 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>, "bruno.chatras@orange-ftgroup.com" <bruno.chatras@orange-ftgroup.com>
Date: Wed, 31 Mar 2010 09:52:49 -0400
Thread-Topic: Issue with existing SIP trunking solutions, was Re: [martini] #21: 	3.2.2 describes an issue with some PBX
Thread-Index: AcrQtXSFvblRkOFXRgWwa+apJOEY6wAIzE/A
Message-ID: <430FC6BDED356B4C8498F634416644A91A79E92C83@mail>
References: <p2i9ae56b1e1003310235hbbecb059r8b9b84bd91cad1f@mail.gmail.com>
In-Reply-To: <p2i9ae56b1e1003310235hbbecb059r8b9b84bd91cad1f@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_430FC6BDED356B4C8498F634416644A91A79E92C83mail_"
MIME-Version: 1.0
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Issue with existing SIP trunking solutions, was Re:  #21: 	3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 13:52:24 -0000

--_000_430FC6BDED356B4C8498F634416644A91A79E92C83mail_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hi,
I'm not sure I understand the question exactly.
My only point was that in practice we've found that what IP-PBX's expect to=
 receive in the request-uri is inconsistent, and that even if the IP-PBX th=
inks it is following the ETSI model it's not clear what it will or should e=
xpect to get.
But really we're also focusing too much on this particular issue I think - =
there're other reasons to have the options-tag.

-hadriel

________________________________
From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
Sent: Wednesday, March 31, 2010 5:35 AM
To: bruno.chatras@orange-ftgroup.com
Cc: Hadriel Kaplan; richard@shockey.us; john.elwell@siemens-enterprise.com;=
 martini@ietf.org
Subject: Issue with existing SIP trunking solutions, was Re: [martini] #21:=
 3.2.2 describes an issue with some PBX

Hi Hadriel,

(Changed the thread name.)

Is your point that the use of a loose-route to the PBX as such is not so mu=
ch of a problem, but that SSP's would use it to deliver Request-URI's conta=
ining the SSP's domain to the IP-PBX?

BR,
/Hans Erik van Elburg


--_000_430FC6BDED356B4C8498F634416644A91A79E92C83mail_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"Person=
Name"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I&#8217;m not sure I understand the qu=
estion
exactly.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>My only point was that in practice we&=
#8217;ve
found that what IP-PBX&#8217;s expect to receive in the request-uri is inco=
nsistent,
and that even if the IP-PBX thinks it is following the ETSI model it&#8217;=
s not
clear what it will or should expect to get.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>But really we&#8217;re also focusing t=
oo much on
this particular issue I think &#8211; there&#8217;re other reasons to have =
the options-tag.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>-hadriel<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> <st1:Per=
sonName
w:st=3D"on">Hans Erik van Elburg</st1:PersonName>
[mailto:ietf.hanserik@gmail.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, March 31, 2=
010
5:35 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b>
bruno.chatras@orange-ftgroup.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName w:st=3D"=
on">Hadriel
 Kaplan</st1:PersonName>; richard@shockey.us;
john.elwell@siemens-enterprise.com; <st1:PersonName w:st=3D"on">martini@iet=
f.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Issue with existing=
 SIP
trunking solutions, was Re: [martini] #21: 3.2.2 describes an issue with so=
me
PBX</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>Hi Hadriel,<br>
<br>
(Changed the thread name.)<br>
<br>
Is your point that the use of a loose-route to the PBX as such is not so mu=
ch
of a problem, but that SSP's would use it to deliver Request-URI's containi=
ng
the SSP's domain to the IP-PBX?<br>
<br>
BR,<br clear=3Dall>
/<st1:PersonName w:st=3D"on">Hans Erik van Elburg</st1:PersonName><o:p></o:=
p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>

</body>

</html>

--_000_430FC6BDED356B4C8498F634416644A91A79E92C83mail_--

From HKaplan@acmepacket.com  Wed Mar 31 06:58:41 2010
Return-Path: <HKaplan@acmepacket.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 177CC3A68A9 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 06:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.563
X-Spam-Level: 
X-Spam-Status: No, score=-0.563 tagged_above=-999 required=5 tests=[AWL=0.905,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 I861t1FiEwJS for <martini@core3.amsl.com>; Wed, 31 Mar 2010 06:58:37 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id B86DC3A68A7 for <martini@ietf.org>; Wed, 31 Mar 2010 06:58:36 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Wed, 31 Mar 2010 09:59:06 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Wed, 31 Mar 2010 09:59:06 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Date: Wed, 31 Mar 2010 09:59:05 -0400
Thread-Topic: [martini] Need for a SIP/SDP profile for SIP trunking ,	was Re:  #21: 	3.2.2 describes an issue with some PBX
Thread-Index: AcrQxWPVY6shJVSHQZS9cZTanv/8XgAFCfoQ
Message-ID: <430FC6BDED356B4C8498F634416644A91A79E92C8D@mail>
References: <w2v9ae56b1e1003310428o6fc07243j294b603eec953a1a@mail.gmail.com>
In-Reply-To: <w2v9ae56b1e1003310428o6fc07243j294b603eec953a1a@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_430FC6BDED356B4C8498F634416644A91A79E92C8Dmail_"
MIME-Version: 1.0
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re:  #21: 	3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 13:58:41 -0000

--_000_430FC6BDED356B4C8498F634416644A91A79E92C8Dmail_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Somehow I knew we were going to get that question. :)
IF we really need this type of thing, then while we can't decide on profile=
s in the IETF (or at least won't ever finish if we try), what we could do i=
s make the Martini option-tag require a complaint device to support a "Prof=
ile" header, such that if a "Profile" header exists in the message, then th=
e receiver must support one of the profiles names listed in it.
In other words, we don't have to define any profiles in the IETF, and inser=
ting a Profile header field would be optional, but if you get it then you h=
ave to understand it.

-hadriel

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Hans Erik van Elburg
Sent: Wednesday, March 31, 2010 7:29 AM
To: DRAGE, Keith (Keith)
Cc: martini@ietf.org
Subject: [martini] Need for a SIP/SDP profile for SIP trunking , was Re: #2=
1: 3.2.2 describes an issue with some PBX

Yes, I agree with that observation.

Only solving the routing issue does not solve the overall problem. For that=
 a minimum SIP/SDP profile needs to be agreed upon. Also what are common de=
nominator as codec for voice, fax, dtmf etc.

The question rises if there should be an option tag to signal support for a=
 profile instead of only signalling what routing method is preferred.

BR,
/Hans Erik van Elburg


--_000_430FC6BDED356B4C8498F634416644A91A79E92C8Dmail_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"Person=
Name"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Somehow I knew we were going to get th=
at
question. </span></font><font size=3D2 color=3Dnavy face=3DWingdings><span
style=3D'font-size:10.0pt;font-family:Wingdings;color:navy'>J</span></font>=
<font
size=3D2 color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;font-fam=
ily:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>IF we really need this type of thing, =
then
while we can&#8217;t decide on profiles in the IETF (or at least won&#8217;=
t
ever finish if we try), what we <i><span style=3D'font-style:italic'>could<=
/span></i>
do is make the Martini option-tag require a complaint device to support a &=
#8220;Profile&#8221;
header, such that if a &#8220;Profile&#8221; header exists in the message, =
then
the receiver must support one of the profiles names listed in it.<o:p></o:p=
></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>In other words, we don&#8217;t have to=
 define
any profiles in the IETF, and inserting a Profile header field would be
optional, but if you get it then you have to understand it.<o:p></o:p></spa=
n></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>-hadriel<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b><st1:PersonName w:st=3D"=
on">Hans
 Erik van Elburg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, March 31, 2=
010
7:29 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> DRAGE, Keith (Keith)<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName w:st=3D"=
on">martini@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [martini] Need for =
a
SIP/SDP profile for SIP trunking , was Re: #21: 3.2.2 describes an issue wi=
th
some PBX</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>Yes, I agree with=
 that
observation.<br>
<br>
Only solving the routing issue does not solve the overall problem. For that=
 a
minimum SIP/SDP profile needs to be agreed upon. Also what are common
denominator as codec for voice, fax, dtmf etc. <br>
<br>
The question rises if there should be an option tag to signal support for a
profile instead of only signalling what routing method is preferred.<br>
<br>
BR,<br clear=3Dall>
/<st1:PersonName w:st=3D"on">Hans Erik van Elburg</st1:PersonName><br>
<br>
<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

--_000_430FC6BDED356B4C8498F634416644A91A79E92C8Dmail_--

From HKaplan@acmepacket.com  Wed Mar 31 07:02:26 2010
Return-Path: <HKaplan@acmepacket.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 B1EBA3A68A9 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:02:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.581
X-Spam-Level: 
X-Spam-Status: No, score=-0.581 tagged_above=-999 required=5 tests=[AWL=0.888,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 ebp3jBjZDbj6 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:02:22 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 7665F3A685E for <martini@ietf.org>; Wed, 31 Mar 2010 07:02:21 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Wed, 31 Mar 2010 10:02:51 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Wed, 31 Mar 2010 10:02:51 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, 'Richard Shockey' <richard@shockey.us>, "bruno.chatras@orange-ftgroup.com" <bruno.chatras@orange-ftgroup.com>, "ietf.hanserik@gmail.com" <ietf.hanserik@gmail.com>, "john.elwell@siemens-enterprise.com" <john.elwell@siemens-enterprise.com>
Date: Wed, 31 Mar 2010 10:02:22 -0400
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNgAAVBprAAEgqT0AAc5mFwABRadzAAFsnZAA==
Message-ID: <430FC6BDED356B4C8498F634416644A91A79E92C8F@mail>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com> <9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr> <430FC6BDED356B4C8498F634416644A91A79E928EE@mail> <FF84A09F50A6DC48ACB6714F4666CC745E21B5A8EC@ESESSCMS0354.eemea.ericsson.se> <00b101cad02e$5e1a37d0$1a4ea770$@us> <FF84A09F50A6DC48ACB6714F4666CC745E21BEF4E4@ESESSCMS0354.eemea.ericsson.se>
In-Reply-To: <FF84A09F50A6DC48ACB6714F4666CC745E21BEF4E4@ESESSCMS0354.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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 14:02:26 -0000

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> Sent: Wednesday, March 31, 2010 1:51 AM
> To: 'Richard Shockey'; Hadriel Kaplan; bruno.chatras@orange-ftgroup.com;
>=20
> And, if people are ok with two solutions, why was there a suggestion to
> send an LS to 3GPP and ask them to adopt the IETF solution?

I didn't mean they had to deprecate the old way - they can if they feel so =
inclined - but all I was asking was that they support Martini as well, so t=
hat IP-PBX's which do Martini could be supported by IMS networks.

-hadriel

From ietf.hanserik@gmail.com  Wed Mar 31 07:06:28 2010
Return-Path: <ietf.hanserik@gmail.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 B2B0A3A68BF for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:06:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.681
X-Spam-Level: 
X-Spam-Status: No, score=-0.681 tagged_above=-999 required=5 tests=[AWL=0.787,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 ocSl246LLrIf for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:06:27 -0700 (PDT)
Received: from mail-ew0-f224.google.com (mail-ew0-f224.google.com [209.85.219.224]) by core3.amsl.com (Postfix) with ESMTP id 6BE0F3A685E for <martini@ietf.org>; Wed, 31 Mar 2010 07:06:27 -0700 (PDT)
Received: by ewy24 with SMTP id 24so44066ewy.13 for <martini@ietf.org>; Wed, 31 Mar 2010 07:06:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=36Q/gZ9n4/5qBtTqlTiZJe8Gf6jaBRYID5BXekk8XuA=; b=kezLdlOqmwrv1Oxst+a3azQX+722HTphNfDKEOk7zJeFkbjKMNJkeoO9tjhJTRACZB dK6PNVarX960/EyRZ9GCMVyF2RlTFEx3FsgQS6H+9f3Vrg5A8hNyA12+1WsgBCmYEsnj l/UmNvRm1HqEFybacQ3Go1cfVTKpyyxBypE0M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=e+SAvGXZeOGX32qbBNE8cRSm9SaoSDULyjBvi5nm7fAF2QyjEJ3jjBveD0FEy2lH9N KRgJCK4KePuj0Yvw8JfkEHZLKBh0zwXdLxfrlVtgY+7HEQRNlwL3zW/BBMvMO5lGs51s +pwf0684xjQWAGRu1SrLVOIdK2ROceM3h/6GA=
MIME-Version: 1.0
Received: by 10.213.15.138 with HTTP; Wed, 31 Mar 2010 07:06:55 -0700 (PDT)
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79E92C83@mail>
References: <p2i9ae56b1e1003310235hbbecb059r8b9b84bd91cad1f@mail.gmail.com> <430FC6BDED356B4C8498F634416644A91A79E92C83@mail>
Date: Wed, 31 Mar 2010 16:06:55 +0200
Received: by 10.213.95.129 with SMTP id d1mr4497445ebn.13.1270044415274; Wed,  31 Mar 2010 07:06:55 -0700 (PDT)
Message-ID: <n2i9ae56b1e1003310706pf2d3d6c6m550941d1579a1046@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Content-Type: multipart/alternative; boundary=0014852d36c438b88d04831942dd
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Issue with existing SIP trunking solutions, was Re:  	#21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 14:06:28 -0000

--0014852d36c438b88d04831942dd
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Hadriel,

People say there is a mistake in the ETSI/3GPP solution that martini is
addressing. I'm only trying to see if there really is a mistake or if this
is just an opinion about a design choice being made. I am not yet convinced
that it is a mistake.

Also I think we need to be fair on this, martini is not addressing the
issues with existing solutions and fixing them, it is creating a new
solution trying to avoid some issues with existing solutions. That is a
different approach.

I think nobody denies the need for an option tag. In fact having an option
tag for the IMS method would make sense. And would fix an issue with that
solution.

/Hans Erik van Elburg


On Wed, Mar 31, 2010 at 3:52 PM, Hadriel Kaplan <HKaplan@acmepacket.com>wro=
te:

>
>
> Hi,
>
> I=92m not sure I understand the question exactly.
>
> My only point was that in practice we=92ve found that what IP-PBX=92s exp=
ect to
> receive in the request-uri is inconsistent, and that even if the IP-PBX
> thinks it is following the ETSI model it=92s not clear what it will or sh=
ould
> expect to get.
>
> But really we=92re also focusing too much on this particular issue I thin=
k =96
> there=92re other reasons to have the options-tag.
>
>
>
> -hadriel
>
>
>   ------------------------------
>
> *From:* Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
> *Sent:* Wednesday, March 31, 2010 5:35 AM
> *To:* bruno.chatras@orange-ftgroup.com
> *Cc:* Hadriel Kaplan; richard@shockey.us;
> john.elwell@siemens-enterprise.com; martini@ietf.org
> *Subject:* Issue with existing SIP trunking solutions, was Re: [martini]
> #21: 3.2.2 describes an issue with some PBX
>
>
>
> Hi Hadriel,
>
> (Changed the thread name.)
>
> Is your point that the use of a loose-route to the PBX as such is not so
> much of a problem, but that SSP's would use it to deliver Request-URI's
> containing the SSP's domain to the IP-PBX?
>
> BR,
> /Hans Erik van Elburg
>
>
>

--0014852d36c438b88d04831942dd
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Hadriel,<br><br>People say there is a mistake in the ETSI/3GPP solution =
that martini is addressing. I&#39;m only trying to see if there really is a=
 mistake or if this is just an opinion about a design choice being made. I =
am not yet convinced that it is a mistake. <br>
<br>Also I think we need to be fair on this, martini is not addressing the =
issues with existing solutions and fixing them, it is creating a new soluti=
on trying to avoid some issues with existing solutions. That is a different=
 approach.<br>
<br>I think nobody denies the need for an option tag. In fact having an opt=
ion tag for the IMS method would make sense. And would fix an issue with th=
at solution.<br><br clear=3D"all">/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Wed, Mar 31, 2010 at 3:52 PM, Hadriel=
 Kaplan <span dir=3D"ltr">&lt;<a href=3D"mailto:HKaplan@acmepacket.com">HKa=
plan@acmepacket.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204=
, 204); padding-left: 1ex;">











<div link=3D"blue" vlink=3D"blue" lang=3D"EN-US">

<div>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><span=
 style=3D"font-size: 10pt; font-family: Arial; color: navy;">=A0</span></fo=
nt></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><span=
 style=3D"font-size: 10pt; font-family: Arial; color: navy;">Hi,</span></fo=
nt></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><span=
 style=3D"font-size: 10pt; font-family: Arial; color: navy;">I=92m not sure=
 I understand the question
exactly.</span></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><span=
 style=3D"font-size: 10pt; font-family: Arial; color: navy;">My only point =
was that in practice we=92ve
found that what IP-PBX=92s expect to receive in the request-uri is inconsis=
tent,
and that even if the IP-PBX thinks it is following the ETSI model it=92s no=
t
clear what it will or should expect to get.</span></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><span=
 style=3D"font-size: 10pt; font-family: Arial; color: navy;">But really we=
=92re also focusing too much on
this particular issue I think =96 there=92re other reasons to have the opti=
ons-tag.</span></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><span=
 style=3D"font-size: 10pt; font-family: Arial; color: navy;">=A0</span></fo=
nt></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><span=
 style=3D"font-size: 10pt; font-family: Arial; color: navy;">-hadriel</span=
></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial" size=3D"2"><span=
 style=3D"font-size: 10pt; font-family: Arial; color: navy;">=A0</span></fo=
nt></p>

<div style=3D"border-width: medium medium medium 1.5pt; border-style: none =
none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz=
-use-text-color blue; padding: 0in 0in 0in 4pt;">

<div>

<div class=3D"MsoNormal" style=3D"text-align: center;" align=3D"center"><fo=
nt face=3D"Times New Roman" size=3D"3"><span style=3D"font-size: 12pt;">

<hr width=3D"100%" align=3D"center" size=3D"2">

</span></font></div>

<p class=3D"MsoNormal"><b><font face=3D"Tahoma" size=3D"2"><span style=3D"f=
ont-size: 10pt; font-family: Tahoma; font-weight: bold;">From:</span></font=
></b><font face=3D"Tahoma" size=3D"2"><span style=3D"font-size: 10pt; font-=
family: Tahoma;"> Hans Erik van Elburg
[mailto:<a href=3D"mailto:ietf.hanserik@gmail.com" target=3D"_blank">ietf.h=
anserik@gmail.com</a>] <br>
<b><span style=3D"font-weight: bold;">Sent:</span></b> Wednesday, March 31,=
 2010
5:35 AM<br>
<b><span style=3D"font-weight: bold;">To:</span></b>
<a href=3D"mailto:bruno.chatras@orange-ftgroup.com" target=3D"_blank">bruno=
.chatras@orange-ftgroup.com</a><br>
<b><span style=3D"font-weight: bold;">Cc:</span></b> Hadriel
 Kaplan; <a href=3D"mailto:richard@shockey.us" target=3D"_blank">richard@sh=
ockey.us</a>;
<a href=3D"mailto:john.elwell@siemens-enterprise.com" target=3D"_blank">joh=
n.elwell@siemens-enterprise.com</a>; <a href=3D"mailto:martini@ietf.org" ta=
rget=3D"_blank">martini@ietf.org</a><br>
<b><span style=3D"font-weight: bold;">Subject:</span></b> Issue with existi=
ng SIP
trunking solutions, was Re: [martini] #21: 3.2.2 describes an issue with so=
me
PBX</span></font></p>

</div><div class=3D"im">

<p class=3D"MsoNormal"><font face=3D"Times New Roman" size=3D"3"><span styl=
e=3D"font-size: 12pt;">=A0</span></font></p>

<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;"><font face=3D"Times N=
ew Roman" size=3D"3"><span style=3D"font-size: 12pt;">Hi Hadriel,<br>
<br>
(Changed the thread name.)<br>
<br>
Is your point that the use of a loose-route to the PBX as such is not so mu=
ch
of a problem, but that SSP&#39;s would use it to deliver Request-URI&#39;s =
containing
the SSP&#39;s domain to the IP-PBX?<br>
<br>
BR,<br clear=3D"all">
/Hans Erik van Elburg</span></font></p>

<p class=3D"MsoNormal"><font face=3D"Times New Roman" size=3D"3"><span styl=
e=3D"font-size: 12pt;">=A0</span></font></p>

</div></div>

</div>

</div>


</blockquote></div><br>

--0014852d36c438b88d04831942dd--

From keith.drage@alcatel-lucent.com  Wed Mar 31 07:10:43 2010
Return-Path: <keith.drage@alcatel-lucent.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 413DD3A6928 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:10:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.051
X-Spam-Level: 
X-Spam-Status: No, score=-4.051 tagged_above=-999 required=5 tests=[AWL=1.068,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, 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 zBtjowyVyUnA for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:10:41 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id 580E33A6876 for <martini@ietf.org>; Wed, 31 Mar 2010 07:10:41 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o2VEAZAK024510 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 31 Mar 2010 16:11:03 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Wed, 31 Mar 2010 16:11:00 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>, Christer Holmberg <christer.holmberg@ericsson.com>, "'Richard Shockey'" <richard@shockey.us>, "bruno.chatras@orange-ftgroup.com" <bruno.chatras@orange-ftgroup.com>,  "ietf.hanserik@gmail.com" <ietf.hanserik@GMAIL.COM>, "john.elwell@siemens-enterprise.com" <john.elwell@siemens-enterprise.com>
Date: Wed, 31 Mar 2010 16:10:58 +0200
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrPXNA0ZjYZSdvUTvWT/VD9WEKUwgAADSNgAAVBprAAEgqT0AAc5mFwABRadzAAFsnZAAAAVcaA
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE20D1C833F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com> <9ECCF01B52E7AB408A7EB85352642141014634FD@ftrdmel0.rd.francetelecom.fr> <430FC6BDED356B4C8498F634416644A91A79E928EE@mail> <FF84A09F50A6DC48ACB6714F4666CC745E21B5A8EC@ESESSCMS0354.eemea.ericsson.se> <00b101cad02e$5e1a37d0$1a4ea770$@us> <FF84A09F50A6DC48ACB6714F4666CC745E21BEF4E4@ESESSCMS0354.eemea.ericsson.se> <430FC6BDED356B4C8498F634416644A91A79E92C8F@mail>
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79E92C8F@mail>
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-Scanned-By: MIMEDefang 2.64 on 155.132.188.83
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 14:10:43 -0000

So you want 3GPP to also support a mechanism that has less functionality ju=
st because IETF has decided to go off in a different direction.

The 3GPP solution adequately handles private numbering plans, SIP URIs, int=
erworking with Centrex type solutions, provision of special services for pr=
ivate networked calls, all of which have been omitted from the current mart=
ini solution.

regards

Keith=20

> -----Original Message-----
> From: martini-bounces@ietf.org=20
> [mailto:martini-bounces@ietf.org] On Behalf Of Hadriel Kaplan
> Sent: Wednesday, March 31, 2010 3:02 PM
> To: Christer Holmberg; 'Richard Shockey';=20
> bruno.chatras@orange-ftgroup.com; ietf.hanserik@gmail.com;=20
> john.elwell@siemens-enterprise.com
> Cc: martini@ietf.org
> Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
>=20
>=20
>=20
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> > Sent: Wednesday, March 31, 2010 1:51 AM
> > To: 'Richard Shockey'; Hadriel Kaplan;=20
> > bruno.chatras@orange-ftgroup.com;
> >=20
> > And, if people are ok with two solutions, why was there a=20
> suggestion=20
> > to send an LS to 3GPP and ask them to adopt the IETF solution?
>=20
> I didn't mean they had to deprecate the old way - they can if=20
> they feel so inclined - but all I was asking was that they=20
> support Martini as well, so that IP-PBX's which do Martini=20
> could be supported by IMS networks.
>=20
> -hadriel
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini
> =

From adam@nostrum.com  Wed Mar 31 07:13:06 2010
Return-Path: <adam@nostrum.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 3532C3A68BF for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:13:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.664
X-Spam-Level: 
X-Spam-Status: No, score=-0.664 tagged_above=-999 required=5 tests=[AWL=0.805,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, SPF_PASS=-0.001]
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 Yc9v8Ugpq+iI for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:13:05 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id E020F3A6876 for <martini@ietf.org>; Wed, 31 Mar 2010 07:13:04 -0700 (PDT)
Received: from [172.16.3.231] (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o2VEDB9g081361 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Mar 2010 09:13:11 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4BB35877.9030409@nostrum.com>
Date: Wed, 31 Mar 2010 09:13:11 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org>	<074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org>	<s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com>	<A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net>	<9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com>	<A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net>	<g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com>	<A444A0F8084434499206E78C106220CADE11BA34@MCHP058A.global-ad.net>	<x2y9ae56b1e1003300349gc3ec82c7o449ba7554b7740b3@mail.gmail.com>	<A444A0F8084434499206E78C106220CADE11BF8E@MCHP058A.global-ad.net> <EDC0A1AE77C57744B664A310A0B23AE20D1C8238@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE20D1C8238@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="------------000909000603040102050209"
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 14:13:06 -0000

This is a multi-part message in MIME format.
--------------000909000603040102050209
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 3/31/10 6:18 AM, DRAGE, Keith (Keith) wrote:
> ...I still have an issue that providing some signalling to do this 
> solves all the issues. There are all sorts of other issues associated 
> with what the PBX "expects" that also cause all sorts of issues, such 
> as whether it expects a tel URI in tel URI format or SIP URI format...

What are you talking about? GIN nails down the format what shows up at 
the PBX: they're SIP (or SIPS) URIs.

> ...and so on, that are not signalled.

Regarding the other things that GIN does not solve: keep in mind that 
we're not addressing every possible PBX/SSP interconnect issue here. 
MARTINI has a refreshingly narrow charter, and that is by design. From 
an IETF perspective, the rest of the peering problem space is being 
solved mostly in SPEERMINT and DRINKS.

I suggest you and Hans Erik take a moment to refresh your memories about 
what we're working on here: https://datatracker.ietf.org/wg/martini/charter/

/a

--------------000909000603040102050209
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 3/31/10 6:18 AM, DRAGE, Keith (Keith) wrote:
<blockquote
 cite="mid:EDC0A1AE77C57744B664A310A0B23AE20D1C8238@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com"
 type="cite">
  <meta http-equiv="Content-Type"
 content="text/html; charset=ISO-8859-1">
  <meta content="MSHTML 6.00.2900.3660" name="GENERATOR">
  <div dir="ltr" align="left"><span class="756321311-31032010"></span> <span
 class="756321311-31032010"><font color="#0000ff" face="Arial" size="2">...I
still have an issue that providing some signalling to do this solves
all the issues. There are all sorts of other issues associated with
what the PBX "expects" that also cause all sorts of issues, such as
whether it expects a tel URI in tel URI format or SIP URI format...</font></span><br>
  </div>
</blockquote>
<font color="#0000ff"><font size="2"><font face="Arial"><font
 color="#000000"><br>
What are you talking about? GIN nails down the format what shows up at
the PBX: they're SIP (or SIPS) URIs.<br>
<br>
<blockquote type="cite"><span class="756321311-31032010"><font
 color="#0000ff" face="Arial" size="2">...and so on, that are not
signalled.<br>
  </font></span></blockquote>
<br>
Regarding the other things that GIN does not solve: keep in mind that
we're not addressing every possible PBX/SSP interconnect issue here.
MARTINI has a refreshingly narrow charter, and that is by design. From
an IETF perspective, the rest of the peering problem space is being
solved mostly in SPEERMINT and DRINKS.<br>
<br>
I suggest you and Hans Erik take a moment to refresh your memories
about what we're working on here:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/wg/martini/charter/">https://datatracker.ietf.org/wg/martini/charter/</a><br>
<br>
/a</font><br>
</font></font></font>
</body>
</html>

--------------000909000603040102050209--

From keith.drage@alcatel-lucent.com  Wed Mar 31 07:16:01 2010
Return-Path: <keith.drage@alcatel-lucent.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 11FDB3A68BF for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:16:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.085
X-Spam-Level: 
X-Spam-Status: No, score=-4.085 tagged_above=-999 required=5 tests=[AWL=1.033,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, HTML_MESSAGE=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 ajKcITn-en6T for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:16:00 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by core3.amsl.com (Postfix) with ESMTP id 39B383A685E for <martini@ietf.org>; Wed, 31 Mar 2010 07:15:59 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o2VEFhtA018696 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 31 Mar 2010 16:16:26 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Wed, 31 Mar 2010 16:15:54 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Adam Roach <adam@nostrum.com>
Date: Wed, 31 Mar 2010 16:15:52 +0200
Thread-Topic: [martini] #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrQ3GF/D2f6bDVIRpW17GXLEKLOSgAADNUA
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE20D1C8343@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org> <s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net> <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11BA34@MCHP058A.global-ad.net> <x2y9ae56b1e1003300349gc3ec82c7o449ba7554b7740b3@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11BF8E@MCHP058A.global-ad.net> <EDC0A1AE77C57744B664A310A0B23AE20D1C8238@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4BB35877.9030409@nostrum.com>
In-Reply-To: <4BB35877.9030409@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_EDC0A1AE77C57744B664A310A0B23AE20D1C8343FRMRSSXCHMBSC3d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.13
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 14:16:01 -0000

--_000_EDC0A1AE77C57744B664A310A0B23AE20D1C8343FRMRSSXCHMBSC3d_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

We are talking about the an issue on the requirements document here - not a=
 solutions document that as far as I am concerned does not have consensus

Keith

________________________________
From: Adam Roach [mailto:adam@nostrum.com]
Sent: Wednesday, March 31, 2010 3:13 PM
To: DRAGE, Keith (Keith)
Cc: Elwell, John; Hans Erik van Elburg; martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX

On 3/31/10 6:18 AM, DRAGE, Keith (Keith) wrote:
...I still have an issue that providing some signalling to do this solves a=
ll the issues. There are all sorts of other issues associated with what the=
 PBX "expects" that also cause all sorts of issues, such as whether it expe=
cts a tel URI in tel URI format or SIP URI format...

What are you talking about? GIN nails down the format what shows up at the =
PBX: they're SIP (or SIPS) URIs.

...and so on, that are not signalled.

Regarding the other things that GIN does not solve: keep in mind that we're=
 not addressing every possible PBX/SSP interconnect issue here. MARTINI has=
 a refreshingly narrow charter, and that is by design. From an IETF perspec=
tive, the rest of the peering problem space is being solved mostly in SPEER=
MINT and DRINKS.

I suggest you and Hans Erik take a moment to refresh your memories about wh=
at we're working on here: https://datatracker.ietf.org/wg/martini/charter/

/a

--_000_EDC0A1AE77C57744B664A310A0B23AE20D1C8343FRMRSSXCHMBSC3d_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1"=
>
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D214141514-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>We are talking about the an issue on the requireme=
nts=20
document here - not a solutions document that as far as I am concerned does=
 not=20
have consensus</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D214141514-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D214141514-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Keith</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Adam Roach [mailto:adam@nostrum=
.com]=20
  <BR><B>Sent:</B> Wednesday, March 31, 2010 3:13 PM<BR><B>To:</B> DRAGE, K=
eith=20
  (Keith)<BR><B>Cc:</B> Elwell, John; Hans Erik van Elburg;=20
  martini@ietf.org<BR><B>Subject:</B> Re: [martini] #21: 3.2.2 describes an=
=20
  issue with some PBX<BR></FONT><BR></DIV>
  <DIV></DIV>On 3/31/10 6:18 AM, DRAGE, Keith (Keith) wrote:=20
  <BLOCKQUOTE=20
  cite=3Dmid:EDC0A1AE77C57744B664A310A0B23AE20D1C8238@FRMRSSXCHMBSC3.dc-m.a=
lcatel-lucent.com=20
  type=3D"cite">
    <META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D756321311-31032010></SPAN><SP=
AN=20
    class=3D756321311-31032010><FONT face=3DArial color=3D#0000ff size=3D2>=
...I still=20
    have an issue that providing some signalling to do this solves all the=
=20
    issues. There are all sorts of other issues associated with what the PB=
X=20
    "expects" that also cause all sorts of issues, such as whether it expec=
ts a=20
    tel URI in tel URI format or SIP URI=20
  format...</FONT></SPAN><BR></DIV></BLOCKQUOTE><FONT color=3D#0000ff><FONT=
=20
  size=3D2><FONT face=3DArial><FONT color=3D#000000><BR>What are you talkin=
g about?=20
  GIN nails down the format what shows up at the PBX: they're SIP (or SIPS)=
=20
  URIs.<BR><BR>
  <BLOCKQUOTE type=3D"cite"><SPAN class=3D756321311-31032010><FONT face=3DA=
rial=20
    color=3D#0000ff size=3D2>...and so on, that are not=20
  signalled.<BR></FONT></SPAN></BLOCKQUOTE><BR>Regarding the other things t=
hat=20
  GIN does not solve: keep in mind that we're not addressing every possible=
=20
  PBX/SSP interconnect issue here. MARTINI has a refreshingly narrow charte=
r,=20
  and that is by design. From an IETF perspective, the rest of the peering=
=20
  problem space is being solved mostly in SPEERMINT and DRINKS.<BR><BR>I su=
ggest=20
  you and Hans Erik take a moment to refresh your memories about what we're=
=20
  working on here: <A class=3Dmoz-txt-link-freetext=20
  href=3D"https://datatracker.ietf.org/wg/martini/charter/">https://datatra=
cker.ietf.org/wg/martini/charter/</A><BR><BR>/a</FONT><BR></BLOCKQUOTE></FO=
NT></FONT></FONT></BODY></HTML>

--_000_EDC0A1AE77C57744B664A310A0B23AE20D1C8343FRMRSSXCHMBSC3d_--

From ietf.hanserik@gmail.com  Wed Mar 31 07:17:04 2010
Return-Path: <ietf.hanserik@gmail.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 842833A6876 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.742
X-Spam-Level: 
X-Spam-Status: No, score=-0.742 tagged_above=-999 required=5 tests=[AWL=0.726,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 qcF2SKbeJNhu for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:17:03 -0700 (PDT)
Received: from mail-ew0-f224.google.com (mail-ew0-f224.google.com [209.85.219.224]) by core3.amsl.com (Postfix) with ESMTP id 919563A6919 for <martini@ietf.org>; Wed, 31 Mar 2010 07:17:01 -0700 (PDT)
Received: by ewy24 with SMTP id 24so48298ewy.13 for <martini@ietf.org>; Wed, 31 Mar 2010 07:17:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=rrKkDAs/CtQHoegu8NczHDNiXC5KFhUNYl+qcOZFt/I=; b=pXx4CtwhVzyZk7meVfx2cMVTDKcswxdHANii+xz9jT16SX6c7S30oCuGMAypRWl4iH ZU4md9MDojS5CPs/ayOwbIY8lgQr0sKf0EzmHY1lOoQ6soOYE/n7MC2g5WbDunsGjITz 3GtLyBk1MDc4JnCt2xixrAeJMEjbGeTJQORc0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Ihcu1B52YQxdaCFpVc0IowM2YIxvkjFRjsLrOTucRuZm4UCmtcDHhD5dBnWRnrU2bd XtHCwmX7h0iS2fBSON25gKdzTEWpYtF+4+foGGN6e376GoTIDeya9xQHyh/1OaRKWFPx 5z1d1xm15NPYK4uXmUryOLsmQ0Rug/vtx0lJ8=
MIME-Version: 1.0
Received: by 10.213.15.138 with HTTP; Wed, 31 Mar 2010 07:17:28 -0700 (PDT)
In-Reply-To: <4BB35877.9030409@nostrum.com>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org> <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net> <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net> <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11BA34@MCHP058A.global-ad.net> <x2y9ae56b1e1003300349gc3ec82c7o449ba7554b7740b3@mail.gmail.com> <A444A0F8084434499206E78C106220CADE11BF8E@MCHP058A.global-ad.net> <EDC0A1AE77C57744B664A310A0B23AE20D1C8238@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4BB35877.9030409@nostrum.com>
Date: Wed, 31 Mar 2010 16:17:28 +0200
Received: by 10.213.0.212 with SMTP id 20mr3153073ebc.43.1270045048452; Wed,  31 Mar 2010 07:17:28 -0700 (PDT)
Message-ID: <n2z9ae56b1e1003310717v4b966f33j3709aa055b058f2d@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: Adam Roach <adam@nostrum.com>
Content-Type: multipart/alternative; boundary=000e0ce04002f63b8704831967d5
Cc: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 14:17:04 -0000

--000e0ce04002f63b8704831967d5
Content-Type: text/plain; charset=ISO-8859-1

Adam,

Did that several times:
"The task of this working group is to to standardize a multiple-AoR
registration mechanism for SIP that can be widely deployed by service
providers at large scale."

/Hans Erik van Elburg


On Wed, Mar 31, 2010 at 4:13 PM, Adam Roach <adam@nostrum.com> wrote:

>  On 3/31/10 6:18 AM, DRAGE, Keith (Keith) wrote:
>
>  ...I still have an issue that providing some signalling to do this solves
> all the issues. There are all sorts of other issues associated with what the
> PBX "expects" that also cause all sorts of issues, such as whether it
> expects a tel URI in tel URI format or SIP URI format...
>
>
> What are you talking about? GIN nails down the format what shows up at the
> PBX: they're SIP (or SIPS) URIs.
>
> ...and so on, that are not signalled.
>
>
> Regarding the other things that GIN does not solve: keep in mind that we're
> not addressing every possible PBX/SSP interconnect issue here. MARTINI has a
> refreshingly narrow charter, and that is by design. From an IETF
> perspective, the rest of the peering problem space is being solved mostly in
> SPEERMINT and DRINKS.
>
> I suggest you and Hans Erik take a moment to refresh your memories about
> what we're working on here:
> https://datatracker.ietf.org/wg/martini/charter/
>
> /a
>

--000e0ce04002f63b8704831967d5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Adam,<br><br>Did that several times:<br>&quot;The task of this working grou=
p is to to standardize a multiple-AoR<br>registration mechanism for SIP tha=
t can be widely deployed by service<br>providers at large scale.&quot;<br>
<br clear=3D"all">/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Wed, Mar 31, 2010 at 4:13 PM, Adam Ro=
ach <span dir=3D"ltr">&lt;<a href=3D"mailto:adam@nostrum.com">adam@nostrum.=
com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-=
left: 1ex;">



 =20

<div bgcolor=3D"#ffffff" text=3D"#000000">
On 3/31/10 6:18 AM, DRAGE, Keith (Keith) wrote:
<blockquote type=3D"cite">
 =20
 =20
  <div dir=3D"ltr" align=3D"left"><span></span> <span><font color=3D"#0000f=
f" face=3D"Arial" size=3D"2">...I
still have an issue that providing some signalling to do this solves
all the issues. There are all sorts of other issues associated with
what the PBX &quot;expects&quot; that also cause all sorts of issues, such =
as
whether it expects a tel URI in tel URI format or SIP URI format...</font><=
/span><br>
  </div>
</blockquote>
<font color=3D"#0000ff"><font size=3D"2"><font face=3D"Arial"><font color=
=3D"#000000"><br>
What are you talking about? GIN nails down the format what shows up at
the PBX: they&#39;re SIP (or SIPS) URIs.<br>
<br>
<blockquote type=3D"cite"><span><font color=3D"#0000ff" face=3D"Arial" size=
=3D"2">...and so on, that are not
signalled.<br>
  </font></span></blockquote>
<br>
Regarding the other things that GIN does not solve: keep in mind that
we&#39;re not addressing every possible PBX/SSP interconnect issue here.
MARTINI has a refreshingly narrow charter, and that is by design. From
an IETF perspective, the rest of the peering problem space is being
solved mostly in SPEERMINT and DRINKS.<br>
<br>
I suggest you and Hans Erik take a moment to refresh your memories
about what we&#39;re working on here:
<a href=3D"https://datatracker.ietf.org/wg/martini/charter/" target=3D"_bla=
nk">https://datatracker.ietf.org/wg/martini/charter/</a><br>
<br>
/a</font><br>
</font></font></font>
</div>

</blockquote></div><br>

--000e0ce04002f63b8704831967d5--

From adam@nostrum.com  Wed Mar 31 07:20:10 2010
Return-Path: <adam@nostrum.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 003233A67B1 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.78
X-Spam-Level: 
X-Spam-Status: No, score=-0.78 tagged_above=-999 required=5 tests=[AWL=0.690,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, SPF_PASS=-0.001]
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 Bdns7JgYseJy for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:20:08 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 187C03A6931 for <martini@ietf.org>; Wed, 31 Mar 2010 07:19:54 -0700 (PDT)
Received: from [172.16.3.231] (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o2VEKLJo081924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Mar 2010 09:20:21 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4BB35A25.1050308@nostrum.com>
Date: Wed, 31 Mar 2010 09:20:21 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org>	 <A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net>	 <9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com>	 <A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net>	 <g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com>	 <A444A0F8084434499206E78C106220CADE11BA34@MCHP058A.global-ad.net>	 <x2y9ae56b1e1003300349gc3ec82c7o449ba7554b7740b3@mail.gmail.com>	 <A444A0F8084434499206E78C106220CADE11BF8E@MCHP058A.global-ad.net>	 <EDC0A1AE77C57744B664A310A0B23AE20D1C8238@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	 <4BB35877.9030409@nostrum.com> <n2z9ae56b1e1003310717v4b966f33j3709aa055b058f2d@mail.gmail.com>
In-Reply-To: <n2z9ae56b1e1003310717v4b966f33j3709aa055b058f2d@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 14:20:10 -0000

On 3/31/10 9:17 AM, Hans Erik van Elburg wrote:
> Adam,
>
> Did that several times:
> "The task of this working group is to to standardize a multiple-AoR
> registration mechanism for SIP that can be widely deployed by service
> providers at large scale."

And, from that, you deduced that we need to talk about SDP profiles?

/a

From pkyzivat@cisco.com  Wed Mar 31 07:38:25 2010
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 9A6A03A6967 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:38:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.625
X-Spam-Level: 
X-Spam-Status: No, score=-8.625 tagged_above=-999 required=5 tests=[AWL=0.844,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_HI=-8]
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 mMRi3r6+lSft for <martini@core3.amsl.com>; Wed, 31 Mar 2010 07:38:24 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 8DB063A69DA for <martini@ietf.org>; Wed, 31 Mar 2010 07:38:22 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEADD7sktAZnwM/2dsb2JhbACbNnGoCZkbgmCCIAQ
X-IronPort-AV: E=Sophos;i="4.51,341,1267401600"; d="scan'208";a="97816574"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 31 Mar 2010 14:38:52 +0000
Received: from [161.44.174.156] (dhcp-161-44-174-156.cisco.com [161.44.174.156]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o2VEcq8i028788; Wed, 31 Mar 2010 14:38:52 GMT
Message-ID: <4BB35E7C.30808@cisco.com>
Date: Wed, 31 Mar 2010 10:38:52 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org>	<074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org>	<s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com>	<A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net>	<9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com>	<A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net>	<g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com>	<A444A0F8084434499206E78C106220CADE11BA34@MCHP058A.global-ad.net>	<x2y9ae56b1e1003300349gc3ec82c7o449ba7554b7740b3@mail.gmail.com>	<A444A0F8084434499206E78C106220CADE11BF8E@MCHP058A.global-ad.net> <EDC0A1AE77C57744B664A310A0B23AE20D1C8238@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE20D1C8238@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 14:38:25 -0000

DRAGE, Keith (Keith) wrote:
> So assuming that this text is accepted, I guess the key argument of 
> providing this distinction is not that both behaviours are non-standard, 
> but that some means is needed to distinguish the two.
>  
> While I do not have a problem with that specifically, I still have an 
> issue that providing some signalling to do this solves all the issues. 
> There are all sorts of other issues associated with what the PBX 
> "expects" that also cause all sorts of issues, such as whether it 
> expects a tel URI in tel URI format or SIP URI format, and so on, that 
> are not signalled.

> Therefore at the end of the day, one is still going to end up with 
> configuration information at either end of this interface that is not 
> explicitly signalled, and in the absence of both sides having 
> preconfigured knowledge of that information, the interface is not going 
> to work.

The simple answer to this is that such "expectations" should be 
abandoned, in favor of supporting all valid usage that conforms to the 
basic standards and specified options. It is not rocket science to 
support a tel URI. (Though I'm not certain what the context is where 
that particular issue would come up.)

	Thanks,
	Paul

> regards
>  
> Keith
>  
> ------------------------------------------------------------------------
> *From:* martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] *On 
> Behalf Of *Elwell, John
> *Sent:* Tuesday, March 30, 2010 6:11 PM
> *To:* Hans Erik van Elburg
> *Cc:* martini@ietf.org
> *Subject:* Re: [martini] #21: 3.2.2 describes an issue with some PBX
> 
>     OK, fixed in my working copy.
>      
>     John
> 
>         ------------------------------------------------------------------------
>         *From:* Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
>         *Sent:* 30 March 2010 11:49
>         *To:* Elwell, John
>         *Cc:* martini@ietf.org
>         *Subject:* Re: [martini] #21: 3.2.2 describes an issue with some PBX
> 
>         Hi John,
> 
>         Inline...
> 
>         /Hans Erik van Elburg
> 
>         On Mon, Mar 29, 2010 at 9:55 PM, Elwell, John
>         <john.elwell@siemens-enterprise.com
>         <mailto:john.elwell@siemens-enterprise.com>> wrote:
> 
>             Hans Erik,
> 
>             I think the point you are trying to make is that it is not
>             one-sided. The fact is, each side has different ways of
>             working, and you need to have the two sides operating in
>             compatible manners for it to work. In practice, I think
>             there are other variants, besides the two cited in the
>             present 3.2.2.
> 
>         Yes. And there is no objective way to automatically determine
>         what variant the PBX or the SSP is supporting. Which is what an
>         options tag could resolve.
>          
> 
>             I would suggest:
> 
>                    <t>Even where all information needed by the SIP-PBX
>             is provided, in some deployments inbound SIP requests from
>             the SSP have the registered Contact URI in the Request-URI,
>             whereas in other deployments inbound SIP requests have the
>             intended target (AOR) in the Request-URI and the Contact URI
>             in the Route header field. There are other variants too.
>             Interoperability problems arise when a PBX designed for or
>             configured for one variant attempts to interwork with an SSP
>             designed for or configured for another variant.</t>
> 
>         Yes, slightly modified to add the objective means issue:
>          <t>Even where all information needed by the SIP-PBX is
>         provided, in some deployments inbound SIP requests from the SSP
>         have the registered PBX Contact URI in the Request-URI, whereas
>         in other deployments inbound SIP requests have the intended
>         target PBX user (AOR) in the Request-URI and the Contact URI in
>         the Route header field. There are other variants too.
>         Interoperability problems arise when a PBX designed for or
>         configured for one variant attempts to interwork with an SSP
>         designed for or configured for another variant. There is
>         currently no objective means in the signalling during
>         registration for either party to discover what mechanism the
>         other side supports.</t>
>          
> 
>             To accompany this, I think the title of the section should
>             be changed too: "Inconsistent placement of information in
>             inbound requests"
> 
>         Yes, slightly modified to make it more specific: "Inconsistent
>         placement of target URI information in inbound requests".
>          
> 
>             John
> 
>              > -----Original Message-----
>              > From: Hans Erik van Elburg
>             [mailto:ietf.hanserik@gmail.com
>             <mailto:ietf.hanserik@gmail.com>]
>              > Sent: 29 March 2010 17:27
>              > To: Elwell, John
>              > Cc: martini@ietf.org <mailto:martini@ietf.org>
>              > Subject: Re: [martini] #21: 3.2.2 describes an issue with
>             some PBX
>              >
>              > Hi John,
>              >
>              > I was just trying to find a text that describes the issue.
>              >
>              > But now the issue reads like "some PBX like apples, some like
>              > bananas". To me that does not sound like a usefull issue to
>              > describe in an RFC.
>              >
>              > So I think one or two more sentence would make clear why this
>              > is an issue.
>              >
>              > I think there is multiple underlying issues here:
>              > - PBX have different SIP profiles or all SIP-PBX are
>             different
>              > - PBX support SIP trunking flavour A, or support SIP trunking
>              > flavour B
>              > - SSP systems don't know what mechanism the PBX support (can
>              > be resolved with explicit indicator, this draft proposes an
>              > indicator for flavour B but for another purpose it seems)
>              > - PBX do not know what SIP trunking flavour the SSP supports
>              > (not addressed it seems)
>              >
>              > I don't seem to have a lucky hand with proposing an improved
>              > text, so maybe you should have a go at it.
>              >
>              > BR,
>              > /Hans Erik van Elburg
>              >
>              > p.s. I never said or implied that a SIP-PBX shall implement
>              > IMS. But it would be really, really, really good if they
>              > would interwork on the UNI with the IMS business trunking.  I
>              > think that should also be in your interest and in fact you
>              > have been part of that work...
>              >
>              >
>              >
>              > On Mon, Mar 29, 2010 at 5:56 PM, Elwell, John
>              > <john.elwell@siemens-enterprise.com
>             <mailto:john.elwell@siemens-enterprise.com>> wrote:
>              >
>              >
>              >       Hans Erik,
>              >
>              >       As an individual, I disagree with the proposed text,
>              > since it is misleading. The "international standards" to
>              > which you prefer are standards specific to an IMS
>              > environment. The implication of the wording as proposed is
>              > that SIP-PBXs ought to implement IMS specifications. And as
>              > Hadriel points out, implementing those IMS specifications
>              > does not eliminate the problems that the SIPconnect people
>              > are trying to solve. I believe the existing text in draft-03
>              > is sufficient.
>              >
>              >
>              >       John
>              >
>              >       > -----Original Message-----
>              >       > From: Hans Erik van Elburg
>             [mailto:ietf.hanserik@gmail.com
>             <mailto:ietf.hanserik@gmail.com>]
>              >
>              >       > Sent: 26 March 2010 23:03
>              >       > To: Elwell, John
>              >       > Cc: martini@ietf.org <mailto:martini@ietf.org>
>              >       > Subject: Re: [martini] #21: 3.2.2 describes an issue
>              > with some PBX
>              >       >
>              >       > I will not argue with you about the validity of
>             that argument.
>              >       >
>              >       > Can you agree to the modified text?
>              >       >
>              >       > "Request-URI vs. loose-route acceptance
>              >       > Some IP-PBX do not implement international
>             standards or SIP
>              >       > profiles for SIP trunking. As a consequence some
>             SIP-PBXs
>              >       > expect that inbound SIP requests from the SSP
>             will have the
>              >       > registered Contact-URI in the Request-URI, and
>             thus not
>              >       > interoperate with the loose-route scheme of 3GPP
>             and ETSI.
>              >       > Other SIP-PBXs are fine with the Request-URI
>             being the
>              >       > intended target, but cannot handle receiving a
>             Route header
>              >       > field identifying their registered Contact-URI as a
>              >       > loose-route entry."
>              >       >
>              >       > BR,
>              >       > /Hans Erik van Elburg
>              >       >
>              >       >
>              >       > On Fri, Mar 26, 2010 at 9:03 PM, Elwell, John
>              >       > <john.elwell@siemens-enterprise.com
>             <mailto:john.elwell@siemens-enterprise.com>> wrote:
>              >       >
>              >       >
>              >       >       The IETF does not have a mechanism, and
>             that is the
>              >       > reason for the MARTINI work. In particular, the
>             IETF has not
>              >       > published the so-called loose-route mechanism.
>             Hence the
>              >       > reason for the IETF, as owner of SIP, to publish
>             a mechanism
>              >       > for bulk registrations.
>              >       >
>              >       >       John
>              >       >
>              >       >
>              >       >       > -----Original Message-----
>              >       >       > From: Hans Erik van Elburg
>              > [mailto:ietf.hanserik@gmail.com
>             <mailto:ietf.hanserik@gmail.com>]
>              >       >       > Sent: 26 March 2010 02:21
>              >       >       > To: trac@localhost.amsl.com
>             <mailto:trac@localhost.amsl.com>
>              >       >       > Cc: Elwell, John; martini@ietf.org
>             <mailto:martini@ietf.org>
>              >       >       > Subject: Re: [martini] #21: 3.2.2
>             describes an issue
>              >       > with some PBX
>              >       >       >
>              >       >       >
>              >       >       > Then you should rephrase to what the real
>             issue is:
>              >       >       > "
>              >       >       >
>              >       >       >
>              >       >       > Request-URI vs. loose-route acceptance
>              >       >       >
>              >       >       >
>              >       >       > Some IP-PBX do not implement international
>              > standards or SIP
>              >       >       > profiles for SIP trunking. As a consequence
>              > some SIP-PBXs
>              >       >       > expect that inbound SIP requests from the SSP
>              > will have the
>              >       >       > registered Contact-URI in the Request-URI,
>              > and thus not
>              >       >       > interoperate with the loose-route scheme of
>              > 3GPP and ETSI.
>              >       >       > Other SIP-PBXs are fine with the
>             Request-URI being the
>              >       >       > intended target, but cannot handle receiving
>              > a Route header
>              >       >       > field identifying their registered
>             Contact-URI as a
>              >       >       > loose-route entry."
>              >       >       >
>              >       >       >
>              >       >       > Is this an issue, yes. Does introducing
>             yet another
>              >       > profile help? No.
>              >       >       >
>              >       >       > /Hans Erik van Elburg
>              >       >       >
>              >       >       >
>              >       >       > On Thu, Mar 25, 2010 at 9:22 PM, martini
>             issue tracker
>              >       >       > <trac@tools.ietf.org
>             <mailto:trac@tools.ietf.org>> wrote:
>              >       >       >
>              >       >       >
>              >       >       >       #21: 3.2.2 describes an issue with
>             some PBX
>              >       >       >
>              >       >       >
>              >
>             -------------------------------------+------------------------
>              >       >       > --------------
>              >       >       >        Reporter:  ietf.hanserik@...
>              > |        Owner:
>              >       >       >
>              >       >       >           Type:  defect                   |
>              >       > Status:  closed
>              >       >       >
>              >       >       >        Priority:  minor                    |
>              >       > Milestone:  milestone1
>              >       >       >       Component:  reqs                     |
>              >       > Version:  1.0
>              >       >       >
>              >       >       >        Severity:  In WG Last Call          |
>              >       > Resolution:  invalid
>              >       >       >        Keywords:                           |
>              >       >       >
>              >       >       >
>              >
>             -------------------------------------+------------------------
>              >       >       > --------------
>              >       >       >       Changes (by john.elwell@...):
>              >       >       >
>              >       >       >        * status:  new => closed
>              >       >       >        * resolution:  => invalid
>              >       >       >
>              >       >       >
>              >       >       >       Comment:
>              >       >       >
>              >       >       >
>              >       >       >        The text of 3.2.2 just underlines the
>              > fact that there
>              >       >       > are different
>              >       >       >        implementations around. A PBX that
>              > expects the loose
>              >       >       > route mechanism to be
>              >       >       >        used would fail to interwork with
>             SSPs using a
>              >       >       > different mechanism (e.g.,
>              >       >       >        SIPconnect 1.0), and a PBX not
>              > expecting the loose
>              >       >       > route mechanism to be
>              >       >       >        used would fail to interwork with
>             a loose route
>              >       >       > implementation (e.g.,
>              >       >       >        ETSI/3GPP). Hence the urgent need for
>              > a standard.
>              >       >       >
>              >       >       >       --
>              >       >       >       Ticket URL:
>              >       >       >
>              >       >
>              >
>             <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
>              >       >       >
>              >       >       >       martini
>             <http://tools.ietf.org/martini/>
>              >       >       >
>              >       >       >
>              >       >       >      
>             _______________________________________________
>              >       >       >       martini mailing list
>              >       >       >       martini@ietf.org
>             <mailto:martini@ietf.org>
>              >       >       >      
>             https://www.ietf.org/mailman/listinfo/martini
>              >       >       >
>              >       >       >
>              >       >       >
>              >       >       >
>              >       >
>              >       >
>              >       >
>              >
>              >
>              > 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini

From spencer@wonderhamster.org  Wed Mar 31 08:29:14 2010
Return-Path: <spencer@wonderhamster.org>
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 08FD33A69F2 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 08:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level: 
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 G6EximyopXvH for <martini@core3.amsl.com>; Wed, 31 Mar 2010 08:29:13 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 70FF93A6A0C for <martini@ietf.org>; Wed, 31 Mar 2010 08:29:12 -0700 (PDT)
Received: from S73602b ([12.172.14.11]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0M3RNI-1NfT0A0qOW-00qoPr; Wed, 31 Mar 2010 11:29:13 -0400
Message-ID: <D33441D41BE14D02A0FE96E2AFEFF7C9@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, "Adam Roach" <adam@nostrum.com>
References: <065.8a4abab950b8bd86aa5b8dd3edb78118@tools.ietf.org><074.f6306870cffc33c30891c5a51ff71c56@tools.ietf.org><s2h9ae56b1e1003260221t7426a1efsae9b09a823b067ed@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B377@MCHP058A.global-ad.net><9ae56b1e1003261603n12235533s3e9801bd41b09821@mail.gmail.com><A444A0F8084434499206E78C106220CADE11B923@MCHP058A.global-ad.net><g2h9ae56b1e1003290927uc4a7487yaac99df7cd4070f6@mail.gmail.com><A444A0F8084434499206E78C106220CADE11BA34@MCHP058A.global-ad.net><x2y9ae56b1e1003300349gc3ec82c7o449ba7554b7740b3@mail.gmail.com><A444A0F8084434499206E78C106220CADE11BF8E@MCHP058A.global-ad.net><EDC0A1AE77C57744B664A310A0B23AE20D1C8238@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com><4BB35877.9030409@nostrum.com> <EDC0A1AE77C57744B664A310A0B23AE20D1C8343@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Wed, 31 Mar 2010 10:28:55 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0997_01CAD0BC.F76F5C60"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1/ACvJj1i/nPv+BUxWMl34y4H8Hkt68p1gjNI5 kc6hNfV1mpDucc1Hoi5rWiAILkZd+zOHHcCCDRPPm53kFAk50X WNE3Yvi3RAVZTawuRQLLwXTGw8s09FWgunc4oa7St0=
Cc: martini@ietf.org
Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 15:29:14 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0997_01CAD0BC.F76F5C60
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Speaking as chair ... and the chairs have not declared consensus on the =
solutions document. We have agreed to adopt GIN as a working group draft =
for the solutions milestone, and this would be a great time for the =
working group to start working on that draft.

Spencer
  ----- Original Message -----=20
  From: DRAGE, Keith (Keith)=20
  To: Adam Roach=20
  Cc: martini@ietf.org=20
  Sent: Wednesday, March 31, 2010 9:15 AM
  Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX


  We are talking about the an issue on the requirements document here - =
not a solutions document that as far as I am concerned does not have =
consensus

  Keith



-------------------------------------------------------------------------=
---
    From: Adam Roach [mailto:adam@nostrum.com]=20
    Sent: Wednesday, March 31, 2010 3:13 PM
    To: DRAGE, Keith (Keith)
    Cc: Elwell, John; Hans Erik van Elburg; martini@ietf.org
    Subject: Re: [martini] #21: 3.2.2 describes an issue with some PBX


    On 3/31/10 6:18 AM, DRAGE, Keith (Keith) wrote:=20
      ...I still have an issue that providing some signalling to do this =
solves all the issues. There are all sorts of other issues associated =
with what the PBX "expects" that also cause all sorts of issues, such as =
whether it expects a tel URI in tel URI format or SIP URI format...


    What are you talking about? GIN nails down the format what shows up =
at the PBX: they're SIP (or SIPS) URIs.


      ...and so on, that are not signalled.


    Regarding the other things that GIN does not solve: keep in mind =
that we're not addressing every possible PBX/SSP interconnect issue =
here. MARTINI has a refreshingly narrow charter, and that is by design. =
>From an IETF perspective, the rest of the peering problem space is being =
solved mostly in SPEERMINT and DRINKS.

    I suggest you and Hans Erik take a moment to refresh your memories =
about what we're working on here: =
https://datatracker.ietf.org/wg/martini/charter/

    /a



-------------------------------------------------------------------------=
-----


  _______________________________________________
  martini mailing list
  martini@ietf.org
  https://www.ietf.org/mailman/listinfo/martini

------=_NextPart_000_0997_01CAD0BC.F76F5C60
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3DISO-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18876">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff text=3D#000000>
<DIV><FONT size=3D2>Speaking as chair ... and the chairs have not =
declared=20
consensus on the solutions document. We have agreed to adopt GIN as a =
working=20
group draft for the solutions milestone, and this would be a great time =
for the=20
working group to start working on that draft.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Spencer</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; =
PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: =
black"><B>From:</B>=20
  <A title=3Dkeith.drage@alcatel-lucent.com=20
  href=3D"mailto:keith.drage@alcatel-lucent.com">DRAGE, Keith =
(Keith)</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Dadam@nostrum.com =

  href=3D"mailto:adam@nostrum.com">Adam Roach</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A title=3Dmartini@ietf.org =

  href=3D"mailto:martini@ietf.org">martini@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, March 31, 2010 =
9:15=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [martini] #21: =
3.2.2=20
  describes an issue with some PBX</DIV>
  <DIV><BR></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D214141514-31032010><FONT =
color=3D#0000ff=20
  size=3D2 face=3DArial>We are talking about the an issue on the =
requirements=20
  document here - not a solutions document that as far as I am concerned =
does=20
  not have consensus</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D214141514-31032010><FONT =
color=3D#0000ff=20
  size=3D2 face=3DArial></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D214141514-31032010><FONT =
color=3D#0000ff=20
  size=3D2 face=3DArial>Keith</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE=20
  style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; =
MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
    <DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT size=3D2 face=3DTahoma><B>From:</B> Adam Roach =
[mailto:adam@nostrum.com]=20
    <BR><B>Sent:</B> Wednesday, March 31, 2010 3:13 PM<BR><B>To:</B> =
DRAGE,=20
    Keith (Keith)<BR><B>Cc:</B> Elwell, John; Hans Erik van Elburg; <A=20
    =
href=3D"mailto:martini@ietf.org">martini@ietf.org</A><BR><B>Subject:</B> =
Re:=20
    [martini] #21: 3.2.2 describes an issue with some =
PBX<BR></FONT><BR></DIV>
    <DIV></DIV>On 3/31/10 6:18 AM, DRAGE, Keith (Keith) wrote:=20
    <BLOCKQUOTE=20
    =
cite=3Dmid:EDC0A1AE77C57744B664A310A0B23AE20D1C8238@FRMRSSXCHMBSC3.dc-m.a=
lcatel-lucent.com=20
    type=3D"cite">
      <META name=3DGENERATOR content=3D"MSHTML 6.00.2900.3660">
      <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D756321311-31032010></SPAN><SPAN=20
      class=3D756321311-31032010><FONT color=3D#0000ff size=3D2 =
face=3DArial>...I still=20
      have an issue that providing some signalling to do this solves all =
the=20
      issues. There are all sorts of other issues associated with what =
the PBX=20
      "expects" that also cause all sorts of issues, such as whether it =
expects=20
      a tel URI in tel URI format or SIP URI=20
    format...</FONT></SPAN><BR></DIV></BLOCKQUOTE><FONT =
color=3D#0000ff><FONT=20
    size=3D2><FONT face=3DArial><FONT color=3D#000000><BR>What are you =
talking about?=20
    GIN nails down the format what shows up at the PBX: they're SIP (or =
SIPS)=20
    URIs.<BR><BR>
    <BLOCKQUOTE type=3D"cite"><SPAN class=3D756321311-31032010><FONT =
color=3D#0000ff=20
      size=3D2 face=3DArial>...and so on, that are not=20
    signalled.<BR></FONT></SPAN></BLOCKQUOTE><BR>Regarding the other =
things that=20
    GIN does not solve: keep in mind that we're not addressing every =
possible=20
    PBX/SSP interconnect issue here. MARTINI has a refreshingly narrow =
charter,=20
    and that is by design. From an IETF perspective, the rest of the =
peering=20
    problem space is being solved mostly in SPEERMINT and =
DRINKS.<BR><BR>I=20
    suggest you and Hans Erik take a moment to refresh your memories =
about what=20
    we're working on here: <A class=3Dmoz-txt-link-freetext=20
    =
href=3D"https://datatracker.ietf.org/wg/martini/charter/">https://datatra=
cker.ietf.org/wg/martini/charter/</A><BR><BR>/a</FONT><BR></BLOCKQUOTE></=
FONT></FONT></FONT>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>martini =
mailing=20
  =
list<BR>martini@ietf.org<BR>https://www.ietf.org/mailman/listinfo/martini=
<BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0997_01CAD0BC.F76F5C60--


From john.elwell@siemens-enterprise.com  Wed Mar 31 08:41:27 2010
Return-Path: <john.elwell@siemens-enterprise.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 BBB863A6A34 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 08:41:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.467
X-Spam-Level: 
X-Spam-Status: No, score=-0.467 tagged_above=-999 required=5 tests=[AWL=1.002,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 lEdmWJgVD1cW for <martini@core3.amsl.com>; Wed, 31 Mar 2010 08:41:26 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 9F6513A681A for <martini@ietf.org>; Wed, 31 Mar 2010 08:41:18 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1410532; Wed, 31 Mar 2010 17:41:48 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id CC5CE1EB82B6; Wed, 31 Mar 2010 17:41:48 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Wed, 31 Mar 2010 17:41:49 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hans Erik van Elburg <ietf.hanserik@gmail.com>, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Date: Wed, 31 Mar 2010 17:41:47 +0200
Thread-Topic: Need for a SIP/SDP profile for SIP trunking , was Re: [martini] #21: 	3.2.2 describes an issue with some PBX
Thread-Index: AcrQxVJd63qpV5hrR+CgoIga7UnubwAIwxjw
Message-ID: <A444A0F8084434499206E78C106220CADE18B7D6@MCHP058A.global-ad.net>
References: <w2v9ae56b1e1003310428o6fc07243j294b603eec953a1a@mail.gmail.com>
In-Reply-To: <w2v9ae56b1e1003310428o6fc07243j294b603eec953a1a@mail.gmail.com>
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
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re:  #21: 	3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 15:41:27 -0000

I don't see the relevance of SDP, codecs, voice, fax, etc.. These are all i=
ssues for the UAs behind the SIP-PBX and the SSP. MARTINI is about reachabi=
lity of the SIP-PBX from an SSP.

John

> -----Original Message-----
> From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com]
> Sent: 31 March 2010 12:29
> To: DRAGE, Keith (Keith)
> Cc: Elwell, John; martini@ietf.org
> Subject: Need for a SIP/SDP profile for SIP trunking , was
> Re: [martini] #21: 3.2.2 describes an issue with some PBX
>
> Yes, I agree with that observation.
>
> Only solving the routing issue does not solve the overall
> problem. For that a minimum SIP/SDP profile needs to be
> agreed upon. Also what are common denominator as codec for
> voice, fax, dtmf etc.
>
> The question rises if there should be an option tag to signal
> support for a profile instead of only signalling what routing
> method is preferred.
>
> BR,
> /Hans Erik van Elburg
>
>
>
> On Wed, Mar 31, 2010 at 1:18 PM, DRAGE, Keith (Keith)
> <keith.drage@alcatel-lucent.com> wrote:
>
>
>       So assuming that this text is accepted, I guess the key
> argument of providing this distinction is not that both
> behaviours are non-standard, but that some means is needed to
> distinguish the two.
>
>       While I do not have a problem with that specifically, I
> still have an issue that providing some signalling to do this
> solves all the issues. There are all sorts of other issues
> associated with what the PBX "expects" that also cause all
> sorts of issues, such as whether it expects a tel URI in tel
> URI format or SIP URI format, and so on, that are not signalled.
>
>       Therefore at the end of the day, one is still going to
> end up with configuration information at either end of this
> interface that is not explicitly signalled, and in the
> absence of both sides having preconfigured knowledge of that
> information, the interface is not going to work.
>
>       regards
>
>       Keith
>
> ________________________________
>
>       From: martini-bounces@ietf.org
> [mailto:martini-bounces@ietf.org] On Behalf Of Elwell, John
>       Sent: Tuesday, March 30, 2010 6:11 PM
>       To: Hans Erik van Elburg
>
>       Cc: martini@ietf.org
>       Subject: Re: [martini] #21: 3.2.2 describes an issue
> with some PBX
>
>
>
>
>               OK, fixed in my working copy.
>
>               John
>
>
> ________________________________
>
>                       From: Hans Erik van Elburg
> [mailto:ietf.hanserik@gmail.com]
>                       Sent: 30 March 2010 11:49
>                       To: Elwell, John
>                       Cc: martini@ietf.org
>                       Subject: Re: [martini] #21: 3.2.2
> describes an issue with some PBX
>
>
>                       Hi John,
>
>                       Inline...
>
>                       /Hans Erik van Elburg
>
>
>                       On Mon, Mar 29, 2010 at 9:55 PM,
> Elwell, John <john.elwell@siemens-enterprise.com> wrote:
>
>
>                               Hans Erik,
>
>                               I think the point you are
> trying to make is that it is not one-sided. The fact is, each
> side has different ways of working, and you need to have the
> two sides operating in compatible manners for it to work. In
> practice, I think there are other variants, besides the two
> cited in the present 3.2.2.
>
>                       Yes. And there is no objective way to
> automatically determine what variant the PBX or the SSP is
> supporting. Which is what an options tag could resolve.
>
>
>                               I would suggest:
>
>                                      <t>Even where all
> information needed by the SIP-PBX is provided, in some
> deployments inbound SIP requests from the SSP have the
> registered Contact URI in the Request-URI, whereas in other
> deployments inbound SIP requests have the intended target
> (AOR) in the Request-URI and the Contact URI in the Route
> header field. There are other variants too. Interoperability
> problems arise when a PBX designed for or configured for one
> variant attempts to interwork with an SSP designed for or
> configured for another variant.</t>
>
>
>                       Yes, slightly modified to add the
> objective means issue:
>                        <t>Even where all information needed
> by the SIP-PBX is provided, in some deployments inbound SIP
> requests from the SSP have the registered PBX Contact URI in
> the Request-URI, whereas in other deployments inbound SIP
> requests have the intended target PBX user (AOR) in the
> Request-URI and the Contact URI in the Route header field.
> There are other variants too. Interoperability problems arise
> when a PBX designed for or configured for one variant
> attempts to interwork with an SSP designed for or configured
> for another variant. There is currently no objective means in
> the signalling during registration for either party to
> discover what mechanism the other side supports.</t>
>
>
>                               To accompany this, I think the
> title of the section should be changed too: "Inconsistent
> placement of information in inbound requests"
>
>
>
>                       Yes, slightly modified to make it more
> specific: "Inconsistent placement of target URI information
> in inbound requests".
>
>
>                               John
>
>                               > -----Original Message-----
>                               > From: Hans Erik van Elburg
> [mailto:ietf.hanserik@gmail.com]
>
>                               > Sent: 29 March 2010 17:27
>                               > To: Elwell, John
>                               > Cc: martini@ietf.org
>                               > Subject: Re: [martini] #21:
> 3.2.2 describes an issue with some PBX
>                               >
>                               > Hi John,
>                               >
>                               > I was just trying to find a
> text that describes the issue.
>                               >
>                               > But now the issue reads like
> "some PBX like apples, some like
>                               > bananas". To me that does not
> sound like a usefull issue to
>                               > describe in an RFC.
>                               >
>                               > So I think one or two more
> sentence would make clear why this
>                               > is an issue.
>                               >
>                               > I think there is multiple
> underlying issues here:
>                               > - PBX have different SIP
> profiles or all SIP-PBX are different
>                               > - PBX support SIP trunking
> flavour A, or support SIP trunking
>                               > flavour B
>                               > - SSP systems don't know what
> mechanism the PBX support (can
>                               > be resolved with explicit
> indicator, this draft proposes an
>                               > indicator for flavour B but
> for another purpose it seems)
>                               > - PBX do not know what SIP
> trunking flavour the SSP supports
>                               > (not addressed it seems)
>                               >
>                               > I don't seem to have a lucky
> hand with proposing an improved
>                               > text, so maybe you should
> have a go at it.
>                               >
>                               > BR,
>                               > /Hans Erik van Elburg
>                               >
>                               > p.s. I never said or implied
> that a SIP-PBX shall implement
>                               > IMS. But it would be really,
> really, really good if they
>                               > would interwork on the UNI
> with the IMS business trunking.  I
>                               > think that should also be in
> your interest and in fact you
>                               > have been part of that work...
>                               >
>                               >
>                               >
>                               > On Mon, Mar 29, 2010 at 5:56
> PM, Elwell, John
>                               >
> <john.elwell@siemens-enterprise.com> wrote:
>                               >
>                               >
>                               >       Hans Erik,
>                               >
>                               >       As an individual, I
> disagree with the proposed text,
>                               > since it is misleading. The
> "international standards" to
>                               > which you prefer are
> standards specific to an IMS
>                               > environment. The implication
> of the wording as proposed is
>                               > that SIP-PBXs ought to
> implement IMS specifications. And as
>                               > Hadriel points out,
> implementing those IMS specifications
>                               > does not eliminate the
> problems that the SIPconnect people
>                               > are trying to solve. I
> believe the existing text in draft-03
>                               > is sufficient.
>                               >
>                               >
>                               >       John
>                               >
>                               >       > -----Original Message-----
>                               >       > From: Hans Erik van
> Elburg [mailto:ietf.hanserik@gmail.com]
>                               >
>                               >       > Sent: 26 March 2010 23:03
>                               >       > To: Elwell, John
>                               >       > Cc: martini@ietf.org
>                               >       > Subject: Re:
> [martini] #21: 3.2.2 describes an issue
>                               > with some PBX
>                               >       >
>                               >       > I will not argue with
> you about the validity of that argument.
>                               >       >
>                               >       > Can you agree to the
> modified text?
>                               >       >
>                               >       > "Request-URI vs.
> loose-route acceptance
>                               >       > Some IP-PBX do not
> implement international standards or SIP
>                               >       > profiles for SIP
> trunking. As a consequence some SIP-PBXs
>                               >       > expect that inbound
> SIP requests from the SSP will have the
>                               >       > registered
> Contact-URI in the Request-URI, and thus not
>                               >       > interoperate with the
> loose-route scheme of 3GPP and ETSI.
>                               >       > Other SIP-PBXs are
> fine with the Request-URI being the
>                               >       > intended target, but
> cannot handle receiving a Route header
>                               >       > field identifying
> their registered Contact-URI as a
>                               >       > loose-route entry."
>                               >       >
>                               >       > BR,
>                               >       > /Hans Erik van Elburg
>                               >       >
>                               >       >
>                               >       > On Fri, Mar 26, 2010
> at 9:03 PM, Elwell, John
>                               >       >
> <john.elwell@siemens-enterprise.com> wrote:
>                               >       >
>                               >       >
>                               >       >       The IETF does
> not have a mechanism, and that is the
>                               >       > reason for the
> MARTINI work. In particular, the IETF has not
>                               >       > published the
> so-called loose-route mechanism. Hence the
>                               >       > reason for the IETF,
> as owner of SIP, to publish a mechanism
>                               >       > for bulk registrations.
>                               >       >
>                               >       >       John
>                               >       >
>                               >       >
>                               >       >       > -----Original
> Message-----
>                               >       >       > From: Hans
> Erik van Elburg
>                               > [mailto:ietf.hanserik@gmail.com]
>                               >       >       > Sent: 26
> March 2010 02:21
>                               >       >       > To:
> trac@localhost.amsl.com
>                               >       >       > Cc: Elwell,
> John; martini@ietf.org
>                               >       >       > Subject: Re:
> [martini] #21: 3.2.2 describes an issue
>                               >       > with some PBX
>                               >       >       >
>                               >       >       >
>                               >       >       > Then you
> should rephrase to what the real issue is:
>                               >       >       > "
>                               >       >       >
>                               >       >       >
>                               >       >       > Request-URI
> vs. loose-route acceptance
>                               >       >       >
>                               >       >       >
>                               >       >       > Some IP-PBX
> do not implement international
>                               > standards or SIP
>                               >       >       > profiles for
> SIP trunking. As a consequence
>                               > some SIP-PBXs
>                               >       >       > expect that
> inbound SIP requests from the SSP
>                               > will have the
>                               >       >       > registered
> Contact-URI in the Request-URI,
>                               > and thus not
>                               >       >       > interoperate
> with the loose-route scheme of
>                               > 3GPP and ETSI.
>                               >       >       > Other
> SIP-PBXs are fine with the Request-URI being the
>                               >       >       > intended
> target, but cannot handle receiving
>                               > a Route header
>                               >       >       > field
> identifying their registered Contact-URI as a
>                               >       >       > loose-route entry."
>                               >       >       >
>                               >       >       >
>                               >       >       > Is this an
> issue, yes. Does introducing yet another
>                               >       > profile help? No.
>                               >       >       >
>                               >       >       > /Hans Erik van Elburg
>                               >       >       >
>                               >       >       >
>                               >       >       > On Thu, Mar
> 25, 2010 at 9:22 PM, martini issue tracker
>                               >       >       >
> <trac@tools.ietf.org> wrote:
>                               >       >       >
>                               >       >       >
>                               >       >       >       #21:
> 3.2.2 describes an issue with some PBX
>                               >       >       >
>                               >       >       >
>                               >
> -------------------------------------+------------------------
>                               >       >       > --------------
>                               >       >       >
> Reporter:  ietf.hanserik@...
>                               > |        Owner:
>                               >       >       >
>                               >       >       >
> Type:  defect                   |
>                               >       > Status:  closed
>                               >       >       >
>                               >       >       >
> Priority:  minor                    |
>                               >       > Milestone:  milestone1
>                               >       >       >
> Component:  reqs                     |
>                               >       > Version:  1.0
>                               >       >       >
>                               >       >       >
> Severity:  In WG Last Call          |
>                               >       > Resolution:  invalid
>                               >       >       >
> Keywords:                           |
>                               >       >       >
>                               >       >       >
>                               >
> -------------------------------------+------------------------
>                               >       >       > --------------
>                               >       >       >       Changes
> (by john.elwell@...):
>                               >       >       >
>                               >       >       >        *
> status:  new =3D> closed
>                               >       >       >        *
> resolution:  =3D> invalid
>                               >       >       >
>                               >       >       >
>                               >       >       >       Comment:
>                               >       >       >
>                               >       >       >
>                               >       >       >        The
> text of 3.2.2 just underlines the
>                               > fact that there
>                               >       >       > are different
>                               >       >       >
> implementations around. A PBX that
>                               > expects the loose
>                               >       >       > route mechanism to be
>                               >       >       >        used
> would fail to interwork with SSPs using a
>                               >       >       > different
> mechanism (e.g.,
>                               >       >       >
> SIPconnect 1.0), and a PBX not
>                               > expecting the loose
>                               >       >       > route mechanism to be
>                               >       >       >        used
> would fail to interwork with a loose route
>                               >       >       > implementation (e.g.,
>                               >       >       >
> ETSI/3GPP). Hence the urgent need for
>                               > a standard.
>                               >       >       >
>                               >       >       >       --
>                               >       >       >       Ticket URL:
>                               >       >       >
>                               >       >
>                               >
> <http://trac.tools.ietf.org/wg/martini/trac/ticket/21#comment:1>
>                               >       >       >
>                               >       >       >       martini
> <http://tools.ietf.org/martini/>
>                               >       >       >
>                               >       >       >
>                               >       >       >
> _______________________________________________
>                               >       >       >       martini
> mailing list
>                               >       >       >       martini@ietf.org
>                               >       >       >
> https://www.ietf.org/mailman/listinfo/martini
>                               >       >       >
>                               >       >       >
>                               >       >       >
>                               >       >       >
>                               >       >
>                               >       >
>                               >       >
>                               >
>                               >
>                               >
>
>
>
>

From christer.holmberg@ericsson.com  Wed Mar 31 14:11:14 2010
Return-Path: <christer.holmberg@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 6FD333A697D for <martini@core3.amsl.com>; Wed, 31 Mar 2010 14:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.176
X-Spam-Level: 
X-Spam-Status: No, score=-4.176 tagged_above=-999 required=5 tests=[AWL=1.293,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 tZa3mAnydu-p for <martini@core3.amsl.com>; Wed, 31 Mar 2010 14:11:13 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id A7CC43A68BE for <martini@ietf.org>; Wed, 31 Mar 2010 14:11:12 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bf6ae000005bec-07-4bb3ba8e555d
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 25.7B.23532.E8AB3BB4; Wed, 31 Mar 2010 23:11:42 +0200 (CEST)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.2.223]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Wed, 31 Mar 2010 23:11:42 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: 'Spencer Dawkins' <spencer@wonderhamster.org>, Hans Erik van Elburg <ietf.hanserik@gmail.com>, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Date: Wed, 31 Mar 2010 23:11:41 +0200
Thread-Topic: [martini] Need for a SIP/SDP profile for SIP trunking , was Re: 	#21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrQ2Bmv1Nj8iOcLQ1C9Ru07o3UHUwAPThdA
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC745E21B5A90E@ESESSCMS0354.eemea.ericsson.se>
References: <w2v9ae56b1e1003310428o6fc07243j294b603eec953a1a@mail.gmail.com><m2k9ae56b1e1003310523zc70f6a83ub0e5b1bdaeddd5ce@mail.gmail.com><EDC0A1AE77C57744B664A310A0B23AE20D1C8293@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com><m2v9ae56b1e1003310548i739c29c1t8080612ae5b4eea7@mail.gmail.com> <FF84A09F50A6DC48ACB6714F4666CC745E21C25448@ESESSCMS0354.eemea.ericsson.se> <EC41EF9AA5E140A381247657BA04C611@china.huawei.com>
In-Reply-To: <EC41EF9AA5E140A381247657BA04C611@china.huawei.com>
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==
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was Re: 	#21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 21:11:14 -0000

Hi,=20
=20
>Speaking as chair, I can assure you that an overall SIP PBX profile is out=
 of scope for MARTINI :-)
>
>Speaking as an individual, I would expect that http://tools.ietf.org/html/=
rfc5727 would point to having a proposal for an IMS option tag going throug=
h DISPATCH, but DISPATCH can certainly send work to an=20
>existing working group, and if that happens, MARTINI would be an obvious c=
andidate destination.

I was wondering whether it could be taken directly to MARTINI. If it can be=
 considered helpful for the work we are doing I think it could fit the MART=
INI charter.

My main preference, however, is to have a single solution.

><out of scope for MARTINI mailing list>=20
>
>Again, speaking as an individual - my understanding is that the SIPconnect=
 guys were OK with an option tag for SIPconnect 1.1, because SIPconnect 1.0=
 was incredibly underspecified ("register one AOR and=20
>a miracle may occur"). SIPconnect really is ready to remove the earlier op=
tionless mode of operation from SIPconnect 1.1.
>
>Would ETSI/TISPAN/3GPP move to an optioned mode of operation for Release 1=
N? Or would this be retained, so that IMS would have two modes of operation=
?=20

I don't think the issue is whether 3GPP would document the IETF solution, b=
ut to allow implementations to know which solution(s) are supported.

Regards,

Christer






	----- Original Message -----=20
	From: Christer Holmberg <mailto:christer.holmberg@ericsson.com> =20
	To: Hans Erik van Elburg <mailto:ietf.hanserik@gmail.com>  ; DRAGE, Keith =
(Keith) <mailto:keith.drage@alcatel-lucent.com> =20
	Cc: martini@ietf.org=20
	Sent: Wednesday, March 31, 2010 8:01 AM
	Subject: Re: [martini] Need for a SIP/SDP profile for SIP trunking , was R=
e: #21: 3.2.2 describes an issue with some PBX

	Hi,
	=20
	While I agree on the usefulness of such profiles, I doubt IETF is the corr=
ect place to define those. I also think that it is outside the scope of MAR=
TINI.
	=20
	Now, regarding the option-tag to indicate the routing mechanism: since an =
option-tag requires an RFC, would MARTINI be the place to define such optio=
n-tag for the IMS solution (should the involved people choose to define one=
)?


From christer.holmberg@ericsson.com  Wed Mar 31 14:15:32 2010
Return-Path: <christer.holmberg@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 A45613A6AD5 for <martini@core3.amsl.com>; Wed, 31 Mar 2010 14:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.914
X-Spam-Level: 
X-Spam-Status: No, score=-3.914 tagged_above=-999 required=5 tests=[AWL=0.954,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, 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 wkpgsNZs4afA for <martini@core3.amsl.com>; Wed, 31 Mar 2010 14:15:28 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id F1EE03A6AD6 for <martini@ietf.org>; Wed, 31 Mar 2010 14:15:20 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bf6ae000005bec-42-4bb3bb8710b4
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 6B.9B.23532.78BB3BB4; Wed, 31 Mar 2010 23:15:51 +0200 (CEST)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.2.223]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Wed, 31 Mar 2010 23:15:50 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: 'Hans Erik van Elburg' <ietf.hanserik@gmail.com>, Hadriel Kaplan <HKaplan@acmepacket.com>
Date: Wed, 31 Mar 2010 23:15:50 +0200
Thread-Topic: [martini] Issue with existing SIP trunking solutions,	was Re: #21: 3.2.2 describes an issue with some PBX
Thread-Index: AcrQ23D3EqrCTe1bR2izj67MexoX3wAO4MiA
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC745E21B5A90F@ESESSCMS0354.eemea.ericsson.se>
References: <p2i9ae56b1e1003310235hbbecb059r8b9b84bd91cad1f@mail.gmail.com> <430FC6BDED356B4C8498F634416644A91A79E92C83@mail> <n2i9ae56b1e1003310706pf2d3d6c6m550941d1579a1046@mail.gmail.com>
In-Reply-To: <n2i9ae56b1e1003310706pf2d3d6c6m550941d1579a1046@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_FF84A09F50A6DC48ACB6714F4666CC745E21B5A90FESESSCMS0354e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Issue with existing SIP trunking solutions, was Re:  	#21: 3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 21:15:32 -0000

--_000_FF84A09F50A6DC48ACB6714F4666CC745E21B5A90FESESSCMS0354e_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I agree with Hans Erik.

If it is about issues within existing solutions, wouldn't it be better to t=
ry to address those (by communicating with 3GPP/ETSI) instead of defining a=
 completely new mechanism?

Regards,

Christer

________________________________
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf =
Of Hans Erik van Elburg
Sent: 31. maaliskuuta 2010 17:07
To: Hadriel Kaplan
Cc: martini@ietf.org
Subject: Re: [martini] Issue with existing SIP trunking solutions, was Re: =
#21: 3.2.2 describes an issue with some PBX

Hi Hadriel,

People say there is a mistake in the ETSI/3GPP solution that martini is add=
ressing. I'm only trying to see if there really is a mistake or if this is =
just an opinion about a design choice being made. I am not yet convinced th=
at it is a mistake.

Also I think we need to be fair on this, martini is not addressing the issu=
es with existing solutions and fixing them, it is creating a new solution t=
rying to avoid some issues with existing solutions. That is a different app=
roach.

I think nobody denies the need for an option tag. In fact having an option =
tag for the IMS method would make sense. And would fix an issue with that s=
olution.

/Hans Erik van Elburg


On Wed, Mar 31, 2010 at 3:52 PM, Hadriel Kaplan <HKaplan@acmepacket.com<mai=
lto:HKaplan@acmepacket.com>> wrote:

Hi,
I'm not sure I understand the question exactly.
My only point was that in practice we've found that what IP-PBX's expect to=
 receive in the request-uri is inconsistent, and that even if the IP-PBX th=
inks it is following the ETSI model it's not clear what it will or should e=
xpect to get.
But really we're also focusing too much on this particular issue I think - =
there're other reasons to have the options-tag.

-hadriel

________________________________
From: Hans Erik van Elburg [mailto:ietf.hanserik@gmail.com<mailto:ietf.hans=
erik@gmail.com>]
Sent: Wednesday, March 31, 2010 5:35 AM
To: bruno.chatras@orange-ftgroup.com<mailto:bruno.chatras@orange-ftgroup.co=
m>
Cc: Hadriel Kaplan; richard@shockey.us<mailto:richard@shockey.us>; john.elw=
ell@siemens-enterprise.com<mailto:john.elwell@siemens-enterprise.com>; mart=
ini@ietf.org<mailto:martini@ietf.org>
Subject: Issue with existing SIP trunking solutions, was Re: [martini] #21:=
 3.2.2 describes an issue with some PBX

Hi Hadriel,

(Changed the thread name.)

Is your point that the use of a loose-route to the PBX as such is not so mu=
ch of a problem, but that SSP's would use it to deliver Request-URI's conta=
ining the SSP's domain to the IP-PBX?

BR,
/Hans Erik van Elburg



--_000_FF84A09F50A6DC48ACB6714F4666CC745E21B5A90FESESSCMS0354e_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.3790.4639" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D848041321-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D848041321-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D848041321-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I agree with Hans Erik.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D848041321-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D848041321-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>If it is about issues within existing solutions, w=
ouldn't=20
it be better to try to address those (by communicating with 3GPP/ETSI) inst=
ead=20
of defining a completely new mechanism?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D848041321-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D848041321-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D848041321-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D848041321-31032010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Christer</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> martini-bounces@ietf.org=20
[mailto:martini-bounces@ietf.org] <B>On Behalf Of </B>Hans Erik van=20
Elburg<BR><B>Sent:</B> 31. maaliskuuta 2010 17:07<BR><B>To:</B> Hadriel=20
Kaplan<BR><B>Cc:</B> martini@ietf.org<BR><B>Subject:</B> Re: [martini] Issu=
e=20
with existing SIP trunking solutions, was Re: #21: 3.2.2 describes an issue=
 with=20
some PBX<BR></FONT><BR></DIV>
<DIV></DIV>Hi Hadriel,<BR><BR>People say there is a mistake in the ETSI/3GP=
P=20
solution that martini is addressing. I'm only trying to see if there really=
 is a=20
mistake or if this is just an opinion about a design choice being made. I a=
m not=20
yet convinced that it is a mistake. <BR><BR>Also I think we need to be fair=
 on=20
this, martini is not addressing the issues with existing solutions and fixi=
ng=20
them, it is creating a new solution trying to avoid some issues with existi=
ng=20
solutions. That is a different approach.<BR><BR>I think nobody denies the n=
eed=20
for an option tag. In fact having an option tag for the IMS method would ma=
ke=20
sense. And would fix an issue with that solution.<BR><BR clear=3Dall>/Hans =
Erik=20
van Elburg<BR><BR><BR>
<DIV class=3Dgmail_quote>On Wed, Mar 31, 2010 at 3:52 PM, Hadriel Kaplan <S=
PAN=20
dir=3Dltr>&lt;<A=20
href=3D"mailto:HKaplan@acmepacket.com">HKaplan@acmepacket.com</A>&gt;</SPAN=
>=20
wrote:<BR>
<BLOCKQUOTE class=3Dgmail_quote=20
style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204=
,204,204) 1px solid">
  <DIV lang=3DEN-US vlink=3D"blue" link=3D"blue">
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT>=
&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Hi,</SPAN></FO=
NT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I&#8217;m not =
sure I=20
  understand the question exactly.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">My only point =
was=20
  that in practice we&#8217;ve found that what IP-PBX&#8217;s expect to rec=
eive in the=20
  request-uri is inconsistent, and that even if the IP-PBX thinks it is=20
  following the ETSI model it&#8217;s not clear what it will or should expe=
ct to=20
  get.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">But really we&=
#8217;re also=20
  focusing too much on this particular issue I think &#8211; there&#8217;re=
 other reasons to=20
  have the options-tag.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT>=
&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">-hadriel</SPAN=
></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT>=
&nbsp;</P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: mediu=
m none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: 1.5pt solid; P=
ADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <DIV>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT=
=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
  <HR align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</=
SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahom=
a"> Hans=20
  Erik van Elburg [mailto:<A href=3D"mailto:ietf.hanserik@gmail.com"=20
  target=3D_blank>ietf.hanserik@gmail.com</A>] <BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, March 31, 2010 5:=
35=20
  AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> <A=20
  href=3D"mailto:bruno.chatras@orange-ftgroup.com"=20
  target=3D_blank>bruno.chatras@orange-ftgroup.com</A><BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Hadriel Kaplan; <A=20
  href=3D"mailto:richard@shockey.us" target=3D_blank>richard@shockey.us</A>=
; <A=20
  href=3D"mailto:john.elwell@siemens-enterprise.com"=20
  target=3D_blank>john.elwell@siemens-enterprise.com</A>; <A=20
  href=3D"mailto:martini@ietf.org" target=3D_blank>martini@ietf.org</A><BR>=
<B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Issue with existing SIP t=
runking=20
  solutions, was Re: [martini] #21: 3.2.2 describes an issue with some=20
  PBX</SPAN></FONT></P></DIV>
  <DIV class=3Dim>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT face=3D"Times Ne=
w Roman"=20
  size=3D3><SPAN style=3D"FONT-SIZE: 12pt">Hi Hadriel,<BR><BR>(Changed the =
thread=20
  name.)<BR><BR>Is your point that the use of a loose-route to the PBX as s=
uch=20
  is not so much of a problem, but that SSP's would use it to deliver=20
  Request-URI's containing the SSP's domain to the IP-PBX?<BR><BR>BR,<BR=20
  clear=3Dall>/Hans Erik van Elburg</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV></DIV></DIV></DIV=
></BLOCKQUOTE></DIV><BR></BODY></HTML>

--_000_FF84A09F50A6DC48ACB6714F4666CC745E21B5A90FESESSCMS0354e_--

From dean.willis@softarmor.com  Wed Mar 31 16:36:03 2010
Return-Path: <dean.willis@softarmor.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 D66033A68CC for <martini@core3.amsl.com>; Wed, 31 Mar 2010 16:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.781
X-Spam-Level: 
X-Spam-Status: No, score=0.781 tagged_above=-999 required=5 tests=[AWL=-0.164,  BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13]
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 ud2E2jrBtMxA for <martini@core3.amsl.com>; Wed, 31 Mar 2010 16:36:03 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 122C13A6827 for <martini@ietf.org>; Wed, 31 Mar 2010 16:36:03 -0700 (PDT)
Received: from [192.168.2.112] (cpe-66-25-30-183.tx.res.rr.com [66.25.30.183]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id o2VNaUGR031116 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 31 Mar 2010 18:36:31 -0500
Message-Id: <C863E92B-43F4-4C4B-BE98-4B4E99E3FA77@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79E92C83@mail>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 31 Mar 2010 18:36:24 -0500
References: <p2i9ae56b1e1003310235hbbecb059r8b9b84bd91cad1f@mail.gmail.com> <430FC6BDED356B4C8498F634416644A91A79E92C83@mail>
X-Mailer: Apple Mail (2.936)
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Issue with existing SIP trunking solutions, was Re:  #21: 	3.2.2 describes an issue with some PBX
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: Wed, 31 Mar 2010 23:36:04 -0000

On Mar 31, 2010, at 8:52 AM, Hadriel Kaplan wrote:

>
> Hi,
> I=92m not sure I understand the question exactly.
> My only point was that in practice we=92ve found that what IP-PBX=92s =20=

> expect to receive in the request-uri is inconsistent, and that even =20=

> if the IP-PBX thinks it is following the ETSI model it=92s not clear =20=

> what it will or should expect to get.
> But really we=92re also focusing too much on this particular issue I =20=

> think =96 there=92re other reasons to have the options-tag.

The ETSI model for PBX behavior is currently underspecified. The IETF =20=

model is currently unspecified: we think of PBXes as big phones, and =20
our phone model is underspecified.

You expected this stuff to actually work without a more rigid interop =20=

spec?

And yeah, we need the options-tag anyhow.

--
Dean (who expects to be struck by a meteor tomorrow, just after the =20
alarm clock goes off, and will be pleasantly surprised if it doesn't, =20=

assuming he hasn't died first of something else and is therefore =20
unable to appreciate having not been hit by a meteor).=
