[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ecrit] PhoneBCP
- To: Richard Barnes <rbarnes at bbn.com>, "Gellens, Randall" <randy at qualcomm.com>, ECRIT <ecrit at ietf.org>
- Subject: Re: [Ecrit] PhoneBCP
- From: "Edge, Stephen" <sedge at qualcomm.com>
- Date: Mon, 27 Apr 2009 22:42:00 -0700
- Accept-language: en-US
- Acceptlanguage: en-US
- Delivered-to: ecrit at core3.amsl.com
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=sedge at qualcomm.com; q=dns/txt; s=qcdkim; t=1240897324; x=1272433324; h=from:to:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version:x-ironport-av; z=From:=20"Edge,=20Stephen"=20<sedge at qualcomm.com>|To:=20R ichard=20Barnes=20<rbarnes at bbn.com>,=20"Gellens,=20Randal l"=20<randy at qualcomm.com>,=0D=0A=20=20=20=20=20=20=20=20E CRIT=20<ecrit at ietf.org>|Date:=20Mon,=2027=20Apr=202009=20 22:42:00=20-0700|Subject:=20RE:=20[Ecrit]=20PhoneBCP |Thread-Topic:=20[Ecrit]=20PhoneBCP|Thread-Index:=20AcnHu 8GIGqsMJy5ZQFmAuQlFWecLywABf2YA|Message-ID:=20<1288E74A73 964940B132A0B9EA8D8ABC5926A334 at NASANEXMB04.na.qualcomm.co m>|References:=20<C6177BF4.147ED%mlinsner at cisco.com><p062 4080dc617d32a1604 at [10.227.68.1=0932]>=0D=0A=09<49F27637.7 050201 at bbn.com>=0D=0A=09<E51D5B15BFDEFD448F90BDD17D41CFF1 04A3430A at AHQEX1.andrew.com>=0D=0A=09<058701c9c5d0$53c5ef4 0$fb51cdc0$ at net>=0D=0A=09<E51D5B15BFDEFD448F90BDD17D41CFF 104A3430B at AHQEX1.andrew.com>=0D=0A=09<28B7C3AA2A7ABA4A841 F11217ABE78D67590BD8E at FRMRSSXCHMBSB3.dc-m.alcatel-=0D=0A =09lucent.com>=09<p0624060ac61bfca58f3b at [172.28.171.53]> =0D=0A=20<49F6891E.7080706 at bbn.com>|In-Reply-To:=20<49F68 91E.7080706 at bbn.com>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5598"=3B=20a=3D"17531441"; bh=fWhPCUtuTRLQAf+J7bnSj2UlosQHN//vQAyX+IuOdB8=; b=kCJFuxpnXhkzRitSulvlVxRvM7gpbX+5yoW8LVjSNF8c48JzVvllO2hK Cci4tIMujYUQfsc5RV3vRqh4Fn/lzXwjAQ5dTXjHOneskrydzyyAvjs+d 86FSggHbYrVROX5N8faOv1otdtmGrPci5YavTOcqeljFioFX8s2+25Bib U=;
- In-reply-to: <49F6891E.7080706 at bbn.com>
- List-archive: <http://www.ietf.org/mail-archive/web/ecrit>
- List-help: <mailto:ecrit-request@ietf.org?subject=help>
- List-id: <ecrit.ietf.org>
- List-post: <mailto:ecrit@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
- References: <C6177BF4.147ED%mlinsner at cisco.com><p0624080dc617d32a1604 at [10.227.68.1 32]> <49F27637.7050201 at bbn.com> <E51D5B15BFDEFD448F90BDD17D41CFF104A3430A at AHQEX1.andrew.com> <058701c9c5d0$53c5ef40$fb51cdc0$ at net> <E51D5B15BFDEFD448F90BDD17D41CFF104A3430B at AHQEX1.andrew.com> <28B7C3AA2A7ABA4A841F11217ABE78D67590BD8E at FRMRSSXCHMBSB3.dc-m.alcatel- lucent.com> <p0624060ac61bfca58f3b at [172.28.171.53]> <49F6891E.7080706 at bbn.com>
- Thread-index: AcnHu8GIGqsMJy5ZQFmAuQlFWecLywABf2YA
- Thread-topic: [Ecrit] PhoneBCP
All
The statement "The underlying protocols can also be used to support other models in which parts of the process are delegated to the Communications Service Provider" seems applicable to the 3GPP/3GPP2 solution - e.g. because it does not say that all the protocols must be used, nor does it say that other protocols must not be used, but is consistent with a selection of some subset. (That is also applicable to the preferred Ecrit solution which allows choice of LCP in the network.)
So I support the current applicability statement and, based on the very long discussion that it took to get to that, foresee a possibly equally long discussion ahead if this issue has to be restarted.
Kind Regards
Stephen
-----Original Message-----
From: ecrit-bounces at ietf.org [mailto:ecrit-bounces at ietf.org] On Behalf Of Richard Barnes
Sent: Monday, April 27, 2009 9:42 PM
To: Gellens, Randall
Cc: ECRIT
Subject: Re: [Ecrit] PhoneBCP
Ok, we clearly need to revise the text, since that's a pretty serious
misunderstanding. The text doesn't constrain the use of the protocols
at all -- in fact it says "they underlying protocols can also be used to
support other models in which parts of the process are delegated to the
Communications Service Provider". For example, in the 3GPP model, an
E-CSCF could do everything on behalf of the endpoint, but could still
use SIP for calling, LoST for PSAP URI discovery, and HELD for location
retreival.
The point of the current text is just that those scenarios aren't
discussed in this draft, not that the overall model doesn't apply to
those scenarios.
--Richard
Randall Gellens wrote:
> I hum for the text, which doesn't constrain the use of the protocols,
> but merely describes the assumptions under which it works. As such, it
> is useful and helpful. Even for those who think the assumptions are
> obvious, it does no harm to state them.
>
> We had a lot of debate on this in SFO, and the text in this version was
> discussed on the mailing list in the days during and following the meeting.
_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www.ietf.org/mailman/listinfo/ecrit