Abhayakara / draft-ietf-homenet-simple-naming-arch

Simple Naming Architecture for Homenet
0 stars 0 forks source link

Architecture Section #5

Open mglt opened 7 years ago

mglt commented 7 years ago

I believe an architecture section describing the different components are as well as their interactions for various actions happening in the network is necessary. It would also be nice to have a diagram showing how these boxes or functions are interconnected.

The following elements I consider in the simple home network are: The Simple Home Network Naming Architecture is composed by the following elements:

o Discovery Proxies: The home network has at least one Discovery Proxy in order to make the services advertised through service discovery using mDNS available on any other links of the home network. A single Discovery Proxy for the whole network may be sufficient. Each Discovery Proxy defines a Proxy Zone attached to a specific subdomain. The subdomain can have a link granularity. The use of a single Discovery Proxy considers a single Proxy Zone for the whole home network.

o Discovery Broker: The home network has a single Discovery Broker. The Discovery Broker is believed to coordinates the resolution inside the home network. First, the Discovery Broker is aware of the different Discovery Proxies and associated Proxy Zones. In addition, the Broker is also aware of the Advertising Proxy that contains all resources registered by hosts or services.

o Advertising Proxy: The home network has a single Advertising Proxy specific homenet-aware devices or services register to.

o DNS Proxy: The home network has a DNS Proxy the DNS requests are sent to. The DNS Proxy is responsible to distinguish between the DNS queries that concerns the Global DNS and those that concern a resolution on the home network. In the simple home network architecture the difference is based on the "home.arpa" suffix.

o DNS Resolvers: That are in charge of performing the resolution over the Global DNS system. In the case of home networks multi- homed, it is expected that the Resolver can perform resolution via multiple ISPs or that each ISP is associated a Resolver. Optionally, a home network may also have multiple Discovery Relays. The complexity of Discovery Proxies may be lowered by the implementation of Discovery Relays. In that case, such devices are expected to associate themselves to a Discovery Proxy and instead of having their own Proxy Zone extends the one associated to the Discovery Proxy they are attached to.

Abhayakara commented 7 years ago

This is describing components of an architecture, not an architecture. This text isn't necessarily wrong, but it's not the right place to start.

Action item: Ted writes some text that talks about this at a high level and relates to this text; then we discuss what to do next?

mglt commented 7 years ago

fine. it might be challenging to describe the architecture without the components. ;-) I agree on going th is way.