[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ecrit] Why an applicability statement to framework and BCP is not required
- To: Richard Barnes <rbarnes at bbn.com>, "Winterbottom, James" <James.Winterbottom at andrew.com>
- Subject: Re: [Ecrit] Why an applicability statement to framework and BCP is not required
- From: Ted Hardie <hardie at qualcomm.com>
- Date: Wed, 25 Mar 2009 14:52:49 -0700
- Cc: "ecrit at ietf.org" <ecrit at ietf.org>
- Delivered-to: ecrit at core3.amsl.com
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=hardie at qualcomm.com; q=dns/txt; s=qcdkim; t=1238017977; x=1269553977; h=mime-version:message-id:in-reply-to:references:date:to: from:subject:cc:content-type:x-ironport-av; z=MIME-Version:=201.0|Message-ID:=20<p06240807c5f056f0e165 @[130.129.80.242]>|In-Reply-To:=20<49CA7782.2090806 at bbn.c om>|References:=20<E51D5B15BFDEFD448F90BDD17D41CFF1058BD1 8C at AHQEX1.andrew.com>=0D=0A=20<49CA7782.2090806 at bbn.com> |Date:=20Wed,=2025=20Mar=202009=2014:52:49=20-0700|To:=20 Richard=20Barnes=20<rbarnes at bbn.com>,=0D=0A=20=20=20=20 =20=20=20=20"Winterbottom,=20James"=0D=0A=09<James.Winter bottom at andrew.com>|From:=20Ted=20Hardie=20<hardie at qualcom m.com>|Subject:=20Re:=20[Ecrit]=20Why=20an=20applicabilit y=20statement=20to=20framework=20and=20BCP=0D=0A=20is=20 =20not=09required|CC:=20"ecrit at ietf.org"=20<ecrit at ietf.or g>|Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5300,2777,5564"=3B=20 a=3D"16596400"; bh=pRTn3Y8b6/7tGr8BxeVr6ABkj7KmDiODgFgXJysh1Ds=; b=ZCWc3S0NWjDGkLxePMRtigL60wPZL5HFxBmIhO+dtylABYIJUNafbI6u mLSP/2TESyU7d6uEattpfzWf9dJZpPfvrgdf6Ku+xeuBFNwA311A3W/xZ /NQEpVf7OwSMecYyQyQfenWE9RzHiNOg8FRaVu1C3mCmHmnYAigKPzLhi 0=;
- In-reply-to: <49CA7782.2090806 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: <E51D5B15BFDEFD448F90BDD17D41CFF1058BD18C at AHQEX1.andrew.com> <49CA7782.2090806 at bbn.com>
At 11:27 AM -0700 3/25/09, Richard Barnes wrote:
>This argument is pretty persuasive. Could someone who wants to add
>something propose a paragraph and explain why the below doesn't apply?
>If no such text is forthcoming, ISTM that we should go ahead with the
>document as it is.
>--Richard
Actually, the argument James puts forward below seems pretty much
the same as he put forward in late February, and which Stephen
answered then (Feb 26th, at least as it arrived to me).
It is pretty obvious that we're not going to get to full or measurable rough
consensus on this, and I thought Brian's text was a very useful step in getting
us to a working compromise. Going back over discussions that led us to the
conclusion that we weren't going to get consensus doesn't seem likely to move
us forward much.
I can't speak for anyone else, but moving forward with text discussions
to see if there is a compromise statement here seems more likely to get
us out of these weeds.
Two cents,
Ted
>Winterbottom, James wrote:
>> I agree with the people that have said this debate is farcical.
>>
>>
>>
>> Cellular carriers can and do market their 3G services as wireless
>> broadband. In a number of cases, and I can't believe that it is only
>> here, services provide open Internet connectivity allowing access to
>> independent voice service providers (not IMS). When these services are
>> sold in this manner, they are still cellular, but the carrier is really
>> just an ISP and the ECRIT model for emergency calling is as applicable
>> to them as it is for any DSL ISP. Any specific "cellular" emergency call
>> procedures are not invoked, the carrier by the very nature of the
>> service they are selling has broken the access-to-voice-service link.
>> This makes the ECRIT architecture applicable.
>>
>>
>>
>> The result is that no applicability statement is required in the ECRIT
>> documents. Indeed, unless specific statements in the 3GPP specifications
>> are made to say that open Internet services SHALL NOT be provided
>> through these technologies I can't see how ECRIT is not applicable to
>> cellular. I can't see 3GPP adding such a statement, and I think that
>> their primary customers would go up in arms if they did. I propose that
>> the applicability statement resolution be dropped unless the proponents
>> of these applicability statements can stand up and say that open
>> Internet services over 3GPP networks don't happen now and will not
>> happen in the future or they can point us to a 3GPP specification that
>> describes how a totally decoupled access and voice service can deliver
>> an emergency call to the correct PSAP.
>>
>>
>>
>> Cheers
>>
>> James
>>
>>
>>
>> ------------------------------------------------------------------------------------------------
>> This message is for the designated recipient only and may
>> contain privileged, proprietary, or otherwise private information.
>> If you have received it in error, please notify the sender
>> immediately and delete the original. Any unauthorized use of
>> this email is prohibited.
>> ------------------------------------------------------------------------------------------------
>> [mf2]
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Ecrit mailing list
>> Ecrit at ietf.org
>> https://www.ietf.org/mailman/listinfo/ecrit
>_______________________________________________
>Ecrit mailing list
>Ecrit at ietf.org
>https://www.ietf.org/mailman/listinfo/ecrit