Re: [homenet] New Version Notification for draft-howard-homenet-routing-comparison-00.txt

[Ray Hunter <[e-mail]>]

What is wrong with applying the Autonomous System concept to Homenet (as 
defined in RFC1930)?

IMVHO a number of problems might become clearer if Homenet explicitly 
acknowledged management boundaries and potential conflicts in routing 
policy.

Under RFC1930: Homenet would be classified as a multi-homed site.

A "Walled Garden" would then be when a Homenet AS has a private peering 
with a non-transit AS.

On the upside, there's also a number of private AS numbers reserved for 
use if needed.

Interestingly enough, applying the AS model also highlights a potential 
downside weakness in the current RFC6204 & 6204bis documents (which seem 
to assume that the customer's site is an integral part of a single 
provider's AS, and not an independent entity with its own routing 
policy), and PD & DHCPv6 (the protocol does not contain an AS number, 
and a Homenet may communicate with multiple non-coordinated sources of 
management information).

BTW I am not explicitly advocating BGP.

regards,
RayH

Michael Richardson wrote:
>>>>>> "Acee" == Acee Lindem<[e-mail]>  writes:
>>>>>>              
>      Acee>  Hi Michael, Can you provided a precise definition of "walled
>      Acee>  garden", as well as, define the bi-directional connectivity
>      Acee>  rules with a few bullets (hopefully less than 5). I fear there
>      Acee>  may be more than one view of this (or possibly I'm the only
>      Acee>  one ;^).
>
> I don't have a precise definition.
> This is what I would advance:
>
>    + A walled-garden network is provided by a service-specific internet
>      service provider (SS/ISP) to a residential or small office.
>    + The service-specific connection is in the form of a dedicated WAN link into
>      the dwelling. (The link may be physical or might be carried by a virtual
>      layer-2).  Some dwellings may have only the service specific connection.
>    + The service-specific connection provides access to a service
>      (IPTV is a known example), and is not general Internet service.
>    + The IPv6 service is reachable only using IPv6 from a block that the
>      service-specific ISP will allocate to the residence using regular
>      mechanism.
>    + The IPv6 service is numbered using globally unique IPv6 addresses,
>      which are usually not accessible outside of the "garden", i.e. they
>      are not routed in the global Default-Free Zone.
>    + In IPv6, no special DNS tricks are required to make the clients
>      systems pick the right target address.  Multiple AAAA records,
>      (possibly with walled-garden ACLs on authoritative servers) and
>      happy eyeballs is enough.
>
> A walled-garden is no different than a multiple ISPs in a residence,
> except that general internet traffic does not transit that connection.
>
>