Re: [Ecrit] Emergency Call Framework for Canada; Questions on draft-ietf-ecrit-framework-09

["Stark, Barbara" <bs7652 at att.com>]

Most service providers do offer plans with multiple addresses, but the vast majority of people do not subscribe to these plans. Your service provider sounds unique in the world of service providers, to give away 3 addresses to all subscribers. Most service providers who utilize PPPoE limit (through RADIUS) the number of concurrent PPPoE sessions that are allowed to 1. The termination points for PPPoE sessions in the network tend to be capacity limited by number of concurrent sessions, so it would be a major cost to increase the number of supported PPPoE sessions per customer, in a world where those customers were actually expected to use those multiple sessions. Also, each PPPoE session requires an IP address. Today that's IPv4. As we all know, we're rapidly running out of those addresses, and doubling the number of IPv4 addresses used by all customer would be a Very Bad Thing. 

Oh, and help desk costs of helping people to enter PPPoE login password in an additional device are significant. Forgotten login/password info have historically been one of the largest help desk costs that service providers experience. Again, your proposal is a costly proposal.

People who can do the things that you have done in your home network are few and far between. You are not average. We must have solutions that work for the average person, and not just the special elite people who actually understand this stuff.
Barbara

> -----Original Message-----
> From: ecrit-bounces at ietf.org [mailto:ecrit-bounces at ietf.org] On Behalf
> Of "François D. Ménard"
> Sent: Tuesday, June 02, 2009 6:01 PM
> To: Brian Rosen
> Cc: ecrit
> Subject: Re: [Ecrit] Emergency Call Framework for Canada;Questions on
> draft-ietf-ecrit-framework-09
> 
> 
> > DHCP works very well in residential VoIP.  The phone may have a NATed
> > address, but as long as the home router passes the location option,
> > the
> > query to the provider will have the right thing to get the DHCP
> > system to
> > return the location of the residence.  If you don't like DHCP, use
> > HELD, but
> > you still have some remnants of the VPN problem.  Don't confuse DHCP
> > for LIS
> > discovery with DHCP for location configuration.  Both work, but DHCP
> > discovery of a HELD server works.
> >
> 
> I concur.
> 
> If you have a router which does not pass on DHCP Option 99, you can
> always initiate a PPPoE tunnel from your ATA and do a DHCP Option 99
> fetching through it.
> 
> There is nothing wrong with having multiple PPPoE sessions from your
> home to your ISP, and one dedicated to VoIP.
> 
> Furthermore, this will be an excellent mean to use PPPoE to prioritize
> the username/password for a VoIP PPPoE session over the username/
> password for Internet access, for two sessions coming from the same
> home.
> 
> The ATAs we use here can be patched to support DHCP Option 99 fetching
> through a PPPoE session. All you need is to put a little Ethernet
> switch between your DSL modem / Cable Modem and your ATA and to allow
> for the possibility that both your ATA as well as your Router will
> launch a PPPoE tunnel to your ISP.
> 
> I'll send you a sticker you can can put on your router here... plug
> here and die - this box does not pass on location.
> 
> This architecture has the added bonus of accelerating the transition
> to IPv6.
> 
> For those concerned with that, our wholesale cable modem incumbent
> cable operator, permits up to 3 public IPs behind a single cable
> modem, and I use a switch behind my CM to assign a separate public IP
> for my VoIP PBX SIPtrunk client, from the public IP address of my
> router, which currently is too dumb to relay DHCP Option 99.
> 
> So all I need is to have the DHCP server programmed to send a PIDF-LO.
> 
> And for my SIP client to support SIP LOCATION CONVEYANCE.
> 
> And for it not to never send a BYE if I dial 9-1-1, even if I hang-up.
> 
> F.
> 
> _______________________________________________
> Ecrit mailing list
> Ecrit at ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit

*****

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. 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 is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA625