Re: [v6ops] Requirements for IPv6 routers in various locations

Can we define what is a customer edge? Is it different than what I’ve mention in my previous email:

1) Pure residential
2) Residential with small home office
3) Residential/techie (with or w/o home office) that have exported services (email server, web server, VPN server, etc.).
4) Small home office
5) SMEs with just use Internet for “browsing”, emailing, etc.
6) SMEs as in the previous case that also have exported services (email server, web server, VPN server, etc.).

In my opinion is the router provided to residential customers, SMEs, etc., by 95% of the access links in the world and even sold in markets so customer can buy a new one if broken or a better one with better WiFi support to replace the one that the ISP deployed.

Some ISPs just provide a “modem” or “bridge” and is the customer the one that need to buy it.

Some ISPs make their own as OEM devices from vendors, or have such volume that get their logo on it and even specific firmware versions.

Smaller ISPs need to go to the local market to buy them because they need smaller quantities and have no way to ask for “features” which they need. Same as when you buy it in the local store, you will find what is generally available and can’t ask for a special software.

Regards,
Jordi

-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de Fred Baker <fredbaker.ietf@gmail.com>
Responder a: <fredbaker.ietf@gmail.com>
Fecha: miércoles, 22 de febrero de 2017, 2:29
Para: Joe Touch <touch@isi.edu>
CC: IPv6 Ops WG <v6ops@ietf.org>
Asunto: Re: [v6ops] Requirements for IPv6 routers in various locations

    > On Feb 21, 2017, at 5:17 PM, Joe Touch <touch@isi.edu> wrote:
    > 
    > 
    > 
    > On 2/21/2017 5:09 PM, Fred Baker wrote:
    >> This argument is essentially what I was referring to with respect to draft-ali-ipv6rtr-reqs when I said we had multiple markets that RFC 1812 didn't have to address. They include, at least, ISP, content network, data center, enterprise, residential, IoT, and mobile wireless networks. Those markets have differing non-exclusive sets of requirements.
    > Is there a way to focus on the core requirements that all routers need
    > to support in this doc, assuming that there are lots of things a router
    > in general MAY also do...
    > 
    > And then leave it to other documents to focus on the additional
    > requirements (or relaxations of SHOULDs) that apply to these environments?

    There may be; it would be the "core document" I referred to. A document that is accurately described as "7084-bis" would not be that document; 7084 describes a router in a particular application, and probably a particular price point, something called "customer-edge".
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops

**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.