RE: [Sipping-emergency] Re: [Sipping-emergency] draft-schulzrinne -sipping-emergency-req-00
"Peterson, Jon" <jon.peterson@neustar.biz> Tue, 25 February 2003 21:42 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18653 for <sipping-emergency-archive@odin.ietf.org>; Tue, 25 Feb 2003 16:42:51 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1PLq3601237 for sipping-emergency-archive@odin.ietf.org; Tue, 25 Feb 2003 16:52:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PLq3p01234 for <sipping-emergency-web-archive@optimus.ietf.org>; Tue, 25 Feb 2003 16:52:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18640 for <sipping-emergency-web-archive@ietf.org>; Tue, 25 Feb 2003 16:42:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PLq1p01217 for <sipping-emergency-web-archive@ietf.org>; Tue, 25 Feb 2003 16:52:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PLpcp01183 for <sipping-emergency@optimus.ietf.org>; Tue, 25 Feb 2003 16:51:38 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18632 for <sipping-emergency@ietf.org>; Tue, 25 Feb 2003 16:41:55 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11]) by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h1PLirC05904; Tue, 25 Feb 2003 21:44:53 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19) id <ZH2JPV08>; Tue, 25 Feb 2003 16:44:59 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214E43@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: 'Henning Schulzrinne' <hgs@cs.columbia.edu>, "King, Kimberly S." <KIMBERLY.S.KING@saic.com>
Cc: sipping-emergency@ietf.org
Subject: RE: [Sipping-emergency] Re: [Sipping-emergency] draft-schulzrinne -sipping-emergency-req-00
Date: Tue, 25 Feb 2003 16:44:57 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: sipping-emergency-admin@ietf.org
Errors-To: sipping-emergency-admin@ietf.org
X-BeenThere: sipping-emergency@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>, <mailto:sipping-emergency-request@ietf.org?subject=unsubscribe>
List-Id: <sipping-emergency.ietf.org>
List-Post: <mailto:sipping-emergency@ietf.org>
List-Help: <mailto:sipping-emergency-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>, <mailto:sipping-emergency-request@ietf.org?subject=subscribe>
I also looked around a bit on the web to see how the term 'last-mile' was being used. This seems typical of the definitions I could find: The last mile refers to the distance between the subscriber and the telephone company's central office, or the subscriber and the neighborhood node of the cable company. http://cablingdb.com/GlossaryPages/GlossaryL/Last_Mile.asp Refers to the telecommunications technology that connects the customer's home directly to the cable or telephone company. When used as an adjective, spelled last-mile, as in "the last-mile technology." http://isp.webopedia.com/TERM/L/last_mile.html - J > -----Original Message----- > From: Peterson, Jon [mailto:jon.peterson@neustar.biz] > Sent: Tuesday, February 25, 2003 1:33 PM > To: 'Henning Schulzrinne'; King, Kimberly S. > Cc: sipping-emergency@ietf.org > Subject: RE: [Sipping-emergency] Re: [Sipping-emergency] > draft-schulzrinne -sipping-emergency-req-00 > > > > Heh, right. I've been considering the 'last mile' chunk to be > between the > end user (currently, their POTS phone - in the future, their > IP phone) and > the selection router - that's how I thought we were using the > term in our > conf call, and hence my confusion (I was contrasting the > terms 'last mile' > with 'trunking replacement' on the call). The use of the term > 'access' in > the title of section 4 made me think you were describing the > access portion > of the network (i.e. copper to the home, etc). Your > suggestion in the intro > to the section that the transport could be analog or ISDN but might be > replaced with DSL certainly supported that reading. I thought the term > 'trunking' was used casually there. > > I guess looking more closely at that section, requirement M-7 > and a few > others might have tipped me off that these requirements were about the > trunking replacement. The definition in section 3 of 'last > mile emergency > service' also is a pretty good indicator. I don't know if > this would have > been unclear to someone who hadn't been on our conference > call. I imagine > that paraphrasing the definition of 'last mile' from section > 3 in the intro > to section 4 would clear up any conceivable ambiguity. I also > would avoid > using the term 'access' in the title of section 4. > > From my perspective anyway, what I'm concerned about is that > the full e2e > solution be bundled separately from the more immediately > achievable work. > Whether or not these two are in separate sections is less > material to me, > but ultimately, we know that the section 4 solution is not > depending on > geopriv, but the later material is. I think there is value in > having the > section 4 work go forward on its own merits, and fully specifying this > solution - I know you think this is trivial, but to me, trivial means > achievable. :) Putting the later e2e work in a separate document would > remove any geopriv dependencies for the section 4 work. > > - J > > > -----Original Message----- > > From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu] > > Sent: Tuesday, February 25, 2003 7:06 AM > > To: King, Kimberly S. > > Cc: Peterson, Jon; sipping-emergency@ietf.org > > Subject: Re: [Sipping-emergency] Re: [Sipping-emergency] > > draft-schulzrinne-sipping-emergency-req-00 > > > > > > Maybe we're getting closer to the source of the confusion... > > During the > > teleconference, I had associated 'last-mile' with the > > recently-completed > > NENA effort, which only deals with what section 4 describes. > > Since it's > > the last mile before reaching the PSAP/ECC, I used that term. Maybe > > others were thinking of what I'd consider 'first-mile', > i.e., from a > > VoIP phone to a PSTN gateway? > > > > That might explain a few of the rounds of discussion... > Jon, Allison: > > where's first and last? :-) > > > > King, Kimberly S. wrote: > > > Henning, > > > > > > > > >>"In last-mile access, an ECC replaces an analog (CAMA) or > > >>digital (ISDN) > > >>trunk with packet-based access, > > >>typically over one or more high-speed access lines such as DSL > > >>or leased > > >>lines." > > >> > > >>Suggestions on how to make this clearer are welcome. > > > > > > > > > > > > I believe it isn't as clear because it disorients the > > reader. The last mile > > > (reader is thinking from the perspective of being the client) has > > > packet-based access (access puts the reader in the > > perspective of being on > > > the "server" side). > > > > > > I can't completely re-word it as I'm not totally clear what > > you are trying > > > to say but I'll take a shot at it. > > > > > > "In the last mile situation, instead of calls being > > terminated by analog > > > (CAMA) or digital (ISDN) trunks, they are terminated by > > high-speed DSL or > > > leased line packet-based solutions." > > > > > > Kimberly > > > _______________________________________________ > Sipping-emergency mailing list > Sipping-emergency@ietf.org > https://www1.ietf.org/mailman/listinfo/sipping-emergency > _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency
- RE: [Sipping-emergency] Re: [Sipping-emergency] d… Peterson, Jon
- Re: [Sipping-emergency] Re: [Sipping-emergency] d… Henning Schulzrinne
- RE: [Sipping-emergency] Re: [Sipping-emergency] d… Peterson, Jon
- RE: [Sipping-emergency] Re: [Sipping-emergency] d… Peterson, Jon
- Re: [Sipping-emergency] Re: [Sipping-emergency] d… Henning Schulzrinne
- RE: [Sipping-emergency] Re: [Sipping-emergency] d… Peterson, Jon
- Re: [Sipping-emergency] Re: [Sipping-emergency] d… Henning Schulzrinne
- RE: [Sipping-emergency] Re: [Sipping-emergency] d… Peterson, Jon
- Re: [Sipping-emergency] Re: [Sipping-emergency] d… James M. Polk
- Re: [Sipping-emergency] Re: [Sipping-emergency] d… Henning Schulzrinne